feat(sf): PredictorTraining auto-syncs predictor.yaml from alpha-engine-config#194
Merged
Conversation
…ha-engine-config Closes the same staleness vector PR #193 closed for DataPhase1: the SF PredictorTraining task pulls alpha-engine-predictor on every run but relies on the dispatcher's local ``alpha-engine-predictor/config/predictor.yaml`` for training config. That file is gitignored in the predictor repo and must be staged from the alpha-engine-config sibling clone — but nothing in the SF flow was keeping the staged copy in lockstep with origin/main of alpha-engine-config. The 2026-05-09 horizon migration (alpha-engine-config #90: forward_days 5 → 21, output_distribution_gate_blocking false → true, purge_days bump) would not have reached the next Saturday training without a manual SSM-side intervention to copy the config from alpha-engine-config to alpha-engine-predictor. Adds two commands before the spot_train.sh invocation: - ``git -C alpha-engine-config pull --ff-only origin main`` - ``cp alpha-engine-config/predictor/predictor.yaml alpha-engine-predictor/config/predictor.yaml`` Now any merged config change in alpha-engine-config reaches the next PredictorTraining cycle automatically. Mirrors the symmetric DataPhase1 fix from PR #193. Co-Authored-By: Claude Opus 4.7 (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
Symmetric fix to PR #193 (DataPhase1's alpha-engine-config pull). PredictorTraining task pulls alpha-engine-predictor but relies on the dispatcher's local
alpha-engine-predictor/config/predictor.yaml(gitignored in predictor repo, staged from alpha-engine-config sibling clone). Nothing was keeping the staged copy in lockstep with origin/main of alpha-engine-config.The 2026-05-09 horizon migration (alpha-engine-config #90:
forward_days 5 → 21,output_distribution_gate_blocking false → true,purge_days 5 → 21) would not have reached the next Saturday training without a manual SSM-sidecpintervention.Adds two commands before the spot_train.sh invocation:
git -C alpha-engine-config pull --ff-only origin maincp alpha-engine-config/predictor/predictor.yaml alpha-engine-predictor/config/predictor.yamlTest plan
🤖 Generated with Claude Code