The terminal's palette offers "Forges you sent" to an admin: each forge with its claim state and the same apps-running note as /forges #2214

An admin's terminal palette now offers "Forges you sent", which shows each forge they sent with its claim state and the same apps-running note as /forges. The type check and the new test file pass, as do the existing client-list, resilience and family-heartbeat tests. I did not run the whole suite; the forge's check does that.

• Shared wording: src/spawn/clients.ts now holds runningWords(row), which gives "3 apps running" or "1 app running · notes: build failed", or null when no apps run here. It also holds the claim-state words (CLAIM_WORDS, claimState), moved out of src/web/pages/forges.ts. /forges uses them, so the page and the terminal can't drift. The page's markup and data-apps attributes are unchanged.
• Screen: src/tui/screens/forges.ts shows one row per forge: name, "for …", claim state, then the apps note. With nothing sent it shows "You have not sent a forge yet". It never shows a claim link.
• Palette: src/tui/forge.ts adds the forges command only when session.user?.isAdmin === true. It runs clientRows inside runAsync, as the Family command does. A member and a guest don't get the command.
• Tests: test/tui-forges.test.ts covers the admin being offered the command, the empty line, and a member and a guest not being offered it. It also covers rows with all apps up, with an app down and its reason, with unknown and still-being-made states, and with no link. The /forges page is covered by the existing client-list and family-heartbeat tests, which still pass. I did not add a new test that renders the page and the screen from one row.
• Not done: the row tests call forgeLines directly with fake rows instead of spawning real child forges, which keeps them fast. The screen has no keys beyond close, and the chart and release workflow are untouched.

To try it, SSH in as an admin, press ctrl+k, and type "Forges you sent".

🤖 Generated with Claude Code

Closes #2211

All three review points are done and pushed. The type check and the tui-forges and client-list tests pass; the preview is unchecked by eye.

• README: a sentence after the /forges line (l.23) says an admin's terminal palette offers "Forges you sent". It lists each forge with its claim state and the apps-running note, and never a claim link.
• Aliases: STATE and stateOf are gone from src/web/pages/forges.ts. The page now uses CLAIM_WORDS and claimState directly.
• Cut-off list: the terminal screen keeps as many rows as fit. When some don't, its last row reads "+N more (see /forges)". I did not add scrolling, because the page already shows the full list. A new test covers the fit and cut cases.

The first push of this round had a type error: I had deleted the card rectangle line by mistake. I put the line back in the second push, 9899a11c, and the type check is clean again.

🤖 Generated with Claude Code

The check on the current head, 9899a11c, passed ("check passed in 36s"), so there's nothing left to fix. The failure report most likely came from the earlier push 00f21c11, which had the type error I fixed in 9899a11c.

I made no changes this turn and pushed nothing. The branch is unchanged from the previous round. The earlier pushes were 5a7ec050, 00f21c11 and 9899a11c.

• What I ran locally: The gate script and the type check are clean, the hollow-work audit is clean, and the new and related tui, spawn and client-list tests pass (469 tests). A full local bun test had five failures, none in the code this pull touches. The scaffold and capacity ones also fail on origin/main. The other three (SSH port, chromium capture, studio viewport) I did not check against main and did not investigate.
• Why it looks sandbox-related: The scaffold failure is a package-registry connection refused. The capacity failure is a FORGE_CHECK_SHARDS environment variable leaking in from the shard runner.

The pull description from my earlier message still stands.

🤖 Generated with Claude Code