fix(docker): install Node/npm at runtime for npm-based CLI Apps

[Ho1yShif]

Problem

Installing an npm-based CLI App (e.g. hyperframes) from the WebUI failed with:

GET /api/settings/cli-apps/install?name=hyperframes → 400 Bad Request
"npm is not installed"

Root cause

The runtime image (ghcr.io/astral-sh/uv:python3.12-bookworm-slim) is Python-only. Node/npm existed only in the discarded webui-builder stage, so at runtime shutil.which("npm") in nanobot/apps/cli/service.py returned None and raised CliAppError("npm is not installed") — which defaults to HTTP 400.

A second latent issue: the gateway runs as the non-root nanobot user, and npm install -g defaults to /usr/local, which that user can't write to (EACCES).

Fix

• Copy Node + npm from the existing webui-builder stage into the runtime image (reuses the toolchain already in the build — no second download).
• Route npm install -g to a user-writable prefix (/home/nanobot/.npm-global) and put its bin/ on PATH, so installs succeed as nanobot and the installed CLI resolves via shutil.which(entry_point).

Verification

Built the image and ran the exact registry command as the nanobot user:

$ npm install -g hyperframes
install ok: /home/nanobot/.npm-global/bin/hyperframes

Both node --version / npm --version also run as a build-time check.

Notes

• Adds Node (~150MB) to the runtime image.
• .npm-global lives in the image home, not the mounted disk, so npm-installed CLIs are ephemeral across redeploys (same as the existing pip apps). Can be moved onto the disk in a follow-up if persistence is desired.

🤖 Generated with Claude Code