Kill asks the host to signal at once and says when a shell has no job to signal

Kill queued a signal effect for later, so the job it saw running by its marks
could have ended, and another started, before the signal went; and with job
control off the job shares the shell's process group, so the host skipped it
and Kill reported nothing. Kill now calls the host's kill_job while it holds the
turn, and when the only job is the shell's own group says 'Kill: no job to
signal', which also fails a write of Kill to ctl.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 7 insertions, 0 deletions

diff --git a/src/macos.zig b/src/macos.zig
index ebe8193b..62858887 100644
--- a/src/macos.zig
+++ b/src/macos.zig
@@ -2312,6 +2312,7 @@ const vtable: pardes.Host.VTable = .{
     .pty_signal = ptySignal,
     .close_pty = closePty,
     .tty_taken = ttyTaken,
+    .kill_job = killJob,
     .write_file = writeFile,
     .write_dump = writeDump,
     .watch_file = watchFile,
@@ -2435,6 +2436,12 @@ fn ttyTaken(ctx: ?*anyopaque, pane: u8) bool {
     return host_io.ttyTaken(pt.pid, pt.file.handle);
 }
 
+fn killJob(ctx: ?*anyopaque, pane: u8) bool {
+    const st = hostState(ctx);
+    const pt = st.ptys[pane] orelse return false;
+    return host_io.killJob(pt.pid, pt.file.handle);
+}
+
 fn writeFile(ctx: ?*anyopaque, pane: u8, path: []const u8, bytes: []const u8) void {
     const st = hostState(ctx);
     filesystem.write(st.core, path, bytes) catch |err|