@charset "UTF-8";

        html[data-theme="dark"] {
            /* One token, one decision. --nav follows the shared chrome so the rail can
               never disagree with the bar above it again. The two accents beside it are
               still navy-derived on purpose: they are edges and hovers ON the chrome,
               not the chrome itself, and they read as depth in either colour. */
            --nav: var(--cbp-chrome, #262626); --nav-hi: #393939; --nav-line: #4a4a4a;
            --nav-ink: #dfe9f7; --nav-ink-dim: #c3ccd9; --nav-ink-hi: #f6f9ff;
            /* THE ROOT CAUSE of "blue bars on a grey background", and it is this one line.
               --brand was re-declared here at its DAYLIGHT value, on the reasoning that
               the brand blue is an accent and an accent should not move. That reasoning
               holds for an accent. It does not hold for a FILL, and twenty-five of the
               twenty-five background declarations that read this token are fills: the
               dealer rail's active nav pill, the primary button on every form, the chat
               Send button and every message the dealer sent, the bid-limit call to action,
               the Save button in My Cars, the paginator's current page, the mobile
               drawer's active tile, the claim form's submit. Every one of them was
               painting the daylight indigo onto a grey card at 1.96 to 1 -- a saturated
               blue bar with nothing behind it.
               So --brand takes the shared night fill. It is the same value the Log in and
               Search buttons take, so a primary action is one colour everywhere.

               --brand-2 deliberately does NOT move. Its job at night is the focus RING on
               .ds-link, .dp-btn and the chat composer, where it reads 3.66 against the
               card -- above the 3 to 1 a ring needs. Taking it to the slate hover would
               drop it to 2.67 and fail. Where it is used as the light end of a GRADIENT
               instead, that gradient gets its own night rule below. */
            --brand: var(--cbp-blue-fill, #4c5a6b);
            --brand-2: #4a7fd4;   /* the focus ring: bright on purpose, see above */
        }
        /* NEVER write `background:` (the shorthand) on .cbp-nav in a theme block. An
           earlier dark rule read `background: #2b2b2b`, and the shorthand resets
           background-image, so dark mode was not tinting the topographic texture — it
           was deleting it (computed background-image: none). The colour now moves
           through --cbp-chrome, which touches nothing else. */
        /* The .cbp-badge ring rule that used to sit here matched NOTHING -- that class
           appears nowhere else in the codebase. The element it was written for is
           .cbp-bell-badge, which is fixed where it is drawn. A selector that matches
           nothing looks like coverage and is not. */
        /* The .wl-thumb / .won-thumb placeholders are the same object drawn by two
           different pages; only one had a night rule, so they sat side by side on the
           dashboard in two different colours. Both follow the chrome now. */
        html[data-theme="dark"] .wl-thumb, html[data-theme="dark"] .won-thumb { background: var(--cbp-chrome, #262626); }
        html[data-theme="dark"] .dp-title { color: var(--cbp-ink); }
        html[data-theme="dark"] .dp-kpi .k-val,
        html[data-theme="dark"] .dp-veh,
        html[data-theme="dark"] .wl-name { color: var(--cbp-ink); }