[FIX] L1 pin root-caused and cleared; S-series closed; instrument census

mindfabric-00 had been event-loop-pinned for 6+ days (100% CPU, /health silent).
Profile + CDP inspector named two hot paths, both from runTemporalPipeline:

  checkForCycle -> getCausalEdgesFromSqlite   99.8% of samples
  tryExtendChains -> getChainsContainingSeq   now dominant (json_each scan)

Cause of the first: ANALYZE had never been run, so SQLite preferred a boolean
index (idx_caused_tombstoned, matching ~all 836k edges) over idx_caused_from.
ANALYZE across 15 module DBs flipped the plan; 6.4x on a microbenchmark and
99.8% -> 6.0% in the live profile. /health went from silent to 200 in 0.13s.

B1.1's fan-out cap is IMPLEMENTED AND WORKING (today: max in-degree exactly 20,
zero violations; pre-23-June: max 629, avg 67.6). The defect is data, not code —
836k edges / 813k chains minted under ungoverned fan-out before the fix landed.
Repair run: derived stores wiped, logchain preserved, replay in flight.

S-series closed (jurist had already ruled all of Q1-Q5 on 2026-05-18):
  S6/S7/S9 implemented (Symmetria §3 flags, `suspend` outcome, wrap-up §8 tenses)
  S2 rebuilt as [FIX] — wake-digest unwrapped-session detector, discrimination-
    gated on real sessions (11 wrapped / 2 unwrapped)
  S4/S5 withdrawn with MemPalace (steward ruling)
Dormant legacy dispositioned: PENDING-4/5/11/12, CD-03, ICP-19 duplicate.
Open authorization items 22 -> 10.

Census 01: which instruments have no real negative instance. Finding — the
governance drift-check has 3 of 5 families inert against the current CLAUDE.md,
and 71 of 75 verification-ladder entries are cited nowhere outside the ladder.

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

claude/governance/fool/census-01-negative-instances-PREREGISTRATION.md

@@ -0,0 +1,68 @@
+# Census 01 — Which instruments have no real negative instance?
+
+**Pre-registered:** 2026-08-03, before reading any instrument source or the verification ladder.
+**Origin:** the literal question left by the 2026-08-02 evening wrap.
+
+---
+
+## The question
+
+Five times on 2026-08-02, a passing check certified a property of the *code* while
+claiming a property of the *result*. The discrimination gate (`e9f3544`) is the mechanical
+answer **for checks that have a real negative instance to test against**.
+
+So: **which of our current instruments have no real negative instance available, and is
+that absence recorded anywhere, or does it look like coverage?**
+
+## Unit of census
+
+An **instrument** = any check, gate, guard, or test suite whose verdict is used to license
+a claim. Two populations, both censused entire (no sampling, no `| head`):
+
+1. Everything in `~/dotfiles/claude/governance/fool/` that returns a verdict.
+2. Every named entry in `reference-verification-ladder.md`.
+
+## The test applied to each
+
+**Was this instrument demonstrated returning its FAIL verdict on a REAL artifact** — one
+drawn from actual work, not authored so the test would exercise the branch?
+
+Three outcomes:
+
+- **DEMONSTRATED** — names the real artifact it was shown failing on.
+- **ABSENT-RECORDED** — no real negative instance, and the instrument or its record says so.
+- **ABSENT-UNRECORDED** — no real negative instance, and nothing says so. **This is the finding**: absence that reads as coverage.
+
+Synthetic fixtures do not count as negative instances. That is the whole point of the
+discrimination gate: fixtures derived from the check inherit the check's blind spot.
+
+## Predictions (recorded before the read)
+
+1. **The discrimination gate itself → DEMONSTRATED.** It was built and shown rejecting the
+   §3.3 pattern as it actually shipped, on two real artifacts.
+2. **`test_reduce.py` and `test_twin.py` → ABSENT-UNRECORDED.** Expectation is that they
+   are fixture-based and say nothing about it.
+3. **The trial-03 degraded guard → ABSENT, now RECORDED.** It had no negative instance
+   until trial 03 supplied one by failing; the record exists because the failure did.
+4. **Verification-ladder entries → mixed, skewed DEMONSTRATED.** Ladder entries were earned
+   from real failures, so most should name the artifact. If they do *not* name it — if the
+   entry states the rule but drops the instance — that is the same concealment shape as
+   yesterday's, at the level of the record rather than the document.
+5. **Overall skew → ABSENT-UNRECORDED dominant.** Prior: this is the pattern that surfaced
+   five times in one session.
+
+## The census's own discrimination condition
+
+This census is an instrument. Its negative instance is an instrument that genuinely *does*
+have a real negative instance, correctly classified DEMONSTRATED, standing beside one that
+does not, classified ABSENT.
+
+**If every instrument lands in one bucket, the census has discriminated nothing** and must
+be reported as such rather than as a result. If the skew comes out opposite to prediction 5
+— mostly DEMONSTRATED — the first hypothesis to test is that my classification went lenient,
+not that the instruments are sound.
+
+## Stopping rule
+
+The census is complete when both populations are enumerated entire and every member is
+classified. Unclassifiable members are reported as unclassifiable, not dropped.