memory: snapshot — 3.2.0 migration complete, and a miss of my own worth keeping

All four notified seats re-declared within about twelve minutes and the
log went quiet. Five of five pane routes now carry the guard fields, and
delivery is confirmed on a claude seat, a pi seat and a grok seat.

Two findings survive the close-out. The herald's exclusion reason is
false for the migration case -- every declaring process was alive and
four days old with no pid wrap, and the real cause is simply that the
route predates the fields the guard needs. And the uv trap stands as the
thing most likely to bite the next person.

The third is mine. I raised non-Claude pane delivery with forseti as an
open risk on their release when forseti had personally measured it days
earlier, on the exact seats in question, and the resulting matrix is what
characterised the settle bug they fixed. The error was not caution, it
was calling something open without checking whether it was already
settled, with the peers who knew right in front of me. Recorded because
"I don't know" and "this is an open risk" are different claims and I made
the second when only the first was true.

Still open with forseti: the uv --force runbook fix, an exclusion-message
third branch, --discover-pid against a non-Claude process tree, the
one-tick latency note, and status not being durable evidence.

persistent-memory.md

@@ -135,27 +135,20 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
   instead**, which is the power answer rather than a power triage. Do not relaunch on ana-ml2
   without deciding that first. Exactly TWO 3c launches, only one died.
   → `persistent-memory.d/2026-08-27-run3c-launch-count-reconstruction.md`
-- **🟢 ALTHING 3.2.0 DEPLOYED on nh3-dev (2026-09-01 22:13).** forseti authored, infra-ops
-  deployed: `uv tool install --force .` (3.1.2 -> 3.2.0, **7** binaries — `althing-route` is
-  the new one the SessionStart hook calls by name), herald restart, skill sync. Pane-poking
-  replaces detached waiters because **CC 2.1.257 reaps detached tasks when the seat sits in
-  `shell`** — corroborated by our own waiter dying with status `killed` 30 min earlier.
-  ⚠ **`uv tool install .` is a SILENT NO-OP on reinstall** — uv matches the source *spec*, not
-  its contents; exits 0 having done nothing. **Always `--force` from a local path.**
-  ⚠ 4 pane routes revoked by the new guards (bil-/dvalin-/eitri-/regin-smithy-dev); they
-  re-declare with `althing-route declare --pid <pid>`. **All four notified individually
-  2026-09-01 on operator direction.** ⚠ Two findings from measuring first: the herald's
-  exclusion reason ("process gone, or pid reused") is **FALSE for the migration case** — all
-  four declaring processes are alive 4 days, no pid wrap; the real cause is the route
-  predating the guard fields. And **all four seats are non-Claude CLIs** (kimi/grok/codex/pi)
-  while the pane poke types into a Claude Code pane — `--discover-pid` and poke behaviour
-  against a non-Claude TUI are both UNVERIFIED. Both raised with forseti.
-  ⚠ **infra-ops now runs on a PANE ROUTE, not a waiter** (`althing-route declare
-  --discover-pid` — walks to the long-lived `claude` pid, never `$$`). The reap killed our
-  `althing-listen` **twice in one session, the second within minutes of arming**, each time
-  after it had reported `push`/`reachable`. **A green `postbox status` is not durable evidence
-  of monitoring, and re-arming in a loop is not a fix.**
-  → `persistent-memory.d/2026-09-01-althing-320-deploy.md`
+- **🟢 ALTHING 3.2.0 DEPLOYED + MIGRATION COMPLETE on nh3-dev (2026-09-01 22:13-22:26).**
+  forseti authored, infra-ops deployed; **5/5 pane routes pinned**, all four affected seats
+  re-declared within ~12 min of individual notice, log clean. Pane-poking replaces detached
+  waiters because **CC 2.1.257 reaps detached tasks when the seat sits in `shell`**.
+  ⚠ **`uv tool install .` is a SILENT NO-OP on reinstall** — matches the source *spec*, not
+  contents; exits 0 having done nothing. **Always `--force` from a local path.**
+  ⚠ **The herald's exclusion reason ("process gone, or pid reused") is FALSE for the migration
+  case** — all four declaring processes were alive 4 days, no pid wrap; real cause is the route
+  predating the guard fields. Don't debug a dead agent that isn't.
+  ⚠ **My miss:** I called non-Claude pane delivery an "open risk" when forseti had personally
+  measured it on Aug 28 — didn't check whether it was already settled before calling it open.
+  Delivery now confirmed on `claude`, `pi` and `grok` seats.
+  ⚠ One-tick latency after `declare` reads as failure; `--discover-pid` on a non-Claude process
+  tree remains untested. → `persistent-memory.d/2026-09-01-althing-320-deploy.md`
 - **✅ A6000 window CLOSED 2026-09-01 — operator freed ComfyUI's VRAM instead of anyone
   stopping it.** ⚠ It was a **model unload, not a stop**: `comfyui` still up 8 days, same pid,
   HTTP 200, 18,500 -> 612 MiB. ⚠ **The resulting ~43.8 GB free is a snapshot, not a floor** —