Ran the suite after a session of edits to boot.gd, screen_view.gd, four tools and
two authored files. Every asserting check passes, and verify-screen's two DIFFERS
are the named pair with per-screen reasons.
Two oracle rows moved: title_plate 12.83/0.00% to 13.04/0.09%, title_band
15.31/0.35% to 12.86/0.00%. Opposite directions, which is a phase change rather
than a regression, and the cause is mine -- adding --leaf-time=0 to
verify-capture's render sites pinned the sweeps while the captures froze them
wherever the shutter caught them.
That makes the capture-phase term concrete: I documented +/-5.56 for title from a
sweep, and here it moved two published rows from a one-line harness change. It also
touches a number I published -- the boot-end-frame 0.00% was measured before the
pin, and the equivalent row now reads 0.09%. Both inside the term, and the right
reading is that neither is 'the' number.
Also narrowed the withdrawal-time hook. Its regex matched headings ABOUT
corrections rather than headings making them, so 33 was a measurement of the
regex; narrowed to a leading WITHDRAWN/CORRECTION/Refuted, it gives 10, all
genuine retractions.
Residual limit named: several of the ten are flagged because the registered phrase
does not appear in that section -- the corrected JP heading reads 'does NOT go
against the port', which does not contain 'goes against the port'. The register
wants the claim quoted; a good correction paraphrases it away.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
653e317197