# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Add the tables in `design.md` to the web app. If there is no app yet, build the smallest one: a signed-in user and one API route to call. If there is no tool yet, build one with a single command that calls that route. Check: migrations run from empty, and the tool's command reaches the route. 2. **Start (R1).** The server route and the first half of `login`, named after the `cli_name` input. Honour `open_browser`. Check: the R1 acceptance tests pass. 3. **Approve (R2).** The page and its two actions. Check: the R2 acceptance tests pass. 4. **Wait (R3).** The token route and the tool's loop, with a clock that tests can set. Check: the R3 acceptance tests pass. 5. **Tokens (R4).** Checking a token on API requests, expiry from the `token_days` input, and the tokens page. Check: the R4 acceptance tests pass. 6. **Keep the token (R5).** Keychain and fallback file. Check: the R5 acceptance tests pass with a stand-in keychain. 7. **Use and sign out (R6).** Check: the R6 acceptance tests pass. 8. **Automation (R7).** Only if `ci_tokens` is on. Check: the R7 acceptance tests pass. 9. **Pages (R8).** Check: every page can be used with a keyboard alone and at 360 pixels wide. 10. **Finish.** Write the README and run the whole test suite. Check: every item under "Definition of done" in `spec.md` is true.