Tokens as a unit people can feel: files, runs, issues and pulls carry a token count the way storage carries MB and GB #554

I brought the branch up to date with main so the token-count work can be reviewed and land. Nothing about the feature itself changed.

Why it was parked. The test list in forge.json's check.run is one line. Almost every pull edits that line, so a pull with a new test conflicts with main every time someone else adds one. This is what parked #526 twice.

What changed.

• forge.json: I took main's list as it stands (which adds map-closing) and put tokens back after usage.
• Second merge: main moved again while the check was running, adding the fleet graph (#553). That second merge needed no manual fixes. #553 did not add fleet-graph to the check list, so this pull doesn't either.

Tests. The full check.run passed on the first merge: typecheck, then 728 tests across 52 files, 0 failures. After the second merge, the typecheck and test/tokens.test.ts plus test/fleet-graph.test.ts pass; the full check did not run again.

What I chose not to do. I didn't split #403 or rewrite what done looks like. The work is finished and reviewed; only the merge was stuck. The likely conflict next time is the same line, and resolving it is the same edit: take main's list and add tokens. A follow-up that lets the check find test files itself, instead of listing them, would stop this for every pull. That should be its own issue.

How to try it. On the preview, open any issue, pull, file view or run page. Each one shows a token count next to its size, the way storage shows MB and GB.

🤖 Generated with Claude Code

Closes #403

I merged main (now at #552) into the branch so #554 merges cleanly again; the token-count feature itself is unchanged. The full check passed: typecheck, then 771 tests across 56 files with no failures. main hadn't moved again by the time of the push.

The conflict. It was the same one line as last time: the test list in forge.json's check.run. #552 added review-route, review-lines, review-gate and board to that list. I took main's list as it is and put tokens back after usage. Nothing else conflicted, including src/web/pages/board.ts.

What I chose not to do. This line will conflict again whenever another pull adds a test, and the fix will be the same edit. A follow-up that lets the check find test files itself, instead of listing them in forge.json, would stop this for every pull. That belongs in its own issue, not this one.

How to try it. On the preview, open any issue, pull, file view or run page. Each one shows a token count next to its size, the way storage shows MB and GB.

🤖 Generated with Claude Code