fix: standardize Node.js minimum version to 22.16

[cv]

Summary

• Docs, installers, and agent skills all referenced Node.js 20 as the minimum while package.json engines required >=22. This aligns everything to >=22.16.0 to match the OpenClaw runtime requirement.
• Bumps engines in both package.json files to >=22.16.0
• Bumps MIN_NODE_MAJOR from 20 to 22 in both installer scripts and removes the now-redundant "recommended" distinction
• Updates README, CONTRIBUTING, troubleshooting docs (both copies), and get-started skill
• Bumps @types/node from ^20 to ^22

Test plan

• Verify npm install succeeds on Node 22.16+ — clean install on Node 25.4.0
• Verify npm install --engine-strict rejects Node 20 — EBADENGINE: Required: {"node":">=22.16.0"}, Actual: v20.20.1
• Run install.sh on a machine with Node 20 and confirm it rejects with a clear error — Unsupported runtime detected: Node.js v20.20.1... NemoClaw requires Node.js >=22
• Grep for stale "Node.js 20" references — no matches

Evidence

npm install --engine-strict on Node 20 (via docker run node:20-slim):

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: nemoclaw@0.1.0
npm error notsup Required: {"node":">=22.16.0"}
npm error notsup Actual:   {"npm":"10.8.2","node":"v20.20.1"}

install.sh on Node 20 (via docker run node:20-slim):

[INFO]  Node.js found: v20.20.1
[ERROR] Unsupported runtime detected: Node.js v20.20.1, npm 10.8.2. NemoClaw requires Node.js >=22 and npm >=10. Upgrade Node.js and rerun the installer.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Updated minimum Node.js requirement from 20 to 22.16 across docs, README, and contributor guides.
  • Revised troubleshooting guidance and nvm examples to reference Node.js 22.16.

• Chores

  • Enforced Node.js >=22.16.0 as the minimum runtime in installer messages and runtime checks.
  • Switched installer/runtime validation to exact semver checks and updated tests/fixtures to match the new requirement.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Node.js minimum requirement raised to 22.16.0 across docs, installer scripts, package configs, and tests. Installer scripts now perform semantic-version comparisons (added version_gte) and removed the separate “recommended” version constant; TypeScript Node typings bumped to ^22.

Changes

Cohort / File(s)	Summary
Documentation Prerequisites README.md, CONTRIBUTING.md, .agents/skills/nemoclaw-get-started/SKILL.md	Updated Node.js minimum from 20 to 22.16.0 in prerequisites and contributor guidance.
Troubleshooting Guides docs/reference/troubleshooting.md, .agents/skills/nemoclaw-reference/references/troubleshooting.md	Adjusted documented Node.js minimum to 22.16.0; updated nvm examples from nvm install 20/nvm use 20 to nvm install 22/nvm use 22 and threshold text.
Installer Scripts install.sh, scripts/install.sh	Replaced major-only check (MIN_NODE_MAJOR=20) with semver minimum (MIN_NODE_VERSION="22.16.0"); removed RECOMMENDED_NODE_MAJOR; added version_gte() to compare semver and reject prerelease; updated runtime validation, messages, and nvm install/use target to 22.
Package Configuration package.json, nemoclaw/package.json	Tightened engines.node to >=22.16.0; bumped @types/node devDependency from ^20.19.37 to ^22.0.0.
Tests test/install-preflight.test.js	Updated faked Node.js runtime versions to v22.16.0 and updated expected runtime message to Node.js >=22.16.0 and npm >=10.

Sequence Diagram(s)

sequenceDiagram
  participant User as User
  participant Installer as Installer script
  participant NVM as nvm
  participant Node as Node.js runtime
  participant NPM as npm

  User->>Installer: run install.sh
  Installer->>Node: node -v (detect version)
  alt prerelease suffix detected
    Installer-->>User: reject version (prerelease not allowed)
  else
    Installer->>Installer: version_gte(node_version, MIN_NODE_VERSION)
    alt version >= 22.16.0
      Installer->>NPM: npm -v (detect npm)
      alt npm_major >= 10
        Installer->>User: proceed
      else
        Installer-->>User: error "npm >=10" required
      end
    else
      Installer->>NVM: nvm install 22 / nvm use 22
      NVM->>Node: install/select Node 22.x
      Installer->>Node: node -v (verify)
      Installer->>User: success or further instructions
    end
  end

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Poem

🐰 I hopped through docs and scripts today,
Bumped Node to twenty-two point one six — hooray!
Semver checks now tidy and spry,
Tests and packages all hopped in line,
Carrots and code both feel just fine. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 60.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: standardizing the Node.js minimum version to 22.16 across the repository.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/node-version-consistency

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@install.sh`:
- Around line 190-193: The runtime check currently compares only major Node
version via MIN_NODE_MAJOR, allowing Node 22.0.0–22.15.x to pass; change the
check to use the existing version_gte() helper to compare the full Node semver
string against "22.16.0" (e.g. derive node_version from `node -v` and call
version_gte "$node_version" "22.16.0"), update the requirement constant/message
to a full semver (e.g. set MIN_NODE_VERSION="22.16.0" and update
RUNTIME_REQUIREMENT_MSG to mention Node.js >=22.16.0), and remove or stop
relying on the old MIN_NODE_MAJOR comparison so the installer enforces the same
engines.node >=22.16.0 requirement as package.json.

In `@scripts/install.sh`:
- Around line 129-132: The installer currently only enforces MIN_NODE_MAJOR and
compares node_major (and checks current_major == "22"), which allows Node
22.0–22.15 despite package.json requiring >=22.16.0; update the script to use a
MIN_NODE_VERSION (e.g., "22.16.0") and parse the current Node version into
major, minor, patch (from the node --version string) and perform a proper
semantic comparison (compare major, then minor, then patch) instead of only
comparing node_major or checking current_major; replace any hardcoded checks
that use current_major == "22" with a full-version check against
MIN_NODE_VERSION and adjust RUNTIME_REQUIREMENT_MSG to reflect the full required
version.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 199f81d2-3315-4eeb-8eb6-da0364028d5f

📥 Commits

Reviewing files that changed from the base of the PR and between bb8ba78 and b07b4a0.

⛔ Files ignored due to path filters (1)

• nemoclaw/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• .agents/skills/nemoclaw-get-started/SKILL.md
• .agents/skills/nemoclaw-reference/references/troubleshooting.md
• CONTRIBUTING.md
• README.md
• docs/reference/troubleshooting.md
• install.sh
• nemoclaw/package.json
• package.json
• scripts/install.sh

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

test/install-preflight.test.js (1)

61-105: Add a 22.15.x regression case.

Line 61 still fails with both Node and npm below floor, so it verifies the message text but not the new Node-only semver boundary. A case like v22.15.9 with npm 10.9.2 would catch any regression back to a major-only check.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/install-preflight.test.js` around lines 61 - 105, Add a new test case
similar to the existing "fails fast with a clear message on unsupported Node.js
and npm" that specifically exercises the Node-only semver boundary: create a
temporary fake bin where "node" --version prints "v22.15.9" and "npm" --version
prints "10.9.2", run the installer the same way as the current test, assert the
process exits non-zero, and assert the output contains the same Unsupported
runtime message plus the printed Node and npm versions (e.g., match /v22\.15\.9/
and /10\.9\.2/) to prevent regressions where only major version is checked; use
the same helper functions (writeExecutable, spawnSync) and test harness
structure as the existing it("fails fast...") block.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@scripts/install.sh`:
- Around line 129-131: The manual-install fallback message currently tells users
to install “Node.js 22” but should reference the declared minimum version to
avoid mismatch; update the fallback string to use the MIN_NODE_VERSION variable
(or RUNTIME_REQUIREMENT_MSG) instead of the hardcoded “Node.js 22” so the
last-resort guidance matches the preflight MIN_NODE_VERSION setting.
- Around line 172-183: The version_gte() function should validate that each
semver token is strictly numeric before doing arithmetic to avoid crashes on
prerelease strings like "0-rc"; add a regex check after the IFS.read -ra a/b
step to ensure all tokens in arrays a and b match ^[0-9]+$ (or otherwise that
a[0..2] and b[0..2] are numeric), and if not call fail() with a clear error
about unsupported non-numeric semver (so the script exits via fail() instead of
hitting an arithmetic error).

---

Nitpick comments:
In `@test/install-preflight.test.js`:
- Around line 61-105: Add a new test case similar to the existing "fails fast
with a clear message on unsupported Node.js and npm" that specifically exercises
the Node-only semver boundary: create a temporary fake bin where "node"
--version prints "v22.15.9" and "npm" --version prints "10.9.2", run the
installer the same way as the current test, assert the process exits non-zero,
and assert the output contains the same Unsupported runtime message plus the
printed Node and npm versions (e.g., match /v22\.15\.9/ and /10\.9\.2/) to
prevent regressions where only major version is checked; use the same helper
functions (writeExecutable, spawnSync) and test harness structure as the
existing it("fails fast...") block.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ff88fffc-8786-4320-a345-782ada6695ca

📥 Commits

Reviewing files that changed from the base of the PR and between b07b4a0 and ababcb3.

📒 Files selected for processing (3)

• install.sh
• scripts/install.sh
• test/install-preflight.test.js

🚧 Files skipped from review as they are similar to previous changes (1)

• install.sh

[coderabbitai]

🧹 Nitpick comments (1)

install.sh (1)

323-326: Consider pinning to 22.16 for explicit minimum version alignment.

Using nvm install 22 installs the latest 22.x, which is typically fine since ensure_supported_runtime() validates afterward. However, if a user has a stale nvm cache, they might get an older 22.x version (< 22.16.0), causing the installer to fail at the validation step with a confusing error.

Pinning to 22.16 would make the minimum requirement explicit and provide a clearer failure mode if the version isn't available.

♻️ Optional: Pin to minor version

-  spin "Installing Node.js 22..." bash -c ". \"$NVM_DIR/nvm.sh\" && nvm install 22 --no-progress"
+  spin "Installing Node.js 22.16..." bash -c ". \"$NVM_DIR/nvm.sh\" && nvm install 22.16 --no-progress"
   ensure_nvm_loaded
-  nvm use 22 --silent
+  nvm use 22.16 --silent

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@install.sh` around lines 323 - 326, Update the Node install steps to pin to
the minimum 22.16 release instead of the floating 22 major; change the
invocations that call nvm to use "22.16" (the spinner call that runs nvm
install, and the subsequent nvm use --silent) so the script explicitly requests
the minimum supported minor version and avoids pulling an older 22.x from a
stale cache; keep existing helpers (spin, ensure_nvm_loaded, info) and flags
(--no-progress / --silent) intact when making this change.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@install.sh`:
- Around line 323-326: Update the Node install steps to pin to the minimum 22.16
release instead of the floating 22 major; change the invocations that call nvm
to use "22.16" (the spinner call that runs nvm install, and the subsequent nvm
use --silent) so the script explicitly requests the minimum supported minor
version and avoids pulling an older 22.x from a stale cache; keep existing
helpers (spin, ensure_nvm_loaded, info) and flags (--no-progress / --silent)
intact when making this change.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f3f4d314-4bb0-48e0-876f-cc2c094476ca

📥 Commits

Reviewing files that changed from the base of the PR and between 34ccd79 and 921903a.

📒 Files selected for processing (1)

• install.sh