szn

Bug 208 — renderToDisplayClient skips frame generation on successful display backlog flush

208. renderToDisplayClient skips frame generation on successful display backlog flush

File: src/server/server.zig:2236–2239 Severity: HIGH Status: ✅ FIXED — wrapped the continue statement in renderToDisplayClient inside the conditional block, so the event loop only skips frame generation if the flush was incomplete (returned false).

When a display client socket had pending bytes in its output buffer, renderToDisplayClient attempted to flush the backlog. However, even if flushDisplayClient fully wrote all pending bytes (returning true and clearing the buffer), the loop executed an unconditional continue, skipping the generation and transmission of the current frame (e.g., the second line of the shell prompt) for that client. Because the backlog was fully cleared, the server then cleared the dirty flags, putting the render loop to sleep without ever rendering/sending the new frame until the user typed a key.