docs: what dogfooding asked of the second round

The served README, the skill and docs/fs.md now say where an address search
starts, that an event record's text may hold newlines and is read by its
count, that truncating tag clears its default words too (append to keep them,
u in the tag to get them back), how Dump and Restore behave and where dumps
go, that Kill stops only the foreground job (the rest of 'sleep 30; echo done'
still runs) and that Joincol needs a column to the right. The skill and
fs.md had Collapse as a column word; it folds the pane it is given.

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

1 files changed, 3 insertions, 3 deletions

diff --git a/src/fs-help.txt b/src/fs-help.txt
index 4633d91c..7e869f9e 100644
--- a/src/fs-help.txt
+++ b/src/fs-help.txt
@@ -9,7 +9,7 @@ log         events: new/del/rename/save <serial> <name>, msg <serial|-> <text>,
 screen      rendered screen as JSON, frozen from open to close
 listeners   the session's dial addresses
 focus       the serial of the pane with the keyboard; write a serial to give it the keyboard
-ctl         settings, one a line as a write takes them; or Newcol, Dump, Exit (quits), Kill (stops cmds)
+ctl         settings, one a line; or Newcol, Dump, Exit (quits; asks once), Kill (stops the fg job)
 commands    every builtin: its word, arg if it takes one, and root or pane: which ctl takes it
 pane/new    open it to make a pane (named +New); the read answers that pane's serial
 pane/<n>/   name body tag ctl addr dot limit data xdata sel dirty mark scroll errors (write-only:
@@ -35,9 +35,9 @@ Below, $m is the mount (/mnt/9p/pardes/<pid> via 9ns --mntgen; PARDES_MOUNT in a
 
 Pitfalls, one each:
   Each open of pane/new makes another pane (ls, stat, find never do); rmdir closes even a dirty one.
-  addr takes #n,#m or sam-style /regexp/ (^ $ per line); a failed one makes data refuse until reset.
+  addr takes #n,#m or /regexp/ from the current address (^ $ per line); a failed one refuses data.
   data: > replaces the addr range, : > deletes it, a 2nd > inserts (addr moved); body: > empties all.
-  tag reads the path, then the tag's own text; writes append to that text; truncating clears it.
+  tag reads the path, then its own text; writes append; truncating clears it, default words too.
   A terminal's body is a history snapshot frozen per open; pty/data is the live stream.
   exec: a word no builtin knows is typed into a terminal in the pane's directory, and not an error.
   Through a mount a malformed write is EINVAL, a well-formed one that fails EIO: log's err says why.