0.45.1 — give the context number its own card, not badge nineteen - #129
Merged
Conversation
0.45.0 published the figure and then buried it: a shields badge sitting second in a row of nineteen, between "MIT License" and "TypeScript 5". Those are table stakes. This is the one number nothing else in the ecosystem publishes, and no amount of colour rescues something in a badge wall. It now sits directly under the install command as a card — figure large, with a reference unit that makes it mean something (6% of a 200K window), the --profile trading alternative at -57%, and the line that does the work: every turn, whether or not you call a tool. The shields badge is retired; the wall is down to eighteen. Generated, never hand-drawn: `npm run brand:card` renders both variants from the live measurement, so the card cannot outlive the number it states. test/schema-tokens.test.ts checks the headline figure, the reference percentage, the trading figure and the saving against a fresh in-process measurement, in BOTH variants — verified by doctoring a card and confirming the build fails. Light and dark are separate SVGs behind <picture>, because an SVG cannot restyle itself from the host page. Relative paths are safe here: raw.githubusercontent now serves SVG as image/svg+xml, so npm's rewriting of relative image URLs renders the card rather than dumping markup. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WUL3ExR4Nz7uebxKaKwjDi
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.45.0 published the context figure and then buried it: a shields badge sitting second in a row of nineteen, between
MIT LicenseandTypeScript 5. Those are table stakes. This is the one number nothing else in the ecosystem publishes. No amount of colour rescues something in a badge wall — the problem was placement, not design.What changed
The figure now sits directly under the install command as a card, which is the highest-attention spot in any README:
6% of a 200K context window. Install-size badges work because everyone knows what 100MB is; tokens have no such intuition yet, and supplying one is the actual brand work--profile tradingalternative at −57%The shields badge is retired. The wall is down to eighteen.
Generated, never hand-drawn
npm run brand:cardrenders both variants from the live measurement, so the card cannot outlive the number it states.test/schema-tokens.test.tschecks the headline figure, the reference percentage, the trading figure and the saving against a fresh in-process measurement — in both variants, since a dark-mode reader sees a different file. Verified by doctoring a card and confirming the build fails.Light and dark are separate SVGs behind
<picture>: an SVG cannot restyle itself from the host page's colour scheme, so a single file would show a white card on a dark README.One thing I checked rather than assumed
Relative paths are safe here.
raw.githubusercontent.comnow serves SVG asimage/svg+xml(it historically servedtext/plain, which would have rendered as broken markup), so npm's rewriting of relative image URLs displays the card correctly on npmjs.com too. No PNG fallback needed.Verification
sync-brand-numbers --checkclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01WUL3ExR4Nz7uebxKaKwjDi