* fix: isolate concurrent remote connections
* refactor: harden remote connection state
* fix(cli): scope every emitted connect command to its own session
`scopeNextSteps` only reached `ConnectReadiness.nextSteps`, so two
command-bearing outputs still shipped unscoped:
- `providerArtifactNotes()` emitted `agent-device artifacts --json` as a
prose note, which never passes through that helper.
- `buildDeferredRuntimeNotice()` emitted `agent-device metro prepare
--remote-config <path>` independently in connection.ts.
On the shared-host concurrency path this branch fixes, following either
one resolves against the host-global active connection, so the artifacts
instruction can return another job's provider video and log URLs (#1659).
Both producers now take the connection state and format through one
exported `scopeCommand` helper, which is the single place a suggested
command is bound to its originating session. The metro config path is
shell-quoted alongside the session name.
Coverage: the BrowserStack route asserts human and JSON shapes carry one
`--session` per suggested command and that each emitted session resolves
back through `readRemoteConnectionState` to the connection that printed
it; `connection status` pins the scoped deferred-metro `nextStep`.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Michał Pierzchała