Complete inbox CLI implementation

docs/implementation-roadmap.md

@@ -12,16 +12,18 @@ As of now:
 
 - architecture and workflow docs are written
 - CLI surfaces for `inbox`, `orch`, worktree execution, and `council-review` are defined
-- SQLite schema drafts exist in the docs
+- embedded SQLite schema and migrations exist in code
 - JSON output shapes are defined for the major flows
 - Go module and initial command skeletons exist
 - `inbox` and `orch` both compile
 - shared SQLite schema initialization exists
-- `inbox init` works and creates the database schema
+- `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, and `--body-file`
+- integration tests cover the main inbox lifecycle plus wait/watch flows
 - `orch` currently exists as a command skeleton only
-- no higher-level inbox or orch workflows have been implemented yet
+- no scheduler workflows have been implemented yet
 
-This means the project is past design discovery and ready for code implementation.
+This means the project is past design discovery and ready for `orch` implementation.
 
 ## Source Of Truth
 
@@ -59,10 +61,11 @@ Build a Go-based local agent orchestration stack with:
 Current implementation status:
 
 - `Milestone 1: Go Skeleton` is complete
-- `Milestone 2: Shared DB Layer` is partially complete
-- `Milestone 3: Inbox Happy Path` has started only through `inbox init`
+- `Milestone 2: Shared DB Layer` is complete enough for both CLIs
+- `Milestone 3: Inbox Happy Path` is complete
+- `Milestone 6: Waiting Primitives` is partially complete through `inbox wait-reply`
 
-The next practical coding target is the rest of the inbox happy path.
+The next practical coding target is `Milestone 4: Orch Core Scheduling`.
 
 ### Milestone 1: Go Skeleton
 
@@ -113,7 +116,7 @@ Definition of done:
 
 Status:
 
-- partially completed
+- completed for current inbox needs
 
 Completed so far:
 
@@ -124,7 +127,7 @@ Completed so far:
 
 Remaining:
 
-- decide whether `orch` should gain an explicit DB bootstrap check or reuse `inbox init`
+- decide whether `orch` should gain an explicit DB bootstrap check or continue to rely on `inbox init`
 
 ### Milestone 3: Inbox Happy Path
 
@@ -158,20 +161,24 @@ Definition of done:
 
 Status:
 
-- not complete
+- completed
 
 Completed so far:
 
 - `inbox init`
-
-Next commands to implement:
-
 - `inbox send`
 - `inbox fetch`
 - `inbox claim`
+- `inbox renew`
 - `inbox update`
+- `inbox reply`
 - `inbox done`
+- `inbox fail`
+- `inbox cancel`
+- `inbox list`
 - `inbox show`
+- `inbox watch`
+- `inbox wait-reply`
 
 ### Milestone 4: Orch Core Scheduling