docs/design/audit.md says, for every top-level page, what it is for and what is wrong with it against DESIGN.md #2725

docs/design/audit.md now has one entry for each of the 65 top-level pages, and a new test keeps it in step with the router. test/design-audit.test.ts and test/design-lint.test.ts pass. I did not run the full suite or the type check. The test also failed when I added a fake /ghost route and removed /flow, so it does catch both kinds of drift.

What changed

• Per-page entries: each entry gives the route, the module that renders it, what it is for, what duplicates it, and what breaks DESIGN.md.

- "Breaks" is the colour and off-scale font-size counts from docs/design/baseline.json, per module. - The entries replace the old Finding 2 table, which listed a /settings/spend route that doesn't exist (spend is a table module shared by the subscriptions page and the board). - The 65 are every static GET route in src/http/server.ts that returns a page. /audit.csv, /fleet/graph/live, /fleet/graph.csv and /settings/origins/callback are listed as machine routes and have no entry.

• Closing sections:

- "Merge or retire" follows #2692–#2696 and adds four merges I noticed that no issue covers yet: people into accounts, family into forges, tokens and keys into one credentials page, and deleting /big. - "What the clean app template does better" is about src/apps/scaffold.ts.

• Test: every static page route in the router has an entry, every entry is a registered route, and no entry appears twice.

Left out

• No screenshots, so the audit says nothing about how pages look. "None seen" means the design lint found nothing in the module, not that anyone looked at the page. That sweep is #2690.
• The /:owner/:name/* repository pages are not listed one by one. The repo header and tabs already unify them.
• "What duplicates it" and "what it is for" are read from each module's header comment and the router, not from using the pages.

To check: bun test test/design-audit.test.ts.

Closes #2709

docs/design/audit.md now has one entry for each of the 65 top-level pages, and a new test keeps it in step with the router. test/design-audit.test.ts and test/design-lint.test.ts pass. I did not run the full suite or the type check. The test also failed when I added a fake /ghost route and removed /flow, so it does catch both kinds of drift.

What changed

• Per-page entries: each entry gives the route, the module that renders it, what it is for, what duplicates it, and what breaks DESIGN.md.

- "Breaks" is the colour and off-scale font-size counts from docs/design/baseline.json, per module. - The entries replace the old Finding 2 table, which listed a /settings/spend route that doesn't exist (spend is a table module shared by the subscriptions page and the board). - The 65 are every static GET route in src/http/server.ts that returns a page. /audit.csv, /fleet/graph/live, /fleet/graph.csv and /settings/origins/callback are listed as machine routes and have no entry.

• Closing sections:

- "Merge or retire" follows #2692–#2696 and adds four merges I noticed that no issue covers yet: people into accounts, family into forges, tokens and keys into one credentials page, and deleting /big. - "What the clean app template does better" is about src/apps/scaffold.ts.

• Test: every static page route in the router has an entry, every entry is a registered route, and no entry appears twice.

Left out

• No screenshots, so the audit says nothing about how pages look. "None seen" means the design lint found nothing in the module, not that anyone looked at the page. That sweep is #2690.
• The /:owner/:name/* repository pages are not listed one by one. The repo header and tabs already unify them.
• "What duplicates it" and "what it is for" are read from each module's header comment and the router, not from using the pages.

To check: bun test test/design-audit.test.ts.

I made both changes and pushed. test/design-audit.test.ts and test/design-lint.test.ts pass. I did not run the full suite or the type check.

• Duplicate section: I deleted the trailing "What the clean app template does better" section. Its one new fact is now in Finding 3: the template's stylesheet uses only token words (font-size: var(--text-sm), no literals) and is linked by content hash with a year of cache.
• Page count: the prose now says "There are 59 top-level pages". The test reads that number from the doc and requires it to equal both the number of pages in the router and the number of entries. A drifting number in the prose now fails the test.
• My earlier "65" was wrong: the audit text never stated 65, only my pull description did. The real count is 59, which is the number the doc and test now use. The entries themselves are unchanged.