Sections 1 to 4 MEASURED on build-5 and build-6 (22:35 to 23:15 UK) under the lease pool and pid watchers, the harness tools/finality-attacks/v4.mjs (the v3.mjs shape with three islands, an equivocating key, a leaving voter, a strip, a kept-datadir restart, a fresh node at the heal, the carried-certificate capture; lib/net.mjs gained the per-node EVM RPC port for the lock kind) and tools/finality-attacks/verifier-row.mjs (the shared Sepolia verifier and the same contract on anvil with the harness table). 1a PASS (every island pauses); 1b PASS on runs 2 and 3 (exactly the island above half of the anchored table recovers after a full window, the others pause and join its chain; run 1 drew the island under half by Poisson jitter and paused as the rule says); 1c the measured conflict of 6.5 (two recovery certificates, the anchored history untouched) with the plan's FAIL line hit: a recovery certificate reads lockKind "final" on every node that did not form it (finding 1, node change owed), and a node holding two certificates reports active and keeps locking (finding 2, 3.11.4); 1d PASS (pause only, the equivocator stripped at the heal); 2 PASS (the fresh node holds every pre-heal lock by carried certificates, the restarted node agrees, the pause ends within two intervals of the reconnect, four epoch boundaries inside the pause); 3a to 3d PASS on the node facts; 4 PASS (a recovery certificate fails closed on both verifiers). Section 6: the enforced lane's harness needs its cache-history-node pair (c591e63b) and the 0x51cd pin; runs 1 and 2 recorded with their cause, run 3 follows. Batch fin-native-20261008T2300Z recorded (FIN-02, FIN-07 PASS on node:finality-realnode; FIN-08 RUNNING).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
96a558ebcc