Phase 13: web dashboard at /_bridge/dashboard

Single-page club management UI served by the bridge. The Core URL is
injected server-side so client JS calls Core directly without routing
through the proxy. Vanilla HTML/CSS/JS, dark theme matching admin.html.

Sections: Club (name/manager/coins/stats edit), Collection (filterable
card grid with stat bars + chemistry/training pills), Packs (open with
modal, history), Objectives (progress bars + one-click claim), Division
(W/D/L record, season progress, rivals weekly claim), FUT Champions
(current session with in-browser match simulation, claim, history),
Notifications (badge count in nav).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

src/main.rs

@@ -56,6 +56,7 @@ fn build_router(state: ProxyState) -> Router {
         .route("/_bridge/health", get(routes::health::get_health))
         .route("/_bridge/cert.pem", get(routes::health::get_cert))
         .route("/_bridge/guide", get(routes::health::get_guide))
+        .route("/_bridge/dashboard", get(routes::health::get_dashboard))
         .route("/_bridge/admin", get(routes::admin::get_admin_dashboard))
         .route("/_bridge/captures", get(routes::admin::get_captures))
         .route("/_bridge/captures", delete(routes::admin::delete_captures))