feat: recover data history and archive vintages - #2
Open
jonit-dev wants to merge 2 commits into
Open
Conversation
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.
Status
PARTIAL: the full data-history/vintage implementation and offline tests are present. Real ALFRED history, committed vintage archives, live OI growth, and live on-chain missingness proof are blocked because noFRED_API_KEYexists locally or in GitHub repository secrets.Source PRD:
docs/PRDs/2026-08-02/DATA_HISTORY_RECOVERY_AND_VINTAGE_ARCHIVE.md(authoritative local input for this swarm run).Changes
insufficient-dataregime handling.FRED_API_KEYinto the data-only forecast refresh workflow and added coverage/freshness tests.Verification
yarn test: PASS, 27 files / 116 tests.yarn lint: PASS.yarn build: PASS; existing large-chunk warning only.yarn build:features: PASS, 5,842 rows.yarn backtest: PASS quality and robustness gates.yarn validate:features: expected FAIL,futuresOpenInterestUSD28/30.yarn check:freshness: expected FAIL on stale baseline sources versus declared caps.yarn validate:data: known baseline FAIL, 5,722 CoinMetrics MVRV mismatches.No fabricated
src/data/vintagesrecords were committed. The workflow has no deployment step.External blocker / merge condition
FRED_API_KEYis absent andgh secret listis empty. The exact unblock is:Do not claim the real 2010+ macro/vintage acceptance or merge this PR as complete until the real updater run produces and verifies the archives, reconstruction, and growing OI history.