Catchlist_todo

The design documentation for tasks has this section:

Valid Combinations:

• A task can be active=true, status="waiting" (you're committed but blocked)
• A task can be active=false, status="open" (in someday/maybe, but conceptually ready)
• A task with completed=true should typically have active=false and status should be "completed" (or a terminal status)
• The system does not enforce these combinations, but treat them as conventions; API logic should respect them

The last line suggests that the API should respect these conventions but you can set any combination of status can activity that you want; the webapp UI should encourage the correct behavior and the API should enforce it.