A refused or failed write is an err record in the log, naming the file and the reason

Through a mount every refusal reads as Invalid argument, so a shell user
could not tell a missing regexp match from a bad ctl word. Every write or
truncation the tree refuses or that fails now adds err <serial|-> <file>:
<why> to /log. No per-pane readable error file: acme's errors only takes
text, and one stream is simpler to watch.

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

1 files changed, 1 insertions, 0 deletions

diff --git a/src/pardes.zig b/src/pardes.zig
index 084b2216..9d336db3 100644
--- a/src/pardes.zig
+++ b/src/pardes.zig
@@ -4642,6 +4642,7 @@ pub const Pardes = struct {
         p.raw_hover_intent = false;
         look.cancelLookHover(p);
         const reply = ctlfs.handle(p, req);
+        if (reply.status == .err and (req.op == .write or req.op == .setattr)) ctlfs.events.noteError(p, req, reply);
         // The request was a whole step of its own, so it settles the way a
         // step does: the cursor and scroll reconciled, the scripted panes
         // told, and the panes it made announced to /log now rather than at