Repository navigation
Revert the corpus re-pin (#258): the runner preflight binds the gitlink to the campaign's corpus head - #259
Merged
Merged
Conversation
…neration (#258)" The Cloud Run case runner's preflight requires the corpus bundle commit (the campaign's corpus evidence head, bound to the active baseline: b46cd80) to equal the engine's corpus gitlink; #258 moved the gitlink to 442d497 and the first sweep on top of it rejected a job ("corpus bundle commit differs from the Engine gitlink"). The regenerated corpus stays on pineforge-corpus main for local runs and is re-pinned together with the next baseline promotion. This reverts commit c64a682. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01CSmYixVAp4NqWpBZxkrLPT
luisleo526
added a commit
that referenced
this pull request
Sep 21, 2026
… lane N15, item 1) The recorded gitlink b46cd80 predates the R4-D host shape: its committed generated.cpp derive from BacktestEngine and assign the members the lowering moved behind pineforge::source::PineStrategyConfig (script_has_strategy_close_, process_orders_on_close_, max_intraday_filled_orders_), so -DPINEFORGE_BUILD_CORPUS_STRATEGIES=ON does not build at the pin the repository records. Every R5 lane's parity sweep therefore ran at 442d497 by hand, a pin nothing recorded. This is #258 (reverted by #259) restored. #259's reason was external: the Cloud Run case runner's preflight requires the lane's registered corpus bundle commit to equal the Engine tree's corpus gitlink (cloudrun/runner/preflight.mjs, materializeCorpusRepository), and the campaign registry still pinned b46cd80 from migration 0037. That side is re-pinned by the companion pineforge-workflow branch n15/corpus-pin; the two must land together. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> (cherry picked from commit 477003849563300547231762246c04723018b617)
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
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.
Reverts #258. The Cloud Run case runner's preflight requires the corpus bundle commit (the campaign's corpus evidence head, bound to the active baseline:
b46cd80) to equal the engine's corpus gitlink. The first sweep on a tree carrying #258 rejected a job withcorpus bundle commit differs from the Engine gitlink, which would surface ascoverage.lost-measurement.The regenerated corpus (pineforge-corpus#18, main
442d497) stays available for localrun_corpus.shruns (git -C corpus checkout main) and is re-pinned together with the next baseline promotion. No engine code changes.🤖 Generated with Claude Code
https://claude.ai/code/session_01CSmYixVAp4NqWpBZxkrLPT