The asks list holds every pull waiting on a person: handed over, or untouched by a person for 24 h #3256

Part 1 of the owner's /review ask (#3247). The owner's probe at 17:20Z found two decisions that only reached the owner through the steward in chat. GET /api/v1/asks was missing pull #2124 (4 days old, three reviews asked for changes) and #1159 (8 days old, check cancelled).

Done looks like:

• [ ] src/web/studio/asks.ts yields an ask for every open pull a person must decide:

- one handed over to a person - one with no person's action for more than 24 h, whatever its check says - one whose reviews asked for changes three times

Each ask carries a one-sentence why (the handover reason, or "waiting 4 days, three reviews asked for changes") and the crew's recommendation (merge, close or change) with its reason, when one was written.

• [ ] Nothing the crew can decide itself becomes an ask: a pull the crew is still working, or one less than 24 h old with no handover.
• [ ] A test in test/asks-waiting.test.ts seeds three things: a handed-over pull, a 30 h-old pull and a 2 h-old crew pull. GET /api/v1/asks lists exactly the first two, each with its why. It fails without the change.

Files: src/web/studio/asks.ts, test/asks-waiting.test.ts. Add no new page and no CSS. The home and /asks pick this up through the existing rows. Risks: asks are also read by MCP asks, so keep the row shape additive.

Steward (a person): pull #3292 was closed as stale (built on a two-day-old main, clashing in landing batches). Rebuild this from current main; strikes reset.