Repository navigation
Extend the Mover v3 session calendar back to 2015-09-01 (N01 reach) - #194
Merged
Merged
Conversation
The code-first core in #190 requires the calendar from 2015-09-01, the t-60 lookbacks of the first 2016 sessions; the file generated for #186 began at 2016-01-04 (independent review finding N01, calendar reach). Regenerated deterministically with the same pinned exchange_calendars 4.13.2 / tzdata and the same columnar schema: 3854 sessions, 34 early closes (adds 2015-11-27 and 2015-12-24), last session 2030-12-31 unchanged. data-pins.json, the generator pin, the tests and the evidence manifest are updated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
seathatflowsinourveins
added
the
lane:trading
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
seathatflowsinourveins
deleted the
claude/mover-v3-calendar-2015-reach
branch
September 24, 2026 15:58
seathatflowsinourveins
pushed a commit
that referenced
this pull request
Sep 25, 2026
Main moved 150+ commits, including #186 and #194 (the v3 data files and calendar extension) and #197 (leverage-ladder gate wording in the v3 README, which merged cleanly). manifests/evidence.json is main's registry with the stale digests refreshed. The study tree is bound by its own tree hash and pinned copies, and was never registered there. Co-Authored-By: Claude Opus 5.5 (1M context) <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
Resolves the calendar-reach part of independent-review finding N01 on #190: the code-first core requires
data/session-calendar.jsonfrom 2015-09-01 (the t-60 lookbacks of the first 2016 sessions); the file from #186 began at 2016-01-04.exchange_calendars==4.13.2, pinned tzdata, same columnar schemasession, open_et, close_et, open_utc, close_utc, early_close;--checkreports a byte match).data/session-calendar.jsonsha25644f0ebf7c82ceee6a1fd2beceeca38c5a1e894c723bbc7c0ac677f452f592b5c(514006 bytes); generator sha256c646bcd8…;data-pins.jsonsummary updated.Checks
python3 -m unittest tests.test_mover_v3_data: 18 OK (adds a 2015 early-close assertion; the 2016-2020 list is now windowed);scripts/validate.py: passed (5280 hashed files);scripts/evidence_manifest.py --check: ordered.🤖 Generated with Claude Code