Orch Markdown Test Cases

Status

author the first complete wave of human-readable Markdown test-plan cases for orch, using the existing docs/tests/inbox/ structure and writing style as the reference model

add concrete command-case Markdown files under docs/tests/orch/<leaf-command>/
add concrete workflow cases under docs/tests/orch/workflows/README.md
update each affected command index README.md
keep docs/tests/orch/ROADMAP.md synchronized with authored files, authored-case counts, and remaining backlog
update docs/implementation-roadmap.md if the documentation progress materially changes

create or adopt an execution roadmap for the workstream
inspect representative inbox Markdown case files and map orch cases from current backlog
author core scheduler command cases and update their indexes
author interactive leader command cases and update their indexes
author council command cases and update their indexes
author workflow cases and synchronize docs/tests/orch/ROADMAP.md
update docs/implementation-roadmap.md
archive this roadmap with a completion summary

use the existing docs/tests/inbox/ case structure and tone as the immediate template for orch
keep shared index/count integration in the main thread, while delegating disjoint command-directory write scopes to sub-agents
keep docs/tests/orch/ROADMAP.md aligned with the richer docs/tests/inbox/ROADMAP.md format by tracking individual case files in Document Progress and Authored Case Register

no further step in this workstream; future changes should start from docs/tests/orch/ROADMAP.md if new cases are added

authored the current planned orch Markdown test-plan set across workflow, core scheduler, interactive control, and council command surfaces
synchronized docs/tests/orch/ROADMAP.md with real files on disk, authored-case counts, and a completed authored-case register
updated docs/implementation-roadmap.md so future agents see docs/tests/orch/ as an authored test-plan set rather than only a skeleton