memory: snapshot — infra-ops moved to a pane route; waiters get reaped

The waiter died a second time, within minutes of being armed, so this
seat stopped re-arming and declared a pane route instead. That is exactly
what 3.2.0 shipped for.

- althing-route declare --discover-pid walks the ancestry to the
  long-lived claude process rather than the ephemeral bash that invoked
  it. Passing --pid $$ would bind the route to a shell that dies with the
  tool call.
- Recorded the sharper form of the failure: the waiter does not just die,
  it dies after confirming it is up. Both waiters reported push and
  reachable immediately after arming. So a green postbox status is not
  durable evidence of monitoring, and the reap is not confined to the
  pane seats that were migrated -- this seat is a fifo waiter and was hit
  twice.

Both consequences raised with forseti on the deploy thread, along with a
note that reachable is a report rather than a delivered poke.

persistent-memory.md

@@ -145,6 +145,11 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
   ⚠ 4 pane routes revoked by the new guards (bil-/dvalin-/eitri-/regin-smithy-dev); they
   re-declare with `althing-route declare --pid <pid>`. **Deliberately not notified** (no
   unsolicited fleet broadcast) — operator's call.
+  ⚠ **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`
 - **✅ 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,