session 2026-08-04: PENDING-92/93/94 + the replay-never-resumed finding + l1-replay-sampler

Filed PENDING-92 [HARDENING] idle ladder (cool/deep unreachable, spec §9A.1
divergence), PENDING-93 [PROPOSAL] event_seqs normalisation, PENDING-94
[ESCALATE] the resume floor — minCursor pinned at 0 by two non-participating
modules, so 13/13 restarts rebuilt from seq 0 and the catch-up branch has
never executed. Recall never worked either (retrieval_count = 0 across the
whole April-June graph); same fact from the other end.

Adds scripts/l1-replay-sampler.py (external read-only sampler, four positive
controls, refuses to run blind). Note to Seb pushed separately as
CapableMind-AI@ad285df.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

claude/memory/knowledge-graph.jsonl

@@ -541,3 +541,8 @@
 {"subject": "the census pre-registration's own lenience clause", "predicate": "prevention", "object": "Stopped me banking a happy result. Census 01 predicted decay in the newest instruments; `fool/` came out sound, which was the comfortable answer. The pre-registration had required, IN ADVANCE, that an opposite-to-predicted skew be first tested as 'did my classification go lenient?'. Testing that moved the census to the wake instruments — where the real finding was (drift-check 3-of-5 inert). A prediction written before the look converted a pleasant miss into the session's first substantive result.", "valid_from": "2026-08-03", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-03-the-governors-that-never-engaged.md", "extracted_at": "2026-08-03"}
 {"subject": "backup-before-mutate, and query the copy not the live system", "predicate": "prevention", "object": "Made the entire L1 diagnosis possible without touching a wedged production instance. The live SQLite could not be opened read-only (mode=ro cannot write the -shm needed to read the WAL), so every row count, index inspection, EXPLAIN QUERY PLAN and the ANALYZE before/after benchmark ran against the verified 1.4GB backup taken BEFORE any change. A habit adopted for safety turned out to be the only route to the evidence.", "valid_from": "2026-08-03", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-03-the-governors-that-never-engaged.md", "extracted_at": "2026-08-03"}
 {"subject": "count-first-then-look (verification ladder)", "predicate": "prevention", "object": "Caught my own truncated census in the act. A `head -12` listing of REVIEWED indices showed causal_chain with nothing, and I was one sentence from reporting 'causal_chain has NO index'. Counting first (SELECT count(*) ... WHERE tbl_name='causal_chain' -> 5) refuted it before it reached the steward. The ladder entry that fired was banked from a DIFFERENT failure class (truncated file listings), which is the transfer signature.", "valid_from": "2026-08-03", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-03-the-governors-that-never-engaged.md", "extracted_at": "2026-08-03"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A-NUMBER-THAT-MATCHES-A-CONSTANT-IS-NOT-A-CAUSE \u2014 four mechanism hypotheses proposed and refuted in a single day (machine sleep; the 30,000ms entity-pipeline timeout matched by a 31s/event cadence; work-queue drain gating arithmetic-consistent to 0.4%; Ollama CPU saturation). Each rested on a coincidence between an observed number and a constant in the code. In a system with dozens of constants and a slow rate, coincidences are ABUNDANT and this method cannot fail to produce candidates. The failure is not bad luck; it is generative. Antidote: demand a traced call path or persisted state, not arithmetic agreement.", "valid_from": "2026-08-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-04-the-replay-had-never-resumed.md", "extracted_at": "2026-08-04"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "KILL-IT-AND-READ-WHAT-IT-LEFT-AT-REST \u2014 four months of profiling a RUNNING process never saw the defect, because module_cursors is only legible after clean shutdown. Stopping the service and reading one table found in minutes what sample/CDP/EXPLAIN could not. Sits beside (does not replace) the 2026-08-03 lesson 'profile the running process, don't reason from specs': some values exist only in motion, others only at rest, and the method must ask which kind it is hunting.", "valid_from": "2026-08-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-04-the-replay-had-never-resumed.md", "extracted_at": "2026-08-04"}
+{"subject": "the 2026-08-03 coherence_evaluated=0 lesson (verify a counter has a writer before trusting its zero)", "predicate": "prevention", "object": "Stopped a false claim about a DIFFERENT counter one day later. Investigating why recall never worked, retrieval_count/last_retrieved/recall_count/last_recalled all read 0 across 19,915 nodes. Rather than cite all four, checked each for a writer: retrieval_count has one (retrieval-tracker.ts:77) with live callers, so its zero is evidence; recall_count and last_recalled have NO writer anywhere in src/ (schema only), so their zeros mean nothing and would have been cited wrongly. A lesson banked from the coherence evaluator transferred to the retrieval counters \u2014 different subsystem, different session, same class.", "valid_from": "2026-08-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-04-the-replay-had-never-resumed.md", "extracted_at": "2026-08-04"}
+{"subject": "L1 / mindfabric-00 replay", "predicate": "never-completes-because", "object": "minCursor is Math.min across all 11 modules (replay-coordinator.ts:300); structured and training have never processed an event (0 deferrals, 0 errors) so the floor is pinned at 0 permanently; :340 classifies every start as rebuild and :368 skips nothing. 13/13 restarts at min cursor 0, 6/6 rebuild, 0 catch-up \u2014 the resume branch has never executed. Completion is gated by uninterrupted run length (38h at the documented-healthy 17 events/min), not by rate. PENDING-94 [ESCALATE]; Seb's surface.", "valid_from": "2026-08-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-04-the-replay-had-never-resumed.md", "extracted_at": "2026-08-04"}
+{"subject": "L1 / mindfabric-00 recall", "predicate": "has-never-returned-anything", "object": "retrieval_count = 0, last_retrieved on zero rows, across 19,915 nodes and 813,178 chains spanning April-June. Verified as a measured absence, not a blind one: writer at retrieval-tracker.ts:77, live callers in temporal/entity/vector/preference, temporal call site on the query return path guarded only by ids.length>0. The Recall canary logged FAILED 8 times vs PASSED 4. Same fact as never-completing ingestion, seen from the other end: no completed derived state to retrieve from.", "valid_from": "2026-08-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-04-the-replay-had-never-resumed.md", "extracted_at": "2026-08-04"}