Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
docs(api): explain settings fallback and read-only semantics [O5,O6]
Corey Olson9a4f3cc18f6b
diff --git a/docs/api.md b/docs/api.mdindex f5a601a4..f50a0fe4 100644--- a/docs/api.md+++ b/docs/api.md@@ -392,6 +392,8 @@ The server checks any Origin against its own address and grants no CORS permissi| `GET /api/v1/view-link` | Whether the full-machine view can start device sign-in || `POST /api/v1/view-link` | Start, inspect, cancel or continue device sign-in in that view |+Settings `default` names the shipped fallback before other settings constrain it. For example, `testConcurrency.browser` has a default cap of 2, while its current `value` is capped by the effective file concurrency. Credential presence describes configured storage, not whether a credential currently authenticates. Reads preserve settings, registry, durable board data and schema; SQLite may create its normal `-wal`/`-shm` read-lock sidecars.+The local API exposes token management for a board already linked to the relay. `GET` returns `{version: 1, tokens: [...]}`; each row contains only `id`, `board`, `agent`, `created`, `expires` and `revoked`, never a bearer credential. `POST` accepts only `{id}` from that board's token list and returns `{version: 1, linked, board, url, link, sequence, behind, recovery, id, revoked}` with `revoked: true`. Revocation is a person action: the local view has the required person channel, while an ordinary `pullboard serve` API caller is refused with `B26_PERSON_CHANNEL`. An unlinked board cannot list or revoke its relay tokens.The full-machine local view calls `/api/v1/view-link` with its `X-Pullboard-Key` header only. This route rejects query strings and `Authorization`, and a project-scoped view reports `available: false` and refuses sign-in. `GET` returns `{version: 1, available}`. `POST` takes a JSON action: `{action: "start"}` returns `{version, intentId, verificationURL, userCode, expiresAt}`; `{action: "status", intentId}` returns the public state and board outcomes; `{action: "cancel", intentId}` returns the state after cancellation; and `{action: "pairing", intentId}` returns a short HTML page with a link to continue the pending phone-pairing step. The intent id must have been started in this view. Status and cancellation results include `{version, state, boards}` and may include a public `error` or `pairingCleanup`; private machine paths, relay tickets and credentials are not returned. Sign-in and pairing use the existing person flow, so completed board links are not described as rolled back if pairing is cancelled.