igneum-labs 4e1eae54e1 The 2.0.3 reruns of rows 1b and 1c on the fixed node (finality-2.0.3-kind-and-conflict c8d22a85, 9 October 2026, 01:27 to 01:45 UK): the lock kind reads recovery on every node, two valid certificates at one index pause finality with reason conflict and no new lock above it; rows, files and the registry batch ... Three runs on real nodes (igneumd a37f4b63 built from c8d22a85's code, build-5 and build-6, lease pool, pid watchers, zero restarts): 1b with e at 0.20 (A recovered at index 10 at 55.46 percent; that certificate reads lockKind recovery on A's, B's and C's nodes; 0 conflicts, 0 disagreement, all three at 24), 1b with e at 0.30 (the same at index 11, all three at 27), 1c (A and B recovered at index 11, two recovery certificates; after the heal both holders read "conflict: two valid certificates at index 11", finalityActive false, no lock installed above it; C followed A's chain, B's never reached it). Finding 1 and finding 2 of the native runs closed on the node. Batch fin-203-20261009T0127Z recorded (FIN-02, FIN-07 PASS on node:finality-realnode, manifest c8d22a85). Harness: v4.mjs records finalityActive per node; run-row.sh takes PAIR. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-10-09 00:47:43 +00:00
..
native-2026-10-09	The 2.0.3 reruns of rows 1b and 1c on the fixed node (finality-2.0.3-kind-and-conflict c8d22a85, 9 October 2026, 01:27 to 01:45 UK): the lock kind reads recovery on every node, two valid certificates at one index pause finality with reason conflict and no new lock above it; rows, files and the registry batch	2026-10-09 00:47:43 +00:00
v3-known-failed.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-pause-fix.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-pause.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-recovery-fix.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-recovery-split70-fix.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-recovery-split70.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00
v4-recovery.md	Rule v4 harness, the reruns on the fixed node (12424341, HEAL 400): the pause-only run resumes after the heal (the node fault closed), the recovery run locks exactly the side above half (54.62 percent this time; 51.26 the other way in the first run), split70 as before; the seven result files in sim/finality-attacks-results/	2026-10-08 19:26:24 +00:00