[Bounty: $80] Align Node.js version claims across README, runtime-requirements docs, package engines, and CI

[sadiquhammedabubakar-art]

Context
Node version claims disagree across the repo. package.json declares engines.node >= 20.0.0; .github/workflows/ci.yml runs the test matrix on Node 20, 22, and 24; the README "Requirements & Compatibility" section says CI runs against Node 20 and 22; and docs/runtime-requirements.md claims a minimum of Node.js 18 (LTS) and "Tested: Node.js 18, 20, 22, 24". tests/ci-matrix-node24.test.ts pins parts of this, so the drift is verifiable.

Proposed Change
Pick the supported baseline (Node >= 20 per engines) and update README.md, docs/runtime-requirements.md, and any CI/version test expectations to one consistent statement (minimum, recommended, and the CI matrix of 20/22/24).

Acceptance Criteria

• No doc or test claims Node 18 as supported when engines require >= 20.
• README CI-matrix wording matches .github/workflows/ci.yml.
• docs/runtime-requirements.md and package.json engines agree.

Suggested Label (documentation)

ETA: 24 hours

[Aming9303]

I'd like to take this. I'll make the Node support statement consistent across package engines, CI, README, runtime docs, and the version assertions, then run the focused documentation/version checks.

[Jashandeep5911]

Hi, I would like to work on this bounty. Before I begin, could you confirm that it is still unclaimed, the exact acceptance criteria, and how the $80 payment is issued to a contributor in India?

[Zhiyilang074811]

PR submitted: #545

Wallet: 3rb3NNaU5foZFvVk4faVuMmqMvoxfADW3Xw5Wv5vfZr6