Align snapshot-age claims with validator behavior - #37
Merged
Conversation
Re-express the claim-hygiene stabilization slice against current main. Removes hardcoded, drift-prone snapshot-age wording from the release note and reviewer demo notes and points reviewers to the dashboard's dynamically computed snapshot-age badge instead. Replaces the matching hardcoded day-count guards in validate-public-mirror.ps1 with a durable badge-cue check. Adds public-backlog follow-ups for a publication-time stale-snapshot gate, a stale-source fail-vs-warn decision, Python/PowerShell validator unification, and computed source/weather stale status. Scope is limited to docs and validator claim-hygiene. Main already had no -AllowStaleSnapshot references and its fail-closed language accurately describes the refresh pipeline, so neither was changed. 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.
Small, focused claim-hygiene slice re-expressed against current
main(a follow-up to the review that produced the larger, still-open #36).What this changes
docs/public-snapshot-release-note-2026-05-13.mdanddocs/reviewer-demo-notes.md(the "23 days old" / "25 days old" phrasing) and pointed reviewers to the dashboard's dynamically computed snapshot-age badge instead.scripts/validate-public-mirror.ps1(twoAssert-TextContainsneedles that required a specific day count) to check for the durable badge cue — so the guards can't drift out of sync with the docs again.docs/public-backlog.md) for a publication-time stale-snapshot gate, a stale-source fail-vs-warn decision, Python/PowerShell validator unification, and computed source/weather stale status.Deliberately not changed on main
-AllowStaleSnapshot:mainhas no references to this flag anywhere, so there was nothing to remove.mainthis accurately describes the real refresh-pipeline gate (refresh-live-data.ps1stops on stale FHABS resources, per the formal refresh runbook and a recorded rehearsal). It was left intact rather than downgraded, to avoid making the docs less accurate.These branch-only concerns are handled separately on the larger field-sensor-readiness branch (#36).
Validation
python scripts/validate-public-mirror.py→ PASS (exit 0)pwsh ./scripts/validate-public-mirror.ps1→ PASS (exit 0)git diff --check→ cleanRemaining validator output is the intentional staleness warnings (snapshot age, FHABS source ages) — the trust signals this slice preserves. Scope is docs + validator claim-hygiene only; no dashboard or data-publication code touched.
🤖 Generated with Claude Code