The settings tab and account checklists

Each row on the settings tab is an account this project needs.

Where the rows come from

The rows come from the roster and the platforms the project builds, by the same code torta doctor uses. The catalog covers Claude Code, GitHub, Vercel and the other targets a project can declare.

Each row shows:

• what it is and why this project needs it
• the login command or the sign-up page
• which agents asked for it
• every step, with its state

How a step is checked

Three kinds of step:

• a command: a real command is run for its exit status. Its output is always discarded.
• a config value: a key in torta.json is filled in or it is not.
• a manual step: nothing can be probed, so you tick it yourself.

A failed step names what failed: “Two of your four repos do not exist, and here are the commands”.

The Claude Code row has its own probe: it knows an API key in the environment, a credentials file and a keychain entry, and tells “signed out” from “this machine cannot say”.

Green, red and dormant

The tab reports blockers: every row that is not ready and not dormant. A dormant row is a delivery target nobody has released through yet.

The tab is not part of the board’s live state; it is asked for when opened. A check-again control re-runs the Claude Code row alone.

What the board may write

The board writes three things into torta.json, one at a time:

• domain, the project’s hostname
• confirm, ticking a manual step
• unconfirm, unticking one

Anything else is refused. A domain must be a bare hostname: example.com, not https://example.com/. One value is replaced; the rest of the file goes back untouched.

The route and its error shapes are in the HTTP reference.