/* =============================================================
 * SUPERFLY — SINGLE PRODUCT
 *
 * Shape: revamp/product-b.html, itself a measured reconstruction
 * of the Lupine product page.
 *
 *   ┌───────────────┬──────────────────────────────────────────┐
 *   │ ★★★★★ 0 REVIEWS│                                          │
 *   │ PROJECT X      │            (gallery, 4:3)                │
 *   │ 4 SPOKE RIMS   │                                          │
 *   │ RM448 – RM475  │                                          │
 *   │ [qty][ADD CART]├──────────────────────────────────────────┤
 *   │ SKU / Category │  GOES WELL WITH                          │
 *   │ ─────────────  │  ┌─────┐ ┌─────┐ ┌─────┐                 │
 *   │ short descr.   │  DESCRIPTION / REVIEWS                   │
 *   └───────────────┴──────────────────────────────────────────┘
 *     sticky, 470px      scrolls past it
 *
 * THE SIDES ARE SWAPPED from WooCommerce's default (gallery left,
 * buy panel right). The buy rail is LEFT, in the same 470px slot
 * the category page's filter rail occupies, so moving from a
 * category to a product does not move the page furniture.
 *
 * ---- THE MEASUREMENTS ----
 * Read off the reference at a 1425px content width.
 *
 *   layout        grid 470px + the rest
 *   rail          sticky top 48, padding 48 → 374 content
 *   title         60px / 54px uppercase
 *   price         tech 16px / 18.4, letter-spacing .64
 *   purchase row  height 56; the button 176x56
 *   add to cart   tech 10px / 12, ls 1, radius 2
 *   description   margin-top 48; 14px / 18.48, ls .24, #878787
 *   gallery       padding 48, stage 4:3a
 *   editorial     column, gap 48, padding 0 48, margin-top 48
 *   section head  40px / 40, ls .8, uppercase
 *   card          column gap 24; image 4/5 radius 2; content gap 8
 *   story h2      110px / 99 uppercase  (only if the description
 *                 has headings — see section 6)
 *
 * ---- WHY A SEPARATE FILE ----
 * woocommerce.css skins everything WooCommerce draws, cart and
 * account included. This changes the product page only, loads
 * after it, and is enqueued only on is_product() — so a mistake
 * here cannot reach the cart, and reverting is one enqueue line.
 * It overrides woocommerce.css section 5 ("One product").
 *
 * ---- MARKUP IS WOOCOMMERCE'S OWN ----
 * WooCommerce 11.1.1 renders this page with BLOCKS, not the
 * legacy PHP template — there is no .summary.entry-summary on the
 * page at all. The class names below are the plugin's and were
 * read off the live page, not guessed. The `sf-pdp*` classes are
 * ours, set in templates/single-product.html.
 *
 * Type is the house trio; the accent is SUPERFLY's #ec1e79.
 *
 * Enqueue: functions.php — superfly_single_product_assets()
 * Markup:  templates/single-product.html
 * Concept: revamp/product-b.html
 * ============================================================= */

/* BOTH SELECTORS, NOT JUST .sf-pdp. The editorial stack was moved OUT of
   the columns block (see the note in templates/single-product.html), which
   took it outside the element these are declared on - so every single one
   of them became undefined inside it. A `var()` that resolves to nothing
   makes the whole declaration invalid at computed-value time and the
   property silently falls back to the inherited value, which is why
   "RELATED PRODUCTS" rendered in Archivo instead of Archivo Black: the
   rule asked for var(--sp-title) and got nothing.

   It read as a font bug and it was not. --sp-accent, --sp-line, --sp-radius
   and the rest were all gone too; several of them merely happened to match
   what the theme inherits, which is luck, not correctness. Anything added
   to this list must stay available to both. */
/* ---- THE PRODUCT PAGE IS LIGHT (operator, 2026-10-23) -----------------
 *
 * "i want exactly same like this ... light theme also like this button
 * color also like this later i will change by myself", with the
 * logitechg.com Yeti 2 page as the reference.
 *
 * ONLY THIS PAGE. single-product.css is enqueued on is_product() alone —
 * see superfly_single_product_assets() — so the shop, the home page and
 * every information page keep the carbon. The light band is painted on
 * .sf-pdp and .sf-pdp__editorial rather than on <body>, because body
 * carries the carbon weave for the HEADER AND FOOTER TOO: whitening it
 * would turn the navbar's white logo and the footer's light type
 * invisible. See the note on the band below.
 *
 * THE COLOURS ARE THE REFERENCE'S, NOT THE BRAND'S. --sp-accent is
 * Logitech's cyan, not SUPERFLY's #ec1e79, because the operator asked for
 * that button colour explicitly and said they will change it themselves.
 * So: to take this page back to the brand, the whole job is the four
 * values in THE LIGHT PALETTE below — everything downstream reads them.
 * The dark values are kept beside them, commented, for the same reason.
 *
 * The tokens have to stay available to BOTH selectors — the original
 * reason is in the note above this block and has not changed. */
.sf-pdp,
.sf-pdp__editorial {
	/* ---- THE CARBON PALETTE (operator, 2026-10-26) ----
	 *
	 * Back to dark, keeping the reference's ARRANGEMENT. The light band
	 * was the operator's call on 2026-10-23 ("light theme also like this
	 * button color also like this later i will change by myself"); the
	 * later half of that sentence is what this is. They rebuilt the test
	 * page in carbon with the brand magenta and real SUPERFLY photography
	 * and asked for the product page to follow it.
	 *
	 * NOTHING BUT COLOUR CHANGED. The tile grid, the buy box, the
	 * dropdowns and the editorial stack are the same rules they were
	 * under the light palette — which is the whole point of the file
	 * being written this way, and the second time now that the page has
	 * been flipped by editing this block alone.
	 *
	 * The light values are kept beside each one, as the dark values were
	 * kept here before. */
	--sp-bg:     #101014;             /* was #ffffff */
	--sp-text:   #f2f2f4;             /* was #1b1b1b */
	--sp-muted:  #9a9a9f;             /* was #6e7076 */
	--sp-faint:  rgba(242, 242, 244, 0.42);
	--sp-line:   rgba(242, 242, 244, 0.16);
	--sp-hair:   rgba(242, 242, 244, 0.10);
	--sp-accent: #ec1e79;             /* was #00b8fc — the brand magenta */
	/* WHITE PLATES ON A CARBON PAGE, which is what this value was before
	   the light band and is not an oversight. Nearly every photograph in
	   this catalogue is a part shot on a white studio background: on a
	   #15151a tile each one renders as a white square with a thin dark
	   frame around it, which reads as a border someone forgot to remove.
	   Deployed dark at #15151a first and measured it on product 889 —
	   eight white squares on carbon. A white plate simply contains them.
	   The test page the operator built looked right with a dark tile
	   because its pictures were dark lifestyle shots, not studio cutouts;
	   when this catalogue has those, this is the value to revisit. */
	--sp-tile:   #ffffff;             /* was #eaebed */
	--sp-dark:   #0f0f0f;             /* was #f2f2f3 */
	--sp-radius: 2px;

	/* ---- derived, so a palette change carries ---- */
	/* the face of every control plate: the quantity box, the editorial
	   buttons. Kept FLAT, as the light version made them — the reference's
	   controls are flat with a hairline, and the old neumorphic highlight
	   belonged to a different design, not to this one being dark. */
	--sp-plate:        #15151a;
	--sp-plate-shadow: none;

	/* Text on --sp-accent. WHITE BY THE OPERATOR'S DECISION (2026-11-02:
	   "i want color white"). It is the one value that does NOT simply
	   follow the accent, which is why it is stated here rather than
	   hardcoded into the button.

	   KNOW WHAT THIS COSTS. Measured against #ec1e79, not estimated:

	       black  5.03:1   passes AA
	       white  4.18:1   FAILS AA for normal text (needs 4.5)

	   The old note here claimed 4.6:1 for white, which was wrong and is
	   why the trade looked free. The ADD TO CART label is 12px, weight
	   500 — nowhere near the 18.66px-bold large-text exemption — so this
	   is a genuine AA failure on the page's single most important
	   control, and the hover tint is worse again at 3.63:1.

	   TO KEEP WHITE AND PASS: darken the pill a little. 95% of the
	   accent, #e01c73, takes white to 4.58:1 and is barely tellable from
	   the brand magenta. Not done here because --sp-accent is the brand
	   colour and that is the operator's call, not a style fix. */
	--sp-accent-fg: #ffffff;

	/* the price is the brightest text on the page, not the accent */
	--sp-price: #f2f2f4;

	/* in stock. #0a7d2f is the reference's green and it is unreadable on
	   black — measured 1.9:1. This one is 9.4:1 on the carbon. */
	--sp-stock: #4ade80;

	--sp-title: "Archivo Black", "Arial Black", sans-serif;
	--sp-body:  "Archivo", "Inter", sans-serif;
	--sp-tech:  "Chakra Petch", "Archivo", sans-serif;

	--sp-step: 10px;

	/* THIS PAGE KEEPS THE 1300px MEASURE ON ITS OWN, and it has to be a local
	   literal rather than --sf-measure: that token went to "none" on
	   2026-11-17 when every other page was uncapped, and the four padding
	   rules below feed it to calc(). calc(none - ...) is INVALID, which drops
	   the declaration silently and takes the page gutter with it.

	   The product page was NOT part of that change and is a separate
	   decision: it is the only page on a different gutter system (--sp-step,
	   a flat 48px) rather than --sf-gutter, so matching it means moving both
	   numbers, not one. Ask before doing it. */
	/* READ BY NOTHING since 2026-11-17, when this page went full bleed with
	   the rest of the site. It was introduced one day earlier, purely so the
	   two padding sums below could not be invalidated by --sf-measure going
	   to "none" -- and then both sums were replaced by a flat --sf-gutter,
	   which needs no measure at all. Kept because restoring the cap means
	   this value and the two sums, and because 1300 is still what the rest of
	   the site would return to. */
	--sp-measure: 1300px;
	/* 50%, NOT A LENGTH, SINCE 2026-11-18 (operator: "right now i want you
	   make it 50/50 like first image", against yucca.co.za's product page,
	   where the picture and the buy column are near enough the same width).
	 *
	 * .sf-pdp__gallery is `flex: 1 1 0` and takes whatever is left of the
	 * row, so one half here makes the two columns equal at every width with
	 * no second number to keep in step. Measured at a 1430px client: gallery
	 * 654, rail 654, the gallery stage 598 square -- the reference's own
	 * image panel measures 603 at the same width.
	 *
	 * A PERCENTAGE RESOLVES AGAINST .sf-pdp's CONTENT BOX, which is the
	 * painted width less --sf-gutter either side, so the split follows the
	 * page gutter on its own. Below 1000px section 7 sets `flex: 1 1 100%`
	 * on both columns and this stops applying.
	 *
	 * WHAT IT COSTS, and it was asked for with the reference visible: the
	 * rail's CONTENT goes 350 -> 558 at 1430, and 350 is the measure the
	 * title's line count, the variation selects and the justified body text
	 * were each tuned against -- re-measure them if any is re-pitched.
	 * Nothing clips at 558. It also grows without limit now that the page
	 * is uncapped: 779 of content at a 1900px client, against the
	 * reference's 648. Cap the RAIL if that is ever too much, not the page.
	 *
	 * THE FIXED-RAIL ARITHMETIC BELOW IS HISTORY and binds again the moment
	 * a length comes back here. ------------------------------------------
	/* 446, NOT 470 (operator, 2026-11-03). The 24 comes off the rail and
	   goes to the gallery, which takes its tiles from 363 to 375 against
	   the Yeti 2 reference's 388.
	 *
	 * WHY THE RAIL AND NOT THE PAGE GUTTER. The other 13 needed for 388
	 * is only available from the 77px gutter, and that number is derived
	 * rather than chosen: it is what puts the gallery's first tile at
	 * x=125, which is where the shop grid starts — measured on /shop/,
	 * grid left 125, width 1180. Taking it would make the page jog
	 * sideways every time a customer opens a product from the shop. The
	 * tile stops at 375 for that reason and the gap to the reference is
	 * deliberate: it has no shop grid to line up with, and a rail with no
	 * padding at all.
	 *
	 * WHAT THIS COSTS. The rail's content goes 374 -> 350, and 374 is the
	 * measure several decisions in this file were taken against — the
	 * product title's line count, the variation selects, the justified
	 * body text. Each was re-measured at 350 when this changed; see the
	 * note on the title. Re-check them if this number moves again. */
	--sp-rail: 50%;
}

/* THE LIGHT BAND.
 *
 * Both blocks are alignfull, so painting them covers the full width of
 * the page without touching <body>. The header and footer stay dark and
 * keep the carbon, which is deliberate: they are template parts shared
 * with every other page, and a navbar that changes colour on one page
 * reads as a fault rather than as a design.
 *
 * MARGINS BETWEEN THEM WOULD SHOW AS DARK STRIPES. .sf-pdp carries a
 * bottom margin and .sf-pdp__editorial a top one in section 5; both are
 * zeroed here and the same air is put back as PADDING, inside the white,
 * so the band is continuous. */
.sf-pdp,
.sf-pdp__editorial {
	/* TRANSPARENT, NOT var(--sp-bg), NOW THAT THE PALETTE IS CARBON AGAIN.
	 * Painting #171717 over the body is the exact mistake this file
	 * recorded on 2026-10-07: body carries the carbon WEAVE, a flat
	 * rectangle of the same colour sits on top of it, and the texture
	 * stops dead where the block begins — a seam across the page in a
	 * colour that matches perfectly. The band only has to paint itself
	 * when it differs from the page, which is what the light version was.
	 * --sp-bg still carries #171717 because the --wc-* tokens below read
	 * it, and those DO need a real colour. */
	background-color: transparent;
	color: var(--sp-text);

	/* ---- AND woocommerce.css's OWN TOKENS COME WITH US ----
	 *
	 * woocommerce.css skins every WooCommerce surface on the site from a
	 * --wc-* set declared on `.woocommerce, .woocommerce-page, body...`
	 * (its section 1), and those values are the dark theme. It loads
	 * BEFORE this file but that is not the point: its rules reference the
	 * variables, so whatever those resolve to at the element is what
	 * paints, and specificity never enters into it.
	 *
	 * Re-pointing them here, on the two blocks that make up this page,
	 * flips every WooCommerce control inside them in one go and leaves
	 * the cart, the account pages and the shop archive untouched.
	 *
	 * This is what the first attempt missed. Flipping only the --sp-*
	 * tokens left the variation <select> as a #131317 box with white text
	 * in the middle of a white column, the review rating select the same,
	 * and the active "Description" tab a dark chip — all three were
	 * --wc-panel, not anything this file had ever set. */
	--wc-bg:     var(--sp-bg);
	--wc-panel:  var(--sp-plate);
	--wc-text:   var(--sp-text);
	--wc-muted:  var(--sp-muted);
	--wc-faint:  var(--sp-faint);
	--wc-line:   var(--sp-line);
	--wc-accent: var(--sp-accent);
}

.sf-pdp.wp-block-columns {
	margin-bottom: 0;
	padding-bottom: var(--sp-step);
}

/* The editorial's own half-step top margin is section 5's, and on a dark
   page it was invisible air. On a light band it is a 24px black stripe
   across the full width, between the foot of the buy module and
   "Related products" — measured. Same air, moved inside the white.
 *
 * body.single-product, NOT a bare .sf-pdp__editorial: section 5 sets
 * padding-top: 0 and the margin at (0,1,0) and sits 1500 lines FURTHER
 * DOWN this file, so an equally specific rule here loses on order and
 * the stripe stays. (0,2,1) wins wherever it is written. */
body.single-product .sf-pdp__editorial {
	margin-top: 0;
	padding-top: calc(var(--sp-step) / 2);
/* 	padding-bottom: var(--sp-step); */
	padding-bottom: 50px;
}

.sf-pdp *,
.sf-pdp *::before,
.sf-pdp *::after,
.sf-pdp__editorial *,
.sf-pdp__editorial *::before,
.sf-pdp__editorial *::after {
	box-sizing: border-box;
}


/* -------------------------------------------------------------
 * 1. THE SPLIT
 * ------------------------------------------------------------- */
.sf-pdp.wp-block-columns {
	gap: 0;
	margin-top: 0;
	align-items: flex-start;

	/* !important IS REQUIRED, and only here. Core ships
	   `@media (min-width: 782px){ .wp-block-columns { flex-wrap: nowrap !important } }`
	   so a plain `flex-wrap: wrap` loses no matter how specific the
	   selector is - measured: computed flex-wrap stayed `nowrap`, the
	   editorial stack never wrapped to its own row, and it sat in the first
	   row squeezing the gallery down to 96px wide. */
	flex-wrap: wrap !important;

	/* THE PAGE AGREES WITH EVERY OTHER PAGE NOW (operator, 2026-10-06:
	   "it looks too empty").
	 *
	 * It used to be a true full-bleed 1430px band. The shop grid, and every
	 * information page, sets 1180 of content starting at x=125 on a 1440
	 * screen. This page started its text at x=24 and ran to 1406, so it was
	 * 250px wider than anything a customer sees before or after it - and
	 * the extra width had nothing to fill it. The rail holds 317px of
	 * content (a title, a price, a button, a category and one line of
	 * description) and the picture is capped at 620 because the source
	 * files are only 420 wide. Measured at 1440: 583px of empty rail and
	 * 170px of dead space either side of the photograph.
	 *
	 * DONE WITH PADDING, NOT max-width AND AUTO MARGINS. The obvious
	 * version - `max-width: calc(...); margin-inline: auto` - was written
	 * first and it breaks the block: this is an `alignfull` block, and
	 * alignfull escapes its constrained parent with NEGATIVE margins, which
	 * auto margins overwrite. Measured: the band stopped escaping, came out
	 * 1222 wide at x=104 instead of 1430 at 0, and on a phone it collapsed
	 * to 315 of a 375 screen - which took the rail's content to 267 and
	 * wrapped the wishlist heart onto a line of its own under Add to cart.
	 *
	 * Padding leaves the margins alone, and max() makes the same single
	 * declaration self-cancelling on a narrow screen.
	 *
	 * THE `+ root-padding * 2` IS NOT OPTIONAL. A percentage padding
	 * resolves against the CONTAINING BLOCK, which here is the constrained
	 * parent at 1222 - not the 1430 the block actually paints, which it
	 * reaches by escaping with margin-inline: -104px. Without the term the
	 * arithmetic came out (1222 - 1276) / 2, went negative, and max()
	 * clamped it to zero: the declaration silently did nothing at all and
	 * measured identical to no rule. Adding back the two 104px escapes
	 * reconstructs the painted width.
	 *
	 * At 1440: (1222 + 208 - 1276) / 2 = 77 a side, which puts the rail's
	 * content at x=125 - the shop grid's own left edge, so a customer
	 * moving from the shop to a product sees the page stay still. Below
	 * about 1276 the subtraction goes negative, max() clamps to 0, and the
	 * block is full-bleed again with the rail keeping its measure through
	 * its own 668px cap. No media query needed. */
	box-sizing: border-box;
	/* FULL BLEED ON --sf-gutter SINCE 2026-11-17 (operator: "Match it too"),
	 * so this page sits on the same edge as every other one. Measured at a
	 * 1770px client: 74.76px, against the home page section 2 at 74.75.
	 *
	 * IT WAS A PERCENTAGE SUM reconstructing the alignfull escape --
	 * max(0px, (100% + root-padding * 2 - (--sp-measure + --sp-step * 2)) / 2)
	 * -- which centred 1300 of content inside two 48px steps and measured
	 * 187px a side here. Everything the long note above says about WHY that
	 * sum was shaped the way it was still holds, and it is kept because it is
	 * the only record of it; it simply has no cap left to centre.
	 *
	 * A FLAT LENGTH NEEDS NONE OF THAT ARITHMETIC. The block still escapes
	 * with margin-inline, so its border box starts at the painted left edge
	 * and the padding IS the inset -- no containing-block percentage, no
	 * escape to add back, nothing to clamp with max().
	 *
	 * --sp-step IS DELIBERATELY STILL 48px AND IS NOT THIS. It is the rail
	 * internal padding and the vertical rhythm (see .sf-pdp__rail below and
	 * the section spacing above); pointing it at --sf-gutter would take the
	 * rail own padding to 75 on a wide screen, which is a different change
	 * nobody asked for. */
	padding-left: var(--sf-gutter);
	padding-right: var(--sf-gutter);
}

/* border-box so the 470 is the WHOLE rail including its 48px
   padding, leaving 374 of content — the concept's width, and the
   same slot the category filter rail uses. Left as content-box a
   wp-block-column comes out 566. */
.sf-pdp__rail,
.sf-pdp__presentation {
	box-sizing: border-box;
}

.sf-pdp__rail {
	position: sticky;
	top: var(--sp-step);
	padding: var(--sp-step);
	/* NO max-height / overflow HERE, deliberately (operator, 2026-11-02).
	 *
	 * This was `max-height: 100vh; overflow-y: auto` with the scrollbar
	 * hidden — a visible one takes 10px out of the 374 the rail is built
	 * on. It was there so a rail taller than the screen could not put Add
	 * to cart out of reach on a short laptop.
	 *
	 * BOTH HALVES OF THAT STOPPED HOLDING once the accordion cards were
	 * added below the buy block:
	 *
	 *   - The cap SLICED them. Measured at 1440x900: rail content 1171px
	 *     against a 900px box, so the Description card was cut clean in
	 *     half at the viewport edge and Product details never appeared —
	 *     and with the scrollbar hidden there was nothing to say why. It
	 *     read as a broken card, not as a scroll.
	 *   - The sticky it was protecting barely travels any more. The
	 *     editorial stack was moved out of the columns (see the note
	 *     further down), so the containing block is now one row — 1217px
	 *     against a 1169px rail, about 48px of travel. Add to cart sits
	 *     ~330px down and is on the first screen regardless.
	 *
	 * Uncapped, the rail takes its natural height and scrolls with the
	 * page, which is what section 7 already does below 1000px. Measure the
	 * rail against the viewport before capping this again. */
}

/* THE PRESENTATION COLUMN IS DISSOLVED AT EVERY WIDTH.
 *
 * It was a wrapper holding the gallery and the editorial stack, which
 * forced the related products to live inside the right-hand column: they
 * rendered 864px wide starting at x=518, while the SAME cards on the shop
 * are 1180 wide starting at x=125. Four cards at 864 are 198 each against
 * the archive's 282 - the card was being shown at two different sizes on
 * two pages, which is the thing this whole section exists to prevent.
 *
 * `display: contents` lifts the gallery and the editorial stack up to be
 * flex items of .sf-pdp itself, so each can be sized on its own: the
 * gallery takes the rest of the first row beside the rail, and the
 * editorial is given a 100% basis, wraps to a row of its own and spans
 * the full measure. Nothing in the markup moves.
 *
 * The column carries no background and no padding of its own, so there is
 * nothing to lose by dissolving it. */
.sf-pdp__presentation {
	display: contents;
}

/* the rail is a fixed slot; the gallery takes what is left of the row.
 *
 * READS THE TOKEN NOW. --sp-rail has been declared since this file was
 * written and nothing consumed it — the width was hardcoded here, so the
 * two could disagree without anything saying so. One number.
 *
 * BUT THIS DECLARATION DOES NOT DECIDE THE WIDTH, AND NEVER DID.
 * templates/single-product.html writes the column as
 *     <div class="wp-block-column sf-pdp__rail" style="flex-basis:470px">
 * because that is how wp:column stores a width, and an inline style beats
 * every rule in this file. Found the hard way on 2026-11-03: --sp-rail was
 * changed to 446, the token computed 446 on the element, and the rail went
 * on rendering 470 with no rule anywhere supplying that number.
 *
 * So the real width lives in the template and this is the fallback. Change
 * them together — the template's TWO occurrences (the block comment's
 * `"width"` and the div's inline `flex-basis`) and --sp-rail. !important
 * would work here too and is deliberately not used: it would leave the
 * template quietly disagreeing with the stylesheet. */
.sf-pdp__rail {
	flex: 0 0 var(--sp-rail);
}

.sf-pdp__gallery {
	flex: 1 1 0;
	min-width: 0;
}

/* ---- THE SIDES ARE SWAPPED BACK (operator, 2026-10-22) ----------------
 *
 * Gallery LEFT, buy rail RIGHT — the arrangement every large storefront
 * uses, and the one the operator pointed at (logitechg.com product page).
 *
 * THIS REVERSES A DELIBERATE EARLIER DECISION, so the reasoning that put
 * the rail on the left is worth keeping rather than deleting: the rail
 * occupied the same 470px slot the category page's filter rail does, so
 * moving from a category to a product did not move the page furniture.
 * That is a real benefit and it is being given up. What buys it back is
 * that a customer arrives at a product far more often from search, a link
 * or the home page than from the filtered category view, and in all of
 * those the picture leading is what they expect.
 *
 * DONE WITH `order`, NOT BY MOVING THE BLOCKS IN THE TEMPLATE.
 * templates/single-product.html keeps the rail first, which is the right
 * DOM order: on a phone the whole row stacks and the title, price and Add
 * to cart should not sit below a screenful of photographs — and it is also
 * the reading order a screen reader gets. Reversing it here changes only
 * what is painted. Reverting is these two declarations.
 *
 * Section 7 sets `order: -1` on the gallery below 1000px. That still wins
 * (later in the file, same specificity) and says the same thing, so the
 * stacked order is unchanged. */
.sf-pdp__gallery {
	order: 1;
}

.sf-pdp__rail {
	order: 2;
}

/* THE EDITORIAL STACK IS NO LONGER INSIDE THE COLUMNS AT ALL - it is a
 * sibling alignfull block, moved there in templates/single-product.html
 * because the sticky rail was painting over RELATED PRODUCTS. A sticky
 * element is bounded by its containing block, so while the editorial was
 * inside the columns the rail kept sticking all the way down past its own
 * row. See the note in the template.
 *
 * It therefore needs the measure itself, by the same arithmetic .sf-pdp
 * uses - 1180 of content plus the gutters, self-cancelling below that. */
/* The tokens, including --sp-step, now reach this block through the shared
   declaration at the top of the file. Its MEASURE is set in section 5,
   where this block's padding already lived - two padding rules on one
   selector and the later one simply wins, which is how the first attempt
   at it silently came out at 48px instead of 125. */
.sf-pdp__editorial {
	box-sizing: border-box;
}


/* -------------------------------------------------------------
 * 2. THE RAIL
 * ------------------------------------------------------------- */

/* ---- the rating line above the title ---- */
.sf-pdp__rail .wc-block-components-product-rating {
	margin: 0 0 16px;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	line-height: 12px;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--sp-muted);
}

/* STARS AND LINK, SPACED AND IN BRAND (operator, 2026-10-06: "not have a
   space between star and [1 CUSTOMER REVIEW] and the star not pink").
 *
 * WooCommerce lays this out as an inline-block of stars followed by an
 * inline <span> with nothing between them but the whitespace in the markup
 * - measured 3px, which is why the two ran together. A flex container with
 * an explicit gap replaces that, and `flex-wrap` means a long count label
 * drops to its own line on a narrow rail instead of being squeezed.
 *
 * The stars were grey because the block inherits `color` from the rating
 * line, which is --sp-muted. WooCommerce draws the empty stars from the
 * element and the filled ones from the inner span, both in currentColor,
 * so one declaration colours the pair correctly - the same thing that
 * fixed the stars in the reviews tab. 13px matches them to it. */
.sf-pdp__rail .wc-block-components-product-rating__container {
	display: flex;
	align-items: center;
	flex-wrap: wrap;
	gap: 4px 10px;
}

.sf-pdp__rail .wc-block-components-product-rating__stars {
	font-size: 13px;
	color: var(--sp-accent);
}

.sf-pdp__rail .wc-block-components-product-rating__reviews_count {
	margin: 0;
}

/* ---- the title: 60 / 54 ---- */
.sf-pdp__rail h1.wp-block-post-title {
	margin: 0;
	font-family: var(--sp-title);
	/* The reference sets 60/54, but its product names are short. Ours are
	   "Superfly Project X 4 Spoke Sport Rims (Gold)" — 44 characters, which
	   at 60px ran SIX lines and 324px down a 374px rail. Sized to read
	   rather than to shout. Put 60/54 back the day product names get
	   shorter.
	 *
	 * 28, NOT 30, SINCE THE RAIL WENT TO 350 (2026-11-03). The narrowing
	 * that took the gallery's tiles to 375 cost 24px of rail, and at 30px
	 * that was enough to stop "ADJUSTABLE" and "SUSPENSION" fitting a
	 * line each: product 889's title went from THREE lines to FIVE, 96px
	 * to 160, and pushed Add to cart 64px down the column. Measured at
	 * 350: 30px = 5 lines, 28px = 3, and so do 27, 26 and 24 — so 28 is
	 * the largest size that holds the old line count, not an arbitrary
	 * step down. Back to 30 if --sp-rail ever returns to 470. */
	font-size: 28px;
	font-weight: 400;
	line-height: 32px;
	letter-spacing: -0.01em;
	text-transform: uppercase;
	color: var(--sp-text);
}

/* ---- price: the reference's 16px mono ----
 * woocommerce.css sets clamp(22px, 2.4vw, 32px) at
 *   body.single-product .wp-block-woocommerce-product-price .wc-block-components-product-price
 * which is (0,3,1). Adding .sf-pdp__rail makes this (0,4,1), so it wins
 * on specificity alone — no !important needed. */
body.single-product .sf-pdp__rail .wp-block-woocommerce-product-price .wc-block-components-product-price,
body.single-product .sf-pdp__rail .wc-block-components-product-price {
	display: block;
	margin: 16px 0 0;
	font-family: var(--sp-tech);
	font-size: 16px;
	font-weight: 500;
	line-height: 18.4px;
	letter-spacing: 0.64px;
	color: var(--sp-accent);
}

.sf-pdp__rail .wc-block-components-product-price del {
	color: var(--sp-faint);
}

.sf-pdp__rail .wc-block-components-product-price ins {
	text-decoration: none;
}

/* -------------------------------------------------------------
 * 3. THE CONTROLS
 *
 * assets/css/shop-beast.css is DEQUEUED on product pages — see
 * superfly_single_product_drop_beast() in functions.php — so this
 * file owns every control in the form and there is no specificity
 * war. Everywhere else on the site the Beast styles are untouched.
 *
 * shop-beast.JS still runs, and it is why the form looks like this:
 * it rewrites WooCommerce's variation <select> into
 *
 *   .sb-label   "Select model"
 *   .sb-rows    the stack
 *     .sb-row   <button><span>EGO 18T 1.6x14</span><b>RM448.00</b></button>
 *               states: .is-on (chosen), .is-out (no stock)
 *   .sb-hidden  the real <select>, visually hidden but still in the
 *               form, so WooCommerce receives exactly what it expects
 *
 * Those class names belong to that script. If it is ever removed the
 * rows go and WooCommerce's dropdown returns — the <select> rules
 * further down still cover that case.
 * ------------------------------------------------------------- */
.sf-pdp__rail .wp-block-add-to-cart-form,
.sf-pdp__rail form.cart {
	width: 100%;
	margin: 24px 0 0;
}

/* ---- the fitment rows ---- */
.sf-pdp__rail .sb-label {
	margin: 0 0 12px;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	line-height: 12px;
	letter-spacing: 1px;
	text-transform: uppercase;
	color: var(--sp-muted);
}

.sf-pdp__rail .sb-rows {
	display: grid;
	gap: 8px;
	margin: 0 0 24px;
}

/* NEUMORPHIC PLATES, NO BORDERS (operator, 2026-10-06: "in product page i
   want neuphormics themes and border shadow, no need at border").

   Every one of these was a 1px line on a transparent background. They are
   now raised surfaces: a #16161a face - the same plate colour the sort
   control, the pagination and the card buttons use - lifted off the page
   by a light highlight top-left and a dark shadow bottom-right.

   THE SELECTED ROW IS PRESSED IN, NOT OUTLINED. Without a border the
   chosen model still has to be unmistakable, so it inverts the lighting:
   the shadows go inset, which reads as a key pushed down, and it carries a
   magenta tint and magenta type. That is the neumorphic idiom for "on",
   and it needs no line at all. */
.sf-pdp__rail .sb-row {
	display: grid;
	grid-template-columns: minmax(0, 1fr) auto;
	align-items: center;
	gap: 12px;
	width: 100%;
	padding: 14px 16px;
	border: 0;
	border-radius: 6px;
	background: var(--sp-plate);
	box-shadow: var(--sp-plate-shadow);
	color: var(--sp-text);
	font-family: var(--sp-body);
	font-size: 14px;
	line-height: 18.48px;
	letter-spacing: 0.24px;
	text-align: left;
	cursor: pointer;
	transition: box-shadow 0.2s ease, background-color 0.2s ease,
	            color 0.2s ease;
}

.sf-pdp__rail .sb-row:hover {
	background: #1b1b20;
	box-shadow: -3px -3px 8px rgba(255, 255, 255, 0.03),
	             4px 4px 10px rgba(0, 0, 0, 0.5);
}

.sf-pdp__rail .sb-row.is-on {
	background: rgba(236, 30, 121, 0.10);
	box-shadow: inset 3px 3px 7px rgba(0, 0, 0, 0.5),
	            inset -2px -2px 5px rgba(255, 255, 255, 0.03);
	color: var(--sp-accent);
}

.sf-pdp__rail .sb-row:focus-visible {
	outline: 2px solid var(--sp-accent);
	outline-offset: 2px;
}

/* the price on each row — the whole reason these rows exist */
.sf-pdp__rail .sb-row b {
	font-family: var(--sp-tech);
	font-size: 14px;
	font-weight: 500;
	letter-spacing: 0.56px;
	color: var(--sp-accent);
}

.sf-pdp__rail .sb-row.is-out {
	opacity: 0.45;
	cursor: not-allowed;
}

.sf-pdp__rail .sb-row.is-out b {
	color: var(--sp-faint);
}

/* the real <select>: hidden from sight, still in the form */
.sf-pdp__rail .sb-hidden {
	position: absolute;
	width: 1px;
	height: 1px;
	margin: -1px;
	padding: 0;
	overflow: hidden;
	clip: rect(0 0 0 0);
	clip-path: inset(50%);
	white-space: nowrap;
}

/* ---- the dropdown, for when the rows are not there ----
 * A product whose variations the script cannot read, or the script
 * removed entirely, falls back to WooCommerce's own <select>.
 *
 * (0,6,3), AND IT NEEDS IT FOR THE `border` ALONE. woocommerce.css
 * carries
 *     .woocommerce div.product form.cart .variations
 * at (0,4,2) with `border-top: 1px solid var(--wc-line)` — the house
 * rule above a variations table everywhere on the site. Written as
 * plain `.sf-pdp__rail table.variations:not(.sb-hidden)` this was
 * (0,3,1) and lost, so the `border: 0` below never took: the page
 * drew that hairline AND the deliberate one under the price (section
 * 3b), 32px apart, reading as a double rule above "Fits" (operator,
 * 2026-11-02: "why have 2 lines?").
 *
 * The price divider is the one that stays — it is the reference's,
 * and it closes "what it is" before "what you are choosing" begins.
 * This table sits inside that second group and needs no lid of its
 * own. Everything else here applied all along; only the border was
 * being overruled. */
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) {
	width: 100%;
	/* NO BOTTOM MARGIN. The last cell's own 16px padding already closes
	   the group, and form.cart is a flex row with an 8px gap, so a margin
	   here was a third helping: 16 (cell) + 16 (margin) + 8 (gap) = 40px
	   of nothing between the last dropdown and the stock line, against 16
	   between one attribute and the next. Measured. */
	margin: 0;
	border: 0;
	border-collapse: collapse;
}

/* THE tbody AND THE tr HAVE TO GO BLOCK AS WELL, not just the cells.
   Left as `display: table-row` the row still generates an anonymous table
   box around the block-level cells, and a `width: 100%` cell resolves
   against THAT box's shrink-to-fit width rather than the form's. Measured
   on a 375px screen: form 327 wide, table 327 wide, and every <select>
   244 — the width of the longest option label. It reads as a dropdown
   that refuses to fill its column and there is nothing wrong with the
   select at all. Same on desktop, 130px short in a 374px rail. */
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) tbody,
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) tr,
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) th,
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) td {
	display: block;
	width: 100%;
	padding: 0;
	border: 0;
	text-align: left;
}

/* (0,6,4), AND THE `padding` IS WHY. woocommerce.css carries
 *     .woocommerce div.product form.cart .variations th,
 *     .woocommerce div.product form.cart .variations td
 * at (0,4,2) with `padding: 14px 0` — the house spacing for a variations
 * table drawn as a real table, where the cells need their own air. This
 * rule was (0,3,2) and lost it, so every cell kept 14px top and bottom
 * on top of the layout below: 14 under the label, 10 from the head row's
 * own margin, 14 over the control. 38px between FITS and its dropdown,
 * where the design says 10 (operator, 2026-11-02: "why too many space on
 * the top of that option?").
 *
 * It only showed once the label became an 11px eyebrow — as an 18px
 * heading the same gap read as heading spacing rather than as a fault.
 *
 * The spacing between one attribute and the next lives on the cell, not
 * on every block above it, which is what the second rule is for. */
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) td {
	padding-bottom: 16px;
}

.sf-pdp__rail table.variations th label {
	display: block;
	margin: 0 0 8px;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	letter-spacing: 1px;
	text-transform: uppercase;
	color: var(--sp-muted);
}

.sf-pdp__rail select {
	width: 100%;
	height: 44px;
	padding: 0 40px 0 14px;
	border: 1px solid var(--sp-line);
	border-radius: var(--sp-radius);
	background-color: transparent;
	color: var(--sp-text);
	font-family: var(--sp-tech);
	font-size: 11px;
	font-weight: 500;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	appearance: none;
	-webkit-appearance: none;
	cursor: pointer;
	background-image:
		linear-gradient(45deg, transparent 50%, var(--sp-muted) 50%),
		linear-gradient(135deg, var(--sp-muted) 50%, transparent 50%);
	background-position: calc(100% - 20px) 20px, calc(100% - 15px) 20px;
	background-size: 5px 5px, 5px 5px;
	background-repeat: no-repeat;
}

.sf-pdp__rail select option {
	background: #111114;
	color: #ffffff;
	font-weight: 500;
}

/* WooCommerce's own reset link, HIDDEN (operator, 2026-11-02).
 *
 * It clears every attribute at once, so it belongs to no single control
 * and WooCommerce has nowhere to put it but the foot of the form — a bare
 * underlined CLEAR under the last dropdown, with nothing around it to say
 * whether it resets Size or both. Section 3b replaces it with a per-
 * attribute reset on each label line, where the scope is the row it sits
 * in. See "the attribute head row" there.
 *
 * `display`, not `visibility`: WooCommerce toggles this link by writing
 * `visibility` inline as choices are made, and an inline style would beat
 * a `visibility: hidden` here. It leaves `display` alone.
 *
 * STILL IN THE FORM, not removed, so nothing in variation-form.js is
 * reaching for an element that is not there.
 *
 * (0,5,3), AND IT NEEDS IT. This was a plain `.sf-pdp__rail
 * .reset_variations` at (0,2,0), which looked fine locally and lost on
 * the real site: WOOCOMMERCE'S OWN STYLESHEET carries
 *     .woocommerce div.product form.cart .reset_variations
 * at (0,4,2) with a `display` on it, and that is a plugin file, not one
 * of ours — docs/concepts/pdp-picker-harness.html loads the theme's CSS
 * but not WooCommerce's, so the harness showed the link hidden while the
 * live page still printed CLEAR under the last dropdown (operator,
 * 2026-11-02). Our own woocommerce.css has the identical selector a few
 * lines apart; that is the one to measure against when touching this. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .reset_variations,
body.single-product .sf-pdp .sf-pdp__rail .reset_variations {
	display: none;
}

/* WooCommerce's own single-variation price, kept hidden: the chosen
   price is already in the 32px headline above, written there by
   shop-beast.js from the same variation data. A second copy under the
   dropdowns is noise.
   (It was hidden for the fitment rows originally, which printed a price
   on every row. The rows went on 2026-10-22; this stays.) */
.sf-pdp__rail .woocommerce-variation-price {
	display: none;
}

.sf-pdp__rail .woocommerce-variation-availability p {
	margin: 0 0 12px;
	font-size: 13px;
	line-height: 18.48px;
	color: var(--sp-muted);
}

/* ---- the purchase row ----
 * The reference puts [qty][Add to cart] on one line, the button
 * 176x56 in 10px mono at 1px tracking. */
.sf-pdp__rail form.cart,
.sf-pdp__rail .woocommerce-variation-add-to-cart {
	display: flex;
	flex-wrap: wrap;
	align-items: stretch;
	gap: 8px;
}

/* everything that is not the qty box or the button spans the row.
 *
 * .single_variation_wrap IS THE ONE THAT MATTERS, and it was missing until
 * 2026-11-02. On a VARIABLE product WooCommerce does not hand form.cart the
 * variation block and the purchase row as two children — it wraps both in
 * .single_variation_wrap:
 *
 *     form.cart
 *       table.variations
 *       div.single_variation_wrap
 *         div.woocommerce-variation.single_variation   (price, stock)
 *         div.woocommerce-variation-add-to-cart        (qty, button, heart)
 *
 * so the two selectors below that name those inner divs as CHILDREN of
 * form.cart match nothing at all there. Left without a rule, the wrap is a
 * flex item at `flex: 0 1 auto` and shrink-to-fits its widest line — the
 * purchase row — which is why ADD TO CART stopped at about 290px of a 470px
 * rail instead of growing into it, and why the stock line above it read as
 * centred over the BUTTONS rather than over the column (operator,
 * 2026-11-02: "should be the add to cart is full width").
 *
 * The button itself was always `flex: 1 1 120px` and always willing to
 * grow; it had nothing to grow into. Nothing in the purchase row rules
 * further down needed changing.
 *
 * The inner two stay listed: a SIMPLE product has no wrap, and the swatches
 * plugin flattens this on some templates. Both shapes are covered. */
.sf-pdp__rail form.cart > .sb-label,
.sf-pdp__rail form.cart > .sb-rows,
.sf-pdp__rail form.cart > table.variations,
.sf-pdp__rail form.cart > .single_variation_wrap,
.sf-pdp__rail form.cart > .woocommerce-variation-add-to-cart,
.sf-pdp__rail form.cart > .woocommerce-variation,
.sf-pdp__rail form.cart > .reset_variations {
	flex: 1 0 100%;
	margin-left: 0;
	margin-right: 0;
}

/* ONE ROW: [qty] [Add to cart] [heart]  (operator, 2026-10-06).
   This previously forced the ShopEngine badges onto a SECOND full-width
   row, which was deterministic but looked like it: a loose heart and a
   loose compare arrow floating under the button with a gap above them.
   Measured at 417px — heart and compare on their own line at top 68.

   Compare and quick-view are hidden, as they are on the archive; the
   operator asked for those to go. The heart stays and becomes a 56px
   square that sits in the row, matching the quantity box and the button
   either side of it. */
.sf-pdp__rail form.cart > .shopengine-comparison,
.sf-pdp__rail form.cart > .shopengine_comparison_add_to_list_action,
.sf-pdp__rail form.cart > .shopengine-quickview-trigger,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-comparison,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine_comparison_add_to_list_action,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-quickview-trigger {
	display: none;
}

.sf-pdp__rail form.cart > .shopengine-wishlist,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist {
	order: 3;
	flex: 0 0 56px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 56px;
	height: 56px;
	margin: 0;
	/* a plate, like the quantity box and the model rows - no line */
	border: 0;
	border-radius: 6px;
	background: var(--sp-plate);
	box-shadow: var(--sp-plate-shadow);
	color: var(--sp-muted);
	font-family: var(--sp-tech);
	font-size: 15px;
	transition: box-shadow 0.2s ease, color 0.2s ease, background-color 0.2s ease;
}

/* `body.single-product .sf-pdp` IS LOAD-BEARING ON BOTH OF THESE.
   Without it they are (0,4,1), and the circle rule further down the file
   — "the heart becomes a circle beside the pill", (0,5,1) — sets
   `background: transparent; box-shadow: none` and wins on specificity
   AND on order. Measured 2026-11-02: adding .active to the live button
   left the background at rgba(0,0,0,0). Hover was dead the same way. */
body.single-product .sf-pdp .sf-pdp__rail form.cart > .shopengine-wishlist:hover,
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist:hover {
	background: var(--sp-accent);
	color: #fff;
	/* the circle rule gives it a 2px --sp-line ring; left alone that stays
	   grey on magenta and reads as an outline rather than a filled button */
	border-color: var(--sp-accent);
	box-shadow: 0 4px 16px rgba(236, 30, 121, 0.42);
}

/* SAVED: filled magenta with a white heart (operator, 2026-10-06).
   ShopEngine adds `.active` when the product is in the wishlist, and
   nothing here was listening for it — a saved product looked exactly like
   an unsaved one, so there was no way to tell from the page whether you had
   already added it. The archive card has had this state for a while; the
   product page had not. */
body.single-product .sf-pdp .sf-pdp__rail form.cart > .shopengine-wishlist.active,
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist.active {
	background: var(--sp-accent);
	color: #fff;
	border-color: var(--sp-accent);
	box-shadow: 0 4px 16px rgba(236, 30, 121, 0.42);
}

/* the glyph is an icon font, so it paints in `color` — and ShopEngine's own
   `.badge.active { color: #f03d3f }` is waiting to claim it otherwise */
.sf-pdp__rail form.cart > .shopengine-wishlist.active i,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist.active i,
.sf-pdp__rail form.cart > .shopengine-wishlist:hover i,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist:hover i {
	color: #fff;
}

/* the heart's own icon colour follows the link, so it goes white on hover
   instead of staying magenta on magenta — the same trap the archive card
   had. */
.sf-pdp__rail form.cart > .shopengine-wishlist i,
.sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist i {
	color: inherit;
}

/* THE HIDDEN VARIATIONS TABLE WAS PUSHING THE PAGE SIDEWAYS.
   The swatches plugin replaces WooCommerce's <table class="variations"> with
   its own rows and marks the original `.sb-hidden` — but it was still being
   laid out, 758px wide inside a 744px column, so the document scrolled 14px
   horizontally at 768. Measured: document 782 against a 768 viewport, and
   the table was the only element over by exactly that much.

   Taken out of layout rather than just constrained: it is already redundant
   once the swatch rows are drawn, and it stays in the DOM for the plugin's
   own JavaScript either way. The max-width is a belt for the case where the
   plugin is not active and the table IS the control. */
.sf-pdp__rail form.cart table.variations.sb-hidden {
	display: none;
}

.sf-pdp__rail form.cart table.variations {
	max-width: 100%;
}

.sf-pdp__rail .quantity {
	order: 1;
	display: inline-flex;
	align-items: stretch;
	flex: none;
	height: 56px;
	margin: 0;
	/* a plate, like the model rows above it - see the note there */
	border: 0;
	border-radius: 6px;
	background: var(--sp-plate);
	box-shadow: var(--sp-plate-shadow);
}

/* THE DOUBLE BORDER (operator, 2026-10-06: "why is it double").
   The wrapper .quantity carries the frame — 56px tall, 2px radius, matching
   the button beside it. The INPUT inside was drawing a second one, so the
   control read as a box inside a box.

   It was not that the rule below was missing; it was losing. Our own
   woocommerce.css styles the quantity field as a panel in its own right:
       .woocommerce div.product form.cart .quantity .qty
           { border: 1px solid var(--wc-line); background: var(--wc-panel); }
   That is (0,5,2) and correct everywhere else — on the cart page the field
   has no wrapper frame around it. A plain `.sf-pdp__rail .quantity input.qty`
   is only (0,3,1), so it never stood a chance. The selector below is
   (0,6,3), the same approach the add-to-cart button underneath already
   uses. Specificity, not !important. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .quantity input.qty,
.sf-pdp__rail .quantity input.qty {
	width: 78px;
	height: 100%;
	padding: 0;
	border: 0;
	background: transparent;
	text-align: center;
	color: var(--sp-text);
	font-family: var(--sp-tech);
	font-size: 13px;
	font-weight: 500;
	letter-spacing: 0.06em;
	-moz-appearance: textfield;
}

.sf-pdp__rail .quantity input.qty::-webkit-outer-spin-button,
.sf-pdp__rail .quantity input.qty::-webkit-inner-spin-button {
	-webkit-appearance: none;
	margin: 0;
}

/* (0,5,3), to beat woocommerce.css's `.woocommerce div.product form.cart .button`
   at (0,4,2). Specificity, not !important. */
body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button,
body.single-product .sf-pdp .sf-pdp__rail form.cart .single_add_to_cart_button {
	order: 2;
	/* 176px is the reference's width and still the target, but it GIVES now.
	   `flex: 0 0 176px` could not shrink, so once the heart joined the row
	   the three items could not fit a narrow rail and the heart wrapped to a
	   line of its own. `1 1 176px` keeps 176 as the basis, lets it grow into
	   spare space and shrink when there is none, so the row survives down to
	   a phone. The 120px floor stops the label wrapping inside the button. */
	/* THE BASIS IS 120, NOT 176, and that distinction is the whole fix.
	   flex-wrap decides using the BASIS, before shrink ever runs: at a
	   basis of 176 the row needed 87 + 176 + 56 + 16 = 335 inside a 327px
	   rail, so the heart wrapped to a second line and the button then grew
	   to fill the first — measured, twice. At 120 the three fit (279), stay
	   on one line, and grow spreads the spare width into the button, which
	   lands near the reference's 176 on a desktop rail anyway. */
	flex: 1 1 120px;
	min-width: 120px;
	width: auto;
	max-width: 100%;
	height: 56px;
	padding: 0 24px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid var(--sp-accent);
	border-radius: var(--sp-radius);
	background: var(--sp-accent);
	/* THE TOKEN, NOT A LITERAL. Section 3b restates this declaration with
	   var(--sp-accent-fg), so a hardcoded black here meant the one value
	   had to be changed in two places, and whichever was missed would
	   show up only at whichever width the other rule lost. */
	color: var(--sp-accent-fg);
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	line-height: 12px;
	letter-spacing: 1px;
	text-transform: uppercase;
	cursor: pointer;
	transition: background-color 0.2s ease, border-color 0.2s ease;
}

body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button:hover {
	background: #ff3d92;
	border-color: #ff3d92;
}

body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button.disabled,
body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button:disabled {
	background: transparent;
	border-color: var(--sp-line);
	color: var(--sp-muted);
	cursor: not-allowed;
}

/* ---- NOTHING PICKED YET ----
   (operator, 2026-11-03: "i want like color add to cart button when hover,
   no more transparent".)

   The rule above greys the button for EVERY disabled state, and against
   the carbon a transparent plate with a --sp-line border all but
   disappears. This state gets the HOVER fill instead — the full pill, no
   transparency — so the control the rider has to come back to is the
   loudest thing in the buy box.

   wc-variation-selection-needed is WooCommerce's own class for exactly
   one of those states — "choose your options first". The other disabled
   states (wc-variation-is-unavailable, out of stock) keep the grey above,
   because there grey is the honest answer: nothing the rider picks will
   make the button work.

   TWO THINGS THIS COSTS, both known and both the operator's call:
   it looks exactly like a live button while it is not one, so the
   cursor stays not-allowed as the only signal; and white on the hover
   tint measures 3.63:1, under AA — the same trade the pill itself makes
   at 4.18:1 (see the --sp-accent-fg note at the top). */
body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button.disabled.wc-variation-selection-needed,
body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button.disabled.wc-variation-selection-needed:hover {
	background: color-mix(in srgb, var(--sp-accent) 85%, white);
	border-color: color-mix(in srgb, var(--sp-accent) 85%, white);
	color: var(--sp-accent-fg);
	cursor: not-allowed;

	/* woocommerce.css fades every .button.disabled to .5, which turned the
	   full pill into the washed-out one this state was meant to replace —
	   measured on the live page, opacity .5 over the carbon. */
	opacity: 1;
}

/* ---- meta: SKU, category, tags ---- */
/* TIGHTENED (operator, 2026-10-06: "why too many space"). It was
   24 above the rule and 18 below it, so a single 18px line of grey text
   carried 42px of approach - and the excerpt beneath repeated it with
   24 + 20. Measured on the brake rotor: 124px of empty rail wrapped
   around two single lines of text.

   18/14 keeps the rule clearly separated from the Add to cart row above
   while sitting closer to the line it introduces, which is the right
   relationship anyway: a rule belongs to the block it heads, not to the
   one it leaves behind. */
.sf-pdp__rail .wp-block-woocommerce-product-meta {
	margin: 18px 0 0;
	padding: 14px 0 0;
	border-top: 1px solid var(--sp-hair);
}

/* ONE TAXONOMY PER LINE (operator, 2026-11-02: "why like this? should
 * be its will new line").
 *
 * WooCommerce's product-meta block does NOT hand over three equal rows.
 * It wraps Category and Tags in a `wp-block-group is-layout-flex` and
 * leaves Brands outside it, as a sibling:
 *
 *     .wp-block-woocommerce-product-meta
 *       .wp-block-group.is-layout-flex      <- flex ROW
 *         .taxonomy-product_cat
 *         .taxonomy-product_tag
 *       .taxonomy-product_brand             <- on its own
 *
 * So two of them shared a line and the third did not, which reads as a
 * wrap gone wrong rather than as a layout. This rule unwinds the group;
 * `display` beats core's `.is-layout-flex` (0,1,0) easily at (0,3,0).
 * The `gap` it replaces was there to space them when they wrapped. */
.sf-pdp__rail .wp-block-woocommerce-product-meta .wp-block-group {
	display: block;
}

/* label | value, so the three values line up down the card instead of
   starting wherever their prefix happens to end.
 *
 * A HANGING INDENT, NOT FLEX OR GRID. Both of those make every inline
 * child of the row a box of its own — and WooCommerce prints the tag
 * list as `<a>, <span>, <a>`, so the separator became a flex item and
 * the comma drifted into the middle of a gap: "LC135 5S , Y15ZR".
 * Measured. Indenting the row and pulling the prefix back into the
 * gutter leaves the links and their commas in ordinary inline flow, and
 * a value too long for one line wraps under the value column rather
 * than under the label. */
.sf-pdp__rail .wp-block-post-terms {
	display: block;
	padding-left: 72px;
}

.sf-pdp__rail .wp-block-post-terms__prefix {
	display: inline-block;
	width: 72px;
	margin-left: -72px;
}

/* the spacing between rows, written as a top margin on each row AFTER
   the first — `:last-child` cannot do this job here, because the last
   row inside the group is Tags, not Brands, and zeroing it would close
   the gap in the middle of the block */
.sf-pdp__rail .wp-block-post-terms + .wp-block-post-terms,
.sf-pdp__rail .wp-block-woocommerce-product-meta .wp-block-group + .wp-block-post-terms {
	margin-top: 6px;
}

.sf-pdp__rail .wp-block-woocommerce-product-meta,
.sf-pdp__rail .wp-block-woocommerce-product-sku,
.sf-pdp__rail .wp-block-post-terms {
	font-family: var(--sp-body);
	font-size: 13px;
	line-height: 18.48px;
	letter-spacing: 0.24px;
	color: var(--sp-muted);
}

.sf-pdp__rail .wp-block-post-terms a {
	color: var(--sp-text);
	text-decoration: none;
}

.sf-pdp__rail .wp-block-post-terms a:hover {
	color: var(--sp-accent);
}

/* ---- the description, at the foot of the rail ----
 * POST CONTENT, NOT POST EXCERPT (operator, 2026-11-02). These rules
 * read `.wp-block-post-excerpt` until the template swapped the block;
 * the class comes from the block type, so they matched nothing for as
 * long as the two disagreed and the description rendered at the theme's
 * own 16.8px, unjustified, with no rule above it. Keep this block name
 * in step with templates/single-product.html and the CARDS table in
 * assets/js/single-product-rail.js. */
.sf-pdp__rail .wp-block-post-content {
	/* matched to the meta block above it - see the note there */
	margin: 18px 0 0;
	padding: 14px 0 0;
	border-top: 1px solid var(--sp-hair);
}

/* NO `__excerpt` COUNTERPART. The excerpt block wrapped its text in an
   inner .wp-block-post-excerpt__excerpt; Post Content has no such
   wrapper, its paragraphs are direct children. A find-and-replace of
   the old selector leaves `.wp-block-post-content__excerpt`, which can
   never match — the live stylesheet still carries one. */
.sf-pdp__rail .wp-block-post-content p {
	margin: 0 0 10px;
	font-family: var(--sp-body);
	font-size: 14px;
	line-height: 18.48px;
	letter-spacing: 0.24px;
	/* justified with the description tab - see the note there. The rail is
	   374px of content, well inside the measure where rivers would show. */
	text-align: justify;
	color: var(--sp-muted);
}

/* THE LAST PARAGRAPH DOES NOT NEED A GAP UNDER IT. Its 14px bottom
   margin sat on top of the rail's own 24px bottom padding, so the rail
   ended with 38px of nothing - the dead strip under the description in
   the operator's screenshot. The margin is right BETWEEN paragraphs and
   wrong after the last one. */
.sf-pdp__rail .wp-block-post-content > :last-child,
.sf-pdp__rail .wp-block-post-content p:last-child {
	margin-bottom: 0;
}

/* nothing written → no empty rule floating at the foot of the rail */
.sf-pdp__rail .wp-block-post-content:empty {
	display: none;
}


/* -------------------------------------------------------------
 * 3b. THE BUY BOX, MATCHED TO THE REFERENCE
 *
 * (operator, 2026-10-22, with a screenshot of the logitechg.com Yeti 2
 * product page: "its not same like the interface that i send it to you".)
 *
 * Section 3 above is the rail as it was designed from revamp/product-b.html
 * — a tight technical column: 10px mono labels, a 16.8px price, a 176px
 * button ranged left beside a quantity plate. That is a different object
 * from the reference, which is a wide, airy buy panel. Measured side by
 * side at 1440, these were the differences that actually showed:
 *
 *   price            reference ~32px      ours 16.8px
 *   option label     "Color  Black"       "COLOUR" only, value hidden in
 *                                         the select
 *   stock line       centred, green       left, white, body size
 *   add to cart      full-width pill      123px button + 85px qty plate
 *   delivery/returns two panels           missing entirely
 *   description      headed, in column    unheaded excerpt at the foot
 *
 * WHY A SEPARATE BLOCK RATHER THAN EDITS THREADED THROUGH SECTION 3.
 * Every rule up there carries the measurement and the operator decision
 * that produced it, and several are specificity fixes against
 * woocommerce.css that are easy to break by accident. Overriding in one
 * labelled place keeps that history readable and makes this one block to
 * delete if the technical column is ever wanted back.
 *
 * It sits BEFORE section 4 so it is still inside the controls, and after
 * everything in section 3 so it wins on order at equal specificity.
 * ------------------------------------------------------------- */
.sf-pdp__rail {
	/* the pill. See the note on the button. */
	--sp-pill: 60px;
}

/* ---- the price leads ----
 * 32px, which is the reference's size and happens to be exactly double
 * what was there. On the reference the price is the page's DARKEST text,
 * not an accent — so it takes --sp-price, which is the body colour, and
 * not --sp-accent. Changing the accent back to magenta later must not
 * drag the price with it. */
.sf-pdp__rail .wp-block-woocommerce-product-price,
.sf-pdp__rail .wp-block-woocommerce-product-price .price,
.sf-pdp__rail .wp-block-woocommerce-product-price .amount,
.sf-pdp__rail .wp-block-woocommerce-product-price bdi {
	font-family: var(--sp-tech);
	font-size: 32px;
	font-weight: 600;
	line-height: 36px;
	letter-spacing: 0.5px;
	color: var(--sp-price);
}

/* a rule under the price, closing the "what it is" group before the
   "what you are choosing" group starts — the reference's divider */
.sf-pdp__rail .wp-block-woocommerce-product-price {
	padding-bottom: 24px;
	border-bottom: 1px solid var(--sp-hair);
}

/* ---- the attribute head row: "FITS            RESET" ----
 * (operator, 2026-11-02: the label, the dropdown and CLEAR "is not
 * perfect"; option 1 of docs/concepts/pdp-variation-picker.html.)
 *
 * THE NAME IS A CAPTION OVER A CONTROL, SO IT IS SET AS ONE. It was an
 * 18px Archivo heading with the chosen value repeated beside it in grey —
 * heavier than the stock line, nearly as heavy as the price, and saying
 * "NVX / Aerox" directly above a box that already says NVX / Aerox.
 *
 * That echo was right when it was written (2026-10-22): the native
 * <select> was the only place the value appeared, and the label was the
 * one element CSS could reach. The .sf-pick button built on 2026-11-02
 * prints the value itself — section 8 — so the echo became a duplicate
 * rather than an answer, and the span that carried it is gone from
 * shop-beast.js with it. Putting it back means reviving BOTH.
 *
 * THE RESET SITS ON THIS LINE, one per attribute, written here by
 * shop-beast.js — see "the per-attribute reset" there. WooCommerce's own
 * .reset_variations link is hidden in section 3 instead: it clears every
 * attribute at once and had nowhere to live but the foot of the form,
 * where it read as an orphan with no stated scope.
 *
 * (0,5,3) on the label, for the same reason the old rule needed it.
 * woocommerce.css has
 *     .woocommerce div.product form.cart .variations label
 * at (0,4,2) — 11px Chakra Petch caps at 2.2px tracking in --sp-faint,
 * the label style for the whole site's WooCommerce forms. A (0,3,3)
 * version of this loses on class count and the house rule paints
 * instead. Same trap as the <select> below. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .variations th label,
body.single-product .sf-pdp .sf-pdp__rail form.cart .variations label {
	display: block;
	margin: 0;
	font-family: var(--sp-tech);
	font-size: 11px;
	font-weight: 600;
	line-height: 18px;
	letter-spacing: 1.6px;
	text-transform: uppercase;
	color: var(--sp-muted);
}

/* THE <th> IS THE ROW, and it has to beat section 3's own
 *     … table.variations:not(.sb-hidden) th { display: block }
 * which is (0,6,4) since the cell-padding fix. (0,7,4) here: the same
 * stack plus `table`, the `:not()` and the head class. Raise that rule
 * and this one has to move with it — they are fighting over `display`
 * on the same element, and if block wins the RESET drops onto its own
 * line under the label. `min-height` keeps the line the same height
 * whether the reset is showing or not, so choosing a value does not
 * nudge the dropdown down by a pixel. */
body.single-product .sf-pdp .sf-pdp__rail form.cart table.variations:not(.sb-hidden) th.sf-attr__head {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 12px;
	min-height: 18px;
	margin: 0 0 10px;
}

/* IT IS ONLY THERE ONCE THERE IS SOMETHING TO CLEAR. Hidden with opacity
   rather than display so the row cannot reflow as it appears, and with
   pointer-events because a 0-opacity button is still clickable. The button
   is `disabled` in that state as well — opacity alone leaves it in the tab
   order; see paint() in shop-beast.js. */
.sf-pdp__rail .sf-attr__reset {
	padding: 0;
	border: 0;
	background: none;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	letter-spacing: 1.2px;
	text-transform: uppercase;
	color: var(--sp-faint);
	cursor: pointer;
	opacity: 0;
	pointer-events: none;
	transition: opacity 0.18s ease, color 0.18s ease;
}

.sf-pdp__rail .sf-attr__head.is-set .sf-attr__reset {
	opacity: 1;
	pointer-events: auto;
}

.sf-pdp__rail .sf-attr__reset:hover {
	color: var(--sp-accent);
}

.sf-pdp__rail .sf-attr__reset:focus-visible {
	outline: 2px solid var(--sp-accent);
	outline-offset: 2px;
}

@media (prefers-reduced-motion: reduce) {
	.sf-pdp__rail .sf-attr__reset {
		transition-duration: 0.001ms;
	}
}

/* ---- the dropdown itself ----
 * (0,5,3), and it needs every bit of it. woocommerce.css carries
 *     .woocommerce div.product form.cart .variations select
 * at (0,4,2) with `background: var(--wc-panel)` and
 * `color: var(--wc-text)` — both dark-theme values. Section 3's
 * `.sf-pdp__rail select` is (0,1,1) and lost to it, so on the light page
 * the control came out a near-black #131317 box with white text sitting
 * in the middle of a white column. Measured; it is the one element the
 * palette flip could not reach.
 *
 * Styled like the reference's: a light plate, a hairline, text at
 * reading size rather than the 11px technical caps section 3 uses. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .variations select,
body.single-product .sf-pdp .sf-pdp__rail form.cart select {
	height: 52px;
	padding: 0 44px 0 16px;
	border: 1px solid var(--sp-line);
	border-radius: 6px;
	background-color: var(--sp-plate);
	color: var(--sp-text);
	font-family: var(--sp-body);
	font-size: 15px;
	font-weight: 500;
	letter-spacing: 0;
	text-transform: none;
	/* the caret, redrawn at the new height — section 3 positions it for a
	   44px control and it would sit 4px high on a 52px one */
	background-position: calc(100% - 22px) 24px, calc(100% - 17px) 24px;
}

body.single-product .sf-pdp .sf-pdp__rail form.cart select:focus-visible {
	outline: 2px solid var(--sp-accent);
	outline-offset: 2px;
}

/* the open list is drawn by the OS from these two, so they have to flip
   with the theme or the menu stays black-on-black */
body.single-product .sf-pdp .sf-pdp__rail form.cart select option {
	background: var(--sp-bg);
	color: var(--sp-text);
}

/* ---- the stock line: under the options, left, green in the dot ----
 *
 * IT WAS CENTRED AND BOLD GREEN, which made an inventory count the
 * loudest thing in the buy box — louder than the price — sitting in the
 * path between the choice and the button, with no column edge to line up
 * with (operator, 2026-11-02: "is it suitable the stock indicator is
 * position like that? or more suitable if under the table option and on
 * the left"). Compared three ways in docs/concepts/pdp-stock-line.html.
 *
 * THE DOM POSITION DOES NOT MOVE and did not need to: WooCommerce already
 * prints this between the variations table and the purchase row. Only the
 * alignment and the weight change.
 *
 * THE GREEN MOVES INTO A 6px DOT. The signal survives, the shouting does
 * not, and the brightest thing in the box is the button again. The text
 * itself is muted, as a confirmation should be — see the out-of-stock
 * rule further down, which deliberately inverts that. */
.sf-pdp__rail .woocommerce-variation-availability {
	order: 1;
	flex: 1 0 100%;
	width: 100%;
}

/* THE SITE'S STOCK CHIP IS STRIPPED BACK TO TEXT, HERE ONLY.
 * notices.css draws `.woocommerce div.product .stock` as an inline-flex
 * pill — 999px radius, a tinted background, a 1px border and a leading
 * dot — and that is the house pattern everywhere WooCommerce reports
 * stock. This page keeps the dot and drops the pill: a badge on a line
 * that is true of nearly every product is decoration, and in the sold-out
 * state it badges bad news.
 *
 * (0,5,3) to clear notices.css's (0,3,2) comfortably; it also has to beat
 * the `--c` custom property that rule sets, which is why the colour is
 * restated rather than inherited.
 *
 * THE BLOCK FORM IS A THIRD ARM, AND ON THIS THEME IT IS THE ONLY ONE
 * THAT MATCHES A SIMPLE PRODUCT. `form.cart` is the CLASSIC template's
 * wrapper; a block theme renders the purchase box as
 * `div.wp-block-add-to-cart-form` and there is no `form.cart` anywhere
 * in the document — checked on the live page. So until 2026-11-03 this
 * whole section only ever reached VARIABLE products, through the
 * `.woocommerce-variation-availability` arm, and every simple product
 * kept notices.css's pill. The design was deployed and correct and was
 * simply never selected (operator, 2026-11-03: "why only this have the
 * UI that i want"). Measured: 877 variable drew the new line while the
 * simple product beside it computed border-radius 999px.
 *
 * The `form.cart` arm is KEPT beside it — it costs nothing and covers
 * the classic template if WooCommerce is ever rendered that way here.
 *
 * On a variable product the block arm ALSO matches the availability
 * line, which sits inside the same wrapper. Both arms carry identical
 * declarations, so the overlap is harmless by construction — keep it
 * that way if either arm is edited. */
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-availability p.stock,
body.single-product .sf-pdp .sf-pdp__rail .wp-block-add-to-cart-form p.stock,
body.single-product .sf-pdp .sf-pdp__rail form.cart p.stock {
	display: flex;
	align-items: center;
	gap: 8px;
	width: 100%;
	padding: 0;
	border: 0;
	border-radius: 0;
	background: none;
	font-family: var(--sp-tech);
	font-size: 12px;
	font-weight: 500;
	letter-spacing: 0.6px;
	text-align: left;
	color: var(--sp-muted);
}

/* the dot. `flex` on the basis, not `width` alone — a flex item with text
   beside it will shrink a square to an oval otherwise. */
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-availability p.stock::before,
body.single-product .sf-pdp .sf-pdp__rail .wp-block-add-to-cart-form p.stock::before,
body.single-product .sf-pdp .sf-pdp__rail form.cart p.stock::before {
	content: "";
	flex: 0 0 6px;
	width: 6px;
	height: 6px;
	border-radius: 50%;
	background: var(--sp-stock);
}

/* ::after ONLY. This killed `::before` as well until 2026-11-02 — same
   (0,5,3) as the dot rule above but further down the file, so it won on
   source order and the dot never drew. The chip's trailing element is
   still unwanted; its leading one is now ours. */
body.single-product .sf-pdp .sf-pdp__rail .wp-block-add-to-cart-form p.stock::after,
body.single-product .sf-pdp .sf-pdp__rail form.cart p.stock::after {
	content: none;
}

.sf-pdp__rail .woocommerce-variation-availability p,
.sf-pdp__rail .woocommerce-variation-availability p.stock,
.sf-pdp__rail .wp-block-add-to-cart-form p.stock,
.sf-pdp__rail form.cart p.stock {
	margin: 2px 0 16px;
	line-height: 18px;
	text-align: left;
}

/* OUT OF STOCK IS NOT A GREEN FACT.
 *
 * (0,6,3), and every bit of it is needed. WooCommerce prints this line as
 * `<p class="stock out-of-stock">` — the SAME p.stock the two rules above
 * paint `--sp-stock` on, one of them at (0,5,3). Written as the plain
 * `.sf-pdp__rail .woocommerce-variation-availability p.out-of-stock` it
 * was (0,3,1) and lost to both, so a sold-out variation announced itself
 * in the in-stock green (operator, 2026-11-02: "out of stock but why
 * green color?"). The `form.cart` arm matches the same two selectors, for
 * the simple-product case where the line is not inside the variation
 * wrapper.
 *
 * Not red: the button beside it is already disabled and greyed, and a red
 * alarm for "come back later" overstates it. The one thing it must not
 * read as is a confirmation.
 *
 * BRIGHTER THAN THE IN-STOCK LINE, WHICH IS THE WAY ROUND IT LOOKS WRONG
 * AND IS NOT. "101 in stock" is a confirmation of what the customer
 * already assumed and can stay muted; "Out of stock" is news and has to
 * be read. The dot loses its green for the same reason — nothing here is
 * a go signal. On a variable product this line belongs to the COMBINATION
 * just picked, not to the product, which is why it sits under the picker:
 * the control that fixes it is the one directly above. */
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-availability p.stock.out-of-stock,
body.single-product .sf-pdp .sf-pdp__rail .wp-block-add-to-cart-form p.stock.out-of-stock,
body.single-product .sf-pdp .sf-pdp__rail form.cart p.stock.out-of-stock {
	color: var(--sp-text);
}

body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-availability p.stock.out-of-stock::before,
body.single-product .sf-pdp .sf-pdp__rail .wp-block-add-to-cart-form p.stock.out-of-stock::before,
body.single-product .sf-pdp .sf-pdp__rail form.cart p.stock.out-of-stock::before {
	background: var(--sp-faint);
}

/* ---- [qty] [ADD TO CART] [heart] ----
 * The reference row is just the pill and a circular heart. The quantity
 * plate is KEPT — dropping it would be a change to what the shop can
 * sell, not a change to how it looks — but it shrinks to 72px so the
 * pill is unmistakably the thing in the row.
 *
 * THE PILL IS A DEPARTURE FROM THE HOUSE RADIUS and worth knowing about:
 * everything else on this site is --sp-radius (2px) or a 6px plate, and
 * the cart and checkout buttons still are. It is here because the pill is
 * the single most recognisable part of the reference's buy box. One
 * variable, --sp-pill, reverts it. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .quantity {
	flex: 0 0 72px;
	width: 72px;
	/* 52, not section 3's 56 — the row reads as one control strip only if
	   the three items share a height, and the pill sets it */
	height: 52px;
	border-radius: 6px;
	border: 1px solid var(--sp-line);
}

body.single-product .sf-pdp .sf-pdp__rail form.cart .quantity input.qty {
	width: 72px;
	height: 52px;
}

body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button,
body.single-product .sf-pdp .sf-pdp__rail form.cart .single_add_to_cart_button {
	/* grows into everything the qty plate and the heart leave. The 120px
	   basis from section 3 is kept as the floor for the same reason it
	   was chosen there: flex-wrap decides on the basis, before shrink. */
	flex: 1 1 120px;
	height: 52px;
	border-radius: var(--sp-pill);
	font-size: 12px;
	letter-spacing: 1.2px;

	/* THE LABEL COLOUR IS A TOKEN, NOT BLACK. Section 3 hardcodes
	   `color: #000000`, which was right against magenta and is wrong
	   against the reference's cyan — black on #00b8fc is the one
	   combination in this palette that fails to read. --sp-accent-fg
	   moves with the accent; see THE LIGHT PALETTE at the top. */
	color: var(--sp-accent-fg);
	border-color: var(--sp-accent);
	background: var(--sp-accent);
}

/* the hover was a hardcoded lighter magenta; `color-mix` keeps it a
   lighter whatever-the-accent-is, so changing the accent later does not
   leave a pink hover behind on a cyan button */
body.single-product .sf-pdp .sf-pdp__rail form.cart button.single_add_to_cart_button:hover {
	background: color-mix(in srgb, var(--sp-accent) 85%, white);
	border-color: color-mix(in srgb, var(--sp-accent) 85%, white);
}

/* the heart becomes a circle beside the pill, as in the reference */
body.single-product .sf-pdp .sf-pdp__rail form.cart > .shopengine-wishlist,
body.single-product .sf-pdp .sf-pdp__rail .woocommerce-variation-add-to-cart > .shopengine-wishlist {
	flex: 0 0 52px;
	width: 52px;
	height: 52px;
	border-radius: 50%;
	background: transparent;
	border: 2px solid var(--sp-line);
	box-shadow: none;
}

/* ---- the two reassurance panels ----
 * Markup is in templates/single-product.html (.sf-pdp__assure). The
 * reference carries delivery and returns here, directly under the button,
 * because that is where the question gets asked.
 *
 * THE COPY IS NOT INVENTED. It repeats what the shipping and returns
 * pages already say; if those change, change these with them. */
.sf-pdp__assure {
	display: grid;
	gap: 8px;
	margin-top: 20px;
}

/* THE SAME EDGE AS THE DROPDOWN (operator, 2026-11-02: "i want that
   delivery and waranty card border same like border option").

   These were borderless plates at an 8px radius while the control above
   them is a 1px --sp-line hairline at 6px. Two plate treatments a few
   pixels apart in one column read as a mistake rather than a hierarchy.
   Both values now match .sf-pick__btn in section 8 — if that control's
   edge changes, change these with it. */
/* ---- A ROW, ICON LEFT (operator, 2026-11-03) ----
 *
 * REVERTED. These were turned into centred badges — icon above, text
 * centred under it — and taken back the same day: "revert back to old
 * cause its not perfect".
 *
 * Keeping why, so it is not rebuilt from the same reasoning: centring
 * was exact (every line measured the same gap either side) and the
 * lines were evened with `text-wrap: balance`, 264/56 to 161/159. What
 * it could not fix is that two short centred sentences in a 350px rail
 * read as decoration rather than as information, and the rows grew
 * from 62px to 80-98px each — about 54px pushed under Add to cart,
 * twice, in the most valuable part of the page.
 *
 * The one real fault found along the way is still here and still
 * unfixed: with the text on two lines, `align-items: center` puts the
 * icon BETWEEN them — measured 9px below the first line centre.
 * `flex-start` fixes it without changing anything else. Offered, not
 * taken; the comparison page is docs/home-concepts/pdp-assure.html. */
.sf-pdp__assure-row {
	display: flex;
	align-items: center;
	gap: 12px;
	padding: 12px 14px;
	border: 1px solid var(--sp-line);
	border-radius: 6px;
	background: var(--sp-plate);
	font-family: var(--sp-body);
	font-size: 13px;
	line-height: 18px;
	color: var(--sp-muted);
}

.sf-pdp__assure-row svg {
	flex: 0 0 20px;
	width: 20px;
	height: 20px;
	color: var(--sp-text);
}


.sf-pdp__assure-row b {
	color: var(--sp-text);
	font-weight: 700;
}

/* ---- the description gets a heading ----
 * The excerpt already sits at the foot of the rail under a rule. The
 * reference heads it, which is what tells a customer the column has not
 * simply run out. Done with a generated heading rather than a block in
 * the template, so WooCommerce keeps owning the text. */
/* OFF ONCE THE CARD SUPPLIES IT (2026-10-26). The card's own button says
   "Description", so the generated heading made it twice — once as the row
   you click and again as the first line of what it opens. The rule is left
   in place rather than deleted because it is still what heads the excerpt
   if the cards are ever taken off again; this is the narrower selector
   turning it off, not a replacement for it.

   THREE CLASSES, DELIBERATELY. At `.sf-pdp__card-body .wp-block-post-content`
   this ties with the rule below and loses on order, because it is written
   above it — which is exactly what happened on the first attempt: measured
   the ::before still rendering "Description" under a card head saying the
   same. Adding .sf-pdp__rail wins on specificity instead, so the two rules
   can sit in either order. */
.sf-pdp__rail .sf-pdp__card-body .wp-block-post-content::before {
	content: none;
}

.sf-pdp__rail .wp-block-post-content::before {
	content: "Description";
	display: block;
	margin: 0 0 12px;
	font-family: var(--sp-body);
	font-size: 18px;
	font-weight: 700;
	line-height: 22px;
	color: var(--sp-text);
}


/* -------------------------------------------------------------
 * 4. THE GALLERY
 *
 * WooCommerce's own gallery (FlexSlider + thumbnails + zoom) is
 * kept intact — rebuilding it would cost the lightbox and the
 * variation image swap. Only the stage is restyled: 4:3 on a dark
 * tile, with the product CONTAINed rather than cropped.
 * ------------------------------------------------------------- */
.sf-pdp__gallery {
	/* THE GUTTER TO THE RAIL IS 56, NOT 96 (operator, 2026-11-03).
	 *
	 * This was `padding: var(--sp-step)` — 48 on all four sides. The rail
	 * pads its own left by another 48, so the channel between the last
	 * tile and the price column measured 96 against the reference's 56,
	 * and every pixel of that excess came out of the tiles. Measured at
	 * 1440 before: gallery inner 710, tiles 349 square. The reference's
	 * are 388.
	 *
	 * The 40 is given back here rather than by widening the column,
	 * because both of the other numbers in that row are load-bearing and
	 * documented elsewhere in this file:
	 *
	 *   - the 77px page gutter is derived, not chosen — it is what puts
	 *     this column's content at x=125, the shop grid's own left edge,
	 *     so the page does not jump when a customer opens a product from
	 *     the shop. See the max() padding on .sf-pdp.
	 *   - the rail's 470 is the concept's 374 of content plus its 48s,
	 *     and the same slot the category filter rail occupies.
	 *
	 * So the LEFT padding stays at --sp-step and only the right side
	 * moves. calc() rather than a flat 8px so it keeps tracking --sp-step:
	 * the two paddings either side of the channel always sum to 56, which
	 * is the number being matched. Below 1000px --sp-step is 24 and the
	 * row has already stacked, so the rail is not beside it any more and
	 * the clamp keeps this from going negative.
	 *
	 * Measured after: gallery inner 750, tiles 363 square. The remaining
	 * 25 to the reference's 388 is exactly the two numbers above, and is
	 * not worth the page jumping. */
	padding: var(--sp-step) max(0px, calc(56px - var(--sp-step))) var(--sp-step) var(--sp-step);
	/* NO SLAB (operator, 2026-10-07: "the background is carbon"). This was
	   var(--sp-bg) - a flat #171717 fill. It is almost the same colour as
	   the page, which is why it took a screenshot of the EDGE to see it at
	   all: the page carries the carbon weave and this painted a plain
	   rectangle straight over it, so the texture stopped dead where the
	   gallery began. Transparent lets the weave run through. */
	background: transparent;
}

/* The block wrapper and the gallery both carry widths of their own
   (512px, and an inline one FlexSlider writes) — they have to give. */
.sf-pdp__gallery .wp-block-woocommerce-product-image-gallery,
.sf-pdp__gallery .woocommerce-product-gallery {
	width: 100% !important;
	max-width: none;
	/* `margin: 0` here is load-bearing, not tidiness. WooCommerce ships
	   .woocommerce-product-gallery with margin-bottom: 2em, which rendered
	   33.6px of nothing between the thumbnails and the foot of the gallery
	   panel - invisible, because the panel's own 48px of padding is below
	   it, so it just read as the gap to RELATED PRODUCTS being too big
	   (operator, 2026-10-06). Measured: thumbnails ended at 714, the panel
	   at 796.

	   The `margin: 0` on THIS selector does not win - see the rule below. */
	margin: 0;
}

/* AND IT TAKES (0,4,2) TO BEAT IT. WooCommerce sets that 2em through
   `.woocommerce div.product div.images`, and the gallery element really
   does carry `images` among its classes. That selector is (0,3,2); the
   rule above is (0,2,0), so `margin: 0` lost and the computed value stayed
   33.6px while the stylesheet looked correct. body + .single-product +
   .sf-pdp + .sf-pdp__gallery + div + .woocommerce-product-gallery is
   (0,4,2), which clears it. Same trap as the quantity border and the
   thumbnail row - this file has three of them now. */
body.single-product .sf-pdp .sf-pdp__gallery div.woocommerce-product-gallery {
	margin-bottom: 0;
}

/* ===== THE GALLERY IS A TILE GRID (operator, 2026-10-22) ==============
 *
 * Every photograph is on screen at once, as a grid of square tiles —
 * the arrangement on the logitechg.com product page the operator pointed
 * at. It replaces the single capped 4:3 stage with a thumbnail strip
 * under it.
 *
 * WHY IT IS BETTER HERE SPECIFICALLY: this product has two photographs.
 * A slider with two slides and a two-item thumbnail row spends a whole
 * control affordance on one hidden picture, and the old stage was capped
 * at 620px inside a ~1050px column precisely because one big picture had
 * nothing to fill the width with. Two tiles fill it with content instead.
 *
 * THE SLIDER IS STILL THERE AND STILL WORKS. FlexSlider initialises as
 * normal, writes its inline styles, and PhotoSwipe still opens on a
 * click; this only re-lays the track out as a grid. That is why the
 * !importants below are here and why they are the only ones in this
 * section — see the note on them.
 *
 * To put the single stage back: delete this block and the two that
 * follow it, and restore the thumbnail row's `display`.
 *
 * COLUMN COUNT IS A VARIABLE so a product with three or six photographs
 * can be tuned in one place rather than per rule. */
.sf-pdp__gallery {
	--sp-tile-cols: 2;
	/* 24px is the reference's gap, measured on its own grid at 1440:
	   two 388.33 tracks, 24 between them. This was 12, which read as
	   two tiles butted together rather than as a grid. */
	--sp-tile-gap: 24px;
	--sp-tile-ar: 1 / 1;

	/* The tile plate, the reference's #eaebed. It reads --sp-tile from
	   THE LIGHT PALETTE rather than carrying its own value, so the tiles
	   follow when the palette is taken back to the brand.
	 *
	 * NOTE WHAT THIS REPLACED, because the reasoning is still live if the
	 * page ever goes dark again: on 2026-10-07 the gallery lost its slab
	 * because "the background is carbon" — a page-wide #171717 rectangle
	 * painted over the weave and the texture stopped dead where the
	 * gallery began. On a dark page the tile wants to be transparent with
	 * a glow, not a fill. On a light one it wants the reference's grey,
	 * because most of this photography is shot on a pale background and
	 * without a plate the product floats on a ragged white blob. */
	--sp-tile-bg: var(--sp-tile);
}

/* ---- the slider's window stops being a window ----
 * .flex-viewport is a 620px, 465px-tall, overflow-hidden box with its
 * height written INLINE by FlexSlider on every resize. An inline style
 * cannot be beaten by specificity, so height and overflow take
 * !important; everything else here is ordinary.
 *
 * The second selector is the no-JS / no-slider case, where FlexSlider
 * never ran and __wrapper is the direct child. Both are kept so this
 * survives `remove_theme_support( 'wc-product-gallery-slider' )` if that
 * is ever added — at which point every !important below becomes a no-op
 * and can go. */
.sf-pdp__gallery .flex-viewport,
.sf-pdp__gallery .woocommerce-product-gallery > .woocommerce-product-gallery__wrapper {
	height: auto !important;
	overflow: visible !important;
	aspect-ratio: auto;
	width: 100%;
	/* NO CAP ANY MORE. The 620px cap was there because ONE picture in a
	   ~1050px column had to be stopped from upscaling 420px source files
	   to 1057. Two tiles of a 1050px column are about 519 each, so the
	   same files sit at 519 less their padding — still above native, but
	   the whole column is used and nothing is stretched 2.5x. Raise
	   --sp-tile-cols before raising this if a product gains photographs. */
	max-width: none;
	margin-left: 0;
	margin-right: 0;

	/* the panel, its radius and its glow all moved DOWN to the tile — see
	   the rule below. Cleared here so the old stage does not paint a
	   second, column-wide copy of them behind the grid. */
	border-radius: 0;
	box-shadow: none;
	background: none;
}

/* ---- the slider's TRACK becomes the grid ----
 * __wrapper is FlexSlider's track: inline `width: 400%` with a
 * translate3d on it, which is how one slide at a time is shown. Both are
 * inline, so both take !important. Reset to a grid it stops translating
 * anywhere and simply lays its slides out.
 *
 * `width: 400%` is NOT 400% of the column — it is sized against the
 * viewport box, so left alone the grid came out four times too wide and
 * each tile overflowed the column. Measured before the override: wrapper
 * 2480px in a 620px window. */
.sf-pdp__gallery .woocommerce-product-gallery__wrapper {
	display: grid !important;
	grid-template-columns: repeat(var(--sp-tile-cols), minmax(0, 1fr));
	gap: var(--sp-tile-gap);
	width: 100% !important;
	height: auto !important;
	transform: none !important;
	margin: 0;
	padding: 0;
	aspect-ratio: auto;
	background: none;
	list-style: none;
}

/* ---- one tile ----
 * FlexSlider writes `width: 620px; float: left; display: block` on every
 * slide. The width and the float have to go or the grid cells are all
 *620 wide and floated out of their tracks; `display` is harmless and is
 * left alone so a slide that FlexSlider has hidden stays hidden.
 *
 * The plate colour is --sp-tile-bg, set at the top of this section with
 *
 * The plate colour is --sp-tile-bg, set at the top of this section with
 * the reasoning for it.
 *
 * THE RADIUS IS 12, NOT 8 (2026-11-03). The comment here used to claim 8
 * matched the reference; measuring it says otherwise — its tiles compute
 * `border-radius: 12px`. Corrected, and the empty plates below follow
 * through the same value. */
.sf-pdp__gallery .woocommerce-product-gallery__image {
	width: auto !important;
	float: none !important;
	margin: 0 !important;
	aspect-ratio: var(--sp-tile-ar);
	border-radius: 12px;
	overflow: hidden;
	background: var(--sp-tile-bg);
}

.sf-pdp__gallery .woocommerce-product-gallery__image,
.sf-pdp__gallery .woocommerce-product-gallery__image a {
	display: block;
	height: 100%;
}

/* SIZED BY ITS HEIGHT, NOT BY `height: 100%`.
   `height: 100%` was losing to a `height: auto` rule elsewhere, so the image
   took its width from the stage (620) and, being square, came out 620 TALL
   inside a 465 stage — overflowing by 155px and silently clipped by the
   stage's overflow:hidden. The bottom of the rim was cut off.

   max-height/max-width with auto sizing cannot be beaten the same way:
   whatever `height` resolves to, the box can never exceed the stage. At a
   620x465 stage that lands a square photo at about 417px, which is its
   native 420 — sharp, and inside the frame. */
.sf-pdp__gallery .woocommerce-product-gallery__image img {
	box-sizing: border-box;
	width: auto;
	height: auto;
	/* min AND max (operator, 2026-11-03: "why the image have padding?").
	   max-* alone only CAPS: with auto sizing the photo draws at its
	   intrinsic size and never scales UP, which became a white border
	   the moment the tile grew past it. Measured on 877 at the 1300
	   measure: tile 435 square, photo 420 square, 15px of plate showing.
	   min-* pins the box from below so it is exactly 100% of the tile,
	   and constrains the used value rather than setting it, so it is not
	   beaten by the stray height:auto the note above describes.
	   object-fit below keeps the ratio, so a non-square photo letterboxes
	   rather than stretching. A tile wider than the photograph now
	   enlarges it: 877 is a 420px jpeg drawn at 1.036x, while most of the
	   catalogue is a 2560px -scaled file. Bigger upload, not CSS. */
	min-width: 100%;
	min-height: 100%;
	max-width: 100%;
	max-height: 100%;
	margin: 0 auto;
	object-fit: contain;

	/* NO INSET (operator, 2026-11-02: "why every image have white border?").
	   This was 24px of breathing room, and on a studio cutout it is
	   invisible — white padding over a white plate over a photo already
	   shot on white. On a LIFESTYLE shot it is a white frame, because the
	   plate is --sp-tile: #ffffff and the photo stops 24px short of the
	   tile edge on every side. Measured on product 871: 218px tile, 170px
	   photo, a 24px white ring.

	   Taking it to 0 costs the cutouts nothing — a 600x600 part shot
	   carries its own whitespace inside the file — and lets the lifestyle
	   photography run edge to edge. Nothing crops either way: the tile is
	   1/1 and the catalogue's files are square, and `contain` is kept so a
	   non-square one letterboxes rather than losing its edges. */
	padding: 0;
}

/* the slide centres its image rather than ranging it left */
.sf-pdp__gallery .woocommerce-product-gallery__image,
.sf-pdp__gallery .woocommerce-product-gallery__image a {
	display: flex;
	align-items: center;
	justify-content: center;
}

/* THE LIGHTBOX TRIGGER IS HIDDEN (operator, 2026-10-06).
   It is WooCommerce's magnifying glass, which opens the PhotoSwipe
   fullscreen viewer.

   NOTHING IS LOST BY HIDING IT, and that was checked rather than assumed:
   the product image is itself a link to the full-size file, and clicking
   the photograph opens the SAME lightbox — verified by clicking it and
   watching PhotoSwipe open (pswp--open) with no navigation away.

   What it does cost is a hint: the icon was the only visible sign that the
   picture enlarges. If customers turn out not to discover it, bring the
   button back and restyle it as a 28px outlined circle to match the cart
   and heart, rather than leaving WooCommerce's black default. */
.sf-pdp__gallery .woocommerce-product-gallery__trigger {
	display: none;
}

/* ---- the rail's cards (operator, 2026-10-26) ----
 * The description and the SKU/category/tags/brands block, each
 * behind a heading that opens and closes — the reference's arrangement,
 * and what keeps the rail inside its own max-height. Built by
 * assets/js/single-product-rail.js; the reasoning is in its header.
 *
 * Styled off the editorial stack's rules rather than inventing a third
 * look for a heading on this page: --sp-title at the accordion size, a
 * hairline above each row, and the +/- the reference uses. */
/* A RULE ABOVE EVERY CARD, THE FIRST ONE INCLUDED (operator,
   2026-11-03: "on the top of description added back the old line").

   It was briefly `.sf-pdp__card + .sf-pdp__card`, which drew the
   separators between cards but nothing above Description. Put back.
   The rules UNDER the two heads stay gone — that was a separate ask
   the same day and is not what came back. */
.sf-pdp__card {
	border-top: 1px solid var(--sp-line);
}

.sf-pdp__card-head {
	width: 100%;
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 16px;
	padding: 18px 0;
	background: none;
	border: 0;
	cursor: pointer;
	text-align: left;
	font-family: var(--sp-tech);
	font-size: 12px;
	font-weight: 600;
	text-transform: uppercase;
	letter-spacing: 1.8px;
	line-height: 1.2;
	color: var(--sp-text);
}

/* the +/-: one bar always, the second one scaled away when open.
   `transform`, not `display`, so it animates and so the row never
   changes height as it toggles. */
.sf-pdp__card-sign {
	position: relative;
	flex: none;
	width: 14px;
	height: 14px;
}

.sf-pdp__card-sign::before,
.sf-pdp__card-sign::after {
	content: "";
	position: absolute;
	inset: 0;
	margin: auto;
	background: var(--sp-text);
}

.sf-pdp__card-sign::before { width: 14px; height: 2px; }
.sf-pdp__card-sign::after  { width: 2px; height: 14px; transition: transform .18s ease; }
.sf-pdp__card.is-open .sf-pdp__card-sign::after { transform: scaleY(0); }

.sf-pdp__card-body {
	display: none;
	padding-bottom: 20px;
}

.sf-pdp__card.is-open .sf-pdp__card-body {
	display: block;
}

/* the blocks inside lose the margins they had as rail children */
.sf-pdp__card-body > * {
	margin-block: 0;
}

/* ---- NO RULE UNDER A CARD HEAD (operator, 2026-11-03: "remove the line
 *      under description title and under product details title")
 *
 * Both blocks carried a `border-top` from when they sat loose in the
 * rail and needed separating from what was above them — the template
 * still says the description sits "under a rule". Inside a card the head
 * does that job, and the line read as a second, thinner divider 18px
 * below the first. Specifications never had one, so this also makes the
 * three cards agree.
 *
 * THE SPACING THEY CAME WITH GOES TOO. The rule sat 18px below the head
 * on a margin, with 14px of padding under it — 32px of air that only
 * made sense around a line. Zeroed, the content starts where the
 * attribute table's first row does: 10px, which is that row's own
 * padding. The description is given the same 10px by hand, since prose
 * has no row padding of its own. Measured after: all three cards open
 * 10px under their head. */
.sf-pdp__card-body .wp-block-woocommerce-product-meta {
	border-top: 0;
	margin-top: 0;
	padding-top: 0;
}

.sf-pdp__card-body .wp-block-post-content,
.sf-pdp__card-body .wp-block-post-excerpt {
	border-top: 0;
	margin-top: 0;
	padding-top: 10px;
}

/* ---- the attribute table, inside the rail now (operator, 2026-11-03) ----
 *
 * This used to be the Additional information tab at the foot of the page.
 * templates/single-product.html renders it in the rail with the
 * [superfly_product_attributes] shortcode and the card script wraps it.
 *
 * IT HAD TO BE RESTYLED, NOT JUST MOVED. Every rule this file already has
 * for the table is scoped to .sf-pdp__editorial — the tabs' own container
 * — so none of it reaches the rail, and the table arrived wearing
 * WooCommerce's default: full-width borders, striped rows and 12px of
 * padding, in a 350px column. These rules put it in the same language as
 * the meta block in the card above it: label left and muted, value right,
 * a hairline between rows and nothing round the outside.
 *
 * `table-layout: fixed` with a 40% label column, because an attribute
 * called "Fits" and one called "Compatible models" otherwise give two
 * different label widths in the same table — WooCommerce sizes the column
 * to its content. The values wrap instead, which is what should give.
 *
 * COUNT THE TYPE SELECTORS — the same trap as the thumbnails and the
 * add-to-cart button further down. Our own woocommerce.css carries
 *     .woocommerce table.shop_attributes th { font-size: 11px; ... }
 * at (0,2,2), and `.woocommerce` is on <body>, so it reaches the rail.
 * The first version of this block was `.sf-pdp__card-body .sf-pdp__attrs
 * th` at (0,2,1) — the same class count, one fewer type — and lost every
 * declaration. Deployed and measured before the fix: label 11px uppercase
 * at 42% opacity with 8px of padding, none of it from here, and the 40%
 * column never applied either. Naming `table.shop_attributes` takes these
 * to (0,3,2), which wins on class count. Specificity, not !important. */
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes {
	width: 100%;
	table-layout: fixed;
	border-collapse: collapse;
	border: 0;
	margin: 0;
}

.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes th,
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes td {
	border: 0;
	border-bottom: 1px solid var(--sp-line);
	padding: 10px 0;
	vertical-align: top;
	background: none;           /* WooCommerce stripes alternate rows */
	font-family: var(--sp-body);
	font-size: 13px;
	line-height: 1.6;
}

.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes th {
	width: 40%;
	padding-right: 16px;
	font-weight: 400;
	text-align: left;
	color: var(--sp-muted);

	/* STATED, NOT INHERITED. woocommerce.css gives these labels the
	   small-caps treatment it uses for section labels — uppercase at
	   0.16em. That is right for a standalone table on a wide page and
	   wrong here, where the label sits beside "SKU:" and "Category:" in
	   the card above it, which are sentence case. Both have to be undone
	   by hand: neither is reset by the font-size above. */
	text-transform: none;
	letter-spacing: normal;
}

.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes td {
	color: var(--sp-text);
}

/* the last row closes on the card's own rule, not on one of its own */
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes tr:last-child th,
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes tr:last-child td {
	border-bottom: 0;
	padding-bottom: 0;
}

/* WooCommerce wraps each value in a <p>, and that <p> carries 8px of
   PADDING, not margin — resetting the margin alone left it. Measured:
   rows 57px tall against the 41 the padding above asks for, and the value
   sitting 8px below its own label, which is what it looked like. */
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes td p {
	margin: 0;
	padding: 0;
	font-size: inherit;
	line-height: inherit;
	color: inherit;
	font-style: inherit;
}

/* NOT ITALIC. WooCommerce's own stylesheet italicises every value in
   this table — its default for shop_attributes. It reads as emphasis
   that is not meant, and nothing else in the rail is italic. */
.sf-pdp__card-body .sf-pdp__attrs table.shop_attributes td {
	font-style: normal;
}

/* ---- Product details gets the same rhythm (operator, 2026-11-03:
 *      "why product details doesnt have space like specification space")
 *
 * The meta block came from WooCommerce as a tight stack — rows 18px tall,
 * 24px apart — while the attribute table beside it breathes on 10px of
 * padding with a hairline between rows. Two cards in the same rail, one
 * above the other, reading as two different components.
 *
 * The rows are given the table's rhythm rather than the table being
 * squeezed into theirs, because the table's is the one the operator
 * pointed at. SKU and Category/Tags sit inside a .wp-block-group and
 * Brands is a SIBLING of it — so both have to be named, and the last of
 * either closes the card without a rule under it. */
.sf-pdp__card-body .wp-block-woocommerce-product-meta .wp-block-group > *,
.sf-pdp__card-body .wp-block-woocommerce-product-meta > .wp-block-post-terms {
	margin: 0;
	padding: 10px 0;
	border-bottom: 1px solid var(--sp-line);
}

.sf-pdp__card-body .wp-block-woocommerce-product-meta > .wp-block-post-terms:last-child,
.sf-pdp__card-body .wp-block-woocommerce-product-meta > .wp-block-group:last-child > :last-child {
	border-bottom: 0;
	padding-bottom: 0;
}

/* the group's own gap would add to the padding and give a bigger step
   between SKU and Category than between Category and Brands */
.sf-pdp__card-body .wp-block-woocommerce-product-meta .wp-block-group {
	gap: 0;
}

/* ---- and one label column across both cards ----
 *
 * 40% and a 16px gutter, the same two numbers the attribute table uses,
 * so "Category:" and "Fits" start on the same x and so do their values.
 * Both rows are 100% of the card body, so the two 40%s resolve to the
 * same pixel — 140 of 350 in the rail at the 1300 measure.
 *
 * THE SECOND BOX IS MADE BY SCRIPT. WooCommerce emits the row as a label
 * span followed by loose links, so flex here alone would make every link
 * and every comma between them its own column. single-product-rail.js
 * wraps everything after the label in .sf-pdp__meta-value first — see
 * the note there. The flex below is only safe because of it. */
.sf-pdp__card-body .wp-block-post-terms,
.sf-pdp__card-body .wc-block-components-product-sku {
	display: flex;
	align-items: flex-start;   /* the table's cells are vertical-align: top */
}

.sf-pdp__card-body .wp-block-post-terms__prefix {
	flex: 0 0 40%;
	box-sizing: border-box;
	padding-right: 16px;

	/* THIS SUPERSEDES AN EARLIER HANGING INDENT, and has to undo it.
	   `.sf-pdp__rail .wp-block-post-terms__prefix` solved the same
	   problem without a wrapper: the row took `padding-left: 72px` and
	   the label was pulled back into that gutter with
	   `margin-left: -72px`, leaving the links in ordinary inline flow.
	   Clever, and it gave a 72px label column that could not be made to
	   agree with the attribute table's 40%.

	   The flex-basis above beats its `width: 72px`, but a negative
	   margin is not a width — nothing here cancels it, and it drew the
	   label 72px OUTSIDE the card. Measured: row at x=1061, label at
	   x=989, against the table's 1061.

	   Stated as 0 rather than deleting that rule, because it is in the
	   deployed stylesheet and not in this repo — one of the places the
	   two have drifted. Harmless where the old rule does not exist. */
	margin-left: 0;
}

/* min-width: 0 or a long unbroken value — a tag like
   "Belang / Raider, LC135 SS, Y15ZR / Y16ZR" — refuses to wrap and
   pushes the row wider than the rail. */
.sf-pdp__card-body .sf-pdp__meta-value {
	flex: 1 1 auto;
	min-width: 0;
}

@media (prefers-reduced-motion: reduce) {
	.sf-pdp__card-sign::after { transition: none; }
}

/* ---- the empty tiles (operator, 2026-10-26) ----
 * The grid is always at least six tiles, so a product with two
 * photographs shows two pictures and four waiting plates rather than a
 * half-built grid. assets/js/single-product-gallery.js adds them; the
 * reasoning for six, and for it being JS, is in that file's header.
 *
 * They are PLATES, not dropzones. Nothing here suggests a customer can
 * do anything with them: same tile colour, same radius, same square as
 * the real ones, with the line dropped to --sp-hair and a small icon at
 * the faintest text value. On the shop they read as "more to come"; in
 * wp-admin the operator knows what they mean.
 *
 * Deliberately NOT display:none on a live catalogue page. The whole
 * point is that the shape of the gallery does not change when a photo is
 * added — the picture simply appears where a plate was. */
/* WooCommerce's OWN placeholder is hidden, or a product with no pictures
   gets seven tiles: its grey "no image" graphic plus our six. Ours are
   kept rather than its, because they are the same plate as a real tile
   and its is a stock illustration from the plugin. The JS already
   excludes it from the count, so the moment a first photograph is
   uploaded WooCommerce drops the placeholder, the count becomes 1, and
   the padding falls to five with no change here. */
.sf-pdp__gallery .woocommerce-product-gallery__image--placeholder {
	display: none;
}

/* AN EMPTY FRAME, NOT AN EMPTY PHOTOGRAPH. The first version used
   --sp-tile-bg so a slot matched a real tile exactly, and a product with
   no pictures came out as six large white squares on a carbon page —
   louder than the product it was standing in for. Carbon with a hairline
   says "nothing here yet" without taking the eye. */
.sf-pdp__slot {
	aspect-ratio: var(--sp-tile-ar);
	/* 12, following the real tile above — the two sit in the same grid
	   and a plate with a tighter corner than the photograph beside it
	   reads as a different component. */
	border-radius: 12px;
	background: transparent;
	box-shadow: inset 0 0 0 1px var(--sp-line);
	display: grid;
	place-items: center;
}

.sf-pdp__slot svg {
	width: 28px;
	height: 28px;
	color: var(--sp-faint);
}

/* ---- THE THUMBNAIL ROW IS OFF (operator, 2026-10-22) ----
 * Every photograph is now a tile in the grid above, so the thumbnails
 * were a second, smaller copy of the same two pictures sitting directly
 * underneath them.
 *
 * THE ROW IS ONLY HIDDEN, NOT REMOVED, and the rules that style it are
 * kept below it. FlexSlider still builds it and still tracks the active
 * slide through it, and restoring the single stage means restoring this
 * one declaration rather than rewriting the section.
 *
 * `display: none` has to be the FIRST declaration here, not a separate
 * rule further down: our own woocommerce.css reaches these elements at
 * (0,4,2) — see the specificity note below — and the heavy selectors at
 * the foot of this section would otherwise be the only things it beats. */
.sf-pdp__gallery .flex-control-thumbs {
	display: none;
	flex-wrap: wrap;
	gap: 8px;
	/* matched to the capped stage above, or the thumbnails run on past it,
	   and centred with it */
	max-width: 620px;
	margin: 8px auto 0;
	/* CENTRED UNDER THE STAGE (operator, 2026-10-06). The row was already the
	   same 620px as the stage and starting at the same left edge — the issue
	   was the thumbnails inside it. Two of them span 318px, and at the
	   default flex-start that left 302px of empty space to the right, so they
	   read as shoved into the corner of a wide frame. Centring puts them
	   under the middle of the picture at any count: two, three or six. */
	justify-content: center;
	padding: 0;
	list-style: none;
}

.sf-pdp__gallery .flex-control-thumbs li {
	width: 88px;
	margin: 0;
	list-style: none;
}

/* THE GAP AND THE THUMB SIZE BOTH NEEDED A HEAVIER SELECTOR.
   Our own woocommerce.css carries
       .woocommerce div.product div.images .flex-control-thumbs { margin: 0 }
       .woocommerce div.product div.images .flex-control-thumbs li { ... }
   at (0,3,2), which beats the `.sf-pdp__gallery .flex-control-thumbs` rules
   above at (0,2,0). So the 8px top margin computed to 0 and the thumbnails
   sat flush against the bottom of the picture, and the 88px width never
   applied either — they were rendering at 155.

   COUNT THE TYPE SELECTORS. WooCommerce's rule is (0,4,2), not (0,3,2) —
   `div.product` and `div.images` each contribute a type as well as a class.
   A first attempt at `body.single-product .sf-pdp .sf-pdp__gallery ...` was
   (0,4,1) and still lost, because at equal class counts the type count
   decides. Adding .sf-pdp__presentation takes these to (0,5,1), which wins
   outright. Same approach as the quantity field and the add-to-cart button
   elsewhere in this file: specificity, not !important. */
body.single-product .sf-pdp .sf-pdp__presentation .sf-pdp__gallery .flex-control-thumbs {
	margin-top: 14px;
	margin-left: auto;
	margin-right: auto;
}

body.single-product .sf-pdp .sf-pdp__presentation .sf-pdp__gallery .flex-control-thumbs li {
	width: 88px;
}

/* THE PHOTOGRAPH ITSELF HAS NO LINE EITHER. Same WooCommerce rule, same
   (0,3,3): the main gallery image carried a 1px --wc-line, which drew a
   grey rectangle just inside the stage's own rounded corner. The stage is
   the panel now; the picture inside it does not need an edge of its own. */
body.single-product .sf-pdp .sf-pdp__gallery .woocommerce-product-gallery__image img,
body.single-product .sf-pdp .sf-pdp__gallery .woocommerce-product-gallery__wrapper img {
	border: 0;
}

/* THE THUMBNAILS ARE PLATES TOO, and the selected one is a magenta GLOW
   rather than a magenta outline - the border was the last line left in the
   gallery. */
/* (0,4,1) IS WHAT IT TAKES. Our own woocommerce.css sets BOTH
   `border: 1px solid var(--wc-line)` AND `box-shadow: none` through
   `.woocommerce div.product div.images img`, which is (0,3,3) - so the
   first version of this rule, at (0,2,1), lost twice over: the line stayed
   and the plate shadow never painted. Adding body.single-product and
   .sf-pdp takes it to (0,4,1), which clears it on class count alone. */
body.single-product .sf-pdp .sf-pdp__gallery .flex-control-thumbs img {
	width: 100%;
	aspect-ratio: 1 / 1;
	object-fit: contain;
	padding: 6px;
	border: 0;
	border-radius: 6px;
	background: var(--sp-dark);
	/* FLAT (operator, 2026-10-06: "remove the shadow neuphormic"). These
	   had a plate shadow and the selected one a magenta glow, and at 88px
	   square the glow was wider than the gap between the two thumbnails -
	   it read as a pink haze round the row rather than as a selection.
	   Opacity alone carries the state: 0.55 against 1. */
	opacity: 0.55;
	cursor: pointer;
	transition: opacity 0.2s ease;
}

body.single-product .sf-pdp .sf-pdp__gallery .flex-control-thumbs img:hover {
	opacity: 1;
}

body.single-product .sf-pdp .sf-pdp__gallery .flex-control-thumbs img.flex-active {
	opacity: 1;
}


/* -------------------------------------------------------------
 * 5. THE EDITORIAL STACK
 * ------------------------------------------------------------- */
/* THE MEASURE. Same arithmetic as .sf-pdp in section 1: 1180 of content
   centred, reconstructed from the containing block plus the two alignfull
   escapes, and self-cancelling to a plain --sp-step gutter below that. It
   lands the related grid at 1180 wide starting at x=125 - the shop's own
   grid, to the pixel, so the same card is never shown at two sizes. */
.sf-pdp__editorial {
	padding-top: 0;
	padding-bottom: 0;
	/* FULL BLEED ON --sf-gutter SINCE 2026-11-17, with .sf-pdp above -- the
	   two are a pair and the related grid has to start on the same edge as
	   the gallery. It was max(--sp-step, (100% + root-padding * 2 -
	   --sp-measure) / 2), the same arithmetic one section up. */
	padding-left: var(--sf-gutter);
	padding-right: var(--sf-gutter);

	/* HALF A STEP, NOT A WHOLE ONE. The gallery panel already carries
	   --sp-step of padding inside its bottom edge, so a full step here put
	   96px of blank between the thumbnails and the heading on a desktop.
	   Half lands it at 72, which still reads as a section break. */
	margin-top: calc(var(--sp-step) / 2);
}

.sf-pdp__editorial > * + * {
	margin-top: var(--sp-step);
}

/* every section heading on this column - "Related products",
   "Description", "Reviews" - at the concept's 40/40 on a desktop.
 *
 * IT USED TO BE A FLAT 40px AND IT BROKE ON A PHONE (operator,
 * 2026-10-06: "the title is not nice"). "RELATED PRODUCTS" sets about
 * 420px at 40px uppercase. That is one comfortable line in the 1057px
 * desktop panel and still one line in the 620px stacked panel - but a
 * 375px phone gives the panel 327px, so it wrapped to two lines, and
 * `line-height: 40px` is a ratio of exactly 1.0, so the two lines sat
 * on top of each other with no air between them. Then a 40px bottom
 * margin under a heading that was now 80px tall.
 *
 * So: the size is fluid down to 26px, where "RELATED PRODUCTS" measures
 * about 273px and fits a phone on ONE line; the leading gets a little
 * room in case something longer does wrap; and the space beneath scales
 * with it. 5.2vw keeps the full 40px from 769px up, so a tablet and a
 * desktop are unchanged - only the phone moves.
 *
 * The letter-spacing goes NEGATIVE to match the house. shop-archive.css
 * sets -0.028em on its page title; a positive 0.02em here was both off
 * the brand and ~13px wider across this heading, which is part of why it
 * wrapped in the first place. */
.sf-pdp__editorial h2,
.sf-pdp__editorial h2.wp-block-heading {
	margin: 0 0 clamp(22px, 4.6vw, 40px);
	font-family: var(--sp-title);
	font-size: clamp(26px, 5.2vw, 40px);
	font-weight: 400;
	line-height: 1.04;
	letter-spacing: -0.02em;
	text-transform: uppercase;
	color: var(--sp-text);
}

/* ---- RELATED PRODUCTS: THE ARCHIVE CARD, KEPT IN STEP ----
 *
 * These are copied from shop-archive.css so a product looks the SAME here
 * as it does on the shop. They had drifted badly: this block still carried
 * the card as it was built originally — a white tile, the photo CONTAINed
 * inside it, 20px titles — while the archive card was rebuilt as a
 * full-bleed photograph with a scrim, a leading-zero index and the
 * cart/heart row. The two no longer looked like the same product.
 * Measured before this rewrite: the cards rendered 37px wide.
 *
 * IF THE ARCHIVE CARD CHANGES, CHANGE THIS WITH IT. There is no shared
 * file; shop-archive.css only loads on the shop and taxonomy archives,
 * never on a single product, so the values have to be repeated here.
 * ------------------------------------------------------------- */
.sf-pdp__editorial ul.wc-block-product-template {
	display: grid;
	/* FOUR ACROSS, not three (operator, 2026-10-06: "too big, make it
	   small"). Four 4/5 cards in the 1057px panel come out about 250 wide
	   against 340 at three — close to the archive's own 282, which is the
	   size the card was drawn for. The template asks for 4 products, so this
	   is one tidy row rather than three-and-a-gap. */
	grid-template-columns: repeat(4, minmax(0, 1fr));
	gap: 16px;
	margin: 0;
	padding: 0;
	list-style: none;
	counter-reset: sp-rel;
}

/* THE WIDTH OVERRIDE IS LOAD-BEARING, and it needs this much selector.
   WooCommerce ships, inside a (min-width:600px) query:
       .wc-block-product-template.is-flex-container.is-flex-container.columns-5 > li
           { width: calc(20% - 1em); }
   — the class is repeated deliberately to raise it to (0,4,1). That is
   written for a FLEX list, where 20% means a fifth of the row. This list is
   a GRID, so the percentage resolves against the li's own 276px track
   instead: 20% of 276 less 1em = 38px. Every related card rendered 38px
   wide and 48px tall, which is what they had been doing on the live page.
   Repeating the list classes below takes this to (0,4,2) and settles it. */
.sf-pdp__editorial ul.wc-block-product-template.is-flex-container > li.wc-block-product,
.sf-pdp__editorial li.wc-block-product {
	position: relative;
	display: flex;
	width: 100%;
	flex-direction: column;
	justify-content: flex-end;
	gap: 8px;
	/* the archive card's shape */
	aspect-ratio: 4 / 5;
	width: 100%;
	padding: 0 0 14px;
	border: 0;
	border-radius: 8px;
	overflow: hidden;
	/* NO FACE OF ITS OWN (operator, 2026-10-08: "i dont want the border, i
	   just want the shadow for all the products card"). This was #0d0d10 --
	   three levels lighter than the page, which is what turns any frame
	   round the photo into something that reads as a border. Transparent
	   also lets the page's carbon weave run through the card instead of
	   stopping at it; see section 8, where a flat var(--sp-bg) fill did
	   exactly that to the gallery. Mirrors shop-archive.css. */
	background: transparent;
	counter-increment: sp-rel;
	/* SOFT AND DIFFUSE, NOT STRONG (operator, 2026-10-08: "reduce a shadow
	   for all the card .. i want smooth shadow like second image").

	   This was briefly -5/-5/14 at 6% white over 6/6/16 at 55% black, pushed
	   that hard earlier the same day because the card had just lost its face
	   and its border and there was nothing else describing it. Beside a white
	   rim photograph it read as a hard dark rim rather than a shadow.

	   Smooth comes from BLUR, not from opacity: the sink is now wider (28px)
	   and much weaker (38%), with a small vertical bias so the card reads as
	   lifted off the page rather than lit from one corner. The white side
	   stays, but barely -- just enough to keep the top-left from going dead.

	   Still stronger than the information pages' shared set, which is right:
	   those panels sit on their own lighter backgrounds and these sit on
	   rgb(10,10,10). Do not copy these numbers back to contact/privacy. */
	/* NO SHADOW AT ALL (operator, 2026-10-08: "remove the shadow").

	   The end of a long walk, and the whole route is worth knowing before
	   anyone adds one back:
	     border          -> removed, the site's language is not edges
	     neumorphic set  -> invisible on rgb(10,10,10), three levels
	     strong shadow   -> visible, but a hard rim beside a white photo
	     soft wide shadow-> better, still unwanted
	     none            -> this

	   Nothing now describes the card: no border, no face (it is
	   transparent), no shadow. What separates one product from the next is
	   the feathered photograph and the grid's own gap, and that is the
	   intended result rather than an oversight. The cards are images on a
	   page, not panels.

	   If a shadow is ever wanted back, it belongs here, and read the note on
	   the feather first -- the two have to be judged together, because a
	   shadow outside a photo that fades to nothing draws a rim around empty
	   space. */
	box-shadow: none;
	transition: box-shadow 0.35s cubic-bezier(0.22, 0.61, 0.36, 1),
	            transform 0.35s cubic-bezier(0.22, 0.61, 0.36, 1);
}

.sf-pdp__editorial li.wc-block-product:hover {
	border: 0;
	transform: translateY(-3px);
	box-shadow: none;
}

/* the photograph fills the card */
.sf-pdp__editorial li.wc-block-product .wc-block-components-product-image {
	position: absolute;
	inset: 0;
	z-index: 0;
	margin: 0;
	padding: 0;
	aspect-ratio: auto;
	overflow: hidden;
	background: transparent;
	border-radius: 8px;

	/* NO FEATHER, NO SHADOW, NO BORDER -- the photograph is simply the card
	   (operator, 2026-10-08: "why the product still have the shadow ?
	   please remove").

	   A mask used to fade the outer 26px of the picture to nothing. On the
	   dark shots it was invisible; on the white studio shots -- and the
	   source JPEGs are pure 255,255,255 right to their edge, verified by
	   sampling the file rather than by eye -- it faded white straight into a
	   near-black page, which IS a dark halo round the product. Once the
	   card's box-shadow was gone it was the only soft edge left on screen,
	   and it read as the shadow that had just been removed.

	   THE WHOLE SEQUENCE, so nobody re-opens a closed question:
	     hairline border        removed
	     lighter card face      removed (it made any frame read as a panel)
	     inset frame            tried twice, worse both times
	     edge vignette          removed
	     neumorphic shadow      removed, after being strengthened and softened
	     feather mask           removed -- this
	   What is left is the photograph, full bleed, hard edged, with 8px
	   corners. The grid gap separates one product from the next and nothing
	   else does. That is the settled answer, reached by eliminating every
	   alternative in turn.

	   The one soft thing that REMAINS is the scrim gradient on ::after, and
	   it is not decoration: the name and price sit on the photograph and
	   over a white rim they are unreadable without it. Do not remove that
	   without moving the text off the picture first. */

}

.sf-pdp__editorial li.wc-block-product .wc-block-components-product-image a,
.sf-pdp__editorial li.wc-block-product .wc-block-components-product-image img {
	display: block;
	width: 100%;
	height: 100%;
}

.sf-pdp__editorial li.wc-block-product .wc-block-components-product-image img {
	object-fit: cover;
	background: transparent;
	transition: transform 0.45s cubic-bezier(0.22, 1, 0.36, 1);
}

.sf-pdp__editorial li.wc-block-product:hover .wc-block-components-product-image img {
	transform: scale(1.04);
}

/* the scrim, so the words hold up over a white studio shot */
.sf-pdp__editorial li.wc-block-product::after {
	content: "";
	/* THE EDGE VIGNETTE IS GONE (operator, 2026-10-08: "why the product
	   have shadow inside the image ? please remove it").

	   It was `box-shadow: inset 0 0 44px 16px rgba(0,0,0,.78)` on this
	   pseudo-element, added 2026-10-06 to give the neumorphic light a dark
	   surface to fall on where the photograph was a white studio shot. It
	   worked as a lighting trick and read as a dirty shadow painted inside
	   the picture, which is what was asked to be removed. The card is now
	   defined by its OUTER neumorphic shadow only, the same way contact.css
	   draws its panels.

	   If the white-backed shots ever need help again, do it on the CARD
	   (its face, its shadow), never inside the photo. And note the trap
	   that put it here in the first place: an inset box-shadow on the image
	   WRAPPER paints below its children, so the <img> covers it -- the
	   computed value looks right and the screen does not change.

	   The gradient below stays. That is the text scrim, not the vignette:
	   without it the name and price are unreadable over a white product. */
	position: absolute;
	inset: 0;
	border-radius: 8px;
	z-index: 1;
	pointer-events: none;
	/* THE LAST STOP IS OPAQUE, AND IT IS THE PAGE'S OWN COLOUR
	   (operator, 2026-10-08: "why i stil see the border ? in product
	   cards").

	   It used to end at `rgba(10,10,12,0.96)`. Two things were wrong with
	   that and together they drew what looked exactly like a border:

	     * 0.96, not 1 -- so 4% of the PHOTOGRAPH still came through at the
	       very bottom of the card. These shots are mostly light grey
	       studio backdrops, so 4% of ~200 lifted the strip about eight
	       levels above the page.
	     * 10,10,12 against a page of 10,10,10 -- two more levels, blue.

	   The card is `overflow: hidden` with an 8px radius, so that lighter
	   strip was clipped to a rounded rectangle: a crisp, rounded, slightly
	   bright edge sitting exactly where a 1px border would be. Nothing in
	   the cascade declared one -- computed `border` read `0px none`
	   throughout, which is why it survived the first pass.

	   Now it reaches solid rgb(10,10,10) at 90% and holds it to the foot,
	   so the bottom of the card IS the page and there is no edge to see.
	   If the page background ever changes, change this with it. */
	background: linear-gradient(180deg,
		rgba(10, 10, 10, 0.55) 0%,
		rgba(10, 10, 10, 0) 26%,
		rgba(10, 10, 10, 0) 44%,
		rgba(10, 10, 10, 0.82) 72%,
		rgb(10, 10, 10) 90%,
		rgb(10, 10, 10) 100%);
}

/* the leading-zero index, top left */
.sf-pdp__editorial li.wc-block-product::before {
	content: counter( sp-rel, decimal-leading-zero );
	position: absolute;
	top: 10px;
	left: 12px;
	z-index: 3;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 700;
	letter-spacing: 0.18em;
	color: rgba(255, 255, 255, 0.85);
	text-shadow: 0 1px 3px rgba(0, 0, 0, 0.55);
}

.sf-pdp__editorial li.wc-block-product .wp-block-post-terms {
	position: relative;
	z-index: 3;
	margin: 0;
	/* 14px of gutter, 10.5/0.2em - the archive card's own numbers. These had
	   drifted to 12px, 9.5px and 0.18em, which is small enough to look like
	   a rendering difference rather than a decision, and that is exactly the
	   problem: the same card in two sizes on two pages. */
	padding: 0 14px;
	font-family: var(--sp-tech);
	font-size: 10.5px;
	font-weight: 700;
	line-height: 13px;
	letter-spacing: 0.2em;
	text-transform: uppercase;
	color: var(--sp-accent);
}

.sf-pdp__editorial li.wc-block-product h3.wp-block-post-title,
.sf-pdp__editorial li.wc-block-product h2.wp-block-post-title {
	position: relative;
	z-index: 3;
	margin: 6px 0 0;
	/* 12.5px, matched to .sf-shop__grid - it was 11.5 */
	padding: 0 14px;
	font-family: var(--sp-title);
	font-size: 12.5px;
	font-weight: 600;
	line-height: 16.5px;
	letter-spacing: -0.01em;
	text-transform: uppercase;
	text-align: left;
	color: var(--sp-text);
}

.sf-pdp__editorial li.wc-block-product .wp-block-post-title a {
	display: -webkit-box;
	-webkit-line-clamp: 2;
	line-clamp: 2;
	-webkit-box-orient: vertical;
	overflow: hidden;
	color: inherit;
	text-decoration: none;
}

.sf-pdp__editorial li.wc-block-product .wc-block-components-product-price {
	position: relative;
	z-index: 3;
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 10px;
	margin: 4px 0 0;
	/* 14px with the two rows above it, and 700 to match the archive's own
	   price - it was 12px and 600, so the card's three lines did not even
	   share a left edge with each other. */
	padding: 0 14px;
	font-family: var(--sp-tech);
	font-size: 12px;
	font-weight: 700;
	color: var(--sp-muted);
}

/* the excerpt is not wanted on a card */
.sf-pdp__editorial li.wc-block-product .wp-block-post-excerpt {
	display: none;
}

/* ShopEngine's own controls, hidden — the same rule the archive carries.
   The plugin appends wishlist, quick-view and compare as DIRECT CHILDREN of
   the card, and the product-button block adds a fourth. Left alone they
   stacked up under the price and pushed the title to the middle of the
   card. The child combinator is what makes this safe: the heart that IS
   wanted lives inside .sf-shop__wish within the price element, several
   levels down, and is untouched. */
.sf-pdp__editorial li.wc-block-product > a.shopengine_add_to_list_action,
.sf-pdp__editorial li.wc-block-product > a.shopengine-quickview-trigger,
.sf-pdp__editorial li.wc-block-product > a.shopengine_comparison_add_to_list_action,
.sf-pdp__editorial li.wc-block-product > a.shopengine-wishlist,
.sf-pdp__editorial li.wc-block-product > a.shopengine-comparison,
.sf-pdp__editorial li.wc-block-product > .wp-block-button {
	display: none;
}

/* the heart and cart, now injected into the price row by functions.php */
.sf-pdp__editorial li.wc-block-product .sf-shop__acts {
	display: inline-flex;
	align-items: center;
	gap: 8px;
	flex: none;
}

.sf-pdp__editorial li.wc-block-product .sf-shop__priceval {
	min-width: 0;
	flex: 0 1 auto;
}

.sf-pdp__editorial li.wc-block-product .sf-shop__wish a,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart a,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart button,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart .wp-block-button__link {
	position: static;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 28px;
	height: 28px;
	min-height: 0;
	padding: 0;
	margin: 0;
	/* NEUMORPHIC PLATE, NO BORDER (operator, 2026-10-06: "i dont want
	   border, just added a shadow and neuphormic themes"). It was a 1px
	   rgba(245,245,245,.28) outline on a transparent circle, which is the
	   one piece of the card still drawn as a line rather than as a surface.

	   The face is #16161a - the same plate colour the sort control and the
	   pagination use - and it sits on a #0d0d10 card, so it reads as a
	   raised disc rather than a drawn ring. The light edge carries the
	   shape: on a near-black page a black shadow has almost no headroom,
	   light is the only direction with room, which is why the highlight is
	   the stronger half of the pair. */
	border: 0;
	background: var(--sp-plate);
	box-shadow: var(--sp-plate-shadow);
	border-radius: 50%;
	color: var(--sp-muted);
	font-size: 0;
	line-height: 0;
	text-decoration: none;
	transition: box-shadow 0.25s ease, color 0.25s ease,
	            background-color 0.25s ease, transform 0.2s ease;
}

.sf-pdp__editorial li.wc-block-product .sf-shop__wish a:hover,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart a:hover,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart button:hover {
	background: var(--sp-accent);
	color: #fff;
	box-shadow: 0 3px 12px rgba(236, 30, 121, 0.38);
	transform: scale(1.1);
}

.sf-pdp__editorial li.wc-block-product .sf-shop__wish a i {
	font-size: 12px;
	line-height: 1;
}

/* THE LABEL IS HIDDEN FROM THE EYE, NOT FROM A SCREEN READER.
   WooCommerce puts the text in a <span> inside the button. `font-size: 0` on
   the button alone was not enough — WordPress's generated
   `.has-small-font-size { ... !important }` overrode it and "Add to cart"
   rendered at 14.4px inside a 28px circle. The attribute that adds that
   class is gone from the template, and the span is clipped here as well, so
   neither depends on the other. */
.sf-pdp__editorial li.wc-block-product .sf-shop__cart a > *,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart button > * {
	position: absolute !important;
	width: 1px;
	height: 1px;
	margin: -1px;
	padding: 0;
	overflow: hidden;
	clip-path: inset(50%);
	white-space: nowrap;
	border: 0;
}

/* THE CATEGORY IS A LINK, and the link was taking the theme's text colour —
   so the block read magenta while the words you actually see read white. */
.sf-pdp__editorial li.wc-block-product .wp-block-post-terms a {
	color: inherit;
	text-decoration: none;
}

.sf-pdp__editorial li.wc-block-product .wp-block-post-terms a:hover {
	color: #fff;
}

/* the cart/sliders glyph, drawn with a mask as on the archive */
.sf-pdp__editorial li.wc-block-product .sf-shop__cart a::before,
.sf-pdp__editorial li.wc-block-product .sf-shop__cart button::before {
	content: "";
	flex: none;
	width: 14px;
	height: 14px;
	background: currentColor;
	-webkit-mask: var(--sp-cart) center / contain no-repeat;
	        mask: var(--sp-cart) center / contain no-repeat;
	--sp-cart: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="9" cy="20" r="1.5"/><circle cx="18" cy="20" r="1.5"/><path d="M2 3h3l2.6 12.2a1.6 1.6 0 0 0 1.6 1.3h8.6a1.6 1.6 0 0 0 1.6-1.3L21.5 7H6"/></svg>');
}

.sf-pdp__editorial li.wc-block-product .sf-shop__cart a.product_type_variable::before {
	--sp-cart: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="black" stroke-width="2" stroke-linecap="round"><path d="M4 6h16M4 12h16M4 18h16"/><circle cx="9" cy="6" r="2.2" fill="white"/><circle cx="15" cy="12" r="2.2" fill="white"/><circle cx="8" cy="18" r="2.2" fill="white"/></svg>');
}


/* -------------------------------------------------------------
 * 6. DESCRIPTION + REVIEWS (the product-details block)
 * ------------------------------------------------------------- */
.sf-pdp__editorial .woocommerce-tabs ul.tabs {
	display: flex;
	flex-wrap: wrap;
	gap: 24px;
	margin: 0 0 32px;
	padding: 0 0 16px;
	border-bottom: 1px solid var(--sp-hair);
	list-style: none;
}

.sf-pdp__editorial .woocommerce-tabs ul.tabs li {
	margin: 0;
	padding: 0;
	border: 0;
	background: transparent;
}

.sf-pdp__editorial .woocommerce-tabs ul.tabs li a {
	padding: 0;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	line-height: 12px;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--sp-muted);
	text-decoration: none;
}

.sf-pdp__editorial .woocommerce-tabs ul.tabs li.active a,
.sf-pdp__editorial .woocommerce-tabs ul.tabs li a:hover {
	color: var(--sp-accent);
}

/* the panel heading is a duplicate of the tab it sits under */
.sf-pdp__editorial .woocommerce-Tabs-panel > h2:first-child {
	display: none;
}

/* The concept's story blocks are one huge headline over italic
   prose. There is no WooCommerce field for that, so nothing is
   invented: a heading inside the product's own description gets
   the 110/99 treatment, and the body gets the italic. Write the
   description with h2s and the story blocks appear; write it flat
   and it stays a plain description. */
.sf-pdp__editorial .woocommerce-Tabs-panel h2,
.sf-pdp__editorial .woocommerce-Tabs-panel h3 {
	margin: 48px 0 24px;
	font-family: var(--sp-title);
	font-size: clamp(40px, 7vw, 110px);
	font-weight: 400;
	line-height: 0.9;
	letter-spacing: -0.02em;
	text-transform: uppercase;
	color: var(--sp-text);
}

.sf-pdp__editorial .woocommerce-Tabs-panel h2:first-of-type {
	margin-top: 0;
}

.sf-pdp__editorial .woocommerce-Tabs-panel h2 em,
.sf-pdp__editorial .woocommerce-Tabs-panel h2 strong {
	font-style: normal;
	font-weight: inherit;
	color: var(--sp-accent);
}

/* THE EDITORIAL TREATMENT IS FOR THE DESCRIPTION ONLY (operator,
   2026-10-06: "why too big").

   This was `.woocommerce-Tabs-panel p, li` — EVERY paragraph and list item
   in EVERY tab. It was written for the product story, but the review form
   lives in a tab panel too, so it also set 24px italic on "Your email
   address will not be published", on every field label, and on the "save my
   name" checkbox line. A form rendered as editorial body copy.

   Scoped to #tab-description now, and down from 24px to 16. One sentence of
   copy did not need 24px, and the panel is only 703px wide. */
.sf-pdp__editorial #tab-description p,
.sf-pdp__editorial #tab-description li {
	/* PLAIN BODY COPY, matching the rest of the site (operator, 2026-10-06:
	   "still big and not same with other page"). It had been 24px italic as
	   an editorial treatment, then 16px italic; the italic was the half that
	   still made it look like a different page from every other one. */
	max-width: 68ch;
	font-family: var(--sp-body);
	font-style: normal;
	font-size: 15px;
	line-height: 25px;
	/* JUSTIFIED (operator, 2026-10-07: "make it align justify"), the same
	   treatment the category description already carries on the shop
	   archive, so the two bodies of product prose on this site match.

	   THE 68ch MEASURE ABOVE IS WHAT MAKES IT SAFE. Justified text in a very
	   wide column opens "rivers" of white between the words; held to about
	   68 characters the extra space per line stays small enough not to show.
	   Do not remove the max-width and leave this in. */
	text-align: justify;
	color: var(--sp-text);
}

/* everything else in a panel is interface, not prose */
.sf-pdp__editorial .woocommerce-Tabs-panel p,
.sf-pdp__editorial .woocommerce-Tabs-panel li,
.sf-pdp__editorial .woocommerce-Tabs-panel label {
	font-family: var(--sp-body);
	font-style: normal;
	font-size: 13.5px;
	line-height: 21px;
	color: var(--sp-muted);
}

/* the attributes table: our own woocommerce.css italicises
   `table.shop_attributes td`, which reads as a mistake beside the labels */
/* ONE SIZE FOR SUPPORTING TEXT (operator, 2026-10-06: "the font is big, not
   standardised with the others").

   The page had THREE body sizes, measured at 375px:
       15px   the description
       14px   these attribute values
       13px   the category line in the rail
   — plus 11px Chakra Petch for the labels and tab names. Three sizes within
   two pixels of each other is not a scale, it is drift; nothing looks
   deliberate and everything looks slightly wrong.

   The scale is now:
       15px   prose you read (the description)
       13px   data you scan (attribute values, the rail's category)
       11px   labels, in Chakra Petch
   Attribute values are data, not prose, so they take 13 and sit level with
   the category line rather than floating between the other two. */
.sf-pdp__editorial .woocommerce-product-attributes td,
.sf-pdp__editorial table.shop_attributes td {
	font-family: var(--sp-body);
	font-style: normal;
	font-size: 13px;
	line-height: 20px;
	color: var(--sp-text);
}

/* THE VALUE IS INSIDE A <p>, AND THAT IS WHERE THE 19px CAME FROM
   (operator, 2026-10-06: "why in mobile and tablet this font still big").
 *
 * WooCommerce prints the cell as `<td><p>EGO 18T 1.6-1.6x14, ...</p></td>`.
 * The rule above sets the <td> to 13px and it does - but the <p> inside it
 * is matched by `.sf-pdp__editorial .woocommerce-Tabs-panel p, li`, which
 * is 13.5px on a desktop and 19px below 1000px. So the cell was 13 and the
 * text in it was 19.
 *
 * I checked this at 375px earlier and reported it fixed, because I measured
 * the <td>. Measuring the box that carries the rule rather than the box
 * that carries the text is exactly how this hid.
 *
 * (0,2,2) against that rule's (0,2,1), so it wins at both widths and the
 * value sits on the 13px data size everywhere. */
.sf-pdp__editorial table.shop_attributes td p,
.sf-pdp__editorial .woocommerce-product-attributes td p {
	margin: 0;
	font-family: var(--sp-body);
	font-size: 13px;
	line-height: 20px;
	color: var(--sp-text);
}

/* ---- the attribute rows: air, and no rule under the last one ----
 * (operator, 2026-10-06: "no need add border under the last additional
 * information, and also increase the gap")
 *
 * WooCommerce's own 0.5em gave 8px above and below a 20px line, and the
 * <td> carried none at all, so three attributes read as one dense block.
 * 14px opens them without turning a 3-row table into a page.
 *
 * The closing rule is removed because it is a SEPARATOR, and there is
 * nothing after the last row to separate it from - it just drew a line
 * under the section and left the panel looking unfinished.
 *
 * body.single-product is needed to carry this: the border is set by our
 * own woocommerce.css at `.woocommerce table.shop_attributes th, td`,
 * which is (0,2,2) - the same as this selector without it, and a tie is
 * settled by file order, which is not something to rely on. */
body.single-product .sf-pdp__editorial table.shop_attributes th,
body.single-product .sf-pdp__editorial table.shop_attributes td,
body.single-product .sf-pdp__editorial .woocommerce-product-attributes th,
body.single-product .sf-pdp__editorial .woocommerce-product-attributes td {
	padding-top: 14px;
	padding-bottom: 14px;
}

body.single-product .sf-pdp__editorial table.shop_attributes tr:last-child th,
body.single-product .sf-pdp__editorial table.shop_attributes tr:last-child td,
body.single-product .sf-pdp__editorial .woocommerce-product-attributes tr:last-child th,
body.single-product .sf-pdp__editorial .woocommerce-product-attributes tr:last-child td {
	border-bottom: 0;
}

/* ---- reviews ---- */
.sf-pdp__editorial #reviews .commentlist {
	margin: 0;
	padding: 0;
	list-style: none;
}

/* ---- OPTION A, "MEASURED COLUMN" (operator, 2026-10-06) ----
 * Chosen from revamp/review-options.html, which also holds the three
 * designs that were not chosen and the measurements that justified the
 * change. What was wrong, measured at 1440:
 *
 *     textarea        1180px wide - the whole page measure
 *     "Add a review"  16.8px Archivo bold, sentence case
 *     submit          84px, alone at x=1221
 *
 * Nothing structural moves. The form is given the 620px measure the
 * description already uses, the review list becomes 15px body copy on the
 * house scale, and the submit ends the FORM rather than the page.
 * ------------------------------------------------------------------ */
.sf-pdp__editorial #reviews .comment_container {
	display: flex;
	align-items: flex-start;
	gap: 16px;
	padding: 0 0 22px;
	margin: 0 0 22px;
	border-bottom: 1px solid var(--sp-hair);
}

/* the last review closes the list; the rule under it separated it from
   nothing, the same argument as the attributes table */
.sf-pdp__editorial #reviews li.review:last-child .comment_container {
	margin-bottom: 0;
	border-bottom: 0;
}

.sf-pdp__editorial #reviews .comment-text {
	flex: 1;
	min-width: 0;
	/* REORDERED IN CSS, NOT IN PHP. WooCommerce prints the stars, then the
	   author line, then the body. Reading it that way puts a score before
	   you know whose it is; name first, then score, then what they said.
	   A flex column lets that happen without touching the template. */
	display: flex;
	flex-direction: column;
}

/* WOOCOMMERCE BOXES THE REVIEW AND IT TAKES (2,4,3) TO UNBOX IT. The
   plugin's own stylesheet draws a 1px #e1dde7 border with a 4px radius and
   1em of padding through
   `.woocommerce #reviews #comments ol.commentlist li .comment-text`, which
   is two ids, three classes and two types. That pale lilac border is a
   light-theme default and it was outlining every review on a near-black
   page. Option A has no box - the rule between reviews does that job. */
body.single-product .sf-pdp__editorial #reviews #comments ol.commentlist li .comment-text {
	border: 0;
	border-radius: 0;
	padding: 0;

	/* AND THE 50px LEFT MARGIN HAS TO GO WITH IT. WooCommerce sets
	   `margin: 0 0 0 50px` in the same rule, from the days when it
	   positioned the avatar absolutely and had to reserve room for it. The
	   avatar here is a flex item with a 16px gap, so the 50px was ADDED on
	   top: measured at 375px, the text started 66px in and had 221px of a
	   327px panel left to live in. A third of the width gone to an empty
	   gutter is most of what "not responsive" was describing. */
	margin: 0;
}

.sf-pdp__editorial #reviews .comment-text .meta { order: 1; }
.sf-pdp__editorial #reviews .comment-text .star-rating { order: 2; margin: 7px 0 0; }
.sf-pdp__editorial #reviews .comment-text .description { order: 3; }

/* THE LIST TITLE. It computed 18px with a line-height of 16.2px - leading
   SMALLER than the type, so on a phone "1 review for Superfly Project X 4
   Spoke Sport Rims (Chameleon)" wrapped to four lines that overlapped each
   other. The 0.9 came from the display treatment on
   `.woocommerce-Tabs-panel h2, h3` (clamp(40px, 7vw, 110px)/0.9); WooCommerce
   won the font-size at 18px but the 0.9 line-height still applied to it.
   A ratio that only works at 110px is a trap on anything that inherits it. */
.sf-pdp__editorial #reviews .woocommerce-Reviews-title {
	font-family: var(--sp-title);
	font-size: clamp(15px, 4vw, 18px);
	font-weight: 400;
	line-height: 1.3;
	letter-spacing: 0.01em;
	text-transform: uppercase;
	color: var(--sp-text);
	margin: 0 0 26px;
	gap: 1000px;
}

/* THE REVIEW IS NOT EDITORIAL BODY COPY. `.woocommerce-Tabs-panel p, li`
   sets 19px below 1000px, and a review is an <li> - so every review
   inherited 19px, which is why the stars rendered at 19px too (the star
   font sizes in em). Stated at (1,2,1) so the panel rule cannot reach in. */
.sf-pdp__editorial #reviews li.review {
	font-size: 15px;
	line-height: 25px;
}

/* magenta, and on the scale rather than at whatever the parent happened to
   be. WooCommerce draws these in its own icon font sized in em. */
.sf-pdp__editorial #reviews .star-rating {
	font-size: 13px;
	color: var(--sp-accent);
}

/* the author line */
.sf-pdp__editorial #reviews p.meta {
	display: flex;
	align-items: baseline;
	gap: 10px;
	margin: 0;
}

.sf-pdp__editorial #reviews .woocommerce-review__author {
	font-family: var(--sp-tech);
	font-size: 11px;
	font-weight: 700;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--sp-text);
}

/* the dash is punctuation holding two things apart that the gap already
   holds apart */
.sf-pdp__editorial #reviews .woocommerce-review__dash {
	display: none;
}

.sf-pdp__editorial #reviews .woocommerce-review__published-date {
	font-size: 12px;
	color: var(--sp-faint);
}

.sf-pdp__editorial #reviews .description p {
	max-width: 68ch;
	font-family: var(--sp-body);
	font-size: 15px;
	line-height: 25px;
	color: var(--sp-text);
}

/* THE SPACE UNDER THE STARS (operator, 2026-10-06: "added a space between
   star and the review text"). It was written as `margin: 9px 0 0` on the
   rule above and measured ZERO - WooCommerce sets `margin: 0 0 1em` through
   `.woocommerce #reviews #comments ol.commentlist li .comment-text p`,
   which is (2,3,3) against that rule's (1,2,1). The stylesheet read as
   though there were 9px of air and there was none.

   Restated at (2,5,3) so it actually applies, and the bottom margin goes
   with it: a 1em gap under the last line of a review only pushed the form
   further away. */
body.single-product .sf-pdp__editorial #reviews #comments ol.commentlist li .comment-text .description p {
	margin: 13px 0 0;
}

/* THE AVATAR. superfly_review_initial_avatar() in functions.php replaces
   WordPress's Gravatar <img> with a <span class="avatar sf-review-avatar">
   holding the author's initial - see the note there for why that one piece
   could not be done in CSS. Both selectors are styled so the disc is right
   whichever is served. */
.sf-pdp__editorial #reviews .avatar {
	flex: none;
	width: 40px;
	height: 40px;
	border-radius: 50%;
	display: flex;
	align-items: center;
	justify-content: center;
	background: rgba(236, 30, 121, 0.14);
	color: var(--sp-accent);
	font-family: var(--sp-title);
	font-size: 15px;
	line-height: 1;
	overflow: hidden;
	object-fit: cover;
}

/* 40px for "there are no reviews yet" was shouting about an absence.
   18px states it and gets out of the way. */
.sf-pdp__editorial #reviews .woocommerce-noreviews {
	/* ranged left with the rest of the panel. It had max-width 760 and sat
	   centred, so it floated 149px in from both sides while every other
	   element in the tab started at the left edge. */
	/* NOT A MESSAGE PANEL. Stated here as well as in notices.css because the
	   copy of woocommerce.css ON THE SERVER has drifted from the repo and
	   still carries the old notice group — including
	   `border-top-color: var(--wc-accent)`, which is where the magenta line
	   across the top came from. Until that file is reconciled, this clears
	   it locally. */
	background: none;
	border: 0;
	border-radius: 0;
	max-width: none;
	margin: 0;
	padding: 22px 0;
	text-align: left;
	font-family: var(--sp-tech);
	font-size: 12px;
	font-weight: 700;
	line-height: 18px;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	color: var(--sp-faint);
}

/* the form's own labels and notes, a step quieter than the fields */
.sf-pdp__editorial #review_form .comment-notes,
.sf-pdp__editorial #review_form .comment-form-cookies-consent label {
	font-size: 12.5px;
	line-height: 19px;
	color: var(--sp-muted);
}

.sf-pdp__editorial #review_form label {
	display: block;
	margin: 0 0 6px;
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 700;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	color: var(--sp-muted);
}

.sf-pdp__editorial #review_form .comment-form-cookies-consent label {
	display: inline;
	margin: 0 0 0 8px;
	font-family: var(--sp-body);
	font-size: 12.5px;
	font-weight: 400;
	letter-spacing: 0;
	text-transform: none;
}

.sf-pdp__editorial #review_form p { margin: 0 0 16px; }

/* FULL WIDTH. THE OPERATOR HAS NOW CHOSEN THIS TWICE - do not cap it
   again without asking (2026-10-06).
 *
 * The history, so nobody re-litigates it: capped at 620, opened to full
 * width on request, capped again at 620 as part of Option A, and opened
 * again here. The argument for 620 is that a single-line field as wide as
 * the site is hard to read back; the argument for full width is that a form
 * ending halfway across its panel looks unfinished. The operator wants the
 * panel filled, and the panel gets filled.
 *
 * What makes it work rather than just wide: NAME and EMAIL sit two-up in
 * the grid below, so neither of them is a 1180px single-line box, and the
 * submit still ends hard right. The textarea is the one field that does
 * take the full measure - and a textarea is the one field where that is
 * defensible, because it wraps. */
.sf-pdp__editorial #review_form,
.sf-pdp__editorial #commentform {
	max-width: none;
}

/* CLOSING THE GAP ABOVE THE FORM (operator, 2026-10-06: "reduce a space
   between review and add a review"). It measured 122px from the last line
   of the review to "ADD A REVIEW", and no single value was to blame - five
   margins stacked:

       15.0  p margin-bottom          (WooCommerce, 1em)
       20.0  li margin-bottom         (WooCommerce)
       19.2  #comments margin-bottom  (theme block gap)
       34.0  wrapper margin-top       (ours)
       30.0  wrapper padding-top      (ours)

   The first three are all "space after a thing that has nothing after it",
   so they go; the last two are the section break and stay, trimmed. 122 to
   about 58. */
.sf-pdp__editorial #reviews #comments {
	margin-bottom: 0;
}

body.single-product .sf-pdp__editorial #reviews #comments ol.commentlist li:last-child {
	margin-bottom: 0;
}

/* the form is a section of its own, under a rule */
.sf-pdp__editorial #review_form_wrapper {
	/* trimmed again on request, 2026-10-06: 122 -> 81 -> 65 from the last
	   line of a review to "ADD A REVIEW". These two are now the ONLY things
	   in that gap - the three stacked WooCommerce margins above were
	   removed - so the number here is the number on screen. */
	margin-top: 20px;
	padding-top: 22px;
/* 	border-top: 1px solid var(--sp-line); */
}

/* "Add a review" was 16.8px Archivo bold in sentence case - the browser's
   default heading size coming through a <span role="heading">, and the one
   piece of type on this page off the 40/18/15/13/11 scale. 18px Archivo
   Black uppercase is what every other section heading here uses. */
.sf-pdp__editorial #review_form #reply-title {
	display: block;
	margin: 0 0 22px;
	font-family: var(--sp-title);
	font-size: 18px;
	font-weight: 400;
	line-height: 24px;
	letter-spacing: 0.01em;
	text-transform: uppercase;
	color: var(--sp-text);
}

/* AIR BETWEEN THE RATING AND THE REVIEW (operator, 2026-10-06). The stars
   sat 10px off "YOUR REVIEW", which is the same distance a label sits from
   its own field - so the five stars read as belonging to the textarea
   below rather than to the "YOUR RATING" label above them. The 10px was
   the inner <p class="stars">'s own margin and .comment-form-rating, which
   is a <div>, contributed nothing.

   The inner margin goes to zero and the block carries 24px instead, so the
   gap between the two fields is twice the gap inside either one. */
.sf-pdp__editorial #review_form .comment-form-rating {
	margin: 0 0 24px;
}

.sf-pdp__editorial #review_form .comment-form-rating p.stars {
	margin-bottom: 0;
}

/* NAME AND EMAIL SIDE BY SIDE - and at full width this is what stops the
   form being a stack of 1180px boxes. Without a wrapper to hang them on.
   WooCommerce prints them as two sibling <p>s with nothing around them, so
   the form itself becomes the grid: everything spans both columns except
   those two. No template override, no PHP.

   These two fields only exist for LOGGED-OUT visitors, which is every real
   customer - signed in, the form has no name or email at all, which is why
   they are missing from the operator's screenshot. */
.sf-pdp__editorial #review_form form#commentform {
	display: grid;
	grid-template-columns: 1fr 1fr;
	column-gap: 14px;
}

.sf-pdp__editorial #review_form form#commentform > * {
	grid-column: 1 / -1;
}

.sf-pdp__editorial #review_form form#commentform > .comment-form-author {
	grid-column: 1;
}

.sf-pdp__editorial #review_form form#commentform > .comment-form-email {
	grid-column: 2;
}

@media (max-width: 620px) {
	.sf-pdp__editorial #review_form form#commentform > .comment-form-author,
	.sf-pdp__editorial #review_form form#commentform > .comment-form-email {
		grid-column: 1 / -1;
	}
}

/* the button ends the form, hard right */
.sf-pdp__editorial #review_form .form-submit {
	display: flex;
	justify-content: flex-end;
	margin: 20px 0 0;
}

.sf-pdp__editorial #review_form input[type="text"],
.sf-pdp__editorial #review_form input[type="email"],
.sf-pdp__editorial #review_form textarea {
	width: 100%;
	padding: 12px 14px;
	border: 1px solid var(--sp-line);
	border-radius: var(--sp-radius);
	background: transparent;
	color: var(--sp-text);
	font-family: var(--sp-body);
	font-size: 14px;
}

.sf-pdp__editorial #review_form input:focus,
.sf-pdp__editorial #review_form textarea:focus {
	outline: 2px solid var(--sp-accent);
	outline-offset: 2px;
}

.sf-pdp__editorial #review_form .submit {
	height: 44px;
	padding: 0 20px;
	border: 1px solid var(--sp-accent);
	border-radius: var(--sp-radius);
	background: var(--sp-accent);
	/* same token as ADD TO CART. Left as a literal this was the one
	   magenta button on the page still printing its label dark. */
	color: var(--sp-accent-fg);
	font-family: var(--sp-tech);
	font-size: 10px;
	font-weight: 500;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	cursor: pointer;
}


/* -------------------------------------------------------------
 * 7. NARROWER SCREENS
 *
 * Below 1000 the rail stops being a rail: it goes back on top,
 * unsticky, and the gallery follows it. A sticky panel taller
 * than a phone screen is a trap, not a convenience.
 * ------------------------------------------------------------- */
@media (max-width: 1200px) {
	/* RELATED PRODUCTS STEP 4 - 3 - 2, mirroring the shop archive
	   (operator, 2026-10-06). They are the same card, so they should break
	   at the same rhythm; a customer moving from the shop to a product
	   should not find the grid behaving differently. */
	.sf-pdp__editorial ul.wc-block-product-template {
		grid-template-columns: repeat(3, minmax(0, 1fr));
	}
}

/* THE SUBMIT BUTTON GOES FULL WIDTH ON TABLET AND PHONE (operator,
   2026-10-06). On a desktop it is an 84px button ranged left, which is
   right for a pointer; on a touch screen a narrow button in a column of
   full-width fields reads as an afterthought and is a smaller target than
   everything above it. 1000px is the same breakpoint the rail already uses
   to stop being a rail, so the page changes shape in one place rather than
   two. */
@media (max-width: 1000px) {
	/* on a touch screen the button stops being a right-hand full stop and
	   becomes the full-width target at the end of the column */
	.sf-pdp__editorial #review_form .form-submit {
		display: block;
	}

	.sf-pdp__editorial #review_form .submit {
		display: block;
		width: 100%;
		height: 52px;
	}
}

@media (max-width: 1000px) {
	.sf-pdp {
		--sp-step: 24px;
	}

	/* THE NARROWED RIGHT PADDING IS A DESKTOP-ONLY TRICK. Above this
	   width it exists to make the channel to the rail measure 56 rather
	   than 96 — see the gallery's padding in section 4. Here the row has
	   stacked, there is no rail beside the pictures, and the same
	   declaration would just hang the grid 8px off centre: 24 of gutter
	   on the left against 32 on the right. Measured at 375 before this
	   line: tile left 24, tile right 32. Square again after. */
	.sf-pdp__gallery {
		padding-right: var(--sp-step);
	}

	/* ---- THE PICTURE LEADS ONCE THE ROW STACKS ----
	 * (operator, 2026-10-06: "yes do the image first on mobile")
	 *
	 * The three pieces are already flex items of .sf-pdp in their own
	 * right - see `display: contents` in section 1 - so all this needs is
	 * to say which comes first. DO NOT try to do it with `order` on
	 * .sf-pdp__presentation if that is ever reinstated as a real box: the
	 * presentation column is the gallery PLUS the description tabs PLUS
	 * related products, so ordering it moves all three together and pushes
	 * Add to cart below the related products. Tried, measured: rail top
	 * 1564 against the gallery's 99. */
	.sf-pdp__gallery {
		order: -1;
	}

	.sf-pdp__rail,
	.sf-pdp__gallery {
		flex: 1 1 100%;
		max-width: 100%;
	}

	.sf-pdp__editorial {
		--sp-step: 24px;

		/* A FULL STEP AGAIN ONCE STACKED. The half step on a desktop is
		   there because the gallery PANEL sits above this block and brings
		   its own --sp-step of padding inside its bottom edge. Stacked, the
		   block above is the rail, which ends on text - so half a step put
		   the heading 12px under the description. */
		margin-top: var(--sp-step);
	}

	.sf-pdp__rail {
		position: static;
		max-height: none;
		overflow: visible;

		/* AND THE RAIL KEEPS A MEASURE. Every block inside it is built for
		   the 374px of content in a 470px column. Stacked it inherits the
		   whole page width, so a one-line "Category: Brakes" and a one-line
		   excerpt each get a hairline rule running the full 758px with
		   nothing underneath it - the empty box in the screenshot. It was
		   not that the rules were too tall, it was that they were too WIDE.

		   620px is the gallery stage's own cap, and the two --sp-step
		   gutters are added on top because the rail is border-box - so the
		   text lands at exactly the width of the photograph above it and
		   shares its left edge. Below 668px the cap stops binding and the
		   rail is full width again, which is what a phone wants. */
		width: 100%;
		max-width: calc(620px + var(--sp-step) * 2);
	}

	/* CENTRED WITH THE PICTURE, and it needs the extra class to do it:
	   core's own `.wp-block-columns .wp-block-column` zeroes the margins at
	   (0,2,0), so a bare `.sf-pdp__rail` at (0,1,0) computed margin-left:0
	   and the rail sat hard against the left edge while the 620px stage
	   above it was centred - measured, rail content at x=24, stage at x=69.
	   Adding .sf-pdp takes this to (0,3,0) and the auto margins apply. */
	.sf-pdp.wp-block-columns .sf-pdp__rail {
		margin-left: auto;
		margin-right: auto;
	}

	.sf-pdp__rail h1.wp-block-post-title {
		font-size: 26px;
		line-height: 28px;
	}

	.sf-pdp__editorial .woocommerce-Tabs-panel p,
	.sf-pdp__editorial .woocommerce-Tabs-panel li {
		font-size: 19px;
		line-height: 24px;
	}
}

@media (max-width: 600px) {
	/* ONE TILE ACROSS ON A PHONE (operator, 2026-10-22).
	   Two tiles of a 375px screen are 158px square, and these are front
	   forks photographed end-on — at 158px, less the 24px of padding
	   inside the tile, the product is a 110px smear. Measured. One column
	   gives a 327px square per photograph and the page simply scrolls,
	   which is what a phone is for.

	   NOTE THIS IS THE OPPOSITE CALL FROM THE RELATED CARDS BELOW, which
	   go two across on the same screen. They are different things: a
	   related card is a thumbnail you are scanning past, and these are
	   the photographs the customer came to look at. */
	.sf-pdp__gallery {
		--sp-tile-cols: 1;
	}

	/* AND THE EMPTY PLATES ARE OFF ON A PHONE.
	   One column is right for photographs and wrong for placeholders: at
	   327px square each, a product with one picture put five empty frames
	   between it and the price. Measured on product 877 at 375px — the
	   gallery ran 2070px and the buy rail started at y=2161, so the price
	   and Add to cart were two full screens down a page of nothing.

	   They earn their place on desktop, where they show the shape of the
	   grid beside the real pictures at no cost. A customer on a phone
	   gains nothing from them, and an uploaded photograph still appears
	   here exactly as before — these are only ever the remainder. */
	.sf-pdp__slot {
		display: none;
	}

	/* TWO ACROSS ON A PHONE, not one. One column gave a single 327px card
	   per row — the card is 4/5, so that is a 409px-tall tile for a related
	   product, and the archive shows two across at the same width. This was
	   left over from the old tall "white tile" related card. */
	.sf-pdp__editorial ul.wc-block-product-template {
		grid-template-columns: repeat(2, minmax(0, 1fr));
		gap: 12px;
	}

	.sf-pdp__rail .quantity input.qty {
		width: 60px;
	}

	/* IT GROWS ON A PHONE TOO (operator, 2026-10-06: "in mobile why add to
	   cart not full width"). This was `flex: 0 1 176px` - shrink but never
	   grow - so once the quantity field dropped to 60px the button stayed
	   at 176 and left a gap of bare rail between it and the heart. Nothing
	   needed that restraint: 60 + 120 + 56 plus two 12px gaps is 260 in a
	   327px rail, so a growing button fills the remainder and cannot
	   overflow. Same declaration as the desktop rule now, so the button
	   behaves the same way at every width and only the basis differs. */
	.sf-pdp__rail button.single_add_to_cart_button {
		flex: 1 1 120px;
	}
}

@media (prefers-reduced-motion: reduce) {
	.sf-pdp__editorial li.wc-block-product .wc-block-components-product-image img,
	.sf-pdp__rail button.single_add_to_cart_button {
		transition-duration: 0.001ms;
	}
}


/* -------------------------------------------------------------
 * 8. THE FITMENT DROPDOWN
 *
 * The native <select>'s open list is drawn by the OPERATING SYSTEM,
 * outside the document, so the `select option` rule in section 3b is
 * the whole of what CSS ever reached — and Windows ignores even that
 * for the highlight, which is where the blue bar came from
 * (operator, 2026-11-02: "i want like my themes").
 *
 * So shop-beast.js rebuilds the control as a button plus a listbox,
 * which these rules CAN style, and hides the real <select> inside
 * the form. See "THE FITMENT DROPDOWN" there.
 *
 * MEASURED OFF THE NATIVE CONTROL IT REPLACES — 52px tall, 6px
 * radius, --sp-plate on a --sp-line hairline, 15px --sp-body at 500.
 * Section 3b sets exactly that on the <select>; the button copies it
 * so nothing on the page moves when the two swap over.
 *
 * THE LIST ESCAPES THE RAIL because .sf-pdp__rail no longer clips —
 * the max-height/overflow pair came off on 2026-11-02. Putting any
 * overflow back on the rail would shear the open list off at the
 * same line it used to shear the cards.
 * ------------------------------------------------------------- */
.sf-pdp__rail .sf-pick {
	position: relative;
	width: 100%;
}

/* the real control: still in the form, still what WooCommerce reads,
   simply not drawn. Not `visibility`/clip — a focusable copy of the
   same control behind the new one is a keyboard trap. */
body.single-product .sf-pdp .sf-pdp__rail form.cart .variations select.sf-pick-native,
body.single-product .sf-pdp .sf-pdp__rail form.cart select.sf-pick-native {
	display: none;
}

/* ---- the closed box ---- */
body.single-product .sf-pdp .sf-pdp__rail .sf-pick__btn {
	display: flex;
	align-items: center;
	width: 100%;
	height: 52px;
	padding: 0 44px 0 16px;
	border: 1px solid var(--sp-line);
	border-radius: 6px;
	background: var(--sp-plate);
	color: var(--sp-text);
	font-family: var(--sp-body);
	font-size: 15px;
	font-weight: 500;
	line-height: 1.2;
	letter-spacing: 0;
	text-align: left;
	text-transform: none;
	cursor: pointer;
	transition: border-color 0.18s ease;
}

body.single-product .sf-pdp .sf-pdp__rail .sf-pick__btn:hover,
body.single-product .sf-pdp .sf-pdp__rail .sf-pick.is-open .sf-pick__btn {
	border-color: var(--sp-accent);
}

body.single-product .sf-pdp .sf-pdp__rail .sf-pick__btn:focus-visible {
	outline: 2px solid var(--sp-accent);
	outline-offset: 2px;
}

.sf-pdp__rail .sf-pick__value {
	overflow: hidden;
	white-space: nowrap;
	text-overflow: ellipsis;
}

/* "Choose an option" is a prompt, not an answer — muted, the way the
   placeholder in a text field is */
.sf-pdp__rail .sf-pick.is-empty .sf-pick__value {
	color: var(--sp-muted);
}

/* the caret, redrawn as a chevron that turns when the list opens —
   the <select> could only ever show a static one */
.sf-pdp__rail .sf-pick__caret {
	position: absolute;
	top: 50%;
	right: 20px;
	width: 7px;
	height: 7px;
	margin-top: -5px;
	border-right: 1.5px solid var(--sp-muted);
	border-bottom: 1.5px solid var(--sp-muted);
	transform: rotate(45deg);
	transition: transform 0.18s ease, border-color 0.18s ease, margin-top 0.18s ease;
}

.sf-pdp__rail .sf-pick.is-open .sf-pick__caret {
	margin-top: -2px;
	border-color: var(--sp-accent);
	transform: rotate(-135deg);
}

/* ---- the open list ---- */
.sf-pdp__rail .sf-pick__list {
	position: absolute;
	top: calc(100% + 6px);
	right: 0;
	left: 0;
	z-index: 30;
	max-height: 264px;
	margin: 0;
	padding: 6px;
	overflow-y: auto;
	border: 1px solid var(--sp-line);
	border-radius: 6px;
	background: var(--sp-plate);
	box-shadow: 0 18px 44px rgba(0, 0, 0, 0.55);
	list-style: none;
}

.sf-pdp__rail .sf-pick__list:focus-visible {
	outline: none;            /* the active row is the visible focus */
}

.sf-pdp__rail .sf-pick__opt {
	margin: 0;
	padding: 11px 14px;
	border-radius: 4px;
	color: var(--sp-text);
	font-family: var(--sp-body);
	font-size: 15px;
	font-weight: 500;
	line-height: 1.2;
	list-style: none;
	cursor: pointer;
}

/* hover and keyboard land on the same paint, so the two never disagree */
.sf-pdp__rail .sf-pick__opt:hover,
.sf-pdp__rail .sf-pick__opt.is-active {
	background: rgba(236, 30, 121, 0.14);
}

.sf-pdp__rail .sf-pick__opt[aria-selected="true"] {
	color: var(--sp-accent);
}

/* what WooCommerce has ruled out: still listed, so the list does not
   change length as choices are made, but plainly not available */
.sf-pdp__rail .sf-pick__opt[aria-disabled="true"] {
	opacity: 0.38;
	cursor: not-allowed;
}

.sf-pdp__rail .sf-pick__opt[aria-disabled="true"]:hover {
	background: none;
}

@media (prefers-reduced-motion: reduce) {
	.sf-pdp__rail .sf-pick__btn,
	.sf-pdp__rail .sf-pick__caret {
		transition-duration: 0.001ms;
	}
}


/* =============================================================
 * 9. THE RELATED CARD IS THE ARCHIVE CARD AGAIN (2026-11-18)
 *
 * Operator, with the related row cropped: "i want this card section
 * its will follow the card like in product category page".
 *
 * IT HAD DRIFTED BY A WHOLE REDESIGN. The block far above says in
 * capitals "IF THE ARCHIVE CARD CHANGES, CHANGE THIS WITH IT", and
 * on 2026-11-16 the archive card was rebuilt as design B -- square
 * photograph, a meta row, a hairline, a bold price and the action as
 * a mark -- and this copy was not touched. Measured side by side at
 * 1440 before this:
 *
 *                    archive            related
 *   card face        #0d0d10            transparent
 *   radius           12px               8px
 *   emboss           .06 / .45          none
 *   photograph       222 x 222 square   335 x 410, the whole card
 *   category         10px/600 grey      10.5px/700 MAGENTA
 *   name             Inter 13/700       Archivo Black 12.5/600
 *   price            Inter 16/700       Chakra Petch 12/700
 *   action           a 16px mark        a 29px control
 *   index            in the meta row    a badge over the photograph
 *
 * SO THIS IS shop-archive.css's OWN BLOCK, COPIED, with three
 * mechanical changes and nothing else:
 *
 *   .sf-shop__grid li.wc-block-product  ->  the selector below
 *   h2.wp-block-post-title              ->  h3 (this template's level)
 *   counter( sf-item )                  ->  counter( sp-rel )
 *
 * KEEPING IT A VERBATIM COPY IS THE POINT. The next time the archive
 * card moves, this can be re-copied and re-prefixed rather than
 * re-reasoned -- which is what failed last time.
 *
 * AND THE --sa-* TOKENS COME WITH IT, declared on the list below.
 * shop-archive.css never loads on a product page, so every
 * var(--sa-...) in the copied rules would otherwise be unresolved --
 * and an unresolved var() is INVALID AT COMPUTED-VALUE TIME, which
 * makes the whole declaration `unset` rather than falling back to
 * anything. pdp-related.css records what that looks like: a heading
 * that was present, correct and painted nothing at all.
 *
 * NOTE --sa-body IS INTER AND --sp-body IS ARCHIVO. Pointing the
 * copied rules at the page's own tokens would have changed the card
 * name's face while every value still read "right".
 * ============================================================= */

.sf-pdp__editorial ul.wc-block-product-template {
	/* shop-archive.css's values, as literals -- the same decision this
	   file already records for --sfop-radius against the navbar's. */
	--sa-text:   #f2f2f4;
	--sa-muted:  #878787;
	--sa-accent: #ec1e79;
	--sa-body:  "Inter", system-ui, -apple-system, sans-serif;
	--sa-tech:  "Chakra Petch", "Archivo", sans-serif;

	--sa-card-face: #0d0d10;
	--sa-card-lift: rgba(255, 255, 255, 0.06);
	--sa-card-sink: rgba(0, 0, 0, 0.45);
}

/* the face and the emboss, and the hover RESTATES them -- left alone it
   would repeat the older values and the card would flatten the moment
   the pointer arrived. shop-archive.css carries the argument. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product:hover {
	background: var(--sa-card-face);
	border-radius: 12px;
	box-shadow: -4px -4px 10px var(--sa-card-lift),
	             5px 5px 14px var(--sa-card-sink);
}

/* =============================================================
 * THE PRODUCT CARD — DESIGN B (operator, 2026-11-16)
 *
 * "i think this card product category is not perfect enough .. its
 * not aesthetic/professional or if user see this , user will not
 * interested even the interface looks like old school". Four designs
 * went up on localhost (docs/home-concepts/card-proposals.css, with
 * mirror-shop.js building the lab from the real archive) and B was
 * chosen, then narrowed twice: "no need to put this" (the fitment
 * chips) and "the price and button i want like this" (bold price,
 * the action as a mark, no label).
 *
 * WHAT WAS ACTUALLY WRONG, measured on the live wheels archive at
 * 1340px rather than described:
 *
 *   THE PRODUCT FILLED 26% OF THE CARD. The media box was 4/3 with
 *   `object-fit: contain` over a SQUARE source, so a 1024x1024
 *   photograph painted 175x175 inside a 234x175 box -- dead space
 *   down both sides, plus 47.2px of margin above it and 36px below.
 *   The card was 257x493 and the thing it sells had a quarter of it.
 *   That is most of why it read as empty, and it is why the first
 *   rule below is the media and not the type.
 *
 *   THE EXCERPT WAS LOUDER THAN THE NAME -- 16.8px against 16px, at
 *   full ink, and truncated mid-sentence. It is off.
 *
 * Measured after, same width: card 454 -> 422, photograph 26% -> 56%
 * of the card. On a 390px phone, 372 -> 305.
 *
 * THIS BLOCK SUPERSEDES RULES ABOVE IT rather than editing them,
 * which is a deliberate trade and not laziness: the rules it changes
 * are scattered over ~400 lines, each carrying the argument for a
 * decision that is still worth reading, and another session was
 * deploying to this box the same afternoon. Deleting it restores the
 * previous card exactly. CONSOLIDATING THE TWO IS WORTH DOING once
 * this design has settled.
 *
 * SELECTOR SHAPES ARE COPIED FROM THE RULES BEING SUPERSEDED, not
 * written fresh. The title is `h3.wp-block-post-title` (0,3,2) above,
 * so a plain `.wp-block-post-title` here would LOSE and the type
 * would silently stay as it was. Equal specificity plus source order
 * is what carries this block.
 * ============================================================= */

/* ---- 1. the card is a column, and the photograph is the top of it */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product {
	display: flex;
	flex-direction: column;
	/* was 24px; every child below carries its own 18px gutter so the
	   photograph can reach the card's edges */
	padding: 0;
	overflow: hidden;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-image {
	/* the whole of the 26% problem is these four lines */
	margin: 0;
	padding: 0;
	aspect-ratio: 1 / 1;
	height: auto;
	overflow: hidden;
}

/* THE SOURCES ARE 1024x1024, so a square box crops NOTHING -- `cover`
   here is pure gain over `contain`, not a trade. Re-check this if a
   product is ever uploaded at a different ratio: cover would then
   crop it, and the fix is the FILE, as category-grid.css records. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-image a,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-image img {
	display: block;
	width: 100%;
	height: 100%;
	margin: 0;
	/* !important BECAUSE THE RULE IT SUPERSEDES HAS IT. The earlier
	   `object-fit: contain !important` sits on the identical selector,
	   so equal specificity plus source order is NOT enough -- an
	   important declaration beats a normal one whatever the order.
	   Measured live after the first deploy: still `contain`, with the
	   element's own inline `object-fit:cover` from WooCommerce losing
	   to it as well. shop-beast.css sets contain twice more. */
	object-fit: cover !important;
}

/* ---- 2. the excerpt is off ---------------------------------- */
/* Truncated marketing copy, and it was the loudest text on the card.
   Hidden rather than removed from the template: the block is in
   archive-product.html, and a CSS hide is one line to undo where a
   template edit is a deploy. It still costs the markup; take it out
   of the template if that ever matters. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-excerpt,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-excerpt:empty {
	display: none;
}

/* ---- 3. the meta row: the index, then the category ----------- */
/* THE NUMBER IS THE SAME COUNTER THE CORNER BADGE USED. It is
   incremented on the <li> itself (see the card's own rule, far
   above), not on the ::before, so hiding that badge does not stop it
   counting and a descendant can still read it. That is what lets
   this row be pure CSS with no markup and no script. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product::before {
	display: none;
}

/* the category label has been `display: none` since the card was
   rebuilt; it is the other half of the meta row now */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms {
	display: flex;
	align-items: center;
	gap: 8px;
	margin: 12px 18px 0;
	font-family: var(--sa-tech);
	font-size: 10px;
	font-weight: 600;
	letter-spacing: .16em;
	line-height: 1.4;
	text-transform: uppercase;
	color: var(--sa-muted);
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms::before {
	content: counter( sp-rel, decimal-leading-zero );
	color: var(--sa-accent);
	font-variant-numeric: tabular-nums;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms a {
	color: inherit;
	text-decoration: none;
}

/* THE SALE BADGE TAKES THE CORNER THE NUMBER VACATED. Its `left` was
   a hard offset clearing that badge -- 24 + the badge's 40 + 6 -- and
   with the badge gone it would have floated in the middle of the
   photograph's top edge. The pair moved together before and still
   does. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-sale-badge {
	left: 24px;
}

/* ---- 4. the name -------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product h3.wp-block-post-title {
	margin: 8px 18px 12px;
	font-family: var(--sa-body);
	font-size: 13px;
	font-weight: 700;
	line-height: 1.42;
	letter-spacing: .02em;
	/* UPPERCASE STAYS, AND THE REASON IS THE DATA. Turning the
	   transform off to try sentence case showed what is actually
	   stored: product 889 is "Superfly Project 4 4 Spoke Sport Rims
	   For Yamaha Y15, LC135 5S" in title case while its neighbours are
	   full caps. With the transform off the grid shows BOTH, card by
	   card, which is worse than shouting consistently. Sentence-case
	   names are an edit to 104 product titles and the operator's
	   call. */
	text-transform: uppercase;
	/* two lines, always -- see the min-height rule above, which is the
	   other half of keeping a row's price line level */
	display: -webkit-box;
	-webkit-line-clamp: 2;
	-webkit-box-orient: vertical;
	overflow: hidden;
}

/* ---- 5. the price row --------------------------------------- */
/* THIS PUTS BACK A BORDER THE OPERATOR HAD REMOVED ON 2026-10-08
   ("why i stil see the border ? in product cards"), and that is worth
   knowing before anyone treats it as an oversight. It is deliberate:
   the hairline is part of design B, which was chosen from four with
   the line visible in every screenshot. What changed since October is
   the card around it -- it had a face then, so a rule across it read
   as a box being divided; the card is now the page colour with a
   full-bleed photograph, and the line is the only thing separating
   the name from the price. One line to drop if it is ever unwanted.

   THE HAIRLINE IS THIS BLOCK'S OWN BORDER, not an element. The
   proposal used a spacer div the script inserted; a border needs no
   markup, cannot fall out of order, and puts the gap above it and the
   gap below it in two properties that are read together.

   THE 24px PADDING THIS BLOCK CARRIES IS THE THEME'S, and it is the
   reason the gap looked wrong at first: the margin that appears to
   set it is on the INNER element, so a "12px" gap measured 36. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-woocommerce-product-price {
	/* auto, so the price line stays level across a row whatever the
	   names do; 12px is then the minimum gap above the rule */
	margin: auto 18px 16px;
	padding-top: 12px;
	border-top: 1px solid rgba(255, 255, 255, .10);
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-price {
	margin: 0;
	padding: 0;
	align-items: center;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__priceval {
	font-family: var(--sa-body);
	font-size: 16px;
	font-weight: 700;
	letter-spacing: normal;
	color: var(--sa-text);
}

/* ---- 6. the action is a mark, not a label ------------------- */
/* `font-size: 0` collapses the text without removing it, so
   WooCommerce's own aria-label -- "Select options for ..." / "Add to
   cart: ..." -- survives for a screen reader. `display: none` would
   take that with it and leave an unlabelled icon.

   THE MARK IS A MASKED SVG, NOT AN ICON FONT. The theme's ::before
   carries `content: ""` with a mask-image data URI and
   `background-color: currentColor`, so FONT-SIZE DOES NOTHING here --
   sizing it needs width/height, and `color` is what tints it. A first
   cut set `font-size: 16px` and the mark stayed 14px.

   THIS REINSTATES SOMETHING 2026-10-22 DELIBERATELY ENDED: the
   control became the words SELECT OPTIONS because "an icon cannot
   say that" -- a variable product says Select options where a simple
   one says Add to cart. Checked before shipping: the mask is a
   DIFFERENT SVG per type, sliders against a trolley, verified across
   all 8 cards as exactly two distinct masks tracking
   product-type-variable / product-type-simple. So the two are still
   told apart visually -- but a first-time visitor will not know that
   sliders means "pick a colour first". Operator's call, made with
   the words visible in the alternative. */
/* THE CLASS IS IN THE SELECTOR ON PURPOSE. The rule being superseded
   is `body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a` with
   `font-size: 12px !important` -- identical specificity to a plain
   version of this, and TWO IMPORTANT DECLARATIONS AT EQUAL
   SPECIFICITY are decided by source order, which should have been
   enough. It was not: measured live after the first deploy, the
   label was still painting at 12px with this rule present, correct
   and last in the file. Adding `.wp-element-button` takes it to
   (0,4,2) so the question does not arise. WooCommerce puts that
   class on the anchor itself. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a.wp-element-button,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button.wp-element-button {
	gap: 0 !important;
	font-size: 0 !important;
	letter-spacing: 0 !important;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a::before,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button::before {
	width: 16px !important;
	height: 16px !important;
	color: var(--sa-accent) !important;
}

/* ---- 7. the phone ------------------------------------------- */
/* The gutters come in with the card, which is 165px wide at 390 --
   18px each side there is a fifth of the measure. The breakpoint is
   the card's own 760px, not a new one. */
@media (max-width: 760px) {
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms {
		margin: 10px 14px 0;
		font-size: 9px;
	}

	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product h3.wp-block-post-title {
		margin: 6px 14px 10px;
		font-size: 12px;
	}

	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-woocommerce-product-price {
		margin: auto 14px 14px;
		padding-top: 10px;
	}

	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__priceval {
		font-size: 14px;
	}

	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-sale-badge {
		left: 16px;
	}

	/* THE PHONE'S MAGENTA DISC GOES, AND NOT FOR TIDINESS. The
	   2026-10-22 rule above restores a 26px filled disc here, with
	   `color: #fff !important` for the glyph inside it -- and this
	   design tints that glyph with the accent, so the first deploy
	   painted magenta on magenta and every phone card showed a SOLID
	   PINK CIRCLE with no mark in it at all. Measured on the live page
	   at 390px; invisible on desktop, which is why it shipped.

	   Two ways out: put the glyph back to white and keep the disc, or
	   drop the disc so the phone reads like the desktop. The disc's
	   own argument was that a phone has no room for the LABEL beside a
	   price -- and the label is gone at every width now, so the disc
	   is solving a problem this design already solved. Dropping it
	   also makes the two look like one card.

	   THE TARGET GETS BIGGER, NOT SMALLER: 26px of disc becomes 44px
	   of tap area around a 16px mark, bought with padding and handed
	   straight back with an equal negative margin so the price row's
	   layout does not move. Same construction as the wishlist heart
	   two sections up.

	   `.wp-block-button__link` is in the list for the reason that rule
	   gives: without it these lose to the full-size selector at
	   (0,4,1). */
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a,
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button,
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart .wp-block-button__link {
		width: auto !important;
		height: auto !important;
		min-width: 0 !important;
		min-height: 0 !important;
		padding: 14px !important;
		margin: -14px !important;
		background: none !important;
		border: 0 !important;
		border-radius: 0 !important;
		box-shadow: none !important;
	}
}


/* ---- 9b. AND THE DISC GOES WITH IT -------------------------------
 *
 * The block above gives the control the archive's bare 16px mark, but
 * this card had its own 28px DISC underneath -- a #16161a face with a
 * light edge, added on its own account and never part of design B.
 * Measured after the port: the mark was right and still sat inside a
 * 29px plate, so the two cards still did not match.
 *
 * The archive has no disc at ANY width, so this clears it at any
 * width. All !important because the rule it is beating is already
 * !important in places and sits on a shorter selector.
 *
 * THE PHONE GETS ITS TAP TARGET BACK below, which is the archive's own
 * construction: 44px of padding round a 16px mark, handed straight back
 * with an equal negative margin so the price row's layout does not
 * move. It has to be restated here because the ported media block is
 * EARLIER in the file than this one.
 * ------------------------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart .wp-block-button__link {
	width: auto !important;
	height: auto !important;
	min-width: 0 !important;
	min-height: 0 !important;
	padding: 0 !important;
	margin: 0 !important;
	background: none !important;
	border: 0 !important;
	border-radius: 0 !important;
	box-shadow: none !important;
}

@media (max-width: 760px) {
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart a,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart button,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__cart .wp-block-button__link {
		padding: 14px !important;
		margin: -14px !important;
	}
}


/* ---- 9c. AND THE FULL-BLEED CARD UNDERNEATH HAS TO BE UNDONE -------
 *
 * Operator, with the row cropped: "why like this ? .. i want you check
 * and follow exactly same 100% product category page".
 *
 * THE PORT SET EVERY PROPERTY THE ARCHIVE SETS AND NONE OF THE ONES IT
 * NEVER NEEDED TO. This card was the OLD archive design -- a
 * full-bleed photograph with the category and the name laid OVER it --
 * and that design is built out of properties design B simply does not
 * mention, so nothing in the copied block could clear them:
 *
 *   li                 aspect-ratio: 4 / 5   -- the tall card shape
 *   .…product-image    position: absolute; inset: 0  -- the photograph
 *                      filling the whole card behind the text
 *   li::after          a scrim gradient over it
 *   terms / title      z-index: 3, to sit on top of that scrim
 *
 * Measured after the port and before this: the photograph computed
 * 331x331 -- correctly square, from the copied aspect-ratio -- while
 * still being absolutely positioned at the card's top-left, so the text
 * ran across it and the card kept its 4:5 shape.
 *
 * THE LESSON IS GENERAL AND THIS IS THE SECOND TIME IN ONE DAY: a port
 * is the union of two designs until the old one's own properties are
 * named and reset. The disc in 9b was the first.
 * ------------------------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product {
	/* the archive card has no shape of its own -- its height is its
	   content, which is what puts the price row at the bottom */
	aspect-ratio: auto;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product::after {
	/* the scrim existed to make white text readable ON the photograph;
	   there is no text on the photograph now */
	content: none;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wc-block-components-product-image {
	position: relative;
	inset: auto;
	z-index: auto;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product h3.wp-block-post-title {
	/* they were lifted above the scrim; there is nothing to clear now */
	z-index: auto;
}

/* ---- 9d. THE ROW FILLS THE MEASURE, AND THE CARD GROWS WITH IT -----
 *
 * Operator, looking at the ported row: "why not full width ?" -- four
 * cards of 222px sat at the left with a third of the measure empty.
 *
 * THE TWO CANNOT BOTH BE HAD, AND THAT WAS PUT TO THEM. The category
 * page fills its row because it has SIXTEEN products; this band has
 * four. Its 222px card is not a number it chooses either -- it is
 * `repeat(4, minmax(0, 1fr))` inside a grid that has already given
 * 320px to the filter rail: (941 - 3x18) / 4 = 221.77. With no rail and
 * four products, a card that size cannot reach the right edge.
 *
 * The choice offered was: raise the related query so the row fills at
 * ~222, or keep four cards and let them grow. **They chose to keep
 * four**, with the sizes visible in the ask:
 *
 *     at 1430   4 cards of 315
 *     at 1890   4 cards of 425
 *
 * SO THE CARD IS ~1.4x THE ARCHIVE'S, DELIBERATELY. This is the same
 * `repeat(4, minmax(0, 1fr))` the archive uses -- the rule is identical
 * and the measure is not, which is the whole of the difference. The
 * ANATOMY is still the archive's to the pixel: square photograph, meta
 * row, two-line name, hairline, bold price, 16px mark.
 *
 * The gap is the archive's 18px. Below 980px it is the archive's own
 * two columns, which is its rule as well as ours.
 *
 * IF "TOO BIG" COMES BACK, the fix is the OTHER half of that choice --
 * more related products, not a smaller card -- because a smaller card
 * is exactly the empty right edge this replaced. perPage lives in
 * templates/single-product.html.
 * ------------------------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template {
	grid-template-columns: repeat(4, minmax(0, 1fr));
	gap: 18px;
}

@media (max-width: 980px) {
	body.single-product .sf-pdp__editorial ul.wc-block-product-template {
		grid-template-columns: repeat(2, minmax(0, 1fr));
	}
}


/* ---- 9e. THE WISHLIST HEART GOES BACK ON THE PHOTOGRAPH ------------
 *
 * The last difference between the two cards, and it was costing 48px
 * of height: this card had the heart IN FLOW above the meta row, so
 * every card carried an empty 48px band under its photograph.
 * Measured: related 222 x 434 against the archive's 222 x 381.
 *
 * shop-archive.css's own block, copied with the same prefix swap as 9
 * above -- including the keyframes, because that file never loads here
 * and an animation-name with no @keyframes behind it is silently
 * nothing.
 *
 * superfly_wishlist_on_image() appends the span as a child of the card
 * li on BOTH pages, and the li is position: relative on both, so the
 * offsets land the same way without any markup change.
 * ------------------------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish {
	/* TOP RIGHT, OPPOSITE THE BADGES (operator, 2026-10-22).

	   The whole history, because this corner has now been argued twice: it
	   began top right, moved to the price line on 2026-10-05 so the price
	   and the heart read as one row, and came back here when the card was
	   rebuilt to the reference's anatomy -- the price row carries the words
	   ADD TO CART now and there is no room for a third item on it.

	   The old objection to this corner was that a fixed offset broke when a
	   title wrapped and moved the price. It does not apply up here: the top
	   of the card does not move, whatever the title does.

	   superfly_wishlist_on_image() in functions.php appends this after the
	   image block, so it is a child of the card `li`, which is
	   `position: relative` -- these offsets are against the card. */
	/* 24 from the top and the right -- the card's own padding, so the heart
	   lines up with the badge opposite it. */
	position: absolute;
	top: 24px;
	right: 24px;
	z-index: 3;
	display: inline-flex;
	align-items: center;
	flex: none;
	line-height: 1;
}

/* ---- the button ----
   ShopEngine ships it as a filled pink "badge" block. Only the look is
   overridden here — the element, its classes and its data-pid are still
   ShopEngine's, so the plugin's own list, its /wishlist/ page and its REST
   route are untouched.

   THE LOOK DID NOT CHANGE ON 2026-11-16. Everything in this block is the
   same bare outline heart it has drawn since 2026-10-22; what changed is
   that the control now works. See assets/js/wishlist-card.js for the four
   faults that were measured on the live archive, of which the first is the
   only one a customer could describe: a guest click ran ShopEngine's own
   alert("Please login first.") and nothing else.

   NO DISC, NO RING, NO PLATE, IN ANY STATE (operator, 2026-11-16: "i think
   A , but i dont want circle border"). Three round things were offered on
   the localhost proposal and all three were turned down — a glass plate
   under the glyph on hover, a faint magenta one behind the saved state, and
   a ring pulsing out of the glyph on press. That also puts the control back
   on this card's own earlier ruling, recorded above: "a bare outline heart
   in the corner, no background and no ring."

   WHAT CARRIES THE AFFORDANCE INSTEAD, now that nothing is painted behind
   the glyph: the glyph itself. Magenta and 12% larger on hover or focus.
   Colour and motion, no new shape. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish .se-btn,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish .badge {
	/* ShopEngine ships this button `position: absolute`, with no offsets set.
	   That is the trap: with all offsets auto an absolute box sits at its
	   STATIC position, so it looks perfectly in place while being out of
	   flow -- the wrapper span collapses to 0x0 and nothing stops the heart
	   being painted outside the card. Measured at 375px before this line:
	   wrapper 0x0 and the button 15-17px past the right edge of the card on
	   half the tiles. Forcing it back into flow is what makes the row
	   responsive, so do not drop this. */
	position: static;
	display: inline-flex;
	align-items: center;
	justify-content: center;

	/* 44px OF TARGET, 28px OF INK, AND NOTHING PAINTED ON EITHER.

	   It was a 28px box -- under the 44px a finger wants, with a 16px glyph
	   inside it and no plate, so a customer on a phone was aiming at a
	   hairline. The box is 44 now and the NEGATIVE MARGINS put the glyph
	   back where it has always been: the wrapper sits at top 24 / right 24,
	   so -8 on each pulls the larger box out until the glyph's centre lands
	   at 38 / 38 from the card's corner -- the pixel the 28px box centred on.
	   Measured live before and after; the control does not move.

	   CHANGE THE PAIR TOGETHER. A width without the matching margin shifts
	   the heart off the line it shares with the 01 badge opposite it. */
	width: 44px;
	height: 44px;
	margin: -8px -8px 0 0;
	padding: 0;

	border: 0;
	background: none;
	box-shadow: none;
	border-radius: 0;
	color: var(--sa-card-ink);
	font-size: 16px;
	line-height: 1;
	/* the icon-font fallback is a FONT, so it inherits letter-spacing, and
	   the 0.16em the card's type carries pushed it 2.6px off its own box --
	   measured, the 16px heart was rendering 18.6 wide and right of centre */
	letter-spacing: 0;
	cursor: pointer;
	/* colour only. Nothing else about this control transitions, because
	   nothing else about it changes. */
	transition: color .25s ease;
}

/* THE GLYPH IS AN INLINE SVG, NOT THE ICON FONT, and that is what lets the
   saved state be a FILL rather than a second glyph. An icon font paints a
   shape chosen by its codepoint; `fill: currentColor` on a path is one
   declaration. superfly_wishlist_button() in functions.php swaps it in
   server-side, so there is no flash of the old glyph on load and the
   control is correct with JavaScript off.

   IF THAT SWAP EVER FAILS the <i> ShopEngine rendered is still there and
   still inherits `color` from the rule above, so the card degrades to the
   outline heart it had before rather than to an empty corner. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a .sfw-heart {
	width: 19px;
	height: 19px;
	flex: none;
	fill: none;
	stroke: currentColor;
	stroke-width: 1.8;
	stroke-linejoin: round;
	transition: transform .18s cubic-bezier(.34, 1.56, .64, 1), fill .18s ease;
}

/* hover and keyboard focus are the same state: there is one affordance and
   it should not depend on which input you arrived with */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:hover,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:focus-visible {
	color: var(--sa-accent);
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:hover .sfw-heart,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:focus-visible .sfw-heart {
	/* 12%, not more: the glyph sits 24px from two card edges and anything
	   that reads as a jump up here pulls the eye off the photograph, which
	   is the card's subject. */
	transform: scale(1.12);
}

/* THE FOCUS RING IS THE ONE RING LEFT, and it is a rounded RECTANGLE, not a
   circle. It appears only for a keyboard user, for whom it is the sole
   indication of where they are on the page. The negative offset pulls it in
   off the 44px target so it hugs the glyph instead of floating in the
   card's corner. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:focus-visible {
	outline: 2px solid var(--sa-accent);
	outline-offset: -8px;
	border-radius: 6px;
}

/* SAVED: the outline fills. This is the one state a customer has to read at
   a glance down a row of cards, and it is why the glyph had to stop being
   an icon font. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.active {
	color: var(--sa-accent);
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.active .sfw-heart {
	fill: currentColor;
}

/* THE PRESS. A spring on the glyph, which is motion rather than a shape.
   Applied by wishlist-card.js, which removes the class 600ms later so the
   next press can restart it. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.is-sfw-pop .sfw-heart {
	animation: sfWishPop .42s cubic-bezier(.34, 1.56, .64, 1);
}

/* A MOUSE IS STILL OVER THE CONTROL AT THE MOMENT OF THE CLICK, so the
   plain keyframes would run 1 -> 1.32 -> 1 and then snap back up to the
   hover's 1.12 the instant they finished. This set starts and ends where
   the hover leaves it. A touch user never hovers and gets the plain one. */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.is-sfw-pop:hover .sfw-heart,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.is-sfw-pop:focus-visible .sfw-heart {
	animation-name: sfWishPopHover;
}

@keyframes sfWishPop {
	0%   { transform: scale(1); }
	38%  { transform: scale(1.32); }
	100% { transform: scale(1); }
}

@keyframes sfWishPopHover {
	0%   { transform: scale(1.12); }
	38%  { transform: scale(1.42); }
	100% { transform: scale(1.12); }
}

@media (prefers-reduced-motion: reduce) {
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a .sfw-heart {
		transition: fill .18s ease;
	}
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:hover .sfw-heart,
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a:focus-visible .sfw-heart {
		transform: none;
	}
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish a.is-sfw-pop .sfw-heart {
		animation: none;
	}
}


/* ---- 9f. THE LAST OF THE OLD CARD, FOUND ON A PHONE ----------------
 *
 * Three leftovers the desktop happened to hide. Measured at 375 against
 * the archive: card 323 against 279, the text indented twice, and the
 * heart at 24/24 where the archive puts it at 16/16.
 *
 *   padding-inline   the old design gutted its text with PADDING as
 *                    well as margin; design B uses margin alone, so the
 *                    two stacked and the text sat 14px further in.
 *   min-height       the old card had one. With it the card is taller
 *                    than its content, the price block's `margin: auto`
 *                    eats the difference -- it computed 21.7px against
 *                    the archive's 0 -- and the card runs 44px long.
 *                    THAT AUTO MARGIN IS WHY THE DESKTOP LOOKED RIGHT:
 *                    it absorbs whatever is spare, so a card that is
 *                    too tall still ends its price row at the bottom.
 *   the heart        16/16 on a phone, which is the archive's own
 *                    offset at this width.
 *
 * All three are cleared at every width; only the heart's offset is
 * breakpointed, because only it differs between them.
 * ------------------------------------------------------------- */
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product {
	min-height: 0;
}

body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .wp-block-post-terms,
body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product h3.wp-block-post-title {
	padding-inline: 0;
}

@media (max-width: 760px) {
	body.single-product .sf-pdp__editorial ul.wc-block-product-template li.wc-block-product .sf-shop__wish {
		top: 16px;
		right: 16px;
	}
}
