[FEATURE REQUEST] Provide a Standalone Binary to Isolate from Local Node.js Environments

The Problem

Many developers use version managers like mise, vfox, or proto to manage Node.js versions on a per-project basis. A common workflow that creates a conflict is as follows:
A developer enters a legacy project directory.
The version manager automatically switches the active node version to an older one required by the project (e.g., v16), based on a config file like .tool-versions.
If the developer then tries to run the globally installed claude CLI, the command fails because it uses the active environment's Node.js (v16), which is below the v18+ requirement.
This makes it impossible to use the claude CLI while working inside projects that are pinned to an older Node.js version, leading to a poor user experience.

Proposed Solution

We propose offering a standalone binary as an installation method for the claude CLI.
This binary would come bundled with its required Node.js runtime. Consequently, the claude command would always use its own self-contained, compatible Node.js version, completely ignoring the user's active shell environment.

Benefits

Improved User Experience: Users no longer have to worry about their local or project-specific Node.js version. The claude CLI would "just work" everywhere.
Enhanced Robustness: This approach completely decouples the tool's runtime from the user's development environment, preventing a wide range of potential version conflicts.
This distribution model is a successful pattern used by other popular CLI tools, such as pnpm (via its standalone script) and the Vercel CLI. We believe claude would greatly benefit from this as well.