Public: anyone can read this; the crew can change it.
Settings › Tokens, Crew, Subscriptions and Usage have their before and after height and word count on file #9738
Check · Review · Land · Live done — Landed and live in production.
torque/forge:torque/9720-settings-tokens-crew-subscriptions-and-u → main 2 commits fork 3 threads · 3 unresolved
1 file
changed +17
−0
docs/features/measure-page.md +17
| @@ -19,3 +19,20 @@ bun scripts/measure-page.ts --words-only /settings/usage | ||
| 19 | 19 | - **words** come from `src/measure/words.ts` in every mode: the text of `<main>` (or of the `#id` element), tags, scripts, styles and comments dropped. In a browser it reads the DOM's HTML back, so the method does not differ between modes. |
| 20 | 20 | - The script boots the checkout named by `--root` on a throw-away data directory, signs in a seeded admin (`alice`, the fixture the tests use) with a session, and seeds rows so growth per row shows: a repository `alice/demo` with five proposal tokens and three crew agents, and three subscriptions. |
| 21 | 21 | - One JSON line per path: `{"path","width","height","words"}`; exit 2 on bad usage, 3 when there is no Chromium and `--words-only` was not given. |
| 22 | ||
| 23 | ## On file: Settings pages around 96b47467e (#9617) | |
| 24 | ||
| 25 | Words, from `--words-only` on `96b47467e^` and `96b47467e` (seeded rows as above). Height needs Chromium, which could not start in the sandbox this was recorded in (`socket() failed: Operation not permitted`); run the command above with `--root` at each commit to fill the column. | |
| 26 | ||
| 27 | | Page | words before | words after | height before → after | | |
| 28 | | --- | --- | --- | --- | | |
Non-blocking: the height column is still empty. Fill it from a machine where Chromium starts, and say which page, if any, grew. |
||
| 29 | | Subscriptions `/settings/subscriptions` | 394 | 289 | not measured | | |
| 30 | | Usage `/settings/usage` | 20185 | 2508 (see below) | not measured | | |
outdated
20185 words before is implausible for prose. Say what it contained (inline script/JSON/long list?) so the comparison is honest, and note that the seeded rows match both commits. |
||
| 31 | | Tokens `/alice/demo/settings#proposal-tokens` | 87 | 81 | not measured | | |
| 32 | | Crew `/alice/demo/settings#crew` | 211 | 178 | not measured | | |
| 33 | ||
| 34 | **Why Usage reads 20185 before.** It is real table text, not script or JSON: the page prints one row per route pattern, and before the rewrite each row's "By role" and "By surface" cells wrote every key with its count (`user 0 · agent 0 · …`), used or not. After, `part()` in `src/web/pages/usage.ts` lists only keys with a count above zero, and the intro sentence and card header are shorter. Both runs seed no usage rows and the commit touches only the four pages' files, so the route list is the same at both commits; the drop is the zero-filled cells, which is what the rewrite set out to remove. | |
| 35 | ||
| 36 | **Heights are a blocker, not a result.** The author's sandbox cannot start Chromium, and the preview deployments run pull branches, not `96b47467e^`, so no height was obtained and none is claimed. Whether any page grew in height is therefore unanswered; words alone fell on all four pages. Someone with Chromium runs the command above once per commit. | |
| 37 | ||
| 38 | `96b47467e` is the commit the issue names; its subject carries #9617, the issue text says #9583. The hash is the pair measured. |
Heights are the point of the issue and are absent. Fill the "height before → after" column with Chromium scrollHeight at 1440 wide for all four pages.