docs: correct stale v2 migration status in config and README#13
Merged
Conversation
The store was migrated to schema v2 by a full producer pass (2026-07-14), but two doc statements still described the pre-migration world: - config.py claimed the store "does not actually carry v2 shape until a full producer pass re-writes it" — no longer true. Reword to note the migration is done and that schema_version() reflects on-disk truth. - README described Volume_Reconstructed as "systematically higher than raw Volume." Verified against the store this is symbol-dependent: higher for products whose rolls spread volume across contracts, but roughly equal or lower for near-empty-back-month symbols like crypto (BTC/ETH reconstruct to ~0.98-1.00x raw). Reword to reflect that. Docs-only; no code behavior change. Store verified: schema_version=2, 84/84 price files carry reconstructed volume. Co-Authored-By: Claude Opus 4.8 <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.
What
Two docs-only corrections. The schema v1→v2 reconstructed-volume migration completed via a full producer pass on 2026-07-14, but two statements still described the pre-migration world:
config.pyclaimed the store "does not actually carry v2 shape until a full producer pass re-writes it." No longer true — reworded to note the migration is done and thatschema_version()reflects on-disk manifest truth (a fresh/partial store can still read <2).README.mddescribedVolume_Reconstructedas "systematically higher than raw Volume." Verified against the live store: it's symbol-dependent — higher for products whose rolls spread volume across contracts, but roughly equal or lower for near-empty-back-month symbols like crypto (BTC/ETH reconstruct to ~0.98–1.00× raw). Reworded accordingly.Verification
Checked against the actual store (
schema_version=2):Volume_Reconstructed; 829k rows allVolume_Source=reconstructed.No code behavior change.
🤖 Generated with Claude Code