Exit quits and Kill stops commands, as in acme

Kill quit the editor, which in acme is Exit; acme's Kill stops the
commands it started. Exit now quits as acme's does (exec.c, rowclean):
it refuses once, naming each pane with unsaved text, and quits when
asked again with nothing edited since (a small scratch is not asked
about). Kill, bare or with names, stops the commands pardes typed into a
terminal (an exec, a middle click, a pty/run) while their shell's marks
say they run, by SIGTERM to the terminal's foreground job, never to the
shell (acme posts the kill note, which terminates). Both are session
builtins; the topbar's Kill becomes Exit, same width, and every golden's
topbar row changed by exactly that word (checked line by line); the
builtins script scrolls one more row for the index's new line.

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

1 files changed, 1 insertions, 1 deletions

diff --git a/test/snapshots/exec.golden b/test/snapshots/exec.golden
index 2ddd7eec..68a9737f 100644
--- a/test/snapshots/exec.golden
+++ b/test/snapshots/exec.golden
@@ -1,5 +1,5 @@
 == snap exec grid=140x31 cursor=16,8
-|Newcol Joincol Find Grep Help Changelog Tutor Dump NextColor Debug Kill
+|Newcol Joincol Find Grep Help Changelog Tutor Dump NextColor Debug Exit
 |   New Tty Find Grep Joincol Delcol                                      New Tty Find Grep Joincol Delcol
 |   /tmp/pardes-snap/exec/cwd Tty Save Mode Filter Collapse Del           /tmp/pardes-snap/exec/cwd Tty Save Mode Filter Collapse Del
 |  ls                                                             Exec   ls