Repository navigation
chore(register): review-rr strategic — curation, and a drift class the guard cannot catch - #179
Merged
Merged
Conversation
…e guard cannot catch Two entries sat under Open with their defects already fixed: - C-63 (the silent config fork) was fixed by #149 on 2026-07-31 — the manager carries zero wire_contract branches and two launch_config asserts — but the entry never moved. - C-47 (the stale reconciliation/ bytecode) was fixed by #177 hours ago. Worth naming precisely: test_register_integrity.py did NOT catch either, and correctly so. It asserts that no entry whose HEADING says RESOLVED sits under Open. Neither heading said so — the code was fixed and the record was not. The guard verifies internal consistency; only reading the tree catches this. C-62's trigger had already fired. It read "when cutting this repo's first release (#125)" — 1.0.0 was tagged on 2026-08-01 and the dependency drag shipped with it. Rewritten to the half that is still ahead: the 3.0.0 bump, plus a re-check before any PyPI publish, which is the point the footprint reaches someone else. Cluster M added: five open concerns, one upstream publish. C-44, C-62, C-72, C-73 and C-07 all resolve on the pipeline-core 3.0.0 pin bump and none can be taken before it. They had been readable as five separate backlog items; they are one blocked action. What this repo owes at the bump is a single verification — confirm the delivery selects the run it expects — recorded in C-73's trigger. Register: 73 concerns, 24 open, 49 resolved. Integrity guard green. Co-Authored-By: Claude Fable 5 <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
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.
Strategic pass on the register. 2 resolved, 1 trigger rewritten, 1 cluster added.
The finding worth naming
Two entries sat under Open with their defects already fixed — C-63 (fixed by #149 yesterday) and C-47 (fixed by #177 hours ago).
test_register_integrity.pydid not catch either, and correctly so. It asserts that no entry whose heading says RESOLVED sits under Open. Neither heading said so — the code was fixed and the record wasn't. The guard verifies internal consistency; only reading the tree catches this.That's a real limit of the mechanical guard I added on 31 July, and it's now stated rather than assumed.
C-62's trigger had already fired
It read "when cutting this repo's first release (#125)". was tagged yesterday and the dependency drag shipped with it. Rewritten to the half still ahead — the 3.0.0 bump — plus a re-check before any PyPI publish, which is the point the footprint reaches someone other than this team.
Cluster M — five concerns, one publish
C-44, C-62, C-72, C-73, C-07 all resolve on the pipeline-core 3.0.0 pin bump, and none can be taken before it. They had been readable as five separate backlog items. They are one blocked action, and the register should say so rather than let a reader triage them separately five times.
What this repo owes at the bump is one verification, already in C-73's trigger: confirm the delivery selects the run it expects.
Register: 73 concerns, 24 open, 49 resolved.
🤖 Generated with Claude Code