feat: v2 user-centric todo spec — full Todoist-style app from behaviors
Rewrote spec from user perspective: "users can create tasks with
priorities and due dates" instead of "POST /todos must accept JSON".
Phoenix derives API endpoints, database schema, JOINs, computed
fields (is_overdue, active_task_count, completion_percentage), and
a full web UI from behavioral descriptions.
Architecture target now translates user requirements to implementation:
"users can view X" → GET endpoint, "users can filter by Y" → query
params, "visually highlighted" → UI concern.
Fixed: cmdRegen now loads architecture from config. Architecture stub
fallback produces valid Hono routers. Added trigger/migration guidance.
7 IUs generated: Tasks, Projects, Filtering, Quick Stats, Integration,
Data Integrity, Web Experience.
This is a binary file and will not be displayed.
This is a binary file and will not be displayed.
This is a binary file and will not be displayed.