chore!: require Node 26

[faraa2m]

Summary

• Require Node.js 26 locally via engines and .nvmrc.
• Run CI, release, registry, and automation workflows on Node 26.
• Move the published JavaScript Action runtime to GitHub Actions' latest supported Node runtime, node24.
• Add a major Changesets entry for the published runtime packages.

Verification

• fnm exec --using 26 npm run lint
• fnm exec --using 26 npm run typecheck
• fnm exec --using 26 npm test
• fnm exec --using 26 npm run build
• fnm exec --using 26 npm run build -w @tokenometer/action
• JSON/YAML parse checks
• git diff --check

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tokenometer	Error		May 19, 2026 2:11pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ef6d2cb04d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add Node engine to published packages

This only updates the private workspace root, so npm consumers of the packages being major-bumped here still receive package manifests without a Node 26 engine requirement: packages/cli/package.json, packages/core/package.json, packages/mcp/package.json, and packages/react/package.json do not declare engines.node. Because npm publishes each workspace's own package.json, installing tokenometer or @tokenometer/* on Node 20/22 will not warn or reject even though the release notes say these packages now require Node 26.

Useful? React with 👍 / 👎.