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, 5 insertions, 0 deletions

diff --git a/src/Messages.zig b/src/Messages.zig
index f4ea1c3e..72b3b63c 100644
--- a/src/Messages.zig
+++ b/src/Messages.zig
@@ -388,6 +388,11 @@ pub fn messageLog(m: *const Messages, i: usize) ?*const LoggedMessage {
 pub fn reportError(p: *Pardes, id: usize, operation: []const u8, err: anyerror) void {
     var buf: [256]u8 = undefined;
     const text = std.fmt.bufPrint(&buf, "{s}: {s}", .{ operation, @errorName(err) }) catch operation;
+    reportFailure(p, id, text);
+}
+
+/// reportError with the words already chosen.
+pub fn reportFailure(p: *Pardes, id: usize, text: []const u8) void {
     // A builtin a ctl write runs: its first error is also the write's.
     if (p.fs.no_prompt and p.fs.failure_len == 0) {
         const n = @min(text.len, p.fs.failure.len);