The docs give the full-column refusal, an Edit block left open at close, and byte columns

Round 11's doc findings: the skill names the full-column refusal beside the
64-pane cap; fs.md and the skill say an Edit block still open when its open
closes fails with unmatched { and an err; and line:col's byte columns get
the tip for character columns from tools (the same on ASCII, else a
search or #n). A unit test pins the unmatched { at close.

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

1 files changed, 4 insertions, 2 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 38f84e77..e64c0118 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -95,7 +95,8 @@ $m/pane/new   open it to make a pane (a scratch named <dir>/+New), read names it
               the ACTIVE column (the one last typed or clicked in, or Newcol's), filling it if
               empty, else taking the bottom half of its last pane (ctl `Placement pardes`: the old rules);
               a session holds 64 panes (16 on the board): past that, every route that opens one
-              fails with `no space for a pane: 64 max` (ENOSPC); rmdir $m/pane/<n> closes it; a column's last pane leaves the column EMPTY
+              fails with `no space for a pane: 64 max` (ENOSPC), and so does one whose column
+              has no rows left (each pane keeps its tag and 2 rows: `no space for a pane in that column`); rmdir $m/pane/<n> closes it; a column's last pane leaves the column EMPTY
               (focus reads empty, the log says only del), and the session's LAST pane QUITS it
 $m/pane/<n>/errors  write-only: text appended to the +Errors pane of the pane's directory
 $m/os/        the host filesystem
@@ -145,7 +146,8 @@ made, or the pane it focused or acted on: an open's own last write's, or, on
 an open that never wrote, the session's last. With other clients about,
 write and read one open (`exec 3<>$m/look; echo x >&3; cat <&3; exec 3<&-`).
 Each command line runs once whole, however a mount cuts a big write; a last
-line with no newline runs when the open closes. A command that fails is reported in
+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
 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