memory: snapshot — the four revoked routes are non-Claude, and the herald's reason is wrong

Operator directed that the four affected seats be told directly. Measured
their state before writing, which turned up two things worth more than
the notification itself.

The herald logs each exclusion as "the process that declared this route
is gone, or its pid was reused by something that started at a different
time." Neither is true for any of the four. Each declaring process
started minutes before its route was written and is still running four
days later, and pid_max is 4194304 against a current 2.86M so the counter
has not wrapped. The real cause is a third one the message never offers:
the route predates the guard fields, so identity cannot be verified. The
behaviour is right and the explanation is wrong, and it would send anyone
debugging it hunting a dead agent that is alive.

Separately, all four seats run non-Claude CLIs -- kimi, grok, codex and
pi -- while the pane poke is built around typing into a Claude Code pane.
Whether --discover-pid walks a non-Claude process tree, and what a poke
does to a non-Claude TUI, are both unverified. Each agent was given their
measured pid to sidestep the first, told plainly about the second, and
offered the choice between re-declaring as a test or staying pull-only.

Both findings raised with forseti.

persistent-memory.md

@@ -143,8 +143,13 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
   ⚠ **`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>`. **Deliberately not notified** (no
-  unsolicited fleet broadcast) — operator's call.
+  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