Add orch Markdown test-plan skeleton

docs/implementation-roadmap.md

@@ -21,6 +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 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
@@ -475,15 +476,42 @@ Definition of done:
 - shared assumptions are centralized instead of copied into each command file
 - a new agent can pick any case and implement it as an automated test with minimal additional discovery
 
+## Orch Test Documentation Roadmap
+
+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`
+
+Goal:
+
+- make `orch` behavior easy for a new agent to understand and convert into automated tests or manual validation steps without re-reading all scheduler code paths
+
+Directory layout:
+
+- `docs/tests/orch/README.md`
+- `docs/tests/orch/ROADMAP.md`
+- `docs/tests/orch/_shared/README.md`
+- `docs/tests/orch/workflows/README.md`
+- `docs/tests/orch/<leaf-command>/README.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`
+
+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
+
 ## Out Of Scope For First Pass
 
 Do not block v1 on these:
 
-- distributed execution
 - advanced auth or permissions
-- patch-producing council mode
-- configurable reviewer counts beyond three
-- rich similarity engines for proposal grouping
 - background daemons beyond blocking CLI commands
 
 ## Handoff Notes For Future Agents