fix(test): stabilize ssh.process.replaced flake

After the 999->888 takeover, the 888 monitor would eventually fail
network reads, call processLost, then searchForProcess would find
888 again and emit ssh.process.recovered (same-PID rediscovery).
On slow CI runners that race won the negative assertion at
sshProcess.test.ts:469. Return [] from find after the takeover so
no rediscovery is possible.

Author: EhabY

test/unit/remote/sshProcess.test.ts

@@ -445,7 +445,10 @@ describe("SshProcessMonitor", () => {
 			});
 			vi.mocked(find)
 				.mockResolvedValueOnce([{ pid: 999, ppid: 1, name: "ssh", cmd: "ssh" }])
-				.mockResolvedValue([{ pid: 888, ppid: 1, name: "ssh", cmd: "ssh" }]);
+				.mockResolvedValueOnce([{ pid: 888, ppid: 1, name: "ssh", cmd: "ssh" }])
+				// No rediscovery after takeover: a same-PID rediscovery would
+				// emit ssh.process.recovered and break the negative assertion.
+				.mockResolvedValue([]);
 
 			const monitor = createMonitor({
 				networkInfoPath: "/network",
@@ -456,8 +459,6 @@ describe("SshProcessMonitor", () => {
 			await waitUntil(
 				() => sink.eventsNamed("ssh.process.replaced").length > 0,
 			);
-			// Halt monitoring before the negative assertion so the 888 loop
-			// can't race ahead and emit its own lost/recovered cycle.
 			monitor.dispose();
 
 			const replaced = sink.eventsNamed("ssh.process.replaced");