Summary

After ./install.sh completes successfully, nemoclaw is often not available on PATH. Users see command not found and must manually recover with npm link, npx nemoclaw, or shell-specific nvm setup commands.

Problem

The install flow reports success, but the globally installed package is not reliably linked into the active shell environment. This breaks the expected out-of-the-box experience and forces users to debug Node/npm installation details after installation.

Expected behavior

Running ./install.sh from the repo should leave a working nemoclaw command available immediately in the current shell and in future shells.

Acceptance criteria

• ./install.sh verifies that the nemoclaw executable is installed and discoverable on PATH.
• If installation depends on nvm, the installer handles that explicitly or fails with a clear remediation message.
• The installer exits non-zero if nemoclaw --help cannot be executed after install.
• The docs no longer require npx nemoclaw or npm link as recovery steps for normal installs.