An a, c or i text with no . line fails the Edit, as an open { does

sam takes the end of input as a text block's end, so a block cut short (a
write that lost its tail, an open closed early) inserted half of itself.
An Edit whose a, c or i text never meets its . line now fails with "a, c
or i text not ended by a . line" and changes nothing, as an unclosed {
does; at a close, logged as an err.

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 ae42bc86..e363b7cb 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -150,7 +150,8 @@ A read is a stream: once read, a second read on the same fd gives EOF (on
 an open that wrote, until its next write); open again, or seek to 0, to read
 it again. Each command line runs once whole, however a mount cuts a big write; a last
 line with no newline runs when the open closes, and an Edit block still open
-then fails there (an `err`, ``unmatched `{'``), changing nothing. A command that fails is reported in
+then fails there (an `err`: ``unmatched `{'``, or an a/c/i text with no `.`
+line), changing nothing. A command that fails is reported in
 the editor, not as a write error, so inspect the resulting pane, index, message
 or screen; only a malformed line fails the write itself. A word no builtin
 knows (a typo included) is a command line: written at a terminal at its