/* =============================================================
 * SUPERFLY — THE CART PAGE
 * Design B ("order sheet"), chosen by the operator 2026-11-18 from
 * three proposals built at docs/home-concepts/cart-live/. That
 * harness is still there and still loads the real WooCommerce block
 * stylesheets; it is where this was tuned.
 *
 * It replaces design H ("Your garage"), which had been on the page
 * since 2026-09-30 and which — see below — had not actually been
 * RENDERING for some time.
 *
 * Three parts, only one of which is this file:
 *   page 8's Elementor widget   the masthead and the strip
 *   assets/js/cart.js           the list head, the pager, the fit
 *                               note and the foot
 *   this file                   everything else
 *
 *
 * WHY DESIGN H STOPPED WORKING, because this is the whole reason
 * there is a new design at all and it must not happen again.
 *
 * cart.css used to declare its seven tokens on `.sf-cart-page` —
 * a class that ONLY templates/page-cart.html puts on the page.
 * Page 8 carries `_wp_page_template = page-full-width` and is an
 * Elementor page, and either of those alone bypasses that template.
 * So the class was absent, and an unresolved var() is INVALID AT
 * COMPUTED-VALUE TIME, which makes the property `unset` — it does
 * NOT fall back to a previous rule. Forty declarations went with
 * it. Measured on the live page 2026-11-18:
 *
 *   row border-bottom   none       (should be a hairline)
 *   summary background  transparent   (should be a card)
 *   quantity border     none
 *   line total font     Archivo    (should be Chakra Petch)
 *   checkout button     transparent   (should be magenta)
 *
 * Every selector still MATCHED, which is why it read as messy
 * rather than unstyled: the real layout with every colour, rule,
 * panel and number face knocked out of it.
 *
 * SO THE TOKENS ARE ON `body.woocommerce-cart` NOW. WooCommerce
 * puts that class there itself and no template or page-builder
 * choice can take it away. DO NOT MOVE THEM TO A WRAPPER, however
 * tidy it looks — that is the bug, not a style.
 *
 *
 * TYPE RULES, carried from design H and still true:
 *   - Chakra Petch for NUMBERS. Never for the word "subtotal".
 *   - Labels and copy in sentence-case Archivo.
 *   - Magenta on the checkout button and the per-unit price.
 *   - Hairlines, not boxes.
 *
 * Class names are WooCommerce's own; a rename in a future release
 * will quietly undo parts of this.
 *
 * SPECIFICITY, and it is not optional here. WooCommerce ships its
 * row rules as five-class selectors with an element in them —
 * (0,5,1) — e.g.
 *
 *   .wc-block-cart table.wc-block-cart-items
 *     :not(.wc-block-mini-cart-items):not(:last-child)
 *     .wc-block-cart-items__row
 *
 * A rule written as `body.woocommerce-cart .wc-block-<thing>` is
 * (0,2,1) and loses however late it appears. Several rules below
 * therefore repeat their chain. THE TEST IS THE COMPUTED VALUE,
 * never the stylesheet: walk document.styleSheets for rules that
 * both match the element and declare the property.
 * ============================================================= */


/* -------------------------------------------------------------
 * 1. TOKENS AND THE PAGE SURFACE
 * ------------------------------------------------------------- */
body.woocommerce-cart {
	--sf-ink:    #f2f2f4;
	--sf-line:   rgba(242, 242, 244, .12);
	--sf-muted:  rgba(242, 242, 244, .62);
	--sf-faint:  rgba(242, 242, 244, .38);
	--sf-page:   #101014;
	--sf-panel:  #0d0d10;
	--sf-accent: var(--wp--preset--color--accent-1, #ec1e79);
	--sf-num:    "Chakra Petch", "Archivo", sans-serif;
	--sf-body:   "Archivo", "Inter", system-ui, sans-serif;
	--sf-title:  "Inter", system-ui, -apple-system, sans-serif;

	/* THE SITE GUTTER, not a local one. style.css has carried this
	   exact ramp as --sf-gutter since 2026-11-17 and every page reads
	   it; the fallback repeats the expression so a missing token
	   degrades to the right number rather than to zero. */
	--sf-cart-gutter: var(--sf-gutter, clamp(20px, 4.2vw, 80px));

	/* THE FIXED SOCIAL RAIL. .sfsr is 46px wide (40 below 782px) at
	   z-index 90 down the left edge of every page. 58px is the house
	   clearance — .sfidx, .sfcg, .sfbw and .sfdw all use it — and the
	   max() unwinds to 0 on a desktop, where the gutter already
	   clears it. CHECK IT BY MEASURING THE TEXT with a Range: the
	   clearance is padding inside the box, so a rect on the element
	   still reads 20 and looks like a collision after the fix. */
	--sf-cart-rail: max(0px, calc(58px - var(--sf-cart-gutter)));

	/* THE NAVBAR IS A FLOATING PILL AND IS IN FLOW. <header> reserves
	   66px, then navbar.css pushes the bar down by its own gutter, so
	   the bar PAINTS to about 90px while the flow it reserves ends at
	   66 — anything starting at the flow edge is 24px under the glass.
	   A literal, not a var() read across files: navbar.css declares
	   --sf-navbar-gutter on :root and a cross-file read resolves by
	   load order. CHANGE WITH navbar.css OR NEITHER. */
	--sf-cart-nav: 24px;
}

/* attachment:fixed is what this rule buys over the shop-wide carbon
   in woocommerce.css — the weave stays put while the page scrolls,
   where the shop-wide copy scrolls with it. The hexes have matched
   since 2026-11-16; the attachment does not. Do not delete it as a
   duplicate. */
body.woocommerce-cart {
	background-color: var(--sf-page);
	background-image:
		repeating-linear-gradient( 45deg, rgba(255, 255, 255, .025) 0 2px, transparent 2px 4px),
		repeating-linear-gradient(-45deg, rgba(0, 0, 0, .35)        0 2px, transparent 2px 4px);
	background-attachment: fixed;
}


/* -------------------------------------------------------------
 * 2. THE FRAME
 *
 * FULL BLEED INSIDE THE GUTTER, like every other page since the
 * 2026-11-17 uncap set --sf-measure to none. Design H was pitched
 * for an 1180px measure and kept it after that change, which is
 * half of why the band sat oddly on a wide screen.
 * ------------------------------------------------------------- */
body.woocommerce-cart .sf-cart-wrap {
	padding-top:    calc(clamp(40px, 3.6vw, 64px) + var(--sf-cart-nav));
	padding-bottom: clamp(48px, 6vw, 96px);
	padding-inline: var(--sf-cart-gutter);
}

/* TWO ELEMENTS CARRY .wc-block-cart, one inside the other — the
   outer .wp-block-woocommerce-cart and the inner
   .wc-block-components-sidebar-layout. A rule written for
   ".wc-block-cart" alone lands on both and doubles its padding.
   That cost an hour on the checkout page; the frame belongs to the
   outer one and the columns to the inner one. */
body.woocommerce-cart .wp-block-woocommerce-cart {
	max-width: none;
	margin: 0;
	padding: 0;
}

/* THE SIDEBAR LAYOUT IS A GRID, AND THAT IS THE OTHER HALF OF THE
   RESPONSIVE COMPLAINT. WooCommerce's own layout is a flex row
   holding the summary at a FIXED 300px against a flexible main —
   measured on the live page at 1353px: main 890, sidebar 300. So
   every pixel a wider screen adds goes to the items column and the
   summary stays a narrow strip. An explicit second track scales
   both. */
body.woocommerce-cart .wc-block-cart.wc-block-components-sidebar-layout {
	display: grid;
	grid-template-columns: minmax(0, 1fr) clamp(300px, 26vw, 420px);
	gap: clamp(24px, 3vw, 56px);
	align-items: start;
	max-width: none;
	margin: 0;
	padding: 0;
}
body.woocommerce-cart .wc-block-cart__main,
body.woocommerce-cart .wc-block-cart__sidebar {
	width: auto;
	max-width: none;
	flex: none;
	padding: 0;
}

/* ONE BREAKPOINT SET, NOT THREE. Design H broke at 1080, 620 and
   520 and the rows, the summary and the strip each changed at a
   different one, which is why the page read as three layouts
   disagreeing. The summary drops under the items at 960 and the row
   restacks at 680, and nothing else moves. */
@media (max-width: 960px) {
	body.woocommerce-cart .wc-block-cart.wc-block-components-sidebar-layout {
		grid-template-columns: minmax(0, 1fr);
	}
}


/* -------------------------------------------------------------
 * 3. THE MASTHEAD
 *
 * IT IS THE PRODUCT-CATEGORY ARCHIVE'S TITLE, VALUE FOR VALUE
 * (operator, 2026-11-18: "match with product category page title ..
 * 2 line"). Read off the SERVED shop-archive.css, not out of
 * CLAUDE.md and not out of that file's own comments — those still
 * argue at length for Archivo Black, and the face was changed under
 * them without the note being updated. What /product-category/
 * brakes/ actually computes:
 *
 *   font-family    Inter, system-ui, -apple-system, sans-serif
 *   font-weight    700
 *   font-size      30 / 48 / 60 / 72 / 100
 *                  at base / 768 / 1024 / 1280 / 1900
 *   line-height    1
 *   letter-spacing -0.075em
 *   text-transform uppercase
 *
 * THE TOP STEP IS 100, NOT 112. 112 is the home page's number, and
 * the two would have differed at 1900 only — exactly the kind of
 * difference that survives a review. SIX stylesheets carry these as
 * literals rather than one shared token, because a :root token
 * declared in a conditionally loaded sheet and read from another
 * resolves by load order and fails silently. CHANGE THEM ALL OR
 * NONE.
 *
 * THE TWO LINES ARE THE ARCHIVE'S ARRANGEMENT TOO: a solid white
 * label over a swept subject — "KNOW YOUR / BRAKES." there, "YOUR /
 * GARAGE." here. The full stop is theirs as well, and it is swept
 * with the word.
 * ------------------------------------------------------------- */
body.woocommerce-cart .sf-cart-mast {
	padding-left: var(--sf-cart-rail);
	margin-bottom: clamp(28px, 3.2vw, 52px);
}
body.woocommerce-cart .sf-cart-mast__eyebrow {
	margin: 0 0 14px;
	font-family: var(--sf-num);
	font-size: 11px;
	font-weight: 600;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--sf-accent);
}
body.woocommerce-cart .sf-cart-mast__title {
	margin: 0;
	font-family: var(--sf-title);
	font-weight: 700;
	font-size: 30px;
	line-height: 1;
	letter-spacing: -.075em;
	text-transform: uppercase;
	color: var(--sf-ink);
}
@media (min-width:  768px) { body.woocommerce-cart .sf-cart-mast__title { font-size:  48px } }
@media (min-width: 1024px) { body.woocommerce-cart .sf-cart-mast__title { font-size:  60px } }
@media (min-width: 1280px) { body.woocommerce-cart .sf-cart-mast__title { font-size:  72px } }
@media (min-width: 1900px) { body.woocommerce-cart .sf-cart-mast__title { font-size: 100px } }

/* THE LABEL LINE. Solid ink, no gradient — the archive's ::before
   does exactly this, and its own note warns not to make it
   transparent "for consistency", because it would immediately start
   showing the sweep and stop being white. */
body.woocommerce-cart .sf-cart-mast__lead {
	display: block;
	color: var(--sf-ink);
}

/* THE SWEPT LINE — section 2's sheen, the same one the archive
   title, .sfcg__word and .sfop__line--accent carry: ink -> magenta
   -> ink clipped to the glyphs and looping, so it reads as a light
   passing through the word rather than as a second colour.

   BOTH background-clip LONGHANDS OR BLINK PAINTS A SOLID MAGENTA
   BAND WITH INVISIBLE TYPE INSIDE IT. Four other bands in this
   theme record the same trap.

   THE TEST IS THE PAINTED PIXELS — A SCREENSHOT — never the
   computed value, which reads correct in the broken state.

   width: fit-content IS REQUIRED AND IS NOT SET ON THE ARCHIVE.
   This span is display:block, so without it the background's
   positioning area is the whole masthead measure and the sweep
   spreads across the page instead of across the word — the exact
   failure home-opening.css records for .sfop__line--accent. The
   archive gets away without it only because its gradient sits on an
   h1 holding BOTH lines, where shrink-wrapping would buy nothing.

   The negative margin and matching padding give the last glyph the
   room the background box would otherwise clip. */
body.woocommerce-cart .sf-cart-mast__word {
	display: block;
	width: fit-content;
	color: transparent;
	background-image: linear-gradient(90deg,
		var(--sf-ink)    0%,
		var(--sf-accent) 48%,
		var(--sf-ink)   100%);
	background-size: 220% 220%;
	-webkit-background-clip: text;
	background-clip: text;
	animation: sfSheen 5s ease infinite;
	margin-right: -.12em;
	padding-right: .12em;
}

/* The archive's own keyframes, unchanged. Against a 220% image a
   background-position percentage is a percentage of (area - image),
   so these two stops are what carry the light across the glyphs.
   CHANGE THE 220% AND YOU MUST REDO THEM. */
@keyframes sfSheen {
	0%   { background-position: 10% 0 }
	50%  { background-position: 91% 100% }
	100% { background-position: 10% 0 }
}


/* -------------------------------------------------------------
 * 4. THE LIST HEAD, THE FOOT AND THE STRIP
 * The first two are injected by cart.js; the strip is markup.
 * ------------------------------------------------------------- */
body.woocommerce-cart .sf-cart-lhead {
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	gap: 16px;
	margin: 0 0 18px;
}
body.woocommerce-cart .sf-cart-lhead h2 {
	margin: 0;
	padding: 0;
	font-family: var(--sf-num);
	font-size: 11px;
	font-weight: 600;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--sf-faint);
}
body.woocommerce-cart .sf-cart-lhead__count {
	margin: 0;
	font-family: var(--sf-num);
	font-size: 12px;
	font-weight: 600;
	letter-spacing: .04em;
	color: var(--sf-muted);
}


/* -------------------------------------------------------------
 * 5. THE LINES
 *
 * WooCommerce renders a <table>. It is driven as a grid instead,
 * which is what lets the row restack on a phone — a <td> cannot be
 * re-ordered, a grid item can.
 * ------------------------------------------------------------- */
body.woocommerce-cart .wc-block-cart-items {
	display: block;
	width: 100%;
	margin: 0;
	border: 0;
	border-spacing: 0;
	background: none;
}
body.woocommerce-cart .wc-block-cart-items thead,
body.woocommerce-cart .wc-block-cart-items caption,
body.woocommerce-cart .wc-block-cart-items__header { display: none }
body.woocommerce-cart .wc-block-cart-items tbody { display: block; counter-reset: sf-row }

body.woocommerce-cart .wc-block-cart-items__row td {
	display: block;
	padding: 0;
	border: 0;
	background: none;
	vertical-align: top;
}

/* THE ROW NUMBER IS ABSOLUTE, NOT A GRID ITEM, AND THAT IS NOT A
   style choice. A ::before on a grid container IS a grid item, so
   as a fourth item it shifted image/product/total one column right
   and the placement in section 6 then put the total where the
   product was, leaving a fourth IMPLICIT track. Measured at 1024px
   during the build: `34px 128px 344.675px 13.4125px`, that last
   track being the collapsed remainder. */
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row {
	counter-increment: sf-row;
	position: relative;
	display: grid;
	align-items: start;
	grid-template-columns: 128px minmax(0, 1fr) auto;
	gap: 0 24px;
	width: 100%;
	margin: 0;
	padding: 26px 0 26px 34px;
	border: 0;
	border-bottom: 1px solid var(--sf-line);
	background: none;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:first-child {
	padding-top: 0;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row::before {
	content: "0" counter(sf-row);
	position: absolute;
	left: 0;
	top: 30px;
	font-family: var(--sf-num);
	font-size: 11px;
	font-weight: 600;
	letter-spacing: .1em;
	color: var(--sf-accent);
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:first-child::before {
	top: 4px;
}

/* NO HAIRLINE UNDER THE LIST (operator, 2026-11-18: "i want you
   remove 1 line .. cause the line too many in UI"). The last row's
   own border closed the list and .sf-cart-foot's border-top then
   drew a second rule 54px under it, so this zeroed the row's.

   THE FOOT ITSELF WENT ON 2026-11-19, so the list now closes with
   NO rule at all rather than one. That follows the same "too many
   lines" direction; put a border-bottom back on the last row if it
   ever reads as unfinished.

   IT TAKES (0,5,2). Woo draws the separator with

     .wc-block-cart table.wc-block-cart-items
       :not(.wc-block-mini-cart-items):not(:last-child)
       .wc-block-cart-items__row

   — five classes and an element, the two :not()s each counting as
   their argument. A reset at (0,5,0) loses by exactly one element
   selector, so `tbody` is in the chain to clear it rather than tie.

   IT LOST AT 768 AND WON AT 1440 DURING THE BUILD, which looked
   impossible since specificity does not depend on viewport: Woo
   ships that declaration twice, once plain and once width-gated,
   and only the weaker copy was in play at the wider size. A rule
   that works at the width you happen to be testing is not a rule
   that works.

   THE TELL WAS THE COLOUR — the border computed
   rgba(242,242,244,.2) where --sf-line is .12, so the winner was
   neither of ours. */
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items tbody .wc-block-cart-items__row:last-child {
	border-bottom: 0;
}

/* a row the pager has hidden. Visual only — the block's totals
   still count it. */
body.woocommerce-cart .wc-block-cart-items__row.sf-cart-off {
	display: none;
}

/* THE PHOTO TILE. 53 of the 100 published products have no featured
   image, so the placeholder is a first-class state: house carbon
   plus a magenta bloom, the convention .sfcg and .sfbr already use.
   Never leave it an empty box — an empty box reads as a failed
   request. */
body.woocommerce-cart .wc-block-cart-item__image a {
	display: block;
	position: relative;
	aspect-ratio: 1;
	overflow: hidden;
	border-radius: 8px;
	background: #16161a;
}
body.woocommerce-cart .wc-block-cart-item__image img {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
	margin: 0;
	border-radius: 0;
}
/* WOOCOMMERCE'S OWN PLACEHOLDER IS AN <img> WITH NO CLASS, so it is
   matched on its src — checked on the live page rather than
   assumed, where it renders as

     <img src=".../woocommerce-placeholder-300x300.webp" width="80">

   with an empty class attribute. The anchor-with-no-img selector is
   kept beside it because that is what the proposal harness renders
   and what a future WooCommerce could render instead; neither alone
   covers both. A browser without :has() shows WooCommerce's grey
   logo tile, which is the old behaviour rather than a broken one. */
body.woocommerce-cart .wc-block-cart-item__image a:not(:has(img)),
body.woocommerce-cart .wc-block-cart-item__image a:has(img[src*="woocommerce-placeholder"]) {
	background-color: var(--sf-panel);
	background-image:
		radial-gradient(120% 110% at 78% 12%, rgba(236, 30, 121, .34) 0%, rgba(236, 30, 121, .10) 48%, rgba(236, 30, 121, 0) 74%),
		repeating-linear-gradient( 45deg, rgba(255, 255, 255, .025) 0 2px, transparent 2px 4px),
		repeating-linear-gradient(-45deg, rgba(0, 0, 0, .35)        0 2px, transparent 2px 4px);
}
body.woocommerce-cart .wc-block-cart-item__image img[src*="woocommerce-placeholder"] {
	opacity: 0;
}
body.woocommerce-cart .wc-block-cart-item__image a:has(img[src*="woocommerce-placeholder"])::after {
	content: "No photo";
	position: absolute;
	inset: auto 0 8px;
	text-align: center;
	font-family: var(--sf-num);
	font-size: 8.5px;
	font-weight: 600;
	letter-spacing: .14em;
	text-transform: uppercase;
	color: rgba(242, 242, 244, .72);
}

body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-components-product-name {
	display: block;
	/* THE PRODUCT CARD'S TYPE, VALUE FOR VALUE (operator, 2026-11-19:
	   "i think its too big .. please make it small size .. like font in
	   single product page"). Read off the LIVE related-products card on
	   a product page, not out of shop-archive.css, whose comments still
	   argue for a face that was changed under them:

	     Inter / 700 / 13px / line-height 1.42 / .02em / uppercase

	   It was Inter 700 clamp(15px, 1.3vw, 19px) at -.02em/1.24, which
	   measured 18.72px at 1440. The clamp is gone on purpose: a card
	   name does not ramp with the viewport either, and a row that is
	   one of a list should not be the loudest thing on the page.

	   FIVE LITERALS AGAINST .sf-shop__grid's CARD, not a shared token,
	   the decision this project records throughout: a custom property
	   substitutes at computed-value time on the element where it is
	   DECLARED, so a :root token read across stylesheets resolves by
	   load order and fails silently. CHANGE BOTH FILES OR NEITHER. */
	font-family: var(--sf-title);
	font-weight: 700;
	font-size: 13px;
	text-transform: uppercase;
	letter-spacing: .02em;
	line-height: 1.42;
	color: var(--sf-ink);
	text-decoration: none;
	transition: color .2s;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-components-product-name:hover {
	color: var(--sf-accent);
}

/* THE PER-UNIT PRICE IS MAGENTA — from the reference the operator
   supplied, and cart.css has carried it since 2026-09-30. It is the
   only magenta on the row, which is what keeps the LINE total
   reading as the number that matters. */
body.woocommerce-cart .wc-block-cart-item__prices .wc-block-components-product-price__value {
	font-family: var(--sf-num);
	font-weight: 600;
	font-size: 12.5px;
	letter-spacing: .02em;
	color: var(--sf-accent);
}

/* VARIATION CHIPS. WooCommerce prints these as a <ul> of name/value
   pairs. As plain text they are the noisiest thing in the row; as
   pills they read as the spec they are. */
body.woocommerce-cart .wc-block-components-product-metadata { margin: 0 }
body.woocommerce-cart .wc-block-components-product-metadata ul {
	display: flex;
	flex-wrap: wrap;
	gap: 6px;
	margin: 0;
	padding: 0;
	list-style: none;
}
body.woocommerce-cart .wc-block-components-product-metadata li {
	margin: 0;
	padding: 4px 9px;
	border: 1px solid var(--sf-line);
	border-radius: 999px;
	font-family: var(--sf-body);
	font-size: 10.5px;
	line-height: 1.3;
	color: var(--sf-muted);
	white-space: nowrap;
}
body.woocommerce-cart .wc-block-components-product-details__name {
	color: var(--sf-faint);
	font-weight: 400;
}
body.woocommerce-cart .wc-block-components-product-details__value {
	font-family: var(--sf-num);
	font-weight: 600;
	letter-spacing: .03em;
	color: var(--sf-ink);
}

/* THE STEPPER. WooCommerce's own is three borderless controls that
   read as text.

   `flex`, not `inline-flex`, and the difference is not a choice:
   this is a flex ITEM of .wc-block-cart-item__quantity and a flex
   item's display is BLOCKIFIED, so inline-flex computes to flex
   anyway. Written as flex so the computed value matches the file
   and nobody goes hunting for the rule that "beat" it. */
body.woocommerce-cart .wc-block-cart-item__quantity {
	display: flex;
	align-items: center;
	gap: 16px;
	margin: 0;
	padding: 0;
	border: 0;
}
body.woocommerce-cart .wc-block-components-quantity-selector {
	display: flex;
	align-items: stretch;
	min-width: 0;
	margin: 0;
	border: 1px solid var(--sf-line);
	border-radius: 8px;
	background: rgba(255, 255, 255, .02);
	overflow: hidden;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-components-quantity-selector {
	width: auto;
	max-width: none;
}
body.woocommerce-cart .wc-block-components-quantity-selector::after { display: none }
body.woocommerce-cart .wc-block-components-quantity-selector__button {
	width: 34px;
	min-width: 34px;
	height: 34px;
	padding: 0;
	border: 0;
	background: none;
	font-family: var(--sf-body);
	font-size: 15px;
	line-height: 1;
	color: var(--sf-muted);
	opacity: 1;
	cursor: pointer;
	transition: color .18s, background-color .18s;
}
body.woocommerce-cart .wc-block-components-quantity-selector__button:hover {
	color: var(--sf-ink);
	background: rgba(255, 255, 255, .05);
}
body.woocommerce-cart .wc-block-components-quantity-selector__input {
	width: 40px;
	min-width: 40px;
	height: 34px;
	padding: 0;
	border: 0;
	border-inline: 1px solid var(--sf-line);
	background: none;
	text-align: center;
	color: var(--sf-ink);
	-moz-appearance: textfield;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-components-quantity-selector__input {
	font-family: var(--sf-num);
	font-size: 13px;
	font-weight: 600;
}
body.woocommerce-cart .wc-block-components-quantity-selector__input::-webkit-outer-spin-button,
body.woocommerce-cart .wc-block-components-quantity-selector__input::-webkit-inner-spin-button {
	-webkit-appearance: none;
	margin: 0;
}

body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__remove-link {
	padding: 0;
	border: 0;
	background: none;
	font-family: var(--sf-num);
	font-size: 10px;
	font-weight: 600;
	letter-spacing: .14em;
	text-transform: uppercase;
	color: var(--sf-faint);
	text-decoration: none;
	cursor: pointer;
	transition: color .2s;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__remove-link:hover {
	color: var(--sf-accent);
	text-decoration: none;
}

/* WOOCOMMERCE RENDERS THIS AS A 24px TRASH ICON, NOT AS TEXT —
   checked on the live page, where the button's only child is an
   <svg> and its textContent is empty. The design the operator
   approved shows a text link, so the icon is hidden and the words
   are drawn instead.

   THE BUTTON KEEPS ITS OWN ACCESSIBLE NAME either way: it carries
   aria-label="Remove <product name> from cart", which is better
   than the visible text and which generated content cannot
   override. That is the only reason doing this in CSS is
   acceptable — generated content is not selectable and not
   translatable, so a control whose real name depended on it would
   be a regression.

   The way back to WooCommerce's icon is deleting these two rules. */
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__remove-link svg {
	display: none;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__remove-link::after {
	content: "Remove item";
}

/* THE LINE TOTAL IS THE CARD'S PRICE (same instruction, same day):
   Inter / 700 / 16px, which is .sf-shop__grid's .sf-shop__priceval.
   It was Chakra Petch 700 clamp(17px, 1.5vw, 22px), 21.6px at 1440 —
   bigger than the product's own name, which is what made the row
   read as a price list with a picture beside it.

   TABULAR FIGURES ARE KEPT AND THE CARD HAS NONE, which is the one
   deliberate difference. A card shows one price; here they stack into
   a COLUMN, and without it the decimals walk. Inter carries the
   feature, so this costs nothing. */
body.woocommerce-cart .wc-block-cart-item__total .wc-block-components-product-price__value {
	font-family: var(--sf-title);
	font-weight: 700;
	font-size: 16px;
	letter-spacing: normal;
	font-variant-numeric: tabular-nums;
	color: var(--sf-ink);
}


/* -------------------------------------------------------------
 * 6. WHERE THE ROW'S PIECES GO
 *
 * WOOCOMMERCE PLACES THEM EXPLICITLY, AND EXPLICIT PLACEMENT IS NOT
 * SOMETHING AUTO-FLOW CAN ROUTE AROUND. Measured at 390px during
 * the build:
 *
 *   .wc-block-cart-item__product   grid-column 2/4   grid-row 1
 *   .wc-block-cart-item__total                       grid-row 1
 *   .wc-block-cart-item__quantity  grid-area 2 / 1   (in the wrap)
 *
 * The first two put the line total and the product name in the SAME
 * CELL — the total printed straight over the title. The third
 * pulled the stepper above the price and the chips, so the row read
 * name / stepper / price / chips against a DOM order of name /
 * price / chips / stepper.
 *
 * None of it reports anything: no overflow, no console, and every
 * rule of ours computing exactly what it says.
 *
 * The wrap's children are PINNED rather than reset to auto, so the
 * reading order is a decision and not a by-product of DOM order:
 * name, what one costs, what it is, then how many. The stepper last
 * is deliberate — it is the only control in the row, and a control
 * belongs under the facts it acts on.
 * ------------------------------------------------------------- */
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row > .wc-block-cart-item__image   { grid-column: 1; grid-row: 1 }
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row > .wc-block-cart-item__product { grid-column: 2; grid-row: 1 }
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row > .wc-block-cart-item__total   { grid-column: 3; grid-row: 1; align-self: start; text-align: right; white-space: nowrap }

body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__wrap {
	display: grid;
	gap: 12px;
	min-width: 0;
}
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__wrap > *       { grid-column: 1 }
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-components-product-name     { grid-row: 1 }
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__prices           { grid-row: 2 }
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-components-product-metadata { grid-row: 3 }
body.woocommerce-cart .wc-block-cart table.wc-block-cart-items .wc-block-cart-items__row .wc-block-cart-item__quantity         { grid-row: 4 }


/* -------------------------------------------------------------
 * 7. PAGES — injected by cart.js
 * ------------------------------------------------------------- */
/* THE SHOP'S PAGER, VALUE FOR VALUE (operator, 2026-11-20: "i want
   the button standardize with design button that exist in page
   shop"). Copied from shop-archive.css section 7 as LITERALS — that
   file only loads on shop pages, so its --sa-* tokens do not exist
   here, and a token read across stylesheets resolves by load order
   and fails silently. CHANGE BOTH FILES OR NEITHER.

     number      38px plate, 6px corners, #16161a, a 1px ring at .14
                 and a soft emboss; Chakra Petch 600 12px .06em, grey
     current     solid accent, white, pressed in, a pink glow
     prev/next   the same plate with words, 10px 700 .14em uppercase,
                 and a drawn chevron; they turn pink on hover

   It was 34px outlined squares with a tinted current page and greyed
   arrows at both ends. The row is CENTRED now, as the shop's is. */
body.woocommerce-cart .sf-cart-pager {
	display: flex;
	align-items: center;
	justify-content: center;
	gap: 8px;
	flex-wrap: wrap;
	margin: 28px 0 0;
}
body.woocommerce-cart .sf-cart-pager:empty { display: none }
body.woocommerce-cart .sf-cart-pager button {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	box-sizing: border-box;
	min-width: 38px;
	height: 38px;
	margin: 0;
	padding: 0 10px;
	border: 0;
	border-radius: 6px;
	background: #16161a;
	box-shadow: 0 0 0 1px rgba(242, 242, 244, .14),
	            -2px -2px 6px rgba(255, 255, 255, .022),
	             3px 3px 8px rgba(0, 0, 0, .26);
	font-family: var(--sf-num);
	font-size: 12px;
	font-weight: 600;
	letter-spacing: .06em;
	color: #878787;
	cursor: pointer;
	transition: color .22s ease, box-shadow .22s ease;
}
body.woocommerce-cart .sf-cart-pager button:hover {
	color: var(--sf-ink);
	box-shadow: -3px -3px 8px rgba(255, 255, 255, .022),
	             4px 4px 10px rgba(0, 0, 0, .26);
}
body.woocommerce-cart .sf-cart-pager button[aria-current="true"] {
	color: #fff;
	background: var(--sf-accent);
	box-shadow: inset 2px 2px 6px rgba(0, 0, 0, .34),
	            0 4px 14px rgba(236, 30, 121, .34);
	cursor: default;
}
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev,
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next {
	gap: 8px;
	padding: 0 16px;
	font-size: 10px;
	font-weight: 700;
	letter-spacing: .14em;
	text-transform: uppercase;
}
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev { margin-right: 4px; }
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next { margin-left: 4px; }
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev:hover,
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next:hover {
	color: var(--sf-accent);
}
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev::before,
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next::after {
	content: "";
	flex: none;
	width: 14px;
	height: 14px;
	background: currentColor;
	-webkit-mask: var(--sf-chev) center / contain no-repeat;
	        mask: var(--sf-chev) center / contain no-repeat;
}
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev::before {
	--sf-chev: 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.4" stroke-linecap="round" stroke-linejoin="round"><path d="M15 5l-7 7 7 7"/></svg>');
}
body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next::after {
	--sf-chev: 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.4" stroke-linecap="round" stroke-linejoin="round"><path d="M9 5l7 7-7 7"/></svg>');
}
/* phones: the shop's own step — 32px plates, and the words on
   previous/next hidden (font-size 0 keeps them for a screen reader) */
@media (max-width: 760px) {
	body.woocommerce-cart .sf-cart-pager { gap: 6px; }
	body.woocommerce-cart .sf-cart-pager button {
		min-width: 32px;
		height: 32px;
		padding: 0 6px;
		font-size: 11.5px;
	}
	body.woocommerce-cart .sf-cart-pager .sf-cart-pager__prev,
	body.woocommerce-cart .sf-cart-pager .sf-cart-pager__next {
		width: 32px;
		padding: 0;
		margin: 0;
		gap: 0;
		font-size: 0;
		letter-spacing: 0;
	}
}


/* -------------------------------------------------------------
 * 8. THE FIT NOTE IS GONE (operator, 2026-11-20)
 *
 * It was two lines under the list — "Great builds start with the
 * right fit." over "Double-check your bike model and wheel size
 * before checkout." — on its own hairline rule. It sat between the
 * items and the summary, which on this page is the one place
 * nothing should: the ledger ends in a bar, and a paragraph in
 * that gap is a large part of why the bar read as adrift.
 *
 * The builder went out of cart.js in the same pass, so nothing
 * renders `.sf-cart-note` any more and these rules went with it
 * rather than being left dead. Both halves are in git.
 * ------------------------------------------------------------- */


/* -------------------------------------------------------------
 * 8b. THE CROSS-SELLS ARE OFF
 * Operator, 2026-11-18: "hide this in cart page", against a
 * screenshot of the "You may be interested in…" block.
 *
 * HIDDEN, NOT REMOVED, and that is a choice worth stating. The
 * block is `woocommerce/product-collection` with
 * `collection: woocommerce/product-collection/cross-sells`, and it
 * is written into page 8's Elementor widget. Taking it out means a
 * widget write plus a cache flush; this is one declaration, no
 * database change, and deleting the rule brings it straight back.
 *
 * WHAT IT COSTS: WooCommerce still runs the cross-sell query and
 * still renders the markup — about 543px of DOM nobody sees,
 * measured live. If that is ever worth reclaiming, delete the
 * `wp:woocommerce/product-collection` block from the widget and
 * this rule together.
 *
 * ONLY TWO PRODUCTS IN THE CATALOGUE DEFINE CROSS-SELLS AT ALL
 * (877 and 368, which point at each other), so the block was
 * invisible on most carts and this will not look like it changed
 * anything unless one of those is in the cart.
 *
 * Scoped to the cart-items block rather than to the page, so a
 * product collection added later for some other purpose is not
 * caught by it.
 * ------------------------------------------------------------- */
body.woocommerce-cart .wp-block-woocommerce-cart-items-block .wp-block-woocommerce-product-collection {
	display: none;
}


/* -------------------------------------------------------------
 * 9. THE SUMMARY
 *
 * IT IS A CARD NOW (operator, 2026-11-19: "its also too simple").
 * It was held by its left hairline alone and nothing else — which
 * was right while the rail had rows in it, and this one has two:
 * a coupon button and a total. See the note on the empty state
 * below before deciding the rail is broken.
 *
 * THE EMBOSS IS THE HOUSE PANEL, the same pair .sfdw__card, .sfcg
 * and the shop's product card carry — face a few units under the
 * page, light from the top-left, shadow to the bottom-right. Two
 * literals rather than a shared token, for the reason this file
 * already gives for --sf-cart-nav. CHANGE WITH THEM OR NEITHER.
 * ------------------------------------------------------------- */
body.woocommerce-cart .wc-block-cart__sidebar {
	position: sticky;
	/* the floating navbar paints to about 90px; this is that plus 20
	   of air, the same sum pdp-gallery.css uses, as a literal for the
	   same cross-file reason. */
	top: 110px;
	padding: clamp(20px, 1.8vw, 26px);
	border: 0;
	border-radius: 12px;
	background: var(--sf-panel);
	box-shadow:
		-4px -4px  8px rgba(255, 255, 255, .06),
		 5px  5px 12px rgba(0, 0, 0, .45);
}
body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-block {
	padding: 0;
	border: 0;
	background: none;
}
body.woocommerce-cart .wc-block-cart__totals-title {
	margin: 0 0 16px;
	padding: 0;
	font-family: var(--sf-num);
	font-size: 11px;
	font-weight: 600;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--sf-faint);
}

body.woocommerce-cart .wc-block-components-totals-coupon { margin: 0 0 4px; border: 0 }

/* A CLOSED COUPON DREW TWO HAIRLINES 4px APART (operator, 2026-11-19:
   "why if accordion coupon close , its will display two border line").
   They belong to two different elements and both are correct on their
   own — the panel button's own border-bottom at y437, and the footer
   total's border-top at y441, measured live at 1440. The 4px between
   them is .wc-block-components-totals-coupon's margin-bottom.

   IT ONLY SHOWS WHEN THE ROWS BETWEEN THEM ARE ABSENT, which is why
   it reads as a bug rather than as spacing: open the coupon and the
   form pushes them apart, and a cart with a subtotal or a shipping
   line has a row between them.

   SO THE TEST IS STRUCTURAL, NOT A WIDTH OR A STATE NAME: the coupon's
   rule is dropped only while the totals block that would sit under it
   is EMPTY and the accordion is CLOSED. Put a coupon or a shipping
   method on the cart and both rules come back on their own, with
   nothing to deploy. A browser without :has() keeps the pair, which
   is the right way round for a cosmetic fix.

   THE TOTAL'S RULE IS THE ONE DROPPED, NOT THE COUPON'S, AND THAT IS
   FORCED BY THE SPEC RATHER THAN CHOSEN. Dropping the coupon's means
   looking FORWARD from it at an empty block, which is the one thing
   :has() may not do:

     :has( + .totals-block:not(:has(*)) )     <- INVALID, and silent

   :has() CANNOT BE NESTED INSIDE :has(), so the whole selector is
   thrown away — the stylesheet still parses, the rule simply is not
   there, and the computed border-bottom reads 0.8px with the file
   plainly saying 0. Chrome only admits it if you ask: el.matches()
   throws "is not a valid selector" on it. :not(:has(*)) on its own
   is fine; it is the nesting that is forbidden.

   So the condition is read from the element that comes AFTER, where
   a plain sibling combinator reaches it, and the coupon keeps the
   hairline. The two sit 4px apart, so which one survives is not
   visible — only that one of them does. */
body.woocommerce-cart
  .wp-block-woocommerce-cart-order-summary-block:has(
    .wc-block-components-panel__button[aria-expanded="false"])
  .wp-block-woocommerce-cart-order-summary-totals-block:not(:has(*))
  + .wc-block-components-totals-wrapper .wc-block-components-totals-footer-item {
	border-top: 0;
}

/* an empty pager still spent its 20px top margin — cart.js clears the
   <nav> and returns when there is only one page, rather than removing
   it, so the element is always there. */
body.woocommerce-cart .sf-cart-pager:empty { margin: 0 }
body.woocommerce-cart .wc-block-components-panel__button {
	display: flex;
	align-items: center;
	justify-content: space-between;
	width: 100%;
	padding: 12px 0;
	border: 0;
	border-bottom: 1px solid var(--sf-line);
	background: none;
	font-family: var(--sf-body);
	font-size: 13px;
	color: var(--sf-muted);
	cursor: pointer;
	transition: color .2s;
}
body.woocommerce-cart .wc-block-components-panel__button:hover { color: var(--sf-ink) }

body.woocommerce-cart .wc-block-components-totals-wrapper { padding: 0; border: 0 }
body.woocommerce-cart .wc-block-components-totals-item {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	justify-content: space-between;
	gap: 4px 16px;
	margin: 0;
	padding: 11px 0;
	font-size: 13px;
}
body.woocommerce-cart .wc-block-components-totals-item__label {
	font-family: var(--sf-body);
	font-weight: 400;
	color: var(--sf-muted);
}
body.woocommerce-cart .wc-block-components-totals-item__value {
	font-family: var(--sf-num);
	font-weight: 600;
	letter-spacing: .01em;
	font-variant-numeric: tabular-nums;
	color: var(--sf-ink);
}
body.woocommerce-cart .wc-block-components-totals-item__description {
	flex: 1 0 100%;
	margin: 0;
	font-family: var(--sf-body);
	font-size: 11px;
	line-height: 1.5;
	color: var(--sf-faint);
}

/* WHY THE RAIL HAS NO SUBTOTAL ROW, AND IT IS NOT OUR MARKUP.
   Checked 2026-11-19 after the operator called the summary too
   simple. The served HTML is already correct — Woo's own
   CartOrderSummaryBlock::render() migrates the old sibling blocks
   into cart-order-summary-totals-block, and all five are there. The
   CLIENT then refuses to draw the subtotal:

     if ( ! parseFloat( total_fees ) && ! parseFloat( total_discount )
          && ! parseFloat( total_shipping ) ) return null;

   (cart-frontend.js, CART_ORDER_SUMMARY_SUBTOTAL). So a cart with no
   fee, no discount and no shipping shows ONE figure, because a
   subtotal would be the same number twice. That is deliberate and
   there is nothing here to fix.

   WHAT IS MISSING IS SHIPPING, AND IT IS A STORE SETTING, NOT CSS.
   Counted the same day: 104 published products, ZERO of them virtual,
   and ZERO shipping zones with ZERO methods — including rest-of-world.
   WC_Cart::needs_shipping() returns false when the enabled method
   count is 0, so the cart reports needs_shipping FALSE for a cart of
   rims and calipers and the whole shipping row is suppressed with it.
   Add one zone with one method and the rail fills itself: shipping
   appears, and the subtotal returns with it. */
body.woocommerce-cart .wc-block-components-totals-footer-item {
	margin-top: 4px;
	padding-top: 16px;
	border-top: 1px solid var(--sf-line);
}
body.woocommerce-cart .wc-block-components-totals-footer-item .wc-block-components-totals-item__label {
	font-family: var(--sf-body);
	font-size: 13px;
	color: var(--sf-ink);
}
body.woocommerce-cart .wc-block-components-totals-footer-item .wc-block-components-totals-item__value {
	font-family: var(--sf-num);
	font-weight: 700;
	font-size: 30px;
	line-height: 1;
	color: var(--sf-ink);
}


/* -------------------------------------------------------------
 * 10. THE BUTTON
 * Magenta, full width, and the one filled thing on the page —
 * which is what makes it the obvious next step. 4.55:1 on this
 * base, so the label stays 13px/600 or larger.
 * ------------------------------------------------------------- */
body.woocommerce-cart .wc-block-cart__submit-button,
body.woocommerce-cart .wp-block-woocommerce-proceed-to-checkout-block .wc-block-cart__submit-button {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 100%;
	min-height: 52px;
	margin: 18px 0 0;
	padding: 14px 20px;
	border: 0;
	border-radius: 10px;
	background: var(--sf-accent);
	font-family: var(--sf-num);
	font-size: 13px;
	font-weight: 700;
	letter-spacing: .14em;
	text-transform: uppercase;
	color: #fff;
	text-decoration: none;
	cursor: pointer;
	transition: filter .2s, transform .2s;
}
body.woocommerce-cart .wc-block-cart__submit-button:hover {
	filter: brightness(1.1);
	transform: translateY(-1px);
}


/* -------------------------------------------------------------
 * 11. PHONES
 * ------------------------------------------------------------- */
@media (max-width: 960px) {
	/* THE CARD STAYS ON A PHONE and the top hairline goes with it —
	   a rule across the top of a panel that already has an edge is the
	   doubled line this same section was just fixed for. Only the
	   stickiness is dropped: there is nothing beside it to stay level
	   with. */
	body.woocommerce-cart .wc-block-cart__sidebar {
		position: static;
		top: auto;
		border-top: 0;
		margin-top: 26px;
	}
}

/* The bar is built by cart.js at every width and shown only below
   680, so the script has one code path and the breakpoint lives in
   one file. THIS RULE MUST STAY ABOVE THE MEDIA QUERY: both are
   (0,2,1) and source order decides, so written after it the bar
   would be hidden at every width — which is how it was first
   shipped into this file. */
body.woocommerce-cart .sf-cart-bar { display: none }

@media (max-width: 680px) {
	/* THE ROW NUMBER GOES, and that is deliberate rather than a
	   saving: at 375px it costs 58px of the 335 available and the
	   name is the thing that needs them. */
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row {
		grid-template-columns: 84px minmax(0, 1fr);
		gap: 0 16px;
		padding: 20px 0;
	}
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row::before { display: none }

	/* THE LINE TOTAL MOVES UNDER THE NAME, not into a third column.
	   A 3-column row at 375px gives the name about 150px, which is
	   four lines of an uppercase product title. */
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row > .wc-block-cart-item__total {
		grid-column: 2;
		grid-row: 2;
		text-align: left;
		margin-top: 12px;
	}

	/* THE PINNED TOTAL AND BUTTON. On a phone the summary sits under
	   three rows, so the total and the next step are a screen and a
	   half from the thing the customer just decided. Design H had
	   nothing like it. */
	body.woocommerce-cart .sf-cart-bar {
		position: fixed;
		inset: auto 0 0;
		z-index: 80;
		display: flex;
		align-items: center;
		gap: 14px;
		padding: 12px 16px calc(12px + env(safe-area-inset-bottom));
		background: rgba(13, 13, 16, .92);
		backdrop-filter: blur(16px) saturate(140%);
		border-top: 1px solid var(--sf-line);
	}
	body.woocommerce-cart .sf-cart-bar__sum { display: grid; gap: 2px; min-width: 0 }
	body.woocommerce-cart .sf-cart-bar__label {
		font-family: var(--sf-num);
		font-size: 9.5px;
		font-weight: 600;
		letter-spacing: .14em;
		text-transform: uppercase;
		color: var(--sf-faint);
	}
	body.woocommerce-cart .sf-cart-bar__value {
		font-family: var(--sf-num);
		font-size: 19px;
		font-weight: 700;
		line-height: 1;
		color: var(--sf-ink);
	}
	body.woocommerce-cart .sf-cart-bar__go {
		flex: 1 1 auto;
		display: flex;
		align-items: center;
		justify-content: center;
		min-height: 46px;
		padding: 0 18px;
		border-radius: 10px;
		background: var(--sf-accent);
		font-family: var(--sf-num);
		font-size: 12.5px;
		font-weight: 700;
		letter-spacing: .14em;
		text-transform: uppercase;
		color: #fff;
		text-decoration: none;
	}
	/* the bar is ~70px of fixed furniture over the end of the page */
	body.woocommerce-cart .sf-cart-wrap { padding-bottom: 104px }
	/* AND THE SUMMARY'S OWN BUTTON IS THEN A DUPLICATE. Both
	   selectors are needed and the second is the one that works:
	   on this install `.wc-block-cart__payment-options` is EMPTY
	   (innerHTML length 0) and the proceed block sits directly in
	   `.wc-block-cart__sidebar`, so hiding the wrapper alone hides
	   nothing and a phone gets two checkout buttons 10px apart —
	   measured live at 390px, "Proceed to Checkout" at y=776 under
	   the bar's own "Checkout" at y=786.

	   THE HARNESS COULD NOT SHOW THIS. docs/home-concepts/cart-live
	   is hand-written markup and it nested the button inside the
	   wrapper, the way the block's own documentation implies. The
	   wrapper is kept in the selector because a WooCommerce version
	   that does fill it would then be covered too. */
	body.woocommerce-cart .wc-block-cart__payment-options,
	body.woocommerce-cart .wp-block-woocommerce-proceed-to-checkout-block { display: none }
}

@media (prefers-reduced-motion: reduce) {
	body.woocommerce-cart * { transition: none !important }
	body.woocommerce-cart .wc-block-cart__submit-button:hover { transform: none }
	/* left in ink rather than wherever `0 0` lands */
	body.woocommerce-cart .sf-cart-mast__word { animation: none; background-position: 10% 0 }
}


/* -------------------------------------------------------------
 * THE EMPTY CART
 * Added 2026-10-01. Rebuilt the same day to follow 404.css,
 * at the operator's request: "layout font style size like that".
 *
 * So every value below is 404.css's, not a new set:
 *   column      660px, centred, clamp(50px,8vw,110px) padding
 *   label       Chakra Petch 11/700, 0.22em, magenta
 *   heading     Archivo Black, clamp(24px,3vw,38px), 1.15
 *   copy        clamp(14px,1.1vw,16px)/1.75, 54ch, 68% white
 *   buttons     15px 26px, Chakra Petch 11/700, 0.16em
 *   phones      stack below 520px
 * If 404.css ever changes, change this with it — they are meant
 * to read as one page in two states, not two pages.
 *
 * WHAT WENT: the dashed box and the cart line-drawing from the
 * first version. 404.css says it plainly — "No illustration, and
 * pink used once" — and an empty cart is the same kind of moment:
 * a calm notice, not a feature. The box also fought the carbon
 * weave that body.error404 puts behind the 404.
 *
 * WHAT THIS REPLACED, all WooCommerce's own default: a sad-face
 * emoji, "Your cart is currently empty!" in Cardo (the parent
 * theme's serif), a dots separator, and four product cards whose
 * Add to cart buttons rendered #f2f2f4 ON #f2f2f4 — white text on
 * a white background, unreadable. See wordpress/cart-empty/.
 *
 * Markup: wordpress/cart-empty/empty-cart-block.html
 * ------------------------------------------------------------- */
/* The block that WooCommerce wraps the empty state in. 404.css puts
   min-height:78svh and flex centring on ITS outer element (.not-found), not
   on the column — copy only the column and you get the right type at half the
   height, with the footer riding up the screen. Measured 2026-10-01: the 404
   stood 713px tall, this stood 325px.

   svh, not vh: on a phone vh counts the area behind the browser chrome, so
   the block is taller than the screen and the buttons sit under the toolbar. */
body.woocommerce-cart .wp-block-woocommerce-empty-cart-block {
	display: flex;
	align-items: center;
	min-height: 78svh;
}

body.woocommerce-cart .sf-cart-empty {
	--text:   #f2f2f4;
	--muted:  rgba(242, 242, 244, 0.68);
	--faint:  rgba(242, 242, 244, 0.40);
	--line:   rgba(242, 242, 244, 0.12);
	--accent: #ec1e79;
	--title:  "Archivo Black", "Arial Black", sans-serif;
	--body:   "Archivo", "Inter", sans-serif;
	--label:  "Chakra Petch", "Archivo", sans-serif;

	width: 100%;
	max-width: 660px;
	margin-inline: auto;
	padding: clamp(50px, 8vw, 110px) clamp(20px, 4vw, 40px);
	color: var(--text);
	font-family: var(--body);
	text-align: center;
}

body.woocommerce-cart .sf-cart-empty *,
body.woocommerce-cart .sf-cart-empty *::before,
body.woocommerce-cart .sf-cart-empty *::after {
	box-sizing: border-box;
}

body.woocommerce-cart .sf-cart-empty__label {
	margin: 0 0 18px;
	font-family: var(--label);
	font-size: 11px;
	font-weight: 700;
	letter-spacing: 0.22em;
	text-transform: uppercase;
	color: var(--accent);
}

body.woocommerce-cart .sf-cart-empty__title {
	margin: 0 0 16px;
	font-family: var(--title);
	font-weight: 400;
	font-size: clamp(24px, 3vw, 38px);
	line-height: 1.15;
	letter-spacing: -0.005em;
	color: var(--text);
	text-transform: none;   /* 404's heading is sentence case; so is this */
}

body.woocommerce-cart .sf-cart-empty__line {
	margin: 0 auto 32px;
	max-width: 54ch;
	font-size: clamp(14px, 1.1vw, 16px);
	line-height: 1.75;
	color: var(--muted);
}

/* ---- the buttons ----
   display:flex is set here, not inherited from WordPress's core block
   stylesheet. wp-block-library does give .wp-block-buttons a flex row,
   but leaning on it means the two buttons sit on top of each other the
   day those styles are deferred — which is exactly what happened in
   preview.html before this line existed. */
body.woocommerce-cart .sf-cart-empty .wp-block-buttons {
	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	gap: 12px;
}

body.woocommerce-cart .sf-cart-empty .wp-block-button__link {
	display: inline-flex;
	align-items: center;
	padding: 15px 26px;
	border-radius: 0;
	text-decoration: none;
	font-family: var(--label);
	font-size: 11px;
	font-weight: 700;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	transition: filter 0.2s ease, border-color 0.2s ease, color 0.2s ease;
}

body.woocommerce-cart .sf-cart-empty__cta .wp-block-button__link {
	background: var(--accent);
	border: 1px solid var(--accent);
	color: #fff;
}

body.woocommerce-cart .sf-cart-empty__cta .wp-block-button__link:hover,
body.woocommerce-cart .sf-cart-empty__cta .wp-block-button__link:focus-visible {
	filter: brightness(1.12);
	color: #fff;
}

/* the second action is a way out, not a second offer — one magenta
   button per screen, the same rule 404.css follows */
body.woocommerce-cart .sf-cart-empty__cta--ghost .wp-block-button__link {
	background: none;
	border: 1px solid var(--line);
	color: var(--muted);
}

body.woocommerce-cart .sf-cart-empty__cta--ghost .wp-block-button__link:hover,
body.woocommerce-cart .sf-cart-empty__cta--ghost .wp-block-button__link:focus-visible {
	border-color: var(--accent);
	color: var(--accent);
}

/* ---- phones ---- */
@media (max-width: 520px) {
	body.woocommerce-cart .sf-cart-empty .wp-block-buttons {
		flex-direction: column;
	}

	body.woocommerce-cart .sf-cart-empty .wp-block-button__link {
		justify-content: center;
	}
}

@media (prefers-reduced-motion: reduce) {
	body.woocommerce-cart .sf-cart-empty .wp-block-button__link {
		transition: none;
	}
}


/* -------------------------------------------------------------
 * 12. THE LEDGER  (design E1, chosen 2026-11-19)
 *
 * EVERY RULE BELOW SUPERSEDES ONE ABOVE IT, and that is on purpose:
 * the sections above are left intact so deleting this block restores
 * the two-column cart exactly. Nothing here is a new element and
 * nothing was written to the database — it is CSS over WooCommerce's
 * own markup, which is why this shipped with no widget write, no
 * functions.php change and no Elementor flush.
 *
 * IT WINS ON SOURCE ORDER, NOT ON SPECIFICITY. Every selector was
 * written in docs/home-concepts/cart-redesign as
 * `body[data-cart="e"] …` and re-scoped to `body.woocommerce-cart …`,
 * which is the SAME weight — body + one class + the rest. So a rule
 * moved out of this block, or a new rule added ABOVE it, silently
 * stops applying. Keep it last in the file.
 *
 * WHAT IT IS. One column: the items are wide panels stacked down the
 * page, and the summary is a BAR under them rather than a rail beside
 * them. The rail was two rows tall — WooCommerce suppresses the
 * subtotal when it would duplicate the total, and there is no shipping
 * row because the store has no shipping method — and a rail is the
 * wrong container for two rows.
 *
 * The harness it was chosen in is docs/home-concepts/cart-redesign/,
 * which still carries the two rejected feet (E2 counter, E3 receipt)
 * and the measurements behind every number here. Read its README
 * before re-pitching any of this.
 * ------------------------------------------------------------- */

/* ---- the frame: one column ---------------------------------- */
body.woocommerce-cart .wc-block-cart.wc-block-components-sidebar-layout {
	grid-template-columns: minmax(0, 1fr);
	gap: clamp(28px, 3vw, 48px);
}

/* ---- the lines become panels -------------------------------- */
body.woocommerce-cart .wc-block-cart-items tbody {
	display: flex;
	flex-direction: column;
	gap: 12px;
}
/* BORDER-BOX, AND IT IS NOT TIDYING. The row is content-box here,
   so its 54px + 24px of padding was ADDED to a 100% table: measured
   1001px of panel in a 923px column, with the line totals clipped
   off the right edge and the summary bar visibly narrower than the
   lines above it. The live row survives this only because its
   padding is smaller than the slack. */
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row {
	box-sizing: border-box;
	grid-template-columns: 112px minmax(0, 1fr) auto;
	align-items: center;
	gap: 0 26px;
	padding: 16px 24px 16px 54px;
	border: 0;
	border-radius: 12px;
	background: #0d0d10;
	box-shadow:
		-4px -4px  8px rgba(255, 255, 255, .06),
		 5px  5px 12px rgba(0, 0, 0, .45);
	transition: box-shadow .25s;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:first-child {
	padding-top: 16px;
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:hover {
	box-shadow:
		-4px -4px  8px rgba(255, 255, 255, .08),
		 6px  6px 16px rgba(0, 0, 0, .55);
}
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row::before,
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:first-child::before {
	top: 50%;
	left: 22px;
	transform: translateY(-50%);
}
body.woocommerce-cart .wc-block-cart-item__image a { border-radius: 8px; }
body.woocommerce-cart .wc-block-cart-item__wrap {
	display: flex;
	flex-direction: column;
	gap: 6px;
}
body.woocommerce-cart .wc-block-components-product-metadata__description {
	font-size: 11.5px;
	line-height: 1.45;
	color: rgba(242, 242, 244, .5);
}
body.woocommerce-cart .wc-block-cart-item__quantity { margin-top: 4px; }
body.woocommerce-cart .wc-block-cart-item__total { align-self: center; }
body.woocommerce-cart .wc-block-cart-item__total .wc-block-components-product-price__value {
	font-size: 20px;
}

/* ---- the summary becomes a bar ------------------------------ */
/* IT IS THE SAME CARD AS A LINE, deliberately: the bar is the last
   panel in the stack rather than a different kind of object. */
body.woocommerce-cart .wc-block-cart__sidebar {
	position: static;
	top: auto;
	padding: 20px 24px;
	border-radius: 12px;
	background: #0d0d10;
	box-shadow:
		-4px -4px  8px rgba(255, 255, 255, .06),
		 5px  5px 12px rgba(0, 0, 0, .45);
}
/* THE BUTTON IS NOT INSIDE THE SUMMARY BLOCK — it is a SIBLING of
   it inside the sidebar, with an EMPTY .wc-block-cart__payment-
   options between them. A flex row on the summary block alone
   therefore leaves the button below, full width, which is what the
   first cut did. cart.css already records the same surprise from
   the other side: its phone rule has to name both selectors.

   So the bar is TWO nested rows: the sidebar holds summary +
   button, and the summary holds label + coupon + total. */
body.woocommerce-cart .wc-block-cart__sidebar {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 14px clamp(20px, 2.4vw, 36px);
}
body.woocommerce-cart .wc-block-cart__payment-options { display: none; }
/* WooCommerce gives this block a 16px bottom margin to separate it
   from the checkout button BELOW it. The button is beside it here,
   and hidden entirely on a phone, so that margin is 16px of empty
   panel under the total — measured at 390. */
/* THE BASIS IS WHAT DECIDES WHICH THING WRAPS FIRST, and at 420 the
   wrong one did. Measured at a 900px viewport: the summary was handed
   less than its three pieces need, so the TOTAL wrapped to a second
   line INSIDE it — stranded at x275 in the middle of an 809px panel —
   while the button stayed up on the first line beside the coupon.

   560 is what the summary actually measures with this cart's words:
   label 89 + coupon 139 + total 267 and two gaps. Below that the BAR
   wraps instead and the button takes its own line, which is the
   failure you want. Re-measure it if the label or the currency
   changes — this is the one number in E1 that is cart-specific.

   IT IS 700 SINCE 2026-11-20, because the coupon OPENS IN PLACE now
   (section 12c) and the summary has to hold the open field, not just
   the pill. 700 leaves the field about 280px at the narrowest width
   where it still shares line one with the button (label 89 + total
   267 + two 3vw gaps take the rest); below that, about a 1090px
   window, the button takes its own line, open OR closed — so opening
   the coupon can never be what pushes it down. 640 was tried first
   and squeezed the field to 186px at 1024. */
body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-block {
	margin-bottom: 0;
	flex: 1 1 700px;
	/* 52 = the height of every control on the bar (section 12c), so the
	   line is the same height whether the coupon is closed or open and
	   nothing on it shifts when it opens. It was 44 while the field was
	   a 44px capsule. */
	min-height: 52px;
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 14px clamp(20px, 3vw, 48px);
}
/* "CART TOTALS" IS THE BAR'S OWN LABEL and sits first in the row,
   so the bar still says what it is without a heading above it. */
body.woocommerce-cart .wc-block-cart__totals-title {
	margin: 0;
	flex: 0 0 auto;
}
body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-coupon-form-block {
	flex: 0 0 auto;
	margin: 0;
}

/* THE COUPON PILL HAS TO BE fit-content, NOT auto, AND THAT IS THE
   WHOLE DIFFERENCE BETWEEN A PILL AND A BROKEN SELECT. The control is
   display:flex with justify-content:space-between (cart.css), so at
   `width: auto` it fills its parent and then pushes the words to one
   end and the chevron to the other: measured 298px at 1440, with
   "Add coupons" at x217 and the chevron at x489. It read as an empty
   dropdown, which is exactly what it is not — it is a disclosure.

   fit-content shrink-wraps it and space-between then has nothing to
   spread, so the gap is the gap. */
body.woocommerce-cart .wc-block-components-panel__button {
	width: fit-content;
	/* THE RIGHT PADDING IS THE CHEVRON'S ROOM, NOT TASTE, and the LEFT
	   one has to be stated. Two things about this control are
	   WooCommerce's and neither is visible in the file:

	     the icon is position:absolute, right:0  -- so it is OUT OF
	     FLOW and contributes NOTHING to the intrinsic width. At
	     fit-content the pill sizes to the words alone and the chevron
	     then sits ON TOP of the last two letters: measured, text
	     ending at x133 with the icon's box starting at x125.

	     padding-left: 0 !IMPORTANT  -- packages-style.css, on the bare
	     class. No specificity beats that, so the words started hard
	     against the pill's own edge and a shorthand of `10px 16px`
	     computed `10px 16px 10px 0`. It is the ONE !important in this
	     file and it is earned: found by walking document.styleSheets
	     for rules that match this element AND mention padding, which
	     is the move whenever a declaration is present, correct and
	     not applying.

	   `gap` is gone with them: a gap cannot reach an absolute child. */
	/* 52 tall like every control on the bar, with the text at the
	   site's field size (15px) — see "the field and APPLY" in 12c. It
	   was 40, with 13px words, beside a 52px checkout button. */
	box-sizing: border-box;
	min-height: 52px;
	padding: 0 42px 0 18px;
	padding-left: 18px !important;
	font-size: 15px;
	border: 1px solid rgba(242, 242, 244, .16);
	border-radius: 10px;   /* PROCEED TO CHECKOUT's corner (operator, 2026-11-20: "why its too rounded ?"). It was 999px, the only fully round control on the page; 12c's capsule, its APPLY and the × follow this. */
}
body.woocommerce-cart .wc-block-components-panel__button-icon {
	right: 14px;
	transition: transform .25s;
}

/* ---- the coupon row has states now ------------------------- */
/* It is a DISCLOSURE, and the only other signal it gives is the form
   appearing below it. Without these it looks inert on the way down. */
body.woocommerce-cart .wc-block-components-panel__button {
	transition: color .2s, border-color .2s;
}
body.woocommerce-cart .wc-block-components-panel__button:hover {
	color: #f2f2f4;
	border-color: rgba(242, 242, 244, .34);
}
body.woocommerce-cart .wc-block-components-panel__button:focus-visible {
	outline: 2px solid rgba(242, 242, 244, .75);
	outline-offset: 2px;
}
/* THE CHEVRON TURNS, AND IT HAS TO RESTATE WOO'S OWN TRANSLATE. The
   icon is positioned with transform: translateY(-12px); a rule that
   sets only the rotation replaces that, and the chevron jumps half
   its own height the moment it turns.

   READ THIS WITH TRANSITIONS KILLED. The pane renders about a frame a
   second, so a getComputedStyle straight after the click returns the
   START matrix and the rule looks dead. With them off it goes
   matrix(1,0,0,1,0,-12) -> matrix(-1,0,0,-1,0,-12). */
body.woocommerce-cart .wc-block-components-panel__button[aria-expanded="true"] .wc-block-components-panel__button-icon {
	transform: translateY(-12px) rotate(180deg);
}

/* THE OPEN FORM. NOT VERIFIED — this harness's accordion only flips
   aria-expanded; the real control is React and renders
   .wc-block-components-panel__content with an input and an Apply
   button, which the captured DOM does not carry. Defensive, not
   measured. Check it on the live page.

   IT IS flex-basis: 100% ON PURPOSE: the content is a child of the
   coupon block, which is a flex item of the bar, so an open form has
   to take a line of its own or it would try to sit in the row. */
body.woocommerce-cart .wc-block-components-panel__content {
	flex: 1 0 100%;
	padding: 14px 0 0;
}
body.woocommerce-cart .wc-block-components-totals-coupon__form {
	display: flex;
	flex-wrap: wrap;
	gap: 10px;
}

/* THE TOTAL IS PUSHED RIGHT, NOT STRETCHED. Three things were each
   absorbing the bar's slack and the row read as four things drifting
   apart rather than as two groups:

     .totals-wrapper        flex: 1 1 auto   -> ate the middle
     .totals-item__label    flex: 1 1 auto   -> 306px wide, so
                                               "Estimated total" sat
                                               far from its own figure
     the empty __description  flex: 1 0 100% -> a zero-height wrap line

   Everything shrink-wraps now and ONE auto margin does the spacing:
   label + coupon on the left, total + button on the right. */
/* THE :not() IS LOAD-BEARING. WooCommerce puts
   .wc-block-components-totals-wrapper on the COUPON block as well as
   on the totals one — the coupon's div carries both that class and
   .wp-block-woocommerce-cart-order-summary-coupon-form-block. Without
   the exclusion the auto margin lands on the coupon too and shoves it
   into the middle of the bar: measured 256px of gap on BOTH sides of
   it at 1440, which looks like a gap value nobody set and is two
   auto margins eating the row. */
body.woocommerce-cart .wc-block-components-totals-wrapper:not(.wp-block-woocommerce-cart-order-summary-coupon-form-block) {
	flex: 0 0 auto;
	margin-left: auto;
}
body.woocommerce-cart .wc-block-components-totals-footer-item {
	margin: 0;
	padding: 0;
	border: 0;
	flex-wrap: nowrap;
	justify-content: flex-end;
	gap: 0 14px;
}
body.woocommerce-cart .wc-block-components-totals-item__label,
body.woocommerce-cart .wc-block-components-totals-item__value {
	flex: 0 0 auto;
}
body.woocommerce-cart .wc-block-components-totals-item__description:empty {
	display: none;
}
body.woocommerce-cart .wc-block-components-totals-footer-item .wc-block-components-totals-item__label {
	color: rgba(242, 242, 244, .62);
}
/* THE BUTTON KEEPS ITS WIDTH AND GAINS AN AUTO MARGIN. It must not
   grow — E2 records what happens when it does, a 254px hole between
   the figure and the button on a shared line — but when it DOES wrap
   onto a line of its own it was sitting at 260px hard against the
   left edge of a 736px panel, which reads as unfinished.

   `margin-left: auto` costs nothing on the shared line, where the
   summary has already taken the free space, and right-aligns it on
   its own line, under the figure it belongs to. */
body.woocommerce-cart .wc-block-cart__submit {
	flex: 0 1 260px;
	margin-left: auto;
}
body.woocommerce-cart .wc-block-cart__submit-button,
body.woocommerce-cart .wp-block-woocommerce-proceed-to-checkout-block .wc-block-cart__submit-button {
	width: 100%;
	margin: 0;
}

/* ---- phones ------------------------------------------------- */
/* Below 680 cart.css already restacks the row and pins its own
   total bar to the bottom of the screen, so the only thing left to
   do is let the summary's row wrap into a column. */
@media (max-width: 760px) {
	body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-block {
		display: block;
	}
	body.woocommerce-cart .wc-block-cart__totals-title { margin-bottom: 14px; }
	body.woocommerce-cart .wc-block-components-totals-footer-item {
		justify-content: space-between;
		margin: 14px 0 0;
	}
	body.woocommerce-cart .wc-block-cart__submit-button,
	body.woocommerce-cart .wp-block-woocommerce-proceed-to-checkout-block .wc-block-cart__submit-button {
		width: 100%;
		min-width: 0;
	}
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row {
		padding-left: 24px;
	}
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row::before,
	body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row:first-child::before {
		top: 10px;
		left: 24px;
		transform: none;
	}
}

/* THE 960 BLOCK ABOVE STILL GIVES THE SIDEBAR A 26px TOP MARGIN. That
   was the air between a rail and the list it dropped under; the bar is
   a grid item with its own gap, so below 960 it would be 26px adrift
   from every other join on the page. The rest of that rule — static,
   no top border — is what this design wants anyway. */
@media (max-width: 960px) {
	body.woocommerce-cart .wc-block-cart__sidebar { margin-top: 0; }
}

/* ---- 12a. THE BAR IS FLAT (design E1a, operator 2026-11-20) ----
   "for the cart total its like a floating".

   MEASURED BEFORE ANYTHING WAS DRAWN, at 1440 with three lines:
   the line panels sat 12px apart, the bar sat 121px below the last
   one, and it was the SAME OBJECT — same fill, same 12px radius,
   same emboss, same width. A panel built exactly like a line item,
   standing ten times further from the list than the lines stand
   from each other, with the fit note in the gap. That is the whole
   of why it read as adrift; not the shadow and not the colour.

   THE CARD COMES OFF, so there is no object left to float. The bar
   is a ruled band on the page surface and the hairline is what says
   the list has ended — which is also the treatment the fit note
   used to carry, two lines further down, before it was removed in
   the same pass.

   Three other treatments were built and compared in
   docs/home-concepts/cart-redesign (E1b joined the stack at the
   rows' own 12px, E1c docked to the foot of the window). This is
   the one that changes no geometry. */
body.woocommerce-cart .wc-block-cart.wc-block-components-sidebar-layout {
	row-gap: 24px;
}
body.woocommerce-cart .wc-block-cart__sidebar {
	padding: 24px 0 0;
	border-radius: 0;
	background: none;
	box-shadow: none;
	border-top: 1px solid var(--sf-line);
}

/* ---- 12b. THE PAGER'S HIDDEN ROWS, PUT BACK --------------------
   FOUND 2026-11-20 AND IT HAD BEEN BROKEN SINCE THE LEDGER SHIPPED.
   cart.js marks the rows that are off the current page with
   .sf-cart-off, and section 5 hides them with

     body.woocommerce-cart .wc-block-cart-items__row.sf-cart-off

   which is (0,3,1). Section 12's row rule is
   `… .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row`
   at (0,4,1) and sets `display: grid`, so from the moment the
   ledger went up it OUT-SPECIFIED the hide and every row painted.

   WHAT IT LOOKED LIKE: a cart of eight showed all eight, under a
   pager that read "Showing 1–6 of 8 lines". Nothing errored, the
   class was on the right rows, and `querySelectorAll(':not(.sf-cart-off)')`
   still counted six — so every check that reads the DOM agreed with
   the pager and only the PAINTED page disagreed. It needed a cart
   with more than six lines in it to show at all.

   The lesson is section 12's own header: those rules win on source
   order at EQUAL specificity, but this one was not equal — it was
   longer, and it swallowed a shorter rule that had nothing to do
   with the design. Grep for anything setting `display` on a row
   before adding to that block. */
body.woocommerce-cart .wc-block-cart .wc-block-cart-items .wc-block-cart-items__row.sf-cart-off {
	display: none;
}

/* ---- 12c. THE COUPON OPENS IN PLACE (operator, 2026-11-20) -----
   "for add coupon its too messy and doesnt have color pink", then
   "floating ? please make it perfect", then "still not perfect..
   change another design". THIS IS THE THIRD DESIGN OF THE DAY and the
   two before it are worth knowing, because each failed for a reason
   that is easy to repeat.

     1. A DROPDOWN — a bordered panel with a shadow hanging under the
        pill, over the page. Rejected on sight: it floated, on a page
        whose previous three rounds were all about the summary
        floating.
     2. A SECOND LINE OF THE BAR — the form absolutely positioned
        under the pill and the bar growing to hold it. It no longer
        floated, but one 400px field on a line of its own left the
        rest of a 1300px bar empty, and it read as an afterthought.

   NOW THE PILL TURNS INTO THE FIELD. Open, the coupon sits on line one
   exactly where "Add coupons" was — a 52px field, a 52px APPLY beside
   it, and a small × after them that closes it again. (For an hour
   APPLY sat INSIDE a 44px capsule; see "the field and APPLY" below for
   why it came out.) Nothing is added to the bar: no new
   line, no new surface, no growth. WooCommerce closes the panel by
   itself on a successful apply, so the pill comes back with the
   discount line in the totals.

   WHAT WAS UNDERNEATH, read off the live page: WooCommerce's own
   light-theme field (white input, 1px grey border, radius 4, 16px
   type, 50px tall) and a pale button, which nothing had ever styled.

   TWO OF WOOCOMMERCE'S RULES BEAT THE SECOND DESIGN, AND ONLY A REAL
   CLICK SHOWS EITHER. The operator's screenshot had the hint sitting
   low in the field and 8px from its edge, and APPLY's label faded:

     .wc-block-components-text-input.is-active input[type="text"]
         padding: 24px 9px 8px  — and :focus adds padding-left 8.5px.
         (0,3,1) and (0,4,1). `is-active` lands on a real focus, NOT
         when the panel is opened by script — so a verification that
         opens it with .click() measures a state no customer sees.
         That is exactly how it shipped. The field's rule below is
         (0,6,2) for this reason.
     .wc-block-components-button:not(.is-link):disabled
       .wc-block-components-button__text            opacity: .5
         WooCommerce disables APPLY until something is typed and dims
         the LABEL, not the button — so white at 50% on solid magenta,
         which reads as a broken button rather than a waiting one.

   APPLY IS SOLID MAGENTA IN EVERY STATE (operator, 2026-11-20: "i
   want the button apply is color pink #ec1e79 like others button").
   For about an hour it was a dark magenta wash while the field was
   empty — the product page's out-of-stock fill — lighting up when a
   code was typed. It read as a different, dimmer button from the
   checkout button beside it, so it went. WooCommerce still DISABLES
   it while the field is empty, so a click does nothing; only the
   look of that state changed, and its label stays at full white.

   THE HINT IS A REAL PLACEHOLDER, set by cart.js's couponHint().
   WooCommerce draws "Enter code" as a <label> that fades on focus —
   and opening the panel AUTOFOCUSES the field, so the hint vanished
   the instant it appeared. The <label> is visually hidden, not
   removed: through its `for` it is still the field's name.

   THE OUTLINE IS OFF THE INPUT AND ON THE CAPSULE. :focus-within
   brightens the capsule's hairline, the same .16 -> .45 step the
   product page's review fields take. That IS the focus indicator for
   a keyboard user — if it ever reads as too quiet, raise the alpha;
   do not put a coloured ring back on the input inside it. */

/* ---- the open coupon replaces the pill on line one ---- */
/* 420 = field + APPLY + the ×, and it SHRINKS rather than wrapping.
   The floor is what the field needs to hold "Enter code" beside a
   full-size APPLY; section 12's summary basis of 700 is sized against
   it, so change them together.

   THE SUMMARY MUST NOT WRAP FOR THIS TO WORK. A wrapping flex row
   moves an item onto a new line BEFORE it shrinks anything — measured
   at 1024: the capsule kept its 380 and the total dropped under it,
   with the bar growing 36px. Phones are excluded because the summary
   is display:block there. */
@media (min-width: 761px) {
	body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-block {
		flex-wrap: nowrap;
	}
}
body.woocommerce-cart .wp-block-woocommerce-cart-order-summary-coupon-form-block:has(.wc-block-components-panel__button[aria-expanded="true"]) {
	flex: 0 1 420px;
	min-width: 270px;
}
body.woocommerce-cart .wc-block-components-totals-coupon {
	margin: 0;
}
body.woocommerce-cart .wc-block-components-totals-coupon:has(> .wc-block-components-panel__button[aria-expanded="true"]) {
	display: flex;
	align-items: center;
	gap: 4px;
}
/* the field comes first and the × after it, though the DOM has the
   toggle first — `order` rather than moving WooCommerce's nodes */
body.woocommerce-cart .wc-block-components-panel__content {
	order: -1;
	flex: 1 1 auto;
	min-width: 0;
	position: static;
	margin: 0;
	padding: 0;
	border: 0;
	border-radius: 0;
	background: none;
	box-shadow: none;
}

/* THREE STRAY MARGINS, ALL WOOCOMMERCE'S OR LEFT FROM THE RAIL. Flex
   `align-items: center` centres the MARGIN box, so each one pushed
   its owner off the line it was meant to share:

     .wc-block-cart__submit             margin-bottom 16px — the gap to
         the payment icons that used to sit under the button; it rode
         the button 8px high of the line's centre.
     .wc-block-components-totals-coupon  margin-bottom 4px — section 9,
         from when the coupon was a row in the rail.
     the panel button when OPEN          margin-bottom 16px — Woo's own,
         which made the control jump 6px up the line on open. */
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-cart__submit {
	margin-bottom: 0;
}

/* ---- the toggle, while open, is the × ----
   THE SAME ELEMENT, so aria-expanded and the keyboard still work and
   a screen reader still hears "Add coupons, expanded". The words go
   to font-size 0 rather than display:none so they stay its name; the
   chevron is hidden and the × is two hairlines.

   padding needs !important to beat WooCommerce's own
   `padding-left: 0 !important` and section 12's `18px !important` —
   an !important at higher specificity is the only thing that does. */
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"] {
	position: relative;
	flex: 0 0 auto;
	width: 36px;
	height: 36px;
	/* section 12 gives the closed control min-height 52, and a
	   min-height beats a height — without this the × is a 36x52 slot */
	min-height: 0;
	margin: 0;
	padding: 0 !important;
	border: 0;
	border-radius: 8px;
	background: none;
	font-size: 0;
	color: rgba(242, 242, 244, .5);
	transition: color .2s, background-color .2s;
}
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"]:hover {
	color: var(--sf-ink);
	background: rgba(255, 255, 255, .06);
}
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"] .wc-block-components-panel__button-icon {
	display: none;
}
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"]::before,
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"]::after {
	content: "";
	position: absolute;
	top: 50%;
	left: 50%;
	width: 14px;
	height: 1.5px;
	border-radius: 1px;
	background: currentColor;
}
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"]::before {
	transform: translate(-50%, -50%) rotate(45deg);
}
body.woocommerce-cart .wc-block-cart__sidebar .wc-block-components-panel__button[aria-expanded="true"]::after {
	transform: translate(-50%, -50%) rotate(-45deg);
}

/* ---- the field and APPLY: two controls, one height ----
   EVERY CONTROL ON THE BAR IS 52px NOW (operator, 2026-11-20: "is the
   button and size button and field is same size .. cause its looks
   like not standardized with all the button that exist in others
   page"). Measured across the site before changing anything:

     product page    variation picker 52, quantity 52, Add to cart 52
     contact form    every field 49, Send message 49
     this cart       PROCEED TO CHECKOUT 52

   So the house rule is that a field and the button beside it are the
   same height, and in the shopping flow that height is 52. The coupon
   broke it three ways: a 44px capsule, a 34px APPLY tucked inside it,
   and a 40px "Add coupons". Now the closed control, the field and
   APPLY are all 52, the same as the checkout button they share the
   line with.

   SO THE CAPSULE IS GONE. APPLY used to sit INSIDE the field, which
   is what made it smaller than every other button on the site. It
   stands beside the field now, as Send message does on the contact
   form and Add to cart does beside the quantity box.

   APPLY IS THE CHECKOUT BUTTON, value for value — Chakra Petch 13px /
   700 / .14em uppercase, white on #ec1e79, 10px corners, the same
   brightness-and-lift hover. The field takes the site's field type,
   Archivo 15px, which is what the product page's picker and the
   contact form's fields are set in. */
body.woocommerce-cart .wc-block-components-totals-coupon__form {
	display: flex;
	flex-wrap: nowrap;
	align-items: stretch;
	gap: 8px;
	box-sizing: border-box;
	width: 100%;
	height: auto;
	margin: 0;
	padding: 0;
	border: 0;
	border-radius: 0;
	background: none;
}
body.woocommerce-cart .wc-block-components-totals-coupon__input {
	flex: 1 1 auto;
	min-width: 0;
	margin: 0;
	padding: 0;
}
/* (0,6,2): it has to beat `.is-active input[type="text"]:focus` at
   (0,4,1) — see the header. Every property WooCommerce sets on the
   field in any state is restated here, because its :focus rule also
   turns the background white and the text dark. */
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-text-input.wc-block-components-totals-coupon__input input[type="text"] {
	box-sizing: border-box;
	width: 100%;
	height: 52px;
	min-height: 0;
	margin: 0;
	padding: 0 16px;
	border: 1px solid rgba(242, 242, 244, .16);
	border-radius: 10px;
	background: rgba(255, 255, 255, .04);
	box-shadow: none;
	outline: none;
	font-family: var(--sf-body);
	font-size: 15px;
	line-height: 50px;
	color: var(--sf-ink);
	transition: border-color .2s, background-color .2s;
}
/* the focus indicator: the hairline brightens, .16 -> .45, as the
   product page's review fields do. Keep it if this is re-pitched — the
   outline is off, so this IS what a keyboard user sees. */
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-text-input.wc-block-components-totals-coupon__input input[type="text"]:focus {
	border-color: rgba(242, 242, 244, .45);
	background: rgba(255, 255, 255, .06);
}
body.woocommerce-cart .wc-block-components-totals-coupon__input input::placeholder {
	color: var(--sf-faint);
	opacity: 1;
}
/* VISUALLY HIDDEN, NOT display:none — display:none would drop the
   field's accessible name, which this label is via its `for`. */
body.woocommerce-cart .wc-block-components-totals-coupon__input label {
	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;
	border: 0;
}

/* ---- APPLY — the checkout button's twin ---- */
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-button.wc-block-components-totals-coupon__button {
	flex: 0 0 auto;
	box-sizing: border-box;
	height: 52px;
	min-height: 52px;
	margin: 0;
	padding: 0 24px;
	border: 0;
	border-radius: 10px;
	background: var(--sf-accent);
	box-shadow: none;
	font-family: var(--sf-num);
	font-size: 13px;
	font-weight: 700;
	letter-spacing: .14em;
	text-transform: uppercase;
	color: #fff;
	cursor: pointer;
	transition: filter .2s, transform .2s;
}
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-button.wc-block-components-totals-coupon__button:not(:disabled):hover {
	filter: brightness(1.1);
	transform: translateY(-1px);
}
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-button .wc-block-components-button__text {
	color: #fff;
}
/* EMPTY FIELD: the same solid magenta, and the label at full strength
   (see the header). Only the cursor says it is waiting. The wash it
   replaced was color-mix(in srgb, var(--sf-accent) 18%, base). */
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-button.wc-block-components-totals-coupon__button:disabled {
	background: var(--sf-accent);
	cursor: default;
	filter: none;
	transform: none;
}
body.woocommerce-cart .wc-block-components-totals-coupon__form .wc-block-components-button:disabled .wc-block-components-button__text {
	opacity: 1;
}

/* ---- a code that does not exist ----
   WooCommerce prints the error under the form, inside the coupon
   block. In the flow that would make line one taller and shift
   everything on it, so on a desktop it hangs below the capsule
   instead, in the space under the bar. */
@media (min-width: 761px) {
	body.woocommerce-cart .wc-block-components-totals-coupon__content {
		position: relative;
	}
	body.woocommerce-cart .wc-block-components-totals-coupon__content .wc-block-components-validation-error {
		position: absolute;
		top: calc(100% + 8px);
		left: 14px;
		/* its own length, not the capsule's: "Coupon "test" cannot be
		   applied because it does not exist." wrapped to two lines
		   inside 326px and read as a block of text rather than a
		   note under a field. The cap keeps a long one off the
		   total on a narrow bar. */
		width: max-content;
		max-width: 480px;
		margin: 0;
	}
}
body.woocommerce-cart .wc-block-components-totals-coupon__content .wc-block-components-validation-error,
body.woocommerce-cart .wc-block-components-totals-coupon__content .wc-block-components-validation-error p {
	font-family: var(--sf-body);
	font-size: 12px;
	line-height: 1.4;
	color: var(--sf-accent);
}

/* ON A PHONE the bar is stacked, so the coupon block is a block of
   its own: the capsule and the × take the whole width, and the error
   sits in the flow under them (the stacked bar grows, which on a
   phone costs nothing). */
@media (max-width: 760px) {
	body.woocommerce-cart .wc-block-components-totals-coupon__content .wc-block-components-validation-error {
		margin: 8px 0 0 14px;
	}
}
