re: the refuted register ignored the deaths I just wrote, and two false positives shared a cause

Three refutations written as prose under ### headings never entered the register:
check_refuted.py parses * "claim" lines, so the count stayed at 188. Registered
them properly (188 -> 192). A register that parses one syntax silently ignores
every other, and it is invisible from the author's side -- ask the register what it
holds, do not re-read what you wrote.

Both standing false positives were bullets under a header that retracts the whole
list, with no marker in the +-4-line window: scope marks them, not proximity. The
scan now includes the nearest preceding header and matches markers
case-insensitively ('An earlier version' was missed by the marker 'an earlier
version'). Controlled by planting a real revival and confirming it is still caught;
register now runs clean at 0.

Also records sylpheed-port's diagnosis of the phase-lock fallout: a number can be
inapplicable rather than wrong, and a tension built on one is manufactured. Plus
their point that some claims are not registrable in a substring register at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v

docs/re/REFUTED.md

@@ -718,6 +718,9 @@ reachable by the person about to repeat it.
 
 ### The JP title might not draw the sweep leaves at rest — ❌ REFUTED (2026-08-30, mine)
 
+* ~~"the JP title does not draw the sweep leaves at rest"~~ — refuted, see below.
+* ~~"build 7's denser logo stack occludes the sweep leaves"~~ — refuted, see below.
+
 I hypothesised that build 7's denser logo stack (katakana + crystalline burst)
 **occludes** the two sweep leaves, to explain why two JP title captures differ by
 RMSE 0.32 inside the adjudication box while two EN captures a plateau-phase apart
@@ -730,6 +733,9 @@ The 0.32 had a different cause: **my own gate**. See below.
 
 ### "Two sessions sample a free-running clock" — ❌ REFUTED (2026-08-30, mine)
 
+* ~~"a free-running clock lands somewhere else on a fresh boot"~~ — refuted, the gate phase-locks it.
+* ~~"the in-box capture noise of 0.32 between sessions"~~ — refuted as a noise floor; it measures the trigger.
+
 `jp-title-at-rest.txt` justified a second capture as probing the between-run axis
 "where a free-running clock lands somewhere else on a fresh boot", and reported
 its in-box **0.32 as capture noise**. Measured at the shutter instant, the sweep