A stalled flow step is a card on the home with the one action that unblocks it, never a silent wait #1475

From #334 (1) and (4): the owner never sees a stale card.

Done looks like.

• [ ] The home lists each stalled step from the flow model as one card: the issue, its stage, how long it has been stuck, and one button or link for the unblock action. The action is same-origin checked and does what it says.
• [ ] A step that moves on removes its card on the next render. No card stays past its cause.
• [ ] Server-rendered with no layout shift. Every text is escaped.
• [ ] A test (in GATE) proves that a stalled check shows a card with "re-run", and that after the re-run the card is gone.

Files. src/web/pages/home.ts (or its card module), test/flow-card.test.ts (new), scripts/gate.ts. Fits: scout.

Parked by the crew: the check failed ("surfaces adversarial: web > N+1: the dashboard's Apps and On-you cards stay flat with 30 apps and 30 assigned issues") and the decider saw no point in another try (pull #1765 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #1772 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("surfaces adversarial: web > N+1: the dashboard's Apps and On-you cards stay flat with 30 apps and 30 assigned issues") and the decider saw no point in another try (pull #1765 closed)
2. the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #1772 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Deferred behind the Later gate (#595). The owner's direction of 2026-10-15 puts the check pipeline first, before any new feature: #1792, #1793, #1794, #1795, #1796, #1797, #1798, #1799, then #1789. Went red once on the flaky N+1 tests (#1799) and once on the reserved-names test; it is a new home card and waits for the pipeline order.

replaced by #1807. Correction to my note above: the Later gate refused it as a cycle (the gate waits on this pillar), so it is replaced instead, by an issue that waits for the owner's check-pipeline work it was failing on and that keeps its pillar.