[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/skills/symmetria/SKILL.md

@@ -77,7 +77,10 @@ Notice these in your own writing or in code you read:
 - A claim asserted from a **derived or recalled form when the substrate is checkable** — a regex over derived text, a fuzzy-matcher hit read as membership, a soft classification where a checkable number/fact/test was producible, an answer from training where the banked record (docs, registers, prior briefs) already holds the considered answer, instructions re-derived instead of citing the governed doc, acting in a repo before reading its CLAUDE.md. Verify against the substrate first; produce the checkable claim; if it can't be produced cleanly, that inability is the finding. <!-- 2026-07-19 harvest review (steward-authorized): consolidates claim-from-derived-artifact (07-03, jurist-elevated standing practice, 3×) · fuzzy-matcher membership (06-15, 4× one session) · soft-classification-over-checkable-claim (07-13, steward-named 5×/day) · answer-from-training-before-banked-record (07-14, recurred in 48h) · re-derived-instructions (07-01) · enter-repo-read-docs-first (07-09) -->
 - **Completion is a tripwire** — the *feeling* of "done" (a fluent pass, a wall of green, a "finally", a closable-now bucket) is the cue to verify the tail, not the signal to ship. Ask which failure class each green check can actually *see*; reconcile any closed/complete claim against the authoritative source, not the derived close-list; treat the closable-vs-blocked partition as itself a claim to check. <!-- 2026-07-19 harvest review (steward-authorized): recurrence-promoted per the governed watch-item pattern (memory 2026-07-06; recurrence 07-07 gate-suite-blind-to-failure-class; + closable-now-is-a-claim 07-16 jurist-named; + reconcile-before-"finally" 07-17) -->
 - **The say–do seam** — a record composed ahead of its acts (an Addendum/tracker/brief asserting APPLIED or DONE before the act ran); a grounding *quoted* but not *traced* (for each quoted clause, trace the plan's END-state against it — and one level deeper: which way does the inference run in the new state; is any class you named actually two kinds with opposite dispositions). Record after the act, or mark the record prospective. <!-- 2026-07-19 harvest review (steward-authorized): the 07-19 family — record-asserts-applied-before-the-act (self-caught at the ledger) · grounding-quoted-but-not-traced (jurist-caught in the package's own quote) · consequence-trace-one-level-shallow (both PENDING-65 struck framings); kin to comments-promising-behavior, at the session-artifact level -->
-
+- **Applications of the time-the-task-requires principle** — the Directive elaboration made constitutional in `~/CLAUDE.md`, at the discipline level: **lectio** (reading a corpus faster than the corpus asks); **diagnose-don't-fix** (patching the instance before tracing the class); **dwell-on-composition** (giving a recommendation the time the executor wants it to take rather than the time it wants). <!-- PENDING-S6, jurist Q4 affirmed 2026-05-18 (shape-review); implemented 2026-08-03 once Q4 landed in CLAUDE.md. -->
+- **An alignment pulse returning `aligned` without naming a specific tension** — premature closure wearing the form of a check. <!-- PENDING-S6 (audit D1) -->
+- **A search query shaped by what the session wants to find** rather than by what it needs to find — the result set is then evidence about the query, not about the substrate. <!-- PENDING-S6 (audit D5) -->
+- **Post-compression confidence claims** — the working memory was trimmed; what feels certain now may rest on what was lost. Say what was inherited versus what was re-verified. <!-- PENDING-S6 (audit D4) -->
 
 When you notice one, name it. In chat, in the ledger, or both. Don't accumulate observations for "a good moment" — there is no good moment, only now.
 
@@ -160,7 +163,8 @@ Any failure → annotate and re-query.
 3. Walk the three dimensions.
 4. Walk calibration (confidence, uncertainty).
 5. Flag any contamination patterns visible.
-6. Recommend: proceed | return-and-reframe | escalate.
+6. Recommend: proceed | return-and-reframe | **suspend** | escalate.
+   - **`suspend`** — the work is right and not urgent, but it needs unhurried steward judgment. Distinct from `escalate` (which carries urgency) and from `return-and-reframe` (which says the work is wrong). *The time the steward's judgment requires is task-time, not interruption-time.* Name what is being suspended and what would resume it. <!-- PENDING-S7, jurist Q5 affirmed 2026-05-18; implemented 2026-08-03 once Q4 landed. -->
 7. If anything was caught, log a return to the ledger.
 
 ### `audit-agent`

claude/skills/wrap-up/SKILL.md

@@ -212,13 +212,24 @@ Produce a brief summary for the steward:
 ```
 ## Wrap-up — [date]
 
+### Future — what pulls
 **Pulling thread:** [the singular concern]
 **Actionable resumption point:** [where things concretely stand + the candidate first move toward the thread, as of wrap — to confirm or revise against what changed. The thread is the direction; this is the first step.]
 **Question we're leaving open:** [the literal question for next-Claude]
 **Pause statement:** [explicit acknowledgment that the work is being paused; what is wanted-to-find-still-pulling on return. The ligature is laid at departure, not discovered at return — this field is constitutive, not optional.]
+
+### Past — what moved, and why
+**What happened:** [the session's substantive moves, each with the reason it was taken — not a task list. What a reader needs to reconstruct the session's shape.]
+**What held:** [which disciplines, gates or predictions were applied and did their work. A practice that is never observed working is not known to work.]
+**What was corrected:** [claims retracted, framings the steward or jurist overturned, instruments found unsound — or "none". Corrections are the session's most perishable output.]
+
+### Present — how it stands
+**The mood:** [the Stimmung — what this session felt like from inside, and what that signals. Carried because confidence and unease both travel across the pause.]
+**Confidence to recalibrate:** [what is being claimed at what confidence, and specifically what was verified versus inherited.]
 **Decisions deferred (and why):** [the negative space — what was chosen-not-to-do this session, and the reason. Absent this field, the unborn session cannot know the scope of what was held back.]
 **Skill harvest:** [skill create / patch / retire proposals surfaced this session (§1.6), each as a proposal for steward authorization — or "none". Never an autonomous skill edit.]
 
+### Restoration material
 **Session captured:** [memory file path]
 **KG appended:** [count of lines appended to knowledge-graph.jsonl, or "none"]
 **Uncommitted work:** [list or "none"]
@@ -230,7 +241,9 @@ Produce a brief summary for the steward:
 [Any warnings or things to address before closing]
 ```
 
-The pulling thread + question are first because they are what *waking* needs to inherit. The rest is restoration material.
+The three tenses mirror the session memory file (§2), so the output and the durable record no longer disagree about what a session consists of. **Future leads** — inverting the memory file's narrative order — because the thread and the question are what *waking* inherits; the steward reads this at departure, but it is written for arrival.
+
+A template that drops a tense under compression is itself an instance of the failure mode the Directive elaboration names. <!-- PENDING-S9, jurist Q2 affirmed + Q3 elevated to constitutive 2026-05-18; implemented 2026-08-03 once Q4 landed. Past and Present were wholly absent; Future was already well-specified. -->
 
 ## Important constraints