workspace-planslisted

# Purpose The private workspace plan format is a contract: the control plane parses it to render plan progress, phase summaries, and spec coverage. A plan that deviates from the format ships work the operator cannot see. # The contract (never violate) - Plans live at `<workspace>/<project>/workspace/working/{YYYY}/{MM}/{DD}/{slug}/plan/`; task-id `yyyy-mm-dd-slug` is derived from the path — never encode the date in the folder name. - `plan/README.md` — objective, architecture decisions with real file paths, the sequencing table with exactly these header cells: `| # | Phase | Doc | Depends on |`, risks, Definition of Done. - `plan/phase-N-<slug>.md` per phase (flat; `step-NN-*.md` is legacy read-compat only) — each with a self-contained copy-paste executor prompt, `- [ ]` acceptance criteria checkable by command or boolean inspection, and an empty `## Completion Report` section as the LAST section. - `plan/manifest.json` — machine-readable phase DAG (must pass `python3 -m json.tool`). - Optional `plan/spec.md` with `- [ ] **SC-n** — <criterion>` lines; then every phase doc carries a `**Covers:** SC-…` header line (coverage is linted). # Executor duties Tick each satisfied criterion `- [ ]` → `- [x]` immediately after verifying it — progress is derived only from these checkboxes. When a phase's last criterion is ticked, fill that doc's `## Completion Report` (what shipped, files/commits, verification output, deviations; ≤50 lines) — the dashboard render