GET /api/v1/cloud/accounts answers the forge's cloud accounts with each token's use and today's calls, never a secret, as MCP `cloud_accounts` does #8319

GET /api/v1/cloud/accounts now answers the forge's cloud accounts, as MCP cloud_accounts does: each token's use and today's calls, never a secret. The gate, tsc, the route's own test (test/api-cloud-accounts.test.ts) and test/tui-model-review.test.ts all pass here.

• Route: it is in src/http/api/cloud.ts, wired in src/http/api.ts and the OpenAPI contract. It reuses cloudOverview and usesByVendor, so the HTTP and MCP answers agree.
• Who can call it: a missing session gets 401. A read-only token gets 403, because every vendor call is audited. A signed-in non-admin gets 404, as if the route didn't exist.
• Why it was parked: the check had gone red on "a non-admin sees no review and cannot decide" in test/tui-model-review.test.ts, a review-screen test this change doesn't touch. It passes here, before and after merging main, so I treated it as unrelated or flaky and changed nothing in it. If the check goes red on it again, that test needs its own look.
• What I did this time: I merged origin/main into the branch (121 new commits, no conflicts) and pushed it.
• What I left out: I did not run the full suite or the whole set of tests scripts/fast.ts named (1157 files, over the 5-minute budget). The forge's check runs everything on push.

To try it, call GET /api/v1/cloud/accounts with an admin's read-write token.

🤖 Generated with Claude Code

Closes #8025

GET /api/v1/cloud/accounts now answers the forge's cloud accounts, as MCP cloud_accounts does: each token's use and today's calls, never a secret. The gate, tsc, the route's own test (test/api-cloud-accounts.test.ts) and test/tui-model-review.test.ts all pass here.

• Route: it is in src/http/api/cloud.ts, wired in src/http/api.ts and the OpenAPI contract. It reuses cloudOverview and usesByVendor, so the HTTP and MCP answers agree.
• Who can call it: a missing session gets 401. A read-only token gets 403, because every vendor call is audited. A signed-in non-admin gets 404, as if the route didn't exist.
• Why it was parked: the check had gone red on "a non-admin sees no review and cannot decide" in test/tui-model-review.test.ts, a review-screen test this change doesn't touch. It passes here, before and after merging main, so I treated it as unrelated or flaky and changed nothing in it. If the check goes red on it again, that test needs its own look.
• What I did this time: I merged origin/main into the branch (121 new commits, no conflicts) and pushed it.
• What I left out: I did not run the full suite or the whole set of tests scripts/fast.ts named (1157 files, over the 5-minute budget). The forge's check runs everything on push.

To try it, call GET /api/v1/cloud/accounts with an admin's read-write token.

🤖 Generated with Claude Code

I added docs/features/cloud.md, as sentinel asked, and pushed it. I did not run bun test or the type check, because the only change is that one markdown file.

The new file covers the four ways to reach the cloud accounts: the Settings → Cloud accounts page, the terminal screen (src/tui/screens/cloud.ts), MCP cloud_accounts, and GET /api/v1/cloud/accounts. For the route it gives a curl example and the 401, 403 and 404 answers. It also says no door ever returns a secret.

The README is untouched, since it is capped.

I left out any write route. The HTTP route only lists accounts; attaching, rotating and removing stay on the page and in the terminal, where the token is typed masked. The doc says this.