From 8fe56cd2eb5b554802c1a9f7d842ad89dd2b12ac Mon Sep 17 00:00:00 2001
From: Keysat <licensing@keysat.xyz>
Date: Tue, 16 Jun 2026 21:36:06 -0500
Subject: [PATCH] Mark capture keyword parsing deployed and verified

---
 AGENTS.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 1c6e7a7..11b70f5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -246,8 +246,9 @@ once" is not done.
 - **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.
+  (commit `0786286`) is **deployed and verified** (Spark updated + restarted 2026-06-16) — leading
+  `bug:`/`feature:`/`chore:`/… keywords now set the inbox item type. 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.