session 2026-09-01 ADDENDUM 2: trim committed; agents-untracked carried forward

The chamber-library CLAUDE.md trim is committed and pushed (c7c30ac,
54,129 -> 22,530 chars, both remotes current), so the one intentionally
dirty file from ADDENDUM 1 is now closed.

Carried to the next session on the steward's direction, and deliberately
NOT filed as a PENDING item — the moratorium to 2026-09-15 is undecided
and the instruction was "attend to it", which is scheduling rather than
filing:

  ~/.claude/agents is not under version control. 51 hand-edited files, 0
  tracked, not a symlink into dotfiles. Every other governed surface in
  this system is tracked, and this one holds EXECUTABLE CONFIGURATION —
  an agent definition determines what a delegated sub-agent is told to do
  — so an untracked, unattributable edit there is a governance surface
  rather than a convenience. It was found by accident while /doctor was
  looking for name collisions, and no instrument was positioned to notice
  it. The 15 renames still have no history, so ADDENDUM 1's mapping table
  remains the only undo; track the directory before anything else edits
  it. Open questions recorded, none answered.

Also logged: a fourteenth instrument error, and this one broke a
discipline the repository documents. I reported "chamber-library pushed"
having pushed only origin; the github mirror was 9 commits behind and
stayed behind through the whole wrap while the record said clean. The
repo's own CLAUDE.md says push to both. Caught by verifying a push whose
&& echo had not fired, not by any control.

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

claude/memory/MEMORY.md

@@ -79,8 +79,9 @@ permalink: claude-memory/memory
 > ⚠ **`RE_ID` CANNOT PARSE THE REGISTER'S OWN HOUSE FORM.** `## REVIEWED-133 (PENDING-137) — …` backtracks to the bare token `REVIEWED`; entries **130–133** are invisible to the integrity control and any future amendment to them reports a **FALSE ORPHAN**. **Fix the REGEX, not the entries — REVIEWED-132's own disposition says "Do not touch placed headers."** Bounded `[FIX]`, ~20 min. *Steward raised it; agreed at the wrap.*
 > 📌 **STEWARD OWES:** the **moratorium decision** · rule **PENDING-171** (unblocks the 322 unread of 362) · **-177** (now with measured evidence; Tier-3 not Tier-2) · **-178** · -160 · -168 · the §5 regrade ruling.
 
-> ⚠ **AFTER THE WRAP — `/doctor` ran, and TWO THINGS ARE UNCOMMITTED/UNTRACKED. Read ADDENDUM 1 of the session file before touching either repo.** (1) **`~/_Dev/chamber-library/CLAUDE.md` carries an UNCOMMITTED 31,861-char deletion** — a steward-approved trim, 54,129→22,530 chars, now under the warning threshold; the doctor protocol forbids the executor committing CLAUDE.md edits, so it awaits the steward. ⚠ `git diff --stat` says *11 lines* and badly understates it — use `--word-diff`. (2) **`~/.claude/agents` IS NOT GIT-TRACKED AT ALL** (51 hand-edited files, 0 tracked, not a symlink) — 8 name collisions were fixed by renaming 15 files, and **the rename mapping in ADDENDUM 1 is the only undo that survives a clear.** ⚠ The wider gap — a governed surface with no version control — is noticed, unfiled, and real.
+> ✅ **AFTER THE WRAP — `/doctor` ran; the chamber-library trim is COMMITTED (`c7c30ac`, 54,129→22,530 chars, both remotes current).** Also fixed: **8 sub-agent name collisions** across 21 files — 15 renamed, 0 remain, and the harness surfaced 15 previously-invisible agents on the spot · 4 invalid `SKILL.md` frontmatters (latent, not live) · `plane` MCP disabled (0 calls / 41 sessions) · `permissions.defaultMode: auto`. **PENDING-169 §5a** (`440d18e`): `tarbuckle-wrap.py` = the `Stop` hook at **median 6.7 s / max 13.6 s**, an order of magnitude above every other hook, on the blocking path at every session end — filed against the **existing** 2026-09-08 trigger, no duplicate block. **Steward: 8 September, with the rest of Tarbuckle.**
-> ✅ Also fixed: 4 invalid `SKILL.md` frontmatters (latent, not live — the harness parses leniently), `plane` MCP disabled (0 calls / 41 sessions), `permissions.defaultMode: auto` set. **PENDING-169 §5a filed** (`440d18e`): `tarbuckle-wrap.py` = the `Stop` hook at **median 6.7 s / max 13.6 s**, an order of magnitude above every other hook, on the blocking path at every session end — filed against the **existing** 2026-09-08 trigger, no duplicate block. **Steward: look at it on 8 September with the rest of Tarbuckle.**
+> 📌 **NEXT SESSION, STEWARD-DIRECTED — `~/.claude/agents` IS NOT UNDER VERSION CONTROL.** 51 hand-edited files, **0 tracked**, not a symlink into `dotfiles`. **Every other governed surface is tracked**; this one holds *executable configuration* — an agent definition determines what a delegated sub-agent is told to do — so an untracked, unattributable edit there is a governance surface, not a convenience. ⚠ **Found by accident** (`/doctor` was looking for name collisions), and **no instrument was positioned to notice it**. NOT filed — the moratorium is undecided and the instruction was *attend to it*, not *file it*. ⚠ **The 15 renames still have no history — ADDENDUM 1's mapping table is the only undo.** Track the directory BEFORE anything else edits it. Open: dotfiles or its own repo · are all 51 the steward's or some vendored · does `~/.claude/skills` (already symlinked into dotfiles) set the precedent.
+> ⚠ **14th instrument error, and it broke a discipline the repo documents:** I reported *"chamber-library pushed ✓"* having pushed only `origin` — **`github` was 9 behind** and stayed behind through the whole wrap while the record said clean. The repo's `CLAUDE.md` says *"push to **both**"*. Both current now.
 
 - [Session 2026-09-01 — the gate that should have existed](session-2026-09-01-the-gate-that-should-have-existed.md) — a day that *became* the thing it diagnosed. Wake found control (c)'s false positive (a Tarbuckle mumble is unattended **by design**) → PENDING-178, the counter's **unit**. FIX-lane check-in held: **EXTENDED PROVISIONAL, n=1**, trigger re-based to use, ⚠ half not machine-checkable and **no proxy invented**. REVIEWED-133 (PENDING-137) ruled + executed — **two of its conditions corrected by executor substrate reads**, and ⚠ `governance-mcp.py --selftest` was **FAILING while the jurist ruled from it** (fixed, 62 controls). **NEXT: the fr cell's last two steps.**
 

claude/memory/session-2026-09-01-the-gate-that-should-have-existed.md

@@ -265,3 +265,49 @@ urgent — but it is the kind of gap this apparatus exists to notice, and it was
 the same output block: `dotfiles` has remotes `gitea` and `github` and **no `origin` at all**; the
 `origin/main [ahead 1]` belonged to `studium-engine`. Same family as the day's other twelve —
 acting on a handle without checking its referent. Caught by verifying rather than by any control.
+
+---
+
+## ADDENDUM 2 — the trim landed; two items carried to the next session
+
+**`chamber-library` CLAUDE.md trim COMMITTED and pushed** — `c7c30ac`, steward-directed.
+54,129 → 22,530 chars. Both remotes current.
+
+⚠ **Fourteenth instrument error, and it violated a discipline the repo documents.** My earlier
+loose-ends sweep ran `git push -q origin main` and reported **"chamber-library pushed ✓"**. True
+of `origin`; false of the mirror. **`github` was 9 commits behind** and stayed behind through the
+whole wrap, while the record said the repo was clean and pushed. The repo's own `CLAUDE.md` says
+it plainly — *"Commit locally; push to **both** (`git push github && git push origin`)"* — so this
+is not a gap in the record, it is a documented discipline I did not follow and then reported
+success on. **The say–do seam, at the smallest possible scale.** Caught by verifying a push whose
+`&& echo` had not fired, rather than by any control.
+
+### ⚠ CARRIED TO THE NEXT SESSION — steward-directed 2026-09-02
+
+**`~/.claude/agents` IS NOT UNDER VERSION CONTROL.** 51 hand-edited files, **0 tracked**, not a
+symlink into `dotfiles`. Established 2026-09-02 while fixing 8 name collisions across 21 of them.
+
+**Why it matters beyond the inconvenience.** Every other governed surface in this system is
+git-tracked — `PENDING.md`, `REVIEWED.md`, the memory files, the skills, the scripts, the corpus.
+The agents directory is the one place where hand edits leave **no history, no diff, and no
+attribution**, in a system whose entire premise is that the record must be checkable. It is also
+**executable configuration**: an agent definition determines what a delegated sub-agent is told to
+do, which makes an untracked, unattributable edit there a governance surface, not a convenience
+one.
+
+⚠ **It was found by accident** — `/doctor` was looking for name collisions, not for missing version
+control, and nothing in the apparatus was positioned to notice. That is the part worth keeping:
+the gap is old, the finding is incidental, and no instrument would have surfaced it.
+
+**Deliberately NOT filed as a PENDING item.** The moratorium to 2026-09-15 is proposed and
+undecided, and the steward's instruction was *attend to it next session*, which is scheduling
+rather than filing. Whether it earns an item is itself a next-session decision.
+
+**Open questions for that session, none answered here:** does the directory belong in `dotfiles`
+(where the other governed surfaces live) or in its own repo · are all 51 files the steward's, or
+are some vendored from a plugin/marketplace and therefore not his to track · does tracking them
+change how they load · and is `~/.claude/skills`, which *is* symlinked into `dotfiles`, the
+precedent to follow.
+
+⚠ **The 15 renames still have no version history**, so ADDENDUM 1's mapping table remains the only
+undo. Whatever is decided, tracking the directory should happen **before** anything else edits it.