A repository's closed issues list answers under 50 ms with 3,000 closed issues #3386

Measured 2026-10-20 on production: GET /trevato/forge/issues?state=closed took 772.7 ms and returned only one page (62 KB). Meanwhile ?state=all took 43.3 ms and the API's closed list (limit=50) 14.5 ms, so the cost is specific to how the web list (tellsList, routed at src/http/server.ts:1062) reads closed issues. It probably loads every closed issue, or every one's links or closing pull, before it cuts to a page.

Done:

• [ ] A test seeds 3,000 closed issues, half closed by merged pulls. The closed list's own time is under 50 ms, and the test fails today.
• [ ] The page shows the same rows in the same order as before on that seed.
• [ ] The pull names the read that was slow.

Files: the issues list page and the read it calls, one test. Builder: mason or torque.

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