A chorded record written back with its two follow-ups runs once, with its argument

Writing a chorded exec's three records back as read ran the argument
and its location as shell commands. The first record (flag 8) now takes
the next record as its argument when it comes in the same write, else
the one kept from the click (or, with none kept, waits for it); its two
follow-up records, however they are written, are consumed as its, never
run. Tested written back together and one per write.

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

1 files changed, 5 insertions, 1 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 1e65bd00..ce33ac7c 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -713,7 +713,11 @@ was expanded from a click (a second record gives the original range), 4 (a
 look) the text is a file name or address, 8 (an exec) chorded: two records
 follow, the argument's text and where it came from, `<file>:#q0,#q1`.
 Written back, an `X`/`x` record executes and an `L`/`l` record looks, as
-the click would have (a chorded one with its argument); the origin letter
+the click would have. A chorded one (flag 8) runs with its argument: the
+record after it in the same write, else the one kept from the click; its
+two follow-up records written back after it, together or in writes of
+their own, are consumed as its, never run as commands (written back alone
+with no argument kept, it waits for its argument record); the origin letter
 written back is ignored but for `F` on `X`, which runs as the command it
 was rather than going to a bound REPL; `I`, `D`, `i` and `d` are reports and
 are refused. Read `n` bytes of the text, not up to a newline -- bytes here, where acme counts runes. Every offset and