An analytics dashboard joins the squadron b9d9b66

The mission desk wants numbers, so numbers it gets — a proper analytics dashboard, plus the plumbing that feeds it:

1. New dashboard at /analytics, styled to the squadron: SORTIE RECORD (missions flown, flight hours, ejections), COMBAT RECORD (MiG kills, AIM-9 and AIM-120 fired, hits by type, cannon rounds, gun hits) and PILOT CHOICES — Hornet versus Falcon picks, and how often each free-flight start point gets the nod, bars and all.
2. Every metric is counted as you play. Missions, flight time, MiG kills, plane and start-point selections, ejections, missiles by type, cannon rounds, missile hits by type and gun hits are all tracked live and kept between sessions. One honest caveat: the dashboard reads the counters in your browser — clear your storage and your record starts over.
3. Every metric also fires as a Google Analytics event — mission_flown, flight_time, mig_kill, plane_select, start_point_select, ejection, missile_fired, cannon_rounds_fired, missile_hit and gun_hits — so the fleet-wide picture across all players builds in the GA4 property. High-frequency streams (flight seconds, cannon rounds, gun hits) batch up and report once a minute and at the end of every sortie; the rest report the moment they happen.
4. ANALYTICS DASHBOARD is a main-menu item (key A, opens in a new tab) — and DEMO has left the menu; the attract loop still runs behind the menu as always, it just no longer takes up a row.

Two menu-router bugs surfaced while wiring all this up, and both are fixed:

1. One keypress was being spent twice. Hitting 2 for FREE FLIGHT used to open the start-point map and — in the very same instant — let that same 2 fall through to the map and pick Oakland for you. The menu now swallows any key it consumes.
2. F1–F7 work in MISSIONS again. The rows always said F1, F2, F3… but the keyboard router wasn’t listening for F-keys — mouse or nothing. Now the keys do what the badges promise.