Mark capture keyword parsing deployed and verified

This commit is contained in:
Keysat
2026-06-16 21:36:06 -05:00
parent 87bb3c95ec
commit 8fe56cd2eb
+3 -2
View File
@@ -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 - **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 `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 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 (commit `0786286`) is **deployed and verified** (Spark updated + restarted 2026-06-16) — leading
running bot logs every capture as `idea`. How it works + the Element `/`-interception caveat: D13. `bug:`/`feature:`/`chore:`/… keywords now set the inbox item type. How it works + the Element
`/`-interception caveat: D13.
- **Optional / triggered next moves:** - **Optional / triggered next moves:**
- Badge reflects container liveness only, not Synapse connectivity — add a Docker `HEALTHCHECK` - 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. (bot-side liveness signal → read `{{.State.Health.Status}}`) when "running but silent" bites.