With 500 leads on the desk, the desk, a lead's page, the week report and the due page still answer in under 50 ms, and a test proves it #103

For: the app has grown many features; a working agent has hundreds of leads, not the handful in the sample. Nothing checks it stays fast.

Done looks like:

• [ ] A test seeds 500 leads with drafts, follow-ups, showings, notes and some lost/qualified, then renders /, a lead's page, /report and the due-today page, and asserts each renders in under 50 ms (median of a few runs, with a generous margin for CI noted in the test).
• [ ] Any page over budget is fixed: indexes added in src/db.ts migrations for the columns the desk and report filter and sort on, and no per-lead query inside a loop over leads (N+1) on these pages.
• [ ] The desk paginates or caps what it lists when it is long (e.g. the 50 most pressing, with a link to the rest) so the first paint stays small; search still finds any lead.
• [ ] bun test passes; README notes the size the app is tested at.

Files likely: src/db.ts, src/pages/desk.ts, src/report.ts, src/leads.ts, a new src/scale.test.ts. Risk: timing tests are flaky; measure render functions directly against an in-process db rather than over the network.