Installer tarball install can make npm update -g resolve prime-agent from npm

[ayushcodes13]

The official installer currently installs the release tarball into the user's global npm package tree. Because the package is not published to the npm registry, a later global update can try to resolve prime-agent from npm and fail with a registry 404.

Original issue/PR context:

• Issue: Official install causes npm update -g to fail with registry 404 for prime-agent #1042
• Closed PR: fix(installer): isolate npm tarball install prefix #1129

Observed behavior:

npm update -g
npm ERR! 404 Not Found - GET https://registry.npmjs.org/prime-agent - Not found

The previous proposed direction was to keep the release tarball install under a Prime-Agent-owned npm prefix and symlink only the prime-agent command into the user's global npm bin directory. That keeps the command globally available while avoiding a fake globally-installed package entry that npm update -g later treats as registry-managed.

Validation that was done in the earlier PR:

• npm run check
• sh -n install.sh
• isolated-prefix smoke test with a fake prime-agent tarball, verifying the user global npm tree stayed empty, the owned prefix contained the package, npm update -g --dry-run --prefix <user-prefix> succeeded, and the user bin shim pointed to the owned prefix

I understand the current process is discussion-first and that unsolicited PRs are not reviewed. If this installer behavior is still in scope, I can help with a focused implementation or additional reproduction details in whatever direction maintainers prefer.