A click written back to event is done as the click, REPL and all; a REPL's ctl line names it

Writing an M record back from a .py body with a REPL bound ran the text as a
shell command (exit 127), where the click itself went to the REPL. acme does
what the click would have done (xfideventwrite, xfid.c:842-844), so a body X
record written back now goes the way a middle click goes: to a bound REPL,
bracketed or line by line, the several-REPLs question included. An F record,
a line written to exec, was never a click and still runs as a command. For a
readable list of bindings, the smallest place: a bound terminal's ctl line
ends with its id after current/notcurrent.

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

1 files changed, 3 insertions, 1 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 9f2aa519..7cc3aeb1 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -132,7 +132,9 @@ command pane, below what it showed. A terminal bound as a REPL (`Repl
 python` on its ctl) takes the middle clicks made on a `.py` body instead,
 but never a 9P write: a script sends code by writing the REPL pane's
 `pty/data`, and runs a command from such a file with `Exec <text>` or the
-tag. Every refused 9P write adds an `err <serial|->
+tag. A bound terminal's `ctl` line ends with its id (`python-a`); an event
+record written back from such a file's body goes to its REPL, as the click
+would. Every refused 9P write adds an `err <serial|->
 <file>: <why>` record to `$m/log`; through a mount the write itself only says
 `Invalid argument`.