docs: correct the documented node and pnpm floors

[Rotorsoft]

Closes #1651

The defect

The pnpm 12 / vitest 5 upgrade raised the enforced floor and left the docs behind. Root engines is { node: ">=22.23.2", pnpm: ">=12.3.3" } with packageManager: pnpm@12.3.3, while:

• CLAUDE.md:70 said Node ≥ 22.23.1, pnpm ≥ 11.9.0
• docs/docs/intro.md:102-103 said the same

engines.pnpm is >=12.3.3, so a contributor following either doc and installing pnpm 11.9 hits a hard engine failure at pnpm install. Not merely stale — actively wrong about the supported floor, in the file the AI assistant is told to treat as authoritative for this repo.

What the grep turned up

The ticket's own fix direction said to grep for other copies of the pair, and it found a second surface the ticket hadn't named: every lib README's Compatibility section understates its own package's engines.node.

	engines.node	README claimed
act, act-crypto, act-diagram, act-http, act-ops, act-patch, act-pino, act-sqlite, act-tck	>=22.23.2	>=22.18.0
act-pg	>=22.23.2	>=22.23.1

That one matters more than the contributor-facing lines: it is a published claim about what a consumer of the package needs, so it is wrong for readers of the package rather than just for people working in the repo. All ten now match their own engines.

Fixed inline rather than deferred, per the doc-audit rule in CLAUDE.md ("Hits get fixed inline; do not leave them for a 'follow-up PR'").

Deliberately left alone

• docs/versioned_docs/version-1.x/intro.md — a frozen snapshot of what the released 1.x line required. Rewriting it would make the versioned docs lie about the version they document.
• libs/act-pg/PERFORMANCE.md:326 — records the Node version a past benchmark actually ran on. That is a measurement record, not a requirement.
• .claude/skills/scaffold-act-app/monorepo-template.md:22 — the template a scaffolded user app declares (node >=22.18.0, pnpm >=10.32.1). Different audience and a different decision from this repo's own floor, so out of scope here. Worth a look separately though: a generated app declaring node >=22.18.0 permits a Node that @rotorsoft/act (>=22.23.2) does not, which is a latent inconsistency rather than an immediate break.

Note on the guard

Nothing verifies these values — check:readmes checks section presence, not content. This is the same gap #1650 records for documented export names. Not addressed here; flagging it since it is why both drifted.

Gates

Lint and typecheck clean (run serially — running four pnpm gates concurrently races an esbuild postinstall in this environment, which is not a repo fault). Full suite: 238 files, 3719 passed, 54 skipped.

pnpm check:readmes reports one failure, libs/act-sse: README.md missing — pre-existing and not from this change. libs/act-sse/ is an untracked local leftover containing only dist/ and node_modules/ from the removed package; it is absent from git, so a clean CI checkout is unaffected. Confirmed by stashing this branch's changes and re-running on master, where it fails identically.

Docs only — no book note, no charter surface, no code touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QPx2Qu7ZHDTSpoWYJvX4RJ

[github-actions]

🎉 This PR is included in version @rotorsoft/act-diagram-v1.1.0 🎉

The release is available on:

• @rotorsoft/act-diagram-v1.1.0
• GitHub release

Your semantic-release bot 📦🚀