summaryrefslogtreecommitdiff
path: root/.agents/skills
diff options
context:
space:
mode:
Diffstat (limited to '.agents/skills')
-rw-r--r--.agents/skills/pardes-9p/SKILL.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 1142efa9..cc129d5c 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -311,7 +311,10 @@ as read acts on its text when the range is empty (the only way for a record
at `0 0`). Chord reports need explicit handling. A record is
`<origin><action><q0> <q1> <flag> <n> <text>\n` and its text may hold
newlines: read `n` bytes of text, never up to the next newline (acme counts
-runes; pardes counts bytes, as all its offsets are).
+runes; pardes counts bytes, as all its offsets are). Every address lands on a
+rune boundary, never inside one and never widened to a grapheme cluster: `#n`
+or `line:col` inside a rune snaps back to its start, a match covers the runes
+it touches, and a combining mark or a CRLF's `\r` is addressable alone.
A Restore puts a new editor under every client: the Restore write is
answered, then every connection is hung up (their fids name the old
editor's panes); dial again, and the new log names the restored panes then