From 18eeb7e628c1bbfc6ec0e92c0b327f384f549509 Mon Sep 17 00:00:00 2001
From: Gabriel Schneider <gbrls@0x4200.cafe>
Date: Tue, 29 Sep 2026 12:35:40 -0300
Subject: The docs say what the code does: body's > replaces and >> appends, an
 image's tag starts with its modes, a Dump's refusal names its file

The SKILL's example wrote body with > and called it an append; an image's tag begins with its mode words, not its path; the Dump refusals show the dump file's path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 .agents/skills/pardes-9p/SKILL.md | 3 ++-
 docs/fs.md                        | 9 ++++++---
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 57b7e32c..a91b4861 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -126,7 +126,8 @@ reuse or close a pane.
 ```sh
 cat "$m/index"                                  # which panes exist
 n=$(cat "$m/pane/new")                          # make one, take its serial
-printf 'text\n' > "$m/pane/$n/body"             # append
+printf 'text\n' > "$m/pane/$n/body"             # replace its text (> truncates)
+printf 'more\n' >> "$m/pane/$n/body"            # append
 cat "$m/pane/$n/tag"                            # what its tagline offers
 echo notes.txt > "$m/pane/$n/name"              # rename the buffer
 echo Save > "$m/pane/$n/exec"                   # save it (or to its ctl)
diff --git a/docs/fs.md b/docs/fs.md
index a7e91fb3..9cf2db53 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -259,7 +259,8 @@ a shell command; a `Shell` or `Tty` naming no
 shell says `no shell "x", not found` (ENOENT); a `DumpDir` whose last
 directory is missing has it made at the Dump, and one further up missing
 says `Dump <path>: no such directory` (ENOENT), one that is no directory
-(`/dev/null`) `Dump <path>: /dev/null is not a directory`; platform and startup facts are `/status`'s and the
+(`/dev/null`) `Dump /dev/null/pardes-<time>.zon: /dev/null is not a
+directory`, each naming the dump file it would have written; platform and startup facts are `/status`'s and the
 Config window's, not settings. A pane's `ctl` takes the builtins that act on
 a pane (`Del`, or `Del k`/`Del j` to give its rows to the pane above or
 below, `Save f`, `Collapse`, which folds that pane, `Undo` and
@@ -698,7 +699,7 @@ text with no final newline. A pattern that names a newline (`\n`) runs over
 the whole text instead, its `.` kept to one line; there a leading `^` still
 matches at every line start, and `$` may stand just before a `\n` (where it
 changes nothing). Any other `^` or `$` in such a pattern, `(^|\n)def` or
-`a\nb$`, is refused with `in a pattern with \n, ^ can only come first and $
+`a\nb$`, is refused, EINVAL, with `bad regular expression: in a pattern with \n, ^ can only come first and $
 only just before a \n`, since mvzr would read it as the start or end of the
 whole text: never a search that silently finds nothing. Within a line, `^`
 inside an alternation (`^def|^ `) matches only where the search starts, so it
@@ -781,7 +782,9 @@ a command pane ends in its own time, told by its `exit` record.
 
 `tag` reads the whole tag as the pane shows it: the computed path or PDF
 page (no mark for unsaved text: the grip shows that, and `dirty` says it),
-then the text you may edit. A write appends to that text,
+then the text you may edit. An image's tag begins with its mode words, not
+its path: `img petscii:off palette:terminal ascii:off <path>`, the modes
+it is drawn in, then the file. A write appends to that text,
 newlines included, and a tag with more than one line takes a row per line on
 screen; truncating `tag` clears it, as acme's `cleartag` does -- the default
 words (`Save Tty Collapse Del` and the rest) with it, since they are that text until
-- 
cgit v1.3