/* -----------------------------------------------------------------------
   Variables
----------------------------------------------------------------------- */
/* -----------------------------------------------------------------------
   Roboto Mono was self-hosted here (two @font-face rules, one per subset)
   until 2026-11-05, when --font-mono became the generic `monospace`. Both
   rules went with it: an @font-face nothing references downloads nothing,
   but it is dead code pointing at two files. The .woff2 files are still in
   shop/assets/fonts/ and on the server, and BUILD "Self-hosted Roboto Mono"
   has the history if it is ever wanted back.
----------------------------------------------------------------------- */

/* -----------------------------------------------------------------------
   Display / hand typeface — self-hosted, replacing Adobe Typekit's `salted`.
   Closes the Adobe half of backlog #18: no visitor IP reaches Adobe any more.

   More Or Less (David Kerkhoff / Hanoded) since 2026-11-05, under a Fontspring
   webfont licence — order 138051341, the EULA and the kit are in
   Documents/Personal/Addsomespite/Font. The .woff2 here is the kit's file
   byte for byte; the family name is the one the kit's own stylesheet.css
   declares, so the two can be diffed without translating. Two terms of that
   licence bind this directory: the fonts may not be redistributed with a
   website's source code, and the pageview ceiling is the one on the receipt.

   It replaced TrashHand, which had held this slot since 2026-10-16, and the
   swap is not like-for-like:

     - It sets about 40% wider. "Add Some Spite" is 6.58 em against
       TrashHand's 4.69 em at the same font-size. That is the change to watch:
       every px size in this file was chosen against the narrower face, so
       headings wrap sooner than they used to.
     - Its capitals are about a fifth taller (cap 1460 units against 1192 on a
       2048 em), so it also draws bigger.
     - Its line box is 1.25 em against TrashHand's 1.08 em, so anything
       leaving line-height at `normal` gains about a sixth of a line. The
       display rules here mostly pin it (1.05–1.2); .result-mark,
       .result-title, .add-confirm and .sold-out-label do not.
     - Both faces are effectively unicase, so `text-transform: lowercase` on
       .page-header h1, .prose h1, .tile-name and .product-info h1 still
       changes the markup and almost nothing on screen — keep it, it is what
       makes the casing an editor types irrelevant. More Or Less carries a
       real lowercase alphabet but draws it at cap height (x-height 1380
       against a 1402 cap); only i, u, w and z dip, and only slightly.

   Bunny Chow was tried in this slot on the same day and is licensed too
   (order 138048194); bunnychow-regular-webfont.woff2 is still in fonts/ but
   nothing references it. TrashHand, Elliot Six (the 2026-10-16 runner-up) and
   their measurements are in BUILD "Self-hosted hand typeface";
   trashhand-webfont.woff2 is still in fonts/ and on the server, unreferenced.
----------------------------------------------------------------------- */
@font-face {
    font-family: 'more_or_less';
    src: url('fonts/more_or_less-webfont.woff2') format('woff2');
    font-weight: 400;
    font-style: normal;
    font-display: swap;
}

:root {
    --spotcolor: #FFE365;
    --black: #000;
    --white: #fff;
    --font-hand: 'more_or_less', cursive, sans-serif;
    /* The generic family, so every visitor gets whatever their own system
       calls monospace — SF Mono, Consolas, DejaVu Sans Mono. Nothing is
       downloaded for body copy any more. The one thing this gives up is a
       guaranteed identical metric everywhere: the shop's measurements are
       set in px and ch-independent, but a line that fitted on one line in
       Roboto Mono may wrap in a wider system face. */
    --font-mono: monospace;
    --clip-full: polygon(0 0, calc(100% - 170px) 0, 100% 100%, 0 100%);
    /* The cart/product bar, at 75% of its original depth (was 140px/200px,
       then briefly 60%, 2026-10-18). These two numbers are the whole height of
       the shape on those pages: the element is far taller, but this clip is
       what shows. They keep the original 0.7 ratio to each other, which is
       what sets the bar's slope. */
    --clip-bar:  polygon(0 0, calc(100% - 170px) 0, calc(100% - 160px) 105px, 0 150px);
    /* The cart circle's rendered width. box-sizing is border-box, so the 3px
       border it grows below 768px is inside this number, not added to it.
       Named here because the wordmark cap on narrow screens is measured from
       it — see the .site-name rule in the 768px block. */
    --cart-circle-size: clamp(60px, 6.25vw, 80px);
    /*--clip-full: polygon(0 0, 88% 0, 100% 100%, 0 100%);
    --clip-bar:  polygon(0 0, 88% 0, calc(100% - 160px) 140px, 0 200px);*/
}

/* -----------------------------------------------------------------------
   Reset & base
----------------------------------------------------------------------- */
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }

html {
    background: var(--white); /* white wedge area where spot-bg is clipped away */
    overflow-x: hidden;       /* prevents scrollbars during page transition scaling */
}

body {
    font-family: var(--font-mono);
    font-size: 16px;
    line-height: 1.6;
    color: var(--black);
    background: transparent; /* let spot-bg show through */
    position: relative;
}

a { color: inherit; text-decoration: none; }
a:hover { text-decoration: underline; }
img { max-width: 100%; display: block; }

:focus { outline: none; }
:focus-visible {
    outline: 3px solid var(--black);
    outline-offset: 2px;
    box-shadow: 0 0 0 5px var(--spotcolor);
}

/* -----------------------------------------------------------------------
   Container
----------------------------------------------------------------------- */
.container {
    max-width: 1280px;
    margin: 0 auto;
    padding: 0 24px;
}

/* -----------------------------------------------------------------------
   View Transitions
----------------------------------------------------------------------- */
@view-transition { navigation: auto; }

/* Homepage → product/cart/theme: old full diagonal shrinks to bar */
:root:has(body.page-product)::view-transition-old(dynamic-shape),
:root:has(body.page-theme)::view-transition-old(dynamic-shape),
:root:has(body.page-prose)::view-transition-old(dynamic-shape),
:root:has(body.page-cart)::view-transition-old(dynamic-shape) {
    animation-name: spot-full-to-bar;
    animation-duration: 0.5s;
    animation-timing-function: ease-in-out;
    animation-fill-mode: forwards;
}
:root:has(body.page-product)::view-transition-new(dynamic-shape),
:root:has(body.page-theme)::view-transition-new(dynamic-shape),
:root:has(body.page-prose)::view-transition-new(dynamic-shape),
:root:has(body.page-cart)::view-transition-new(dynamic-shape) {
    animation-name: none;
}

/* Product/cart/theme → homepage: new full diagonal grows from bar */
:root:has(body.page-home)::view-transition-old(dynamic-shape) {
    animation-name: none;
}
:root:has(body.page-home)::view-transition-new(dynamic-shape) {
    animation-name: spot-bar-to-full;
    animation-duration: 0.5s;
    animation-timing-function: ease-in-out;
    animation-fill-mode: forwards;
}

@keyframes spot-full-to-bar {
    from { clip-path: var(--clip-full); }
    to   { clip-path: var(--clip-bar); }
}

@keyframes spot-bar-to-full {
    from { clip-path: var(--clip-bar); }
    to   { clip-path: var(--clip-full); }
}

/* Global default: all named transitions run at the same pace */
::view-transition-group(*),
::view-transition-old(*),
::view-transition-new(*) {
    animation-duration: 0.5s;
    animation-timing-function: ease-in-out;
}


/* Second wordmark line. It is on every page, at two different sizes, so it gets
   no animation of its own: the default image-pair morph scales it between the
   homepage size and the smaller one, exactly as `wordmark` above is handled.
   It used to fade out on leaving the homepage, which is in BUILD under
   "Line two kept on every page". */

/* -----------------------------------------------------------------------
   Yellow background — fixed behind all content, diagonal wedge right
----------------------------------------------------------------------- */
.spot-bg {
    position: absolute;
    top: 0;
    left: 0;
    width: 100vw;
    /* body is position:relative, so 100% here is the page height, not the
       viewport — this reads like a viewport unit and is not one. */
    height: calc(100% + 30px);
    background-color: var(--spotcolor);
    z-index: -1;
    clip-path: var(--clip-full);
    view-transition-name: dynamic-shape;
    will-change: transform;
}

.page-product .spot-bg, page-cart . spot-bg {
    height: 100vh;
}

.page-product .spot-bg {
    clip-path: var(--clip-bar);
    will-change: transform;
}


.page-cart .spot-bg {
    clip-path: var(--clip-bar);
    will-change: transform;
}

/* A theme page is an inner page with the homepage's layout, so it takes the
   inner pages' bar rather than the full diagonal. 100vh for the same reason
   .page-product does: the bar is at the top and the grid below it can be long,
   and the full-height rule would paint yellow all the way down. */
.page-theme .spot-bg {
    height: 100vh;
    clip-path: var(--clip-bar);
    will-change: transform;
}

/* /about is an inner page with the bar, like the cart. 100vh for the reason
   given above: the yellow must not run the length of the prose. */
.page-prose .spot-bg {
    height: 100vh;
    clip-path: var(--clip-bar);
    will-change: transform;
}

/* -----------------------------------------------------------------------
   Header — sits transparently on the spot background
----------------------------------------------------------------------- */
.site-header {
    position: relative;
    background: transparent;
    padding: 40px 0 16px;
    z-index: 1;
}

.header-inner {
    position: relative;
}

/* Two outlined SVG lines, stacked and tilted (see BUILD "Two-line wordmark").
   Both lines on every page, at a smaller --wordmark-w on cart and product.

   Both lines are sized by WIDTH, not height: the exports are only 22px and 15px
   tall, so height-driven sizing rounds badly. --wordmark-fit drives line one and
   line two is --wordmark-sub-ratio of it, which defaults to 0.73 — 197/270,
   their natural width ratio — so neither can drift out of proportion with the
   other. Lower the ratio on a page to make line two subordinate there rather
   than merely smaller. One number to change the wordmark size, one for the
   ratio, one to change each tilt. */
.site-name {
    /* --wordmark-w is what the page asks for, --wordmark-max the ceiling
       something else in the header imposes, and --wordmark-fit the smaller of
       the two, which is what gets drawn. Keeping them apart is what lets the
       768px block cap the wordmark against the cart circle without having to
       restate the clamp()s — overwriting --wordmark-w there would discard the
       per-page size rather than limit it. */
    --wordmark-w: clamp(280px, 46vw, 600px);
    --wordmark-max: 100%;
    --wordmark-fit: min(var(--wordmark-w), var(--wordmark-max));
    --wordmark-sub-ratio: 0.73;
    --wordmark-sub-tilt: -1deg;
    display: block;
    text-decoration: none;
    color: var(--black);
    transform: rotate(-1.5deg);
    transform-origin: left bottom;
}

@media (max-width: 768px) {
    .cart-circle { background-color: var(--white)!important; }
}

/* The homepage leads with the wordmark, so it runs larger there — the other
   pages keep the base size. Both are capped against the cart circle by
   --wordmark-max in the 768px block. */
.page-home .site-name {
    --wordmark-w: clamp(280px, 50vw, 900px);
}

.site-name:hover { text-decoration: none; }

.site-name .wordmark {
    display: block;
    width: var(--wordmark-fit);
    max-width: 100%;
    height: auto;
    view-transition-name: wordmark;
}

/* Tilt is relative to the block above, which already carries -1.5deg, so the
   two lines are deliberately not quite parallel. */
.site-name .wordmark-sub {
    display: block;
    width: calc(var(--wordmark-fit) * var(--wordmark-sub-ratio));
    max-width: 100%;
    height: auto;
    /*margin-top: clamp(6px, 0.9vw, 12px);*/
    transform: rotate(var(--wordmark-sub-tilt));
    transform-origin: left center;
    view-transition-name: wordmark-sub;
}

/* Cart circle — white circle on spot background */
.cart-circle {
    position: absolute;
    top: 16px;
    right: clamp(16px, 2.5vw, 40px);
    width: var(--cart-circle-size);
    height: var(--cart-circle-size);
    border-radius: 50%;
    background: var(--spotcolor);
    display: flex;
    align-items: center;
    justify-content: center;
    color: var(--black);
    text-decoration: none;
    flex-shrink: 0;
    z-index: 2;
}

.cart-circle img { display: block; }

.cart-circle:hover { opacity: 0.8; text-decoration: none; }


.cart-badge {
    position: absolute;
    top: -4px;
    right: -4px;
    background: var(--black);
    color: var(--white);
    font-family: var(--font-mono);
    font-size: 18px;
    line-height: 1;
    padding: 4px;
    min-width: 18px;
    text-align: center;
    width: 28px;
    height: 28px;
    border-radius: 14px;
}

/* -----------------------------------------------------------------------
   Page main
----------------------------------------------------------------------- */
.page-main { /* open — each page controls its own layout */ }

/* -----------------------------------------------------------------------
   Inner-page content wrapper (product, cart, success, cancel)
----------------------------------------------------------------------- */
.page-content {
    max-width: 1200px;
    margin: 0 auto;
    padding: 36px 24px 72px;
}

/* -----------------------------------------------------------------------
   Inner-page header bar
----------------------------------------------------------------------- */
.page-header {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    margin-bottom: 28px;
    padding-bottom: 14px;
    border-bottom: 2px solid var(--black);
}

.page-header h1 {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: 38px;
    text-transform: lowercase;
}

.page-header a {
    font-family: var(--font-mono);
    font-size: 18px;
    /* border: 2px solid var(--black);*/
    text-decoration: none;
    display: inline-flex;
    align-items: center;
    gap: 4px;
}

.page-header a:hover {
    transform: rotate(0deg);
}

/* -----------------------------------------------------------------------
   Prose pages — /about and the two legal documents

   The pages that are nothing but running text, so the ones that need a
   measure: .page-content is 1200px, which is three times too wide to read a
   paragraph across. 680px is the measure the legal pages set for themselves
   back when each carried its own stylesheet.

   Was .about-content until 2026-11-05; renamed when the legal pages started
   using it, because a privacy policy inside .about-content reads as a
   mistake.
----------------------------------------------------------------------- */
.prose {
    max-width: 680px;
}

/* Lowercase, like every other h1 on the shop (.page-header h1,
   .product-info h1) — it is the house treatment for the hand face, not a
   comment on the copy. Headings inside the copy are left as typed: they are
   people's names on /about and numbered clauses on the legal pages, and
   "1. who's responsible for your data?" reads as a typo. */
.prose h1 {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: clamp(32px, 3.3vw, 42px);
    line-height: 1.2;
    text-transform: lowercase;
    margin-bottom: 20px;
}

.prose h2 {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: 28px;
    line-height: 1.1;
    margin: 36px 0 10px;
}

/* h3 exists only on the legal pages, where h2 is the language version and h3
   is a numbered clause. Mono rather than the hand face: there are eighteen of
   them per document and the display face at that density stops being a
   signal. */
.prose h3 {
    font-family: var(--font-mono);
    font-weight: 700;
    font-size: 17px;
    line-height: 1.3;
    margin: 30px 0 8px;
}

.prose ul,
.prose ol {
    margin: 0 0 16px 22px;
}

.prose li {
    font-family: var(--font-mono);
    font-size: 16px;
    line-height: 1.8;
}

/* The two tables in the privacy policy. Plain black rules, like .page-header
   and the product grid: the shop has no other table style and a bordered box
   would be the only grey thing on the page. */
.prose table {
    width: 100%;
    border-collapse: collapse;
    margin: 0 0 20px;
    font-family: var(--font-mono);
    font-size: 14px;
    line-height: 1.6;
}

.prose th,
.prose td {
    border: 1px solid var(--black);
    padding: 8px 10px;
    text-align: left;
    vertical-align: top;
    /* The Dutch half of the privacy policy has compound words long enough to
       push a three-column table past 390px on their own — "kaartgegevens",
       "Bestelgegevens". `anywhere` is the one wrapping value that lowers a
       cell's min-content width, so the table can shrink to the viewport
       instead of the page scrolling sideways. The alternative, an overflow-x
       wrapper round the table, hides a column behind a scrollbar that a
       phone does not draw. */
    overflow-wrap: anywhere;
}

/* …but `anywhere` alone lets the automatic layout starve a column: at 390px
   it gave the third one four characters and stacked "Rechtsgrond" down the
   page one syllable at a time. Below the breakpoint the columns are shared
   out evenly instead, which is wide enough for every heading in both
   languages. Auto layout stays above it, where it reads better: the "why"
   column there is three times the width of the other two and should be. */
@media (max-width: 767px) {
    .prose table {
        table-layout: fixed;
        /* Two points down from the body copy, which buys a third of a
           column: "kaartgegevens" stops breaking mid-word and the table
           loses about 300px of height. "Betaalgegevens" still splits, and
           pinning a wider first column was tried and made it worse — a
           three-column table of Dutch compounds at 390px has to give
           somewhere. The surrounding prose keeps its own size. */
        font-size: 12px;
    }
}

.prose thead th {
    background: var(--spotcolor);
    font-weight: 700;
}

/* The language switch at the top of each legal document, and its twin
   halfway down. Scroll-margin so the heading it jumps to does not land under
   the cart circle, which is fixed from 768px down. */
.prose [id] {
    scroll-margin-top: calc(16px + var(--cart-circle-size) + 12px);
}

.prose p {
    font-family: var(--font-mono);
    font-size: 16px;
    line-height: 1.8;
    margin-bottom: 16px;
}

/* Underlined, as in the product description: a link in a block of mono text
   is invisible without it, since `a` inherits its colour site-wide. There are
   none in the copy today; this is here so adding one needs no CSS. */
.prose a {
    text-decoration: underline;
    text-underline-offset: 4px;
}

/* …except one that is a button. The underline above is for links in running
   text, where it is the only thing marking them; a .btn is already a filled
   black box and does not need it. /pickup is the one prose page with a button
   on it today. */
.prose a.btn { text-decoration: none; }

/* The same 2px black rule .page-header draws under itself, so the break
   between the two bios and the sign-off is the shop's line and not the
   browser's grey bevel. */
.prose hr {
    border: 0;
    border-top: 2px solid var(--black);
    margin: 32px 0 24px;
}

/* -----------------------------------------------------------------------
   Homepage layout — sidebar text + product grid on spot background
----------------------------------------------------------------------- */
.home-layout {
    display: grid;
    grid-template-columns: minmax(220px, 1fr) 3fr;
    gap: 0 48px;
    max-width: 1280px;
    margin: 0 auto;
    padding: 20px 24px 64px;
}

/* The theme pages' back-link bar. Same .page-header inside it that the cart
   page uses, but 1280px wide and with .home-layout's horizontal padding, so
   the rule under the link lines up with the columns beneath it — .page-content
   is 1200 and would have left it short at both ends. */
.theme-bar {
    max-width: 1280px;
    margin: 0 auto;
    padding: 36px 24px 0;
}

.theme-bar .page-header {
    margin-bottom: 0;
}

.home-sidebar {
    padding: 8px 0 0;
}

/* `tagline` used to pair this with .site-tagline in the header, which morphed
   one into the other between pages. The header tagline is gone (2026-10-18), so
   this is now the only element with the name: it fades on its own, like
   .wordmark-sub. The name is kept rather than renamed so the transition is not
   disturbed; "sidebar-headline" would read better if it is ever touched. */
.sidebar-headline {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    /* Ceiling dropped from 42px to 38px with More Or Less (2026-11-05): the
       wider face took the two-sentence headline to three lines above about
       1200px. The floor and the 3.3vw are untouched, so nothing below that
       width moves. .prose h1 still uses the old clamp — it is one short line
       and did not need it. */
    font-size: clamp(32px, 3.3vw, 38px);
    line-height: 1.05;
    margin-bottom: 20px;
    view-transition-name: tagline;
}

/* One rule for both columns of sidebar copy — the homepage's and a theme
   page's — because they ARE the same copy in the same place, and two sets of
   the same declarations would be two things to keep in step.

   Selected by element rather than by class: both blocks are now Markdown
   rendered through Html::allowlist(), which strips every attribute, so their
   paragraphs cannot carry one. `.sidebar-copy` was that class and is gone. */
.sidebar-prose p,
.theme-intro p {
    font-family: var(--font-mono);
    font-size: clamp(14px, 1.2vw, 16px);
    line-height: 1.8;
    color: var(--black);
    margin-bottom: 14px;
}

.home-products {
    padding: 8px 0 0;
}

/* -----------------------------------------------------------------------
   Item-type filter (above the product grid)

   One segmented control: three radios dressed as segments. Radios rather
   than aria-pressed buttons so the filter survives with JavaScript off, where
   the form's own submit is what applies the choice — and because three
   mutually exclusive options with exactly one always on IS a radio group,
   which brings the right keyboard behaviour (one tab stop, arrows within) at
   no cost.

   The controls themselves are visually hidden: the segment IS the control,
   and a radio dot inside it would say the same thing twice. The input keeps
   a 1px clipped box rather than display:none, so it is still focusable and
   still in the accessibility tree — .visually-hidden's technique, repeated here
   because the rule has to sit on the input itself.

   Unselected is the spot colour and selected is white, which is the inverse
   of the usual and deliberate: the page is already yellow, so a yellow
   segment recedes into it and white is what stands out. Selected also goes
   bold and takes a heavier border.

   Focus has to be drawn on the segment, because the element actually
   receiving it is invisible. Hence :has(input:focus-visible) rather than the
   global :focus-visible rule, which would hang a ring on a 1px box nobody can
   see.
----------------------------------------------------------------------- */
.product-filter {
    margin-bottom: 24px;
    /* Where the control lands when filter.js scrolls the results into view.
       Raised below 768px, where the cart circle is fixed over this corner. */
    scroll-margin-top: 16px;
}

.product-filter fieldset {
    border: 0;
    margin: 0;
    padding: 0;
    display: flex;
    align-items: center;
    justify-content: flex-end;   /* chips sit against the right edge of the list */
    flex-wrap: wrap;
    gap: 10px 14px;
}

/* One segmented control, not three chips: no gap, and each segment after
   the first pulls back over its neighbour by a border width so the seam is a
   single 2px line rather than two stacked ones.

   It still wraps, because three segments do not fit a narrow column. A
   wrapped row starts 2px left of the edge, which is the negative margin on
   what is now the first segment of that line — not worth a :has() rule to
   chase. */
.filter-options {
    display: flex;
    flex-wrap: wrap;
    justify-content: flex-end;
    gap: 0;
}

.filter-options .filter-toggle + .filter-toggle {
    margin-left: -2px;
}

.filter-toggle {
    position: relative;   /* contains the visually hidden input */
    display: inline-flex;
    align-items: center;
    /* Selected swaps 2px of padding for 2px of border, so the chip is exactly
       the same size either way and its neighbour is not shoved sideways. */
    border: 2px solid var(--black);
    padding: 9px 16px;
    cursor: pointer;
    font-family: var(--font-mono);
    font-size: 16px;
    background: var(--spotcolor);
    transition: background .12s, border-width .12s, padding .12s;
    user-select: none;
}

.filter-toggle:hover { background: #FFF1A8; }

/* The selected segment draws over its neighbours: its heavier border has to
   sit on top of the seam, not be overlapped by it. */
.filter-toggle:has(input:checked) {
    background: var(--black);
    border-width: 4px;
    padding: 7px 14px;
    font-weight: bold;
    z-index: 1;
    color: var(--white)
}

/* Same, for the focused segment and the hovered one — whichever is drawing
   something at its edge needs to be above the seam. */
.filter-toggle:has(input:focus-visible),
.filter-toggle:hover {
    z-index: 2;
}

.filter-toggle:has(input:focus-visible) {
    outline: 3px solid var(--black);
    outline-offset: 2px;
    box-shadow: 0 0 0 5px var(--spotcolor);
}

/* The label goes bold when selected, which would widen the chip and — with
   the row right-aligned — shunt its neighbour. The ::after carries the same
   string at bold weight with no height, so the chip is always already as wide
   as it will ever need to be. visibility:hidden keeps the duplicate out of
   the accessibility tree; the grid puts both in one column so the width is
   the larger of the two. */
.filter-toggle span {
    display: inline-grid;
}

.filter-toggle span::after {
    content: attr(data-label);
    font-weight: bold;
    height: 0;
    overflow: hidden;
    visibility: hidden;
    pointer-events: none;
}

/* Any input, not input[type="checkbox"]: these were checkboxes before the
   control became a three-way segmented one, and a type-specific selector is
   exactly what silently stopped matching when they turned into radios. */
.filter-toggle input {
    position: absolute;
    width: 1px;
    height: 1px;
    margin: -1px;
    padding: 0;
    border: 0;
    overflow: hidden;
    clip: rect(0, 0, 0, 0);
    clip-path: inset(50%);
    white-space: nowrap;
}

/* .btn sets display:inline-block, which outranks the user agent's
   `[hidden] { display: none }` — so the button filter.js hides needs this.
   Same reason as .product-tile[hidden] and .product-grid[hidden] below. */
.filter-submit[hidden] { display: none; }

/* Live region: it has no text unless the filter is narrowing the list, so it
   must not reserve a line when it is empty. */
.filter-status {
    font-family: var(--font-mono);
    font-size: 14px;
    margin: 0;
    text-align: right;   /* sits under the chips it is reporting on */
}

.filter-status:empty { display: none; }

/* Narrow: three segments do not fit a phone column, and a segmented control
   that wraps into separate rows is not a segmented control any more. It
   becomes a full-width vertical one instead — which also retires the
   horizontal negative margin, whose only failure mode was nudging a wrapped
   row 2px to the left. */
@media (max-width: 600px) {
    .product-filter fieldset { justify-content: stretch; }

    .filter-options {
        flex-direction: column;
        align-items: stretch;
        width: 100%;
    }

    .filter-toggle { justify-content: center; }

    .filter-options .filter-toggle + .filter-toggle {
        margin-left: 0;
        margin-top: -2px;
    }
}

/* -----------------------------------------------------------------------
   Product grid
----------------------------------------------------------------------- */
.product-grid {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 28px 20px;
}

/* The grid and the tiles both set display, which outranks the user agent's
   `[hidden] { display: none }` — so the hidden state has to be said again.
   index.php sets it server-side on excluded tiles and filter.js toggles it. */
.product-grid[hidden] { display: none; }

/* -----------------------------------------------------------------------
   Product tile
----------------------------------------------------------------------- */
.product-tile {
    text-decoration: none;
    color: var(--black);
    display: block;
    position: relative;
}

.product-tile:hover { text-decoration: none; }

/* display:block above beats the user agent's `[hidden] { display: none }`,
   so the tiles filter.js hides need saying again. */
.product-tile[hidden] { display: none; }

/*.product-tile.sold-out { opacity: 0.5; }*/

.tile-image-wrap {
    width: 100%;
    aspect-ratio: 1;
    display: flex;
    align-items: center;
    justify-content: center;
    margin-bottom: 14px;
    overflow: hidden;
    padding: 14px;

    /* A QUERY CONTAINER PURELY SO THE IMAGE BELOW CAN BE CAPPED IN BOTH AXES.
       Nothing here uses @container; this exists for the cqw/cqh units only.
       Safe because this box's size never depends on its contents: the width
       comes from the grid column and the height from aspect-ratio, which is
       exactly the condition `container-type: size` requires. */
    container-type: size;
}

/* WHY THE CAP IS IN cq UNITS AND NOT PER CENT (2026-11-14).
   `max-height: 86%` resolves against the containing block's height. WebKit
   does not treat a height that came from `aspect-ratio` as definite, so in
   Safari the percentage resolved to `none`, only `max-width` applied, and any
   portrait image rendered at 86% WIDTH and its own natural height — measured
   at 247x354 inside a 294px box, i.e. 60px of the sticker cut off top and
   bottom at rest and 117px on hover. Chrome resolved it correctly all along,
   which is why it went unnoticed.

   cqw/cqh resolve against the query container's content box, which both
   engines agree is definite. 86cqw/86cqh is the SAME NUMBER as 86% was:
   measured identical in Chrome before and after (166x238 at rest,
   185x277 on hover), and it finally applies in Safari.

   The per-cent pair is kept above as the fallback for anything without
   container units (Safari < 16, Chrome < 105) — there it behaves exactly as
   it does today, which is correct in every engine that supports them. */
.tile-image-wrap img {
    max-width: 86%;
    max-height: 86%;
    max-width: 86cqw;
    max-height: 86cqh;
    object-fit: contain;
    transform: rotate(-3deg);
    transition: transform 0.25s ease;
}

.product-tile:hover .tile-image-wrap img {
    transform: rotate(0deg) scale(1.2);
}

.product-tile.sold-out:hover .tile-image-wrap img {
    transform: rotate(-3deg);
}

.tile-placeholder {
    width: 100%;
    height: 100%;
    display: flex;
    align-items: center;
    justify-content: center;
    color: #ccc;
    font-size: 11px;
    font-family: var(--font-mono);
}

.tile-name {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: clamp(21px, 1.9vw, 28px);
    line-height: 1.15;
    /* No letter-spacing. TrashHand set very tight and wanted 2px here;
       More Or Less is a wide face with generous sidebearings and does not,
       and at a 283px column the 2px cost "assumption is the mother of all
       f*ckups" a whole third line. Removed with the face, 2026-11-05. */
    margin-bottom: 6px;
    text-transform: lowercase;
}

.product-tile.sold-out .tile-name {
    text-decoration: line-through;
}

.tile-price {
    font-family: var(--font-mono);
    font-size: 16px;
    font-weight: bold;
    display: inline-block;
    background: var(--spotcolor);
    padding: 2px 6px;
}

.tile-tagline,
.tile-category {
    font-family: var(--font-mono);
    font-size: 16px;
    font-weight: normal;
}

.sold-out-label {
    position: absolute;
    top: 25%;
    left: 0; 
    right: 0; 
    margin-inline: auto; 
    width: fit-content;
    background: var(--black);
    color: var(--white);
    font-family: var(--font-hand);
    font-size: 18px;
    padding: 0.25em 2em;
    text-transform: uppercase;
    letter-spacing: .06em;
    z-index: 2;
    transform: rotate(-12deg);
}

/*
 * The pre-order tile label (BUILD "Pre-orders", 2026-11-14).
 *
 * TOP LEFT CORNER, not across the middle like .sold-out-label. The two labels
 * say different things and so sit differently: sold out is about the whole
 * tile and may cover the sticker, because there is nothing left to look at.
 * A pre-order is a thing being sold — the artwork is the pitch, so the label
 * gets out of its way and flags the corner instead.
 *
 * BLACK ON WHITE, not the black-on-yellow of the product page. The grid sits
 * ON the spot colour, so a #FFE365 label would be invisible here, and white
 * type on the spot colour is out by the brand guide. Which leaves the colour
 * and type .sold-out-label already uses, and sharing those is right: one
 * visual language for "read this before you click", two positions for two
 * meanings.
 *
 * transform-origin at the corner it is pinned to, so the tilt rotates the
 * label INTO the tile. Rotating about the centre, as .sold-out-label does,
 * would swing the bottom-left corner a few px out into the grid gutter.
 */
.preorder-label {
    position: absolute;
    top: 10px;
    left: 10px;
    background: var(--black);
    color: var(--white);
    font-family: var(--font-hand);
    font-size: 18px;
    text-transform: uppercase;
    letter-spacing: .06em;
    z-index: 2;
    transform: rotate(-2deg);
    transform-origin: top left;
    /*
     * NOWRAP, and less side padding than .sold-out-label's 2em.
     * "Pre-order" is a word and a half where "Sold out" is two short ones:
     * left to wrap it became a four-line block 160px wide on a 152px tile.
     */
    white-space: nowrap;
    padding: 0.25em 1em;
}

/*
 * The 2-column phone grid puts a ~152px tile on screen. Measured, not guessed:
 * 18px/1em gives 131px, 14px/0.7em gives 93px, against that 152px tile.
 */
@media (max-width: 768px) {
    .preorder-label {
        font-size: 14px;
        padding: 0.25em 0.7em;
    }
}

/* -----------------------------------------------------------------------
   Product detail
----------------------------------------------------------------------- */
.product-detail {
    display: grid;
    grid-template-columns: 1fr 360px;
    gap: 48px;
    align-items: start;
    margin-bottom: 48px;
}

/* Gallery: images stacked on desktop; the info column stays in view (sticky) */
.gallery-track {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 24px;
}

.gallery-slide img {
    width: 100%;
    height: auto;
    display: block;
}

/* The placeholder has no intrinsic size, so it keeps a square on every width */
.gallery-empty {
    width: 100%;
    aspect-ratio: 1;
    padding: 28px;
    background: #f0f0f0;
    display: flex;
    align-items: center;
    justify-content: center;
    color: #aaa;
}

.product-info {
    position: sticky;
    top: 24px;
}

.product-info .product-description a {
    text-decoration: underline;
    text-underline-offset: 4px;
}

.gallery-controls { display: none; }

.gallery-arrow {
    width: 44px;
    height: 44px;
    display: inline-flex;
    align-items: center;
    justify-content: center;
    background: var(--white);
    border: 2px solid var(--black);
    color: var(--black);
    cursor: pointer;
}

.gallery-arrow[aria-disabled="true"] { opacity: 0.3; cursor: default; }

.gallery-status {
    margin: 0;
    font-family: var(--font-mono);
    font-size: 14px;
}

.product-info h1 {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: 40px;
    line-height: 1.1;
    /* No letter-spacing, matching .tile-name — see there. */
    margin-bottom: 8px;
    text-transform: lowercase;
}

.product-tagline {
    font-family: var(--font-mono);
    font-size: 16px;
    font-weight: 700;
    color: #555;
    margin-bottom: 12px;
}

.product-size {
    font-family: var(--font-mono);
    font-size: 13px;
    color: #444;
    margin-bottom: 16px;
}

.product-meta {
    font-family: var(--font-mono);
    font-size: 12px;
    color: #777;
    margin-bottom: 16px;
}

.product-meta span { margin-right: 16px; }

.product-price {
    font-family: var(--font-mono);
    font-size: 32px;
    font-weight: bold;
    margin-bottom: 6px;
}

.product-description {
    font-family: var(--font-mono);
    font-size: 16px;
    line-height: 1.8;
    color: #333;
    border-top: 1px solid #e0e0e0;
    padding-top: 20px;
    margin-top: 20px;
    margin-bottom: 24px;
}

/* The description's paragraphs need this said explicitly: the reset at the top
   of this file zeroes every margin, so without it a multi-paragraph
   description runs together as one block. 14px matches .sidebar-prose p, which
   is the same kind of copy on the homepage and the theme pages.

   Selected by element for the same reason that rule is: the description goes
   through Html::allowlist(), which strips every attribute, so its paragraphs
   cannot carry a class.

   :last-child is zeroed because .product-description already sets its own
   margin-bottom. Left in, the two would stack to 38px above the add-to-cart
   form and the gap would no longer be the one this block declares. */
.product-description p {
    margin-bottom: 14px;
}

.product-description p:last-child {
    margin-bottom: 0;
}

.add-to-cart-form {
    display: flex;
    align-items: center;
    gap: 12px;
    flex-wrap: wrap;
    margin-bottom: 20px;
}

.qty-input {
    width: 64px;
    padding: 10px 8px;
    border: 2px solid var(--black);
    font-size: 16px;
    font-family: var(--font-mono);
    text-align: center;
    background: var(--white);
    -moz-appearance: textfield;
}

.qty-input::-webkit-inner-spin-button,
.qty-input::-webkit-outer-spin-button { opacity: 1; }

.add-confirm {
    font-family: var(--font-hand);
    font-size: 1.2em;
    font-weight: bold;
    color: #080;
}

.stock-warning {
    font-family: var(--font-mono);
    font-size: 12px;
    font-weight: bold;
    background: var(--spotcolor);
    color: var(--black);
    padding: 6px 12px;
    margin-bottom: 14px;
    display: inline-block;
}

/*
 * The product page's pre-order notice. Black on the spot colour, which is what
 * .stock-warning above already is — this page's established way of saying
 * something about availability inline, and the one place on the site where
 * black-on-yellow reads as intended, because the info column is on white.
 *
 * Its own rule rather than a second class on .stock-warning: it is a longer
 * sentence, it sits higher up the column, and the two can appear together
 * (a pre-order of three) so they need their own spacing.
 */
.preorder-notice {
    font-family: var(--font-mono);
    font-size: 13px;
    font-weight: bold;
    background: var(--spotcolor);
    color: var(--black);
    padding: 8px 14px;
    margin-bottom: 16px;
    display: inline-block;
}

.sold-out-msg {
    font-family: var(--font-mono);
    font-size: 13px;
    font-weight: bold;
    background: var(--black);
    color: var(--white);
    padding: 10px 18px;
    display: inline-block;
    text-transform: uppercase;
    letter-spacing: .05em;
}

/* -----------------------------------------------------------------------
   Buttons
----------------------------------------------------------------------- */
.btn {
    font-family: var(--font-mono);
    font-size: 18px;
    font-weight: bold;
    text-transform: uppercase;
    letter-spacing: .06em;
    border: 2px solid var(--black);
    padding: 10px 20px;
    cursor: pointer;
    text-decoration: none;
    display: inline-block;
    line-height: 1.4;
    background: var(--white);
    color: var(--black);
    transition: background 0.1s, color 0.1s;
}

.btn:hover { background: var(--black); color: var(--white); text-decoration: none; }
.btn-primary { background: var(--black); color: var(--white); }
.btn-primary:hover { background: #333; }
.btn-spot { background: var(--spotcolor); border-color: var(--black); color: var(--black); }
.btn-spot:hover { background: #f0d200; }
.btn-sm { padding: 5px 12px; font-size: 11px; }
.btn-danger { border-color: #c00; color: #c00; background: var(--white); }
.btn-danger:hover { background: #c00; color: var(--white); }
.btn-icon { display: inline-flex; align-items: center; justify-content: center; padding: 6px; line-height: 1; border: none; }

/* Skip link: off-screen until focused, then the first thing you see.
   Uses transform (not display/visibility) so it stays keyboard-reachable. */
.skip-link {
    position: absolute;
    top: 0;
    left: 0;
    z-index: 200;
    padding: 12px 18px;
    background: #fff;
    color: var(--black);
    border: 2px solid var(--black);
    font-family: var(--font-mono);
    font-size: 14px;
    text-decoration: underline;
    transform: translateY(-200%);
}
.skip-link:focus { transform: translateY(0); }

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

/* -----------------------------------------------------------------------
   Alerts
----------------------------------------------------------------------- */
.alert {
    padding: 10px 16px;
    border: 2px solid;
    margin-bottom: 16px;
    font-family: var(--font-mono);
    font-size: 13px;
}

.alert-error   { border-color: #c00; background: #fff0f0; color: #900; }
.alert-success { border-color: #080; background: #f0fff0; color: #050; }
.alert-info    { border-color: #06c; background: #f0f8ff; color: #036; }
.alert-warning { /*border-color: #840;*/ border: none; background: var(--spotcolor); color: #630; }

/* -----------------------------------------------------------------------
   Checkout result (success / cancel)
----------------------------------------------------------------------- */
.checkout-result {
    max-width: 620px;
    margin-left: auto;
    margin-right: auto;
    text-align: center;
}

.result-mark {
    font-family: var(--font-hand);
    font-size: 64px;
    margin-bottom: 8px;
}

.result-title {
    font-family: var(--font-hand);
    font-size: 40px;
    font-weight: 400;
    margin-bottom: 16px;
}

.result-text {
    font-family: var(--font-mono);
    font-size: 14px;
    color: #444;
    margin-bottom: 36px;
}

.result-actions { margin-top: 36px; }
.result-actions .btn + .btn { margin-left: 10px; }

/* Receipt: the cart table, left-aligned inside the centred block */
.receipt-table { text-align: left; }
.receipt-table .receipt-qty    { text-align: right; width: 4em; }
.receipt-table .receipt-amount { text-align: right; width: 8em; white-space: nowrap; }

.checkout-result .cart-totals { margin-left: auto; margin-right: 0; text-align: left; }

.result-reference {
    font-family: var(--font-mono);
    font-size: 11px;
    color: #666;
    text-align: right;
    margin: 0;
}
.result-reference-id { word-break: break-all; }

@media (max-width: 600px) {
    .checkout-result .cart-totals { max-width: none; }
    .result-reference { text-align: left; }
}

/* -----------------------------------------------------------------------
   Cart
----------------------------------------------------------------------- */
.cart-table {
    width: 100%;
    border-collapse: collapse;
    margin-bottom: 24px;
    font-family: var(--font-mono);
}

.cart-table th {
    text-align: left;
    border-bottom: 2px solid var(--black);
    padding: 8px;
    font-size: 16px;
    text-transform: uppercase;
    letter-spacing: .06em;
}

.cart-table td {
    border-bottom: 1px dashed #000;
    padding: 14px 8px;
    font-size: 16px;
    vertical-align: middle;
}

.cart-table a { text-decoration: underline; }

/* Was an inline style="text-align:right" on both the head cell and the body
   cell. Moved here because an inline declaration cannot be overridden by the
   mobile grid below without !important. */
.cart-col-line,
.cart-cell-line { text-align: right; }

.cart-thumb { width: 56px; height: 56px; object-fit: contain; background: #f5f5f5; }
.cart-thumb-empty { width: 56px; height: 56px; background: #f5f5f5; }
.cart-warning { font-size: 11px; color: #840; margin-top: 4px; }

/* The labels over the two amounts. Only ever shown by the mobile grid; on a
   wide screen the column heads do this job and these stay off. */
.cart-cell-unit::before,
.cart-cell-qty::before,
.cart-cell-line::before { display: none; }

/* -----------------------------------------------------------------------
   The cart table on a phone

   The five fixed columns add up to 390px before the product name gets a
   pixel, so below about 585px the table is wider than the screen and the
   page scrolls sideways — taking the remove button out of reach, which is
   the part that actually mattered.

   So below 600px each row stops being a row of cells and becomes a small
   two-line block:

       [thumb] product name ............... [x]
       [thumb] PRICE        QTY      SUBTOTAL

   The table element, its rows and its cells keep their roles (written out
   in cart.php) because `display: grid` here would otherwise strip them and
   the column heads would stop naming the cells.
----------------------------------------------------------------------- */
@media (max-width: 600px) {
    /* Off the screen, not out of the tree: this row is still what tells a
       screen reader that "€ 14,00" is the price. Same recipe as
       .visually-hidden, which cannot be put on a <thead> that is only hidden
       at this width. */
    .cart-table thead tr {
        position: absolute;
        width: 1px;
        height: 1px;
        overflow: hidden;
        clip-path: inset(50%);
        white-space: nowrap;
    }

    .cart-table tbody tr {
        display: grid;
        grid-template-columns: 56px minmax(72px, auto) minmax(56px, 1fr) auto;
        grid-template-areas:
            "thumb name  name remove"
            "thumb price qty  total";
        gap: 10px 10px;
        align-items: center;
        /* The dashed rule moves from the cells to the row. On the grid it
           would otherwise be drawn under each cell separately. */
        border-bottom: 1px dashed #000;
        padding: 14px 0;
    }

    .cart-table tbody td {
        border-bottom: none;
        padding: 0;
    }

    .cart-cell-thumb  { grid-area: thumb; align-self: start; }
    .cart-cell-name   { grid-area: name; }
    .cart-cell-unit   { grid-area: price; }
    .cart-cell-qty    { grid-area: qty; }
    .cart-cell-line   { grid-area: total; }
    .cart-cell-remove { grid-area: remove; justify-self: end; }

    /* Top, not centre. The quantity cell is taller than the two amounts
       beside it (a 33px field under its caption against one line of text),
       and centring each in the track staggered the three captions. Aligned
       to the top they sit on one line and the row reads as a strip. */
    .cart-cell-unit,
    .cart-cell-qty,
    .cart-cell-line { align-self: start; }

    /* "Quantity", not "Qty": the field's accessible name is "Quantity for
       <product>", and a visible label has to be contained in the accessible
       name or voice control cannot address the control by what it says
       (WCAG 2.5.3). The caption is decoration — the real label is the
       aria-label on the input. */
    .cart-cell-unit::before,
    .cart-cell-qty::before,
    .cart-cell-line::before {
        content: attr(data-label);
        display: block;
        font-size: 11px;
        text-transform: uppercase;
        letter-spacing: .06em;
        /* 7.0:1 on white — the amounts themselves stay black. */
        color: #595959;
    }
}

/* Under about 360px the four columns and their gaps no longer fit at the full
   thumbnail size, and the quantity field is the one that gives. Shrink the
   picture instead: it is the only thing here that is decoration. */
@media (max-width: 380px) {
    .cart-table tbody tr {
        grid-template-columns: 44px minmax(68px, auto) minmax(56px, 1fr) auto;
        gap: 8px;
    }

    .cart-table .cart-thumb,
    .cart-table .cart-thumb-empty { width: 44px; height: 44px; }
}

.cart-qty-input {
    width: 56px;
    padding: 5px 6px;
    border: 2px solid var(--black);
    font-size: 16px;
    font-family: var(--font-mono);
    text-align: center;
}

.cart-totals {
    max-width: 380px;
    margin-left: auto;
    border: 2px solid var(--black);
    padding: 20px;
    font-family: var(--font-mono);
    margin-bottom: 24px;
}

.checkout-result .cart-totals {
    max-width: none;
    border: none;
    padding-left: 0;
    padding-right: 0;
}

.totals-row {
    display: flex;
    justify-content: space-between;
    padding: 7px 0;
    font-size: 14px;
    border-bottom: 1px solid #eee;
}

.totals-row.total {
    font-weight: bold;
    font-size: 18px;
    border-bottom: none;
    border-top: 2px solid var(--black);
    padding-top: 12px;
    margin-top: 4px;
}

.cart-actions {
    display: flex;
    flex-direction: column;
    align-items: flex-end;
    margin-bottom: 48px;
    gap: 8px;
}

/* Two flex items only: the box and the <span> holding the whole sentence. The
   span is load-bearing — see the note beside it in cart.php. flex-start rather
   than center so that when the sentence wraps on a phone the box stays on the
   first line instead of floating beside the middle of the block. */
.cart-terms-label {
    display: flex;
    align-items: flex-start;
    gap: 8px;
    font-size: 13px;
    cursor: pointer;
}

.cart-terms-label a {
    text-decoration: underline;
}

/* -----------------------------------------------------------------------
   Checkboxes — the shop's two, which sit in the same box on the cart and so
   cannot look different from each other. The PIM has its own stylesheet and
   keeps the native control.

   Native rendering is ~13px and rounded, which is neither the size nor the
   shape of anything else here: a 20px square with a 1px black border matches
   the inputs and buttons around it. appearance:none is what makes that
   possible, and it also removes the native tick, hence the ::after.

   Focus is left to the global :focus-visible rule — 3px outline, 2px offset —
   which is why nothing here touches outline.
----------------------------------------------------------------------- */
.cart-terms-label input[type="checkbox"],
.cart-business input[type="checkbox"] {
    appearance: none;
    -webkit-appearance: none;
    width: 20px;
    height: 20px;
    flex: 0 0 auto;
    margin: 0;
    border: 1px solid var(--black);
    border-radius: 0;
    background: var(--white, #fff);
    cursor: pointer;
    display: grid;
    place-content: center;
}

/* The tick: two borders of a box, rotated. Drawn rather than a glyph so it
   cannot pick up a font that is not loaded yet. */
.cart-terms-label input[type="checkbox"]::after,
.cart-business input[type="checkbox"]::after {
    content: '';
    width: 5px;
    height: 10px;
    border: solid var(--black);
    border-width: 0 2px 2px 0;
    transform: translateY(-1px) rotate(45deg);
    opacity: 0;
}

.cart-terms-label input[type="checkbox"]:checked::after,
.cart-business input[type="checkbox"]:checked::after {
    opacity: 1;
}

/* Disabled: grey, and not clickable-looking. Only the business one can reach
   this state — below the € 50 floor. */
.cart-business input[type="checkbox"]:disabled {
    border-color: #767676;
    cursor: default;
}

.cart-business input[type="checkbox"]:disabled::after {
    border-color: #767676;
}

/*
 * The cart's pre-order sentence. The spot colour and a 2px black border, which
 * is the shop's own "this is on" signal — the same treatment as .cart-pickup,
 * and for the same reason: this is a statement of fact about the order, not a
 * warning about it. .alert-warning's #630 text is for things that need fixing.
 *
 * align-self, because .cart-actions is align-items: flex-end and a sentence
 * ragged against the right edge of a column reads as a column, not a sentence.
 */
.cart-preorder {
    align-self: stretch;
    background: var(--spotcolor);
    border: 2px solid var(--black);
    padding: 10px 12px;
    font-family: var(--font-mono);
    font-size: 13px;
    color: var(--black);
    margin-bottom: 4px;
}

.cart-preorder[hidden] { display: none; }

.cart-terms-error {
    color: #CC0000;
    font-size: 12px;
    margin: 0;
}

#checkout-btn {
    margin-top: 0.75rem;
}

/* -----------------------------------------------------------------------
   Footer
----------------------------------------------------------------------- */
.site-footer {
    background: transparent;
    color: var(--black);
    font-family: var(--font-mono);
    margin-top: 48px;
    /* The whole footer is tilted, menu and strip together, so the two read as
       one object rather than a straight block with a crooked hem.
       A -2deg rotation moves the corners about 22px vertically at 1280px wide:
       .footer-menu's top padding absorbs the left corner rising into the
       content above, and the bottom padding here absorbs the opposite corner
       dropping below the page. */
    transform: rotate(-1deg);
    padding-bottom: 28px;
    /* The footer opens with the same dashed rule the legal strip closes with,
       so the whole block is bracketed by the device rather than cut by it
       once in the middle. */
    border-top: 2px dashed var(--white);
}

/* -----------------------------------------------------------------------
   Footer menu — three columns above the legal strip

   It is inside <footer> rather than in front of it, so it is inside the
   contentinfo landmark; the partial says why at length. It is a separate
   block from .footer-bar because the strip is tilted and a tilted menu would
   read as a mistake rather than as the device the strip is.
----------------------------------------------------------------------- */
.footer-menu {
    padding: 24px 0;
}

.footer-menu-inner {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 32px 48px;
    align-items: start;
}

.footer-heading {
    font-family: var(--font-hand);
    font-weight: 400;
    font-style: normal;
    font-size: 32px;
    line-height: 1.1;
    margin-bottom: 12px;
}

/* The wordmark at the head of the first column. Sized by width alone — the
   artwork is 270x22 and height:auto keeps that ratio whatever the width.

   No tilt of its own. The whole .site-footer is already at -1deg and the logo
   inherits it, which is within half a degree of the -1.5deg it carries in the
   header; adding its own -1.5deg on top would stack to -2.5deg and put it
   visibly out of step with the column underneath it. */
.footer-wordmark {
    /* 290px is the cap, not the size: the column is narrower than that below
       about 1150px and on a stacked phone layout, and width:100% lets the mark
       come down with it rather than overflow. Past 270px the artwork is being
       scaled up, which costs nothing — it is vector — but it is why there is a
       ceiling at all. */
    width: 100%;
    max-width: 290px;
    height: auto;
    margin: 8px 0 18px;
}

.footer-col ul {
    list-style: none;
}

.footer-col li,
.footer-col p {
    font-size: 14px;
    line-height: 1.9;
}

.footer-col a {
    color: inherit;
    text-decoration: underline;
    text-underline-offset: 4px;
}

/* The page you are already on. A thicker rule rather than colour, which would
   be the only cue for anyone who cannot see it, and rather than a bold weight,
   because the mono face is variable and 700 shifts the line's width. */
.footer-col a[aria-current="page"] {
    text-decoration-thickness: 2px;
}

/* The Instagram column is a panel rather than a third list, and the whole
   panel is the link — see .footer-instagram::after below.

   position: relative is what that overlay is measured against. The 2px border
   is transparent in the resting state and the padding is 2px short of what it
   used to be, so the black border on hover costs no layout: the panel does not
   grow and the text under it does not move. */
.footer-col-follow {
    position: relative;
    background: var(--spotcolor);
    border: 2px solid transparent;
    padding: 18px 22px 22px;
}

/* :focus-within as well as :hover, because reaching the link by keyboard puts
   the global focus ring around the handle alone — eleven characters inside a
   panel that is entirely clickable. The border says how big the target is. */
.footer-col-follow:hover,
.footer-col-follow:focus-within {
    border-color: var(--black);
}

/* White on the homepage, because there the whole page behind the footer is
   already --spotcolor and the panel would be invisible. It is the background
   that flips, not the panel: the point is a block that stands off whatever is
   behind it, and on every other page --spotcolor is what does that. */
.page-home .footer-col-follow {
    background: var(--white);
}

.footer-instagram {
    display: inline-flex;
    align-items: center;
    gap: 8px;
    margin-top: 6px;
    font-size: 14px;
}

/* The <img> is display:block site-wide, which would drop it onto its own line
   inside the inline-flex link. */
.footer-instagram img {
    display: block;
    flex: 0 0 auto;
}

/* What makes the whole panel clickable without wrapping it in an <a>. An
   overlay on the link, stretched over its positioned ancestor — so the link's
   hit area is the panel while the link's CONTENT stays "@add.some.spite".
   Wrapping the panel instead would have handed a screen reader one link whose
   name is the heading, the sentence and the handle run together.

   inset is -2px rather than 0 so the overlay covers the border ring too, and
   the panel is clickable exactly where it draws the hover border.

   The cost, and it is a real one: text inside the panel can no longer be
   selected, because the overlay is above it. Nothing in there is worth
   copying — a sentence and a handle that is also the link — so it is the
   cheaper side of the trade. Giving the <p> a position would win the text
   back and lose the click. */
.footer-instagram::after {
    content: '';
    position: absolute;
    inset: -2px;
}

/* -----------------------------------------------------------------------
   Footer legal strip — the tilted band at the very bottom
----------------------------------------------------------------------- */
.footer-bar {
    padding: 20px 0;
    font-size: 12px;
    border-top: 2px dashed var(--white);
}

.footer-bar .container {
    display: flex;
    align-items: center;
    gap: 24px;
}

.footer-bar a {
    color: inherit;
    text-decoration: underline;
}

@media (max-width: 768px) {
    .footer-menu-inner {
        grid-template-columns: 1fr;
        gap: 28px;
    }
}

@media (max-width: 600px) {
    .footer-bar .container {
        flex-direction: column;
        align-items: center;
        gap: 8px;
    }
}

/* Both dashed rules — the one that opens the footer and the one above the
   legal strip — are white against the homepage's yellow and black against the
   white of every inner page. */
.page-cart .site-footer, .page-product .site-footer, .page-theme .site-footer,
.page-prose .site-footer,
.page-cart .footer-bar, .page-product .footer-bar, .page-theme .footer-bar,
.page-prose .footer-bar {
    border-color: var(--black);
}

/* -----------------------------------------------------------------------
   Misc
----------------------------------------------------------------------- */
.empty-state {
    padding: 56px 0;
    font-family: var(--font-mono);
    font-size: 14px;
    color: #666;
}

.empty-state p { margin-bottom: 20px; }

/* -----------------------------------------------------------------------
   Responsive
----------------------------------------------------------------------- */
@media (max-width: 1100px) {
    .product-grid { grid-template-columns: repeat(2, 1fr); }
}

@media (max-width: 768px) {
    :root {
        --clip-full: polygon(0 0, 100% 0, 100% 100%, 0 100%);
        --clip-bar:  polygon(0 0, 100% 0, 100% 68px, 0 90px);
    }
    /* The circle's own z-index below is not enough by itself. .site-header is
       position:relative with z-index:1, which makes it a stacking context, so
       that 100 only ranks the circle against the wordmark beside it — against
       the rest of the page the whole header counts as 1. .filter-toggle is
       z-index 1 when checked and 2 on hover, sits in the root stacking context
       and comes later in the DOM, so it scrolled over the circle. Lifting the
       header is what actually puts the circle on top; the circle keeps its own
       100 to stay above the wordmark inside. The header's box is only the strip
       at the top of the page, so nothing further down starts catching clicks.
       The skip link stays above both at 200. */
    .site-header { z-index: 100; }

    .cart-circle {
        position: fixed;
        top: 16px;
        right: 16px;
        z-index: 100;
        border: 3px solid var(--spotcolor);
    }
    /* Absolute on /about as well as the cart, and for the same reason: there
       is nothing on either page to add to a basket, so a circle floating over
       the content is in the way rather than within reach. The product and
       theme pages keep it fixed, because there it is the thing you press after
       choosing something. */
    .page-cart .cart-circle, .page-prose .cart-circle { position: absolute; }

    /* The circle floats over the top of the page from here down, so the
       filter has to stop short of it when filter.js scrolls it into view —
       its inset, its own size, and 12px of air, the same three numbers the
       wordmark cap below is built from. */
    .product-filter {
        scroll-margin-top: calc(16px + var(--cart-circle-size) + 12px);
    }

    /* The circle is fixed at the top right from here down, so the wordmark has
       to stop short of it rather than run underneath. What is left is the
       viewport minus the circle, the 16px it is inset by, .container's 24px of
       left padding, and 12px of air between the two — 52px of fixed space plus
       the circle's own width.

       A ceiling, not a width: --wordmark-fit takes the smaller of this and
       whatever size the page asked for, so between roughly 520 and 768px,
       where the clamp()s already fit, this changes nothing. Below that it is
       the binding constraint and the wordmark shrinks past the clamp's 280px
       floor, which is the floor that used to put it under the circle.

       Set on .site-name alone: .page-home overrides --wordmark-w, never this,
       so there is no specificity contest to win here. */
    .site-name {
        --wordmark-max: calc(100vw - var(--cart-circle-size) - 52px);
    }
    .home-layout { grid-template-columns: 1fr; gap: 20px 0; padding: 16px 20px 48px; }

    .product-detail { grid-template-columns: 1fr; gap: 24px; }

    /* Gallery becomes a horizontal swipe row with arrow buttons */
    .product-info { position: static; }
    .gallery-track {
        flex-direction: row;
        gap: 0;
        overflow-x: auto;
        scroll-snap-type: x mandatory;
        scrollbar-width: none;
    }
    .gallery-track::-webkit-scrollbar { display: none; }
    .gallery-slide { flex: 0 0 100%; scroll-snap-align: start; }
    /* One height for every slide, so the content below doesn't jump while swiping.
       On desktop the images stack, so there is nothing to keep still — they run
       at their own height with the track's 24px gap between them. */
    .gallery-slide img {
        aspect-ratio: 1;
        object-fit: contain;
        padding: 28px;
    }
    .gallery-controls {
        display: flex;
        align-items: center;
        justify-content: center;
        gap: 16px;
        margin-top: 8px;
    }
}

@media (max-width: 520px) {
    .product-grid { grid-template-columns: repeat(2, 1fr); gap: 14px; }
    .home-products { padding: 20px 16px; }
    .page-content { padding: 24px 16px 48px; }
    .tile-name { font-size: 21px; }

    /* The back link and the h1 stop sharing a line. Only the cart bar holds
       both — the product, theme and prose bars are a link on their own, so
       for them this is a no-op.

       Side by side the two need 438px unwrapped ("Continue shopping" 188,
       "shopping cart" 250 in the wide hand face), and the bar still has 488
       at this width. So they do fit here; what they do not survive is about
       470px, below which BOTH wrap internally and the bar turns into four
       ragged lines against each other. Stacking slightly early is cheaper
       than stacking badly, and 520 is already the phone breakpoint.

       Link first, in DOM order. The heading on top would read better, but
       column-reverse would put the visual order out of step with the tab
       order, which is not a trade this shop makes. */
    .page-header {
        flex-direction: column;
        align-items: flex-start;
        gap: 10px;
    }
}

/* ---------------------------------------------------------------------------
   Pack contents on the product page (PRD "Packs")
   --------------------------------------------------------------------------- */

.pack-contents {
    margin: 0 0 20px;
    border: 1px solid var(--color-border, #000);
    padding: 12px 14px;
}

.pack-contents-heading {
    font-size: 13px;
    text-transform: uppercase;
    letter-spacing: 0.04em;
    margin: 0 0 10px;
}

.pack-contents-list {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 8px;
}

.pack-contents-item {
    display: flex;
    align-items: center;
    gap: 10px;
}

.pack-contents-thumb {
    width: 48px;
    height: 48px;
    object-fit: contain;
    /*border: 1px solid var(--color-border, #000);*/
    flex: 0 0 auto;
}

.pack-contents-thumb-empty {
    display: block;
}

/* ---------------------------------------------------------------------------
   Delivery country selector (PRD "Shipping by country — phase 1")
   --------------------------------------------------------------------------- */

/* Selector left, totals right. The wrapper carries the layout so .cart-totals
   keeps its own rules — it is reused on the thank-you page, which has no
   selector beside it. */
.cart-summary {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
    gap: 24px;
    margin-top: 24px;
}

.cart-summary .cart-shipping-country {
    flex: 1 1 16rem;
    max-width: 26rem;
}

/* Keeps its 380px, shrinking before it overflows a narrow desktop window.
   margin-left: auto still pushes it right when the two do not fill the row. */
.cart-summary .cart-totals {
    flex: 0 1 380px;
    margin-top: 0;
}

.cart-shipping-country {
    padding: 12px 14px;
    border: 1px solid var(--color-border, #000);
}

.cart-shipping-country label {
    display: block;
    font-weight: 700;
    margin-bottom: 6px;
}

.cart-shipping-country select {
    width: 100%;
    padding: 6px 8px;
    border: 1px solid var(--color-border, #000);
    background: #fff;
    font: inherit;
}

.cart-shipping-country[data-invalid] select,
.cart-shipping-country select[aria-invalid="true"] {
    border-color: #c00;
    border-width: 2px;
}

.cart-shipping-country .hint {
    margin: 6px 0 0;
    font-size: 12px;
    color: #666;
}

.cart-shipping-country .field-error {
    margin: 6px 0 0;
    font-size: 13px;
    font-weight: 700;
    color: #c00;
}

/* Collection in person (BUILD "Collect in person"). Sits in the same box as
   the country selector and takes its place — see cart.php.

   The spot colour and the 2px black border are the shop's own "this is on"
   signal, the same pair the selected filter chip and the footer follow panel
   use. It is a STATE, not a control: the only thing to press is the way back
   out, which is why the button is the plain .btn-sm rather than the primary.

   No margin-bottom. The business checkbox below brings its own top margin, and
   when the box holds only this panel there is nothing underneath to space. */
.cart-pickup {
    background: var(--spotcolor);
    border: 2px solid var(--black);
    padding: 10px 12px;
}

.cart-pickup-head {
    margin: 0;
    font-weight: 700;
}

.cart-pickup .hint {
    /* Overrides .cart-shipping-country .hint's #666, which is a grey chosen
       against white and measures 4.49:1 on the spot colour — a hair under AA.
       Black is what the rest of the yellow panels use, and 16.4:1.

       THIS BLOCK MUST STAY BELOW .cart-shipping-country .hint. The two
       selectors have the same specificity, so source order is the only thing
       deciding which colour wins. */
    margin: 4px 0 10px;
    font-size: 13px;
    color: var(--black);
}

/* White, not the inherited transparent, so the button reads as a control
   against the yellow panel rather than as part of it.

   The :hover line is not decoration — it is a fix. .btn:hover is also 0-2-0,
   so the rule above it here wins on source order and kept the background
   white while .btn:hover still set color:white: invisible label. Restating
   the black background at the same specificity is what lets the hover
   through. */
.cart-pickup .btn { background: #fff; }
.cart-pickup .btn:hover { background: var(--black); }

/* The export minimum notice, under the country selector. .alert's own
   margin-bottom is for a stacked column of alerts at the top of a page; here it
   is a single block ending a group, so the spacing is flipped. */
#export-min-warning {
    margin: 10px 0 0;
    transform: rotate(2deg);
}

/* "Choose a country" where an amount would otherwise be. Not greyed out to the
   point of being hard to read: it is the instruction, not a disabled state. */
.totals-unknown {
    font-style: italic;
    color: #555;
}

/* One column before the two get too narrow to read: a 380px totals box plus a
   16rem selector needs roughly 700px once the gap and padding are counted. */
@media (max-width: 720px) {
    .cart-summary {
        display: block;
    }

    .cart-summary .cart-shipping-country {
        max-width: none;
        margin-bottom: 24px;
    }
}

/* Business / reverse-charge option on the cart (#25) */
.cart-business {
    margin-top: 12px;
    padding-top: 12px;
    border-top: 1px solid var(--color-border, #000);
}

.cart-business label {
    display: flex;
    align-items: flex-start;
    gap: 8px;
    font-weight: 400;
    cursor: pointer;
}

/* The business label wraps to two lines and aligns flex-start, so the box needs
   nudging down to sit on the first line rather than above it. The terms label
   aligns flex-start too but is set at 13px, whose line box is shorter than the
   20px control, so there is nothing to nudge it past. */
.cart-business input[type="checkbox"] {
    margin-top: 3px;
}

.cart-business .hint {
    margin: 6px 0 0;
    font-size: 12px;
    color: #666;
}

/* Below the € 50 floor the checkbox is disabled, so it has to LOOK disabled —
   the mistake the checkout button was deliberately spared (see BUILD "A € 25
   minimum"). Only the label dims: an inactive control is exempt from the
   contrast minimum, but the hint beside it is carrying the reason and must stay
   as readable as ever. */
.cart-business:has(input[type="checkbox"]:disabled) label {
    color: #767676;
    cursor: default;
}

/* Why a B2B cart shows no gross total. Not a warning — a statement of fact. */
.totals-note {
    margin-top: 10px;
    padding-top: 10px;
    border-top: 1px solid #eee;
    font-size: 12px;
    color: #555;
}
