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 #10116
/pinned now lists the pinned forges for a forge admin; anyone else gets a 404. It's pushed, but there's no look on the pull yet. What changed The page: src/web/pages/pinned.ts renders one card per forge from pinnedForges, the same read GET /api/v1/admin/pinned uses.
stopped parked by the crew deploy 9018d85
3 earlier comments
/pinned now lists the pinned forges for a forge admin; anyone else gets a 404. It's pushed, but there's no look on the pull yet.
What changed
- The page:
src/web/pages/pinned.tsrenders one card per forge frompinnedForges, the same readGET /api/v1/admin/pinneduses. Each card shows:- the name, app and version, plus a health badge;
- the address as a link, or a note that it hasn't been read yet;
- the last check and the last change with who and when.
- Empty list: it says how to deploy one and links
/deploy-to. - Cards, not a table: this is meant to avoid sideways scroll at 390px, but I haven't measured it.
- Cloud accounts: that page's footer now links
/pinnednext to "Deploy a pinned forge". - Last check: I added
lastCheckOfinsrc/core/pinned.ts. It reads the most recentpinned.checkevent for the forge, since nothing stored that time before. - Doc: the Not done line is gone from
docs/features/pinned-forge.md, and the Web bullet names/pinned. - Tests:
test/pinned-page.test.tshas three new cases, and the file passes (8 tests). They cover the empty list with its deploy link, one forge listed with its details, and a 404 for a non-admin. Signed-out sends the visitor to sign-in. - Other checks:
tsc, the design lint andtest/mcp-size.test.tspass. I touched no MCP tool.scripts/gate.tsprinted nothing and I didn't look at its exit code.
What I left out
- Look on the pull: I can't take a screenshot from this sandbox, so it needs a look from the preview once it deploys.
- Run from the page: the page only reads. Check, Update and Rollback stay in the API, MCP and terminal.
To try it: sign in as the forge admin and open /pinned, or follow the link from Settings → Cloud accounts.
I found nothing in the code to fix, so I'm not pushing again.
- The preview is up. The log shows the process starting, the health check passing and "done".
/healthzreturns 200 on the preview./pinnedredirects signed-out visitors to sign-in, which is what the page should do. - The "no tests declared" line is not a failure of this change. The
appblock inforge.jsonhas no test command, so the preview deploy has none to run. That setting was already like this on main, and I didn't touchforge.json. The checks sit undercheck, and the forge runs those on push. - My own checks, run before the first push:
test/pinned-page.test.ts(8 tests),tsc, the design lint andtest/mcp-size.test.tsall passed.scripts/gate.tsprinted nothing, but I didn't look at its exit code.
If the deploy status stays "failed" only because no tests are declared, that comes from how the app block is set up. It isn't something this pull should change, so a person would need to decide whether to add a test command there.
This pull adds a forge admin's /pinned page that lists the pinned forges. The check failed only because no commit message had the two lines the gate requires. I added an empty commit carrying both, so no code changed.
- Why now: points to issue #10106 as the reason the page goes ahead of the pipeline.
- Try: sign in as a forge admin and open
/pinnedon the preview,https://lab--10116--forge-trevato-apps.open-platform.sh/pinned.
I pushed it as a new commit because amending would need a force push, which is refused. I didn't re-run the tsc or test steps here, since only the commit message changed. The forge's check will run the full set against this push.
Parked by the crew: the check stayed red through 2 automatic tries
/pinnednow lists the pinned forges for a forge admin; anyone else gets a 404. It's pushed, but there's no look on the pull yet.What changed
src/web/pages/pinned.tsrenders one card per forge frompinnedForges, the same readGET /api/v1/admin/pinneduses. Each card shows:/deploy-to./pinnednext to "Deploy a pinned forge".lastCheckOfinsrc/core/pinned.ts. It reads the most recentpinned.checkevent for the forge, since nothing stored that time before.docs/features/pinned-forge.md, and the Web bullet names/pinned.test/pinned-page.test.tshas three new cases, and the file passes (8 tests). They cover the empty list with its deploy link, one forge listed with its details, and a 404 for a non-admin. Signed-out sends the visitor to sign-in.tsc, the design lint andtest/mcp-size.test.tspass. I touched no MCP tool.scripts/gate.tsprinted nothing and I didn't look at its exit code.What I left out
To try it: sign in as the forge admin and open
/pinned, or follow the link from Settings → Cloud accounts.Closes #10106