A command line cut across writes runs once whole, and look/exec answer per open

A mount cuts a write at its message size, and each piece ran on its own: a
line cut at the boundary ran as shell commands and a 50 KB Edit block
broke. An open of look, exec, tagexec, any ctl or a column's exec now keeps
an unfinished last line, or an Edit block still open, until its next write
or its release, and never runs a fragment. The same open record holds what
its last write touched, which a read on it answers (as /net/tcp/clone
does); an open that never wrote reads the session's last as of its open.
A release that runs a held line waits for quiet and counts as a change;
a clicked line with a control character is still refused at its write.
Tested in unit tests, fs.py (python client, 8 KiB) and selfmount.py (the
kernel mount, a 1000-line seq burst and a 50 KB Edit block).

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

1 files changed, 1 insertions, 1 deletions

diff --git a/src/pardes.zig b/src/pardes.zig
index 706e9ef3..da9889ff 100644
--- a/src/pardes.zig
+++ b/src/pardes.zig
@@ -5311,7 +5311,7 @@ pub const Pardes = struct {
     /// that changes a pane costs a frame, which is why a round trip on a
     /// local socket costs microseconds and not a vsync.
     pub fn serveFs(p: *Pardes, req: ctlfs.Req) ctlfs.Reply {
-        if (!ctlfs.changesPane(req)) return ctlfs.handle(p, req);
+        if (!ctlfs.changesPane(p, req)) return ctlfs.handle(p, req);
         p.needs_frame = true;
         p.raw_hover_intent = false;
         look.cancelLookHover(p);