Roadmap: what should the smallest reliable daily-driver flow be?

[SproutSeeds]

I want clawdad to become easier to adopt as a real daily-driver orchestration tool rather than just an internal-use CLI.

The public question I want to pin down is the smallest loop that must feel solid before anything broader:

register project -> choose session -> dispatch -> read -> resume later

Secure self-hosting and the Tailscale phone flow matter too, but I think they should stay the second layer, not the first adoption gate.

Questions:

• What would you need this smallest loop to do reliably before you would trust it?
• Which part of the current model feels least obvious: project buckets, tracked sessions, dispatch, readback, or secure listener setup?
• If you were going to contribute one thing first, what would it be?