Task tracker

A small authenticated task tracker built by following the skills alone. It is the shortest complete example of the recurring shape: one contract, one implementation, one adapter, one composition root.

What it demonstrates

• The triad in miniature. task-contract declares the operations, task-impl-timescale owns the SQL and rules, task-adapter-htmx owns the forms and pages, and task-web composes them.
• Auth as a stack, not a feature. Login routes, sessions, and CSRF come from the framework's auth stack; the task slice never re-implements them.
• Explicit lifecycle. Migrations and the demo account are separate, approved commands — normal startup neither migrates nor seeds.