task

# Task Progress Tracking Record development progress on a durable task: phase, progress, next step, blockers, and validation evidence. Requires the optional task command. Use `npx ai-devkit@latest` for task and agent commands. Before recording task events, run a real read probe: ```bash npx ai-devkit@latest task list --json # or, when a task name is known: npx ai-devkit@latest task list --name <task-name> --json ``` Only treat task tracing as available when the read probe exits 0. If it fails, continue without task logging and include the failed command plus stderr/stdout summary in the final report. Do not block the user's work just because optional task tracing is unavailable or unusable. ## Core idea - **One task per work item.** Create it once; advance its `phase` field as work moves through the lifecycle or debug workflow. - **`<id>` can be a task name.** Every command below accepts the task name in place of a task id, resolving to the latest non-terminal task. Prefer `<task-name>` so agents do not track task ids. - **Choose stable names.** For lifecycle work, use the feature key as the task name. For debugging or review work, choose a short kebab-case task name. - **Emit at checkpoints, not streaming.** Phase transitions, task toggles, immediate next-step changes, fresh evidence, blockers discovered/resolved. A handful of calls per session. - **Sequence mutations.** Never run task mutation commands in parallel for the same task. Each mutation reads t...