Manual real-desktop SSH reproduction; synthetic disposable target.
AI-assisted; verified with the tests and tools listed above.

Base: f7b81e1d1115bc7284b39161d3cd6c7f3184eb1c
Head: 68c96633b9b45e2a20505182a2468702b201dd90

Desktop and remote target: Linux x64; procps-ng ps 4.0.4.
Both builds are separate real Electron desktops with isolated local state and fresh synthetic remote state.

Base, unrelated process PID:
08:16:03 ssh.environment.ensure.start
About 15 seconds later: client displays "T3 Code on [host label redacted] did not answer".
The stale PID is unchanged and recorded port 3774 remains closed.
08:16:20 ssh.environment.disconnect.start
The in-flight launcher later reports:
"Remote T3 server is still running but did not become ready. Retry the connection; the server was left running."
08:17:04 ssh.environment.disconnect.succeeded
The disposable unrelated process has exited and the launcher PID record is cleared.

The screenshots and recordings include the separate live fixture monitor. It reports actual process state and TCP probe results; it is not app UI. See the driver and observations for the Linux worker-thread ID case and the head comparison.