Joseph Doherty
baae59ce3b
Gateway server-side named-pipe frame path, wire format byte-identical: - Writer (GWC-08/IPC-13): serialize once into a single ArrayPool-rented buffer holding the 4-byte LE length prefix + payload, then one WriteAsync. Removes the second serialization pass (ToByteArray re-ran CalculateSize), the separate prefix array + second stream write, and per-frame heap allocation. - Reader (IPC-14): rent the payload buffer from ArrayPool instead of new byte[] per frame; read/parse bounded to the real length, return in finally. Matches the worker side which already pools. - Correctness: length tracked separately from (larger) pool capacity; every rented buffer returned exactly once in finally incl. the malformed-protobuf path; ParseFrom copies into the message so the envelope never aliases the returned buffer. Cross-checked LE-prefix framing agrees across gateway+worker writer/reader. Server build clean (0 warnings); WorkerFrameProtocol tests 10/10 incl. a new large-payload-near-cap round-trip (forces pool buffer > frame). The 2 failing WorkerClient/FakeWorkerHarness tests are the known macOS UDS 104-char path limit, not a regression. Claude-Session: https://claude.ai/code/session_01DMXXvNuPekkkrTEyPNxEkW