Kill stops a command pane's whole command, its & jobs included

With job control on, a command's & jobs get process groups of their own,
so Kill's signal to the foreground group and the shell's group left them
running, orphaned. A stop of a command pane now signals every process
group in its shell's session (Linux; a /proc scan). Jobs still outlive a
command that exits on its own. Docs and the skill say it per route.

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

1 files changed, 3 insertions, 2 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 844e028f..97050e25 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -77,8 +77,9 @@ $m/ctl        the settings, one a line as a write takes them; write a setting or
               matching a command line's first word; Exit and Restore refuse once,
               naming every unsaved pane, `<a>, <b>: Modified (Exit again to discard them all)`, and the same
               word again DISCARDS that text -- not a retry, unlike lock's `file in use`;
-              Kill signals only the foreground job, so of `sleep 30; echo done` the
-              echo still runs; Joincol needs a column to the right of the keyboard's);
+              Kill stops a command pane's whole line, `&` jobs included; of a line typed into a
+              shell only the foreground job, and the shell decides the rest (of `sleep 30; echo done`
+              fish runs the echo, bash abandons the line); Joincol needs a column to the right of the keyboard's);
               a pane's builtins (Del, Save f, Collapse, which folds that pane, and the
               column word Delcol, which closes that pane's column) go to $m/pane/<n>/ctl
 $m/commands   every builtin: `Word`, `Word arg`, then `root` or `pane` (which ctl takes it)