[andresbott]

Summary

Tasks had no formal path from idea to finished, and subtasks could nest arbitrarily deep. This models the workflow as a kanban board so the TUI and the CLI (used by scripts and agents) share one vocabulary.

What

• Four columns with fixed states: Backlog (open, deferred), Next (new, ready), In Progress (working, review, followup), Done (done).
• The TUI shows one tab per column, each filtering the category tree. Tasks can be moved across columns and states, and a task's plan link can be edited in its dialog.
• Every task gets an optional plan link. Subtasks are limited to one level and follow their parent's column.
• A one-time, backed-up migration moves databases to schema v2. It flattens deeper nesting, maps old statuses, and is serialized across concurrent opens.
• The CLI speaks states, columns and plan links, and list filters match within the column like the TUI.
• Design spec and implementation plan are added under docs/.

Notes

• Breaking: the CLI output and vocabulary changed. Old status names are still accepted on input.
• Movement between columns is not gated, and categories never move. Only tasks change column.