F05 closed: stale partial note — row-6 tests exist and provably watch the row - #10
Merged
Conversation
…tch the row The note recorded row 6 (staging-count sanity) as untested; 5.0.1 added both directions to layer2-ledger-rows.js (deny 20-staged-vs-1-edit isolated from row 5 by a fresh build marker; proportionate negative). Verified before closing: all eleven rows have sections, the file runs 31/0, and a red-test neutering the threshold failed exactly the row-6 positive (30/1), restoring to 31/0. findings_partial now holds F24 alone (U7-floor clause, PHV5-003). Consistency sweep PASS; full suite 8/8. 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
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.
Summary
F05's
findings_partialentry recorded ledger row 6 (the staging-count sanity check) as having no test. That note went stale in 5.0.1, which added both directions totests/layer2-ledger-rows.js: the deny case (20 staged vs 1 session edit, isolated from row 5 by a fresh build marker, against a real repo) and the proportionate negative.Verified before closing, per house convention:
dg-git-guard.js(edits*2+5→edits*2+5000) failed exactly the row-6 positive check (30/1); restoring returned 31/0 — the test provably watches the row.status.json: F05 →findings_closed;findings_partialnow holds F24 alone (its single remaining clause — runtime verification at the U7 floor — rides PHV5-003, which has never run). The_whyprovenance is preserved with a dated addendum.Verification
🤖 Generated with Claude Code