[FIX] MEMORY.md load-integrity breach: relocate workstream state to its trackers

The wake reported MEMORY.md at 26,803 bytes against a 24,986-byte budget, so the
index was being silently truncated at load — the failure the two-file split exists
to prevent, on the one file every session reads first.

The cause was not bulk. It was an inversion the file's own Index discipline section
forbids: "Canonical Trackers as one-line pointers — chronological detail lives in
the linked tracker files, not here." Five tracker entries had grown into paragraphs,
and for three of them the index had become the SOLE custodian of live state:

  - Studium Engine: the tracker's chronological log stopped at 2026-08-13 while the
    index carried engine state through 2026-09-01 (REVIEWED-133, 496cd7e, the
    deleted undisclosed_days_in_force). Relocated verbatim as a dated log entry.
  - The Fool (Tarbuckle): the only linked target was a SEALED seed, which is not a
    place state may be appended, so there was nowhere for it to go. Tracker
    established (project-fool-tarbuckle.md); index line relocated verbatim.
  - L1 reliability: the tracker records that replay is "not resumable" but neither
    the mechanism (minCursor is a minimum over 11 modules, two never participate, so
    it is pinned at 0 by construction) nor the completion criterion (uninterrupted
    run length, not rate). Both appended.

Cut only where the file's own rule says to cut. "Rules that fire silently" was left
untouched by design — those entries keep their rule inline precisely because I would
not know to look them up, and gutting them is the one cut that would do real harm.
The frozen verification-ladder pointer (REVIEWED-123) and the skill-harvest hold
(PENDING-141) were likewise not touched.

Lossless-relocation gate applied: line-range slices, never retyping; md5 per slice;
token-conservation check over all five originals against the trimmed index and the
relocation targets — 0 unconserved after the L1 append. Link canary: 406 pointers,
0 dead, 0 mis-authored; 32 wikilinks clean.

26,803 -> 23,714 bytes. Headroom is only 1.3 KB; the Active Session block still
carries ~5.5 KB that the wrap rotates.

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

claude/memory/project-studium-engine.md

@@ -121,6 +121,16 @@ both still **needing dates, not "later."**
 
 ## Chronological log
 
+### 2026-09-03 — state relocated from the MEMORY.md index at the load-integrity trim
+
+⚠ **Provenance: this entry is the verbatim MEMORY.md index line**, moved here because the index
+had become this workstream's sole custodian — the log below stopped at 2026-08-13 while the index
+carried engine state through 2026-09-01, and MEMORY.md was over its load budget and being
+silently truncated at wake. Relocated, not rewritten; the pointer in the index is now one line.
+
+- [Studium Engine](project-studium-engine.md) — canonical engine tracker. **N0–N2 + R0 + `voice_stamp` built**; corpus **14 sources, trilingual**, fleet **9 suites / 285 green**. **fr cell: TWO STEPS FROM CLOSING.** **REVIEWED-133 (PENDING-137) RULED + EXECUTED 2026-09-01** (`2b30425`, `496cd7e`) — the cell-constant narrowing is now a *placed amendment*: `fr.stratum_amendments` carries **REVIEWED-121 and REVIEWED-133 as siblings** (what cond. 4 turned on). `undisclosed_days_in_force` **deleted, not corrected**; `direction` recorded as **INFERENCE, never measurement** — ⚠ *the narrowing removed the markers the claim turns on, so the before-state is unrecoverable from the file that carries the disclosure.* **NEXT: PENDING-134's disclosure** (⚠ what it now requires is **NOT obvious** — read REVIEWED-133's `If AUTHORIZED` **with** REVIEWED-121 point 9 before touching the file; deliberately not guessed at the wrap), **then `ratio_A_to_B` re-derived ONCE** (REVIEWED-116 pt 5). ⚠ **PENDING-134 was ruled REVIEWED-121 on 2026-08-14** — this line said "NEXT: rule PENDING-134" for 18 days and aimed the steward at the wrong target. ⚠ **PENDING-131 (c) never bound the engine** (`chunker.py` has `char_range` since Cluster A).
+
+
 ### 2026-08-13 — the fence was never blocked; the fr cell all but closed
 
 **REVIEWED-118 EXECUTED** (`e51e30d`) — authorized 2026-08-10, unexecuted for three days, found by