/* ---------------------------------------------------------------------------
   Archivo and JetBrains Mono, self-hosted from public/fonts (both SIL OFL, see
   fonts/OFL.txt).

   These replace IBM Plex. The reason for the earlier move off Roboto still
   holds and is worth restating, because it is the one constraint the display
   face is not allowed to break: real references in this catalog look like
   UJ68FRNBIO, K0N65VN0NL, PI0548W9RQ. A buyer copying K0N65VN0NL onto a
   purchase order has to be able to tell a zero from an O and a 1 from an I.
   JetBrains Mono ships a slashed zero by default and fully disambiguates
   I/l/1, so --t-data keeps every reference and quantity as legible as Plex
   Mono did.

   Archivo is the change in voice: a heavy grotesque that holds up at display
   size, where Plex Sans Condensed was doing the job by narrowing rather than
   by weight. Headings can now carry 800 instead of leaning on the condensed
   cut, which is why --f-condensed resolves here too - there is no separate
   condensed file any more, and nothing asks for one.

   Both are variable, so one file per subset covers the whole weight range:
   4 files, 108KB, against the 8 files and 166KB Plex needed for four static
   cuts. 35% fewer font bytes, same two subsets (latin + latin-ext, both
   required: Movel, Pecas), still no external origin.
   --------------------------------------------------------------------------- */

@font-face {
    font-family: 'Archivo';
    font-style: normal;
    font-weight: 400 900;
    font-display: swap;
    src: url('../fonts/archivo-latin.woff2') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

@font-face {
    font-family: 'Archivo';
    font-style: normal;
    font-weight: 400 900;
    font-display: swap;
    src: url('../fonts/archivo-latin-ext.woff2') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}

/* Caladea Bold, for the brand badge only (includes/generic/brandbadge-defs,
   App\Support\BrandBadge). The owner set his badge mock-up in Cambria; Cambria
   is Microsoft's and cannot be served, and Caladea is the open (OFL 1.1),
   metric-compatible stand-in drawn for exactly that - same widths, same
   bracketed serif. One weight, subset to Latin and Latin Extended-A, 29KB, and
   only fetched by a page that draws a badge. WOFF rather than WOFF2 because
   this machine's font tooling has no Brotli encoder; it is the badge's only
   font, so the difference is a few KB. */
@font-face {
    font-family: 'Caladea';
    font-style: normal;
    font-weight: 700;
    font-display: swap;
    src: url('../fonts/caladea-bold.woff') format('woff');
}

@font-face {
    font-family: 'JetBrains Mono';
    font-style: normal;
    font-weight: 400 700;
    font-display: swap;
    src: url('../fonts/jetbrains-mono-latin.woff2') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

@font-face {
    font-family: 'JetBrains Mono';
    font-style: normal;
    font-weight: 400 700;
    font-display: swap;
    src: url('../fonts/jetbrains-mono-latin-ext.woff2') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
body {
    color: var(--ink);
    /* var(--page), not a hardcoded #F6F6F6. The token existed and this rule
       never read it, so the palette could be retuned without the largest
       surface on the site moving at all. */
    background-color: var(--page);
    font-family: var(--f-sans);
    font-size: 16px;
    font-weight: 400;
    line-height: 1.5;
    text-align: left;
    text-transform: none;
}

/* ---------------------------------------------------------------------------
   Type scale.

   Replaces two @media blocks: one that hard-overrode .fs-1/.fs-2/.fs-5, h5,
   .card-title and small below 576px while leaving .fs-3 and .fs-4 on
   Bootstrap's RFS calc(), and one that dropped body to 14px below 1400px while
   the rem-based .fs-* utilities stayed at their own sizes.

   The first inverted the scale on a phone - .fs-3 landed at 23.1px above .fs-1
   at 22px, so the product h1 rendered ~22% larger than the catalog h1 of equal
   rank. The second put 16px .fs-6 text next to 14px body copy on every laptop.

   Each token is a clamp() from its phone size (at a 390px viewport) to
   Bootstrap's own xxl size, so rank is monotonic at every width and no
   breakpoint has to restate a font size.
   --------------------------------------------------------------------------- */
:root {
    --f-sans: 'Archivo', system-ui, -apple-system, 'Segoe UI', sans-serif;
    /* No separate condensed cut any more: Archivo carries display weight at 800
       rather than by narrowing. Kept as a token so the ~30 callsites that ask
       for it keep working and keep meaning "the display voice". */
    --f-condensed: var(--f-sans);
    /* Identifiers only. See the @font-face note above on why part numbers stop
       being a guessing game in a mono with a slashed zero. */
    --f-mono: 'JetBrains Mono', ui-monospace, 'Cascadia Mono', Consolas, monospace;

    --t-1: clamp(1.625rem, 1.29rem + 1.39vw, 2.5rem);         /* 26 -> 40px */
    --t-2: clamp(1.375rem, 1.13rem + 0.99vw, 2rem);           /* 22 -> 32px */
    --t-3: clamp(1.25rem, 1.06rem + 0.79vw, 1.75rem);         /* 20 -> 28px */
    --t-4: clamp(1.125rem, 0.98rem + 0.59vw, 1.5rem);         /* 18 -> 24px */
    --t-5: clamp(1.0625rem, 0.99rem + 0.3vw, 1.25rem);        /* 17 -> 20px */
    --t-6: 1rem;                                              /* 16px, fixed  */
    --t-display: clamp(2rem, 1.04rem + 3.96vw, 4.5rem);       /* 32 -> 72px */
    --t-display-sm: clamp(1.25rem, 0.77rem + 1.98vw, 2.5rem); /* 20 -> 40px */

    /* #CD212A is 5.46:1 on white but only 3.10:1 on the #1A1D1F header. This
       cooler red stays recognisably in the brand family and clears 4.5:1 there
       for focus indicators and accent text. */
    --accent-on-dark: #FF4554;

    /* -----------------------------------------------------------------------
       Palette, named. AHDP's mark uses true black; #1A1D1F carries that same
       authority across large text and dark surfaces without the glare of a
       full black interface. One raised charcoal remains for selected regions
       inside the bar, where using the identical value would erase the state.
       ----------------------------------------------------------------------- */
    /* Warm neutrals, not cool ones. Every value below used to sit on the blue
       side of grey - #F6F6F6 page, #1A1D1F ink, #DCDCD8 rules - which reads as
       software chrome. This catalog is a paper object: a parts drawing, a
       specification sheet, a printed reference list. Warming the whole neutral
       ramp by a few degrees is what moves it from "web app" to "workshop
       document", and it costs no markup and no copy.

       Hues only. Every value keeps the lightness its cool counterpart had, so
       the contrast ratios the feedback and accent colours were chosen against
       are unchanged. */
    --page: #F4F1EC;
    /* One step below the page, for a media well - the band a card or a tile
       reserves for a picture. The palette had --surface above the page and
       nothing below it, so a well with no photograph in it had no way to read
       as a well: a drawing on --page is ink floating on the tile, and next to a
       sibling holding a bled photograph the two stop looking like the same
       component. This is the page darkened by the same interval --rule already
       uses, which is enough to bound the band without becoming a second panel
       colour. Constant under hover on both kinds of tile, so the chrome inverts
       around the picture rather than through it. */
    --page-sunken: #EAE5DC;
    --surface: #FFFFFF;
    --ink: #141311;
    --ink-muted: #6B6559;
    --bar: #1A1815;
    /* One step below the bar, for the footer. The masthead opens the page on
       --bar and the footer closes it a shade deeper, which is what makes the
       two read as the same chrome at two ends rather than as one repeated
       stripe. Bootstrap's .bg-dark - the compiled #212529 - was doing this job
       in a cool grey the palette no longer contains. */
    --bar-deep: #0F0E0C;
    --bar-raised: #3C3833;
    /* Ink and rules for anything set on --bar or --bar-deep. The values are not
       new: .band-invert's copy, the footer's ink and its hairline have carried
       them for as long as those surfaces have existed, each as a token scoped to
       its own block. The dashboard rail is the first dark surface outside the
       storefront chrome, and a third private copy of the same three values is how
       they would start to drift, so they are named here once.

       Against --bar: --on-dark-ink 17.7:1, --on-dark-copy 10.8:1 and
       --on-dark-muted 5.9:1, so even the muted step clears 4.5:1 at the 10px
       mono the micro-labels are set in. On --bar-raised the muted step drops to
       3.9:1, which is why a raised row lifts its muted text to --on-dark-copy. */
    --on-dark-ink: #FFFFFF;
    --on-dark-copy: #CFC9C0;
    --on-dark-muted: #9A948A;
    --on-dark-rule: rgba(244, 241, 236, .12);
    --accent: #CD212A;

    /* The accent as a *surface*, for the one place it is flooded rather than
       marked: the homepage's closing band.

       --accent is chosen to be the loudest thing in a view, which is right for
       a button, a rule or a focus ring - a few hundred square pixels that have
       to win. Flooded across a full-bleed band it is several hundred thousand,
       and the same chroma that makes a mark read as urgent makes a surface read
       as an alarm. It is also the one value on the site still sitting on the
       cool side of its hue, on a neutral ramp that was deliberately warmed a few
       degrees end to end, so at that area it is the only object on the page not
       in the palette's own light.

       Same hue family, roughly 20% less lightness and less chroma: still
       unmistakably AHDP red, but a considered ground rather than a warning.
       White copy on it goes from 5.5:1 to about 7:1, so the band's text clears
       AA comfortably at body size instead of only at display size. Marks stay on
       --accent - this is not a second brand colour, it is the same one at the
       size where it has to behave differently. */
    --accent-deep: #A81D24;

    /* Feedback owns its own deliberate, high-contrast colors. Success used to
       reuse --ink and was indistinguishable from ordinary dark page chrome;
       error reused the action accent. These appear only when the system has an
       outcome to report, so their rarity keeps their meaning intact. */
    --feedback-success: #185C43;
    --feedback-error: #8F1D25;
    --feedback-on-color: #FFFFFF;

    /* Hairline. The site had no separator token at all: structure was carried
       entirely by white planes sitting on the page grey, so anything on white
       - a filter group, a card body, a table row - had no edge to read. This
       is the page grey darkened until it holds against both #FFFFFF and
       #F6F6F6, which is the only requirement a 1px rule has. */
    --rule: #D6CFC2;
    --rule-strong: #B6AE9E;

    /* Bootstrap resolves --bs-border-color from 5.3 onward; this project is
       pinned to 5.1.3 (head.blade.php:82), which compiles #dee2e6 straight into
       every .border* utility as !important. The token is declared anyway so a
       later Bootstrap bump inherits the right value, and the utilities are
       overridden explicitly further down. */
    --bs-border-color: var(--rule);

    /* -----------------------------------------------------------------------
       Spacing scale, 4px base.

       Spacing was Bootstrap's utilities picked per element: mt-5 next to mb-4
       next to py-5 next to p-4, with no relationship between them. The result
       is the homepage's four bands all separating at roughly the same interval,
       so nothing reads as more or less related to its neighbour than anything
       else.

       --band is the only generous interval; everything inside a band uses the
       steps below it. Rhythm comes from the contrast between the two.
       ----------------------------------------------------------------------- */
    --s-1: .25rem;
    --s-2: .5rem;
    --s-3: .75rem;
    --s-4: 1rem;
    --s-5: 1.5rem;
    --s-6: 2rem;
    --s-7: 3rem;
    --band: clamp(2.75rem, 5.5vw, 5.5rem);

    /* Depth, with an offset and a blur. The file had no shadow of any kind, so
       elevation was never available to say "this is above that" - a card hover
       could only change a text colour. Used on the three things that genuinely
       lift: a hovered card, the sticky masthead once the page scrolls under it,
       and the toast. */
    --shadow-1: 0 1px 2px rgba(31, 32, 34, .05), 0 10px 28px -14px rgba(31, 32, 34, .30);
    --shadow-2: 0 2px 4px rgba(31, 32, 34, .06), 0 18px 44px -18px rgba(31, 32, 34, .34);

    /* Reading measure for the long-form pages. /warranty and /privacy are the
       two longest documents on the site (1202 and 1207 words) and both ran the
       full 1320px container, which is roughly 150 characters a line - double
       the distance an eye can return across without losing the row. */
    --measure: 68ch;
}

/* ---------------------------------------------------------------------------
   Browser surfaces.

   The parts nobody drew. Selection, the caret, the scrollbar and the underline
   offset all shipped as platform defaults, which means four elements of the
   page belonged to no design system at all - the selection highlight was the
   OS blue on a site whose entire palette is one red.
   --------------------------------------------------------------------------- */
::selection {
    background-color: var(--accent);
    color: #FFFFFF;
}

html {
    caret-color: var(--accent);
    scrollbar-color: var(--rule-strong) var(--page);
}

/* Text links carry a real underline offset rather than the baseline-crossing
   default, which on a mono reference cuts through the descender of every glyph
   that has one. */
a {
    text-underline-offset: .18em;
    text-decoration-thickness: from-font;
}

/* The skip link is the first thing a keyboard reaches on every page, and it was
   the one element on the site still painted Bootstrap 5.1.3's #0d6efd - a blue
   that appears nowhere in this palette. It is invisible until focused, which is
   exactly why it had been missed: nothing that renders on load ever showed it.
   Given the site's own focus treatment instead, so the first thing a keyboard
   user sees is not a stray framework default. */
.visually-hidden-focusable:focus,
.visually-hidden-focusable:focus-within {
    /* position, or the z-index below is inert - it was, and the link relied on
       being first in the document to stay in front of the sticky masthead. */
    position: relative;
    z-index: 100;
    padding: var(--s-3) var(--s-4);
    outline: 2px solid var(--accent);
    outline-offset: 2px;
    background-color: var(--bar);
    color: var(--page);
    font-family: var(--f-mono);
    font-size: .75rem;
    letter-spacing: .08em;
    text-transform: uppercase;
    text-decoration: none;
}

.bg-dark ::selection,
footer ::selection {
    background-color: var(--accent-on-dark);
    color: var(--bar);
}

/* Bootstrap's .fs-* utilities are !important, so overriding them has to be. */
.fs-1 { font-size: var(--t-1) !important; }
.fs-2 { font-size: var(--t-2) !important; }
.fs-3 { font-size: var(--t-3) !important; }
.fs-4 { font-size: var(--t-4) !important; }
.fs-5 { font-size: var(--t-5) !important; }
.fs-6 { font-size: var(--t-6) !important; }

/* Same tokens on the elements, so an h5 used as a font size - which /warranty
   and /privacy both do, ten times - cannot drift away from .fs-5. */
h1, .h1 { font-size: var(--t-1); }
h2, .h2 { font-size: var(--t-2); }
h3, .h3 { font-size: var(--t-3); }
h4, .h4 { font-size: var(--t-4); }
h5, .h5 { font-size: var(--t-5); }
h6, .h6 { font-size: var(--t-6); }

/* The hero lines. .agent-1 carries .display-6 and .agent-2 .display-2, both of
   which were previously overridden to fixed pixels below 576px only. */
.agent-1 { font-size: var(--t-display-sm); }
.agent-2 {
    font-size: var(--t-display);
    animation-delay: 0s;
}

/* Condensed for the top three levels and the hero. This is the range the site
   did not have: with one family and effectively one weight, every heading
   reached for text-uppercase + text-danger, which is why 12 heading treatments
   existed for 4 roles - the system had run out of type and improvised with
   colour. Card titles (h3) and below stay sans, so the shift is confined to
   the levels that are meant to read as headings. */
h1, .h1, h2, .h2,
.display-1, .display-2, .display-3, .display-4, .display-5, .display-6,
.agent-1, .agent-2 {
    font-family: var(--f-condensed);
    font-weight: 700;
    letter-spacing: .01em;
}

/* --t-data: every identifier and every number a buyer reads off the screen or
   copies into a purchase order. tabular-nums so quantities and page numbers do
   not shift width as they change; slashed-zero because that is the entire
   point of the mono here. */
.font-data,
.js-reference,
.quantity-input,
.page-link {
    font-family: var(--f-mono);
    font-feature-settings: 'tnum' 1, 'zero' 1;
    font-variant-numeric: tabular-nums slashed-zero;
}

.bg-gray {
    background-color: var(--page);
}

/* Shown past 150px of scroll by catalog/filters.js, which toggles .is-visible.
   The fade used to be jQuery's fadeIn/fadeOut, which had to check
   prefers-reduced-motion in script because CSS could not see it. As a
   transition it is covered by the blanket rule in 03-transitions.css instead.
   Hidden with visibility rather than display so there is something to
   transition; both keep it out of the accessibility tree and out of the way of
   a pointer. */
.back-to-top {
    position: fixed;
    bottom: 25px;
    right: 25px;
    display: inline-block;
    visibility: hidden;
    opacity: 0;
    width: 48px;
    height: 48px;
    padding: 0;
    border-radius: 50%;
    z-index: 2147483646;
    transition: opacity .15s ease, visibility .15s ease;
}

.back-to-top.is-visible {
    visibility: visible;
    opacity: 1;
}

.back-to-top__icon {
    display: flex;
    align-items: center;
    justify-content: center;
    width: 100%;
    height: 100%;
}

.logo {
    max-width: 152px;
    /* Required now that the img carries width/height attributes: without it both
       dimensions are specified, max-width and max-height clamp independently and
       the 400x185 logo renders as a squashed 152x152. */
    height: auto;
    cursor: pointer;
}

/* ---------------------------------------------------------------------------
   Header navigation.

   A quote list is a utility, so it closes the desktop navigation rather than
   opening it. On a phone, menu, brand and language share the first row;
   the labelled quote action has its own row so translated labels can fit.
   --------------------------------------------------------------------------- */
.site-navigation {
    z-index: 1020;
    color: var(--ink);
    background-color: var(--surface);
    border-bottom: 1px solid var(--rule);
}

.site-navigation__bar {
    display: grid;
    grid-template-columns: 44px minmax(0, 1fr) 44px;
    align-items: center;
    min-height: 60px;
}

.site-navigation__toggle {
    position: relative;
    width: 44px;
    height: 44px;
    padding: 0;
    color: var(--ink);
    border: 0;
    border-radius: 0;
}

.site-navigation__toggle:hover,
.site-navigation__toggle:focus-visible {
    color: var(--accent);
    background-color: var(--page);
}

.site-menu-icon {
    display: block;
}

.site-menu-icon--close,
.site-navigation__toggle[aria-expanded="true"] .site-menu-icon--open {
    display: none;
}

.site-navigation__toggle[aria-expanded="true"] .site-menu-icon--close {
    display: block;
}

.site-navigation .site-navigation__logo {
    display: grid;
    place-items: center;
    justify-self: center;
    min-width: 44px;
    min-height: 44px;
    padding: 0;
}

.site-navigation__logo .logo {
    display: block;
    width: 112px;
    max-width: 100%;
    height: auto;
}

.site-navigation__desktop {
    display: none;
}

.copy-value {
    min-width: 44px;
    min-height: 36px;
    padding: 0 var(--s-2);
    border: 1px solid var(--rule-strong);
    background: var(--surface);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .75rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
}

.copy-value:hover,
.copy-value:focus-visible {
    border-color: var(--accent);
    color: var(--accent);
}

.site-navigation__admin {
    display: none;
}

.admin-navigation-link {
    align-items: center;
    justify-content: center;
    gap: var(--s-2);
}

.admin-notification-badge,
.quote-list-badge,
.dash-rail__badge {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 1.25rem;
    height: 1.25rem;
    padding: 0 .3rem;
    border-radius: 0;
    background-color: var(--accent);
    color: #FFFFFF;
    font-family: var(--f-mono);
    font-size: .6875rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
    line-height: 1;
}

.admin-notification-badge--menu {
    position: absolute;
    top: 0;
    right: 0;
}

.quote-list-control {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    justify-self: end;
    width: 44px;
    min-width: 44px;
    min-height: 44px;
    color: var(--ink);
}

.quote-list-control:hover,
.quote-list-control:focus-visible {
    color: var(--accent);
}

.quote-list-control[aria-current="page"] {
    background-color: var(--page);
    box-shadow: inset 0 -3px 0 var(--accent);
    color: var(--accent);
}

.quote-list-icon {
    position: relative;
    display: inline-flex;
    flex: 0 0 auto;
}

.quote-list-badge {
    position: absolute;
    top: -.45rem;
    right: -.65rem;
}

.quote-list-label {
    display: none;
    font-family: var(--f-condensed);
    font-size: .875rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    white-space: nowrap;
}

.site-navigation__mobile {
    color: #FFFFFF;
    background-color: var(--bar);
    /* The header sticks now, so an open menu taller than the screen would
       hold its last links below the fold for good. It scrolls inside itself
       instead, and stops at its ends rather than scrolling the page. */
    max-height: calc(100svh - 4rem);
    overflow-y: auto;
    overscroll-behavior: contain;
}

.site-navigation__mobile .navbar-nav {
    width: 100%;
    padding: var(--s-2) 0;
}

.site-navigation__mobile .nav-link {
    width: 100%;
    min-height: 48px;
}

.site-navigation__mobile .admin-navigation-link {
    display: flex;
}

.site-navigation__mobile :focus-visible {
    outline-color: var(--accent-on-dark) !important;
}

.site-navigation__contact {
    padding: var(--s-3) var(--s-4) var(--s-4);
    border-top: 1px solid rgba(255, 255, 255, .14);
    text-align: center;
}

.site-navigation__logout {
    padding: 0;
    border-top: 1px solid rgba(255, 255, 255, .14);
}

/* ---------------------------------------------------------------------------
   Language switcher

   The storefront shows EN / PT in a fixed order. The active language uses
   bold text and the other language remains a link with a full touch target.

   Sized and coloured like the other utilities beside it rather than like a
   control of its own, because that is what it is.
   --------------------------------------------------------------------------- */
.language-switcher {
    display: flex;
    align-items: center;
    gap: var(--s-1);
}

/* Both codes stay visible; weight identifies the non-interactive current one. */
.language-switcher--pair .language-switcher__option {
    min-width: 44px;
    font-weight: 400;
}

.language-switcher__current {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-height: 44px;
    padding-inline: var(--s-2);
    font-family: var(--f-condensed);
    font-size: .8125rem;
    letter-spacing: .06em;
    font-weight: 700;
    color: #FFFFFF;
}

.language-switcher--mobile .language-switcher__current {
    font-family: var(--f-mono);
}

.language-switcher__separator {
    color: #CFC9C0;
    font-weight: 400;
}

.language-switcher__icon {
    flex: none;
    opacity: .7;
}

.language-switcher__option {
    display: inline-flex;
    align-items: center;
    align-self: stretch;
    justify-content: center;
    min-width: 34px;
    min-height: 44px;
    padding: 0 var(--s-2);
    appearance: none;
    background: none;
    border: 0;
    color: var(--ink-muted);
    cursor: pointer;
    font-family: var(--f-condensed);
    font-size: .8125rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-decoration: none;
}

.language-switcher__option:hover,
.language-switcher__option:focus-visible {
    color: var(--accent);
    text-decoration: none;
}

/* In the collapsed phone panel the switcher is a utility row like the contact
   block above it, so it takes the same hairline and full-width centring. */
.language-switcher--panel {
    justify-content: center;
    padding: var(--s-2) var(--s-4);
    border-top: 1px solid rgba(255, 255, 255, .14);
}

.language-switcher--panel .language-switcher__option {
    min-height: 48px;
    color: rgba(255, 255, 255, .78);
}

.language-switcher--panel .language-switcher__option:hover,
.language-switcher--panel .language-switcher__option:focus-visible {
    color: var(--accent-on-dark);
}

/* ---------------------------------------------------------------------------
   Admin bar

   White, and the only chrome the dashboard has. It replaces two bands: the dark
   storefront bar and the white logo band beneath it, which between them spent
   about 200px of every admin screen to show a logo and four controls, with an
   empty left half above an empty right half.

   White rather than the storefront's dark bar for two reasons. The mark is
   black and red and needs a light ground - knocking it out to white turns the
   roundel into a smear - and the dashboard is a working surface rather than a
   shopfront, so its chrome should recede. The storefront keeps the dark bar,
   which also makes it obvious at a glance which side of the site you are on.

   It is the <header> itself, not a child of one: .sticky-top is positioned
   within its containing block, so a header taller than the bar used to be what
   gave the bar something to stick over. As the header, its containing block is
   the body and it sticks for the whole page.
   --------------------------------------------------------------------------- */
.site-navigation.site-navigation--admin {
    color: var(--ink);
    background-color: var(--surface);
    border-bottom: 1px solid var(--rule);
}

.site-navigation__bar--admin {
    display: flex;
    align-items: center;
    gap: var(--s-2);
    min-height: 64px;
}

.admin-bar__brand {
    display: inline-flex;
    align-items: center;
    padding: var(--s-2) 0;
}

/* width:auto is required, not tidiness: the img carries width/height attributes
   for its aspect ratio, so without it the specified width wins and max-height
   squashes the logo instead of scaling it. */
.admin-bar__brand .logo {
    width: auto;
    max-width: 160px;
    max-height: 34px;
}

.admin-bar__actions {
    display: flex;
    align-items: center;
    margin-left: auto;
}

.admin-bar__link {
    display: inline-flex;
    align-items: center;
    align-self: stretch;
    gap: var(--s-1);
    min-height: 44px;
    padding: 0 var(--s-3);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .8125rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    text-decoration: none;
    white-space: nowrap;
}

.admin-bar__link--button {
    appearance: none;
    background: none;
    border: 0;
    cursor: pointer;
}

.admin-bar__link:hover,
.admin-bar__link:focus-visible {
    color: var(--accent);
    text-decoration: none;
}

/* Log out is the one destructive-ish action up here, so it is separated rather
   than sitting flush against the language control. */
.admin-bar__logout {
    display: inline-flex;
    align-self: stretch;
    margin-left: var(--s-2);
    border-left: 1px solid var(--rule);
}

.language-switcher--admin {
    align-self: stretch;
    padding-left: var(--s-3);
    border-left: 1px solid var(--rule);
}

.language-switcher--admin .language-switcher__current {
    color: var(--ink);
}

/* A phone has room for the logo, the language and the way out, and not much
   else. The bar wraps as a last resort so it can never push the page wider than
   the viewport, which is what it did at every width below 480px. */
@media (max-width: 575.98px) {
    .site-navigation__bar--admin {
        flex-wrap: wrap;
    }

    .admin-bar__brand .logo {
        max-width: 116px;
    }

    .admin-bar__link {
        padding: 0 var(--s-2);
    }

    .admin-bar__label {
        position: absolute;
        width: 1px;
        height: 1px;
        padding: 0;
        margin: -1px;
        overflow: hidden;
        clip: rect(0, 0, 0, 0);
        white-space: nowrap;
        border: 0;
    }

    .language-switcher--admin {
        padding-left: var(--s-2);
    }

    .language-switcher--admin .language-switcher__option {
        padding: 0 var(--s-1);
    }
}

.site-navigation__phone {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    color: #FFFFFF;
    font-family: var(--f-condensed);
    font-size: 1.125rem;
    font-weight: 700;
}

.site-navigation__phone:hover,
.site-navigation__phone:focus-visible {
    color: var(--accent-on-dark);
}

.site-navigation__contact-meta {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    gap: var(--s-2);
    color: #B4AEA4;
    font-size: .75rem;
    /* The panel already sets the quiet tone for this whole row. */
    --note-ink: currentColor;
}

/* The published cost of a call (DL 59/2021). It is a legal notice, so it is
   sized to be read: the footer's copy used to be 10px, uppercase and on lh-1
   via an inline font-size, which made the one sentence on the page that has to
   be legible the smallest and tightest text on the site. .75rem sentence case
   is what the navigation panel and the contact page were already using.

   The colour is left to the surface - --note-ink where a ground defines one,
   the page's muted ink otherwise - because this line sits on the dark footer,
   the dark navigation panel and the light contact page. */
.call-rate-note {
    display: block;
    margin-top: .15rem;
    color: var(--note-ink, var(--ink-muted));
    font-size: .75rem;
    line-height: 1.4;
}

.site-navigation__contact-meta a {
    color: #FFFFFF;
    font-family: var(--f-condensed);
    font-weight: 700;
    letter-spacing: .06em;
    text-underline-offset: .2em;
}

.site-navigation__logout .btn {
    width: 100%;
    min-height: 56px;
    padding: var(--s-3) var(--s-4);
    border-radius: 0;
    font-family: var(--f-condensed);
    letter-spacing: .04em;
}

.site-navigation__logout .btn:hover,
.site-navigation__logout .btn:focus-visible {
    color: #FFFFFF;
    background-color: var(--bar-raised);
}

/* The mobile bar keeps the same identity and primary action as desktop.
   Giving the quote its own row leaves room for the full Portuguese label and
   a populated badge, while language selection remains outside the menu. */
@media (max-width: 991.98px) {
    .site-navigation:not(.site-navigation--admin) {
        color: #FFFFFF;
        background-color: var(--bar);
        border-bottom-color: var(--bar-raised);
    }

    .site-navigation__bar:not(.site-navigation__bar--admin) {
        grid-template-columns: 44px minmax(0, 1fr) auto;
        gap: var(--s-2);
        padding-block: var(--s-2);
    }

    .site-navigation .site-navigation__toggle {
        display: grid;
        place-items: center;
        color: #FFFFFF;
    }

    .site-navigation .site-navigation__toggle:hover,
    .site-navigation .site-navigation__toggle:focus-visible {
        color: var(--accent-on-dark);
        background-color: var(--bar-raised);
    }

    .language-switcher--mobile {
        gap: 0;
        color: #CFC9C0;
    }

    .language-switcher--mobile .language-switcher__option {
        min-width: 44px;
        color: #FFFFFF;
        font-family: var(--f-mono);
    }

    .language-switcher--mobile .language-switcher__option:hover,
    .language-switcher--mobile .language-switcher__option:focus-visible {
        color: var(--accent-on-dark);
    }

    .quote-list-control {
        grid-column: 1 / -1;
        width: 100%;
        gap: var(--s-3);
        padding: var(--s-2) var(--s-4);
        color: #FFFFFF;
        background-color: var(--accent);
    }

    .quote-list-control:hover,
    .quote-list-control:focus-visible,
    .quote-list-control[aria-current="page"] {
        color: #FFFFFF;
        background-color: var(--accent-deep);
    }

    .quote-list-control[aria-current="page"] {
        box-shadow: inset 0 -3px 0 #FFFFFF;
    }

    .quote-list-control .quote-list-badge {
        color: var(--bar);
        background-color: #FFFFFF;
    }

    .quote-list-label {
        display: inline;
        white-space: normal;
        text-align: center;
    }

    .site-navigation__mobile {
        border-top: 1px solid var(--bar-raised);
    }

    .site-navigation__mobile .navbar-nav {
        padding: var(--s-2) var(--s-3);
    }

    .site-navigation__mobile .nav-link {
        padding-inline: var(--s-4);
        border-bottom: 1px solid var(--bar-raised);
        font-family: var(--f-mono);
        font-size: .875rem;
        letter-spacing: .06em;
        text-align: left !important;
        text-transform: uppercase;
    }

    .site-navigation__mobile .admin-navigation-link {
        justify-content: flex-start;
    }

    .site-navigation__contact {
        text-align: left;
    }

    .site-navigation__contact-meta {
        justify-content: flex-start;
    }

    .site-navigation:not(.site-navigation--admin) :focus-visible {
        outline-color: var(--accent-on-dark) !important;
    }
}

@media (min-width: 992px) {
    .site-navigation {
        color: #FFFFFF;
        background-color: var(--bar);
        border-bottom: 0;
    }

    .site-navigation__bar {
        display: flex;
        min-height: 56px;
    }

    .site-navigation__toggle {
        display: none !important;
    }

    .site-navigation__desktop {
        display: flex;
        margin-right: auto;
    }

    .site-navigation__desktop .nav-link {
        min-width: 112px;
    }

    /* The one filled control in the bar.

       The design's bar ends in two controls of deliberately unequal weight - a
       ghost button holding the basket, and the quote action filled in the accent
       - because they are not the same kind of thing. Everything here had been
       levelled to one quiet register instead, so the site's primary conversion
       read exactly as loud as a language toggle.

       A button inset in the bar rather than another full-height cell: filled and
       stretched it would be the .menu-button slab again, which is the navigation's
       state and not an action's shape. Dashboard and the strip's switcher stay
       quiet, so there is one loud thing up here and it is the one worth pressing. */
    .quote-list-control {
        align-self: center;
        width: auto;
        min-height: 0;
        gap: var(--s-2);
        margin-inline-start: var(--s-4);
        padding: var(--s-3) var(--s-4);
        background-color: var(--accent);
        color: #FFFFFF;
    }

    .quote-list-control:hover,
    .quote-list-control:focus-visible {
        /* --accent-deep, the token the closing band already uses for the accent
           as a surface: a filled control darkens on hover rather than changing
           the colour of text that is no longer the thing being seen. */
        background-color: var(--accent-deep);
        color: #FFFFFF;
    }

    /* On /quote itself. It is still the filled control - moving it to an outline
       here would read as disabled - so the current state is the deeper ground
       plus the underline every other current destination in this bar carries. */
    .quote-list-control[aria-current="page"] {
        background-color: var(--accent-deep);
        box-shadow: inset 0 -3px 0 #FFFFFF;
        color: #FFFFFF;
    }

    /* The badge sits on the accent now, where an accent pill is invisible.
       Inverted: the bar's own ink on white, which is what the mockup's count
       does inside its ghost button. */
    .quote-list-control .quote-list-badge {
        background-color: #FFFFFF;
        color: var(--bar);
    }

    .quote-list-label {
        display: inline;
    }

    /* On the dark desktop bar the switcher joins the utility side behind the
       same left hairline as the Admin destination. */
    /* The switcher sits in the utility strip now, not in the navigation - the
       design puts it up there beside the phone number and the address. It wears
       the strip's own voice, which the strip already sets on itself, so this is
       only the geometry: no full-height cell, no divider, no 56px target,
       because it is a line of 11px chrome rather than a bar cell. */
    .language-switcher--ticker {
        gap: var(--s-1);
    }

    .language-switcher--ticker .language-switcher__icon {
        width: 12px;
        height: 12px;
    }

    .language-switcher--ticker .language-switcher__option {
        color: #CFC9C0;
    }

    .language-switcher--ticker .language-switcher__option:hover,
    .language-switcher--ticker .language-switcher__option:focus-visible {
        color: var(--accent-on-dark);
    }

    /* ---------------------------------------------------------------------
       The dashboard link belongs to the utility cluster, not to the navigation.

       It is marked up as a nav item - it carries .nav-link and .menu-button
       alongside Home, Catalog, About Us and Contact Us - but it sits on the
       other side of the bar, between Request a quote and the language
       switcher. It inherited that markup's behaviour and it showed twice:

       Type. Every other control in the bar is set in the mono, uppercase and
       tracked - the nav items at 16/600, Request a quote at 14/700. This was
       the one label in Archivo 400, sentence case, untracked: "Dashboard"
       among REQUEST A QUOTE and PT.

       Hover. .menu-button:hover floods the item with the accent, which is the
       navigation's own state and right for it. In the utility cluster it is
       the odd one out in the other direction: its two neighbours answer a
       pointer by turning their text --accent-on-dark, so hovering along the
       bar went text, slab, text - and the slab is 112px of solid red arriving
       where the two beside it had shown a colour change.

       Matched to Request a quote, which is what it actually sits next to.
       --------------------------------------------------------------------- */
    .site-navigation__admin {
        display: inline-flex;
        align-self: stretch;
        align-items: center;
        justify-content: center;
        min-width: 112px;
        border-left: 1px solid rgba(255, 255, 255, .14);
        /* Size only. The face, weight, tracking and case come from the bar's
           chrome group in 04-structure.css, which this link is now part of. */
        font-size: .875rem;
    }

    /* One class and one element, so it outranks .menu-button:hover wherever that
       sits in the file. !important on the colour for the reason the .border
       overrides in 04-structure.css carry it: the markup puts Bootstrap's
       .text-white on this link, that utility compiles to `#fff !important`, and
       a same-specificity rule is the only thing that reaches past it. */
    a.site-navigation__admin:hover,
    a.site-navigation__admin:focus-visible {
        background-color: transparent;
        color: var(--accent-on-dark) !important;
    }

    .site-navigation__mobile {
        display: none !important;
    }
}

/* Admin sign-in uses the same page ground, typography and ruled surfaces as
   the storefront and dashboard. */
.admin-login {
    display: grid;
    justify-items: center;
    padding-block: clamp(var(--s-7), 9vh, 6rem);
}

.plane.admin-login__panel {
    width: min(100%, 28rem);
    min-width: 0;
    padding: clamp(var(--s-5), 4vw, var(--s-6));
}

.admin-login__intro {
    margin-bottom: var(--s-6);
    padding-bottom: var(--s-5);
    border-bottom: 1px solid var(--rule);
}

.admin-login__title {
    margin-bottom: var(--s-3);
    font-family: var(--f-condensed);
    font-size: clamp(1.75rem, 3vw, 2rem);
    font-weight: 800;
    line-height: 1.15;
    letter-spacing: -.03em;
    overflow-wrap: anywhere;
}

.admin-login__intro p {
    color: var(--ink-muted);
    font-size: .9375rem;
    line-height: 1.6;
}

.admin-login__form .form-label {
    font-weight: 600;
}

.admin-login__form .form-control {
    min-height: 48px;
    padding: var(--s-3);
    background-color: var(--page);
}

.admin-login__form .form-control:focus {
    background-color: var(--surface);
}

.admin-login__form .btn {
    min-height: 48px;
}

/* A refused sign-in, said once for both fields. It is the form's state rather
   than either input's, so it sits above them and takes the register of the
   drawing rather than of Bootstrap: a hairline box, the accent as a 2px rule on
   the leading edge, a tint no stronger than the one .error-border puts in the
   fields it describes, and no radius or shadow. The text stays ink - red copy
   at this size is the alarm the rule already raises, and it reads worse. */
.admin-login__alert {
    margin-bottom: var(--s-4);
    padding: var(--s-3) var(--s-4);
    border: 1px solid var(--rule);
    border-inline-start: 2px solid var(--accent);
    background-color: #FDF3F3;
    color: var(--ink);
    font-size: .9375rem;
    font-weight: 600;
    line-height: 1.5;
    overflow-wrap: anywhere;
}

.admin-login__return {
    display: flex;
    align-items: center;
    justify-content: center;
    gap: var(--s-2);
    min-height: 44px;
    margin-top: var(--s-4);
    padding-top: var(--s-3);
    border-top: 1px solid var(--rule);
    color: var(--ink-muted);
    font-size: .875rem;
    font-weight: 600;
    text-underline-offset: .2em;
}

.admin-login__return:hover,
.admin-login__return:focus-visible {
    color: var(--ink);
}

.site-navigation--admin .logo-lockup__name {
    color: var(--ink);
}

.site-navigation--admin .logo-lockup__sub {
    border-left-color: var(--rule);
    color: var(--ink-muted);
}

@media (max-width: 575.98px) {
    .admin-login {
        padding: var(--s-6) var(--s-4);
    }
}

.pointer {
    cursor: pointer;
}

.transform-zoom {
    transition: transform .4s; /* Animation */
}

.transform-zoom:hover {
    transition: all 400ms ease;
    -moz-transition: all 400ms ease;
    -ms-transition: all 400ms ease;
    -o-transition: all 400ms ease;
    -webkit-transition: all 400ms ease;
    transform: scale(1.1); /* (150% zoom - Note: if the zoom is too large, it will go outside of the viewport) */
}

/* min-height, not height.

   These are fixed heights on blocks that carry text, and the hero now shows its
   lead paragraph on a phone (it was d-none d-md-flex - the only sentence on the
   homepage that says what is sold, hidden from the visitor most likely to need
   it). At 260px fixed, that paragraph plus the two headline lines plus the CTA
   overflows, and the plate's overflow-hidden then clips whatever did not fit.

   As a floor the block still holds its shape when the background image is the
   only thing in it, and grows rather than clips when the copy is long or the
   text has been scaled up. */
.landing-page-image-small {
    min-height: 238px;
    width: 100%;
    clear: both;
}

.landing-page-image-big {
    min-height: 500px;
    width: 100%;
    clear: both;
}

.product-image {
    object-fit: contain;
    width: 250px;
    height: 250px;
}

/* Every photograph in the catalog is shot on white - the corner pixels of all
   twenty files are 254 or brighter - and the plate the catalog card sets them
   on is not: .js-card .card-media is the warm page ground. So a card with a
   photo drew a second, brighter rectangle inside its own media well, with a
   hard straight edge that means nothing and belongs to the file rather than to
   the part, while the cards still waiting on a photo showed none. In a grid
   the two kinds of card stopped reading as the same object.

   Multiply fixes it in the browser instead of asking for twenty re-cut files.
   White multiplied by the ground IS the ground, so the shot's own background
   disappears into the plate exactly, at whatever value the plate happens to be;
   every other pixel is scaled by the ground's channels, which at #F4F1EC is a
   ~5% darkening that warms the part into the surface it now sits on. This is
   also why the rule can stay unconditional: where the ground is still white -
   the stand-in in the quote table's cell - multiplying by white is the
   identity, so nothing there moves.

   The brightness is what closes the last 4%. Not every file is a clean 255:
   the stand-in is 246 and two of the JPEGs are 254, and multiply leaves those
   as a soft grey cloud around the part - the hard edge gone but a smudge where
   it was. A 1.04 lift clips anything from 246 up to pure white, so those
   backgrounds vanish too, and on the part itself it lands within a percent of
   cancelling the darkening multiply just applied. It costs the top of the
   specular highlights on chrome, which is a cheaper thing to spend than the
   edge.

   Three selectors because the three surfaces name their image differently: the
   catalog card and the homepage strip set .product-image, the product page's
   own photo carries only layout classes so it is reached through its panel, and
   the stand-in wraps a bare img of its own. All of them are img, which is what
   excludes the part drawing a product with no photograph at all falls back to:
   that one is a line drawing that already inherits the surface's own ink, and
   there is no white in it to remove. Nothing here is photographed on a dark
   ground, which is the one case multiply would flatten. */
img.product-image,
.product-detail-media img,
.product-image-stand-in img {
    filter: brightness(1.04);
    mix-blend-mode: multiply;
}

/* The box a part drawing is centred in, when a product has neither a
   photograph nor a brand/category stand-in - see components/product-image and
   includes/generic/partglyph.

   It used to be a bordered tile stacking AHDP over PHOTO PENDING over the
   reference, which is why the rules for those three lines are gone with them.
   No border and no fill now: the drawing is the content, and a box around it
   would be the one thing in a grid of photographs still shaped like a form
   field. The sizes below are all this has left to do - it is the same 250px
   the photographs take, so a row of cards keeps one media height whichever
   kind of picture each one landed on. */
.product-image-placeholder {
    display: flex !important;
    align-items: center;
    justify-content: center;
    width: min(100%, 20rem);
    aspect-ratio: 1;
    padding: var(--s-4);
    color: var(--ink-muted);
}

/* Not 100%: a drawing on a 120-unit frame reads as a diagram of a part only
   with air around it, and at full bleed the wheel's rim would touch the media
   plane's own hairline. The design's plates set their glyphs at 70%. */
.part-glyph {
    width: 70%;
    height: 70%;
}

.product-image-placeholder.product-image {
    width: 250px;
    height: 250px;
}

.product-image-placeholder.table-image {
    width: 100px;
    height: 100px;
    padding: var(--s-2);
}

.quote-empty-state__copy {
    max-width: var(--measure);
}

.text-feedback-success {
    color: var(--feedback-success) !important;
}

/* ---------------------------------------------------------------------------
   The brand rail.

   DEUTZ, Perkins, Cummins and Detroit Diesel are the strongest trust signal
   this business has, and they rendered at opacity:50% + grayscale(100%) - a
   treatment the rest of the page uses to mean "unavailable". They are also
   links to the brand landing pages the site was built to rank, so the loudest
   proof and the highest-intent internal links were both drawn as if disabled.

   The desaturation was doing real work: the source logos are not a uniform
   grey, and it made eight unrelated files read as one set. That job moves to
   the geometry instead - one ruled cell per logo, identical size, identical
   optical height, aligned on a grid. Sameness of frame, not sameness of colour,
   so the set reads as a set and each mark still reads as itself.

   A wrapping flex rail lets every row close against the right rule even when
   the database-backed logo count is not divisible by the available columns.
   The final row shares its remaining width instead of exposing an unframed
   white hole beside the last logo.
   --------------------------------------------------------------------------- */
.brand-rail {
    /* A grid, not a wrapped flex row. With flex the final row stretched its
       items to fill the width, so the second line of marks sat in cells half
       again as wide as the first line's - fourteen brands reading as two
       different sets.

       A fixed column count, not auto-fill. auto-fill sizes the columns from the
       viewport and lets the row count fall where it may, which at 1440px was
       nine columns for fourteen brands: a full row, then five and four cells of
       nothing. The wall is a claim about range, and a rectangle makes that claim
       where a shape with a bite out of the corner makes it look like the set ran
       out. Seven columns and fourteen brands is two full rows; below the md
       breakpoint two columns and seven rows is the same rectangle stood on its
       end. Both divide the count exactly - see HomepageController's
       BRAND_WALL_LIMIT, which is the other half of this. */
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    border-top: 1px solid var(--rule);
    border-left: 1px solid var(--rule);
    /* The page ground, not white. It shows through as the hairlines between the
       cells, and it is what the rail would fall back to if a row ever did run
       short - on white a gap in the set reads as a blank slab bolted to it,
       where on the page ground it reads as grid with nothing in it yet. */
    background-color: var(--page);
}

/* The column count comes from brands.blade.php as --rail-cols and
   --rail-cols-md, worked out from how many brands the dashboard features, so
   the rail is always a closed rectangle: eight brands are one row of eight on
   a desktop and two rows of four on the md band. Seven is the fallback the
   rail had before the count was set per page. Below md the rail is one
   swiped row instead (further down), because seven columns of a 360px phone
   is 47px a cell and neither a wordmark nor "CAT - CATERPILLAR" survives that. */
@media (min-width: 768px) {
    .brand-rail {
        grid-template-columns: repeat(var(--rail-cols-md, 7), minmax(0, 1fr));
    }
}

@media (min-width: 992px) {
    .brand-rail {
        grid-template-columns: repeat(var(--rail-cols, 7), minmax(0, 1fr));
    }
}

.brand-rail__cell {
    display: grid;
    place-items: center;
    min-height: 5rem;
    padding: var(--s-3) var(--s-4);
    border-right: 1px solid var(--rule);
    border-bottom: 1px solid var(--rule);
    /* The cells are white; the rail behind them is the page. That is what makes
       the short last row read as empty grid rather than as a white slab, while
       the marks themselves - two of which carry their own white backgrounds -
       still sit on the ground they were drawn for. */
    background-color: var(--surface);
    color: var(--ink-muted);
    text-decoration: none;
    transition: background-color 180ms ease;
}

/* The cells that finish a short last row (brands.blade.php). The page ground,
   not the cell white, so they read as grid with nothing in it rather than as
   a brand that failed to load. */
.brand-rail__cell--filler {
    background-color: transparent;
}

@media (max-width: 767.98px) {
    .brand-rail__cell--filler {
        display: none;
    }
}

.brand-rail__cell:hover,
.brand-rail__cell:focus-visible {
    background-color: var(--page);
}

/* The default cell: the brand's name, where there is no logo file.

   Set as the wall's own type, in the mono register the rest of the page's
   chrome uses, rather than as an apology for a missing picture. Two things
   follow from the cell it has to live in - 8rem wide, shared with logos that
   are optically 3.75rem tall:

   Size. The design sets these at 16px, which is right for its own eight short
   marques; this catalog holds GMB UNIVERSAL JOINTS and CAT - CATERPILLAR, and
   at 16px those set three and four lines in a 96px column and drive the row
   taller than the logos beside them. At .8125rem the longest of them is two.

   Weight and colour. A wordmark is a drawn, solid thing, so 600 in full ink is
   what stops a name cell reading as the faint one beside it. */
.brand-rail__name {
    font-family: var(--f-mono);
    font-size: .8125rem;
    font-weight: 600;
    line-height: 1.3;
    letter-spacing: .06em;
    text-align: center;
    text-transform: uppercase;
    color: var(--ink);
    /* The names are the catalog's own, and some are longer than any column this
       grid will offer them. */
    overflow-wrap: break-word;
    hyphens: none;
}

.brand-rail__cell:hover .brand-rail__name,
.brand-rail__cell:focus-visible .brand-rail__name {
    color: var(--accent);
}

.logo-brands {
    display: block;
    width: auto;
    max-width: 100%;
    /* Optical height, not width: a wordmark and a roundel of the same width read
       at wildly different weights, and max-width was the only constraint before,
       so the tallest logo set the row height for all of them. */
    max-height: 3.75rem;
    height: auto;
    object-fit: contain;
    margin: 0 auto;
    transition: transform 180ms ease-out;
}

/* These cells are real category entrances, not a decorative client wall. A
   two-pixel lift is enough to acknowledge the link without making fourteen
   unrelated logo files pulse or continuously animate. */
.brand-rail__cell:hover .logo-brands,
.brand-rail__cell:focus-visible .logo-brands {
    transform: translateY(-.125rem) scale(1.015);
}

.brand-rail__empty {
    flex: 1 0 100%;
    padding: var(--s-5);
    border-right: 1px solid var(--rule);
    border-bottom: 1px solid var(--rule);
}

/* Seven columns of a 768px container is 103px a cell, and the cell's own
   var(--s-4) inset takes 32 of them. The names are what feel it - "CAT -
   CATERPILLAR" sets three lines at that width - so the inset comes in to the
   step below for the band where the columns are tightest. (This replaced a
   flex-basis on the same selector, left behind when the rail stopped being a
   flex row and became a grid, where flex-basis does nothing at all.) */
@media (min-width: 768px) and (max-width: 991.98px) {
    .brand-rail__cell {
        padding-inline: var(--s-2);
    }
}

@media (min-width: 1200px) and (max-width: 1399.98px) {
    .brand-rail__cell {
        flex-basis: 9rem;
    }
}

/* All available artwork stays in the document. On a phone it becomes one
   compact swipeable row rather than seven or eight stacked rows of logos before
   the visitor reaches the catalog. */
@media (max-width: 767.98px) {
    .brand-rail {
        display: grid;
        flex-wrap: initial;
        grid-template-columns: none;
        grid-auto-flow: column;
        grid-auto-columns: minmax(8.5rem, 44vw);
        overflow-x: auto;
        scroll-snap-type: x mandatory;
        scrollbar-color: var(--rule-strong) transparent;
        scrollbar-width: thin;
    }

    .brand-rail__cell {
        flex: initial;
        scroll-snap-align: start;
    }
}

.bg-red {
    background-color: var(--accent);
}

/* Removed .bg-black - #363945 appeared in no rendered public HTML. The primary
   ink and dark bar now share the same AHDP charcoal token. */

.bg-white {
    background-color: white;
}

.font-primary {
    color: var(--ink);
}

.font-primary:hover {
    color: var(--ink);
}

.list-item-dropdown {
    transition: transform .4s;
}

.text-danger {
    color: var(--accent) !important;
}

/* Bootstrap lays buttons out as inline blocks. Once the site's 44px minimum
   height makes one taller than its padding and line-height require, that extra
   room is left below the line box and the label reads a little high. Making the
   button itself the centering context distributes the room evenly without
   tuning each size, icon, or translated label separately. */
.btn {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    text-align: center;
    /* Uppercase and tracked, like every other action in the design. Buttons
       were the last thing on the site still set in sentence-case body copy, so
       an action read as a phrase rather than as a control - "Browse Parts
       Catalog" sitting in the hero at the same weight as the sentence above it.

       .06em rather than the mono labels' .1em: this is the sans at 600, and the
       looser tracking the mono needs would pull a Portuguese label - "Pedir
       orçamento" - past the width its English counterpart was laid out in. */
    font-weight: 600;
    letter-spacing: .06em;
    text-transform: uppercase;
}

/* Shared brand colors keep actions consistent across public and admin pages. */
.btn-danger {
    background-color: var(--accent) !important;
    border-color: var(--accent);
}

/* Keep Bootstrap interaction and disabled states in the homepage palette. */
.btn-danger:hover,
.btn-danger:focus,
.btn-danger:active,
.btn-danger.active,
.btn-check:checked + .btn-danger,
.btn-check:active + .btn-danger,
.show > .btn-danger.dropdown-toggle {
    background-color: var(--accent-deep) !important;
    border-color: var(--accent-deep);
}

.btn-danger:disabled,
.btn-danger.disabled {
    background-color: var(--accent) !important;
    border-color: var(--accent);
}

.btn-danger:focus,
.btn-outline-danger:focus,
.btn-check:focus + .btn-danger,
.btn-check:focus + .btn-outline-danger {
    box-shadow: 0 0 0 .25rem color-mix(in srgb, var(--accent) 50%, transparent);
}

.btn-outline-danger:disabled,
.btn-outline-danger.disabled {
    color: var(--accent);
    background-color: transparent;
}

/* The outline pair never left Bootstrap's #dc3545, which is a lighter red than
   the brand's: as button text on --page it is 4.02:1 and fails AA, where
   --accent is 4.85:1 and passes. It showed on the product page's "Remove from
   quote", the only place this button carries body-size text - the catalog's
   filter toggle escaped notice because it is bold enough to be scored as large
   text. The filled and outline halves of one action should be the same red in
   any case. */
.btn-outline-danger {
    border-color: var(--accent);
    color: var(--accent);
}

.btn-outline-danger:hover,
.btn-outline-danger:focus,
.btn-outline-danger:active,
.btn-outline-danger.active,
.btn-check:active + .btn-outline-danger,
.show > .btn-outline-danger.dropdown-toggle,
.btn-check:checked + .btn-outline-danger {
    border-color: var(--accent);
    background-color: var(--accent);
    color: var(--feedback-on-color);
}

.btn-destructive {
    border-color: var(--feedback-error);
    background-color: var(--feedback-error);
    color: var(--feedback-on-color);
}

.btn-destructive:hover,
.btn-destructive:focus-visible {
    border-color: #70171d;
    background-color: #70171d;
    color: var(--feedback-on-color);
}

.line-height-control {
    line-height: 1 !important;
}

.list-item-dropdown:hover {
    transition: all 400ms ease;
    -moz-transition: all 400ms ease;
    -ms-transition: all 400ms ease;
    -o-transition: all 400ms ease;
    -webkit-transition: all 400ms ease;
    color: var(--accent);
}

.list-item-dropdown:hover > a {
    transition: all 400ms ease;
    -moz-transition: all 400ms ease;
    -ms-transition: all 400ms ease;
    -o-transition: all 400ms ease;
    -webkit-transition: all 400ms ease;
    color: var(--accent);
}

.text-red {
    color: var(--accent);
}

/* Descendant, not direct child: the image is wrapped in a <picture> now so
   the WebP source can sit beside it, and `>` stopped matching. */
.hover-card-effect img {
    transition: transform 200ms ease-out;
}

/* The `z-index: -1` that used to be here is gone.

   A negative z-index can paint the image behind the card's own white surface,
   making the product disappear when the link is hovered. */
.hover-card-effect:hover img {
    transform: scale(1.03);
}

.menu-button {
    -webkit-transition: background-color 200ms linear;
    -ms-transition: background-color 200ms linear;
    transition: background-color 200ms linear;
}

.menu-button:hover {
    background-color: var(--accent);
    -webkit-transition: background-color 200ms linear;
    -ms-transition: background-color 200ms linear;
    transition: background-color 200ms linear;
}

/* The old greys differed by only 1.51:1 - the "you are here" state
   was effectively invisible, so the accent underline was meant to carry it.
   Measured, that replacement landed at 2.83:1 and was under the same 3:1 floor,
   which left the indicator invisible in a second way. The lightened accent
   clears it at 4.32:1; the fill stays as a supporting cue. */
.menu-button-active {
    background-color: var(--bar-raised);
    box-shadow: inset 0 -3px 0 var(--accent-on-dark);
}

.menu-button-active:hover {
    background-color: var(--bar-raised);
}

/* Every interactive element gets a visible ring. :focus-visible keeps it off
   mouse clicks, which is what the old blanket `outline: none` was reaching for -
   it just took the keyboard ring with it.

   !important because Bootstrap's own `.btn:focus { outline: 0 }` matches at the
   same specificity and would otherwise win on any button carrying a .btn class. */
:focus-visible,
.btn:focus-visible,
.page-link:focus-visible,
.form-control:focus-visible,
.form-check-input:focus-visible {
    outline: 2px solid var(--accent) !important;
    outline-offset: 2px;
}

/* The ring is 2.83:1 against the header and the cookie banner, which is where
   a keyboard user meets it first. Same treatment as .bg-dark .text-muted.

   .table-dark is the third dark surface and was missing from this list: it is
   #212529 like the other two but matches neither selector, so the two column
   sort buttons in the dashboard's table head - the only sorting controls in the
   app - drew the #CD212A ring at that same 2.83:1, under the 3:1 floor a
   non-text indicator has to clear. */
.bg-dark :focus-visible,
.site-footer :focus-visible,
.cookie-consent-banner :focus-visible,
.table-dark :focus-visible {
    outline-color: var(--accent-on-dark) !important;
}

/* Bootstrap paints its own focus state underneath the ring above. More
   importantly, most fields carry .regular-border with an !important grey edge,
   so their red outline used to sit outside that edge rather than replacing it.
   The masthead already solves this by drawing its focus ring inward; use that
   same single-edge treatment for every field. The explicit invalid selectors
   also beat Bootstrap's more-specific red focus glow. */
.form-control:focus,
.form-select:focus,
.form-control.is-invalid:focus,
.form-select.is-invalid:focus,
.was-validated .form-control:invalid:focus,
.was-validated .form-select:invalid:focus,
.form-check-input:focus {
    box-shadow: none;
}

.form-control.is-invalid,
.form-select.is-invalid,
.was-validated .form-control:invalid,
.was-validated .form-select:invalid,
.form-control:focus,
.form-select:focus {
    border-color: var(--accent) !important;
}

.form-control:focus-visible,
.form-select:focus-visible {
    outline-offset: -2px;
}

/* Bootstrap's blue also lands on the one control whose border is not overridden
   by a utility. */
.form-check-input:focus {
    border-color: var(--accent);
}

/* And on the switch's knob: Bootstrap swaps it for a light-blue circle while an
   unticked switch has focus, which is every time it has just been switched off
   with the mouse. Its own resting grey knob instead; the red edge above already
   says it has focus. */
.form-switch .form-check-input:focus:not(:checked) {
    background-image: url("data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'%3e%3ccircle r='3' fill='rgba%280, 0, 0, 0.25%29'/%3e%3c/svg%3e");
}

/* Inside an .input-group the controls are flush against each other, so a ring
   drawn 2px outside the search field runs underneath the button beside it -
   and .btn:focus{z-index:3} lifts that button over it. Drawn inset, the ring
   stays within the control it belongs to and the two stop colliding. */
.input-group > :focus-visible {
    outline-offset: -2px;
    position: relative;
    z-index: 5;
}


/* FADE IN EFFECT FOR HOME PAGE TEXT */

/* Was translateX(-100%) inside an overflow-hidden wrapper: the h1 started a
   full line-width off to the left and was clipped for the whole 0.3s, so the
   page's largest text rendered as a fragment before it settled. A short offset
   reads as the same move without ever leaving the box. */
@keyframes fade-in-left {
    from {
        opacity: 0;
        transform: translateX(-2rem);
    }
    to {
        opacity: 1
    }
}

@keyframes fade-in-right {
    from {
        opacity: 0;
        transform: translatex(100%);
    }
    to {
        opacity: 1
    }
}

@keyframes fade-in-bottom {
    from {
        opacity: 0;
        transform: translateY(2rem);
    }
    to {
        opacity: 1
    }
}

.appear-bottom {
    opacity: 1;
    animation-delay: 0s;
}

.appear-right {
    opacity: 1;
    animation-delay: 0s;
}

.agent-1, .agent-2, .agent-3 {
    opacity: 1;
}

.agent-3 {
    animation-delay: 0s;
}

.hover-category:hover {
    background-color: var(--accent);
    color: white;
    -webkit-transition: background-color 200ms linear;
    -ms-transition: background-color 200ms linear;
    -o-transition: background-color 200ms linear;
    transition: background-color 200ms linear;
}

.hover-carousel-button {
    transition: transform .4s; /* Animation */
    min-width: 44px;
    min-height: 44px;
}

.hover-carousel-button:hover {
    transition: transform .4s;
    transform: scale(1.4);
}

.badge-new {
    position: absolute;
    top: 0px;
    right: 0px;
}

.form-check-label {
    transition: transform 200ms; /* Animation */
    flex: 1 1 auto;
}

.form-check-label:hover {
    transition: transform 200ms ease;
    -moz-transition: all 200ms ease;
    -ms-transition: all 200ms ease;
    -o-transition: all 200ms ease;
    -webkit-transition: all 200ms ease;
    color: var(--accent);
}

.form-check-input:checked {
    background-color: var(--accent);
    border-color: var(--accent);
}

.moving-right {
    position: relative;
    transition: transform 0.3s ease;
    transform: translateX(0px);
}

.moving-right:hover {
    color: white;
    transform: translateX(10px);
}

.text-hover {
    -webkit-transition: color 0.3s; /* For Safari 3.0 to 6.0 */
    transition: color 0.3s; /* For modern browsers */
}

.text-hover:hover {
    color: var(--accent);
}

.image-upload > input {
    display: none;
}

/* Removed .focused-red:focus - no element in resources/views or public/js
   carries the class. It was also the file's only `outline: none` (the thing the
   :focus-visible work above exists to undo) and its only non-brand red, the CSS
   keyword `red` at #ff0000. */

/* Was `2px solid #F6F6F6` on inputs that are themselves #F6F6F6, sitting on a
   white plate: the quote form's three fields and the contact form's four had a
   border the exact colour of their own fill, so the only thing marking a text
   input was a faint grey rectangle with no edge. Same hairline as every other
   boundary on the site. */
.regular-border {
    border: 1px solid var(--rule) !important;
}

/* Has to sit after .regular-border, not before it. login.blade.php puts both on
   the same input - `regular-border @error(...) error-border @enderror` - and the
   two are single-class rules that both carry !important, so the later one in
   this file wins outright. This block used to sit above, which meant the error
   border never actually rendered on the login form: the red rectangle on a
   failed sign-in was the :focus-visible ring on the autofocused field, and it
   looked identical whether or not the credentials had been rejected.

   That is also the second problem. The ring is 2px of #CD212A drawn 2px outside
   the control, so matching it in colour is not enough to be distinguishable.
   The error state keeps a tint after focus moves away, and the adjacent error
   copy supplies the non-colour cue without turning the field into a side tab. */
.error-border {
    border: 1px solid var(--accent) !important;
    /* #CD212A at ~4% over white. Holds against both the #F6F6F6 the login and
       filter fields carry and the plain white of the modal's. */
    background-color: #FDF3F3 !important;
}

/* The send button while the form is not fillable yet.

   Both forms have always validated - `required` is on every mandatory field and the
   browser refuses the submit - but the button gave no sign of it: full opacity,
   pointer cursor, and the only feedback a bubble on one field that vanishes. So
   pressing it read as nothing happening.

   Not the `disabled` attribute, which is why this is a class: disabled takes the
   button out of the tab order and announces no reason, on the one control these
   pages exist for. Pressing it while incomplete is how someone asks what is
   missing, and email/main.js answers by naming every field at once. The cursor
   stays a pointer for the same reason - it is still a button. */
.btn-danger.btn-incomplete {
    background-color: var(--page) !important;
    border-color: var(--rule-strong) !important;
    color: var(--ink-muted) !important;
    opacity: 1;
}

.btn-danger.btn-incomplete:hover,
.btn-danger.btn-incomplete:focus-visible {
    background-color: var(--surface) !important;
    border-color: var(--ink-muted) !important;
    color: var(--ink) !important;
}

/* The backstop for any control that is not .regular-border, which shipped
   Bootstrap's #dee2e6 - a fourth grey.

   It used to catch the catalog's sort select and its two filter fields; both now
   carry the same .regular-border.bg-gray.py-3 as every other field on the site,
   so what is left here is the masthead's part search, where the flush submit
   button beside it already draws the edge. */
.form-control,
.form-select {
    border-color: var(--rule);
}

/* The file picker, which is the one control on the site that had no face.

   A file input draws two things. The field box is ours - .form-control and
   .regular-border dress it like every other field - but the button inside it is
   drawn by the browser and inherits none of that, and this build of Bootstrap
   carries no ::file-selector-button rule to fall back on. So all six upload
   fields rendered a #EFEFEF rectangle with a #767676 border, a 3px radius and
   13.33px of system font: four values the palette does not contain, sitting in
   the middle of forms where everything else was ours. The worst of them is on
   /contact-us, directly under a styled textarea, in the path a buyer takes to
   send us a photograph of the part they want.

   06-admin.css had already noticed the control was a special case - it exempts
   [type=file] from the padding every other field takes - without ever giving it
   one.

   The button takes the secondary action's voice rather than the accent's:
   picking a file is a step on the way to sending the form, not the sending. It
   is inset rather than a full-height segment flush to the field's edge, because
   the contact form's field carries .py-3, and a Bootstrap spacing utility is
   !important - matching the field's inner height would mean answering that with
   an !important of our own, and the pill reads correctly under any padding.

   Only the button is reachable from CSS. The filename beside it is painted by
   the browser using the input's own font and colour, which is why those two are
   set on the field: it puts "nameplate.jpg" in Archivo and the muted ink rather
   than in 13.33px of Segoe UI. Showing the size, or offering to clear a chosen
   file, needs script and is not attempted here. */
.form-control[type="file"] {
    color: var(--ink-muted);
    font-size: .875rem;
}

.form-control[type="file"]::file-selector-button {
    margin-inline-end: var(--s-3);
    padding: var(--s-2) var(--s-4);
    border: 1px solid var(--rule-strong);
    border-radius: 0;
    background-color: var(--page-sunken);
    color: var(--ink);
    font-family: var(--f-sans);
    font-size: .8125rem;
    font-weight: 600;
    letter-spacing: .06em;
    text-transform: uppercase;
    transition: background-color 150ms linear, border-color 150ms linear;
}

.form-control[type="file"]:hover::file-selector-button {
    border-color: var(--ink-muted);
    background-color: var(--rule);
}

/* The field's own focus ring is drawn by the :focus-visible rule above, and it
   marks the whole control. The button keeps a state of its own for the pointer
   press, which the ring does not describe. */
.form-control[type="file"]::file-selector-button:active {
    background-color: var(--rule-strong);
}

.nav-pills .nav-link.active, .nav-pills .show>.nav-link {
    color: #fff;
    background-color: var(--ink);
    border-radius: 0px;
}

.circle-icon {
    background: Gainsboro;
    color: white;
    width: 180px;
    height: 180px;
    text-align: center;
    line-height: 100px;
    vertical-align: middle;
    padding: 50px;
}

.circle-icon:hover {
    cursor: pointer;
    background: Silver;
}

.image-upload {
    border-style: dashed;
    border-color: #636b6f;
}

.quantity-control {
    display: flex;
    align-items: center;
    justify-content: space-between;
    width: fit-content;
    background: #F6F6F6;
    padding: .5rem 0.4rem;
}

/* These are the controls where the visitor commits to what they are asking to be
   quoted, and they measured 15x18 on a phone - directly beside a 16x16 remove
   with no undo behind it. 44px is the floor for a thumb. */
.quantity-btn {
    background: transparent;
    border: none;
    margin: 0;
    padding: 0;
    min-width: 44px;
    min-height: 44px;
    display: inline-flex;
    align-items: center;
    justify-content: center;
    cursor: pointer;
}
.quantity-btn svg {
    width: 16px;
    height: 16px;
}
.quantity-remove {
    min-width: 44px;
    min-height: 44px;
}
.quantity-input {
    user-select: none;
    text-align: center;
    /* Was 20px, which clipped the number out of its own field - Firefox renders
       the spinner inside that width and leaves nothing for the digit. */
    width: 3rem;
    -moz-appearance: textfield;
    background: transparent;
    border: none;
}
.quantity-input::-webkit-inner-spin-button,
.quantity-input::-webkit-outer-spin-button {
    -webkit-appearance: none;
    margin: 0;
}

.corner-ribbon {
    font-weight: bold;
    width: 300px;
    background: var(--accent);
    position: absolute;
    top: 5px;
    right: -130px;
    text-align: center;
    line-height: 30px;
    letter-spacing: 1px;
    /* No colour here: card.blade.php puts .text-white on the same element and
       Bootstrap's .text-white is !important, so the #f0f0f0 that used to sit
       here never rendered. Removing it also drops the file's fifth spelling of
       white. The ribbon measures 5.46:1 on #CD212A either way. */
    transform: rotate(45deg);
    -webkit-transform: rotate(45deg);
}

.remove-dropdown-arrow::-ms-expand {
    display: none;
}

td, th {
    vertical-align: middle;
}

/* contain, not cover: the thumbnails are a mix of square photos and the wider
   "image not available" placeholder, and cover cropped the placeholder's sides
   hard enough that every product without a photo read "MAGE NOT AVAILABL". A
   parts thumbnail wants the whole part in frame anyway. */
.table-image {
    object-fit: contain;
    width: 100px;
    height: 100px;
    background-color: transparent;
}

/* No min-height at all now.

   It was 450px (400 below xxl) to make the cards in a row match, which is a
   thing the grid already does: the parent column is align-items-stretch, so
   height:100% here matches the tallest card in the row exactly, with no value to
   guess and none of the ~100px of dead space a guessed floor leaves under a
   short title. The actions are pushed to the bottom with margin-top:auto in
   .js-card-actions below, so the CTAs line up across a row even when the titles
   above them wrap differently.

   overflow is no longer hidden here either - it moved to .card-media, which is
   the only part of the card the rotated NEW ribbon can escape from. On the card
   it clipped any title long enough to wrap.

   max-width keeps the 300px the grid was drawn around, while width lets the card
   shrink on a narrow phone rather than overflow it. */
.js-card {
    height: 100%;
    width: 100%;
    max-width: 300px;
    background-color: var(--surface);
    border: 1px solid var(--rule);
    transition: border-color 200ms ease, box-shadow 200ms ease;
}

.js-card:hover,
.js-card:focus-within {
    border-color: var(--rule-strong);
    box-shadow: var(--shadow-1);
}

/* The shared 300px cap suits the homepage strip. The catalog has an explicit
   responsive column count, so its track defines the card width at every
   breakpoint; filling it avoids cards floating inside differently sized cells. */
#productslist .js-card {
    max-width: none;
}

/* The image plane. The photo used to sit directly on the card with the body
   text starting straight under it, so a product shot on white against a body on
   white had no boundary - the card read as one undivided rectangle and the eye
   had nothing to anchor the scan to. */
.card-media {
    position: relative;
    overflow: hidden;
    /* The backdrop the photo multiplies against is this plane's own fill and
       nothing behind it. Without the isolation the blend reaches down to
       whatever the nearest stacking context paints, so the well would stop
       being what decides how the shot lands. */
    isolation: isolate;
    /* The card body is `flex: 1 1 auto`, so without this the media plane is the
       only shrinkable item in the column and a tall body squeezes the photo. */
    flex: 0 0 auto;
    display: flex;
    align-items: center;
    justify-content: center;
    padding: var(--s-5) var(--s-4);
    border-bottom: 1px solid var(--rule);
    background-color: var(--surface);
}

/* The reference, set as the card's lead line.

   A buyer's job on this site is matching a part number. The card used to open
   with "MAZDA - FILTERS" over a title reading "MAZDA FILTERS" - the same two
   words twice - and put the reference last, smallest, behind a "Reference:"
   label that took half the line. This is the same three facts in the order the
   task needs them, with the label kept for screen readers only: the mono voice
   and the slashed zero are what identify it visually. */
.card-reference {
    font-size: 1.0625rem;
    font-weight: 600;
    line-height: 1.2;
    color: var(--ink);
    word-break: break-word;
}

/* .cell-meta is the same role in the dashboard's product rows, which show the
   same brand and category under the same title. Sharing the rule is the point:
   it is what stops the two surfaces drifting apart again. */
.card-taxonomy,
.dash-table .cell-meta {
    /* Mono, with the rest of the catalog's metadata. This is the caption under
       a part number that is already set in the mono a line above it, and the
       two reading in different faces was the last place the card mixed voices. */
    font-family: var(--f-mono);
    font-size: .6875rem;
    letter-spacing: .1em;
    text-transform: uppercase;
    color: var(--ink-muted);
}

.js-card-actions {
    margin-top: auto;
}

/* ---------------------------------------------------------------------------
   Product stand-in image

   Shown when a part has no photograph of its own but the dashboard has said
   what parts of its kind look like.

   It carried a caption bar with the reference over it, on the reasoning that a
   card must not look like a photo of the exact part. Every surface that renders
   this component already prints the reference in text beside the picture, and
   the catalog card leads with it - so the bar repeated the same string one line
   above itself. The accessible name still says the photo is representative.

   No background either. That was borrowed from .product-image-placeholder,
   which is a grey bordered tile precisely because it is NOT an image; a
   stand-in is a photograph and belongs on the same ground as .product-image,
   which sets none - so its letterboxing shows the card's own surface instead of
   a slab that only some cards in the grid have.
   --------------------------------------------------------------------------- */
.product-image-stand-in {
    position: relative;
    display: block;
    overflow: hidden;
}
.product-image-stand-in img,
.product-image-stand-in > svg {
    display: block;
    width: 100%;
    height: 100%;
    object-fit: contain;
}

/* The brand badge's artwork (includes/generic/brandbadge-defs), defined once
   per page for every badge to <use>. Not display:none, which stops <use>
   drawing it in some engines: taken out of the flow instead, so the empty
   inline box it would otherwise be cannot nudge the line it sits on. */
.brand-badge-defs {
    position: absolute;
    width: 0;
    height: 0;
    overflow: hidden;
}

.product-image-stand-in__caption {
    position: absolute;
    inset: auto 0 0;
    padding: .25rem .375rem;
    background: var(--page-sunken);
    color: var(--ink);
    font-family: var(--f-sans);
    font-size: .75rem;
    line-height: 1.3;
    text-align: center;
}

/* ---------------------------------------------------------------------------
   The masthead band.

   Its colour used to be a .bg-white utility in the markup, which meant the
   header was two different objects stacked: a dark navigation bar sitting on a
   white search band. At 992px the nav already inverts to --bar; the band now
   inverts with it, so above that width the whole header reads as one dark
   region rather than as a strip glued to a plate.

   Below 992px nothing changes. There the nav is light, the masthead logo is
   hidden and the bar carries its own - inverting only the band would leave a
   white bar above a dark one.
   --------------------------------------------------------------------------- */
.site-masthead {
    background-color: var(--surface);
}

@media (min-width: 992px) {
    /* The logo row stays light.

       It was inverted with the navigation above it, which meant a red-and-black
       mark on a near-black bar - so the wordmark and half the roundel vanished.
       The fix at the time was a paper plate behind it, and a white box sitting
       inside a dark bar is worse than the problem: it reads as a sticker, not
       as a masthead.

       The design solves this by not using a raster mark at all - it builds its
       logo from a solid tile and type. This mark is a real asset and not ours
       to rebuild, so the row it sits in gives way instead. The result is a
       two-tone header: the dark strip carries navigation, the paper row carries
       identity and search. The mark itself is untouched. */
    .site-masthead {
        padding-top: var(--s-3) !important;
        padding-bottom: var(--s-3) !important;
        background-color: var(--page);
        border-bottom-color: var(--rule) !important;
    }
}

/* ---------------------------------------------------------------------------
   The utility strip.

   A thin mono line above the navigation carrying the operating facts - hours,
   where the company is, how to write to it. It is the register the whole
   chrome now speaks in, and it gives the masthead somewhere to start: the bar
   below it stops being the top edge of the page and becomes the middle of a
   header.
   --------------------------------------------------------------------------- */
.site-ticker {
    background-color: var(--bar);
    color: #CFC9C0;
    border-bottom: 1px solid rgba(255, 255, 255, .14);
    font-family: var(--f-mono);
    font-size: .6875rem;
    letter-spacing: .1em;
    text-transform: uppercase;
}

.site-ticker__row {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
    gap: var(--s-2) var(--s-4);
    padding-block: var(--s-2);
}

.site-ticker__group {
    display: inline-flex;
    align-items: center;
    gap: var(--s-2);
}

/* Keep the number and rate on one line in the ticker's mono typeface. */
.site-ticker__phone {
    display: inline-flex;
    align-items: baseline;
    gap: var(--s-2);
    white-space: nowrap;
}

.site-ticker__phone .call-rate-note {
    display: inline;
    margin-top: 0;
    color: #CFC9C0;
    font-family: inherit;
    font-size: inherit;
    letter-spacing: normal;
    text-transform: none;
}

.site-ticker__sep {
    opacity: .5;
}

.site-ticker__brand {
    color: #FFFFFF;
    letter-spacing: .18em;
}

.site-ticker a {
    color: #FFFFFF;
    text-decoration: none;
}

.site-ticker a:hover,
.site-ticker a:focus-visible {
    color: var(--accent-on-dark);
    text-decoration: underline;
    text-underline-offset: .2em;
}

/* The status dot. It pulses to say the line is live rather than decorative,
   which is the one thing a coloured dot can mean here. */
.site-ticker__dot {
    display: inline-block;
    width: 6px;
    height: 6px;
    border-radius: 50%;
    background-color: var(--accent-on-dark);
    animation: ticker-pulse 2s ease-in-out infinite;
}

@keyframes ticker-pulse {
    0%, 100% { opacity: 1; }
    50% { opacity: .3; }
}

@media (prefers-reduced-motion: reduce) {
    .site-ticker__dot {
        animation: none;
    }
}

/* ---------------------------------------------------------------------------
   Header density.

   Three stacked rows - ticker, navigation, identity - came to 202px of chrome
   before the page began. The design does the same work in about 96px, and it
   does it by carrying less: no search field, no phone number in the header at
   all. Both of those are real here and are staying, so the saving has to come
   from the rows themselves rather than from dropping what they hold.
   --------------------------------------------------------------------------- */
@media (min-width: 992px) {
    /* The field was py-3 - 16px top and bottom around a 14px control, which set
       the height of the whole row. */
    .site-masthead .form-control,
    .site-masthead .btn {
        padding-top: var(--s-2) !important;
        padding-bottom: var(--s-2) !important;
    }

    /* The number stays the loudest thing in the row, which is deliberate, but
       it does not also need to set the row's height on its own. */
    .site-masthead .header-text-phone {
        font-size: 1.5rem !important;
        line-height: 1.1;
    }

    .site-masthead .logo {
        max-height: 2.5rem;
        width: auto;
    }
}

/* The original roundel on dark chrome: a single ivory ring defines its
   silhouette while the artwork retains its red and black fills. */
.logo-lockup {
    display: inline-flex;
    align-items: center;
    gap: var(--s-3);
    text-decoration: none;
}

.logo-lockup__mark {
    display: block;
    flex: 0 0 auto;
    width: 44px;
    height: 44px;
}

.logo-lockup__text {
    display: flex;
    align-items: center;
    gap: .625rem;
    line-height: 1;
}

/* The owner's wordmark, drawn (App\Support\Wordmark) and coloured by
   currentColor, so the admin bar's ink rule below still applies to it. */
.logo-lockup__name {
    display: block;
    color: #FFFFFF;
}

.logo-lockup__wordmark {
    display: block;
    width: auto;
    height: 1.625rem;
}

/* AUTOMOTIVE & over INDUSTRIAL PARTS, beside the wordmark behind a hairline, the two
   lines together the wordmark's height - a descriptor set next to a logotype,
   the way a parts maker's lockup carries its trade. Under the wordmark it had
   to share the 44px roundel's height with it and was squeezed to 9px lines. */
.logo-lockup__sub {
    display: flex;
    flex-direction: column;
    gap: .1875rem;
    padding-left: .625rem;
    border-left: 1px solid rgb(207 201 192 / .35);
    color: #CFC9C0;
    font-family: var(--f-mono);
    font-size: .625rem;
    font-weight: 400;
    letter-spacing: .16em;
    text-transform: uppercase;
}

/* The descriptor needs ~125px the bar does not always have. On a phone it ran
   into the language switch (and wrapped the admin bar to a second line), and
   between 992px and the next container step it pushed Contact us onto a
   second row. The wordmark alone is the logo, so there the descriptor waits
   for the room. The footer has it everywhere. */
@media (max-width: 575.98px), (min-width: 992px) and (max-width: 1199.98px) {
    .site-navigation .logo-lockup__sub {
        display: none;
    }
}

.logo-link,
.logo-link:hover,
.logo-link:focus-visible {
    text-decoration: none;
}

@media (min-width: 992px) {
    /* Mark, navigation, actions - the design's three-part bar. */
    .site-navigation__bar {
        gap: var(--s-6);
    }

    /* Actions is one region, and the gap above is between regions.

       The three controls in it are direct children of the bar, so the 32px fired
       between them as well - and each one draws its divider as a border on its
       own left edge. That put every hairline hard against the control to its
       right with 32px of empty bar to its left, so the line read as belonging to
       Dashboard rather than as the boundary between Dashboard and Request a
       quote. It is the gap, not the border, that made it look wrong.

       Cancelled with the same token that creates it, so the two cannot drift:
       the cells abut, each hairline lands on a real edge, and the bar still
       opens the actions region 32px after the navigation ends. */
    .site-navigation__admin {
        margin-left: calc(var(--s-6) * -1);
    }

    /* And they do not shrink.

       These are fixed controls with fixed labels; the navigation beside them is
       the flexible part and already wraps when the bar runs out of room. Left
       shrinkable, the quote cell was compressed below its own content between
       992 and about 1200 - 167px of box holding 172px of label - so "REQUEST A
       QUOTE" overhung its right padding by 5px, across the divider and into
       Dashboard. The 32px gap had been absorbing that overhang rather than
       preventing it, which is why removing the gap is what made it visible. */
    .quote-list-control,
    .site-navigation__admin {
        flex-shrink: 0;
    }

    .site-navigation__desktop {
        margin-right: auto;
    }
}
