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/tagnav.snap b/test/snapshots/tagnav.snap
index c9ac9605..95c4b751 100644
--- a/test/snapshots/tagnav.snap
+++ b/test/snapshots/tagnav.snap
@@ -94,7 +94,7 @@ key c-w k
 stable 400 5000
 snap workspace-tag
 # `$` is the last cell; four long-word steps back land on `Dump`, and the
-# execute key runs it and gives the keyboard back to the body FIRST -- `Kill`
+# execute key runs it and gives the keyboard back to the body FIRST -- `Exit`
 # lives up here too, so a builtin that frees the session must never return
 # into a focused header. Dump grows a `Restore <path>` word, which is also the
 # case where the line gets longer than the column you were parked on.