Windows templates for the marketdata series domain: run-series.cmd and the routine's instructions - #114
Merged
Conversation
…d the routine's instructions Two templates beside the other wrappers, plus the docs that place them: - docs/examples/windows/run-series.cmd: `marketdata-update --build-tradingview` then the two replica syncs, each step guarded on its own following line, no in-file retry (the build reads local files; the retry is the second routine). Header says why it is not a Task Scheduler task, when it runs (18:30 and 19:45 ET, after the equities task and before the 20:55 futures window, so two mirror passes never overlap), and why the raw JSON never rides along (`_raw` is already excluded by both sync scripts). - docs/examples/windows/series-routine.md: the whole instruction set for the Claude Code Desktop local routines that are stage 1. Routine settings, the allow rules (Edit rather than Write, per the docs; the Bash rule matching the exact command; two spellings of the connector tool name), the five steps, the symbol table, what a good night looks like, and why the backfill goes through TradingView's own CSV export rather than a 5000-bar pull through the model. - WINDOWS_SCHEDULING.md gains the wrapper entry; SYNCING.md notes that `_raw/tradingview/` rides under the existing `_raw` exclusion; CHANGELOG. Docs only; the producer is marketdata 0.3.0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs only. Step 5 of cot-analyzer's
docs/design/tradingview-breadth-scoping.md, the box side of theseriesdomain that landed in marketdata 0.3.0 (mspinola/marketdata#31).docs/examples/windows/run-series.cmd: the build wrapper.--build-tradingview, thensync-store.cmd, thenpush-to-server.cmd, each guarded on its own line. No in-file retry: the build reads local files, and the retry is the second routine. Runs at about 18:30 and 19:45 ET, after the equities task and before the 20:55 futures window, so two mirror passes never overlap. Raw JSON never rides along:_rawis already excluded by both sync scripts.docs/examples/windows/series-routine.md: the instruction set for the two Claude Code Desktop local routines (stage 1). Routine settings, allow rules (Editrather thanWrite, which the docs say is never consulted for path rules; the exact Bash command; two spellings of the connector tool name), the five steps, the symbol table, what a good night looks like. The backfill goes through TradingView's own CSV export, not a 5000-bar pull through the model, and names a--tradingview-csvimport to follow in marketdata.WINDOWS_SCHEDULING.md,SYNCING.md,CHANGELOG.mdupdated.Live copies for the box (markers filled, plus the patched
verify-scheduling.ps1and the settings file) were handed over separately: the verifier is local-only on the box and not tracked here.🤖 Generated with Claude Code