fix: relax docs site Node.js engine constraint to >=24

[thomhurst]

Summary

• Renovate PR chore(deps): update node.js to v24 #5264 bumped engines.node in docs/package.json to >=24.14.1, but GitHub Actions runners with setup-node@v6 and node-version: 24 only have 24.14.0 available
• This caused the "Test Deploy to GitHub Pages" CI job to fail with an incompatible engine error
• Relaxed the constraint to >=24 since a strict patch-level pin is unnecessary for the docs site build

Test plan

• Verify "Test Deploy to GitHub Pages" CI job passes

[claude]

Code Review: Relax docs site Node.js engine constraint to >=24

Summary

This is a single-line fix in docs/package.json that changes the Node.js engine requirement from >=24.14.1 (set by Renovate in #5264) back to >=24. The root cause is that the GitHub Actions runner installs Node 24 via setup-node@v6 with node-version: 24, which resolves to 24.14.0 — one patch version below what Renovate pinned.

---

Verdict: Approve ✓

The fix is correct and appropriate. The patch-level pin >=24.14.1 was overly strict for a documentation build tool. The engines field in package.json is a compatibility signal, not a security boundary — requiring any Node.js 24.x release is sensible; requiring a specific patch version creates unnecessary fragility.

---

Potential Follow-up Concerns

1. Renovate will try to pin this again

Unless Renovate is configured to ignore the engines.node field in docs/package.json, it will re-introduce a strict patch pin the next time a new Node.js 24.x patch is released, causing the same CI breakage. Consider adding a Renovate rule to prevent over-pinning of the engines field:

{
  "packageRules": [
    {
      "matchFiles": ["docs/package.json"],
      "matchDepTypes": ["engines"],
      "enabled": false
    }
  ]
}

This is the more important follow-up — without it, this fix will need to be repeated after every Node.js patch release.

2. CI and package.json engines are now decoupled (minor drift risk)

Both workflow files pin node-version: 24 without specifying a patch. The engines field now says >=24. These will naturally drift over time. A longer-term improvement would be using a .node-version or .nvmrc file as a single source of truth and referencing it from both the workflows and package.json, but this is not required for this fix.

3. setup-node@v6 usage

Both workflows use actions/setup-node@v6. Worth confirming this is intentional — the currently widely-used major version is @v4. Unrelated to this PR but noticed during review.

---

Overall this is a clean, minimal, and correct fix. The Renovate config update is the only actionable follow-up to prevent recurrence.