Repository navigation
fix(gates): close the last six boundaries (#2492) - #2507
Merged
Merged
Conversation
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-23 06:47:23 UTC
Summary
Seal Status
|
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.
All twelve boundary survivors from #2503 are gone. The suite stands at 111 mutants across 13 gates — 36 silent, 21 loud, 33 invert, 21 boundary — with two survivors, both proven equivalences that carry their proof in the row.
The six closed here, and what they had in common
Every one needed an input no case had a reason to build, and in each the missing input was the degenerate one:
v[0] > 0in the prose censustotal > 0 and data == 0for a new file>=, on a tree with nothing wrongtotal == 0 and old[0] > 0>=a file that never made one is announced EMPTIED on every run foreverlen(parts) > 1parsing the ledger>=the index raises and the gate dies on a healthy treelen(fixed) > 5Nothing exotic. A control author plants the fault they are testing for, which is by construction a non-degenerate example: a file with the wrong contents, not a file with no contents. The boundary operator's whole yield is the empty case, the equal case, and the one-off-the-edge case — the inputs that are nobody's example.
Two boundaries, one planted tree
The prose count appears in
--update-baseline's header and again in the verify path's census line. A single fixture carrying a zero-case file at record time pins both, because they are the same question asked on either side of the ledger. That case needed its own function for the same reason the refusal case does: what differs is when the fault arrives, and every table case plants after the ledger is written.Cosmetic closed rather than declared, twice
Both
"(+N more)"guards change a message and nothing else. Both got a case anyway — this campaign has twice found a written-down limitation to be invented, and a declared exception costs every future reader more than a case costs to write once.Refs #2492