🤖 Add remote-side timeout using timeout command

When SSH is killed locally, the remote command may continue running
(especially with ControlMaster multiplexing). Wrap remote commands with
the `timeout` utility to ensure they're killed on the remote side too.

Uses SIGKILL and sets remote timeout slightly longer than local timeout
to ensure the local timeout normally fires first.

Author: ammar-agent

src/runtime/SSHRuntime.ts

@@ -90,10 +90,23 @@ export class SSHRuntime implements Runtime {
     parts.push(command);
 
     // Join all parts with && to ensure each step succeeds before continuing
-    const fullCommand = parts.join(" && ");
+    let fullCommand = parts.join(" && ");
+
+    // Wrap command with timeout if specified
+    // This ensures the remote command is killed even if the SSH connection persists
+    // (e.g., due to ControlMaster multiplexing)
+    if (options.timeout !== undefined) {
+      // Use timeout command with KILL signal after timeout expires
+      // The timeout value is slightly longer than our local timeout to ensure
+      // the local timeout fires first in normal cases
+      const remoteTimeout = Math.ceil(options.timeout) + 1;
+      fullCommand = `timeout --signal=KILL ${remoteTimeout} bash -c ${shescape.quote(fullCommand)}`;
+    }
 
     // Wrap in bash -c with shescape for safe shell execution
-    const remoteCommand = `bash -c ${shescape.quote(fullCommand)}`;
+    const remoteCommand = options.timeout
+      ? fullCommand
+      : `bash -c ${shescape.quote(fullCommand)}`;
 
     // Build SSH args
     const sshArgs: string[] = ["-T"];