test: add inbox command integration coverage

docs/implementation-roadmap.md

@@ -19,7 +19,7 @@ As of now:
 - shared SQLite schema initialization exists
 - `inbox` is implemented end-to-end, including send/fetch/claim/renew/update/reply/done/fail/cancel/list/show/watch/wait-reply
 - `inbox` supports blocking waits, lease renewal, unread fetches backed by per-agent read cursors, `--body-file`, artifact attachments, and structured JSON errors with stable exit codes
-- integration tests cover the main inbox lifecycle, wait/watch flows, artifact persistence, and JSON error contracts
+- integration tests now cover each implemented inbox command, plus the main inbox workflows, wait/watch flows, artifact persistence, unread behavior, and JSON error contracts
 - a human-readable inbox command test-plan set has been authored under `docs/tests/inbox/`
 - `orch` currently exists as a command skeleton only
 - no scheduler workflows have been implemented yet
@@ -289,10 +289,14 @@ Reason:
 
 ## Suggested Early Tests
 
-Add these tests before the codebase grows too much:
+Completed so far:
 
 - schema init test
-- inbox thread lifecycle test
+- inbox command-level CLI integration coverage aligned to `docs/tests/inbox/`
+- inbox workflow lifecycle coverage
+
+Still recommended before the codebase grows too much:
+
 - single-task orch dispatch and reconcile test
 - worktree path generation test
 - council tally grouping test