docs: retract an unfounded claim v2.4.1's notes made about v2.3.9 - #431
Merged
Conversation
v2.4.1's release notes carried a section headed "a claim v2.3.9 made that v2.3.9 did not ship", asserting that v2.3.9's published body described release_anchor_audit.rs while the tag did not contain it. That is false, and it was published. What the v2.3.9 body actually says, under the heading "The release anchors, and two documents that were wrong about more than the version", is that eight documents held six different answers about the current version and that "All now read v2.3.9". That describes a MANUAL re-synchronisation, and the manual re-synchronisation is in the v2.3.9 tag. Checked rather than re-asserted: the published body contains no occurrence of "release_anchor_audit", "anchor audit", "standing", "pins", "gate", or "15 anchors", and neither does the v2.3.9 CHANGELOG section. Both halves of the original claim were separately true, which is how they combined into something false. The file really is absent from the tag: $ git cat-file -e v2.3.9:crates/rustynes-test-harness/tests/release_anchor_audit.rs fatal: path '...' exists on disk, but not in 'v2.3.9' And v2.3.9 really is where the anchor drift was found. The step that was never performed was reading the v2.3.9 body to confirm it claimed the gate. It claimed the fix, which it shipped. A hand correction fixing the instance and a later commit adding the mechanism is ordinary sequencing, not a release note describing work its tag does not contain. The retraction is written into the notes rather than edited out of them. The claim was an accusation against a shipped release, it was published under a heading that made the accusation the section's subject, and deleting it would leave no record that the previous release had been wrongly impugned -- which is the shape of scrubbing this project has a standing rule against. AGENTS.md carried the same sentence, since that is where the v2.4.1 summary was drafted from, and is corrected the same way. The published GitHub release body for v2.4.1 is updated from this file, so the repo copy and what users read agree again.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Antigravity review (Gemini via Ultra)This PR updates the v2.4.1 release notes and Blocking issuesNone found. Suggestions
Nitpicks
Automated first-pass review by |
doublegate
added a commit
that referenced
this pull request
Aug 20, 2026
…432) #431 retracted the claim. This records the cause, because the instance is the least interesting part of it. Both inputs to the false statement were real and each had been checked independently: release_anchor_audit.rs genuinely is absent from the v2.3.9 tag, and v2.3.9 genuinely is where the anchor drift was found. What was never checked was the conjunction -- that v2.3.9's release body therefore DESCRIBED the audit -- and checking it was one command: gh release view v2.3.9 --json body That body says the eight drifted documents "All now read v2.3.9", a manual re-synchronisation which is in its tag, and contains no occurrence of "release_anchor_audit", "standing", "gate", or "15 anchors". Verifying every premise is not verifying the conclusion drawn from them. Two propagation mechanisms matter more than the instance, and the bullet names both. The sentence was written into AGENTS.md during the v2.4.0 work, and the v2.4.1 release summary was then drafted FROM AGENTS.md. That is the laundering step: an unverified claim entering this file is indistinguishable from a verified one by the time the next release quotes it, and it then reaches a published release body, a commit body, a PR body and a report to the maintainer in a single pass. AGENTS.md is a notes file, not an oracle, and this is the first entry that says so about itself. The claim also had the shape this project rewards -- a recursive irony, "the same failure one level up". That shape actively suppresses the check, because it reads as an insight rather than as an assertion needing evidence. The house style's appetite for findings of that form is exactly why it needs a verification bar rather than less of one. The bar stated: before writing that a document, release, commit or person SAYS something, open it and grep for the words. Nothing else changes -- one bullet, inserted beside the sibling traps it belongs with (the reviewer-claim bullet it now precedes is the same failure with a different source).
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.
v2.3.9's release notes are not wrong. The claim v2.4.1 made about them is, and it was published.
v2.4.1's notes carried a section headed "a claim v2.3.9 made that v2.3.9 did not ship", asserting that v2.3.9's published body described
release_anchor_audit.rswhile the tag did not contain it.What v2.3.9 actually says
Under "The release anchors, and two documents that were wrong about more than the version", it says eight documents held six different answers and "All now read v2.3.9." That describes a manual re-synchronisation — and the manual re-synchronisation is in the v2.3.9 tag.
Checked rather than re-asserted: the published body contains no occurrence of
release_anchor_audit, "anchor audit", "standing", "pins", "gate", or "15 anchors". Neither does the v2.3.9 CHANGELOG section.How two true facts made a false one
Both halves stood up separately. The file really is absent from the tag:
…and v2.3.9 really is where the anchor drift was found. The step never performed was reading the v2.3.9 body to confirm it claimed the gate. It claimed the fix, which it shipped. A hand correction fixing the instance, followed by a later commit adding the mechanism, is ordinary sequencing — not a release note describing work its tag does not contain.
Why it is retracted in place rather than deleted
The claim was an accusation against a shipped release, published under a heading that made the accusation the section's subject. Deleting it would leave no record that the previous release had been wrongly impugned — the shape of provenance scrubbing this project has a standing rule against. So the section is rewritten to say what is true and to state what it previously said and that it was wrong.
Changed
.github/release-notes/v2.4.1.md— section rewritten as "The release anchors, and the gate that arrived after them", with the retraction stated in it.AGENTS.md— carried the same sentence, since the v2.4.1 summary was drafted from it; corrected the same way.Already applied outside this branch: the published v2.4.1 GitHub release body has been updated from the corrected file, and #430's body now carries the retraction inline, so nothing a reader reaches still asserts it.
Docs only — no source, no manifests. AccuracyCoin and the workspace suites are untouched by construction.