docs: trivial lede edit + verify changesets + auto-major-tag-mover

[faraa2m]

Trivial README copy edit ("CI cost-guardrail" → "CI cost guardrail") plus a patch changeset for `tokenometer` to verify the changesets + auto-major-tag-mover pipeline end-to-end.

After merging this PR

1. Push to main fires the existing `release` workflow
2. Bot sees the changeset and opens a "Version Packages" PR proposing v1.1.0 → v1.1.1
3. Merging that follow-up PR:
   • Bumps `tokenometer` (and any `fixed`-linked packages) to v1.1.1
   • Publishes to npm
   • Cuts the v1.1.1 GitHub Release
   • Fires the new `update-major-tag.yml` workflow which force-moves `v1` from current commit to v1.1.1's commit (with the backwards-move safety guard preventing regression)
4. Marketplace consumers on `@v1` get the updated runtime automatically — no manual `git tag -f v1 && git push --force` needed

Safe to merge

This PR by itself is a docs edit. The actual version bump only happens when you merge the Version Packages PR that the changesets bot will open after this lands. Until that second merge, no npm publish or tag changes occur.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tokenometer	Ready	Preview, Comment	May 12, 2026 4:55am