60 lines
1.9 KiB
Markdown
60 lines
1.9 KiB
Markdown
# Orch Markdown Test Review
|
|
|
|
## Status
|
|
|
|
- `completed`
|
|
|
|
## Owner
|
|
|
|
- codex
|
|
|
|
## Started At
|
|
|
|
- `2026-03-19`
|
|
|
|
## Goal
|
|
|
|
- review the authored `docs/tests/orch/` command directories and case files for completeness against the current `orch` CLI and identify any missing or weakly specified test-plan coverage
|
|
|
|
## Scope
|
|
|
|
- inspect each `docs/tests/orch/<leaf-command>/` directory
|
|
- compare current Markdown cases against the implemented CLI and existing automated integration tests
|
|
- identify missing command-visible contracts, edge cases, or unclear assertions
|
|
- summarize findings without expanding scope into unrelated implementation changes
|
|
|
|
## Checklist
|
|
|
|
- [x] create an execution roadmap for the review
|
|
- [x] inspect current `docs/tests/orch/` files and split the review by command area
|
|
- [x] collect findings for core scheduler command directories
|
|
- [x] collect findings for interactive leader/control command directories
|
|
- [x] collect findings for council command directories
|
|
- [x] summarize whether any command directories need supplemental cases or edits
|
|
- [x] archive this roadmap with a completion summary
|
|
|
|
## Files
|
|
|
|
- `docs/roadmaps/archive/orch-markdown-test-review.md`
|
|
- `docs/tests/orch/README.md`
|
|
- `docs/tests/orch/ROADMAP.md`
|
|
- `docs/tests/orch/<leaf-command>/README.md`
|
|
- `docs/tests/orch/<leaf-command>/<case-slug>.md`
|
|
|
|
## Decisions
|
|
|
|
- treat this as a review task first: surface gaps before proposing edits
|
|
|
|
## Blockers
|
|
|
|
- none
|
|
|
|
## Next Step
|
|
|
|
- none; future follow-up should start from the review findings and add only the missing case files or constraints that were called out
|
|
|
|
## Completion Summary
|
|
|
|
- completed a read-only coverage review of the authored `docs/tests/orch/` command directories against the current `orch` CLI and automated integration tests
|
|
- identified the highest-value missing or weakly specified command-visible cases so follow-up authoring can target concrete gaps instead of re-auditing the whole tree
|