/*
 * The design tokens, re-asserted after the Contao-era stylesheet.
 *
 * app.16989ccd.css is Bootstrap-derived and declares Bootstrap's palette in
 * :root — including `--primary:#6d8fc1` and `--secondary`. Those are the same
 * two names the product uses for its theme tokens, and the product's convention
 * is HSL CHANNELS (`216 40% 59%`), because every utility and every themed rule
 * composes them as `hsl(var(--primary))`.
 *
 * The legacy file loads last, so its hex won. `hsl(#6d8fc1)` is not a colour —
 * the browser discards the declaration — and everything built on those two
 * tokens painted nothing: the .btn-primary call-to-action came out with a
 * transparent background and white text on a white page, invisible, wearing
 * Bootstrap's default 10px radius. Every `bg-primary`, `text-primary` and
 * `border-primary` on the site was in the same state.
 *
 * The values are identical, only the format differs — theme.ts says so itself:
 *   primary   hsl(216 40% 59%) → #6d8fc1 → rgb(109,143,193)
 *   secondary hsl(48 33% 90%)  → #eeebdf
 *
 * Overriding costs the legacy sheet nothing: it declares those variables once
 * and reads them zero times — grep found `--primary` once in 457 KB and `var(`
 * not at all. They are dead weight there and load-bearing here.
 *
 * This file is listed LAST in Theme.assets.stylesheets on purpose. Nothing else
 * fixes the order: the product injects its token block as <style
 * id="vi-active-theme"> before the theme's stylesheet links, so a token written
 * there is always overridden by a legacy sheet that redeclares it.
 */
:root {
  --primary: 216 40% 59%;
  --secondary: 48 33% 90%;

  /* Cookie-consent banner palette. The product's CookieConsent is theme-driven
   * via these two variables and falls back to vi-brand's dark + orange when a
   * site sets nothing — so dietrich sets its own: the brand navy surface (white
   * text stays readable) with the light-blue brand accent for links/buttons. */
  --vi-consent-surface: #0b2344;
  --vi-consent-accent: #95bce3;
}