memory: snapshot — 3.2.1 outcome; the unguardable seats split, and one has a fix

All four seats answered. Delivery is now verified on four TUI families and
forseti's measured idle columns held exactly, so nobody had to guess.

The two seats guard 4 cannot cover made opposite calls on the same facts
and both are right. regin-smithy-dev released to pull-only because the
operator composes in that pane routinely, so the exposure is continuous.
bil-smithy-dev kept its route because that pane is poke-driven, making the
collision window narrow, and because pull-only had already cost them a
notice that sat unread for days. The deciding variable is who composes in
the pane and why, not risk appetite -- a flat rule either way would have
been wrong for one of them.

regin also supplied the only real path to closing the hole: pi and kimi
report no cursor because their input line is not an empty-prompt-at-idle,
so a moment-check reading pane content rather than cursor column would
cover them. Column is a proxy; an empty input line is the actual
predicate. Relayed to forseti as the lead item.

And bil corrected something upstream: the Aug 28 probes proved delivery
against non-Claude TUIs but never exercised the collision case, because
nobody was typing during them. Two different questions, one body of
evidence, only one of them answered by it -- which means the earlier
retraction of the non-Claude risk flag was right about delivery and
silent about stapling.

Note for the operator: regin-smithy-dev is pull-only as of 22:42 and will
not be poked until it declares again.

persistent-memory.md

@@ -155,7 +155,15 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
   guarded** — `kimi` and `pi` report no cursor at all, so bil- and regin-smithy-dev stay
   permanently exposed; "3.2.1 fixes it" is true only where the cursor is legible. Mitigation for
   those = `althing-route release` (pull-only). ⚠ Declare with an EMPTY input line or the pin
-  captures a composing cursor. → `persistent-memory.d/2026-09-01-althing-320-deploy.md`
+  captures a composing cursor. **Outcome:** delivery verified on **four TUI families**
+  (claude/codex 3, grok 7, kimi/pi none). The two unguardable seats split — **regin-smithy-dev
+  RELEASED (now pull-only, operator composes in that pane routinely); bil-smithy-dev KEPT**
+  (pane is poke-driven, and pull-only had already cost them a notice unread for days).
+  ⚠ **Deciding variable is WHO COMPOSES in the pane, not risk appetite** — a flat rule either
+  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.
+  → `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** —