ios --remote eas fails to install: agent-device connection bound to a different platform #1096

Problem

stim ios --remote eas created and booted an EAS Simulator session, then failed to install the app with STIM_INSTALL_FAILED:

agent-device install failed for .../Trailhead.app: Error (INVALID_ARGS): Active remote connection is already bound to a different platform. Re-run connect --force to replace it.

The session kept running (billable) until stim stop.

Evidence

2026-09-25, stim 1.9.0 (main 4d3ba1c, packages/stim-cli/dist/cli.mjs), eas-cli 24.8.0, agent-device 0.21.12, a fresh trailhead worktree after stim start --remote. Output: build ok (4m55s), device EAS Simulator (01a0..) booted (59.5s), then the error above. agent-device diagnostics ID mugbsb84-74764add (~/.agent-device/logs/default/2026-09-25/), session stim-remote-eas-verify-e5b04f08ac84b30b. stim status --json reported the session correctly (remoteDevices, state: claimed, webPreviewUrl), and stim stop ended it (eas simulator:get -> STOPPED). Other agents on the machine may have used agent-device at the same time; ~/.agent-device/remote-connections/ was empty after stop.

Cause

Unknown: either another process's agent-device remote connection was active for a different platform, or Stim's connect step bound the workspace's connection to the wrong platform or reused a shared connection.

Fix idea

Find which connection agent-device considered active (its remote-connections state is per session or per daemon?) and how Stim connects for EAS (packages/stim-cli/src/engine/device-remote.ts). Stim should connect with an explicit platform scoped to its own session, never disturb another tool's connection, and on an install failure after the session started, end or clearly report the billable session instead of leaving it running.