Title

Implement Orch Markdown Test Cases As Automated Tests

Status

Add automated orch coverage for the command-level cases documented under docs/tests/orch/.
Keep roadmap and implementation status synchronized while the work is in progress.

Add or expand Go tests for currently undocumented automation gaps under internal/cli/orch/.
Update docs/implementation-roadmap.md to reflect the broader orch automated coverage.
Update docs/tests/orch/ROADMAP.md to reflect the alignment between Markdown cases and automated coverage.

Review repository instructions, implementation roadmap, and docs/tests/orch/ case inventory.
Map Markdown cases to existing orch automated coverage and identify missing scenarios.
Implement missing non-council command tests.
Implement missing council/report command tests.
Run targeted and full orch test validation.
Update roadmap documents and archive this execution roadmap.

Start from the existing internal/cli/orch/integration_test.go suite instead of creating a second parallel harness.
Use sub-agents with isolated write scopes where practical, while keeping shared roadmap and final integration in the main thread.
Split the missing coverage into four focused test files:
- command_contracts_core_test.go for run show, task add, and ready
- command_contracts_edges_test.go for answer and cleanup
- command_contracts_remaining_test.go for the remaining command and workflow gaps
- council_report_contracts_test.go for council report edge/default behavior

Added 19 focused orch tests across four new test files to close the documented Markdown-case gaps under docs/tests/orch/.
Covered the remaining command contracts for run init/show, task add, ready, dispatch, blocked, answer, cleanup, status, reconcile, and council report edge/default behavior.
Added explicit workflow coverage for strict-worktree dispatch-to-cleanup and council-review end-to-end.
Validation passed with go test ./internal/cli/orch and go test ./....