/* Atomic Signs — the four primitives.
 *
 * Step 2 of the handoff's migration order. The values are the handoff's
 * contract, taken from design_handoff_atomic_signs/primitives.css unchanged.
 *
 * ─── WHY THE CLASS NAMES ARE DIFFERENT ──────────────────────────────────────
 *
 * The handoff calls these .btn, .card, .chip and .badge, and says plainly that
 * "class names are a suggestion; the values are the contract". Taking the
 * suggestion literally here would be destructive: this site runs Bootstrap 5
 * from the bootscore-5 parent, which owns .btn, .card and .badge, and
 * WooCommerce's cart, checkout and My Account are built out of them — as is
 * the sticker studio. Redefining them globally would restyle every button on
 * the site to sell one banner stand.
 *
 * So every primitive is namespaced .as-*. Nothing in this file matches an
 * element that exists today, which is what makes it safe to enqueue globally
 * while the migration is half done. The handoff expects that state: "the rest
 * of the demo can stay unstyled — mismatch mid-migration is expected."
 *
 * Requires css/atomic-tokens.css.
 */

/* ============ 1. BUTTON ============ */
.as-ap__clearq,
.as-ap__helpcta,
.as-ap__emptycta,
.as-bn-setup__cta,
.as-bn__lookup-cta,
.as-acct__btn,
.as-ship-up__go,
.as-faq__clear,
.as-pickup-modal__go,
.asp-pg-upload-section .asp-pg-fix-btn,
.asp-pg-upload-section .asp-pg-browse-btn,
.as-sgnp-repl__cta,
.as-dlx-tpl__cta,
.as-search-overlay__close,
.single-product .woocommerce-message .button,
.as-route-cat .as-cat-body__inner ul.products li.product .button,
.as-btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-2);
  min-height: var(--tap-min);
  padding: 14px 28px;
  border-radius: var(--radius-pill);
  border: none;
  font-family: var(--font-sans);
  font-size: var(--text-body);
  font-weight: 700;
  line-height: 1;
  text-decoration: none;
  cursor: pointer;
  transition: background var(--dur) var(--ease), transform var(--dur) var(--ease),
              box-shadow var(--dur) var(--ease), color var(--dur) var(--ease);
}
.as-btn--primary        { background: var(--atomic-blue); color: var(--color-text-invert); }
.as-btn--primary:hover  { background: #159ac6; color: var(--color-text-invert); }
.as-btn--secondary      { background: var(--atomic-dark); color: var(--color-text-invert); }
.as-btn--secondary:hover{ background: var(--atomic-darker); color: var(--color-text-invert); }
.as-btn--outline        { background: transparent; color: var(--color-text); box-shadow: inset 0 0 0 2px var(--color-text); }
.as-btn--outline:hover  { box-shadow: inset 0 0 0 2px var(--atomic-blue); color: var(--atomic-blue); }

/*
 * Outline on a dark surface.
 *
 * The button above draws itself in --color-text for both the label and the
 * ring, which is correct on white and invisible on navy — an outline button in
 * a --dark card was dark-on-dark, readable only by knowing it was there. The
 * variant inverts rather than the primitive changing meaning.
 */
.as-card--dark .as-btn--outline,
.as-section--dark .as-btn--outline,
.as-home-about__panel .as-btn--outline {
  color: var(--color-text-invert);
  box-shadow: inset 0 0 0 2px var(--color-text-invert);
}
.as-card--dark .as-btn--outline:hover,
.as-section--dark .as-btn--outline:hover,
.as-home-about__panel .as-btn--outline:hover {
  color: var(--atomic-dark);
  background: var(--color-text-invert);
  box-shadow: inset 0 0 0 2px var(--color-text-invert);
}
.as-btn--lg             { padding: 16px 32px; font-size: var(--text-body); }
/*
 * ─── THE SCATTERED CTA IS --sm ──────────────────────────────────────────────
 *
 * Twenty route-level buttons drew themselves, running from 6px 12px to 15px
 * 18px with six different type sizes. They are listed on `.as-btn` and on
 * `--sm` above so this needs no template change, and their own rules keep
 * only what is genuinely local: colour, margin, position, and any display
 * the layout around them depends on.
 *
 * `.as-btn` itself is UNCHANGED at 14px 28px / --text-body. It is used 42
 * times in markup and carries the site's primary actions; shrinking it to
 * tidy twenty strays would be the tail wagging the dog.
 *
 * min-height: 0 is the point of this variant. The base button holds
 * --tap-min (44px); a secondary CTA beside a paragraph does not need to.
 */
.as-btn--sm,
.as-ap__clearq,
.as-ap__helpcta,
.as-ap__emptycta,
.as-bn-setup__cta,
.as-bn__lookup-cta,
.as-acct__btn,
.as-ship-up__go,
.as-faq__clear,
.as-pickup-modal__go,
.asp-pg-upload-section .asp-pg-fix-btn,
.asp-pg-upload-section .asp-pg-browse-btn,
.as-sgnp-repl__cta,
.as-dlx-tpl__cta,
.as-search-overlay__close,
.single-product .woocommerce-message .button,
.as-route-cat .as-cat-body__inner ul.products li.product .button {
  min-height: 0;
  padding: var(--space-2-5) var(--space-4-5);
  font-size: var(--text-sm);
}
/*
 * ─── THE FULL-WIDTH SUBMIT ──────────────────────────────────────────────────
 *
 * The blue pill that spans its column and ends a form: continue to checkout,
 * place order, sign in, add to cart, verify email. Six rules wrote it, and
 * three of those — .as-co__go, #place_order and the thank-you page's verify
 * button — were the same eleven declarations three times over.
 *
 * `.as-btn--block` is the name a style audit guessed this repo already had.
 * It did not; nor did `.as-btn--xs`. That is worth recording, because the
 * reason people hand-rolled this eleven-declaration recipe six times is that
 * the primitive offered `--lg` and `--sm` and nothing for "fills its column".
 * A missing variant is not a neutral gap — it is a duplication generator.
 *
 * SIZE STAYS LOCAL. These six run 15/16/17px of padding and 15/16px of type,
 * and squashing them to one number would resize the add-to-cart button on
 * every product page to tidy a stylesheet. That is a decision about the shop,
 * not about CSS, so the recipe is shared and the size is not.
 *
 * Listed by selector so this needs no template change — the WooCommerce
 * buttons among them are not ours to add a class to anyway.
 */
.as-btn--block,
.as-co__go,
.as-co__place #place_order,
.as-route-thanks .woocommerce-verify-email button,
.as-login__go,
body.woocommerce.single-product button.single_add_to_cart_button,
.single-product .summary .single_add_to_cart_button.button {
  display: block;
  width: 100%;
  border: 0;
  border-radius: var(--radius-pill);
  background: var(--atomic-blue);
  color: var(--color-text-invert);
  font-family: inherit;
  font-weight: 700;
  text-align: center;
  cursor: pointer;
  transition: background var(--dur) var(--ease);
}

/* Playful variant, promo bands only. */
.as-btn--press          { box-shadow: var(--shadow-press); transform: rotate(1deg); }

/* ============ 2. CARD ============ */
.as-card {
  background: var(--color-surface);
  border: 1.5px solid var(--color-border);
  border-radius: var(--radius-md);
  padding: var(--space-6);
}
.as-card--lg    { border-radius: var(--radius-lg); padding: var(--space-8); }
.as-card--tint  { background: var(--color-surface-tint); border-color: transparent; }
.as-card--dark  { background: var(--atomic-dark); color: var(--color-text-invert); border-color: transparent; }
.as-card--float { box-shadow: var(--shadow-card); }
.as-card--link  { transition: transform var(--dur) var(--ease), box-shadow var(--dur) var(--ease); }
.as-card--link:hover { transform: translateY(-4px); box-shadow: var(--shadow-card-hover); }

/* ============ 3. CHIP / BADGE ============ */
.as-chip {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  padding: 9px 16px;
  border-radius: var(--radius-pill);
  font-size: var(--text-sm);
  font-weight: 700;
  line-height: 1;
  white-space: nowrap;
  text-decoration: none;
}
.as-chip--outline  { background: var(--color-surface); border: 1.5px solid var(--color-border); color: var(--color-text); }
.as-chip--solid    { background: var(--atomic-blue); color: var(--color-text-invert); }
.as-chip--tint     { background: var(--color-surface-tint); color: var(--color-text); }
.as-chip--selected { border: 2px solid var(--atomic-blue); background: var(--color-surface-tint); }
/* Small chip: promo card facts, the product card's Included list. */
.as-chip--xs       { padding: 4px 10px; font-size: var(--text-label); font-weight: 600; }
/* Jump chip: adds a directional arrow. */
.as-chip--jump       { font-size: var(--text-body-lg); padding: 11px 22px; gap: var(--space-2-5); letter-spacing: -0.01em; }
.as-chip--jump:hover { border-color: var(--atomic-blue); background: var(--color-surface-tint); color: var(--atomic-blue); }
.as-chip--jump .as-chip__arrow { color: var(--atomic-blue); font-size: var(--text-body); line-height: 1; }

/* Splash badge — circular, tilted, hero decoration only.
 * pointer-events:none is load-bearing: it sits over the artwork drop target
 * and must never swallow a drop. */
.as-badge-splash {
  width: 104px;
  height: 104px;
  border-radius: 50%;
  background: var(--atomic-blue);
  color: var(--color-text-invert);
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: var(--space-0-5);
  transform: rotate(-12deg);
  box-shadow: var(--shadow-pop);
  pointer-events: none;
  text-align: center;
}
.as-badge-splash__num  { font-weight: 800; font-size: var(--text-h2); line-height: 1; letter-spacing: var(--tracking-tight); }
.as-badge-splash__unit { font-weight: 800; font-size: var(--text-sm); line-height: 1; }
.as-badge-splash__note { font-size: var(--text-label); font-weight: 700; letter-spacing: 0.06em; padding-top: 2px; }

/* ============ 3b. IMAGE SLOT ============ */
/*
 * A slot holds its space whether or not a photograph exists yet, so the page is
 * laid out correctly today and correct when the photography lands. The empty
 * state names what belongs there — see inc/image-slot.php.
 *
 * This lives in primitives, not in a route stylesheet. It started in
 * route-home.css because the homepage was the first page to use a slot, which
 * meant the pickup page's slot rendered as a bare line of text: the markup was
 * shared, the styling was not. Anything inc/ can emit anywhere belongs here.
 */
.as-slot {
  display: block;
  position: relative;
  overflow: hidden;
  border-radius: var(--radius-lg);
  background: var(--color-surface-alt);
}

.as-slot__img { display: block; width: 100%; height: 100%; object-fit: cover; }

.as-slot--empty {
  display: grid;
  place-items: center;
  padding: 12px;
  border: 1px dashed var(--color-border);
  background:
    repeating-linear-gradient(
      45deg,
      var(--color-surface-alt) 0 10px,
      var(--color-surface-tint) 10px 20px
    );
}

.as-slot__label {
  font-size: var(--text-xs);
  font-weight: 600;
  line-height: 1.35;
  text-align: center;
  color: var(--color-text-muted);
}

/* ============ 4. SECTION HEADER ============ */
.as-section        { padding: var(--space-14) var(--gutter); }
.as-section--alt   { background: var(--color-surface-alt); }
.as-section--dark  { background: var(--atomic-dark); color: var(--color-text-invert); }
:where(input,
textarea,
select,
button,
a,
[tabindex]):focus-visible,
.as-q__input:focus,
.woocommerce .as-co__form input:focus,
.woocommerce .as-co__form textarea:focus,
.woocommerce .as-co__form select:focus,
.as-route-account .woocommerce input:focus,
.as-route-account input:focus,
.as-srch__form input[type="search"]:focus,
.asp-mine-modal__find:focus,
.as-faq__search:focus,
.as-ap__search:focus-within,
.as-mega__search:focus-within,
.as-bn__field:focus-within,
.as-cat-build__dim:focus-within,
.as-priceline--sign .quantity:focus-within {
  outline: 2px solid var(--focus-ring);
  outline-offset: 2px;
}
/* The header search overlay is NOT on that list: an outline around a bar the
   width of the page drew a square box that spilled 2px up into the
   announcement strip, and the bar needs no ring at all (Dennis, 2026-11-14 —
   see header.css, .as-search-overlay__form). */

/*
 * Search fields that carry their own clear or close button. WebKit draws a ⊗
 * in any type="search" input, and `appearance: none` does not remove it, so
 * these showed two ways to clear side by side.
 */
.as-ap__input::-webkit-search-cancel-button,
.as-faq__search::-webkit-search-cancel-button,
.as-search-overlay__form input[type="search"]::-webkit-search-cancel-button { display: none; }

/*
 * ─── THE FAQ BLOCK ──────────────────────────────────────────────────────────
 *
 * Built three times in PHP and twice in CSS: roughly fourteen rules here for
 * the banner family and fourteen more for the board, describing the same
 * two-column list with an aside. The differences were a class suffix (__aside
 * against __card) and markup (dl/dt/dd against three divs).
 *
 * The renderer now emits dl/dt/dd for both — a FAQ is a description list, and
 * that is what pairs a question with its answer for a screen reader — so the
 * board's `__q` and `__a` rules are gone rather than renamed.
 *
 * Sizes and spacing come from the banner build, which was the one already on
 * the scales.
 */
.as-bn-faq__inner,
.as-dlx-faq__inner {
  display: grid;
  grid-template-columns: 1fr 320px;
  gap: var(--space-14);
  align-items: start;
}
/*
 * SIZE IS NOT SHARED. The banner page sets its section headings at --text-h2
 * and the board page at --text-stat; merging them here put the board's FAQ
 * heading 10px below its own neighbours. Page rhythm is a route decision.
 */
.as-bn-faq__list h2,
.as-dlx-faq__list h2 {
  margin: 0 0 var(--space-2);
  font-weight: 800;
  letter-spacing: var(--tracking-tight);
}
.as-bn-faq__list dl,
.as-dlx-faq__list dl { margin: 0; }

.as-bn-faq__row,
.as-dlx-faq__row {
  display: grid;
  grid-template-columns: 1fr 1.3fr;
  gap: var(--space-8);
  padding: var(--space-5) 0;
  border-bottom: 1px solid var(--color-border-soft);
  align-items: start;
}
.as-bn-faq__row dt,
.as-dlx-faq__row dt { font-weight: 700; font-size: var(--text-body); line-height: 1.35; text-wrap: balance; }
.as-bn-faq__row dd,
.as-dlx-faq__row dd { margin: 0; font-size: var(--text-sm); line-height: 1.65; color: var(--color-text-muted); }

.as-bn-faq__aside,
.as-dlx-faq__aside {
  background: var(--color-surface-alt);
  border-radius: var(--radius-lg);
  padding: var(--space-6) var(--space-7);
  display: flex;
  flex-direction: column;
  gap: var(--space-2-5);
  margin-top: var(--space-12);
}
.as-bn-faq__aside strong,
.as-dlx-faq__aside strong { font-weight: 800; font-size: var(--text-body-lg); }
.as-bn-faq__aside p,
.as-dlx-faq__aside p { margin: 0; font-size: var(--text-sm); line-height: var(--leading-body); color: var(--color-text-muted); }
.as-bn-faq__tel,
.as-dlx-faq__tel { font-weight: 800; font-size: var(--text-h3); color: var(--atomic-dark); }
.as-bn-faq__tel:hover,
.as-dlx-faq__tel:hover { color: var(--atomic-blue); }
.as-bn-faq__mail,
.as-dlx-faq__mail { font-weight: 700; font-size: var(--text-sm); }

@media (max-width: 900px) {
  .as-bn-faq__inner,
  .as-dlx-faq__inner { grid-template-columns: 1fr; gap: var(--space-8); }
  .as-bn-faq__aside,
  .as-dlx-faq__aside { margin-top: 0; }
  .as-bn-faq__row,
  .as-dlx-faq__row { grid-template-columns: 1fr; gap: var(--space-2); }
}

/*
 * ─── THE SEGMENTED CONTROL, AND THE SELECTED PILL ───────────────────────────
 *
 * Two patterns that look alike and are not.
 *
 * A SEGMENTED CONTROL is a track with a thumb: a tinted rail, items that are
 * transparent until chosen, and the chosen one going WHITE so it reads as
 * lifted out of the rail. The banner route builds it twice —
 * .as-bn__grouptabs and .as-bn__rowline .as-bn__pills — with the same rail
 * padding, the same gap, the same radius and the same white-when-on. Two
 * builds of one control is how the next change lands in one of them.
 *
 * A SELECTED PILL is free-standing: white on the page, filling NAVY when
 * chosen. Four do that — the preset, the sheet tab, the standalone pill and
 * the category filter — each with its own padding, which stays local because
 * a filter row and a size tab want different weights of tap target.
 *
 * The two are not interchangeable: white-when-on only reads as selected
 * against a tinted rail, and navy-when-on only reads as selected against a
 * white page. Which is why the on-states are separate rules rather than one.
 */
/*
 * The values are checkout section 2's (design/handoffs/section 2, README X:
 * 4px rail and gap, 12px rail corners, 9px option corners, a 2px blue ring on
 * the chosen one). Dennis, 2026-11-13: the newest design sets the one control
 * everywhere, so the banner route's two tracks took the ring with it.
 */
.as-bn__grouptabs,
.as-bn__rowline .as-bn__pills,
.as-fulfil__track {
  display: flex;
  gap: var(--space-1);
  padding: var(--space-1);
  background: var(--color-surface-alt);
  border-radius: 12px;
}

.as-bn__grouptab,
.as-bn__rowline .as-bn__pill,
.as-fulfil__opt {
  flex: 1 1 0;
  min-width: 0;
  border: 0;
  background: transparent;
  border-radius: 9px;
  font-weight: 700;
  cursor: pointer;
}
/* Hover lifts the text only; the ring and the white are for the chosen one. */
.as-bn__grouptab:hover,
.as-bn__rowline .as-bn__pill:hover,
.as-fulfil__opt:hover {
  color: var(--color-text);
}
.as-bn__grouptab.is-on,
.as-bn__rowline .as-bn__pill.is-on,
.as-fulfil__opt.is-on {
  background: var(--color-surface);
  color: var(--atomic-dark);
  box-shadow: 0 0 0 2px var(--atomic-blue);
}

/* Free-standing, so it fills navy rather than going white. */
.as-unit__opt.is-on,
.as-pill--on,
.as-bn__preset.is-on,
.as-bn__sheet-tab.is-on,
.as-bn__pill.is-on,
.as-cat-filter[aria-pressed="true"] {
  background: var(--atomic-dark);
  color: var(--color-text-invert);
}

/*
 * ─── THE IN | CM SWITCH ─────────────────────────────────────────────────────
 *
 * Centro_Unit_Switch's look, and the only one: the /signs/ hero, Custom
 * Signs, the sticker size step and Window Decals all draw this. A bordered
 * pill group with no fill, the chosen unit navy (in the free-standing on-state
 * list above). Handoff signs-hero 4a; 11.5px there, --text-xs here.
 *
 * Drawn 29px tall, which is the design; the ::after on each option reaches
 * --tap-min without changing what is drawn.
 */
.as-unit {
  display: inline-flex;
  flex: none;
  gap: var(--space-0-5);
  padding: var(--space-0-5);
  border: 1.5px solid var(--color-border-soft);
  border-radius: var(--radius-pill);
  background: transparent;
}
.as-unit__opt {
  position: relative;
  padding: var(--space-1) var(--space-3);
  border: 0;
  border-radius: var(--radius-pill);
  background: transparent;
  color: var(--color-text-muted);
  font: inherit;
  font-size: var(--text-xs);
  font-weight: 700;
  line-height: 1.3;
  cursor: pointer;
}
.as-unit__opt::after { content: ""; position: absolute; inset: calc((var(--tap-min) - 100%) / -2) 0; }
.as-unit__opt:not(.is-on):hover { color: var(--atomic-dark); }

/*
 * ─── THE PRODUCT CARD (handoff option 6c) ───────────────────────────────────
 *
 * Every category grid, /shop/, and anything else that lists products. It lives
 * in primitives rather than route-category.css because it is not a category
 * component — it only ever lived there because categories were the first place
 * it appeared.
 *
 * Image well is 1:1 on white with the product contained, not cropped: the
 * renders are cut-outs on white, so `cover` would trim a board's legs.
 *
 * The split pill is one control, not two: a price half and a View half sharing
 * a 2px navy ring. On hover the whole thing fills navy, which is why the price
 * half needs an explicit colour rather than inheriting.
 *
 * `margin-top: auto` on __foot is what keeps every pill on one baseline when a
 * neighbour's name wraps to two lines. The grid stretches rows; without it the
 * pills stagger.
 */
.as-cat-card {
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
  background: var(--color-surface);
  color: var(--color-text);
  border-radius: var(--radius-lg);
  /* No shadow at rest — only on hover, where it lifts with the card
     (Dennis, 2026-11-14). */
  box-shadow: none;
  overflow: hidden;
  text-decoration: none;
  padding-bottom: var(--space-4-5);
  transition: transform var(--dur) var(--ease), box-shadow var(--dur) var(--ease);
}
.as-cat-card:hover {
  transform: translateY(-5px);
  box-shadow: var(--shadow-card-hover);
  color: var(--color-text);
}

.as-cat-card__shot {
  display: block;
  width: 100%;
  background: var(--color-surface);
  padding: var(--space-3);
}
.as-cat-card__shot .as-slot {
  width: 100%;
  aspect-ratio: 1 / 1;
  border-radius: 0;
}
.as-cat-card__shot img {
  width: 100%;
  height: 100%;
  object-fit: contain;
}

.as-cat-card__body {
  display: flex;
  flex-direction: column;
  align-items: center;
  flex: 1;
  width: 100%;
  padding: 0 var(--space-5);
}
/* The eyebrow recipe comes from .as-eyebrow; only its colour is local. */
.as-cat-card__eyebrow { color: var(--atomic-blue); }
.as-cat-card__name {
  display: block;
  margin: var(--space-1) 0 var(--space-3);
  font-size: var(--text-body);
  font-weight: 700;
  line-height: 1.3;
}

.as-cat-card__foot {
  display: flex;
  flex-direction: column;
  align-items: center;
  margin-top: auto;
  width: 100%;
}
.as-cat-card__incl {
  display: block;
  margin-bottom: var(--space-2);
  font-size: var(--text-xs);
  font-weight: 600;
  color: var(--color-text-muted);
}

.as-cat-card__cta {
  display: flex;
  align-items: stretch;
  border: 2px solid var(--atomic-dark);
  border-radius: var(--radius-pill);
  overflow: hidden;
  font-weight: 800;
  font-size: var(--text-sm);
  line-height: 1;
  transition: background var(--dur) var(--ease);
}
.as-cat-card__price,
.as-cat-card__view {
  display: flex;
  align-items: center;
  justify-content: center;
  padding: var(--space-2) var(--space-4);
  white-space: nowrap;
}
.as-cat-card__price { color: var(--atomic-dark); }
.as-cat-card__view  { background: var(--atomic-dark); color: var(--color-text-invert); }
.as-cat-card:hover .as-cat-card__cta  { background: var(--atomic-dark); }
.as-cat-card:hover .as-cat-card__price { color: var(--color-text-invert); }

/*
 * ─── THE PAGE WRAPPER, ONCE ─────────────────────────────────────────────────
 *
 * Cap at --page-max, centre, and hold the gutter. Sixteen rules across twelve
 * stylesheets wrote that same three-line recipe under sixteen different class
 * names, and two of them — the breadcrumb/product pair in route-product.css —
 * were written TWICE in the same file, the first copy entirely dead because
 * the second repeated all four declarations verbatim and added a selector.
 *
 * Measured across twelve real pages before this change: 58 of the 63 wrappers
 * on the site already resolved to the same numbers — 1440px wide, content edge
 * at x=136. So this consolidates something that was already uniform; it is not
 * a redesign. The five that differ are the deliberately inset bands, which cap
 * at `--page-max` MINUS two gutters and are left alone.
 *
 * Route classes are listed here so this needs no template change. As markup
 * adopts `.as-wrap` the list shrinks; until then there is one recipe, not
 * sixteen.
 *
 * NOT a wrapper, deliberately: anything that also carries block padding
 * (.as-co__wrap, .as-pdp__meta, .as-footer__inner) or a
 * different cap (.as-cat-faq__inner at 860px). They share three declarations
 * with this, not a purpose.
 */
.as-wrap,
.as-ap,
.as-cat__wrap,
.as-contact__wrap,
.as-home__wrap,
.as-promo__wrap,
.as-q__wrap,
.as-srch__wrap,
.as-pdp__wrap,
.as-cat-hero__inner,
.as-cat-body__inner,
.as-sgnp-detail__inner,
.as-sgnp-repl__inner,
.as-sgnp-tpl__inner,
.as-dlx-feat__inner,
.as-dlx-cmp__inner,
.as-dlx-faq__inner,
.single-product .woocommerce-breadcrumb,
.single-product div.product,
/*
 * The notice sits "under the header/breadcrumb in the 1160px container"
 * (section Y), and the container is this recipe — so it joins the list rather
 * than growing a sixteenth copy of max-width + auto margins + gutter. Scoped
 * with :has() so only our card gets it; a plain Woo notice elsewhere keeps
 * whatever it had.
 */
.single-product .woocommerce-notices-wrapper:has(.as-added),
.single-product .woocommerce-notices-wrapper:has(.as-cart-error) {
  max-width: var(--page-max);
  margin-inline: auto;
  padding-inline: var(--gutter);
  box-sizing: border-box;
}

/*
 * ─── AND THE UPPERCASE LABEL IS THE SAME COMPONENT ──────────────────────────
 *
 * Asked whether there were still ten eyebrows, the answer was eleven selectors
 * on one recipe — and then a wider count found 37 uppercase tracked rules
 * carrying 21 recipes, most of them in the group set aside during the first
 * pass as "badges and pills, not eyebrows". Two of them were literally named
 * __eyebrow. That line had been drawn by what the numbers looked like rather
 * than by what the elements are, which is the same error the --strong variant
 * was.
 *
 * Thirty of them join the list: eyebrows, group headings, table headers,
 * badges and data labels, running .05em to .12em of tracking. At 11px that
 * whole spread is half a pixel.
 *
 * TEN ARE LEFT OUT, and the reason each is left matters more than the count:
 *
 *   Four display titles — .as-hero__title and friends — carry NEGATIVE
 *   tracking. They are uppercase and that is all they share with a label.
 *
 *   Three sit at .02em on purpose: the checkout and account form-row labels,
 *   and the shop's product-category line. A label you read inline is not a
 *   label you scan, and 0.02em is the difference being made deliberately.
 *
 *   Three are deliberately larger — --text-sm or --text-body — where dropping
 *   to 11px would be a visible change to a section title, not a correction.
 */
/*
 * ─── THE EYEBROW, ONCE — AND THIS TIME ACTUALLY ONCE ────────────────────────
 *
 * A style audit on 2026-09-20 found 53 rules setting `text-transform:
 * uppercase`; ten of them were genuinely this component, carrying five
 * different type recipes between them. Two of those five were written the
 * same week, by me, in a repo whose CLAUDE.md says to grep before inventing a
 * class. Nothing catches that: the class names are all different, only the
 * numbers repeat.
 *
 * ─── WHY THIS WAS TWO VARIANTS, AND WHY IT IS NOW ONE ───────────────────────
 *
 * The first pass kept `.as-eyebrow` and `.as-eyebrow--strong`, justified as
 * "collapsing would change a font-weight on three components to save a rule".
 * That was the wrong question. The two groups were clustered BY THE NUMBERS
 * THEY HAPPENED TO CARRY, not by what the elements are — so five hero
 * eyebrows ended up split across both, with the quote and homepage heroes in
 * one variant and the promos, stickers and product heroes in the other. The
 * only thing separating them was what someone typed, months apart. Naming
 * that split `--strong` preserved the drift and made it look deliberate.
 *
 * --text-label is the token documented for exactly this ("uppercase eyebrows,
 * letter-spacing .1em"), which is why it is the value that survived rather
 * than the generic --text-xs.
 *
 * COLOUR IS NOT HERE, deliberately. It is contextual — blue on light, white
 * on dark — and `.as-section__eyebrow` below sets blue from outside the
 * component.
 *
 * The route classes are listed alongside so this takes effect without
 * touching a template. As markup adopts `.as-eyebrow` the list shrinks.
 */

.as-eyebrow,
.as-acct__card-head,
.as-acct__pill,
.as-ap__grouphead,
.as-badge-ok,
.as-priceline__eyebrow,
.asp-live-price__label,
.as-bn-compare__table thead th,
.as-bn-mat__badge,
.as-bn__axis,
.as-bn__rowlabel,
.as-bn__rowline .as-bn__rowlabel,
.as-cat-compare__table thead th,
.as-cat-swap__eyebrow,
.as-co__form .shipping_address::before,
.as-contact-way__label,
.as-faq__hourshead,
.as-footer__head,
.as-q__label,
.as-q__side-head,
.as-sgnp-buy__eyebrow,
.as-sgnp-tpl__row dt,
.as-ship__cardhead,
.as-ship__table thead th,
.as-thanks__fact-label,
.asp-pg-label,
.asp-slot-strip__title,
.as-fulfil__label,
.as-cat-masthead__kicker,
.as-promo-hero__kicker,
.as-srch__kicker,
.as-stk-hero__kicker,
.as-pdp__hero-eyebrow,
.single-product .summary .as-pdp__hero-eyebrow,
.as-section__eyebrow,
.as-q-hero__eyebrow,
.as-pdp__eyebrow,
.as-stk-sample__kicker {
  font-size: var(--text-label);
  font-weight: 800;
  letter-spacing: var(--tracking-label);
  text-transform: uppercase;
}

.as-section__eyebrow {
  color: var(--atomic-blue);
}
/* The homepage's and /promos/'s section heads were word-for-word copies. */
.as-section__title,
.as-home__head h2,
.as-promo__head h2 {
  font-size: var(--text-h2);
  font-weight: 700;
  letter-spacing: -0.01em;
  margin: 0;
}
.as-section__sub   { font-size: var(--text-sm); color: var(--color-text-muted); }
/*
 * ─── THE STARBURST BAND, AND THE WHITE CARD TILTED ON IT ─────────────────
 *
 * The homepage's Split 5, /promos/'s newsletter and the sticker page's Split
 * bar are one recipe drawn three times. Each place sets only what differs:
 * its padding, its shadow and its --tilt.
 */
.as-home-split__band,
.as-promo-news__band {
  display: flex;
  align-items: center;
  gap: var(--space-10);
  border-radius: var(--radius-xl);
  background: var(--burst);
}
.as-home-split__card,
.as-promo-news__card,
.as-stk-promos__bar {
  display: flex;
  border-radius: var(--radius-lg);
  background: var(--color-surface);
  transform: rotate(var(--tilt, 0deg));
}

/*
 * ─── THE SEARCH PILL ────────────────────────────────────────────────────
 *
 * /shop/'s filter and the phone menu's search field. Each keeps its own
 * display (the menu's is hidden off a phone, header.css), padding and size.
 */
.as-ap__search,
.as-mega__search {
  align-items: center;
  gap: var(--space-2-5);
  border: 1.5px solid var(--color-border);
  border-radius: var(--radius-pill);
}
.as-ap__input,
.as-mega__search input[type="search"] {
  flex: 1;
  min-width: 0;
  border: 0;
  outline: none;
  background: transparent;
  font-family: inherit;
  color: var(--color-text);
  -webkit-appearance: none;
  appearance: none;
}
.as-ap__input::placeholder,
.as-mega__search input[type="search"]::placeholder { color: var(--color-placeholder); }

.as-section__head {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: var(--space-6);
  margin-bottom: var(--space-6);
}

/* Stat block: thick blue rule above a big numeral. */
.as-stat      { border-top: 4px solid var(--atomic-blue); padding-top: var(--space-4); }
.as-stat__num {
  font-size: var(--text-stat);
  font-weight: 800;
  line-height: 1;
  letter-spacing: var(--tracking-tight);
  /* Required by the handoff — numerals must not wrap. */
  white-space: nowrap;
}

/* ============ SCOPE ============ */
/*
 * Poppins is applied only inside a rebuilt route, never to <body>. The rest of
 * the site keeps the parent theme's face until its route is migrated, which is
 * the difference between a half-finished migration and a broken one.
 */
.as-route {
  font-family: var(--font-sans);
  color: var(--color-text);
  background: var(--color-surface);
}
.as-route a { color: var(--atomic-blue); text-decoration: none; }
.as-route a:hover { color: var(--atomic-dark); }

/* ══ NOTICES — handoff section Y, 2a and 2g ═══════════════════════════════ */

/*
 * ─── 2a · ADDED TO YOUR CART ────────────────────────────────────────────────
 *
 * A white card where Woo drew a tinted bar. It replaces the bar's INSIDES via
 * wc_add_to_cart_message_html, so the .woocommerce-message wrapper is still
 * around it — hence the reset: the wrapper's padding, border and tint would
 * otherwise frame the card inside a second box.
 */
/*
 * Named at every context that tints the bar, because each of those is (0,2,0)
 * and comes later in the cascade — a bare `.woocommerce-message:has(…)` ties
 * and loses. The theme already solves this the same way for .as-eyebrow and
 * .as-wrap: list the selectors rather than reach for !important.
 */
.woocommerce-message:has(.as-added),
.single-product .woocommerce-message:has(.as-added),
.as-route-cart .woocommerce-message:has(.as-added),
.as-route-checkout .woocommerce-message:has(.as-added) {
  background: none;
  border: 0;
  padding: 0;
  /*
   * 14px of top margin so the card clears the breadcrumb above it. At 0 the
   * two touched exactly — breadcrumb ending at 164, card starting at 165 —
   * which read as the card sitting on the trail rather than under it
   * (Dennis, 2026-10-06: "its placement could go down slightly to not
   * interfere with the breadcrumbs").
   */
  margin: 14px 0 22px;
  /*
   * `display: block`, because the theme's notice rule makes this a flex row —
   * which turned the card into a flex item that shrank to its content and sat
   * against the left edge instead of spanning the container.
   */
  display: block;
}
.woocommerce-message:has(.as-added)::before,
.single-product .woocommerce-message:has(.as-added)::before,
.as-route-cart .woocommerce-message:has(.as-added)::before,
.as-route-checkout .woocommerce-message:has(.as-added)::before { content: none; }

.as-added {
  display: flex;
  align-items: center;
  gap: var(--space-3);
  background: var(--color-surface, #FFFFFF);
  border-radius: var(--radius-md, 14px);
  box-shadow: 0 6px 18px rgba(36, 41, 56, .1);
  padding: 12px 14px 12px 12px;
}

.as-added__tick {
  width: 32px;
  height: 32px;
  border-radius: 50%;
  flex: none;
  display: grid;
  place-items: center;
  background: var(--color-positive);
  color: var(--color-text-invert);
}

.as-added__what { display: flex; flex-direction: column; flex: 1; min-width: 0; }
.as-added__what strong { font-size: var(--text-sm); font-weight: 700; color: var(--color-text); }

/* The one line that can run long. */
.as-added__detail {
  font-size: var(--text-xs);
  color: var(--color-text-muted, #555B68);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}

.as-added__stay {
  flex: none;
  font-size: var(--text-sm);
  font-weight: 700;
  color: var(--color-text);
  text-decoration: none;
}
.as-added__stay:hover { color: var(--atomic-blue, #1AB0E0); }

/* .as-btn carries the shape; only the size is this card's own. */
.as-added__go { flex: none; min-height: 0; padding: 10px 20px; font-size: var(--text-sm); }

/*
 * ─── 2g · WE COULDN'T ADD THAT ──────────────────────────────────────────────
 *
 * Same card, red mark, one row per reason with its own fix where we raised it.
 */
.woocommerce-error:has(.as-cart-error),
.single-product .woocommerce-error:has(.as-cart-error),
.as-route-cart .woocommerce-error:has(.as-cart-error),
.as-route-checkout .woocommerce-error:has(.as-cart-error) {
  background: none;
  border: 0;
  padding: 0;
  margin: 0 0 22px;
  list-style: none;
}
.woocommerce-error:has(.as-cart-error)::before,
.single-product .woocommerce-error:has(.as-cart-error)::before,
.as-route-cart .woocommerce-error:has(.as-cart-error)::before,
.as-route-checkout .woocommerce-error:has(.as-cart-error)::before { content: none; }

.as-cart-error {
  display: flex;
  align-items: flex-start;
  gap: var(--space-3);
  background: var(--color-surface, #FFFFFF);
  border-radius: var(--radius-md, 14px);
  box-shadow: 0 6px 18px rgba(36, 41, 56, .1);
  padding: 14px 16px;
}

.as-cart-error__mark {
  width: 32px;
  height: 32px;
  border-radius: 50%;
  flex: none;
  display: grid;
  place-items: center;
  background: #C2372B;
  color: #FFFFFF;
  font-weight: 800;
}

.as-cart-error__body { flex: 1; min-width: 0; display: flex; flex-direction: column; gap: var(--space-2); }
.as-cart-error__head { font-size: var(--text-sm); font-weight: 700; color: var(--color-text); }

.as-cart-error__rows {
  margin: 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  border-top: 1px solid rgba(45, 56, 75, .1);
}
.as-cart-error__rows li {
  display: flex;
  justify-content: space-between;
  gap: var(--space-3);
  padding: 7px 0;
  border-bottom: 1px solid rgba(45, 56, 75, .1);
  font-size: var(--text-xs);
  color: var(--color-text);
}
.as-cart-error__rows a { font-weight: 700; flex: none; }

/*
 * ─── NO WOO PURPLE, DISABLED INCLUDED ───────────────────────────────────────
 *
 * Section Y: "No Woo-purple buttons anywhere."
 *
 * The live button was already the shop's blue, but nothing covered :disabled —
 * so the moment the sticker gate started disabling it, Woo's own purple came
 * through at half opacity. A state nobody had styled, because until there was
 * a gate nothing ever reached it.
 *
 * Outlined rather than filled-and-greyed, matching the sign uploader's CTA:
 * a grey fill reads as a broken button, an outline reads as one that is
 * waiting — and on these pages the line above it says what for.
 */
.woocommerce .single_add_to_cart_button:disabled,
.woocommerce .single_add_to_cart_button.disabled,
.single-product .single_add_to_cart_button:disabled,
.single-product .single_add_to_cart_button.disabled {
  background: var(--color-surface, #FFFFFF);
  border: 1.5px solid rgba(45, 56, 75, .18);
  color: var(--color-text-muted, #9AA0AD);
  opacity: 1;
  cursor: not-allowed;
}
.woocommerce .single_add_to_cart_button:disabled:hover,
.single-product .single_add_to_cart_button:disabled:hover {
  background: var(--color-surface, #FFFFFF);
  border-color: rgba(45, 56, 75, .18);
}

/*
 * ─── THE FAQ ROW ────────────────────────────────────────────────────────────
 *
 * One question per row: a hairline between rows, the question bold at body-lg,
 * a blue + that turns to − when open, the answer muted beneath. The sticker
 * product pages' accordion (.as-pdp-info, as_product_info()) drew it first; the
 * category pages' FAQ (as_cat_faq()) and /faq/ (template-faq.php) wore
 * bordered boxes with a chevron until Dennis asked for this look on them too
 * (2026-11-14). Each renderer keeps its own class names and lists them here,
 * so it is one recipe, not three. It lives in primitives because the routes
 * load different sheets.
 *
 * /faq/ differs in two ways, both in route-info.css: its question is a
 * <button aria-expanded> rather than a <summary> (its search and tabs drive
 * it), so the button reset is there; and its search hides rows, so each row
 * carries its own bottom hairline instead of relying on :last-child.
 */
.as-pdp-info__item,
.as-cat-faq__item { border-top: 1px solid var(--color-border-soft); }
.as-pdp-info__item:last-child,
.as-cat-faq__item:last-child { border-bottom: 1px solid var(--color-border-soft); }
.as-pdp-info__item summary,
.as-cat-faq__item summary,
.as-faq__q {
	display: flex; align-items: center; justify-content: space-between; gap: var(--space-5);
	padding: 20px 0; cursor: pointer;
	list-style: none; /* Safari draws its own marker without this. */
	font-weight: 700; font-size: var(--text-body-lg); letter-spacing: -0.01em;
}
.as-pdp-info__item summary::-webkit-details-marker,
.as-cat-faq__item summary::-webkit-details-marker { display: none; }
.as-pdp-info__mark,
.as-cat-faq__mark,
.as-faq__mark { color: var(--atomic-blue); font-size: var(--text-h3); font-weight: 700; line-height: 1; flex: none; }
.as-pdp-info__mark::before,
.as-cat-faq__mark::before,
.as-faq__mark::before { content: "+"; }
.as-pdp-info__item[open] .as-pdp-info__mark::before,
.as-cat-faq__item[open] .as-cat-faq__mark::before,
.as-faq__q[aria-expanded="true"] .as-faq__mark::before { content: "−"; }
.as-pdp-info__a,
.as-cat-faq__a,
.as-faq__a { font-size: var(--text-sm); line-height: 1.7; color: var(--color-text-muted); padding-bottom: 22px; max-width: 70ch; }
.as-pdp-info__a p,
.as-cat-faq__a p,
.as-faq__a p { margin: 0 0 12px; }
.as-pdp-info__a p:last-child,
.as-cat-faq__a p:last-child,
.as-faq__a p:last-child { margin-bottom: 0; }
/* A link in an answer ("email us at info@…", "see our shipping page") read as
   plain grey text. Underlined in the body's ink, the way the compare table's
   cell links are, rather than a third colour in a muted paragraph. */
.as-pdp-info__a a,
.as-cat-faq__a a,
.as-faq__a a {
	color: var(--color-text); font-weight: 600;
	text-decoration: underline; text-underline-offset: 2px; text-decoration-thickness: 1px;
}
