fix(mcp): memory leak — WebSocket frame payload not freed in handleConnection loop

[gHashTag]

Summary

• Added allocated: bool field to Frame struct to track when payload memory was allocated during unmasking of masked WebSocket frames
• Added defer statement in handleConnection() loop to free the payload when it was allocated, preventing memory leak

Problem

tools/mcp/trinity_mcp/websocket_transport.zig had a memory leak in the handleConnection() loop. When parseFrame() processed a masked WebSocket frame, it allocated memory for the unmasked payload. But after processing the frame in the switch statement, the payload was never freed.

Fix

The fix adds an allocated boolean to the Frame struct that is set to true when memory is allocated for unmasking, and then a defer statement in handleConnection() frees the payload when needed:

defer if (frame.allocated) self.allocator.free(frame.payload);

Test Plan

• zig build compiles successfully
• zig ast-check passes
• Frame payload is freed after each iteration of the handleConnection loop
• No memory leak on masked WebSocket frames

Closes #205

🤖 Generated with Claude Code