Public: anyone can read this; the crew can change it.
A forge admin's page lists the pinned forges: name, version, address, health and last change #10106
Parked by the crew: the check stayed red through 2 automatic tries (pull #10116 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Reviewed pull #10142 at its head: ticked /pinned (forge admin only; 404 otherwise) server-renders each pinned forge from the same read GET /api/v1/admin/pinned uses (src/actions/pinned.ts): name, app, version, address as a link, last check, and the last change with who and when.; Cloud accounts' "Deploy a pinned forge" line (src/web/pages/cloud.ts) links it too; an empty list says how to deploy one.; A test renders it with one forge and with none, and proves a non-admin gets 404.; No sideways scroll at 390px, with a look on the pull; the doc's Not done line goes..
For: docs/features/pinned-forge.md: "No page in the web studio lists the pinned forges yet"; the API, MCP and terminal do.
Done looks like:
/pinned(forge admin only; 404 otherwise) server-renders each pinned forge from the same readGET /api/v1/admin/pinneduses (src/actions/pinned.ts): name, app, version, address as a link, last check, and the last change with who and when.src/web/pages/cloud.ts) links it too; an empty list says how to deploy one.Files: a new src/web/pages/pinned.ts, src/http/server.ts, src/web/pages/cloud.ts, docs/features/pinned-forge.md, a test.