docs: STATUS.md — v0.21.7 is Latest, and the board snapshot was four days stale - #416
Merged
Merged
Conversation
…days stale RELEASE_PROCESS §4 owes a STATUS.md refresh after every release. It still said 'In preparation: v0.21.7' / 'Latest: v0.21.6' an hour after v0.21.7 published, and the board snapshot was from 2026-09-15: proven 70,337 against today's 98,935, contributors 7 against 8, spine [1..45,648] against [1..79,655]. ⛔ AND IT RECORDS SOMETHING THE RELEASE DID NOT FINISH. hazync.org/verify/ still serves v0.21.6's module — 1,064,517 B, sha 344a21b9…, byte-for-byte the previous release — against v0.21.7's 1,065,400 B (f66cfc1f…). check-deployed-verifier.sh fails on exactly this: 'the site is serving something the release did not ship'. The §3 browser-verifier cutover has not run, so the page a stranger lands on from the README's 30-second demo is a release behind. ⚠ The deployed module is STALE, not broken: it still reports the canonical guest id, verifies the live spine through 79,666, and rejects a bit-flipped proof. Saying so matters — 'out of date' and 'wrong' are different problems. Board crossed 10% (pct 10.017) between the release and this commit.
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.
RELEASE_PROCESS.md§4 owes aSTATUS.mdrefresh after every release.What was stale
[1..45,648][1..79,655]The board crossed 10% (
pct 10.017) between the release and this commit.⛔ And it now records something the release did not finish
hazync.org/verify/still serves v0.21.6's module — 1,064,517 B, sha344a21b9…, byte-for-byte identical to the previous release — against v0.21.7's 1,065,400 B (f66cfc1f…).check-deployed-verifier.shfails on exactly this:The §3 browser-verifier cutover has not run, so the page a stranger reaches from the README's 30-second demo is a release behind.
⚠ Stale, not broken. The deployed module still reports the canonical guest id, verifies the live spine through block 79,666, and rejects a bit-flipped proof. Those are different problems and the doc says which one this is.