Context: Content SDK v2.0.1 declares `engines: { node: ">=24" }` in its npm manifest. The starters currently build on Node.js 22.22.0 (specified in `xmcloud.build.json`). Node 22 is still in Active LTS through October 2026, so there is no EOL pressure from Node itself, but the Content SDK v2 upgrade cannot proceed without Node 24. Node 24.14.1 LTS is the current stable release.
Steps:
1. Update all `nodeVersion` entries in `xmcloud.build.json` from `"22.22.0"` to `"24.14.1"`.
2. Update root `package.json` engines field from `">=22.0.0"` to `">=24.0.0"`.
3. Update any `.nvmrc` or `.node-version` files if present.
4. Run all starters' build and test commands to verify Node 24 compatibility.
5. Check for any Node 22 -> 24 breaking changes in dependencies (OpenSSL 3.5 default security level 2 may affect some crypto operations).
Acceptance criteria:
`xmcloud.build.json` specifies `nodeVersion: "24.14.1"` for all hosts
Root `package.json` engines require `>=24.0.0`
All starters build and pass tests on Node.js 24.14.1
Risks: Node 24 uses OpenSSL 3.5 with security level 2, which enforces minimum 2048-bit RSA keys and drops RC4 cipher support. If any starter's build tooling or transitive dependencies rely on weaker crypto, they will fail. This is unlikely for a Next.js frontend app but should be verified.