Scheduled snapshot-age freshness check + deterministic push-CI rehearsal (punch-list 9) - #3
Merged
Merged
Conversation
…s/freshness.yml and scripts/check_freshness.py to private before next overlay)
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 shipped
scripts/check_freshness.py(stdlib-only, fail-closed,--todayinjectable): red when the shipped sample'ssnapshot_dateis >180 days old. FRESH today (snapshot 2026-07-15, deadline 2027-01-11).Per SOP §6.7, README/docs/streamlit_app are overlaid from the private repo — this PR deliberately touches only
.github/workflows/andscripts/. Port BOTH.github/workflows/freshness.ymlANDscripts/check_freshness.pyinto the private repo before the next overlay deploy, and add them to the SOP's public-only file list (the SOP file itself is overlay-owned, so that edit belongs in the private repo).Process
PM-briefed SME plan, Fable plan review, GPT 5.6 Sol implementation, adversarial QC + verified findings, supervised fixes (the
!-negation rehearsal was proven under GitHub'sbash -esemantics). Full data-integrity gate green at every commit.