Two builds of one terminal app clash over a shared remote daemon

If a release build and a dev or forked build of the same SSH-capable terminal app connect to one host, check whether both use the same remote session name and helper path (e.g. ~/.local/bin/<tool>). If they do, each connection uploads its own helper version over the other's, and the long-lived remote daemon keeps running whichever inode it started with. The other app's client then hangs at 'connecting' on version skew, and killing the daemon only helps until the other app reconnects and re-uploads. Diagnose with ps on the client, which shows both apps spawning <tool> remote ssh host --session X, and by the remote binary's mtime changing right after each reconnect. Fix by deriving the session name, helper path, state dirs and sockets from the bundle id or a build tag, so dev and release builds are fully isolated on the remote.