The pods page drew one bar -- host RAM -- and printed VRAM underneath it as a
line of small text. On a page whose job is "what is this rented A40 doing", the
GPU was the one reading an operator had to take differently from everything
else on the row.

Both now get a bar, each labelled, each scaled to its own total. The colours
differ on purpose: host RAM keeps the green/amber/red bands, because that is
the ceiling that has actually killed pods (an OCR pod was OOM-killed at 128
in-flight with the GPU never the constraint). VRAM gets a neutral bar and says
"reserved", because vLLM claims its gpu_memory_utilization share at boot and so
reads ~90% from the first second on every healthy pod -- run that through the
load bands and every pod is permanently red, an alarm that is always on, which
an operator learns to ignore and then ignores the real ones with it.

Either bar is omitted when its telemetry is missing: a booting or unreachable
pod has none, and an empty bar reads as "idle" when the truth is "unknown".

Tested by running the page's own _memCell() in node over real payload shapes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8LAP3ueNzQJtwzhgVbq66