feat: phases + tasks — per-task execution with phase directories

- A phase is now a directory: 00_phase.md (overview + task index) plus
  small, quick NN_task.md task files; complete/ mirrors todo/
- Task is the unit of execution: run-task.sh (one unit), run-phase.sh
  (phase to completion incl. 00_phase.md final pass), auto-phase.sh
  (all units in order); validate.sh gate runs after every task
- PHASE_COMMIT commits at phase boundaries (00_phase.md / legacy file moves)
- Legacy flat todo/NN_name.md files still execute as a single unit;
  new migrate-phases-to-tasks.sh converts them to the directory layout
- phase-status.sh reports per-task state and the next unit
- New task-template.md; phase templates now carry a Tasks index

phased-execution/assets/executor-prompt.md

@@ -5,7 +5,7 @@ Target phase file: `.agent/phases/todo/{{PHASE}}`
 ## Steps
 1. Read `.agent/PLAN.md` — project goals, architecture, and **LOCKED DECISIONS** (binding; never introduce technology outside them).
 2. Read `AGENTS.md` if present.
-3. Read every file in `.agent/phases/complete/` so your work stays architecturally consistent with what is already built.
+3. Read the completed phase files so your work stays architecturally consistent with what is already built: every `00_phase.md` in `.agent/phases/complete/*/`, plus any legacy flat phase files directly in `.agent/phases/complete/`.
 4. Read the target phase file and complete **every** task in it, in order.
 5. Write the unit and integration tests required by the phase's Testing & Quality section. Do not omit parts of the code to inflate coverage.
 6. Run the project's full test suite and linter. If anything fails — including the phase's coverage criterion — fix it and re-run until green.

phased-execution/assets/phase-final-prompt.md

@@ -0,0 +1,26 @@
+You are the phase-completion executor in a phased build pipeline. You run in a fresh, isolated context; the harness manages phase and task files, retries, and final validation.
+
+Phase overview: `.agent/phases/todo/{{PHASE}}/00_phase.md`
+
+## Steps
+1. Read `.agent/PLAN.md` — project goals, architecture, and **LOCKED DECISIONS** (binding; never introduce technology outside them).
+2. Read `AGENTS.md` if present.
+3. Read the phase overview `.agent/phases/todo/{{PHASE}}/00_phase.md`.
+4. Check the phase's task index against `.agent/phases/complete/{{PHASE}}/`: if any task is missing from there, the overview itself still carries work (a legacy phase with an inline task list) — implement that remaining work now, in order, including its tests.
+5. Otherwise every task is done: this is the final verification pass. Verify **each** completion criterion in the phase overview (commands to run, endpoints to hit, artifacts to exist), and execute any phase-level verification blocks it defines (e.g. a dedicated E2E or contract test suite).
+6. Run the project's full test suite and linter. If anything fails — including the phase's coverage criterion or a completion criterion — fix it and re-run until green.
+7. If you find defects in previously completed work (failing tests, lint errors, bugs), fix those as part of this pass.
+
+## Rules
+- Never start work from other files in `todo/`.
+- Do **not** move, rename, or edit the phase overview, other files in `.agent/phases/todo/`, `.agent/PLAN.md`, or anything in `.agent/phases/complete/`. The harness moves the phase file on success.
+- Do not assume the code is correct; fix any errors you find while testing.
+- Leave the repository functional when you finish.
+
+## Final response
+When everything is green, reply with a report of **at most 15 lines**:
+- What was implemented or verified (short bullet list)
+- Test / lint / coverage results (exact commands and outcomes)
+- Completion criteria: each one with its outcome
+- Notable decisions or deviations
+- The next pending phase, if any

phased-execution/assets/task-executor-prompt.md

@@ -0,0 +1,26 @@
+You are a task executor in a phased build pipeline. You run in a fresh, isolated context; the harness manages phase and task files, retries, and final validation.
+
+Target task file: `.agent/phases/todo/{{PHASE}}/{{TASK}}`
+
+## Steps
+1. Read `.agent/PLAN.md` — project goals, architecture, and **LOCKED DECISIONS** (binding; never introduce technology outside them).
+2. Read `AGENTS.md` if present.
+3. Read the phase overview `.agent/phases/todo/{{PHASE}}/00_phase.md` — objective, dependencies, testing & quality mandate, and completion criteria.
+4. Read this phase's completed task files (`.agent/phases/complete/{{PHASE}}/*.md`, excluding `00_phase.md`) and the `00_phase.md` overviews of other completed phases (`.agent/phases/complete/*/00_phase.md`) so your work stays architecturally consistent with what is already built.
+5. Read the target task file and complete it fully, in order.
+6. Write the unit and integration tests required by the task. Do not omit parts of the code to inflate coverage.
+7. Run the project's full test suite and linter. If anything fails — including the task's coverage criterion — fix it and re-run until green.
+8. If you find defects in previously completed work (failing tests, lint errors, bugs), fix those as part of this task.
+
+## Rules
+- Work only on the target task; never start the next task or work from other files in `todo/`.
+- Do **not** move, rename, or edit the task file, `00_phase.md`, other files in `.agent/phases/todo/`, `.agent/PLAN.md`, or anything in `.agent/phases/complete/`. The harness moves the task file on success.
+- Do not assume the code is correct; fix any errors you find while testing.
+- Leave the repository functional when you finish.
+
+## Final response
+When everything is green, reply with a report of **at most 15 lines**:
+- What was implemented (short bullet list)
+- Test / lint / coverage results (exact commands and outcomes)
+- Notable decisions or deviations
+- The next pending task, if any