/* The reporting dashboard's report drawn in the hub (site/dash/page.js). Its styles come from seo/dashboard.css (made by
   tools/extract_dashboard_css.py, scoped to .dk) and seo/page.css (the .dk base); this is what its <main id="view">
   gave the pages on the dashboard (its `main` rule is the dashboard's shell, so it isn't brought over), in the hub's box. */
.dk-report { max-width: none; }
.dk-app > main { padding: 8px 0 28px; display: flex; flex-direction: column; gap: 16px; min-width: 0; }
.dk-app > .fresh { margin: 0 0 8px; color: var(--muted); }   /* on the dashboard it sits on the purple header */
.dk-app > .controls { margin-bottom: 4px; }
.dk-app .foot { padding-left: 0; padding-right: 0; }
/* the Forecasts pages' own menu reaches out over <main>'s padding on the dashboard (forecast.css); here there's none to reach over */
.dk-app #view > .fc-nav { margin: 0; }
/* The hub's sailing page, Website and bookings (sail/page.js → mount sailOnly): the report's Summary is drawn out of sight
   (it works out the figures the sailing's panel shows); only the panel is seen. Its link to the tracker is this same page. */
.dk-offstage { position: absolute; left: -10000px; top: 0; width: 1100px; visibility: hidden; pointer-events: none; }
.dk-sailonly { position: relative; }
.dk-sailonly .tracker-link { display: none; }