Author orch Markdown test plan

This commit is contained in:
2026-03-19 16:27:28 +08:00
parent b448d98e71
commit a20bec1cac
68 changed files with 2225 additions and 160 deletions
@@ -0,0 +1,65 @@
# Orch Markdown Test Cases
## Status
- `completed`
## Owner
- codex
## Started At
- `2026-03-19`
## Goal
- 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
## Scope
- 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
## Checklist
- [x] create or adopt an execution roadmap for the workstream
- [x] inspect representative `inbox` Markdown case files and map `orch` cases from current backlog
- [x] author core scheduler command cases and update their indexes
- [x] author interactive leader command cases and update their indexes
- [x] author council command cases and update their indexes
- [x] author workflow cases and synchronize `docs/tests/orch/ROADMAP.md`
- [x] update `docs/implementation-roadmap.md`
- [x] archive this roadmap with a completion summary
## Files
- `docs/roadmaps/archive/orch-markdown-test-cases.md`
- `docs/implementation-roadmap.md`
- `docs/tests/orch/ROADMAP.md`
- `docs/tests/orch/workflows/README.md`
- `docs/tests/orch/<leaf-command>/README.md`
- `docs/tests/orch/<leaf-command>/<case-slug>.md`
## Decisions
- 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`
## Blockers
- none
## Next Step
- no further step in this workstream; future changes should start from `docs/tests/orch/ROADMAP.md` if new cases are added
## Completion Summary
- 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
@@ -0,0 +1,71 @@
# Orch Markdown Test Gap Fill
## Status
- `completed`
## Owner
- codex
## Started At
- `2026-03-19`
## Goal
- fill the five highest-priority Markdown test-plan gaps in `docs/tests/orch/` so the current `orch` CLI has better coverage for key flag validation, non-default output behavior, and error contracts
## Scope
- add or update `docs/tests/orch/task-add/` for invalid `acceptance-json` and invalid `priority`
- add or update `docs/tests/orch/ready/` for priority ordering and `--limit`
- add or update `docs/tests/orch/answer/` for payload-only or empty-input validation
- add or update `docs/tests/orch/cleanup/` for invalid-input or no-matching-work cleanup behavior
- add or update `docs/tests/orch/council-report/` for pre-tally/invalid-show/only-unanimous report behavior as needed
- keep `docs/tests/orch/ROADMAP.md` and `docs/implementation-roadmap.md` synchronized
## Checklist
- [x] create an execution roadmap for the workstream
- [x] add missing `task add` and `ready` cases and update indexes
- [x] add missing `answer` and `cleanup` cases and update indexes
- [x] add missing `council report` cases and update indexes
- [x] synchronize `docs/tests/orch/ROADMAP.md`
- [x] update `docs/implementation-roadmap.md`
- [x] archive this roadmap with a completion summary
## Files
- `docs/roadmaps/archive/orch-markdown-test-gap-fill.md`
- `docs/implementation-roadmap.md`
- `docs/tests/orch/ROADMAP.md`
- `docs/tests/orch/task-add/README.md`
- `docs/tests/orch/task-add/*.md`
- `docs/tests/orch/ready/README.md`
- `docs/tests/orch/ready/*.md`
- `docs/tests/orch/answer/README.md`
- `docs/tests/orch/answer/*.md`
- `docs/tests/orch/cleanup/README.md`
- `docs/tests/orch/cleanup/*.md`
- `docs/tests/orch/council-report/README.md`
- `docs/tests/orch/council-report/*.md`
## Decisions
- use focused follow-up case files instead of broad rewrites to keep the current authored set stable
- keep shared tracking files in the main thread and delegate only disjoint command directories
## Blockers
- none
## Next Step
- no further step in this workstream; future follow-up should start from the updated `docs/tests/orch/ROADMAP.md`
## Completion Summary
- added 10 supplemental `orch` Markdown test-plan cases covering high-priority gaps in `task add`, `ready`, `answer`, `cleanup`, and `council report`
- synchronized the relevant command index `README.md` files, the shared `docs/tests/orch/ROADMAP.md` ledger, and the project-level implementation roadmap
- used sub-agents for three disjoint directory slices while keeping shared tracking files in the main thread
@@ -0,0 +1,59 @@
# 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