Author orch Markdown test plan

docs/implementation-roadmap.md

@@ -21,7 +21,7 @@ As of now:
 - `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 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/`
-- an inbox-style human-readable `orch` test-plan skeleton now exists under `docs/tests/orch/`, with a `ROADMAP.md`, shared conventions, workflow entrypoint, and one index `README.md` per implemented leaf command
+- a human-readable `orch` test-plan set has now been authored under `docs/tests/orch/`, with a `ROADMAP.md`, shared conventions, workflow scenarios, per-command indexes, and concrete case documents aligned to the current CLI surface, including supplemental coverage for key flag validation, ordering/limit behavior, payload-only answers, cleanup errors, and council report default/error contracts
 - a reusable Codex skill package for `inbox` now exists under `skills/inbox/`, with a formal `SKILL.md`, `agents/openai.yaml`, and a bundled CLI binary asset
 - an inbox skill forward-test plan directory now exists under `docs/tests/inbox-skill/`, with a shared execution template and multiple scenario cases
 - an execution-roadmap workflow now exists under `docs/roadmaps/active/` and `docs/roadmaps/archive/` for agent-level work traces and completion archives
@@ -480,9 +480,10 @@ Definition of done:
 
 Status:
 
-- initial skeleton created under `docs/tests/orch/`
-- global conventions, shared fixtures, workflow entrypoint, and per-command index documents now exist
-- command-case Markdown files are still pending and should be authored against the backlog in `docs/tests/orch/ROADMAP.md`
+- current planned `orch` Markdown test-plan set is authored under `docs/tests/orch/`
+- global conventions, shared fixtures, workflow scenarios, per-command indexes, and concrete case documents now exist
+- `docs/tests/orch/ROADMAP.md` now tracks authored counts, document progress, and future additions in the same style used for `docs/tests/inbox/ROADMAP.md`
+- supplemental command-visible cases now cover high-value gaps in `task add`, `ready`, `answer`, `cleanup`, and `council report`
 
 Goal:
 
@@ -495,17 +496,18 @@ Directory layout:
 - `docs/tests/orch/_shared/README.md`
 - `docs/tests/orch/workflows/README.md`
 - `docs/tests/orch/<leaf-command>/README.md`
+- `docs/tests/orch/<leaf-command>/<case-slug>.md`
 
 Current document model:
 
 - one folder per implemented leaf command
 - each command folder uses `README.md` as an index only
 - workflow cases live in `docs/tests/orch/workflows/README.md`
-- detailed case backlog is tracked centrally in `docs/tests/orch/ROADMAP.md`
+- detailed case backlog and authored-case register are tracked centrally in `docs/tests/orch/ROADMAP.md`
 
 Next documentation step:
 
-- start authoring the highest-value scheduler and workflow cases from `docs/tests/orch/ROADMAP.md`, beginning with the happy-path lifecycle, dependency-blocked-answer flow, and strict worktree dispatch cases
+- keep `docs/tests/orch/ROADMAP.md` synchronized when new `orch` CLI behavior or workflow cases are added, removed, or materially revised
 
 ## Out Of Scope For First Pass