A Python block sent to a REPL gets the second Enter that ends it

A dogfood agent's `def` sent to python3 sat open at the continuation prompt:
a block whose last line is indented is not over at one Enter, pasted into
3.13's REPL or typed into the old one (checked against python 3.14 in a real
pty, both ways). A send to a Python REPL now adds that second Enter, and the
pty/data recipe in the docs and the 9P skill says to.

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 471967ad..845326d2 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -144,7 +144,8 @@ 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. `Repl -` unbinds; a bare `Repl` says the binding. Multi-line code
 written to `pty/data` should be a bracketed paste, `\e[200~<code>\e[201~`
-then `\r`: sent line by line, a blank line ends a Python block, and Python
+then `\r`, and a second `\r` when the code's last line is indented (a `def`
+or `for` body): one Enter leaves such a block open. Sent line by line, a blank line ends a Python block, and Python
 3.14's REPL auto-indents each line it is typed. Every refused 9P write adds an `err <serial|->
 <file>: <why>` record to `$m/log`; through a mount the write itself only says
 `Invalid argument`.