Settings › Tokens, Crew, Subscriptions and Usage have their before and after height and word count on file #9720

For: the box #9662 left open. Show with numbers that the rewrite in 96b47467e (#9583) made each of the four pages shorter. Do not redo the pages.

Done looks like:

• [x] scripts/measure-page.ts <path> prints a page's rendered height at 1440 wide (Chromium document.documentElement.scrollHeight) and the word count of the text in main. It signs in with the admin fixture the tests already use, so later design-pass pulls can reuse it.
• [ ] The pull has a table with the height and word count of each of the four pages at 96b47467e^ and at 96b47467e.
• [ ] If any page is not lower after, the pull says which page and what grew. File nothing else and change no page here.
• [x] bun test passes.

Files: scripts/measure-page.ts, plus a line in the README or docs/DESIGN.md's tooling notes saying how to run it. Risks: the script is tooling, not runtime, so it must not be imported from src/. If Chromium is missing where it runs, it says so and exits non-zero, without guessing.

Reviewed pull #9738 at its head: ticked scripts/measure-page.ts <path> prints a page's rendered height at 1440 wide (Chromium document.documentElement.scrollHeight) and the word count of the text in main. It signs in with the admin fixture the tests already use, so later design-pass pulls can reuse it.; bun test passes.. left open: The pull has a table with the height and word count of each of the four pages at 96b47467e^ and at 96b47467e. — The word counts are filed, but every height cell says not measured because Chromium would not start.; If any page is not lower after, the pull says which page and what grew. File nothing else and change no page here. — Without heights it cannot be said whether any page grew. Words fell on all four, but height is the measure the box asks for..

Left open after pull #9738 landed: 2 unticked items remain (The pull has a table with the height and word count of each of the four pages at 96b47467e^ and at 96b47467e.; If any page is not lower after, the pull says which page and what grew. File nothing else and change no page here.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Closed by the planner: scripts/measure-page.ts and the word counts landed in #9738. The heights need Chromium, which the crew's sandboxes lack, so re-filing would hand a builder work it cannot do. A person can run scripts/measure-page.ts where Chromium is present.

Correction to the comment above: not closed, deferred behind #594. A person's ask stands in this issue, so the planner does not drop it, and its open boxes need a browser the crew's sandboxes lack. A person ticks them by eye (or runs the tool where Chromium is present) and closes it.

Correction: not deferred either. #594 already waits on this pillar chain, so the dependency would loop. It stays open, held for a person: its open boxes need a browser the crew's sandboxes lack, so no builder is handed it. A person ticks them by eye and closes it.