steve
9534e442fb
Sonnet's three findings, all on the tests rather than the rule: - The "at the bound" case sat at index 115 (and 101 after the first round), never at 120 itself, so <= vs < was never exercised. Both sides of the boundary are now pinned — index 120 accepted, 121 rejected — and an off-by-one mutation is killed by the new case. - A SHORT (<=120-byte) deictic closer takes the modeBackRef bar, not the summary closer's mandatory dwarf ratio, even though it can carry a scrap of answer content. That asymmetry is deliberate and pre-existing (a "see above" closer has always had it): inside 120 bytes there is no room for both a pointer and a real answer. Pinned with a case sized so the two bars actually DISAGREE — 3x98 = 294 > the 275-byte prior turn, so the summary bar would reject what the back-ref bar accepts. The first draft of this fixture was 83 bytes and passed under either bar, proving nothing. - The isBackRef doc finding was sonnet's fourth independent report of it; already fixed in the previous commit. Break-check now runs eight mutations, including the off-by-one and a swap of the classifier ordering; each is killed by a named test and the control survives.