A refusal over unsaved panes keeps its list in +Unsaved and shows a short notice

Exit's refusal (and Restore's, Del's, Delcol's, get's) put its full text
on a notice that went: a long list of names, gone before it was read. The
list now goes into one +Unsaved pane, filled again by each refusal, a row
a pane (`<name>: Modified`) and the `Exit again to discard` line; the
notice is short, `3 unsaved panes — Exit again to discard`. The 9P
`unsaved` records and the write's err are as they were.

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

1 files changed, 2 insertions, 1 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 4678d55a..1fe2aed8 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -86,7 +86,8 @@ $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,
               logging `unsaved <serial> <name>` for each unsaved pane, then failing the write with
               `<name>: Modified (Exit again to discard)` for one or `4 unsaved panes: Modified (Exit
-              again to discard)` for more (Restore's says `Restore again`); a second refusal names only the panes edited since the last,
+              again to discard)` for more (Restore's says `Restore again`); on screen the list stays
+              in the one +Unsaved pane under a short notice (`3 unsaved panes — Exit again to discard`); a second refusal names only the panes edited since the last,
               as acme's does, and the same word again with nothing edited since DISCARDS them all -- not a retry, unlike lock's `file in use`;
               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`