diff --git a/AGENTS.md b/AGENTS.md
index e5d56fd..1c6e7a7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -243,14 +243,11 @@ once" is not done.
 - **Phase 3 (Spark Control) shipped 2026-06-16 in v0.21.0:** status badge + Update / Restart /
   Stop-Start / Logs tile; the Spark's dir is now a Gitea clone and deploy = the Update button.
   Detail in ROADMAP + `docs/spark-control-integration.md`; no matrix-bridge code change.
-- **Capture mode (D13) LIVE 2026-06-16 — proven on 1 room, N=3 pending.** A reply in a room's
-  capture thread logs to `standards/INBOX.md` via `capture-note.sh` and confirms in-thread. All 11
-  rooms + all-projects have seeded `capture_thread` roots (IDs in the Mac's `config.toml`). A
-  leading keyword sets the type — `bug:` / `feature:` / `chore:` / `idea:` (etc.); no keyword →
-  `idea`; priority is always `P2` (set the real one at `/triage`). **Element note:** the typed
-  `/capture` fallback is mostly dead — Element grabs any `/`-message as a client command ("Unknown
-  Command"); the no-slash **thread** is the path (`//capture …` forces a literal send if ever
-  needed). Deploying capture-style code? See the master-deploy gotcha under Commands → Deploy.
+- **Capture mode (D13) LIVE 2026-06-16 — proven on 1 room, N=3 pending.** Per-room capture threads
+  → `standards/INBOX.md` via `capture-note.sh`, confirmed in-thread; all 11 rooms + all-projects
+  have seeded `capture_thread` roots (IDs in the gitignored `config.toml`). Keyword type parsing
+  (commit `0786286`) is pushed but **pending one Update** (code-only, no `scp`) — until deployed the
+  running bot logs every capture as `idea`. How it works + the Element `/`-interception caveat: D13.
 - **Optional / triggered next moves:**
   - Badge reflects container liveness only, not Synapse connectivity — add a Docker `HEALTHCHECK`
     (bot-side liveness signal → read `{{.State.Health.Status}}`) when "running but silent" bites.