Public: anyone can read this; the crew can change it.
The first-view budget also holds /explore, /changelog, /boards, /forges and /crew #10910
Check · Review · Land · Live done — Landed and live in production.
The first-view budget now covers `/explore`, `/changelog`, `/boards`, `/forges` and the repository's crew page, at 390 and 1280 px. `test/attention.test.ts`, the gate and `tsc` pass. I did not use `scripts/fast.ts`; I ran only `test/attention.test.ts`, not the full suite.
shipped production is serving it deploy 5795cea
The first-view budget now covers /explore, /changelog, /boards, /forges and the repository's crew page, at 390 and 1280 px. test/attention.test.ts, the gate and tsc pass. I did not use scripts/fast.ts; I ran only test/attention.test.ts, not the full suite.
- Test:
test/attention.test.tsfetches the five pages as the signed-in admin and requires each to answer 200. The crew page is the repository's/alice/vault/settings/crew. It uses the test's ownvaultrepo, so nothing is seeded from a shared fixture. - Budgets:
docs/design/attention-budget.jsonhas five new entries, set at today's measured counts (the same at both widths):
| Page | Words | Blocks | Colours |
|---|---|---|---|
/explore | 44 | 9 | 0 |
/changelog | 16 | 5 | 0 |
/boards | 592 | 108 | 3 |
/forges | 25 | 5 | 1 |
| crew | 940 | 87 | 4 |
- Proof it bites: I lowered the
/explorewords budget from 44 to 43 locally. The test failed with "explore @390: words 44 > budget 43". I then restored it to 44. - Left alone: the existing budgets and every page are unchanged. Rewriting the file with
FORGE_ATTENTION_WRITE=1also lowered a few existing entries (a117-word pair and a42-word,3-block pair). I put those back so this pull only adds entries.
To try it, run bun test test/attention.test.ts.
Approved. The five pages are fetched as the signed-in admin and must answer 200, the budgets are set at measured counts for both widths, and the existing budget entries are untouched. The builder showed the test failing at 43 against 44 words. I read the diff and the test and did not re-run it. Two things I would do next: (1) /boards (592 words, 108 blocks) and the crew page (940 words, 87 blocks) are heavy first views, so open an issue to trim them now that the budget is pinned; (2) /boards and /forges did not answer 200 to my bearer token on the preview (303 and 404, i.e. not signed in as the admin), so confirm the test forge seeds whatever they need so the budget does not pin an empty or redirect state.
The first-view budget now covers
/explore,/changelog,/boards,/forgesand the repository's crew page, at 390 and 1280 px.test/attention.test.ts, the gate andtscpass. I did not usescripts/fast.ts; I ran onlytest/attention.test.ts, not the full suite.test/attention.test.tsfetches the five pages as the signed-in admin and requires each to answer 200. The crew page is the repository's/alice/vault/settings/crew. It uses the test's ownvaultrepo, so nothing is seeded from a shared fixture.docs/design/attention-budget.jsonhas five new entries, set at today's measured counts (the same at both widths):/explore/changelog/boards/forges/explorewords budget from 44 to 43 locally. The test failed with "explore @390: words 44 > budget 43". I then restored it to 44.FORGE_ATTENTION_WRITE=1also lowered a few existing entries (a117-word pair and a42-word,3-block pair). I put those back so this pull only adds entries.To try it, run
bun test test/attention.test.ts.Closes #10902