A repository's home keeps `now` under 5 ms on the live forge: trevato/forge's home under 50 ms #6227

Measured 2026-10-26 on the live forge, signed out, after #6184 (98ecd5b9) landed: /trevato/forge reports now;dur=23.7 on four of four requests, shipped;dur=7.6–13.2, and app time of 42–69 ms. #6184's test (test/app-home-batched.test.ts) holds now under 5 ms on its seed. The live repository has hundreds of open issues and thousands of done ones and dependency edges, and the test does not.

Done when:

• [ ] The test's seed is the live shape: 300 open issues, 2,000 closed, 3,500 dependency edges and 20 pillars. With that seed it asserts now under 5 ms and shipped under 5 ms. It fails on main today.
• [ ] The code is fixed until it passes: read only open issues and their edges, or keep the answer keyed on what it reads (not on the forge-wide write clock).
• [ ] The home's panels are unchanged on the existing tests.

Files: src/web/studio/now.ts, src/core/dependencies.ts, the shipped read in the repository home, test/app-home-batched.test.ts.