test(artifact-registry-coverage): Phase 4 PR 6 — ae-predictor producer-side CI guard#204
Merged
Merged
Conversation
…r-side CI guard Phase 4 PR 6 of the artifact-freshness-monitor arc (plan doc: ~/Development/alpha-engine-docs/private/artifact-freshness-monitor-260527.md). Mirrors alpha-engine-data PR 4 (#336, merged 2026-05-27) across the ae-predictor repo. Cascade completes producer-side coverage across ae-data + ae-research + this repo + ae-backtester. What this catches: new s3.put_object(...) / s3.upload_file(...) in ae-predictor production code without a matching ARTIFACT_REGISTRY.yaml entry. Forces operator attention at every new producer addition. Initial pin: 24 PUT sites across 10 files in ae-predictor production code. Concentrated in training/ (meta_trainer has 7 PUTs covering the slim cache + manifest + diagnostics + risk-model artifacts). Design choice — per-file count over per-key-template extraction. See ae-data PR 4 commit message for the full rationale. 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
Phase 4 PR 6 of the artifact-freshness-monitor arc (plan doc at
~/Development/alpha-engine-docs/private/artifact-freshness-monitor-260527.md; ROADMAP P1 entry in alpha-engine-config #342 / #344). Mirrors alpha-engine-data PR 4 #336 (merged 2026-05-27) across the ae-predictor repo. Cascade now covers ae-data + ae-research + this repo + ae-backtester (PR 7 ships same session).What this catches
A new
s3.put_object(...)ors3.upload_file(...)in ae-predictor production code that hasn't been registered inalpha-engine-config/private-docs/ARTIFACT_REGISTRY.yaml(or explicitly grandfathered). Forces operator attention at every new producer addition.Initial pin
24 PUT sites across 10 files in ae-predictor production code. Concentrations:
training/meta_trainer.py: 7 (per-component weights + manifest + diagnostics + slim cache)training/risk_model_persist.py: 2 (F-matrix + metadata)regime/substrate.py: 2 (dated + latest pointer)inference/s3_io.py: 2 (predictions + daily_closes)Test plan
pytest tests/test_artifact_registry_coverage.py -v— 3 passing🤖 Generated with Claude Code