A Rename that previews other files answers its preview pane to the 9P write that asked it, and says on the message row that it previewed and applied nothing

A multi-file Rename filled a +Search preview but the waiting exec write
answered the pane it was asked from, and nothing was said. lspResponse
now notes the pane it filled (fs.lsp_result); the write that waited for
the answer reads that pane back, as a look or an exec answers the pane
it went to, and the message row says `Rename: N edit(s) across files,
previewed, not applied`.

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

1 files changed, 3 insertions, 0 deletions

diff --git a/src/fs.zig b/src/fs.zig
index 0c04e873..7d6b0d71 100644
--- a/src/fs.zig
+++ b/src/fs.zig
@@ -1529,6 +1529,9 @@ pub const Namespace = struct {
     /// A 9P write asked a language server something: the answer count it
     /// waits to change (`turn.lsp_answers`), so its failure is the write's.
     lsp_answer_at: ?u64 = null,
+    /// The pane a language answer filled (a Rename's preview): what the
+    /// waiting 9P write answers once it is in (9p_io).
+    lsp_result: ?u32 = null,
     /// The most a Twrite of the request being served can carry (msize less
     /// its header), 0 when unknown: a write shorter than it is the whole of
     /// what its client wrote, one that fills it may be cut and go on.