Editing a registry agent's command doesn't change what runs — a binary agent still downloads its registry build #121

The problem

An agent added from the ACP registry keeps its registry link after its command is edited. Saving the card stores the new command, but the link stays, and for a binary agent the link decides the launch: every connect still downloads and runs the registry's pinned archive. The typed command never runs, and declining the download leaves the agent crashed.

Reported by @GF-Huang in anomalyco/opencode#11176: he added OpenCode V2 from the registry and changed its command to his own C:\Users\Huang\cli-tools\opencode.exe acp. On connect he was asked to download OpenCode V2 2.1.2:

Declining left the card crashed, with his edited command shown above it:

Root cause

A registry agent was stored as what Add made of the registry entry: the launch line rendered into the agent's own command and args, its env merged into the agent's env, and only the registry id, the version and — for a binary — the archive kept as the link. The registry's recipe itself was never kept. So an edited command can't be told from the registry's own, and the link survives the edit: the save keeps the stored registrySource whatever the form sends (agents-store.ts, the agent-config save). For a binary agent that link decides the launch — a spec built from it carries the archive as a launch phase (specFromConfig), and the phase runs the archive's executable — and for every kind an Upgrade replaces the edited command with the registry's.

Workaround until then: add the local binary through Add agent → Custom instead of editing the registry card.