todos

1# Chat TODO plan
2 
3## What it is
4 
5- A plan **scoped to this chat** — your tasks for the conversation. Shown to the user in the Todo
6  panel; lives with the session (not committed to the repo).
7- **Group = task, item = step.** One user ask = one group; its title is the *outcome* ("Fix login
8  redirect"), not the process. The steps inside are the items — each has a **title**, a **status**
9  (`pending` → `in_progress` → `done`), and an optional **note**. The note is **agent-facing working
10  detail** — the human's default plan view shows titles + status and keeps notes behind a disclosure —
11  so it's where your own tracking, reminders, and the done-criterion live (e.g. "login e2e green"),
12  never a place the user must read to follow along. A task's own status is never stored — it derives from its steps.
13- **Loose items are the shared raw-input queue — and they sit at the END of the plan.** Both sides
14  write there: the user adds from the UI, and you may drop an unprocessed note with `todo_add` (no
15  `group`, no `after`). Loose is *pre-work* — raw kernels and half-formed asks, never a step you are
16  about to execute. `todo_list` renders them **last**, after every group, on purpose: an item added
17  mid-task queues *after* your current work. So **finish (or resume) the task you're on before you pick
18  up a loose item** — don't jump to a freshly-added item and abandon a step you had in progress.
19…