Installation - "make install" fails when claude-agent-acp binary already exist from a different global npm package

[rapcmia]

Describe the bug

This issue was noticed while running make install on a machine that already had a global claude-agent-acp command available. The setup flow reached the deependency step, detected Node.js, npm, and TypeScript correctly, then tried to install @agentclientprotocol/claude-agent-acp and failed with npm ERR! EEXIST because /home/eddga/.nvm/versions/node/v24.14.1/bin/claude-agent-acp already existed. ❌

From the current setup script behavior, the install check only looks for @agentclientprotocol/claude-agent-acp. It does not recognize that the same claude-agent-acp executable may already be provided by another package such as @zed-industries/claude-agent-acp. The installer treats the dependency as missing and attempts another global install, which causes a binary name collision.

This appears to be a low-tier setup compatibility bug because the main runtime may still work, but the installer gives a confusing failure during setup.

Steps to reproduce

1. Install a global npm package that provides the claude-agent-acp executable, such as @zed-industries/claude-agent-acp
2. In this repo, run make install
3. Wait for the setup script to reach the @agentclientprotocol/claude-agent-acp install step
4. Observe that npm fails with EEXIST because the claude-agent-acp binary already exists

Attach required files

n/a

[cardosofede]

@david-hummingbot can you take this one?