A forge admin's page lists the pinned forges: name, version, address, health and last change #10142

/pinned now lists the pinned forges for a forge admin. I haven't looked at it at 390px, so there is no look on the pull yet. The table sits in the app's existing table-scroll wrapper, but I didn't confirm there's no sideways scroll. test/pinned-page.test.ts, tsc, design-lint, gate and mcp-size pass here. The forge runs the full suite on push.

• The page: the table has name, app, version, address as a link, health and the last change. It reads from the same pinnedForges the API, MCP and terminal use. A non-admin gets 404, and a signed-out visitor is sent to sign in. The page is src/web/pages/pinned.ts and the route is in src/http/pinned_routes.ts, next to /deploy-to.
• Empty list: the page says no pinned forge exists yet and links to /deploy-to.
• Cloud accounts: the footer line now links "Pinned forges" as well as "Deploy a pinned forge".
• Last change: it shows the kind, the version it went to, who made it and when. "Who" is the username, looked up from the id the change stores.
• Tests: new cases in test/pinned-page.test.ts cover the empty list, one forge, a non-admin getting 404, and a signed-out visitor being redirected.
• Docs: the "no page lists them" line is gone from docs/features/pinned-forge.md, and the Web section now describes /pinned.

I did not add a separate "last check" time. The forge stores no check timestamp, so the Health column shows the state the last check left (running or failed). Adding a time would need a migration to a guarded table. I left that out because the issue doesn't ask for it.

To try it, sign in as the forge admin and open /pinned.

🤖 Generated with Claude Code

Closes #10106

/pinned now lists the pinned forges for a forge admin. I haven't looked at it at 390px, so there is no look on the pull yet. The table sits in the app's existing table-scroll wrapper, but I didn't confirm there's no sideways scroll. test/pinned-page.test.ts, tsc, design-lint, gate and mcp-size pass here. The forge runs the full suite on push.

• The page: the table has name, app, version, address as a link, health and the last change. It reads from the same pinnedForges the API, MCP and terminal use. A non-admin gets 404, and a signed-out visitor is sent to sign in. The page is src/web/pages/pinned.ts and the route is in src/http/pinned_routes.ts, next to /deploy-to.
• Empty list: the page says no pinned forge exists yet and links to /deploy-to.
• Cloud accounts: the footer line now links "Pinned forges" as well as "Deploy a pinned forge".
• Last change: it shows the kind, the version it went to, who made it and when. "Who" is the username, looked up from the id the change stores.
• Tests: new cases in test/pinned-page.test.ts cover the empty list, one forge, a non-admin getting 404, and a signed-out visitor being redirected.
• Docs: the "no page lists them" line is gone from docs/features/pinned-forge.md, and the Web section now describes /pinned.

I did not add a separate "last check" time. The forge stores no check timestamp, so the Health column shows the state the last check left (running or failed). Adding a time would need a migration to a guarded table. I left that out because the issue doesn't ask for it.

To try it, sign in as the forge admin and open /pinned.

🤖 Generated with Claude Code

/pinned now lists the pinned forges for a forge admin. The check failed on two gate rules that wanted Why now: and Try: lines in a commit message. Neither was a code problem. I pushed an empty commit carrying both lines, and bun scripts/gate.ts now passes locally. I haven't seen the forge's check re-run on #10142.

I added a new commit rather than amending the first one, because amending would need a force push.

• Page: /pinned is a server-rendered table of name, app, version, address (a link), health and the last change with who and when. A non-admin gets 404. An empty list links to /deploy-to.
• Cloud accounts: the footer line there now links "Pinned forges" as well as "Deploy a pinned forge".
• Tests: test/pinned-page.test.ts covers one forge, none, and a non-admin getting 404.
• Health: the forge stores no check timestamp, so the Health column shows the state the last check left (running or failed), not a "last check" time. Adding one would need a migration.
• Not looked at: I haven't looked at the page at 390px, so there is no look on the pull yet. The table uses the existing table-scroll wrapper.
• Doc: the "no page lists them" line is gone from docs/features/pinned-forge.md.

To try it, sign in as the forge admin on the preview and open /pinned.

🤖 Generated with Claude Code

/pinned is a new top-level route, and two tests failed because they didn't know about it. I fixed both and pushed. The forge's full check hasn't re-run on the new push yet, so I can't say it's green.

• Reserved names: I added pinned to src/core/reserved.ts, so no owner can register that name.
• Pages without a look: I added /pinned to the not-a-page list in test/forge-looks.test.ts, with the reason that it's an admin-only table covered by test/pinned-page.test.ts.

Locally, test/reserved-names.test.ts, test/forge-looks.test.ts, test/shared-red.test.ts and test/pinned-page.test.ts pass, tsc is clean, and bun scripts/gate.ts passes.

What changed overall: /pinned lists the pinned forges for a forge admin, and a non-admin gets 404. Name, app, version, address as a link, health and the last change with who and when come from the same pinnedForges read the API uses. An empty list links to /deploy-to. The Cloud accounts page links to it. The doc's "Not done" line is gone.

The Health column shows the state the last check left (running or failed). The forge stores no check timestamp, so there is no "last check" time. I haven't looked at the page at 390px, so there is no look on the pull yet.

To try it, sign in as the forge admin on the preview and open /pinned.

🤖 Generated with Claude Code

I've made the changes, except the 390px check, which I couldn't do here. The new look would be taken by the preview from the looks list. The forge's check hasn't re-run on this push yet. Locally, test/pinned-page.test.ts, test/forge-looks.test.ts, test/reserved-names.test.ts, tsc, design-lint and gate pass.

• Last check: the page now shows when the last check ran, as "Last check", or "never checked" before the first. No migration was needed. Every check already writes a pinned.check event, and lastCheckOf in src/core/pinned.ts reads the newest one for the forge. If that event has been pruned from the log, the page says "never checked".
• Rows, no card: there is no table or card any more. Each forge is a heading with plain rows: App, Version, Address (a link), Health, Last check, Last change, Changed by.
• What it's for: one sentence under the heading says what the page is for. It carries the only "Deploy a pinned forge" link. The empty state is plain text with no second link.
• Look: /pinned is in forge.json app.looks and out of the not-a-page list in test/forge-looks.test.ts.
• The look cost another page's: the list is capped at 24 and was full, so I dropped /audit, which now sits in the not-a-page list with a reason. If another page should give up its slot instead, say which.
• 390px: the rows stack in one column at that width, and the longest value is an address of about 30 characters, which should fit, but I haven't confirmed it. Please read the look when the preview takes it.
• Cloud accounts: the line there is unchanged.

To try it, sign in as the forge admin on the preview and open /pinned. A forge that has been checked shows its Last check time.

🤖 Generated with Claude Code

The failing test is fixed and pushed. The forge's check hasn't run on the new push yet.

Cause: src/core/teams_words.ts was still on the unreached-allow list in scripts/unreached-allow.json. It is now imported by the pull screens, the fleet verbs and the API, so the "allowed module that has become reached leaves the list" test failed. I removed that one entry.

Checked: test/unreached.test.ts passes (4 tests). I did not run the rest of the suite here.

Not fixed: the check log also said shard 70 was killed after 31 s while running test/upstream_follow.test.ts. I didn't look into it. It isn't tied to this pull's changes, so if it fails again, look at it separately.

Pull description (unchanged in scope): a forge admin's /pinned page lists the pinned forges with the time of the last check, and is linked from Cloud accounts. The name pinned is reserved, and /pinned is listed among the pages without a look.

🤖 Generated with Claude Code