The forge owner's home names a run stopped twice by restarts in one plain line, with Try again #11640

Home now shows one line for each run the forge's restarts stopped twice in the last 24 hours, with a Try again button. bun x tsc --noEmit, bun scripts/gate.ts, bun scripts/design-lint.ts and the touched tests pass. I did not take the before/after screenshot the issue asks for, so the pull has none. The positive Try again path (a signed-in owner's post that re-queues the run) is not tested.

What changed

• The line: src/web/studio/stopped_twice.ts finds failed agent runs whose summary is STOPPED_TWICE ("stopped twice by its forge restarting; not tried again"). It shows the issue (linked), that reason, and a Try again button. All values are escaped. The line appears in home's "Needs you" section, and there is no line when there is none.
• New route: the issue named an existing re-queue route, but only the /fleet preview/apply flow existed. I added POST /:owner/:name/runs/:id/requeue beside the cancel route. It calls requeueRepoRun and does the same-origin check through readForm. It answers with a flash and redirects home.
• Query: one bounded query, at most 5 lines, only for repos the viewer can write to. Reusing home's existing list of writable apps keeps / within its 46-statement budget.
• Tests: test/home-stopped-twice.test.ts covers four cases:

- no line when nothing qualifies; - one line with escaped title and button, while a run over 24 hours old, one with another failure reason, or one with a newer run on its issue shows none; - a stranger sees no line; - a cross-origin post to the route is refused.

Left out

• Flash text: after Try again the flash reads "Queued again." and the refusal reasons are plain sentences. Nothing is added to a run page.

To try it: sign in as an owner who has a run failed with that summary, open /, and press Try again. The line disappears once a newer run exists for that issue.

Closes #11583

Home now shows one line for each run the forge's restarts stopped twice in the last 24 hours, with a Try again button. bun x tsc --noEmit, bun scripts/gate.ts, bun scripts/design-lint.ts and the touched tests pass. I did not take the before/after screenshot the issue asks for, so the pull has none. The positive Try again path (a signed-in owner's post that re-queues the run) is not tested.

What changed

• The line: src/web/studio/stopped_twice.ts finds failed agent runs whose summary is STOPPED_TWICE ("stopped twice by its forge restarting; not tried again"). It shows the issue (linked), that reason, and a Try again button. All values are escaped. The line appears in home's "Needs you" section, and there is no line when there is none.
• New route: the issue named an existing re-queue route, but only the /fleet preview/apply flow existed. I added POST /:owner/:name/runs/:id/requeue beside the cancel route. It calls requeueRepoRun and does the same-origin check through readForm. It answers with a flash and redirects home.
• Query: one bounded query, at most 5 lines, only for repos the viewer can write to. Reusing home's existing list of writable apps keeps / within its 46-statement budget.
• Tests: test/home-stopped-twice.test.ts covers four cases:

- no line when nothing qualifies; - one line with escaped title and button, while a run over 24 hours old, one with another failure reason, or one with a newer run on its issue shows none; - a stranger sees no line; - a cross-origin post to the route is refused.

Left out

• Flash text: after Try again the flash reads "Queued again." and the refusal reasons are plain sentences. Nothing is added to a run page.

To try it: sign in as an owner who has a run failed with that summary, open /, and press Try again. The line disappears once a newer run exists for that issue.

Home now names a run the forge's restarts stopped twice in one line, with Try again, and the terminal has the same list with the same action. The new tests pass, along with tsc, gate.ts, design-lint and the palette tests. I did not run the full suite; the forge's check does that on push.

What changed

• Shared query: src/runs/stopped_twice.ts has stoppedTwiceRuns(db, writableRepos). It returns plain data for runs from the last 24 hours, newest first, up to 5, and leaves out any issue that already has a newer agent run. Home's line (src/web/studio/stopped_twice.ts) and the terminal both read it.
• Terminal door: src/tui/screens/stopped_twice.ts adds a "Stopped runs" palette command, registered in forgeCommands in src/tui/forge.ts like the packs screen.

- It lists only repositories the viewer may write. - j/k move, and Enter or r calls requeueRepoRun, the same action the web route uses. - It re-reads the database on every draw, so a retry on either door shows on the other without a reload. - The web side needed no new push mechanism, because requeueRepoRun is the same code the web route runs.

• Docs: docs/features/stopped-twice.md covers both doors.
• Tests: test/home-stopped-twice.test.ts now includes:

- A writer's same-origin post queues a new run (the issue goes from 1 to 2 agent runs) and the line disappears from Home. - A signed-in non-writer's same-origin post queues nothing and leaves the line in place. - The terminal screen lists the same run, and Enter queues it and clears the line. - The test runs now use a real crew agent as the run's actor, because Try again needs one.

• Roster test: I added the new palette entry to the pinned roster lists in test/palette-roster.test.ts.
• Ordering: runRequeue and requeueRepoRun are back in the existing import order in server.ts and runs.ts. The success redirect to / is now commented as deliberate, since only Home posts this route.

Not done

• Screenshot: I did not add the before/after screenshot. The sandbox has no browser, and the preview needs a stopped-twice run to show anything.
• Retry flash: The Try again flash on Home is still a plain redirect, with no per-run confirmation.
• Agent roster: The palette entry is also listed for agent accounts; it is harmless there, because requeueRepoRun refuses them.

To try it: Sign in as an owner with a run stopped twice, open / and press Try again. In the terminal, open the "Stopped runs" palette command.

Left #11583 open: 1 unticked item remain (bun scripts/design-lint.ts, bun x tsc --noEmit and the touched tests pass in the sandbox before the push; before/after screenshot in the pull).