/* ===========================================================================
   STRUCTURE
   ===========================================================================

   Everything above this line styles an element. Everything below it states a
   relationship: what a band is, what separates two of them, what a plane is,
   and how a heading announces the thing under it.

   The site had none of these. Structure was carried entirely by white
   rectangles sitting on the page grey, spaced with whichever Bootstrap utility
   was to hand - mt-5 beside mb-4 beside py-5 beside p-4 - so every section
   separated from its neighbour by roughly the same interval and nothing read as
   more or less related to anything else.
   =========================================================================== */

/* A band is a major division of a page. The generous interval is the only one
   on the site; everything inside a band uses the --s-* steps, and the rhythm is
   the contrast between the two. */
.band + .band {
    margin-top: var(--band);
}

.band-tight + .band {
    margin-top: var(--s-7);
}

/* ---------------------------------------------------------------------------
   The section head.

   Every section heading on the site used the same device: two words with the
   second wrapped in .fw-bold.text-danger. "Offered Brands", "What we Offer",
   "Related Products", "Quote Request". Applied to all four it stopped
   distinguishing anything - it was the site's one heading idea, spent
   uniformly, so it read as a font rather than as emphasis.

   This replaces it with a structural device instead of a colour one: the
   heading, then a rule that runs to the container edge, opening with a short
   accent segment. The accent still appears once per section, but it now marks
   where the section starts rather than recolouring an arbitrary word, and the
   rule gives every band a visible top edge the page never had.
   --------------------------------------------------------------------------- */
.section-head {
    display: flex;
    align-items: center;
    flex-wrap: wrap;
    gap: var(--s-3) var(--s-4);
    margin-bottom: var(--s-5);
}

.section-head > :first-child {
    margin-bottom: 0;
}

/* The § of a specification clause, set beside the heading it opens. Decorative
   and aria-hidden at the callsite: it marks the head, it does not name it, and
   a screen reader reading "section sign" before every heading on the page would
   be noise. */
.section-head__mark {
    align-self: center;
    white-space: nowrap;
    color: var(--accent);
    font-family: var(--f-mono);
    font-size: var(--t-4);
    line-height: 1;
}

.section-rule {
    flex: 1 1 6rem;
    min-width: 3rem;
    height: 2px;
    background-image: linear-gradient(to right, var(--accent) 0 3rem, var(--rule) 3rem);
}

/* More space above a heading than below it, so a heading binds downward to the
   content it names rather than floating between two blocks. */
.section-head + * {
    margin-top: 0;
}

/* ---------------------------------------------------------------------------
   The panel head.

   .section-head is a page-level device: it opens a band, and the accent segment
   in its rule is what marks where that band starts. That only works if it fires
   once per band. Inside a panel it does the opposite - /contact-us put three of
   them in two side-by-side plates, so the top of the page carried two accent
   top-rules and two accent heading-rules and none of the four marked anything.

   A heading inside a panel is subordinate to the page heading above it, so it
   gets the hairline and no accent. Same shape, one rank down.
   --------------------------------------------------------------------------- */
.panel-head {
    padding-bottom: var(--s-2);
    margin-bottom: var(--s-4);
    border-bottom: 1px solid var(--rule);
}

/* ---------------------------------------------------------------------------
   Planes.

   A white rectangle on #F6F6F6 is a 1.04:1 difference - visible, but with no
   edge, so a filter panel, a card body and a page container all read as the
   same undifferentiated field. The hairline is what turns "lighter than the
   page" into "a bounded surface".
   --------------------------------------------------------------------------- */
.plane {
    background-color: var(--surface);
    border: 1px solid var(--rule);
}

/* The inverse of .plane: a block sunk into the page rather than lifted off it.
   For the one case where a bounded surface has to sit inside another one - the
   product page's reference block inside its details column - where a second
   .plane would read as two panels that happened to overlap. */
.spec-inset {
    background-color: var(--page);
    border: 1px solid var(--rule);
}

.spec-inset__row--separated {
    margin-top: var(--s-2);
    padding-top: var(--s-2);
    border-top: 1px solid var(--rule);
}

/* Bootstrap 5.1.3 compiles #dee2e6 into each of these as `!important`, so the
   only way to reach them is a same-specificity rule later in the cascade
   carrying the same flag. This is the whole reason the site had a fourth
   neutral: every .border-bottom in the views - the filter group heads, the
   category rail, the masthead - drew in a grey the palette does not contain. */
.border,
.border-top,
.border-end,
.border-bottom,
.border-start {
    border-color: var(--rule) !important;
}

/* The footer's dividers sit on the dark bar, where the hairline is invisible. */
footer .border,
footer .border-top,
footer .border-bottom {
    border-color: rgba(255, 255, 255, .14) !important;
}

/* 5.1.3 compiles the table border colour too. */
.table {
    border-color: var(--rule);
}

/* ---------------------------------------------------------------------------
   Square corners, stated once.

   The site is radius-0 - every panel, field, button and plate on it - but that
   was being achieved a component at a time: .site-navigation__toggle,
   .site-navigation__logout .btn and .nav-pills .nav-link.active each turn their
   own radius off, and anything Bootstrap ships that nobody had met yet kept its
   4px. Three had survived that way: .btn-link (the sort controls in the table
   head, "Blank template", "Clear filters"), .form-check-input on every checkbox
   in the catalog rail and the admin, and the first and last .page-link, whose
   rounded end-caps the storefront hid with a rounded-0 in the markup and the
   admin did not - so the same pagination component had square ends on one
   surface and round ends on the other.

   Stated by component rather than as a blanket * reset, because two radii here
   are deliberate: the notification badge and the rail badge are pills, and the
   catalog's own round marks stay round.
   --------------------------------------------------------------------------- */
.btn,
.form-check-input,
.form-control,
.form-select,
.btn-close {
    border-radius: 0;
}

/* Bootstrap reaches the checkbox through an attribute selector, which outranks
   the class list above; the radio keeps its circle. */
.form-check-input[type="checkbox"] {
    border-radius: 0;
}

/* ---------------------------------------------------------------------------
   THE FOOTER.

   Four Bootstrap columns of equal weight became one grid of unequal weight,
   because the four things in it were never the same kind of thing. Three are
   labelled lists of five, three and three links. The first is the company: its
   mark, its registered name, what it sells and where it is. Giving it a
   heading and a column width identical to Policies said those were peers.

   The ground is a shade below --bar rather than Bootstrap's #212529. The
   masthead is --bar, and the footer sitting a step deeper than the bar at the
   other end of the page is what closes the document; the compiled Bootstrap
   value was a cool grey in a palette that has no cool greys left.

   Copy is --footer-ink, a warm mid-grey: the links here are a directory, not
   the page's argument, and white-at-75%-opacity made ten of them shout as
   loudly as the address. The accent on hover is the one colour in the block.
   --------------------------------------------------------------------------- */
.site-footer {
    --footer-ink: #9A948A;
    --footer-rule: rgba(244, 241, 236, .12);
    /* .call-rate-note reads this for its colour; .bg-dark used to supply it. */
    --note-ink: var(--footer-ink);
    padding-top: var(--band);
    background-color: var(--bar-deep);
    color: var(--footer-ink);
    font-size: .875rem;
}

.site-footer__grid {
    display: grid;
    /* The identity column is the widest and the contact column the second
       widest, because both hold running text; the two link lists hold single
       words and only need their own width. */
    grid-template-columns: 2fr 1fr 1fr 1.4fr;
    gap: var(--s-7);
}

/* The registered name. Mono, tracked and uppercase, so it reads as the
   identity's second line rather than as a heading - which is what it did at
   --f-condensed 700, where it was the largest text in the footer and outweighed
   the four column labels it sat beside. */
.site-footer__legal {
    margin-top: var(--s-3);
    margin-bottom: 0;
    color: #CFC9C0;
    font-family: var(--f-mono);
    font-size: .625rem;
    letter-spacing: .16em;
    line-height: 1.6;
    text-transform: uppercase;
}

.site-footer__blurb {
    max-width: 40ch;
    margin-top: var(--s-4);
    margin-bottom: 0;
}

.site-footer__address {
    margin-top: var(--s-5);
    margin-bottom: 0;
    font-family: var(--f-mono);
    font-size: .6875rem;
    letter-spacing: .1em;
    line-height: 1.8;
    text-transform: uppercase;
}

/* The primary footer columns become disclosures on a phone. Their HTML ships
   open so no-JavaScript visitors keep every link; footer.js closes them only
   where the single-column stack would otherwise dominate the page. */
.footer-primary-disclosure > summary {
    display: flex;
    align-items: flex-start;
    gap: var(--s-2);
    color: var(--page);
    /* Mono, with the chrome's other micro-labels - see the micro-typography
       note at the foot of this file. 600, because the mono ships no 700. */
    font-family: var(--f-mono);
    font-size: .6875rem;
    font-weight: 600;
    letter-spacing: .15em;
    text-align: left;
    text-transform: uppercase;
    list-style: none;
}

.footer-primary-disclosure > summary::-webkit-details-marker {
    display: none;
}

.footer-primary-disclosure__body {
    margin-top: var(--s-5);
}

/* One list, three columns. The rows were four sibling anchors in a flex column
   with no list semantics at all, so a screen reader announced ten unrelated
   links instead of three groups of a stated size. */
.site-footer__list {
    display: flex;
    flex-direction: column;
    gap: .625rem;
    margin: 0;
    padding: 0;
    list-style: none;
}

/* The contact rows carry a second line - the call-cost notice - so they need
   more air between them than a row of single words does. */
.site-footer__list--contact {
    gap: var(--s-4);
}

/* The links themselves. Every one of them carried py-3, which is a 48px row:
   the right size for a thumb, and far too much air between five links standing
   in a desktop column - Navigate ran to 240px of mostly nothing for five short
   words, and the four columns finished at wildly different heights because of
   it. The touch target is kept where a finger is doing the pointing and the
   desktop column closes up. */
.footer-link {
    display: inline-block;
    color: inherit;
    text-decoration: none;
}

.footer-link:hover,
.footer-link:focus-visible {
    color: var(--accent-on-dark);
    text-decoration: underline;
}

@media (max-width: 767.98px) {
    .footer-link {
        /* .625rem either side of a 1.5 line box clears 44px. */
        padding-block: .625rem;
    }

    .site-footer__list {
        gap: 0;
    }
}

@media (min-width: 768px) {
    .footer-primary-disclosure > summary {
        pointer-events: none;
    }
}

/* Two columns before one. Four columns at 2fr/1fr/1fr/1.4fr on a tablet gives
   the link lists about 130px, which is narrower than "Warranty & Returns".

   The identity block takes a cell rather than the whole row: as a 2x2 the four
   blocks stay four blocks, where spanning it left Contact alone on the second
   row with a hole beside it. */
@media (max-width: 991.98px) and (min-width: 768px) {
    .site-footer__grid {
        grid-template-columns: 1fr 1fr;
        gap: var(--s-7);
    }
}

@media (max-width: 767.98px) {
    .site-footer {
        padding-top: var(--s-6);
    }

    .site-footer__grid {
        grid-template-columns: 1fr;
        gap: 0;
    }

    /* The identity block keeps its air; the collapsed columns below it butt
       against each other on their own rules. */
    .site-footer__brand {
        margin-bottom: var(--s-6);
    }

    .footer-primary-disclosure {
        border-top: 1px solid var(--footer-rule);
    }

    .footer-primary-disclosure > summary {
        position: relative;
        align-items: center;
        min-height: 52px;
        padding: var(--s-2) 2rem var(--s-2) 0;
        cursor: pointer;
    }

    .footer-primary-disclosure > summary::after {
        content: '';
        position: absolute;
        right: .25rem;
        width: .55rem;
        height: .55rem;
        border-right: 2px solid currentColor;
        border-bottom: 2px solid currentColor;
        transform: translateY(-.15rem) rotate(45deg);
        transition: transform 160ms ease-out;
    }

    .footer-primary-disclosure[open] > summary::after {
        transform: translateY(.15rem) rotate(225deg);
    }

    .footer-primary-disclosure > summary:focus-visible {
        outline: 2px solid var(--accent-on-dark);
        outline-offset: 2px;
    }

    .footer-primary-disclosure__body {
        margin-top: var(--s-2);
        padding-bottom: var(--s-4);
        text-align: left;
    }

    .footer-primary-disclosure__body > :last-child {
        margin-bottom: 0;
    }
}

/* There was a .plate here - .plane plus a 3px accent rule on the top edge - and
   it was a mistake in two ways.

   It double-marked. Every page that used it also opens with a .section-head
   whose rule carries its own accent segment, so the top of the page fired the
   accent twice within about 40px, and on /contact-us - two plates side by side,
   each with a heading - four times. An accent that appears everywhere the
   document starts is not marking where the document starts.

   And it made the surface compete with the heading. A page title is the page's
   title whether or not it sits on a white rectangle; giving the rectangle the
   colour put the emphasis on the container. Surfaces are neutral now: .plane
   for all of them, and the accent belongs to .section-rule and to actions. */

/* ---------------------------------------------------------------------------
   Reading measure.

   /warranty and /privacy are 1202 and 1207 words and both ran the full 1320px
   container - about 150 characters a line, roughly double the distance an eye
   returns across reliably. The heading levels are already correct on these
   pages; the measure never was.
   --------------------------------------------------------------------------- */
/* The measure binds the text, and nothing else. Three earlier versions of this
   rule each put it somewhere it did not belong, and each traded one lopsided
   thing for another:

     - on the children only, leaving a full-container plane with every line
       stopping halfway across it, so the empty half of the rectangle read as a
       column with something missing;
     - on the surface, which shrank the plane itself to 701px and moved the same
       empty half out into the 1320px container beside it;
     - on the surface plus margin-inline: auto, which centred that 701px plane
       and left it floating in the middle of a page whose every other band runs
       the full width.

   None of them was fixable by moving the cap again, because one column of
   readable text cannot fill 1320px - 68ch is about 540px and the rest has to go
   somewhere. Two columns is what spends it: the plane runs the full container
   like every other surface on the site, and the column width - not a max-width
   - is what holds each line near the measure.

   So .prose no longer constrains anything itself. It carries the vertical
   rhythm; .prose-columns below carries the measure. */
.prose > * {
    max-width: 100%;
}

/* ---------------------------------------------------------------------------
   Two-column running text.

   column-count rather than a grid of two divs: the columns balance. A grid puts
   fixed content in each cell, so the two sides end wherever their content
   happens to end - which on the homepage About band was a 200px hole under the
   shorter one. The browser fills these to the same depth by definition, and the
   reading order stays a single top-to-bottom sequence in the markup.

   Below lg the container is already at or under the measure, so one column is
   the measure and the rule does not apply. --------------------------------- */
@media (min-width: 992px) {
    .prose-columns {
        column-count: 2;
        /* Wide enough that the gutter reads as a gutter without a rule drawn in
           it. At the 1320px container this leaves each column near 68ch. */
        column-gap: var(--s-7);
    }
}

/* A heading is the first line of the block under it, so it has to travel with
   it. break-after: avoid is the declaration for that and it is not usable here:
   Firefox implements break-inside for multi-column but has never implemented
   break-before or break-after, so the heading stays put and its paragraph moves
   without it - "BRANDS WE WORK WITH:" alone at the foot of a column.

   .prose-keep is that binding expressed as containment instead, which is the
   one form both engines honour: the wrapper holds the heading and the first
   paragraph under it, and the wrapper is what cannot be broken. Later
   paragraphs in the same section are free to flow on. */
.prose-keep {
    break-inside: avoid;
}

/* Section separation runs on margin-bottom here, not the margin-top the rest of
   .prose uses, because a top margin at the top of a column is unreliable: the
   first block of the left column kept its 32px and the first block of the right
   column collapsed it away, so the two columns started on different lines. A
   bottom margin is never at the top of anything.

   Both classes are on the same element, so the selectors below are written
   .prose.prose-columns deliberately: the .prose h2 rule further down this file
   carries the same specificity as a bare .prose-columns h2 and is later in the
   cascade, so the single-class form loses and the heading keeps its 32px. */
.prose.prose-columns > * {
    margin-top: 0;
    margin-bottom: var(--s-6);
}

.prose.prose-columns > :last-child {
    margin-bottom: 0;
}

.prose.prose-columns h2,
.prose.prose-columns h3 {
    margin-top: 0;
}

/* A paragraph moves between columns whole rather than splitting across the
   break. Left free, the balancing put "BRANDS WE WORK WITH:" plus one line of
   its list at the foot of the left column on /about-us and carried the rest
   over, splitting a marque down the middle - "Thermo" ending one column and
   "King" opening the next.

   orphans/widows is the usual control for that and is the wrong tool here:
   Firefox has never implemented either for multi-column, so it fixes the break
   in Chrome and leaves it in Firefox. break-inside is supported in both.

   The cost is granularity - the longest paragraph here is the ~1000-character
   "Parts we supply", so the columns can now only balance to within one block of
   each other. A block taller than the column it lands in is broken anyway, by
   the spec, so nothing overflows in the worst case. */
.prose-columns p,
.prose-columns ul,
.prose-columns ol {
    break-inside: avoid-column;
}

.prose p,
.prose ul,
.prose ol {
    margin-bottom: var(--s-4);
}

.prose li + li {
    margin-top: var(--s-2);
}

/* Space above a heading, less below it - the rule the rest of this section is
   built on, applied inside running text. :first-child so a plate does not open
   with a gap above its own h1. */
.prose h2,
.prose h3 {
    margin-top: var(--s-6);
    margin-bottom: var(--s-3);
}

.prose > :first-child {
    margin-top: 0;
}

/* The legal pages contain sections with several paragraphs, lists, and, in the
   privacy notice, a table. Only the heading and the first related block are
   kept together in their markup; the section itself must remain fragmentable
   or one large section forces the second column to start too early. */
.policy-prose .prose-section:not(.prose-keep) {
    break-inside: auto;
}

/* ---------------------------------------------------------------------------
   The privacy storage table.

   Public and admin data tables both define their own hierarchy rather than
   falling back to Bootstrap's generic table. This smaller reference table uses
   the same quiet header, condensed labels, and horizontal rules. */
.policy-table {
    --bs-table-border-color: var(--rule);
    border-color: var(--rule);
}

.policy-table > thead > tr > th {
    padding: var(--s-2) var(--s-3);
    border-bottom-color: var(--rule-strong);
    background-color: var(--page);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .75rem;
    letter-spacing: .06em;
    text-transform: uppercase;
    white-space: nowrap;
}

.policy-table > tbody > tr > th,
.policy-table > tbody > tr > td {
    padding: var(--s-3);
    border-inline: 0;
    vertical-align: top;
}

.policy-table > tbody > tr:last-child > th,
.policy-table > tbody > tr:last-child > td {
    border-bottom: 0;
}

/* At phone width the three-column table previously hid Duration beyond an
   unmarked horizontal scroll edge. Keep the native table semantics in the DOM
   while presenting each storage item as a complete, labelled record. */
@media only screen and (max-width: 575.98px) {
    .policy-table-wrap {
        overflow: visible;
    }

    .policy-table {
        display: block;
        width: 100%;
        border: 0;
    }

    .policy-table > thead {
        position: absolute !important;
        width: 1px !important;
        height: 1px !important;
        padding: 0 !important;
        margin: -1px !important;
        overflow: hidden !important;
        clip: rect(0, 0, 0, 0) !important;
        white-space: nowrap !important;
        border: 0 !important;
    }

    .policy-table > tbody {
        display: grid;
        gap: var(--s-3);
    }

    .policy-table > tbody > tr {
        display: block;
        border: 1px solid var(--rule);
        background-color: var(--page);
    }

    .policy-table > tbody > tr > th,
    .policy-table > tbody > tr > td {
        display: block;
        width: 100%;
        padding: var(--s-3);
        border: 0;
    }

    .policy-table > tbody > tr > th {
        border-bottom: 1px solid var(--rule);
        background-color: var(--surface);
    }

    .policy-table > tbody > tr > td {
        display: grid;
        grid-template-columns: 4.75rem minmax(0, 1fr);
        gap: var(--s-3);
    }

    .policy-table > tbody > tr > td + td {
        border-top: 1px solid var(--rule);
    }

    .policy-table > tbody > tr > td::before {
        content: attr(data-label);
        color: var(--ink-muted);
        font-family: var(--f-condensed);
        font-size: .6875rem;
        font-weight: 700;
        letter-spacing: .06em;
        text-transform: uppercase;
    }
}

/* ---------------------------------------------------------------------------
   Elevation, where it means something.

   The masthead is position:sticky and had no edge at all, so a scrolled page
   ran its content up under the bar with nothing marking the boundary. The rule
   is the cheap half; the shadow is what says the bar is above the page rather
   than part of it.
   --------------------------------------------------------------------------- */
header.sticky-top {
    box-shadow: var(--shadow-1);
}
/* The baseline. A rule inside the container, not a separate full-bleed band on
   its own tint: the copyright and the place of business are the last line of
   the footer, not a second surface under it, and the tinted band read as one
   more region on a page that already has enough of them.

   Two ends, so the line is a pair of facts rather than one centred motto. */
.footer-baseline {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
    gap: var(--s-2) var(--s-5);
    margin-top: var(--s-7);
    padding-block: var(--s-4) var(--s-5);
    border-top: 1px solid var(--footer-rule, rgba(244, 241, 236, .12));
}

@media (max-width: 767.98px) {
    .footer-baseline {
        margin-top: var(--s-5);
    }
}

/* The Livro de Reclamações mark, at the baseline's far end, in white. The
   official artwork is dark grey on transparent, which vanishes on
   --bar-deep; it first sat on a light --page tile, but that tile was the
   brightest thing in the footer and read as a sticker. public/
   livro-reclamacoes-white.png is the same artwork with the grey turned white
   - LIVRO DE was already cut out of the circle, so it shows the footer's dark
   through - which is the negative version such marks use on dark grounds.

   It is a mask filled with currentColor rather than an <img>, so it hovers the
   way every footer link does - to --accent-on-dark - instead of growing a red
   box around a picture. 40px tall at the artwork's 500:207 keeps
   "RECLAMAÇÕES" legible at the copyright line's weight. */
.footer-complaints-book {
    display: inline-flex;
    align-items: center;
    color: #FFFFFF;
    outline-offset: 4px;
    transition: color .15s ease;
}

.footer-complaints-book:hover,
.footer-complaints-book:focus-visible {
    color: var(--accent-on-dark);
}

.footer-complaints-book__mark {
    display: block;
    width: 96.6px;
    height: 40px;
    background-color: currentColor;
    -webkit-mask: url('../livro-reclamacoes-white.png') center / contain no-repeat;
    mask: url('../livro-reclamacoes-white.png') center / contain no-repeat;
}

/* ---------------------------------------------------------------------------
   THE DRAWING-SHEET VOCABULARY.

   Five devices, borrowed from the engineering drawing this catalog is really a
   catalog of. They were arriving one page at a time and under page-specific
   names - /quote grew a `.quote-marker` that has nothing to do with quoting -
   so they are named and defined here, once, alongside .plane and .section-head
   that they sit beside.

   The rule for using them: each one marks a different thing. .band-invert
   opens a page, .marker labels a block, .plane--marked bounds a surface,
   .figure-data states a number, .cell-grid divides a set. Two of them on the
   same element is a sign that something is being marked twice - which is what
   retired the old .plate (see the note above).

   None of these carries a font family of its own beyond the two the site
   already loads, and none introduces a colour: --accent on light ground,
   --accent-on-dark on --bar, per 01-foundation.css:145.
   --------------------------------------------------------------------------- */

/* 1. The inverted band. A page opening that needs a field of its own rather
      than a hairline - the conversion pages and the section heads of the
      informational ones. It is --bar because that is already the ground under
      the masthead and the footer, so inverting reads as site chrome rather
      than as a new colour. Scoped tokens, because these copy and rule values
      hold only on this ground. */
.band-invert {
    --band-rule: rgba(255, 255, 255, .18);
    --band-copy: #CFC9C0;
    padding-block: var(--band) var(--s-6);
    background-color: var(--bar);
    color: var(--surface);
}

.band-invert .text-muted,
.band-invert__copy {
    /* Bootstrap 5.1.3 compiles .text-muted as !important, so inverse copy needs
       the same flag - the note .trust-panel carries for the same reason. */
    color: var(--band-copy) !important;
}

/* --f-condensed exists for exactly this and was reaching nothing outside the
   homepage hero. --t-display tops out at 72px, against the --t-2 40px a page
   heading gets from .section-head. */
.band-invert__title {
    margin-bottom: 0;
    font-family: var(--f-condensed);
    font-size: var(--t-display);
    /* 800, not 700. Archivo is a normal-width grotesque, so a display heading
       that used to get its authority from the condensed cut has to get it from
       weight instead. */
    font-weight: 800;
    line-height: 1.02;
    letter-spacing: -.03em;
    /* Sentence case, like the section heads below it. The design writes its
       page titles as statements - "Catalog.", "Request a quote." - and a 72px
       heading shouting in caps was the loudest thing left on the page. */
    text-transform: none;
}

.band-invert__lead {
    max-width: 52ch;
    margin-top: var(--s-4);
    margin-bottom: 0;
    color: var(--band-copy);
    font-size: var(--t-5);
}

/* 2. The section marker. § numbers a clause on a specification sheet rather
      than decorating it, which is the register the catalog already speaks in:
      every row on /quote is a part number set in the mono. Ink-muted by
      default because inside a panel it labels a block; --marker-ink lets a
      caller lift it to the accent when it opens a page instead. */
.marker {
    margin-bottom: var(--s-3);
    color: var(--marker-ink, var(--ink-muted));
    font-family: var(--f-mono);
    font-size: .75rem;
    letter-spacing: .14em;
    text-transform: uppercase;
}

/* A shade larger and wider on the band than inside a panel: it is opening a
   page there rather than labelling a block, and it is the only thing above a
   72px heading. */
.band-invert .marker,
.hero-band .marker {
    --marker-ink: var(--accent-on-dark);
    font-size: .8125rem;
    letter-spacing: .16em;
}

/* 3. Corner marks. Four 10px L's set over a plane's own border. The site
      stacks white planes on one grey field and at 1px of --rule each they read
      as divisions of the page rather than as bounded sheets; the ticks give
      the edge somewhere to start and stop.

      Eight gradients on one pseudo-element rather than the four spans this
      shape is usually built from: an empty <span> per corner is four more
      elements per panel for a screen reader to step over on its way to
      nothing.

      Two things make this device fail silently, so check both before adding
      the class. It owns ::after, so an element that already uses its own -
      .hero-plate paints the photograph's scrim there - simply wins, and the
      marks never appear. And a caller that clips its overflow needs
      --mark-inset pulled inside its edge, because the default -1px sits
      outside the clip. Neither shows up as an error; the marks are just
      absent. */
.plane--marked {
    position: relative;
}

.plane--marked::after {
    /* currentColor, not a fixed grey. These marks sit on white panels, on the
       hero's near-black, on the steel promo plates and on the dark closing
       band, and a single value cannot be quiet on one and legible on the next -
       --rule-strong is 1.6:1 on white, which is why the first version of this
       was invisible everywhere it mattered. Inheriting the surface's own text
       colour and dropping it to 45% gives the same weight on every ground. */
    --mark: linear-gradient(currentColor 0 0);
    opacity: .45;
    content: "";
    position: absolute;
    /* -1px sits the ticks over the plane's own border. A caller that clips its
       own overflow - the hero and promo plates both carry .overflow-hidden to
       hold their photographs - has to pull them inside to 0, or the browser
       clips the marks away and the device silently does nothing. */
    inset: var(--mark-inset, -1px);
    /* Above the content it frames. The hero plate raises its own text panel to
       z-index 2 and paints a background behind it, so at auto the marks were
       drawn and then covered - present in the DOM, invisible on screen. It is
       pointer-events:none, so sitting on top costs no interaction. */
    z-index: 3;
    pointer-events: none;
    background:
        var(--mark) 0 0 / 10px 1px no-repeat,
        var(--mark) 0 0 / 1px 10px no-repeat,
        var(--mark) 100% 0 / 10px 1px no-repeat,
        var(--mark) 100% 0 / 1px 10px no-repeat,
        var(--mark) 0 100% / 10px 1px no-repeat,
        var(--mark) 0 100% / 1px 10px no-repeat,
        var(--mark) 100% 100% / 10px 1px no-repeat,
        var(--mark) 100% 100% / 1px 10px no-repeat;
}

/* 4. The data figure. A quantity, a count, a reference - set in the mono the
      site already puts every part number in, so a number reads as measured
      rather than as headline copy. Size comes from the caller; this only fixes
      the family and the tracking a figure needs. */
.figure-data {
    font-family: var(--f-mono);
    font-variant-numeric: tabular-nums;
    line-height: 1.15;
    letter-spacing: -.01em;
}

/* 5. The cell grid. A set of equal things divided by a single hairline rather
      than by gaps - the drawing-sheet table. The 1px gap over a --rule ground
      is what draws the dividers, so there is one rule between two cells and
      never a doubled 2px seam where borders would meet. */
.cell-grid {
    display: grid;
    gap: 1px;
    background-color: var(--rule);
    border: 1px solid var(--rule);
}

.cell-grid > * {
    background-color: var(--surface);
}

.band-invert .cell-grid,
.cell-grid--invert {
    background-color: var(--band-rule, var(--bar-raised));
    border-color: var(--band-rule, var(--bar-raised));
}

.band-invert .cell-grid > *,
.cell-grid--invert > * {
    background-color: var(--bar);
}

/* ---------------------------------------------------------------------------
   The chrome's micro-typography.

   The masthead and footer are most of what is on screen on every page, and
   every small label in both was set the same way: --f-condensed, 700, uppercase,
   .06em. That is a perfectly good industrial register and it is not the one the
   rest of this restyle speaks - the § markers, the part references, the
   quantities and the quote summary are all mono, and the chrome around them
   was the only thing still answering in the condensed face.

   Moving these to the mono is what makes the drawing-sheet vocabulary read as
   the site's voice rather than as decoration applied to a few panels. Wider
   tracking, because mono at a small size needs it to stop reading as code.

   Weight 600, not 700: the mono ships 400 and 600 only (01-foundation.css
   @font-face), so 700 would be synthesised - a faux-bold smear at exactly the
   size where the letterforms have to stay crisp.
   --------------------------------------------------------------------------- */
.footer-baseline p,
.header-contact-meta a,
.quote-list-label,
/* The dashboard link is in the bar's utility cluster, not in
   .site-navigation__desktop, so the selector below never reached it: it was the
   one label up there still set in Archivo, sentence case and untracked. */
.site-navigation__admin,
.site-navigation__desktop .nav-link {
    font-family: var(--f-mono);
    font-weight: 600;
    letter-spacing: .1em;
    text-transform: uppercase;
}

/* The baseline is a legal line, not a label: it reads at 400 so it stays
   subordinate to the four column headings above it. */
.footer-baseline p {
    margin-bottom: 0;
    font-weight: 400;
    font-size: .75rem;
    letter-spacing: .08em;
}

/* ---------------------------------------------------------------------------
   The editorial section head.

   Rendering the design side by side made the real gap obvious, and it was not
   the marks - it was the heading itself. Every section on this site opened with
   an ALL-CAPS h2 set inline beside a rule running to the container edge, which
   reads as a label on a filing drawer. The design opens with a mono eyebrow on
   its own line and then says something, in sentence case, large and tightly
   tracked: "What we stock.", "56 OEM brands. One source."

   The words are unchanged - they are the site's own headings, and title case is
   how they are written in the Blade. Only the shouting comes off.

   Scoped with :has() to heads that carry a § mark, which is exactly the
   storefront set. The dashboard uses .section-head too and has no business
   becoming editorial; where :has() is unsupported, those heads simply keep the
   layout they already had.
   --------------------------------------------------------------------------- */
.section-head:has(.section-head__mark) {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-end;
    justify-content: space-between;
    gap: var(--s-3) var(--s-5);
    margin-bottom: var(--s-6);
}

.section-head__action {
    margin-left: auto;
    padding-bottom: .35rem;
}

/* The eyebrow takes a line of its own; the heading and any action for the
   section then share the line below it, which is where the design puts the
   "see everything" link that used to sit orphaned under the content. */
.section-head:has(.section-head__mark) .section-head__mark {
    flex: 0 0 100%;
    display: block;
    margin-bottom: var(--s-3);
    /* --ink-muted and --accent are both chosen against the light page ground.
       A dark band reusing this head - .trust-panel is the one that does - needs
       its own pair, so the eyebrow reads as a token the surface sets rather
       than a colour a later rule has to win back on specificity. */
    color: var(--section-mark-ink, var(--ink-muted));
    font-size: .6875rem;
    letter-spacing: .18em;
}

/* The section sign keeps the accent; the numeral beside it stays quiet. The
   whole eyebrow in accent was louder than the heading it introduces. */
.section-head:has(.section-head__mark) .section-head__mark::first-letter {
    color: var(--section-mark-accent, var(--accent));
}

.section-head:has(.section-head__mark) > h1,
.section-head:has(.section-head__mark) > h2 {
    max-width: 22ch;
    /* The scale jumps from --t-1 (40px) to --t-display (72px) with nothing in
       between, and a section heading wants the step that is missing. */
    font-size: clamp(1.75rem, 1.15rem + 2.4vw, 3.25rem);
    font-weight: 700;
    line-height: 1.02;
    letter-spacing: -.025em;
    /* Bootstrap compiles .text-uppercase as !important, so the markup's utility
       has to be answered with the same flag rather than unpicked from 11 views. */
    text-transform: none !important;
}

/* The rule ran to the container edge to mark where a band started. The eyebrow
   does that now, one line above, and carrying both left the head marked twice -
   the thing .plate was retired for.

   !important because one of these rules carries .d-sm-block, and Bootstrap
   compiles its display utilities with the flag - so that single head kept its
   rule while every other one lost it, which is worse than all or none. */
.section-head:has(.section-head__mark) .section-rule {
    display: none !important;
}
