docs(todo): close the inbox-hook and colloquialisms tasks

Both built, tested, and pushed this session: the task-boundary inbox Stop hook (soft-nudge) and the 'the list' before-close queue plus colloquialisms convention.

1 files changed, 6 insertions, 2 deletions

diff --git a/todo.org b/todo.org
index c192486..a986a4d 100644
--- a/todo.org
+++ b/todo.org
@@ -1433,7 +1433,9 @@ Build notes: the checker's regex must key on "no TODO keyword" so it never flags
 live TODO that legitimately carries a SCHEDULED. TDD, canonical-then-mirror. Batches
 with the dated-seal task above (both touch todo-cleanup.el).
 
-** TODO [#B] Enforce the task-boundary inbox check via a hook :feature:
+** DONE [#B] Enforce the task-boundary inbox check via a hook :feature:
+CLOSED: [2026-07-19 Sun]
+Resolved with the soft-nudge design (94e54f6). New =hooks/inbox-boundary-check.sh= Stop hook blocks the yield once + injects the pending count when =inbox-status -q= exits 1, steps aside on the harness re-entry (=stop_hook_active=) so a mid-task pause never wedges, self-skips on no-inbox/no-inbox-status/clean. Wired ahead of =ai-wrap-teardown= in =.claude/settings.json= (which the live =~/.claude/settings.json= symlinks to) + the snippet; glob-installed by =make install-hooks=. 6 bats (pending/clean/re-entry/no-inbox/absent-status/project-name). protocols.org Inbox Monitoring Cadence now notes the enforcement. Live-verified on ratio (clean inbox no-ops, pending fixture blocks); velox synced + hook linked. The UserPromptSubmit visibility complement stayed unbuilt (optional in the design) — file separately if wanted.
 Today the "check =inbox/= at every task boundary" rule (protocols.org, "Inbox
 Monitoring Cadence") is prose-only — present in all 27 projects' synced
 protocols.org, but nothing mechanically enforces it, so it holds only as well as
@@ -1499,7 +1501,9 @@ other reason" — the harness exposes only "the turn is ending," not "a task is
 ending." The design leans on those two being usually the same in Craig's workflow.
 That's the tradeoff hard-block vs soft-nudge is really about.
 
-** TODO [#B] "Colloquialisms and Expansions" + "the list" before-close-queue convention :feature:
+** DONE [#B] "Colloquialisms and Expansions" + "the list" before-close-queue convention :feature:
+CLOSED: [2026-07-19 Sun]
+Resolved (approved in the speedrun). New =* Colloquialisms and Expansions= section in =protocols.org= documents both shorthands: "put X on the list" → append to a session-scoped Before-Close Queue (=* Before-Close Queue= heading in the session anchor, resets on archive, todo.org for must-outlive items); "tell <project> <msg>" → =inbox-send=. =wrap-it-up.org= Step 1 gained a "Work the Before-Close Queue (before the Summary)" sub-step so queued work rides the wrap commit, unfinished items surfaced in the valediction. Design calls: reference in protocols.org not per-project notes.org (synced = shared norm); queue in the session anchor as home did; wrap step at the front of Step 1, not a new half-step (keeps the "Steps 1-5" framing). 4 documentation-integrity bats (=before-close-queue.bats=). Canonical + mirror synced. The UserPromptSubmit-style variant wasn't in scope.
 Home proposes two linked cross-project norms; Craig recommends rolling them out.
 Origin: home handoff 2026-07-18, design preserved at
 [[file:docs/design/2026-07-18-colloquialisms-and-the-list-proposal.md]]. Needs Craig's