[TELEMETRY-HUD] Fix: Asynchronous Event Buffer Starvation Inside Next.js Dynamic Cockpit Polling Channels

Architectural Bottleneck

Under heavy enterprise workloads (thousands of active intercepted connections), the Next.js visual dashboard operator cockpit encounters telemetry data-loss blocks and dropped frames during 1-second active background intervals.

Root Cause Analysis

The core proxy gateway layer (internal/gateway/handlers.go) constantly serializes complex memory tracking matrices into raw text JSON buffers on every network polling request, choking the local HTTP connection channels.

Proposed Fix

Migrate the telemetry pipeline configuration from standard REST polling channels to a low-overhead, high-performance binary streaming WebSocket structure to pipe raw bytes delta changes cleanly with 0% serialization lag.

Read internal/gateway/handlers.go first to understand how telemetry matrices are serialized during polling, then trace the Next.js cockpit channel that consumes those responses. Done means the telemetry path uses the proposed binary WebSocket delta stream and avoids the reported polling-channel data loss and dropped frames.