Require Node 24 in devEngines so it matches the npm >=11 requirement

[t-hamano]

Related issues

• None — found while setting up a local dev environment.

How AI was used in this PR

Claude Code investigated the failing npm install, traced it to the contradiction between the two devEngines constraints, and made the one-line change. I reviewed the reasoning and confirmed the resulting Node/npm resolution locally.

Proposed Changes

The two devEngines constraints contradict each other: runtime allows Node 22, but Node 22 bundles npm 10.9.x, which can never satisfy packageManager: ">=11.0.0". A contributor whose version manager honours the declared runtime floor is blocked from installing at all, with an EBADDEVENGINES error that blames npm rather than Node. Meanwhile, .nvmrc pins 24.15.0.

Testing Instructions

1. Check out this branch and make sure your version manager picks up the change.
2. node -v should report 24.x, and npm -v should report 11.x.
3. npm install should complete without EBADDEVENGINES.

To see the original failure, switch to trunk with a version manager that reads devEngines (or run npm install under Node 22) — the install aborts with the error above.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[sejas]

@t-hamano , thanks for creating this PR. The change looks good to me. We could even specify the version 24.15.0 which lives in .nvmrc.

@fredrikekelund, I would like to know your opinion about increasing the devEngines node runtime version in package.json.