Give the message log to Messages as its own fields

Not a pure move: state moves. Pardes's three message-log fields
(`messages: [message_log]LoggedMessage`, `messages_head`, `messages_len`)
become the fields of Messages.zig itself (`log`, `head`, `len`), and
Pardes embeds one as `messages: Messages = .{}`. messageLog reads only the
ring, so it now takes `m: *const Messages` and is called
`p.messages.messageLog(i)` (Output's +Messages view and the log test);
logMessage still needs the panes and the 9P event log, so it keeps
`p: *Pardes` and writes `p.messages.log/head/len`. No behaviour change.

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

1 files changed, 1 insertions, 2 deletions

diff --git a/src/Output.zig b/src/Output.zig
index b216c0cf..6df2fd34 100644
--- a/src/Output.zig
+++ b/src/Output.zig
@@ -4,7 +4,6 @@ const panes = @import("panes.zig");
 const std = @import("std");
 const pardes = @import("pardes.zig");
 const exec = @import("exec.zig");
-const Messages = @import("Messages.zig");
 const config = @import("config.zig");
 const Pardes = pardes.Pardes;
 const modal = @import("modal.zig");
@@ -686,7 +685,7 @@ pub fn openMessages(p: *Pardes, id: usize) !void {
     var out: std.Io.Writer.Allocating = .init(p.gpa);
     errdefer out.deinit();
     var i: usize = 0;
-    while (Messages.messageLog(p, i)) |m| : (i += 1) {
+    while (p.messages.messageLog(i)) |m| : (i += 1) {
         if (m.serial != 0) try out.writer.print("{d}: ", .{m.serial});
         try out.writer.writeAll(m.slice());
         if (m.repeats > 1) try out.writer.print("  (x{d})", .{m.repeats});