[FEATURE] Connect Next.js Frontend Telemetry Panels with Native Go API Endpoints

Problem

Our Next.js operations console at faultplane.vercel.app/dashboard displays visually stunning tracking grids and performance latency charts, but currently reads static hardcoded states. To advance toward absolute product reality, we need to replace this mock structure with dynamic live streams fetched directly from our low-overhead Go gateway daemon [1.1].

Proposed Solution

Establish clean asynchronous state integration layers between frontend telemetry panels and backend APIs inside /ui/app/dashboard/:

1. Dynamic Fetch Polling Hook: Implement client-side React hooks or WebSockets connections to hit our Go backend infrastructure states endpoint (GET /api/v1/telemetry/runtime) every 2 seconds.
2. Live Telemetry State Hydration: Map fetched data streams directly onto existing metrics cards components like GatewayCard (Uptime tracker), Checkpoints (Snapshot counter), and Latency P99 distribution layouts [1.1].

Use Case

Transitions the FaultPlane control panel from a visual prototype blueprint into a functional, live production observability cockpit, allowing platform engineers to witness real system interactions under chaotic constraints [1.5].

Start by reading /ui/app/dashboard/ and the existing GatewayCard, Checkpoints, and Latency P99 components. Then inspect the Go backend entry point for GET /api/v1/telemetry/runtime and determine whether polling or WebSockets fits the stated integration. Done means the dashboard panels display live endpoint data instead of static states and update every 2 seconds.