Problem
Operators cannot currently see how close the active configuration and traffic are to exhausting context capacity.
Required insight
Add one insight object to the existing /api/insights computation and render that same object in the dashboard. It should combine:
- the prompt-token distribution in the measured request window;
- configured max context;
- KV capacity and current/high-water page utilization;
- max concurrency and active concurrency;
- representative request IDs near the observed limit.
The insight should distinguish large individual prompts from concurrency-driven KV pressure and mark any recommendation as inferred.
Acceptance
Fixtures cover a near-max-context request, concurrency-driven high KV utilization, a comfortably sized workload, and missing capacity telemetry. Missing data must render unavailable rather than zero pressure.
Split from #12.
Problem
Operators cannot currently see how close the active configuration and traffic are to exhausting context capacity.
Required insight
Add one insight object to the existing /api/insights computation and render that same object in the dashboard. It should combine:
The insight should distinguish large individual prompts from concurrency-driven KV pressure and mark any recommendation as inferred.
Acceptance
Fixtures cover a near-max-context request, concurrency-driven high KV utilization, a comfortably sized workload, and missing capacity telemetry. Missing data must render unavailable rather than zero pressure.
Split from #12.