Create a single-file benchmark artifact for the canonical `/dashboard/` route in the master oneshot catalog.

Brief:
Build an orbital launch mission-control dashboard with anomaly feeds, dense live operations data, and believable pressure. The interface should feel like a real launch room watching a heavy-lift vehicle approach window open, not a generic analytics board.

Panel plan:
- Mission header with launch status, countdown, range state, and operator mode pills.
- Vehicle telemetry panel showing altitude, velocity, propellant, thermal load, and guidance confidence.
- Launch timeline panel with milestone states from fuelling through orbital insertion.
- Anomaly feed panel with severity filters, acknowledgement state, and drill-down selection.
- Subsystem matrix for propulsion, avionics, guidance, range safety, ground support, weather, and comms.
- Orbital corridor or ascent track panel that visualises current stage position and target envelope.
- Crew or payload readiness panel with blocked items and operator notes.
- Communications and decision log panel with recent events and recommendation text.
- Drill-down drawer or focused detail panel that explains the selected alert or subsystem, impact, owner, and next action.

Interaction model:
- Keyboard shortcuts for help, pause or resume simulation, cycle anomaly filters, acknowledge the selected alert, and open a drill-down.
- Mouse and touch interactions for selecting alerts, switching subsystem focus, toggling saved views, and expanding details.
- Persist acknowledged alerts, active filter, selected subsystem, paused state, and preferred view in local storage.
- Simulate live-state updates locally with no external APIs. Metrics should drift, countdown should progress, and anomalies should appear resolved or escalate based on system state.

Visual direction:
- Dark launch-room palette with graphite, midnight blue, and signal colours for caution and failure.
- Dense but readable layout with instrument-inspired labels, hard panel edges, restrained glow, and clear scan hierarchy.
- Mobile layout should become a stacked control deck with sticky top status, not a squeezed desktop grid.

Quality bar:
- The dashboard must support real operator decisions.
- Alerts need concrete causes, affected systems, owners, and next actions.
- The simulation should create tension without becoming noisy or random.