Overview's only call (/admin/api/status) was proxied to the engine, so during a
generation (engine GIL-busy) it timed out and the dashboard showed nothing.

The front now builds status from its OWN state — registry (loaded models, per-
engine in-flight), config (backend, load_mode), models.json (enabled models +
aliases) and live torch-free GPU stats (VRAM summed across cards) — with no
engine round-trip. It's used whenever the engine can't answer, and the front
skips the engine entirely when the primary is mid-generation (inflight > 0) so
Overview is instant instead of waiting out the timeout. Engine-only fields
(recent_activity, RAM watcher) are carried over from the last good status; when
the engine is idle the richer engine status is still used.

Verified: _native_status() builds a complete payload (status/backend/load_mode/
enabled_models/vram/requests) via TestClient/standalone.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011DDv7BchtZQWsnPG6Jm49m