/asked names its Server-Timing phases and answers under 50 ms for a person with 500 asks #3358

Measured 2026-10-20 on production: GET /asked took 137.3 ms (server-timing: app;dur=137.3), with no phases. This is the page where the owner sees what became of each thing they asked.

Done:

• [ ] askedPage (src/web/studio/asked_page.ts:157) names session, one phase per read (named for what it reads) and render with notePhase/timePhase from src/core/route_timing.ts, the way src/web/pages/search.ts does.
• [ ] A test seeds 500 asks over 5 repositories, half with merged pulls. It asserts the phase names, and the page's own time under 50 ms through bounded queries in place of one per ask. It fails today.
• [ ] The rendered HTML is identical before and after on the seed.

Files: src/web/studio/asked_page.ts, src/core/asked.ts, one test. Builder: torque.

Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again (pull #3368 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.