Please address the comments from this code review:

## Overall Comments
- The `isSystemScopePath` helper currently relies on hard-coded substrings like `\program files` and assumes Windows-style paths; consider guarding this logic with a `process.platform === 'win32'` check and/or using `process.env.ProgramFiles`, `ProgramFiles(x86)`, and `ProgramData` plus `path.resolve`/`startsWith` to avoid false positives and platform issues.
- Right now `systemScope` is derived from `process.execPath` only; if there are cases where the target of the update differs from the current executable, it may be safer to base the system-scope check on the actual install/update target path rather than the current process path.

## Individual Comments

### Comment 1
<location> `src/commands/upgrade.ts:99-100` </location>
<code_context>
+            const admin = await isAdmin();
+            const systemScope = isSystemScopePath(process.execPath);
+
+            if (context === 'installer' && !admin && options.elevate === false) {
+                throw new Error('System-scope update requires elevation. Re-run without --no-elevate or run as admin.');
+            }

</code_context>

<issue_to_address>
**issue (bug_risk):** Installer-elevation requirement is only enforced when `context === 'installer'`, not when an installer is inferred from the asset name.

The installer path is actually selected with `context === 'installer' || (asset.name.endsWith('.exe') && asset.name.includes('setup'))`, but this pre-check only covers `context === 'installer'`. If the filename implies an installer while `context !== 'installer'`, a non-admin using `--no-elevate` will still reach `applyUpdateInstaller` with `shouldElevate = false` and won’t see this explicit error. Consider basing this check on the same predicate as the installer branch (or re-checking inside that branch) so elevation behavior and messaging are consistent regardless of how installer context is derived.
</issue_to_address>

### Comment 2
<location> `src/commands/upgrade.ts:109-110` </location>
<code_context>
+                await applyUpdateInstaller(downloadPath, options.silent !== false, shouldElevate);
             } else {
                 if (!options.json) logger.info('Applying portable update...');
+                if (systemScope && !admin) {
+                    throw new Error('Portable updates to system-scope installs require admin. Use the installer or re-run as admin.');
+                }
                 // For portable, we need to know the target exe. 
</code_context>

<issue_to_address>
**issue (bug_risk):** The portable system-scope check may block dev/node environments where `process.execPath` is under Program Files, changing previous behavior.

On Windows dev setups, `process.execPath` for Node is typically under `C:\Program Files\nodejs\node.exe`, so `systemScope && !admin` will be true and this branch will now throw before the later packaged-vs-plain-Node logic (which previously only warned about not updating `node.exe`). If you still want warn-only behavior in dev, consider adjusting this condition—e.g., skip the system-scope check when running under `node.exe`, or move it after the packaged-vs-node determination so dev scenarios continue to work.
</issue_to_address>