Greptile Summary

This PR adds a try_load_nvm() helper to scripts/install.sh that proactively sources nvm.sh --no-use and activates the nvm default Node alias before check_node() runs. This correctly fixes the scenario where a stale system-installed Node (e.g. /usr/bin/node v8) appears earlier on PATH in a non-interactive shell (curl ... | bash), causing the installer to unnecessarily trigger install_node() and overwrite the user's nvm environment.

Key changes:

• New try_load_nvm() function (lines 1398–1411): sources nvm if available, then calls nvm use default (falling back to nvm use node) with full error suppression — safe for systems without nvm.
• Called in main() immediately before the check_node / install_node block (line 2362).

Minor concern:

• The inline comment at line 1401 claims the function is "a no-op if nvm is not installed or already loaded," but when nvm is already present in the shell it still re-sources nvm.sh and calls nvm use default. The re-source is idempotent so it won't cause bugs, but the comment should be corrected to avoid confusing future maintainers.

Confidence Score: 4/5

• This PR is safe to merge — the fix is well-scoped, correctly handles the edge cases, and degrades gracefully on systems without nvm.
• The implementation correctly addresses the stated problem. Error handling (2>/dev/null || true) prevents failures on nvm-less systems, the --no-use flag prevents unintended side effects during nvm.sh sourcing, and placement before check_node() is correct. The only deduction is for the mildly inaccurate "no-op if already loaded" comment, which could mislead future contributors but does not affect runtime behaviour.
• No files require special attention.

This is a comment left during a code review.
Path: scripts/install.sh
Line: 1401

Comment:
**Inaccurate "already loaded" no-op comment**

The comment states the function is "a no-op if nvm is not installed or **already loaded**," but this isn't true. When nvm is already available in the shell (`command -v nvm` succeeds before this function runs), the guard `[[ -s "${nvm_dir}/nvm.sh" ]]` is still true, so the function will:
1. Re-source `nvm.sh` with `--no-use` (generally idempotent, so harmless)
2. Call `nvm use default --silent`, potentially switching the active Node version

The behavior itself is intentional and fine — you *do* want to ensure the default nvm Node is active — but the comment is misleading. Either update the comment to reflect what actually happens, or add an early-return guard to make the "already loaded" case a true no-op:

```suggestion
    # Source nvm before checking Node.js so the installer uses the nvm-managed
    # version rather than a system-installed Node that may be too old.
    # This is a no-op if nvm is not installed. If nvm is already loaded,
    # it ensures the default alias is active.
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "fix(installer): load..."}