/* ------------------------------------------------------------------------
   FONTS.  Nothing is hotlinked: Fira is served from assets/fonts/, and
   museo-sans is substituted by the publisher's OWN declared fallback face
   (metric-adjusted Arial), copied verbatim from
   _source/target-capture/theme-2026-11-04.css.

   The Fira weight slots below are the PUBLISHER'S mapping, not Google's:
   their SemiBold file (= Fira 600) is declared at font-weight 700, and they
   ship no upright 800. That is why .content-title's font-weight:800 renders
   SemiBold on the live page, and why reproducing the mapping -- rather than
   changing the weight numbers in the rules below -- is what matches it.
   Do not add an 800 face.
   ------------------------------------------------------------------------ */

@font-face{font-display:swap;font-family:"Fira Sans Extra Condensed";font-style:normal;font-weight:400;src:url(assets/fonts/FiraSansExtraCondensed-Regular.woff2) format("woff2")}
@font-face{font-display:swap;font-family:"Fira Sans Extra Condensed";font-style:normal;font-weight:500;src:url(assets/fonts/FiraSansExtraCondensed-Medium.woff2) format("woff2")}
@font-face{font-display:swap;font-family:"Fira Sans Extra Condensed";font-style:normal;font-weight:700;src:url(assets/fonts/FiraSansExtraCondensed-SemiBold.woff2) format("woff2")}

/* Fira's metric fallback, verbatim from the publisher (local Trebuchet MS). */
@font-face{ascent-override:112.5095%;descent-override:31.8877%;font-display:swap;font-family:"Fira Sans Extra Condensed Fallback";font-style:normal;font-weight:400;size-adjust:83.1041%;src:local("Trebuchet MS")}
@font-face{ascent-override:112.5095%;descent-override:31.8877%;font-display:swap;font-family:"Fira Sans Extra Condensed Fallback";font-style:normal;font-weight:500;size-adjust:83.1041%;src:local("Trebuchet MS")}
@font-face{ascent-override:112.5095%;descent-override:31.8877%;font-display:swap;font-family:"Fira Sans Extra Condensed Fallback";font-style:normal;font-weight:700;size-adjust:83.1041%;src:local("Trebuchet MS")}

/* museo-sans is licensed and cannot ship. The publisher's own fallback face
   carries Museo Sans metrics on Arial; all ten slots are reproduced so a
   300-weight paragraph and a 700-weight <strong> each resolve to a real face
   instead of being synthesised. The local() sources are the publisher's, and
   so is the asymmetry: only normal 700 and normal 900 use "Arial Bold".
   There is deliberately NO 400 slot -- CSS resolves weight 400 up to the 500
   slot, which is the live behaviour. Do not add one.

   ONE DELIBERATE DEPARTURE from the publisher's text: their italic slots are
   all src:local("Arial") -- an UPRIGHT face. On their page that never shows,
   because the real museo-sans italic always arrives and replaces it. Here the
   fallback IS the final face, so declaring an italic @font-face backed by
   upright Arial makes the browser match a "real" italic and never synthesise
   one: the affiliate disclaimer rendered upright where the live page is
   plainly italic (verified against the reference render of the publisher's
   own markup + stylesheet). The italic slots therefore take italic local()
   sources, mirroring their own normal-weight Arial/Arial Bold split. The
   metric overrides are untouched. */
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:normal;font-weight:100;size-adjust:104.2716%;src:local("Arial")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:italic;font-weight:100;size-adjust:104.2716%;src:local("Arial Italic")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:normal;font-weight:300;size-adjust:104.2716%;src:local("Arial")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:italic;font-weight:300;size-adjust:104.2716%;src:local("Arial Italic")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:normal;font-weight:500;size-adjust:104.2716%;src:local("Arial")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:italic;font-weight:500;size-adjust:104.2716%;src:local("Arial Italic")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:normal;font-weight:700;size-adjust:104.2716%;src:local("Arial Bold")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:italic;font-weight:700;size-adjust:104.2716%;src:local("Arial Bold Italic")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:normal;font-weight:900;size-adjust:104.2716%;src:local("Arial Bold")}
@font-face{ascent-override:85.5544%;descent-override:22.0091%;font-display:swap;font-family:"museo-sans fallback";font-style:italic;font-weight:900;size-adjust:104.2716%;src:local("Arial Bold Italic")}

/* ------------------------------------------------------------------------
   A360 article replica — Us Weekly "Rich Mom Fashion Deals"
   Every value below was measured off the live page with getComputedStyle;
   nothing here is estimated. See README.md for the one substitution
   (Museo Sans -> the publisher's own metric-adjusted fallback face, a
   licensing constraint; see the FONTS block above).
   ------------------------------------------------------------------------ */

:root {
  /* color */
  --ink:        #000000;   /* headlines, bold lead-ins, related titles */
  --meta:       #767676;   /* byline, date */
  --accent:     #e70074;   /* links, kicker, "Related:" badge */
  --accent-rule:#ec2b8c;   /* 2px rule on top of the footer */
  --rule:       #d5d5d5;   /* disclaimer hairlines */
  --disc-bg:    #f9f9f9;   /* disclaimer background */
  --page:       #ffffff;

  /* type */
  /* The publisher's own two stacks, plus a tail: their fallback faces are
     sourced from local() fonts that are not present on every machine. Every
     name in each tail is metric-compatible with the one it follows, so the
     size-adjust/ascent-override numbers stay meaningful. */
  --display: "Fira Sans Extra Condensed", "Fira Sans Extra Condensed Fallback", "Trebuchet MS", sans-serif;
  --text:    "museo-sans fallback", Arial, Helvetica, "Liberation Sans", Arimo, sans-serif;
}

*, *::before, *::after { box-sizing: border-box; }

html { -webkit-text-size-adjust: 100%; }

body {
  margin: 0;
  background: var(--page);
  font-family: var(--text);
  font-size: 16px;
  line-height: 28.48px;
  /* No -webkit-font-smoothing: the publisher applies `antialiased` to their
     three icon fonts only, never to text. On body it switched macOS to
     grayscale antialiasing and thinned every glyph by ~7%, which is what
     made the page read grey while getComputedStyle still said #000. */
}

/* --- header ----------------------------------------------------------- */

.kicker {
  /* Live `.article-head .article-type` margin-bottom is 10px at EVERY width:
     .9090909091em against its 11px base font, .5em against the 2em (20px)
     font it takes at min-width:48em. The replica's 6px pulled the headline --
     and with it the hero, the credit, the disclaimer and every paragraph --
     4px up the page. */
  margin: 0 0 10px;
  font-family: var(--display);
  font-size: 22px;
  font-weight: 500;
  line-height: 20.02px;
  letter-spacing: 0.3px;
  text-transform: uppercase;
}
.kicker a { color: var(--accent); text-decoration: none; }
.kicker a:hover { text-decoration: underline; }

.content-title {
  margin: 0;
  color: var(--ink);
  font-family: var(--display);
  font-size: 56px;
  font-weight: 800;
  line-height: 58.8px;
}

.content-subtitle {
  margin: 15px 0 30px;
  color: var(--ink);
  font-family: var(--text);
  font-size: 21px;
  font-weight: 400;
  line-height: 29.4px;
}

/* The byline row (.meta) is styled in "STICKY CHROME + BYLINE" at the foot of
   this file; the old flex rule here set a 14px gap that suppressed the "|"
   separator. The .share / .share__btn rules went with the share icons, which
   the live page does not carry in this row at all. */

/* --- hero ------------------------------------------------------------- */

.item-figure { margin: 0 0 30px; }
.ratio { position: relative; width: 100%; overflow: hidden; background: #efefef; }
.ratio > img {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  display: block;
}
.credit {
  margin-top: 8.06px;
  color: var(--ink);
  font-family: var(--text);
  font-size: 13px;
  font-weight: 300;
  line-height: 17.94px;
}

/* The live figcaption.credit stays #000 and holds an inner <span class="credit">
   that the theme recolours and insets:
     .post-main .lead .credit > .credit { color:#595959; margin:.05em .5em }
   Measured live: ink rgb(89,89,89) starting 8px in from the column edge. */
.credit > span {
  color: #595959;
  margin: 0.05em 0.5em;
}

/* --- affiliate disclaimer --------------------------------------------- */

.disclaimer {
  margin: 30px 0;
  padding: 15px 25px;
  /* All four sides: the theme declares `border:1px solid #d5d5d5`, so the box
     has left and right edges too. Height is unaffected -- 61px either way. */
  border: 1px solid var(--rule);
  background: var(--disc-bg);
  /* 16px / 22.4px / 300 / #5c5c5c is restated in the ARTICLE TYPOGRAPHY
     carve-out, under the renamed --disclaimer-ink token. */
}

/* --- article body ----------------------------------------------------- */

/* Body copy, bold lead-ins, lists, h3/h4 and body links are all set in the
   ARTICLE TYPOGRAPHY section at the foot of this file. The rules that used to
   sit here were built from the DISCLAIMER's 16px/28.48px/#5c5c5c, which is the
   wrong element — see that section's header. */

.article-content h2 {
  margin: 32px 0;
  color: var(--ink);
  font-family: var(--display);
  font-size: var(--h2-size);
  font-weight: 700;
  line-height: var(--h2-leading);
  letter-spacing: 0.3px;
  /* The live article carries style="text-align: center" inline on this h2 --
     an editorial choice stored in the WordPress content, not a theme rule.
     Declared here so the locked .article-content markup stays untouched. */
  text-align: center;
}

.article-content i, .article-content em { font-style: italic; }

/* --- focus visibility (added; the original has no visible focus ring) - */

a:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 2px;
  border-radius: 2px;
}

/* --- mobile ----------------------------------------------------------- */

/* The live page switches these three at three DIFFERENT widths, not one:
   .content-subtitle below 48em (768px), .content-title and .kicker below
   30em (481px). The old single 669px block moved all three at once, which
   left the kicker and headline small across 481-669 and the dek large across
   670-767. .article-content h2 is dropped: its override only restated the
   same two custom properties the base rule already uses. */

@media (max-width: 767px) {
  .content-subtitle { font-size: 19px; line-height: 26.6px; }
}

@media (max-width: 480px) {
  .content-title { font-size: 38px; line-height: 39.9px; }
  .kicker { font-size: 15.4px; font-weight: 800; line-height: 17.556px; }
}

/* ========================================================================
   SITE CHROME — the global header bar
   Merged in from the former partials/ directory (header.html, header.css),
   which was deleted once its content landed in index.html and in this file.
   Measurements come from _source/header.json, captured at viewport 1024.

   This replica mimics only the article surface, so the bar carries the Us
   logo and nothing else: the live page's section nav, hamburger panel and
   Subscribe/search/account toolbar are not reproduced, and neither is the
   right rail or the pink section sub-nav that used to follow this section.
   The bar's own box — 60px (50px below 669px) and the #e1e1e1 hairline —
   is the live page's and is unchanged.
   ======================================================================== */

/* The page shell — container steps, the full-width headline block and the
   centred article column — is in the PAGE LAYOUT section at the foot of this
   file. scroll-padding-top lives in STICKY CHROME. */

/* ------------------------------------------------------------------------
   Global site header — scoped entirely under .site-header
   Markup: the <header class="site-header"> block at the top of index.html.

   Every value is taken from _source/header.json (header.header captured
   2026-11-03 @ viewport 1024) and reuses the tokens already declared in
   styles.css: --display, --ink, --page, --rule, --accent.
   Nothing here touches the article's own selectors.
   ------------------------------------------------------------------------ */

.site-header {
  /* rgb(225,225,225) hairline from the live box-shadow; no global token exists for it */
  --site-header-hairline: #e1e1e1;
  --site-header-height: 60px;

  position: sticky;
  top: 0;
  z-index: 1500000;
  height: var(--site-header-height);
  background: var(--page);
  box-shadow:
    var(--site-header-hairline) 0 1px 0 0,
    rgba(0, 0, 0, 0.05) 0 2px 4px 0;
  font-family: var(--display);
}

/* Live `.header .container-full` has a FOUR-step side padding ladder and a
   max-width of 140em resolved against .header's own font-size, which the theme
   steps 15 / 16 / 19 / 20px at base / 23.4375em / 48em / 75em -- so the cap is
   2100 / 2240 / 2660 / 2800px, not a flat 2660. Both ladders are written in px
   because nothing else in this bar is sized in em. */

.site-header__container {
  display: flex;
  align-items: center;
  justify-content: space-between;
  height: var(--site-header-height);
  max-width: 2100px;
  margin: 0 auto;
  padding: 0 8px;
}

@media (min-width:  375px) { .site-header__container { max-width: 2240px; padding: 0 12px; } }
@media (min-width:  768px) { .site-header__container { max-width: 2660px; padding: 0 20px; } }
@media (min-width: 1200px) { .site-header__container { max-width: 2800px; } }
@media (min-width: 1400px) { .site-header__container { padding: 0 40px; } }

/* --- the logo ---------------------------------------------------------- */

/* No `gap`: the live .header-main's 20px gap separated the logo from the nav,
   and this bar now has a single child. Its `padding-left` ladder (34 / 40 /
   50px) went the same way -- every step of it was clearance for the
   `position:absolute; left:0; width:34px` hamburger, which is not reproduced,
   so the logo belongs on the container's own padding edge. */

.site-header__main {
  display: flex;
  align-items: center;
  height: var(--site-header-height);
  min-width: 0;
}

.site-header__logo {
  display: flex;
  flex: 0 0 auto;
  align-items: center;
  line-height: 0;
  text-decoration: none;
  width: 60px;         /* live `.header-logo`; the ladder is in the two
                          max-width blocks below, never on the graphic */
}

/* Live `.header-logo` -- the ANCHOR, not the graphic -- is what carries the
   width ladder: 50px base, 40px at max-width 21.25em (340), 60px at
   min-width 48em. The theme never gives the SVG a CSS width, so its
   `width="60" height="47"` attributes govern at every viewport and below
   768px the 60x47 mark simply OVERFLOWS the narrower link box. Reproduced the
   same way round below: the ladder is on .site-header__logo and .us-logo's box
   is fixed. Hanging the ladder on the graphic instead shrank the mark to
   50x39.2 / 40x31.3 -- 83% of the live size in both axes -- and on a bar that
   now carries nothing else, the mark IS the mobile header. */
.site-header__logo .us-logo {
  display: block;
  flex: 0 0 auto;
  width: 60px;
  height: 47px;        /* the SVG's own intrinsic box; never scaled */
}

/* --- focus visibility (the original header has no visible focus ring) -- */

.site-header a:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 2px;
  border-radius: 2px;
}

/* --- narrow widths ---------------------------------------------------- */
/* Live `.header{height:50px}` is the BASE value and 60px arrives at
   min-width:48em, so the short bar runs all the way to 767px -- not to 669px,
   which was never one of the publisher's breakpoints. Only the link box steps;
   the mark stays 60x47 and overhangs it, which is what the live page does. */

@media (max-width: 767px) {
  .site-header { --site-header-height: 50px; }
  .site-header__logo { width: 50px; }   /* the 60x47 mark overflows it, as live */
}

@media (max-width: 340px) {
  .site-header__logo { width: 40px; }   /* ditto, 20px of overflow */
}

/* ========================================================================
   ARTICLE TYPOGRAPHY  —  defects 1 and 2 (font, font colour, "zoom")

   ORDER-SENSITIVE: this section and the two below must stay at the foot of
   this file, after every rule and @media block above. Four rules here
   (.article-content, .article-content > p a, .disclaimer, body) tie on
   specificity with rules that remain above or with the UA sheet, and win
   only by coming later.

   Root cause of defects 1 and 2: the replica's body copy was built from the
   affiliate DISCLAIMER's typography (16px / 28.48px / #5c5c5c). The live
   article's body paragraphs are 18px / 1.78 (= 32.04px) / weight 300 / #000,
   margin-bottom 21px — confirmed identical at all ten measured viewport
   widths (_source/layout-spec.json -> body_copy_invariant). 16px against an
   18px baseline is what reads as a different zoom level.

   Museo Sans stays substituted via --text (licensing): the publisher's own
   metric-adjusted fallback face, declared in the FONTS block at the top of
   this file. Only size, weight, line-height and colour are matched here.
   ===================================================================== */

:root {
  /* body copy — the live article's real values */
  --body-size:    18px;
  --body-leading: 1.78;    /* 1.78 x 18px = 32.04px, as measured */
  --body-space:   21px;    /* authored 1.16667em; 21px at 18px */

  /* section headings inside the article body */
  --h2-size:      38px;
  --h2-leading:   1.05;    /* 39.9px */
  --h3-size:      35px;
  --h3-leading:   1.11;    /* 38.85px */

  /* The grey formerly called --body. It is NOT body copy: the affiliate
     disclaimer is the only place it is correct. Renamed so the token can no
     longer be mistaken for article text again. */
  --disclaimer-ink: #5c5c5c;
}

/* Nothing on the page should default to the disclaimer grey. Every element
   that shows text declares its own colour, so this only changes stray text
   nodes — but it stops #5c5c5c being the page-wide default for "text". */
body {
  color: var(--ink);
}

/* --- article body copy -------------------------------------------------
   Child selectors (`>`) throughout, not descendant selectors: the markup
   puts div.disclaimer inside .article-content (and used to put the two
   aside.related strips there as well, before they were stripped out), so a
   descendant selector leaks straight into anything nested there.
   Every real body element is a direct child of .article-content, so `>`
   gives exactly the body copy and nothing else. Keep it that way if a
   nested block is ever reintroduced.
   ---------------------------------------------------------------------- */

.article-content {
  font-size: var(--body-size);
  line-height: var(--body-leading);
}

.article-content > p {
  margin: 0 0 var(--body-space);
  color: var(--ink);
  font-family: var(--text);
  font-size: var(--body-size);
  font-weight: 300;
  line-height: var(--body-leading);
}

/* The bold lead-in of each numbered pick: same 18px and same line box,
   weight 700. Unitless --body-leading means <strong> recomputes to the
   identical 32.04px instead of inheriting a stale pixel value. */
.article-content > p strong,
.article-content > ul strong,
.article-content > ol strong {
  color: var(--ink);
  font-size: var(--body-size);
  font-weight: 700;
  line-height: var(--body-leading);
}

/* Lists: body-copy type, live margins 0 0 1.5em 3em (27px / 54px at 18px).
   This article's frozen content has no <ul>/<ol>, so these rules are inert
   here; they are included so list copy cannot regress to the 16px values. */
.article-content > ul,
.article-content > ol {
  margin: 0 0 1.5em 3em;
  padding: 0;
  color: var(--ink);
  font-family: var(--text);
  font-size: var(--body-size);
  font-weight: 300;
  line-height: var(--body-leading);
}

.article-content > ul li,
.article-content > ol li {
  color: var(--ink);
  font-size: var(--body-size);
  font-weight: 300;
  line-height: var(--body-leading);
}

/* --- headings inside the article body ---------------------------------
   h2 (38px / 1.05 / 700 / .3px / #000) already matched the spec further up
   this file and is left alone there. h3 and h4 were missing entirely; they
   take the same display face, weight, colour and letter-spacing as h2 at
   35px / 1.11. Both are inert in this article: the body copy has no h3 or
   h4 of its own.
   ---------------------------------------------------------------------- */

.article-content > h3,
.article-content > h4 {
  margin: 32px 0;
  color: var(--ink);
  font-family: var(--display);
  font-size: var(--h3-size);
  font-weight: 700;
  line-height: var(--h3-leading);
  letter-spacing: 0.3px;
}

/* --- links in body copy ------------------------------------------------
   Replaces the deleted `.article-content a`, which was too broad: it reached
   every link nested anywhere inside the block. Scoped to body copy plus the
   one disclaimer link.
   ---------------------------------------------------------------------- */

.article-content > p a,
.article-content > ul a,
.article-content > ol a,
.disclaimer a {
  color: var(--accent);
  text-decoration: underline;
  text-decoration-color: var(--accent);
}

.article-content > p a {
  font-weight: 300;
}

/* An anchor nested INSIDE the bold lead-in keeps the lead-in's weight.
   `.article-content > p strong` and `.article-content > p a` both score
   (0,1,2), so the tie breaks on source order and the link rule above wins --
   which renders an <a> inside a <strong> at 300 where the publisher sets it
   bold. The petite article's two UsNow promo paragraphs are exactly
   <p><strong><a>..</a> ..</strong></p>, so they need this. (0,1,3) settles it
   without disturbing either rule above.
   This is the ONLY rule this stylesheet gained for the second article. */
.article-content > p strong a {
  font-weight: 700;
}

/* No :hover rule for body links. They are already underlined at rest
   (.single .article-content a), and the only hover rules that reach them on
   the live page are `body a:hover` / `.post-main a:hover`, both of which just
   re-declare `text-decoration: underline` -- so hovering is a no-op there.
   The replica's old `text-decoration-thickness: 2px` was invented; the string
   does not occur anywhere in the 306 KB theme stylesheet. */

/* --- CARVE-OUT: the affiliate disclaimer ------------------------------
   16px / 22.4px / weight 300 / #5c5c5c is correct for this block and this
   block only. Values are unchanged from the old .article-content p rule;
   they are restated here solely so the renamed token has a home and the old
   --body reference could be deleted. Do not fold these numbers back into
   any body-copy rule.
   ---------------------------------------------------------------------- */

.disclaimer {
  color: var(--disclaimer-ink);
  font-size: 16px;
  /* Live: `body.single .shop-with-us__disclaimer p { font-style: italic }`. */
  font-style: italic;
  font-weight: 300;
  /* no line-height: inherits the unitless 1.78 from .article-content, which
     resolves to the live page's measured 28.48px at this 16px size. The
     wrapper's own `line-height:1.4` in the theme is a decoy -- the nested <p>
     takes 1.78 from .article-content p, and 1.4 shortens the measured 61px
     box to 54px. Both pages measure 61px border to border. */
}

/* No viewport override for body copy: a >200-character body paragraph
   measured 18px / 32.04px / 300 / #000 at every one of the ten widths
   probed on the live page, so the size must not change on phones. */


/* ========================================================================
   PAGE LAYOUT  —  the fluid container and the centred article column

   Replaces the replica's fixed 610 + 20 + 300 shell with the live page's
   responsive model. Every number below is measured, from
   _source/layout-spec.json (10 emulated widths, getBoundingClientRect +
   getComputedStyle, plus the authored rules read out of document.styleSheets).

   The live page's own CSS is written in em against a 10px <body>, while its
   MEDIA QUERIES resolve em against the initial 16px. Those em breakpoints are
   therefore restated here as the px widths they actually match:
       64em = 1024   79.9375em = 1279   80em = 1280
       82.5em = 1320   87.5em = 1400    30.0625em = 481   63.9375em = 1023
       42.5em = 680
   Do NOT set html{font-size:10px} to "fix" the em arithmetic: :root is 16px
   on the live page too (layout-spec corrections_to_parent_spec #1).

   Measured layout table (viewport px -> container / article column):
       <=480      viewport   full bleed, column = 100%
       481-1023   728        column = 100%
       1024-1279  940        610
       1280-1319 1180        820
       1320-1399 1300        970
       1400+     1330        970
   The article column is authored as calc(100% - 330px) / calc(100% - 360px),
   which is how the live page arrives at those widths.

   ONE DELIBERATE DIVERGENCE: the live page's 300px right rail is not
   reproduced. On the live page the headline block spans the whole container
   and the article column sits at the container's left edge, with the rail
   filling the 330/360px gap on the right — so both start at the same x
   (55 at 1440, 10 at 1320, 42 at 1024). Delete the rail and that geometry
   leaves the article hard left under a headline 360px wider than it, with a
   10px gutter at 1320. So the headline block is narrowed to the ARTICLE
   COLUMN's width and both are centred together: `.content-head` and
   `.center-rail` share one width and one pair of auto margins, which keeps
   the live page's "same x" relationship and reads as a deliberate centred
   article instead of a page with a hole in it.

   The body column keeps the measured 610 / 820 / 970, so every line break in
   the article body is still the live page's. The HEADLINE BLOCK's measure is
   the one thing that changes: kicker, h1, dek and byline now set to 610/820/
   970 rather than 940/1180/1300, so the h1 wraps to more lines than the live
   page at desktop widths. That is the cost of the divergence and it is
   deliberate — see README.md "Known deltas".
   ===================================================================== */

:root {
  /* container steps */
  --container-base: 1260px;   /* <=480px: 126em, viewport-limited  */
  --container-sm:    728px;   /* 481-1023   : 72.8em               */
  --container-md:    940px;   /* 1024-1279  : 94em                 */
  --container-lg:   1180px;   /* 1280-1319  : 118em                */
  --container-xl:   1300px;   /* 1320-1399  : 130em                */
  --container-xxl:  1330px;   /* 1400+      : 133em                */

  /* vertical rhythm of the headline block */
  --head-gap:         30px;   /* .content-head margin-bottom, >=681px (3em) */
  --head-gap-sm:      20px;   /* .content-head margin-bottom, <=680px       */
  --head-top-sm:      19px;   /* .content-head margin-top,    <=680px       */

  /* side insets below 42.5em, where the container itself is full-bleed */
  --page-gutter:      30px;   /* section.content-rail padding / head children */
  --kicker-gutter:    33px;   /* the kicker sits at x=33, not x=30            */

  /* Tail of the article shell. ZERO on purpose: the theme authors nothing at
     this seam, and the one live-authored number governing it is
     .footer{margin-top:5em} = 50px, which .site-footer already carries. The
     replica's old 80px had no counterpart upstream and, being the larger of
     the two adjoining margins, swallowed the footer's own 50px. */
  --page-bottom:      0;
}

/* --- the centred container --------------------------------------------
   `margin: auto` alone centres it: the live .site-container has NO
   horizontal padding at any width. At 1320 that leaves a 2.5px side gutter
   and at 375 none at all — adding a minimum gutter here would make every
   width wrong (layout-spec site_container_authored.no_horizontal_padding).
   Ranges are written non-overlapping so the cascade order does not matter.
   ---------------------------------------------------------------------- */

.site-container {
  width: 100%;
  max-width: var(--container-base);
  margin: 0 auto;
}

@media (min-width: 481px)  and (max-width: 1023px) { .site-container { max-width: var(--container-sm); } }
@media (min-width: 1024px) and (max-width: 1279px) { .site-container { max-width: var(--container-md); } }
@media (min-width: 1280px) and (max-width: 1319px) { .site-container { max-width: var(--container-lg); } }
@media (min-width: 1320px) and (max-width: 1399px) { .site-container { max-width: var(--container-xl); } }
@media (min-width: 1400px)                         { .site-container { max-width: var(--container-xxl); } }

/* --- the article shell ------------------------------------------------
   <article class="post"> is kept as an unstyled semantic wrapper around the
   container; it must carry no width, padding or margin of its own.
   ---------------------------------------------------------------------- */

/* Live article.post-main: margin-top 2em (20px) base, 5em (50px) at
   min-width:48em. The 50px is the whole correct gap on the trimmed page --
   the extra ~93px above the live eyebrow was the empty #global-alert plus the
   pink section sub-menu, both of which are deleted chrome, not a stale
   offset. .content-head's own --head-top-sm (19px) collapses into the 20px
   below 768, exactly as it does upstream. */

.post {
  margin: 50px 0 0;
  padding: 0;
}

@media (max-width: 767px) {
  .post { margin-top: 20px; }
}

/* --- headline block: above the article column -------------------------
   Live: header.content-head.site-container, width 100%, padding 0 at every
   width, margin-bottom 3em (30px) at >=47.9375em. It is NOT part of the row
   below it (layout-spec railStartsLevelWith), which is why the live page can
   keep it at full container width while the article column narrows.

   Below 1024px the container IS the column, so 100% is both the live value
   and the right one. From 1024 up it is narrowed to the column width and
   centred with it — see the DIVERGENCE note at the top of this section.
   ---------------------------------------------------------------------- */

.content-head {
  width: 100%;
  margin: 0 auto var(--head-gap);
  padding: 0;
}

/* --- the article row --------------------------------------------------
   Live: div.content-inner.site-container, display:flex. With the rail gone
   it holds a single child, so it stays a flex column at every width and the
   column centres itself with auto side margins.
   ---------------------------------------------------------------------- */

.content-grid {
  display: flex;
  flex-direction: column;
  flex-wrap: nowrap;
  padding: 0;
  margin-bottom: var(--page-bottom);
}

.center-rail {
  width: 100%;
  min-width: 0;        /* lets the column shrink under wide content */
  margin: 0 auto;      /* centred: the live page's rail is not reproduced */
  padding: 0;
}

/* The inset is what the live page authors; it is kept so the column lands on
   the measured 610 / 820 / 970 and the line breaks do not move. Below 1024px
   the column is the full container width, as on the live page.

   The inset is declared on .site-container, not on .content-grid, because the
   headline block is a SIBLING of the row and has to read the same number.
   Custom properties inherit, so .center-rail still resolves it through
   .content-grid exactly as before. One declaration, two users, no chance of
   the two drifting apart — which is precisely how the 180px step at 1440 and
   the 165px step at 1320/1024 got in. */

@media (min-width: 1024px) {
  .site-container { --center-rail-inset: 330px; }                  /*  940 - 330 = 610 */

  .content-head,
  .center-rail {
    width: calc(100% - var(--center-rail-inset));
    margin-left: auto;
    margin-right: auto;
  }
}

@media (min-width: 1280px) {
  .site-container { --center-rail-inset: 360px; }   /* 1180 - 360 = 820 */
}

@media (min-width: 1320px) {
  .site-container { --center-rail-inset: 330px; }   /* 1300 - 330 = 970 */
}

@media (min-width: 1400px) {
  .site-container { --center-rail-inset: 360px; }   /* 1330 - 360 = 970 */
}

/* --- side gutters below the desktop band ------------------------------
   Below 768px the container goes full-bleed and the live page insets each
   piece individually -- and it does NOT do so at one width. The replica used
   to switch everything at 680px, which left the body column and the dek
   running edge to edge across the whole 681-767 band. The publisher's own
   ladder, reproduced step for step:

     element            inset   from the theme
     ---------------    -----   ---------------------------------------------
     .content-rail      10px    padding: 0 1em           base (<340)
          ″             30px    padding: 0 3em           min-width: 21.25em
          ″              0      padding: 0               min-width: 48em
     .article-type      33px    padding: 0 3em  x 11px   max-width: 42.5em
          ″             11px    padding: 0 1em  x 11px   max-width: 21.1875em
     .content-title     44.2px  padding: 0 .789em x 56px max-width: 42.5em
          ″             30px    the same ratio x 38px    (the font drops at 30em)
          ″             10px    padding: 0 .263em x 38px max-width: 21.1875em
     .content-subtitle  30px    padding: 0 1.579em x 19px base, cancelled at 48em
     .content-head-info 30px    padding: 0 3em  x 10px   max-width: 42.5em
          ″             10px    padding: 0 1em  x 10px   max-width: 21.1875em

   So the 681-767 band is genuinely inconsistent upstream: the dek and the
   body column stay inset 30px there while the kicker, headline and byline go
   flush. That is reproduced rather than tidied -- this is a replica, not a
   redesign. The headline's two insets are authored in em against its own
   font-size, as the theme does, so they follow the 56px -> 38px step on their
   own instead of needing a second breakpoint.
   ---------------------------------------------------------------------- */

@media (max-width: 767px) {
  /* live .post-main .content-head: margin-bottom 2em base, 3em at 47.9375em */
  .content-head {
    margin-top: var(--head-top-sm);
    margin-bottom: var(--head-gap-sm);
  }

  .content-subtitle { padding: 0 1.5789473684em; }   /* 30px at its 19px */

  .center-rail {
    padding-left: var(--page-gutter);
    padding-right: var(--page-gutter);
  }
}

@media (max-width: 680px) {
  .content-head > .kicker {
    padding-left: var(--kicker-gutter);
    padding-right: var(--kicker-gutter);
  }

  .content-head > .content-title {
    padding-left: 0.7894736842em;
    padding-right: 0.7894736842em;
  }

  .content-head > .meta {
    padding-left: var(--page-gutter);
    padding-right: var(--page-gutter);
  }
}

@media (max-width: 339px) {
  .content-head > .kicker {
    padding-left: 11px;
    padding-right: 11px;
  }

  .content-head > .content-title {
    padding-left: 0.2631578947em;
    padding-right: 0.2631578947em;
  }

  .content-head > .meta {
    padding-left: 10px;
    padding-right: 10px;
  }

  .center-rail {
    padding-left: 10px;
    padding-right: 10px;
  }
}


/* ========================================================================
   STICKY CHROME + BYLINE  —  the sticky offset and the byline row

   Nothing in this section touches .article-content or any data-copy element.
   Every number is the live page's own value, taken from
   _source/layout-spec.json ("submenu" and "byline" objects, measured
   2026-11-04 with getComputedStyle + getBoundingClientRect).

   Must stay last: it carries scroll-padding-top, and it restates the byline
   row whose old flex rule has been deleted from the header section above.
   The live page's pink section sub-nav was the second sticky bar; it is not
   reproduced, so only the header occludes the top of the page now.
   ===================================================================== */

/* --- tokens -----------------------------------------------------------
   Prefixed so they cannot collide with the tokens the sections above add to
   :root. --chrome-header-height mirrors .site-header's own
   --site-header-height, which is declared ON .site-header and therefore
   invisible to html; it is restated here so the sticky offset can be
   derived instead of hard-coded. Keep the two in sync.
   ---------------------------------------------------------------------- */

:root {
  --chrome-header-height: 60px;   /* live header.header: 60px, sticky at top 0 */
  --chrome-header-hairline: 1px;  /* the #e1e1e1 box-shadow hairline under it */

  /* All the sticky chrome occludes: the hairline's bottom edge, 61px. */
  --sticky-chrome-height: calc(var(--chrome-header-height) + var(--chrome-header-hairline));

  /* Byline: the live page's own em values, which resolve against the 14px
     row, giving 6px either side of the "|" and 5px after the author link. */
  --meta-sep-space: 0.428571em;
  --meta-byline-link-gap: 0.357143em;
}

@media (max-width: 767px) {
  :root {
    /* .site-header shrinks to 50px here, as the live one does -- kept at the
       same 767px as its own ladder so the two cannot drift apart. */
    --chrome-header-height: 50px;
  }
}

/* An anchor jump has to clear the sticky header: 61px desktop, 51px at
   <=767px. The live page's second sticky bar (the pink sub-nav) is not
   reproduced, so nothing else is added here. */
html {
  scroll-padding-top: var(--sticky-chrome-height);
}

/* --- the byline row "By Kaitlin Marks | October 30, 2026" ---
   The replica rendered three flex children (byline, time, and a .share
   group of two share-icon spans) with a 14px flex gap. The live
   .content-head-info has exactly two children, laid out as inline-blocks in
   normal flow, separated by a "|" generated from .content-byline::after.
   The <time> is a bare <time> with no <a> inside and no underline.

   The share icons are gone from index.html. On the live page they are not
   deleted but live in a separate vertical rail (aside#module-social-sharing)
   pinned at the far left of the viewport, outside the container; that rail is
   deliberately NOT reproduced here — see README.md, Known deltas.
   ---------------------------------------------------------------------- */

.meta {
  /* Live .content-head-info: display block, margin-top 2.2em (= 22px against
     its 10px font-size), padding 0, and children with margin-bottom 0.
     Deliberately NO margin-bottom: the 30px below the byline comes from
     .content-head's own margin-bottom, not from this row.

     Deliberately NO `padding` declaration either, even though the live row
     computes to 0 on desktop. .meta has no padding to begin with, and PAGE
     LAYOUT gives `.content-head > *` the 30px page gutter below 680px; a
     `padding: 0` here would tie that rule on specificity and — coming
     later — win, stripping the byline's mobile gutter. */
  display: block;
  margin: 22px 0 0;

  /* Live children rule, verbatim: rgb(118,118,118) = --meta, museo-sans
     (substituted by --text per the house rule), 1.4em = 14px, weight 400,
     line-height 1.4286. */
  color: var(--meta);
  font-family: var(--text);
  font-size: 14px;
  font-weight: 400;
  line-height: 1.4286;
}

.meta .byline,
.meta .published {
  display: inline-block;
  margin-bottom: 0;
  color: inherit;
}

/* The separator the replica was missing. Live:
   .content-head-info .content-byline::after
     { content: "|"; font-weight: 300; margin: 0 0.428571em } */
.meta .byline::after {
  content: "|";
  font-weight: 300;
  margin: 0 var(--meta-sep-space);
}

/* Live: .content-head-info .content-byline a:last-child
         { margin-right: 0.357143em } */
.meta .byline a:last-child {
  margin-right: var(--meta-byline-link-gap);
}

/* Live author link: colour inherited from the row, underlined; the hover
   drops the underline and goes accent. The replica kept the underline on
   hover and hard-coded the colour instead of inheriting it. */
.meta .author {
  color: inherit;
  text-decoration: underline;
}

.meta .author:hover,
.meta .author:focus-visible {
  color: var(--accent);
  text-decoration: none;
}

/* The date is not a link on the live page and must not look like one, even
   if a UA stylesheet or a later rule decorates <time>. */
.meta .published {
  text-decoration: none;
}

/* ========================================================================
   GLOBAL FOOTER  —  measured off the live page at viewport 1440
   Live chain:
     footer.footer            padding 50px 0 0; margin-top 50px; bg #fff;
                              border-top 2px solid rgb(236,43,140)
     .footer__container       max-width 1320px; margin auto; padding 0 20px
     .footer__disclaimer      16px/19.2px, rgb(86,86,86), UPPERCASE, margin 0 0 60px
     .footer__main            margin-bottom 60px
       > .footer__container   display grid; grid-template-columns 3 x 426.66px;
                              gap 50px 0
         column 1             usweekly nav + socials, pushed apart (socials sits on the
                              column's bottom edge: measured y=593 in a 279..656 row)
         columns 1 and 2      padding-right 106.656px
   Those last two are the 1440 SNAPSHOT, not the authored values: the padding
   is `25%` of the track and the margin-bottom is `6em`, both of which step at
   48em/64em. The rules below reproduce the ladders; see each one's comment.
     .footer__heading         Fira SEC 22px/26.4px, weight 700, UPPERCASE, margin 0 0 16px
     .footer-nav              display flex; gap 10px   (links 17px/20.4px, weight 400, #000)
     .footer__socials-list    display flex; gap 20px; wrap   (icons 20x20)
     .footer__magazine        display flex; gap 28px   (cover 205x275)
   The live .footer__form newsletter band and the .footer__bottom McClatchy / WordPress VIP
   bar are deliberately NOT reproduced: this replica mimics only the article surface.
   museo-sans is substituted via --text as everywhere else, but note the footer barely uses
   it: .footer declares Fira Sans Extra Condensed, so the whole block is --display.
   ===================================================================== */

.site-footer {
  margin-top: 50px;
  /* The 60px bottom is .footer__main's own `margin-bottom:6em` moved INSIDE
     the footer box. With the newsletter band and the McClatchy bar deleted,
     .footer__main is the last element on the page and a bottom margin there
     collapses out through <body>, leaving the document with no terminal
     whitespace. The number is still the publisher's, not an invented one. */
  padding: 50px 0 60px;
  background: var(--page);
  border-top: 2px solid var(--accent-rule);
  font-family: var(--display);
  /* Live .footer declares line-height:1.2. Without it each <li>'s strut
     inherits body's FIXED 28.48px and wins the line box over the
     inline-block link's own 20.4px, so every nav row steps 38.5px instead of
     the live 30.4px (= 17 x 1.2 + the 10px flex gap). */
  line-height: 1.2;
}

.site-footer__container {
  box-sizing: border-box;
  max-width: 1320px;
  margin: 0 auto;
  padding: 0 20px;
}

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

/* --- disclaimer band ---------------------------------------------------- */

.site-footer__disclaimer {
  margin: 0 0 60px;
  font-size: 16px;
  font-weight: 400;
  line-height: 19.2px;
  color: #565656;
  text-align: center;       /* live .footer__disclaimer */
  text-transform: uppercase;
}

/* --- main three-column grid --------------------------------------------- */

.site-footer__main {
  margin-bottom: 0;        /* folded into .site-footer's own padding-bottom */
}

.site-footer__cols {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: 50px 0;
}

.site-footer__col {
  min-width: 0;
}

/* The live gutters are PERCENTAGES of the track, not a fixed figure:
   `.column-usweekly{padding-right:25%}` and `.column-legal{padding-left:0;
   padding-right:25%}` at min-width:64em, and between 768 and 1023 it is
   column 2 alone with `padding: 0 4em 0 2.5em`. The replica's 106.66px is 25%
   of a 426.67px track, which only occurs once the container caps at 1320 --
   at 1024 the tracks are 328px, so the right value there is 82px and the
   hard-coded figure was stealing 25px of measure from every link. */

@media (min-width: 768px) and (max-width: 1023px) {
  .site-footer__col:nth-child(2) { padding: 0 40px 0 25px; }
}

@media (min-width: 1024px) {
  .site-footer__col:nth-child(1),
  .site-footer__col:nth-child(2) { padding-right: 25%; }
  .site-footer__col:nth-child(2) { padding-left: 0; }
}

/* The two 1px #ededed rules that make the three lists read as columns. Live
   hangs them off .column-legal as ::before / ::after at min-width:48em, each
   `height:100%` of the grid row. Measured at 1440 on the reference render:
   x=421 and x=847, both 377px tall -- i.e. `left:-20%` = -85.33 off a
   426.67px track at x=506.67, and `right:20%` = 85.33 back off x=933.33. */

@media (min-width: 768px) {
  .site-footer__col:nth-child(2) { position: relative; }

  .site-footer__col:nth-child(2)::before,
  .site-footer__col:nth-child(2)::after {
    content: "";
    display: block;
    position: absolute;
    top: 0;
    width: 1px;
    height: 100%;
    background: #ededed;
  }

  .site-footer__col:nth-child(2)::before { left: 0; }
  .site-footer__col:nth-child(2)::after  { right: 25px; }   /* live right: 2.5em */
}

@media (min-width: 1024px) {
  .site-footer__col:nth-child(2)::before { left: -20%; }
  .site-footer__col:nth-child(2)::after  { right: 20%; }
}

/* column 1 holds two blocks with the socials pinned to the bottom of the row */
.site-footer__col--stack {
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  gap: 50px;
}

/* Upstream, .footer__socials is a SIBLING of the three columns with its own
   grid row (`grid-area:2/1/3/2` at >=48em), so the gap above CONNECT WITH US
   is the grid's 50px row gap PLUS the block's own `.footer__socials{
   margin-top:5em}` -- 100px in all, which is what makes the live grid row
   377px rather than 327px tall. Nested inside column 1 here, it has to state
   both numbers. The margin is a min-width:48em rule upstream: below 768 the
   socials gets a full-width row of its own and the row gap alone separates
   them, so this must not apply there.

   NOTE this contradicts spacing-v2.md F10, which said no change was needed at
   >=768. That held only while the footer lists were still inheriting body's
   28.48px line-height: column 1 was then ~41px taller, and
   `justify-content: space-between` was pushing the icons to the live offset
   by accident. With line-height:1.2 in place the slack is gone and the real
   declaration is needed. Measured: icons at offset 438 below the pink rule
   without this rule, 488 with it, against 488 on the live reference. */

@media (min-width: 768px) {
  .site-footer__socials { margin-top: 50px; }
}

.site-footer__heading {
  margin: 0 0 16px;
  font-size: 22px;
  font-weight: 700;
  line-height: 26.4px;
  color: var(--ink);
  text-transform: uppercase;
}

.site-footer__nav {
  display: flex;
  flex-direction: column;
  gap: 10px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.site-footer__nav a,
.site-footer__inert {
  display: inline-block;
  font-size: 17px;
  font-weight: 400;
  line-height: 20.4px;
  color: #0e0e0e;           /* live .footer-nav a -- not pure black */
  text-decoration: none;
}

/* Live keeps the colour on every state (`.footer-nav a:active,:hover,:link,
   :visited { color: inherit }`) and underlines instead of going accent. */
.site-footer__nav a:hover,
.site-footer__nav a:focus-visible {
  color: inherit;
  text-decoration: underline;
}

/* items that open a JS dialog on the live site and have no real href */
.site-footer__inert {
  cursor: default;
}

/* "Your Privacy Choices": the badge follows the label on the live page, it is
   not a 29x14 box, and the link is a flex row.
     .footer-nav .privacy-choices-link a   { align-items:center; display:flex;
                                             gap:.4705882353em }        = 8px
     .footer-nav .privacy-choices-link img { height:.9411764706em;      = 16px
                                             order:1; width:auto;
                                             position:relative;
                                             top:-.0588235294em }       = -1px
   `order:1` is what puts it after the text -- this is a flex-order change
   upstream, not a markup order, so :has() reproduces it without touching
   index.html. The <li> is outside .article-content either way. */

.site-footer__nav a:has(.site-footer__privacy-icon) {
  display: flex;
  align-items: center;
  gap: 8px;
}

.site-footer__privacy-icon {
  width: auto;
  height: 16px;
  order: 1;
  position: relative;
  top: -1px;
}

/* --- socials ------------------------------------------------------------ */

.site-footer__socials-list {
  display: flex;
  align-items: center;     /* live has it, and it matters once the heights vary */
  flex-wrap: wrap;
  gap: 20px;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* Live: .footer__socials-list a { transition: opacity .3s } and :hover { opacity: .85 } */
.site-footer__socials-list a {
  display: block;
  line-height: 0;
  transition: opacity 0.3s;
}

.site-footer__socials-list a:hover {
  opacity: 0.85;
}

/* Three of the six icons are not square upstream: `.footer__socials-list img`
   is 2em/2em (20px) with per-file width overrides -- twitter 2.2em (22),
   tiktok 1.8em (18), googlenews 2.4em (24). Flattening them all to 20px left
   the whole row 4px short of the live one (80...299 against 80...303). The
   existing filenames already match the publisher's own [src*=] selectors. */

.site-footer__socials-list img {
  display: block;
  width: 20px;
  height: 20px;
  object-fit: contain;
}

.site-footer__socials-list img[src*="twitter"]    { width: 22px; }
.site-footer__socials-list img[src*="tiktok"]     { width: 18px; }
.site-footer__socials-list img[src*="googlenews"] { width: 24px; }

/* --- magazine column ---------------------------------------------------- */

/* Live `.footer__magazine-cover` sets WIDTH only -- height is always auto --
   and steps it 12em / 15em / 20.5em at 48em / 64em / 75em, so 205px is the
   >=1200 value alone and the replica was 55-85px too wide across 768-1199.
   The gap steps with it: none below 30em, 2em to 75em, 2.8em above. */

.site-footer__magazine {
  display: flex;
  align-items: flex-start;   /* live .footer__magazine */
  gap: 20px;
}

@media (min-width: 1200px) { .site-footer__magazine { gap: 28px; } }

.site-footer__cover {
  flex: 0 0 auto;
  width: 120px;
  height: auto;              /* no forced height, so no object-fit crop either */
}

@media (min-width: 1024px) { .site-footer__cover { width: 150px; } }
@media (min-width: 1200px) { .site-footer__cover { width: 205px; } }

/* --- responsive --------------------------------------------------------- */

/* The publisher has exactly ONE footer breakpoint, 48em (768px), and the grid
   is two columns at every width below it -- never one. Its column gap is zero
   at every width (`gap: 5em 0`). The replica stepped 3 -> 2 at 979 with a
   30px column gap and 2 -> 1 at 669, none of which exists upstream, and its
   vertical ladder below 669 (40 / 30 / 40 / 40px) was a set of round numbers
   where the theme has 50 / 35 / 35 / 35.
   ---------------------------------------------------------------------- */

@media (max-width: 767px) {
  .site-footer {
    /* live .footer{padding-top:3.5em} base, 5em at min-width:48em.
       margin-top is 5em at every width, so it is not restated here. */
    padding-top: 35px;
    padding-bottom: 35px;
  }

  .site-footer__disclaimer { margin-bottom: 35px; }   /* live 2.1875em x 16px */

  .site-footer__cols {
    grid-template-columns: repeat(2, 1fr);
    grid-template-rows: repeat(3, auto);
    gap: 50px 0;
  }

  /* Below 48em the live grid is `repeat(2,1fr) / repeat(3,auto)` and CONNECT
     WITH US is a grid item in its own right, spanning both columns:
         .column-usweekly { grid-area: 1/1/2/2 }
         .footer__socials { grid-area: 2/1/3/3 }
         .column-legal    { grid-area: 1/2/2/3 }
         .column-magazine { grid-area: 3/1/4/3 }
     That full-width row is why all six icons stay on ONE line down to 320px
     upstream. Here the socials block is nested inside column 1, so it was
     laid out in a half-width cell (167.5px at 375) and the row wrapped to two
     icons-rows at 600 and below, three at 320 — pushing the magazine cover
     54px down the page. `display: contents` dissolves the column-1 box so its
     two children become grid items and the publisher's own grid-areas can be
     restated verbatim. */

  .site-footer__col--stack { display: contents; }

  .site-footer__col--stack > :first-child {
    min-width: 0;                 /* .site-footer__col's own rule is gone with the box */
    grid-area: 1 / 1 / 2 / 2;
  }

  .site-footer__socials { grid-area: 2 / 1 / 3 / 3; }

  .site-footer__col:nth-child(2) { grid-area: 1 / 2 / 2 / 3; }

  .site-footer__col:nth-child(3) { grid-area: 3 / 1 / 4 / 3; }

  /* Live .footer__socials-list is `gap:2.4em` (24px) with a min-width:48em
     override down to 2em, so the WIDER gap is the small-screen value; and
     `.footer__socials-list img{font-size:1.5em}` scales every icon box by
     1.5 -- 20 -> 30, 22 -> 33, 18 -> 27, 24 -> 36. */
  .site-footer__socials-list { gap: 24px; }
  .site-footer__socials-list img { width: 30px; height: 30px; }
  .site-footer__socials-list img[src*="twitter"]    { width: 33px; }
  .site-footer__socials-list img[src*="tiktok"]     { width: 27px; }
  .site-footer__socials-list img[src*="googlenews"] { width: 36px; }

  /* live .footer__magazine-cover{order:2}: on phones the cover sits to the
     RIGHT of the subscription links, not to their left. */
  .site-footer__cover { width: 150px; order: 2; }
}

@media (max-width: 479px) {
  /* live .footer__magazine has no gap below 30em; the link column takes half
     the width and its own 2em right padding instead
     (.footer__magazine .footer-nav__wrapper{padding-right:2em;width:50%}). */
  .site-footer__magazine { gap: 0; }

  .site-footer__magazine nav {
    width: 50%;
    padding-right: 20px;
  }
}

/* Live: @media (max-width: 24.3125em) { .footer-nav a { font-size: .9411764706em } }
   and the privacy badge drops with it (`img{height:.875em}` x 16px = 14px). */
@media (max-width: 389px) {
  .site-footer__nav a,
  .site-footer__inert { font-size: 16px; }

  .site-footer__privacy-icon { height: 14px; }
}
