A terminal pane that closes takes its shell and pty with it, in every front end

The detached server closed a pane's pty only when the shell was respawned,
hit EOF or the session shut down, so rmdir, Del or Delcol on a terminal
left its shell running with nobody to read it; the tty front end and
macOS did the same. Retiring a terminal pane now emits a close_pty
effect, which each host that runs shells answers by hanging the pty up
and ending the shell (the detached server's and the GUI's existing
retire-and-reap path, and a close plus SIGHUP in the tty and macOS
shells).

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

1 files changed, 2 insertions, 0 deletions

diff --git a/src/ninep/testing.zig b/src/ninep/testing.zig
index 6ea40956..fce77f10 100644
--- a/src/ninep/testing.zig
+++ b/src/ninep/testing.zig
@@ -19,6 +19,7 @@ pub const Answer = struct {
     winsize: ?struct { cols: u16, rows: u16 } = null,
     signal: ?pardes.PtySignal = null,
     spawned: bool = false,
+    closed: bool = false,
 
     pub fn pty(a: *const Answer) []const u8 {
         return a.pty_buf[0..a.pty_len];
@@ -44,6 +45,7 @@ pub fn call(p: *Pardes, req: Req) Answer {
         },
         .resize_pty => |r| ans.winsize = .{ .cols = r.cols, .rows = r.rows },
         .signal_pty => |s| ans.signal = s.sig,
+        .close_pty => ans.closed = true,
         .spawn => ans.spawned = true,
         else => {},
     };