memory: snapshot — althing 3.2.2 deployed; discover-pid was a bug, not an unknown

Four of the five items I raised are closed and tagged. The one that
matters most: --discover-pid matched comm == "claude", which means kimi,
grok, codex and pi would each have walked to the multiplexer and refused.
Four of five pane seats could never have used it. It now matches the
pane's own command, which zellij already reports and guard 1 already
compares against, so discovery and the guard read one string.

Recording a second miss of my own alongside it. I handed all four seats
explicit measured pids because I suspected the ancestry walk was broken,
then reported the suspicion as an open question rather than spending the
same twenty seconds to settle it, with four live non-Claude seats in
front of me. That pairs with the earlier miss in the opposite direction:
asserting an open risk on something the author had already measured. Same
root -- having the means to settle a question and reporting it as open
instead.

Also keeping forseti's two dead ends as negative results, because they
are the obvious things to propose next and both fail: locating a TUI's
input box in a screen dump needs per-TUI parsing, and diffing two dumps
to detect typing refuses every poke forever, because status bars carry
live token counts and clocks so consecutive dumps differ on an idle pane.

The kimi/pi coverage gap is deliberately unfixed and now sits with the
operator, with a recommendation to leave it per-seat.

persistent-memory.md

@@ -163,6 +163,12 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
   way would be wrong for one of them. ⚠ **Path to closing the hole (regin's):** a moment-check
   reading pane CONTENT (input-line length) rather than cursor COLUMN would cover pi/kimi —
   column is a proxy, empty-input-line is the real predicate.
+  ✅ **3.2.2 deployed 22:51** — closes 4 of 5: `--discover-pid` was a **BUG not an unknown**
+  (matched `comm=="claude"`, so 4 of 5 pane seats could never have used it; now matches
+  `pane_command`), exclusion message split rather than softened, `--force` in the runbook,
+  latency + status-not-durable in the skill. 🔵 **PENDING OPERATOR:** the kimi/pi seats guard 4
+  cannot cover — poke unguarded / write-without-Enter / pull-only. **Recommended per-seat
+  status quo**; write-without-Enter beats it for neither seat.
   → `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,