Fix installer Node runtime mismatch

[rolandkakonyi]

Summary

• Problem: install.sh can leave openclaw bound to an older node (for example nvm Node 20), even after installing Node 22.
• Why it matters: users finish install successfully but openclaw immediately fails with openclaw requires Node >=22.12.0.
• What changed:
  • Added Node runtime selection logic to prefer/activate a supported Node (>=22) for installer operations.
  • Added a compatibility shim step for npm installs that writes an openclaw launcher using the selected Node 22 runtime when original shell PATH still points to unsupported Node.
  • Added a hard guard in install flow to fail early if Node 22 cannot be activated.
• What did NOT change: no changes to package contents in openclaw itself; this PR only updates installer behavior in openclaw.ai.

Linked Issue/PR

• Related: [Bug]: CLI unusable when multiple Node versions are present openclaw#21126

Verification

• Reproduced failure in Docker (ubuntu:24.04) with nvm Node 20 active before running installer.
• Re-ran same repro against patched local install.sh:
  • installer now reports Using Node.js runtime at /usr/bin/node
  • shim created in original node bin dir
  • openclaw --version succeeds
  • openclaw config set gateway.mode local succeeds
• Ran shellcheck -s bash public/install.sh after changes (clean).

Risk / Rollback

• Risk: wrapper shim placement could surprise users with custom PATH setups.
• Mitigation: shim is only created when original PATH does not provide supported Node; otherwise no shim is written.
• Rollback: revert this PR to restore previous installer behavior.

AI-Assisted Contribution

• Agent/tool: GPT-5.3-Codex (High reasoning)
• Intent summary:
  • Reproduce issue #21126 with Docker + nvm Node 20 environment.
  • Implement installer-side fix ensuring Node >=22 is used for install and for post-install openclaw invocation.
  • Validate with before/after repro runs and shellcheck.
• Human verification:
  • Reviewed code diff and runtime behavior.
  • Confirmed successful commands and logs after patch.

Companion Test PR

• Companion regression tests PR in openclaw: Installer smoke: add unsupported Node-path regression openclaw#21307
• Merge order: this openclaw.ai installer fix should merge first, then the openclaw regression-test PR.

[vercel]

@rolandkakonyi is attempting to deploy a commit to the Jamie's projects Team on Vercel.

A member of the Team first needs to authorize it.