/* ==========================================================================
   Christian Trends, design sample C: THE DECK
   ==========================================================================

   Replaces THE CARVE, which the client rejected on 2026-08-18: its chrome
   repeated A and B's pattern so it could not read as a new direction, its
   accent sat in the same warm family as B's, and the hairline cut through the
   display type hurt legibility. All three are gone. The creativity here is in
   layout, block geometry and motion, and the type is left plainly readable.
   → HANDOFF §6h

   Prefixes: dk- page, dkc- chrome.

   THE SYSTEM
     - big blocks with a large radius, and colour used in blocks, never as
       hairlines or tints
     - a card-deck hero: the live article at the front, the rest fanned behind
     - a split nav: reader controls left, wordmark centre, theme switch and
       Sections right. No utility strip, no chip rail. This is the part that
       stopped the three samples reading as one site.
     - blobs and a drawn squiggle as the accenting shapes
     - one pill button with a clipped badge whose arrow leaves and is replaced

   PALETTE, six values, measured with `node tools/contrast.mjs deck` in BOTH
   themes. paper/ink/quiet swap roles between themes; the three loud colours do
   not move, which is what keeps this one palette rather than two:
     base      #F4F3EF  paper           ink on it        16.14:1
     neutral   #16171A  ink             paper on it      16.14:1
     primary   #5B2BE0  violet block    paper on it       6.60:1
     secondary #D6F24B  lime block      ink on it        14.22:1
     accent    #FF4D9D  pink block      ink on it         5.80:1
     tertiary  #E9E7E0  quiet card      ink on it        14.49:1

   ⚠ EACH LOUD COLOUR HAS EXACTLY ONE LEGAL LABEL, and the failures are what
   proved it: ink on violet is 2.45:1, paper on pink is 2.78:1, and violet as
   TEXT on the dark ground is 2.45:1. So a violet block always carries paper, a
   pink block always carries ink, and in dark mode violet is a BLOCK only while
   lime takes over as the accent text colour (14.22:1).

   ⚠ THE THEME IS CUSTOM PROPERTIES, not a second stylesheet. They inherit, so
   `.dk-body[data-theme="dark"]` re-points every surface in one flat rule and no
   descendant selector is needed anywhere. That is also closer to the eventual
   ACSS token pass than hardcoded hex was.

   Flat, per-element, fully scoped. NO descendant selectors: build-etch.mjs
   hoists each selector into its own style entry and drops descendants silently.
   Measure caps only where a box can run WIDER than a comfortable measure.
   ========================================================================== */

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

/* ================================================================== THEME */

.dk-body {
  --dk-paper: #F4F3EF;
  --dk-ink: #16171A;
  --dk-quiet: #E9E7E0;
  --dk-line: #DBD8D0;
  --dk-muted: #5D5D5E;
  /* ⚠ THE MUTED VALUE FOR TEXT ON GLASS, WHICH IS NOT THE MUTED VALUE FOR TEXT ON THE PAGE.
     `--dk-muted` is solved against the page ground. The mark's tagline sits on the glass pill,
     and on a phone that pill floats directly over the hero PHOTOGRAPH, so its real ground is
     the glass composited over an image that can be any colour. Measured against the extreme
     (§6h-vii's rule) the page value came out 3.50:1 in the light theme over a black image and
     3.87:1 in the dark theme over a white one — both failing, on 8px type.
     Raising the glass plateau was the wrong lever: the light theme needed 93% to clear 4.5,
     which is opaque, and the glass is the point. So the COLOUR is solved instead, at 78% of
     ink over paper rather than 68%: 4.94:1 and 4.93:1 against those worst grounds, and still
     visibly a step quieter than the wordmark beside it.
     Named for the job rather than the hue, so reaching for the wrong one is visible at the
     point of use. → kit 03 §5d */
  --dk-glassmuted: #474749;
  /* ⚠⚠ THE AND ALSO BAND IS THEME-AWARE NOW, AND IT WAS NOT BEFORE. It was built as "the
     inverted band" on the assumption of a light page: a full-bleed lime field with paper cards
     and ink text, hardcoded, in BOTH themes. So in dark mode it never inverted — it stayed a
     light band on a dark page. Measured, lime is **91x the dark page's luminance**, which is
     exactly the client's "it hits the whole face when it comes into view".
     In the LIGHT theme lime is actually DARKER than paper (0.87x), so there is no flash there at
     all; the field is only knocked back from #D6F24B to lime at 90% toward ink, which takes the
     electric edge off without changing its role.
     In the DARK theme the field becomes a deep lime-tinted ground and the band inverts properly:
     6x the page instead of 91x. Lime then does its work as the ACCENT on that field rather than
     as the field, which keeps the band identifiably the lime one.
     Five tokens, each named for its job so the wrong one is visible at the point of use
     (kit 03 §5d), and every pair measured. → HANDOFF §6h-xix */
  --dk-band: #C3DC46;
  --dk-bandink: #16171A;
  --dk-bandcard: #F4F3EF;
  --dk-bandmuted: #4A4B4E;
  --dk-bandaccent: #5B2BE0;
  --dk-border: #6A6B6B;
  --dk-borderw: 2px;
  --dk-shadow: rgba(22, 23, 26, 0.12);
  /* fixed in both themes */
  --dk-violet: #5B2BE0;
  /* ⚠ VIOLET IS A BLOCK COLOUR. As TEXT it is 6.60:1 on paper but only 2.45:1 on the dark
     ground, which is the rule this palette produced and which I then broke in nine places
     and every focus ring. On dark it lifts 40% toward paper: 5.39:1 on the ground and
     4.66:1 on the quiet card. A derived tint of an existing colour, not a seventh. */
  --dk-accenttext: #5B2BE0;
  /* The accent's text colour for the INVERTED neutral, which is what the category pill flips to on
     hover. In this theme the inverted ground is near-black, so the violet has to be the lifted tint;
     the dark theme sets it back to the raw violet, because there the inverted ground is near-white.
     A derived tint of an existing colour, not a new one. */
  --dk-accentinv: #987BE6;
  --dk-lime: #D6F24B;
  --dk-pink: #FF4D9D;
  /* the block radius, one value the whole page derives from */
  --dk-r: clamp(1.1rem, 2.4vw, 2rem);
  /* ⚠ THE NOTCH GEOMETRY LIVES HERE, not on the notch class, because the BUTTON has to read it as
     well and the button is a SIBLING of the masked link, not a descendant. --dk-ns is the bite's
     radius, --dk-nr the fillet where the bite meets the card's edges. The button is centred on the
     bite using both: the bite's own centre is inset from the corner by exactly --dk-nr, so a button
     placed at the corner is NOT concentric with it and the gap comes out uneven all the way round.
     Card types with a shallower box override --dk-ns on their wrapper. */
  --dk-nr: 9px;
  --dk-ns: 26px;

  margin: 0;
  /* The containing block for the page-level accent shape's wrapper.
     ⚠ `overflow-x: clip` does NOT belong here: overflow set on <body> is PROPAGATED to
     the viewport when <html> is visible, which leaves the body itself behaving as
     `visible` and clipping nothing. It looked like the right fix and the document still
     measured 8vw too wide at every width. The shape gets its own clipping wrapper. */
  position: relative;
  background: var(--dk-paper);
  color: var(--dk-ink);
  font-family: "Newsreader", Georgia, serif;
  font-size: 1.0625rem;
  /* ⚠ 400 was too light to hold a line of body copy, and it is worse reversed out: the
     same weight always renders thinner light-on-dark. This is the reading face for article
     bodies, so it gets a weight rather than a workaround. 450 on paper, 500 on ink. */
  font-weight: 450;
  line-height: 1.62;
  -webkit-font-smoothing: antialiased;
  transition: background-color 320ms cubic-bezier(.22,.61,.36,1), color 320ms cubic-bezier(.22,.61,.36,1);
}

.dk-body[data-theme="dark"] {
  --dk-paper: #16171A;
  --dk-ink: #F4F3EF;
  --dk-quiet: #22242A;
  --dk-line: #33363D;
  --dk-muted: #ADADAB;
  --dk-glassmuted: #C3C3C0;
  /* The band inverts here: a deep lime-tinted field, a lime-tinted card on it, paper text, and
     LIME as the accent, because the lifted violet measures only 4.35:1 on this card while lime
     measures 11.49:1 — and lime is the band's own colour, which is the better answer anyway. */
  --dk-band: #3C4324;
  --dk-bandink: #F4F3EF;
  --dk-bandcard: #272B1E;
  --dk-bandmuted: #ADADAB;
  --dk-bandaccent: #D6F24B;
  --dk-border: #9A9A98;
  --dk-shadow: rgba(0, 0, 0, 0.5);
  --dk-accenttext: #987BE6;
  --dk-accentinv: #5B2BE0;
  font-weight: 500;
}

/* ⚠ THE GUTTER GOES ON <html>, NOT ON <body>. `overflow` set on the body IS propagated to
   the viewport, which is what makes the lock below work, but `scrollbar-gutter` is NOT: it
   only propagates from the root. Put on the body it computes to `stable` on an element
   that never scrolls, does nothing, and the page still jumps by a scrollbar's width the
   moment the menu opens. Measured: html reported `auto` while body reported `stable`.

   At the Etch step this one rule belongs in the GLOBAL stylesheet, not a page block: it is
   a framework-level override and there is no class to scope it to. → kit 01 §4 */
html { scrollbar-gutter: stable; }

/* ⚠ AND THE LOCK MUST GO ON THE SAME ELEMENT AS THE GUTTER. Locking through <body> works,
   because `overflow` propagates from body to the viewport, but then the viewport is the
   scroll container while `scrollbar-gutter` is declared on <html>, which never becomes
   one: the gutter is not reserved and the page jumps by exactly the scrollbar width the
   moment the menu opens. Measured that way: 1167px to 1182px.
   Both on <html>, and the reserved space survives the lock. Measured this way, at real
   viewports of 1456, 1232 and 1000: the body stays 1423px wide and nothing moves.

   ⚠ And do NOT then also hand the width back as padding. That was my first fix, before
   measuring which box was actually changing, and with the gutter already holding the width
   it double-counts: html stayed 1423 while body was squeezed to 1408 and every centred
   band slid 8px left. The property alone is the whole answer. */
html[data-locked="true"] { overflow: hidden; }

.dk-skip {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 60;
  padding: 0.7rem 1rem;
  border-radius: 999px;
  background: var(--dk-violet);
  color: #F4F3EF;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.875rem;
  font-weight: 700;
  text-decoration: none;
}

.dk-skip:focus { left: 0.75rem; top: 0.75rem; }

/* THE ACCENT SHAPE, at page level rather than inside the hero, so it reads as entering
   from the top edge of the site and passes behind the floating header instead of being
   cut off at the section boundary. Decorative, never animated, never in the way. */
/* The wrapper does the clipping, because it is a real element rather than the body, so
   `overflow: clip` on it applies to its own descendants. `clip` and not `hidden`: hidden
   would make it a scroll container. */
.dk-topwrap {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  z-index: 0;
  height: clamp(24rem, 52vw, 46rem);
  overflow: clip;
  pointer-events: none;
}

.dk-topblob {
  position: absolute;
  top: clamp(-14rem, -18vw, -7rem);
  right: clamp(-9rem, -8vw, -4rem);
  z-index: 0;
  width: clamp(20rem, 52vw, 46rem);
  aspect-ratio: 1 / 1;
  border-radius: 46% 54% 38% 62% / 52% 40% 60% 48%;
  background: var(--dk-violet);
  opacity: 0.16;
  pointer-events: none;
}

/* ⚠ `overflow-x: clip` and not `hidden`: clip bounds the box without making it a scroll container,
   so nothing inside stops being sticky and no scrollbar appears. It is here to bound the full-bleed
   wave above. Paired with `visible` on the other axis, which is the one combination the spec
   allows. */
.dk-main { position: relative; z-index: 1; display: block; overflow-x: clip; overflow-y: visible; }

.dk-main:focus-visible { outline: none; }

/* ======================================================= THE ZONE PATTERN
   Concentric arcs behind Thinking AND Living, centred off the canvas at the lower left so only
   their shallow outer curves pass through the page.

   ⚠ IT IS A FIELD, NOT A DIVIDER, and that distinction is the whole design. Five earlier attempts
   were full-width horizontal elements in the gap between the two bands, and every one read as a
   page split, because a horizontal line across the full width IS one however it is drawn. A shape
   this large crossing both bands does the opposite: it ties them together. → HANDOFF §6h-xxi

   ⚠ The arcs are ASYMMETRIC by construction: one centre, off canvas, with the radii spaced
   unevenly. There is no wavelength, so there is nothing that can read as a repeat, which is what
   sank the wavy pattern (§6h-xx). */
.dk-zone { position: relative; }

/* Full bleed the same way the Magazine's wave does it: a fixed inset cannot reach both screen
   edges from inside a capped, centred container. 100vw is wider than the content box whenever a
   scrollbar is present, and this page always reserves a stable gutter, so it is bounded by
   `.dk-main`'s `overflow-x: clip` with `overflow-y: visible`. → kit 03 §5q-i */
.dk-zone__arcs {
  position: absolute;
  top: 0;
  bottom: 0;
  left: 50%;
  width: 100vw;
  transform: translateX(-50%);
  z-index: 0;
  overflow: clip;
  pointer-events: none;
}

/* ⚠ THE MASK IS NOT DECORATION EITHER. A field that stops abruptly draws a line where it stops,
   which reinvents the split the whole approach exists to avoid. It fades out toward the top right,
   away from the arcs' own centre, so the lines have no ends anywhere on screen.
   `slice` rather than `none`, because a non-uniform stretch would turn circles into ellipses and
   the even concentric spacing is what makes them read as one family. */
.dk-zone__svg {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  overflow: visible;
  -webkit-mask-image: radial-gradient(105% 120% at 10% 100%, #000 26%, transparent 82%);
  mask-image: radial-gradient(105% 120% at 10% 100%, #000 26%, transparent 82%);
}

/* Thin, and the interface line's own colour rather than a new one. `vector-effect` keeps the
   stroke at its declared width whatever the slice scale does, which is what stops it fattening
   into a band of colour on a wide monitor. */
.dk-zone__rings {
  fill: none;
  stroke: var(--dk-border);
  stroke-width: 2;
  vector-effect: non-scaling-stroke;
  /* ⚠ 0.5, and the ceiling is measured rather than judged. A band title can sit exactly on a
     stroke, so the worst case is the title's own colour against the stroke composited over the
     page. Measured at 0.50: 7.25:1 dark and 8.16:1 light. It stays above 4.5 all the way to 0.60,
     and the light theme's ACCENT ring is the first to fail, at 0.70 (4.38:1) — which is why the
     accent below is capped lower than these. */
  opacity: 0.5;
}

/* One ring carries the accent, so the family has a focal line rather than being uniform. Violet
   on paper and the lifted violet on ink, which is the token that exists precisely because raw
   violet is 2.45:1 on the dark ground. → §6h-iii */
.dk-zone__ring--accent {
  fill: none;
  stroke: var(--dk-accenttext);
  stroke-width: 3;
  vector-effect: non-scaling-stroke;
  /* Capped at 0.6: the violet is the first stroke to pull a title under the floor, at 0.70 in the
     light theme. 0.60 measures 5.39:1 there, which is the tightest pair the pattern produces. */
  opacity: 0.6;
}

/* ==================================================================== ICONS */

.dk-ico {
  width: 1em;
  height: 1em;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.5;
  stroke-linecap: round;
  stroke-linejoin: round;
  flex: none;
}

/* Meta rows are INLINE FLOW, never flex: flex aligns boxes, type wants
   baselines, and one flex gap cannot tell "icon to its value" from "pair to
   pair". → HANDOFF §6f-ii */
.dk-ico--meta {
  vertical-align: -0.13em;
  margin-right: 0.32em;
}

/* nowrap, or a meta pair splits across lines and leaves a stray unit behind. */
.dk-m__t { margin-right: 1.05em; white-space: nowrap; }

/* The byline is the one meta value a reader looks for by name, so it stops being the same
   weight and colour as the date beside it. Full ink rather than the muted tone: at 0.8125rem
   a weight change alone barely reads, and ink on either ground is 16.14:1 (contrast.mjs). */
/* ⚠⚠ WEIGHT ONLY. NO COLOUR. This rule carried `color: var(--dk-ink)` for one round and it broke
   the byline on every coloured block, in one theme each:

     · on a LIME or PINK tile, `--dk-ink` is the LIGHT value in dark mode  -> light on lime
     · on a VIOLET tile, `--dk-ink` is the DARK value in light mode        -> 2.45:1

   The reason is that a meta row deliberately has NO colour of its own: `.dk-tile__meta` inherits
   the tile's own foreground, which each coloured tile sets correctly, and mutes it with the 0.85
   opacity that §6h solved for the worst of the three blocks. Forcing a token here replaced a
   value that was right per block with one that swaps per THEME, which is the wrong axis.
   The client asked for more weight, and weight is all this needs. Everything else it should
   inherit. → asserted by the metaContrast sweep in tools/interact.mjs */
.dk-m__t--who { font-weight: 700; }

/* ============================================================== THE BUTTON
   A pill with a clipped circular badge. On hover the arrow leaves top-right and
   a second one arrives from bottom-left.

   ⚠ Driven by an INHERITED CUSTOM PROPERTY, not by `.dk-btn:hover .dk-btn__arrow`.
   Custom properties inherit, so a var set on the parent reaches the child, and
   the child's own transform transition animates when the resolved value
   changes. A descendant selector would have been dropped at paste time. */

.dk-btn {
  --dk-go: 0;
  /* The badge is always the INVERSE of the button it sits on, in both themes and in both
     states. Without this the badge kept its resting colours while the button flipped, so
     on hover it was a white circle on a white button and the arrow disappeared.
     Custom properties, because `.dk-btn:hover .dk-btn__badge` is a descendant selector
     and the generator drops those. */
  --dk-badge-bg: var(--dk-ink);
  --dk-badge-fg: var(--dk-paper);
  display: inline-flex;
  align-items: center;
  gap: 0.6rem;
  padding: 0.4rem 0.4rem 0.4rem 1.1rem;
  border: var(--dk-borderw) solid var(--dk-border);
  border-radius: 999px;
  background: var(--dk-paper);
  color: var(--dk-ink);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.8125rem;
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  white-space: nowrap;
  transition: background-color 240ms cubic-bezier(.22,.61,.36,1), color 240ms cubic-bezier(.22,.61,.36,1), border-color 240ms cubic-bezier(.22,.61,.36,1);
}

.dk-btn:hover {
  --dk-go: 1;
  --dk-badge-bg: var(--dk-paper);
  --dk-badge-fg: var(--dk-ink);
  background: var(--dk-ink);
  color: var(--dk-paper);
  border-color: var(--dk-ink);
}

.dk-btn--quiet { background: transparent; }

.dk-btn--onlime {
  /* On the band, so it takes the band's own tokens: an ink pill with paper type in the light
     theme, and a paper pill with dark type in the dark one. Hardcoded it vanished into the deep
     field once the band learned to invert. */
  --dk-badge-bg: var(--dk-bandcard);
  --dk-badge-fg: var(--dk-bandink);
  background: var(--dk-bandink);
  color: var(--dk-bandcard);
  border-color: var(--dk-bandink);
}

.dk-btn--onlime:hover {
  --dk-badge-bg: var(--dk-bandink);
  --dk-badge-fg: var(--dk-bandcard);
  background: var(--dk-bandcard);
  color: var(--dk-bandink);
  border-color: var(--dk-bandcard);
}

.dk-btn__label { display: block; }

.dk-btn__badge {
  position: relative;
  display: grid;
  place-items: center;
  width: 30px;
  height: 30px;
  overflow: hidden;
  border-radius: 50%;
  background: var(--dk-badge-bg);
  color: var(--dk-badge-fg);
  font-size: 0.875rem;
  flex: none;
  transition: background-color 240ms cubic-bezier(.22,.61,.36,1), color 240ms cubic-bezier(.22,.61,.36,1);
}

.dk-btn__arrow {
  grid-area: 1 / 1;
  transform: translate(calc(var(--dk-go) * 150%), calc(var(--dk-go) * -150%));
  transition: transform 320ms cubic-bezier(.22,.61,.36,1);
}

.dk-btn__arrow--in {
  transform: translate(calc((1 - var(--dk-go)) * -150%), calc((1 - var(--dk-go)) * 150%));
}

/* ================================================================= BOOKMARK
   Beside the wrapping anchor, never inside it: a <button> in an <a> is invalid
   and the nested control does not reliably get its own clicks. → HANDOFF §6f-vi

   ⚠⚠ IT SITS IN AN INVERTED-RADIUS NOTCH AT THE CARD'S TOP-RIGHT CORNER, and the notch is a
   HALO rather than a cut. Client's instruction, and the mechanism is worth stating because the
   obvious one does not work: a `mask` with a circular hole in the card would cut the hole through
   every descendant, and the button is a descendant, so the mask erases the button along with the
   corner. Ringing the BUTTON in the surrounding colour paints the same bite and cannot erase what
   it is drawn around.

   One consequence, and it is the reason this is safe: the button's own box stays INSIDE the card's
   bounds, so nothing protrudes to be clipped by a scroller or to collide with the next card in a
   rail. What reads as "outside the card" is the card's surface being cut away around it. Pushing
   the button physically past the corner would need reserved room in six different containers and a
   scroller that does not clip; say so before promising it.

   This also retires the two ground-specific modifiers. The button no longer sits ON anything —
   its halo means it always sits on the page or band colour — so one appearance is correct
   everywhere, where before there was a variant for an image corner and another for the violet
   block. */

.dk-bm {
  position: absolute;
  /* ⚠ Centred ON the card's corner, which is what leaves a real ring of background visible
     between the button and the bite. The bite is 26px and the button 18px, so the gap is 8px of
     whatever is behind the card, and the wavy line runs through it.
     It therefore protrudes 18px up and 18px to the right of the card's box, which is why the
     gaps and the rail's block padding below were opened up to clear it, and why the wrappers no
     longer carry overflow:hidden. */
  /* Centred on the BITE. Its centre sits --dk-nr in from each edge (that is where the mask's own
     radial gradient is offset to), so matching that is what makes the ring of background around
     the button an even width the whole way round. It protrudes 18px - 9px = 9px past the card,
     which is also less than centring on the corner would have cost. */
  top: var(--dk-nr);
  right: var(--dk-nr);
  z-index: 3;
  transform: translate(50%, -50%);
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 36px;
  height: 36px;
  padding: 0;
  font-size: 0.9375rem;
  background: var(--dk-paper);
  border: var(--dk-borderw) solid var(--dk-border);
  border-radius: 50%;
  color: var(--dk-ink);
  cursor: pointer;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1), border-color 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-bm:hover { background: var(--dk-ink); border-color: var(--dk-ink); color: var(--dk-paper); }

.dk-bm:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

.dk-bm[aria-pressed="true"] { background: var(--dk-pink); border-color: var(--dk-pink); color: #16171A; }

@media (pointer: coarse) { .dk-bm { width: 44px; height: 44px; } }

/* ⚠ The touch target grows from 36px to 44px, so the bite has to grow with it or the ring of
   background closes from 8px to 4px and the notch stops reading as a gap. */
@media (pointer: coarse) { .dk-body { --dk-ns: 30px; } }

/* ============================================== THE CARD'S THREE LINKS
   A card used to be ONE anchor. It is now three: the title goes to the article, the category pill to
   the category archive, the author to the author archive. Client's decision, 2026-08-19, and it is
   what removed every card hover: a whole-card lift is a promise that the whole card is one target,
   and it stops being true the moment there are three.

   ⚠ An <a> inside an <a> is invalid and the inner one does not reliably receive its own clicks, so
   the card wrapper had to stop being an anchor. That is the same rule that has always kept the
   bookmark outside it (§6f-iv), arriving from the other direction.

   Each link therefore carries its own affordance, because there is no longer a card-level one:
   the title is underlined by a line that draws in from the left, the author by a dotted underline
   that says "link" without shouting, and the pill by a change of ground. */

/* ⚠⚠ THE PILL LIVES BETWEEN TWO NEUTRALS, AND FLIPS BETWEEN THEM. Client, 2026-08-19: the hover was
   getting lost whenever the colour it changed to matched the card it sat on — a lime pill on a lime
   tile, a violet one on a violet card. No per-pill palette colour can fix that, because the pill does
   not know which card it is on and the four card colours are the same four the palette offers.

   So both states are neutral and they swap: near-white ground at rest and near-black on hover in the
   light theme, and the other way round in the dark one. A neutral cannot collide with any of the
   card colours, so the state is always visible, and one rule replaces the seven per-ground hovers
   this used to need.

   --dk-accentinv is the accent's text colour for the INVERTED ground. Named for the job rather than
   the hue, so choosing the wrong one is a visible error at the point of use (§5d). Measured, all four
   pairs that ship: 6.60:1 for violet on the near-white ground and 5.39:1 for the lifted violet on the
   near-black one, in both directions. */
.dk-cardchip {
  color: var(--dk-accenttext);
  background: var(--dk-paper);
  text-decoration: none;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-cardchip:hover { background: var(--dk-ink); color: var(--dk-accentinv); }

.dk-cardchip:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

/* ⚠ THE TITLE'S UNDERLINE HUGS THE TEXT, LINE BY LINE.
   The gradient used to sit on the link itself, which is a BLOCK, so it spanned the whole column
   whatever the title said — a short headline got an underline half again its length, and a wrapped
   one got a full-width rule under its last line.
   The fix is an inline element inside the link, carrying the gradient, with
   `box-decoration-break: clone` so EVERY line fragment gets its own complete background sized to
   that fragment. Without `clone` the fragments share one imaginary box and only the last line is
   painted, at the full column width, which is the bug wearing a different hat.
   The link keeps the hover, and the state travels down as a custom property because
   `.dk-cardtitle:hover .dk-cardline` is a descendant selector. → kit 03 §6c */
.dk-cardtitle {
  --dk-u: 0%;
  color: inherit;
  text-decoration: none;
}

.dk-cardtitle:hover { --dk-u: 100%; }

.dk-cardtitle:focus-visible { --dk-u: 100%; outline: 2px solid var(--dk-accenttext); outline-offset: 3px; }

.dk-cardline {
  -webkit-box-decoration-break: clone;
  box-decoration-break: clone;
  background-image: linear-gradient(currentColor, currentColor);
  background-repeat: no-repeat;
  background-position: 0 100%;
  background-size: var(--dk-u) 2px;
  transition: background-size 340ms cubic-bezier(.22,.61,.36,1);
}

/* THE AUTHOR. A dotted underline is the quietest mark that still reads as a link, which is what a
   byline wants: findable, and never competing with the headline above it. */
.dk-m__t--who {
  color: inherit;
  text-decoration: underline dotted;
  text-decoration-thickness: 1px;
  text-underline-offset: 3px;
}

.dk-m__t--who:hover { text-decoration-style: solid; }

.dk-m__t--who:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

/* THE EDITORIAL'S OWN BYLINE, the same idea in its italic serif dress. */
.dk-feat__byline {
  color: inherit;
  text-decoration: underline dotted;
  text-decoration-thickness: 1px;
  text-underline-offset: 3px;
}

.dk-feat__byline:hover { text-decoration-style: solid; }

.dk-feat__byline:focus-visible { outline: 2px solid #F4F3EF; outline-offset: 2px; }

/* The image is a pointer convenience only: out of the tab order, unannounced, and adding no box, so
   no card's layout changed when it was wrapped. */
.dk-imglink { display: contents; }

/* THE PILL'S HOVER, one rule per pill because each sits on a different ground and the palette has a
   rule about which colour may carry text on which (§6h). A single shared swap would have been wrong
   on at least three of them: the same "subtle colour change" cannot be written once when the pills
   are variously lime-on-ink, paper-on-violet, outlined-on-a-photo and bare violet text.
   Every pair below is one the contrast matrix already carries. */

/* lime pill on the violet editorial block -> the block's own paper, keeping ink on it */
/* paper pill on the quiet card -> lime, which ink reads on at 14.22:1 */
/* outlined pill over a photograph -> fills with its own inherited colour and knocks the text out */
/* violet pill -> ink, which paper reads on at 16.14:1 */
/* ink pill on the pale feature -> violet, paper on it at 6.60:1 */
/* bare violet text on the lime band: nothing to fill, so the state is the underline */
.dk-also__rowchip:hover { text-decoration: underline; text-underline-offset: 3px; }

/* ==================================================== THE INVERTED-RADIUS NOTCH
   A REAL hole, cut with a mask, so whatever is behind the card shows through the gap and the
   junctions where the bite meets the card's edges are filleted instead of sharp.

   ⚠⚠ THE MASK CANNOT GO ON THE ELEMENT THAT HOLDS THE BUTTON. A mask applies to an element AND
   all its descendants, so masking the card erases the button along with the corner. That is why
   the first attempt used an opaque halo ring instead — which paints a convincing bite but is
   still paint: nothing behind it shows through, and its edges cross the card's own edges at a
   hard angle. The client caught both.
   So the mask goes on the LINK, which paints the whole card and is a SIBLING of the button. That
   in turn is why the background, the radius, the overflow and (on rows) the padding all moved off
   the wrappers and onto the links below: the link had to become the thing that paints.

   The geometry is Temani Afif's inverted-radius, with his --x/--y offsets at zero so the bite is
   centred on the corner. Five mask layers: the bite itself, two conic quadrants that keep the rest
   of the card opaque, and two small radials that round the junctions. --dk-ns is the bite, --dk-nr
   the fillet. */
.dk-notch {
  --dk-nm: /calc(2*var(--dk-nr)) calc(2*var(--dk-nr)) radial-gradient(#000 70%, #0000 72%);
  --dk-ng: conic-gradient(at calc(100% - var(--dk-nr)) var(--dk-nr), #0000 25%, #000 0);
  --dk-nd: (var(--dk-ns) + var(--dk-nr));
  -webkit-mask:
    calc(100% - var(--dk-nd)) 0 var(--dk-nm),
    100% calc(var(--dk-nd)) var(--dk-nm),
    radial-gradient(var(--dk-ns) at 100% 0, #0000 99%, #000 calc(100% + 1px)) calc(-1*var(--dk-nr)) calc(var(--dk-nr)),
    var(--dk-ng) calc(-1*var(--dk-nd)) 0,
    var(--dk-ng) 0 calc(var(--dk-nd));
  mask:
    calc(100% - var(--dk-nd)) 0 var(--dk-nm),
    100% calc(var(--dk-nd)) var(--dk-nm),
    radial-gradient(var(--dk-ns) at 100% 0, #0000 99%, #000 calc(100% + 1px)) calc(-1*var(--dk-nr)) calc(var(--dk-nr)),
    var(--dk-ng) calc(-1*var(--dk-nd)) 0,
    var(--dk-ng) 0 calc(var(--dk-nd));
  -webkit-mask-repeat: no-repeat;
  mask-repeat: no-repeat;
}

/* The two row types are shallower, so the bite is proportionally smaller on them. On the WRAPPER,
   so the button inherits the same number and stays concentric. */
.dk-feat__row { --dk-ns: 24px; }

.dk-also__row { --dk-ns: 24px; }

.dk-feat__rowlink {
  /* Client: the card contents felt claustrophobic. More room inside, on all four sides, and the
     right-hand reserve for the notch grows with it. */
  padding: clamp(0.95rem, 1.8vw, 1.25rem) 3.4rem clamp(0.95rem, 1.8vw, 1.25rem) clamp(0.95rem, 1.8vw, 1.25rem);
  border-radius: calc(var(--dk-r) * 0.75);
  background: var(--dk-quiet);
}

.dk-also__rowlink {
  padding: 0.95rem 3.3rem 0.95rem 1rem;
  border-radius: calc(var(--dk-r) * 0.6);
  background: var(--dk-rowbg);
  transition: background-color 220ms cubic-bezier(.22,.61,.36,1);
}

/* ============================================================ ROUND BUTTON */

.dk-round {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 42px;
  height: 42px;
  padding: 0;
  font-size: 1rem;
  background: transparent;
  border: var(--dk-borderw) solid var(--dk-border);
  border-radius: 50%;
  color: var(--dk-ink);
  cursor: pointer;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1), border-color 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-round:hover { background: var(--dk-ink); border-color: var(--dk-ink); color: var(--dk-paper); }

.dk-round:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

.dk-round[disabled] { opacity: 0.3; cursor: default; }

@media (pointer: coarse) { .dk-round { width: 44px; height: 44px; } }

/* ========================================================== CHROME: the nav
   One rounded bar. Reader controls left, wordmark dead centre, theme switch and
   Sections right. Three tracks with the middle one centred, so the wordmark is
   centred on the PAGE and not on whatever the two sides happen to measure. */

/* ⚠ NO full-width ground, at rest or on scroll. A solid strip across the viewport cut a
   hard horizontal edge through the accent shape as the page moved under it, which is
   exactly the seam this direction is trying not to have. The bar is a floating pill and it
   earns its separation from the page with GLASS instead: a translucent ground plus a
   backdrop blur, so what scrolls beneath stays suggested rather than hidden. */
.dkc-nav {
  position: sticky;
  top: 0;
  z-index: 40;
  padding: clamp(0.6rem, 1.6vw, 1rem) clamp(0.7rem, 3vw, 2rem);
  background: transparent;
  pointer-events: none;
}

/* The strip itself must not swallow clicks meant for the page behind it.
   ⚠ And the bar needs its own z-index: the scrim is a LATER sibling inside this same
   stacking context, so without one it painted straight over the bar and the controls
   disappeared behind the blur the moment the menu opened. */
.dkc-nav__bar { position: relative; z-index: 1; pointer-events: auto; }

.dkc-scrim { pointer-events: auto; }

.dkc-mega { pointer-events: auto; }

.dkc-nav__bar {
  position: relative;
  display: flex;
  align-items: center;
  gap: 0.3rem;
  max-width: 86rem;
  margin-inline: auto;
  padding: 0.45rem 0.55rem;
  border: 1px solid var(--dk-line);
  border-radius: 999px;
  /* 82% and not less: the bar carries text, and its contrast has to survive whatever
     scrolls under it. At this weight the ground stays within a shade of the solid colour
     even over a photograph, while still reading as glass. */
  background: color-mix(in srgb, var(--dk-quiet) 82%, transparent);
  -webkit-backdrop-filter: blur(16px) saturate(1.5);
  backdrop-filter: blur(16px) saturate(1.5);
  box-shadow: 0 8px 26px -16px var(--dk-shadow);
  transition: box-shadow 320ms cubic-bezier(.22,.61,.36,1);
}

/* Lifted a little further off the page once it has something to float above. */
.dkc-nav[data-stuck="true"] { box-shadow: none; }

.dkc-nav__bar[data-stuck="true"] { box-shadow: 0 14px 36px -18px var(--dk-shadow); }

/* THE BAR LEAVES ON THE WAY DOWN AND COMES BACK ON THE WAY UP, on wide screens too.
   The small-screen bar already never moves, because it sits at the foot of the viewport
   and is the one being reached for; this is the top bar on a desktop, where the same
   reading-room argument applies as for the wordmark pill.

   ⚠ The TRANSFORM GOES ON THE BAR, never on `.dkc-nav`. The nav holds the scrim, which is
   `position: fixed; inset: 0`, and a transformed ancestor becomes the containing block for
   its fixed descendants: the scrim would stop covering the viewport and start covering the
   nav. `filter`, `backdrop-filter`, `transform`, `perspective` and `will-change` all do
   this, and it is the same trap that kept the wordmark trapped inside the bar. → §6h-iv

   Exit timing on the base rule, entrance timing on the away state, so returning is faster
   than leaving with no second class and no JS. → §6f-v */
.dkc-nav__bar { transition: box-shadow 320ms cubic-bezier(.22,.61,.36,1), transform 260ms cubic-bezier(.4,0,1,1), opacity 200ms linear; }

.dkc-nav__bar[data-away="true"] {
  transform: translateY(-155%);
  opacity: 0;
  pointer-events: none;
  transition: transform 380ms cubic-bezier(.22,.61,.36,1), opacity 260ms linear;
}

/* ⚠ Below 60rem the bar is the FIXED BOTTOM BAR and must never leave: it is the control
   surface under the reader's thumb. The JS writes one attribute for both sizes, and this is
   what makes it mean nothing down here. */
@media (width < 60rem) { .dkc-nav__bar[data-away="true"] { transform: none; opacity: 1; pointer-events: auto; } }

/* Reduced motion is handled with the rest of the chrome in the REDUCED MOTION section, by
   killing the transition rather than the hide: the bar still leaves and returns, instantly.
   Instant is not motion, which is the same call already made for the wordmark pill. */

.dkc-nav__link {
  padding: 0.35rem 0.6rem;
  border-radius: 999px;
  color: var(--dk-ink);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.8125rem;
  font-weight: 600;
  text-decoration: none;
  white-space: nowrap;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1);
}

.dkc-nav__link:hover { background: var(--dk-paper); }

.dkc-nav__link:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-nav__link { min-height: 44px; display: flex; align-items: center; } }

.dkc-nav__icon {
  flex: none;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 34px;
  height: 34px;
  padding: 0;
  background: transparent;
  border: 0;
  border-radius: 50%;
  color: var(--dk-ink);
  font-size: 0.9375rem;
  cursor: pointer;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1);
}

.dkc-nav__icon:hover { background: var(--dk-paper); }

.dkc-nav__icon:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-nav__icon { width: 44px; height: 44px; } }

/* Centred on the NAV, so it does not drift with the width of either group, and out of the
   bar's flow entirely so it takes no part in the row's spacing.
   ⚠ It must not be a CHILD of the bar: the bar carries a backdrop-filter, and a filtered
   element is the containing block for its position:fixed descendants, so the small-screen
   version below could never leave the bar. It rendered inside the bottom bar instead. */
/* Two lines now: the wordmark, and the tagline under it. The anchor is the LAYOUT box and
   the type lives on the two children, because a single element cannot set two sizes and
   `text-overflow: ellipsis` on the anchor would have clipped whichever line was longer
   rather than the one that needed it. */
/* ⚠⚠ CENTRED WITH `inset-inline: 0` PLUS `margin-inline: auto`, NOT WITH `left: 50%`.
   An out-of-flow box with only `left` set is SHRINK-TO-FIT, and the width it shrinks to fit
   is the space from that `left` to the containing block's right edge. At `left: 50%` that is
   half the width, whatever `max-width` says, so the box can never be wider than half its
   container. With a one-line wordmark nobody noticed. Adding the tagline made the content
   wider than that half, and both lines came out ELLIPSISED on a phone: "CHRISTIAN TRE...".
   Pinning both edges gives the full width to shrink-to-fit inside, and `margin-inline: auto`
   does the centring, which also means the rest state needs no horizontal transform at all. */
.dkc-nav__logo {
  position: absolute;
  top: 50%;
  inset-inline: 0;
  z-index: 2;
  pointer-events: auto;
  transform: translateY(-50%);
  width: fit-content;
  margin-inline: auto;
  max-width: 52%;
  display: flex;
  align-items: center;
  gap: 0.55rem;
  color: var(--dk-ink);
  text-decoration: none;
  /* The ENTRANCE timing. The exit lives on the away state below, so coming back is faster
     than leaving with no second class and no JS. → §6f-v */
  transition: transform 260ms cubic-bezier(.22,.61,.36,1), opacity 200ms linear;
}

/* ⚠ THE WORDMARK LEAVES WITH THE BAR ON WIDE SCREENS TOO. It is a SIBLING of the bar and not
   a child (the bar's backdrop-filter would trap it, §6h-iv), so it does not inherit the
   bar's transform and needs its own away state. Without this it sat alone at the top of the
   viewport after the bar had gone, which is what the client reported.
   ONE translate function at both ends, not `translateY(-50%) translateY(-210%)`: a transform
   list can only interpolate against a list of the same length, and mismatched ends do not
   transition at all, they jump. The rest state is -50% for vertical centring, so the away
   state is a single larger negative on the same axis. */
.dkc-nav__logo[data-hidden="true"] {
  transform: translateY(-260%);
  opacity: 0;
  pointer-events: none;
  transition: transform 380ms cubic-bezier(.22,.61,.36,1), opacity 260ms linear;
}

.dkc-nav__logo:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 4px; }

.dkc-nav__wordmark {
  display: block;
  max-width: 100%;
  overflow: hidden;
  text-overflow: ellipsis;
  /* ⚠ DECLARES its colour rather than inheriting the anchor's. Any subtree that re-points a
     colour token passes the value already COMPUTED further up to anything with no colour of its
     own, which is the fault that made the hero's headline invisible (§6h-viii). One
     declaration, the same value it inherited, and it is immune. */
  color: var(--dk-ink);
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 78, "wght" 800;
  font-size: clamp(1.05rem, 2.3vw, 1.65rem);
  letter-spacing: -0.02em;
  text-transform: uppercase;
  line-height: 1;
  white-space: nowrap;
}

/* THE DEVICE.
   ⚠⚠ ITS HEIGHT IS DECLARED PER BAND, AND `align-self: stretch` CANNOT DO THIS JOB. Stretch
   looked like the self-maintaining answer: make the image as tall as the flex line, which is the
   two-line text block. It does not work, because flexbox sizes the line from each item's
   HYPOTHETICAL cross size first, and for an `<img>` with `height: auto` that is its INTRINSIC
   32px. So the 32px became a floor: measured, the pill went from 51.6px to 53.8px at
   <60rem and from 43.7px to 48.4px under the short-phone dials — and the hero's top clearance
   is arithmetic derived from that height (§6h-vi), so it is not a 2px cosmetic drift.
   Three explicit sizes instead, each matching the measured text-block height for that band:
     · >= 60rem   wordmark 26.4 + gap 2.56 + tagline 9 = 37.96  ->  2.37rem
     · <  60rem   wordmark 19.2 + gap 2.56 + tagline 8 = 29.76  ->  1.86rem
     · short      wordmark 16.8 + gap 2.56 + tagline 8 = 27.36  ->  1.71rem
   Both dimensions are definite by design here, so §3.1's aspect-ratio trap cannot apply. The
   width and height ATTRIBUTES stay on the img: they are what prevents layout shift before the
   SVG has loaded. */
.dkc-nav__mark {
  flex: none;
  width: 2.37rem;
  height: 2.37rem;
}

/* The two lines, left aligned against the device rather than centred on it. */
.dkc-nav__lines {
  display: grid;
  justify-items: start;
  gap: 0.16rem;
  min-width: 0;
}

/* ⚠ The tagline sits on GLASS, not on the page ground, and what is under that glass is the
   page, the violet accent blob, or — on a phone, where the pill floats over the hero — a
   PHOTOGRAPH. So it takes `--dk-glassmuted` rather than `--dk-muted`: measured with
   `node tools/contrast.mjs deck` against the ground flattened twice AND against the worst
   image each theme can put behind it. On `--dk-muted` it measured 3.50:1 over a black image
   in the light theme, which is a fail on 8px type that had never been measured because only
   the flattering pair was in the matrix. */
.dkc-nav__tagline {
  display: block;
  max-width: 100%;
  overflow: hidden;
  text-overflow: ellipsis;
  font-family: "Archivo", system-ui, sans-serif;
  font-weight: 600;
  font-size: 0.5rem;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  line-height: 1;
  color: var(--dk-glassmuted);
  white-space: nowrap;
}

@media (width >= 60rem) { .dkc-nav__tagline { font-size: 0.5625rem; } }

.dkc-theme {
  flex: none;
  position: relative;
  display: grid;
  place-items: center;
  width: 38px;
  height: 38px;
  padding: 0;
  background: var(--dk-paper);
  border: 1px solid var(--dk-line);
  border-radius: 50%;
  color: var(--dk-ink);
  font-size: 0.9375rem;
  cursor: pointer;
  overflow: hidden;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1);
}

.dkc-theme:hover { background: var(--dk-lime); color: #16171A; }

.dkc-theme:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-theme { width: 44px; height: 44px; } }

/* The two glyphs cross over. Driven by a var on the button so no descendant
   selector is needed. */
.dkc-theme__sun {
  grid-area: 1 / 1;
  display: grid;
  place-items: center;
  transform: translateY(calc(var(--dk-moon, 0) * -160%));
  opacity: calc(1 - var(--dk-moon, 0));
  transition: transform 340ms cubic-bezier(.22,.61,.36,1), opacity 220ms cubic-bezier(.22,.61,.36,1);
}

.dkc-theme__moon {
  grid-area: 1 / 1;
  display: grid;
  place-items: center;
  transform: translateY(calc((1 - var(--dk-moon, 0)) * 160%));
  opacity: var(--dk-moon, 0);
  transition: transform 340ms cubic-bezier(.22,.61,.36,1), opacity 220ms cubic-bezier(.22,.61,.36,1);
}

.dkc-theme[aria-pressed="true"] { --dk-moon: 1; }

.dkc-nav__toggle {
  flex: none;
  display: inline-flex;
  align-items: center;
  gap: 0.55rem;
  padding: 0.3rem 0.3rem 0.3rem 0.95rem;
  background: var(--dk-violet);
  border: 1px solid var(--dk-violet);
  border-radius: 999px;
  color: #F4F3EF;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.8125rem;
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  cursor: pointer;
  transition: background-color 220ms cubic-bezier(.22,.61,.36,1), border-color 220ms cubic-bezier(.22,.61,.36,1);
}

.dkc-nav__toggle:hover { background: #16171A; border-color: #16171A; }

.dkc-nav__toggle:focus-visible { outline: 2px solid var(--dk-ink); outline-offset: 3px; }

@media (pointer: coarse) { .dkc-nav__toggle { min-height: 44px; } }

.dkc-nav__togglelabel { white-space: nowrap; }

.dkc-nav__togglebadge {
  display: grid;
  place-items: center;
  width: 28px;
  height: 28px;
  border-radius: 50%;
  background: #F4F3EF;
  color: #5B2BE0;
  font-size: 0.875rem;
  flex: none;
}

/* ==================================================== CHROME: the mega menu
   Four blocks, one per meta-category, in the page's own block language. Opens
   with a slide-down wipe.
   ⚠ clip-path clips the element's own box-shadow, so the open end uses NEGATIVE
   insets sized to the shadow's reach. Both ends need the same component count
   or the value cannot interpolate. → HANDOFF §6f-v */

.dkc-mega {
  position: absolute;
  top: 100%;
  left: 0;
  right: 0;
  z-index: 41;
  max-height: min(82vh, 46rem);
  overflow-y: auto;
  overscroll-behavior: contain;
  padding: 0 clamp(0.7rem, 3vw, 2rem) clamp(0.7rem, 3vw, 2rem);
  clip-path: inset(0 -60px 100% -60px);
  opacity: 0;
  transition: clip-path 190ms cubic-bezier(.4,0,1,1), opacity 140ms cubic-bezier(.4,0,1,1);
}

.dkc-mega[data-open="true"] {
  clip-path: inset(0 -60px -90px -60px);
  opacity: 1;
  transition: clip-path 320ms cubic-bezier(.22,.61,.36,1), opacity 220ms cubic-bezier(.22,.61,.36,1);
}

/* An author `display` rule beats the UA's `[hidden]{display:none}`, so the pair
   must be restated or the panel can never close. → kit 03 §7a */
.dkc-mega[hidden] { display: none; }

.dkc-mega__inner {
  max-width: 86rem;
  margin-inline: auto;
  padding: clamp(1rem, 2.4vw, 1.6rem);
  border-radius: var(--dk-r);
  background: var(--dk-quiet);
  box-shadow: 0 30px 60px -20px var(--dk-shadow);
  transform: translateY(-1.2rem);
  transition: transform 190ms cubic-bezier(.4,0,1,1);
}

.dkc-mega__inner[data-open="true"] {
  transform: none;
  transition: transform 360ms cubic-bezier(.22,.61,.36,1);
}

.dkc-mega__blocks {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(0.7rem, 1.6vw, 1rem);
}

@media (width >= 40rem) { .dkc-mega__blocks { grid-template-columns: repeat(2, 1fr); } }

@media (width >= 68rem) { .dkc-mega__blocks { grid-template-columns: repeat(4, 1fr); } }

.dkc-mega__block {
  padding: clamp(0.9rem, 2vw, 1.4rem);
  border-radius: calc(var(--dk-r) * 0.8);
  min-width: 0;
}

.dkc-mega__block--violet { background: var(--dk-violet); color: #F4F3EF; }

.dkc-mega__block--lime { background: var(--dk-lime); color: #16171A; }

.dkc-mega__block--pink { background: var(--dk-pink); color: #16171A; }

.dkc-mega__block--quiet { background: var(--dk-paper); color: var(--dk-ink); }

.dkc-mega__grouptitle {
  margin: 0 0 0.9rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  /* ⚠ OPACITY IS A CONTRAST CHANGE. Muting text with opacity composites it toward the
     ground, so the real ratio is whatever the mix measures, not what the solid colour
     measured. These labels sit on violet, lime AND pink, so the floor is set by the
     WORST of the three: pink needs >= 0.81 to clear 4.5:1, violet >= 0.77, lime >= 0.61.
     0.85 for all of them, with headroom. Measured at 0.72 this was 3.88:1 on pink. */
  opacity: 0.85;
}

.dkc-mega__list { margin: 0; padding: 0; list-style: none; }

.dkc-mega__item { margin: 0; }

.dkc-mega__link {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: 0.6rem;
  padding: 0.34rem 0;
  color: inherit;
  text-decoration: none;
  transition: opacity 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-mega__link:hover { opacity: 0.65; }

.dkc-mega__link:focus-visible { outline: 2px solid currentColor; outline-offset: 2px; }

@media (pointer: coarse) { .dkc-mega__link { min-height: 44px; align-items: center; } }

.dkc-mega__name {
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 92, "wght" 700;
  font-size: 1.0625rem;
  line-height: 1.2;
  letter-spacing: -0.01em;
}

.dkc-mega__count {
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
 
  /* ⚠ OPACITY IS A CONTRAST CHANGE. Muting text with opacity composites it toward the
     ground, so the real ratio is whatever the mix measures, not what the solid colour
     measured. These labels sit on violet, lime AND pink, so the floor is set by the
     WORST of the three: pink needs >= 0.81 to clear 4.5:1, violet >= 0.77, lime >= 0.61.
     0.85 for all of them, with headroom. Measured at 0.72 this was 3.88:1 on pink. */
  opacity: 0.85;
}

.dkc-mega__foot {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(0.9rem, 2vw, 1.4rem);
  margin-top: clamp(0.7rem, 1.6vw, 1rem);
  padding: clamp(0.9rem, 2vw, 1.4rem);
  border-radius: calc(var(--dk-r) * 0.8);
  background: var(--dk-paper);
}

@media (width >= 52rem) {
  .dkc-mega__foot { grid-template-columns: minmax(0, 1fr) minmax(0, 14rem); align-items: start; }
}

.dkc-mega__issue {
  display: grid;
  grid-template-columns: minmax(0, 8rem) minmax(0, 1fr);
  gap: clamp(0.9rem, 2vw, 1.3rem);
  align-items: start;
}

.dkc-mega__issuecover {
  display: block;
  max-width: 8rem;
  border-radius: calc(var(--dk-r) * 0.45);
  overflow: hidden;
  text-decoration: none;
  transition: transform 260ms cubic-bezier(.22,.61,.36,1);
}

.dkc-mega__issuecover:hover { transform: translateY(-4px); }

.dkc-mega__issuecover:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 3px; }

/* The cover's OWN ratio, so a printed cover is never cropped. */
.dkc-mega__issueimg {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 866 / 1110;
  background: var(--dk-quiet);
}

.dkc-mega__issueside { min-width: 0; }

.dkc-mega__issuelabel {
  margin: 0 0 0.2rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--dk-accenttext);
}

.dkc-mega__issueline {
  margin: 0 0 0.7rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  letter-spacing: 0.03em;
  color: var(--dk-muted);
}

.dkc-mega__issuelinks { margin: 0; padding: 0; list-style: none; }

.dkc-mega__issueitem { margin: 0; }

.dkc-mega__issuelink {
  display: block;
  padding: 0.3rem 0;
  color: var(--dk-ink);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.9375rem;
  font-weight: 600;
  text-decoration: none;
  transition: color 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-mega__issuelink:hover { color: var(--dk-accenttext); }

.dkc-mega__issuelink:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-mega__issuelink { min-height: 44px; display: flex; align-items: center; } }

/* Deliberately quiet: not what anyone opens the menu for. */
.dkc-mega__about {
  margin: 0;
  padding: 0;
  list-style: none;
}

.dkc-mega__aboutitem { margin: 0; }

.dkc-mega__aboutlink {
  display: block;
  padding: 0.26rem 0;
  color: var(--dk-muted);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.8125rem;
  font-weight: 500;
  text-decoration: none;
  transition: color 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-mega__aboutlink:hover { color: var(--dk-ink); }

.dkc-mega__aboutlink:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-mega__aboutlink { min-height: 44px; display: flex; align-items: center; } }

/* ================================================================= THE DECK
   Three lists kept in step by one index: the cards, the text panel and the
   byline legend. Every article is real markup rather than strings injected by
   script, which is what keeps it readable without JS and announceable to a
   screen reader. */

/* FULL BLEED. The section runs edge to edge so the accent shape enters from the screen
   edge rather than being cut off at a content rail; the grid inside keeps its own
   measure so the columns do not sprawl on a wide monitor. */
.dk-deck {
  position: relative;
  z-index: 1;
  padding-block: clamp(1.4rem, 3.4vw, 2.6rem) clamp(1.8rem, 4vw, 3rem);
  overflow: hidden;
}

.dk-deck__inner {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1.2rem, 3vw, 2rem);
  /* The same rail as the nav and the bands. The SECTION is full bleed so the accent shape
     can enter from the screen edge; the grid inside stays on the page's measure, or the
     three columns drift apart on a wide monitor and stop reading as one composition. */
  max-width: 86rem;
  margin-inline: auto;
  padding-inline: clamp(1rem, 3vw, 2rem);
}

/* Three columns, and TWO rows, so the call to action can be pinned to the foot of the
   right-hand column instead of floating up and down with the length of each standfirst. */
@media (width >= 62rem) {
  .dk-deck__inner {
    grid-template-columns: minmax(0, 0.72fr) minmax(0, 1.25fr) minmax(0, 1fr);
    grid-template-rows: 1fr auto;
    align-items: stretch;
  }
}

/* ⚠ The copy wrapper exists only for the overlay band. On the desktop layout it must not be a
   box at all, or the legend and the panel become its children instead of the hero grid's and
   the three-column layout collapses into one cell. `display: contents` is what lets one
   wrapper serve a layout that needs it and a layout that must not see it. */
@media (width >= 62rem) { .dk-deck__copy { display: contents; } }

@media (width >= 62rem) { .dk-deck__legend { grid-column: 1; grid-row: 1 / 3; } }

@media (width >= 62rem) { .dk-deck__stage { grid-column: 2; grid-row: 1 / 3; } }

/* Both rows now that the button has gone, and the base rule's `align-content: center` does the
   rest: the headline and the standfirst sit on the deck's own centre line. */
@media (width >= 62rem) { .dk-deck__panel { grid-column: 3; grid-row: 1 / 3; } }

/* Centred, and the same height whichever card is live. Above 62rem this is a real box
   holding the counter and the byline as one centred group in the left column.
   ⚠ Below 62rem it becomes `display: contents` (see the band rules further down) so the
   counter can sit above the HEADLINE, which is in a different container. That is why the
   counter and the byline each carry their own `position: relative; z-index` rather than
   inheriting one from here: a `display: contents` element generates no box, so it can
   neither stack nor be a reveal target. */
.dk-deck__legend {
  position: relative;
  z-index: 2;
  display: flex;
  flex-direction: column;
  justify-content: center;
  gap: 0.8rem;
  min-width: 0;
}

/* ⚠ THE METAS NEED THEIR OWN GRID. They carried `grid-area: 1 / 1` while their parent was
   a FLEX column, where it means nothing, so all five stacked vertically instead of
   overlaying: the live byline sat at a different height on every card, and the four
   invisible ones padded roughly 500px of empty space into the section, which is what read
   as a huge gap before the next band on a phone. */
/* The chip list. One box per card, all five in ONE grid cell so the block is the height of
   one chip whichever card is live, exactly like the byline list below it. */
.dk-deck__chips {
  position: relative;
  z-index: 2;
  display: grid;
  align-items: start;
  justify-items: start;
  min-width: 0;
  order: 3;
}

.dk-deck__chipbox {
  grid-area: 1 / 1;
  opacity: 0;
  transform: translateY(10px);
  transition: opacity 240ms cubic-bezier(.22,.61,.36,1), transform 240ms cubic-bezier(.22,.61,.36,1);
  pointer-events: none;
}

.dk-deck__chipbox[data-pos="0"] { opacity: 1; transform: none; pointer-events: auto; transition-delay: 130ms; }

.dk-deck__metas {
  position: relative;
  z-index: 2;
  display: grid;
  align-items: center;
  min-width: 0;
  order: 5;
}

.dk-deck__count {
  position: relative;
  z-index: 2;
  order: 2;
  color: var(--dk-ink);
  margin: 0;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 80, "wght" 800;
  font-size: clamp(1.6rem, 3.4vw, 2.6rem);
  line-height: 1;
  letter-spacing: -0.02em;
  font-variant-numeric: tabular-nums;
}

.dk-deck__countnow { color: var(--dk-accenttext); }

.dk-deck__countof { color: var(--dk-muted); }

/* Only the live article's byline is shown; the rest are held out of the flow so
   the block does not grow to its tallest member. */
.dk-deck__meta {
  grid-area: 1 / 1;
  opacity: 0;
  transform: translateY(10px);
  transition: opacity 240ms cubic-bezier(.22,.61,.36,1), transform 240ms cubic-bezier(.22,.61,.36,1);
  pointer-events: none;
}

.dk-deck__meta[data-pos="0"] { opacity: 1; transform: none; pointer-events: auto; transition-delay: 130ms; }

/* The hero pill links to the category archive too. Ink ground on hover: paper on it is 16.14:1. */
.dk-deck__chip {
  display: inline-block;
  padding: 0.3rem 0.75rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-deck__metaline {
  margin: 0;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.8125rem;
  color: var(--dk-muted);
}

.dk-deck__stage {
  position: relative;
  z-index: 2;
  display: flex;
  align-items: center;
  gap: 0.5rem;
  min-width: 0;
  order: 1;
  /* pan-y: the page still scrolls vertically through the deck, while a horizontal drag is
     ours to interpret as a swipe. */
  touch-action: pan-y;
}

/* ⚠ Above the cards. The arrows are laid out correctly either side of the stack, but the
   fanned cards carry z-index 1 to 5 and translate outward by up to 11%, so the next arrow
   was sitting UNDER a card: present, correctly positioned, and unclickable. Confirmed
   with elementFromPoint, which returned the card image rather than the button. */
.dk-deck__arrow {
  position: relative;
  z-index: 6;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 46px;
  height: 46px;
  flex: none;
  padding: 0;
  font-size: 1.05rem;
  background: var(--dk-paper);
  border: var(--dk-borderw) solid var(--dk-border);
  border-radius: 50%;
  color: var(--dk-ink);
  cursor: pointer;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1), transform 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-deck__arrow:hover { background: var(--dk-violet); border-color: var(--dk-accenttext); color: #F4F3EF; }

.dk-deck__arrow:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 3px; }

.dk-deck__arrow--prev:hover { transform: translateX(-3px); }

.dk-deck__arrow--next:hover { transform: translateX(3px); }

/* The stack. Every card sits in one grid cell and the position attribute does
   the fanning, so dealing a card is a change of one attribute. */
/* ⚠ `flex: 1 1 0`, not `auto`. With `auto` the flex base is the content size, and the
   content is a 1200px-wide image, so the stack claimed the whole row and pushed the
   next arrow clean off the section (which is `overflow: hidden`, so it vanished rather
   than overflowing visibly). A zero base makes it take what is left after the arrows. */
.dk-deck__stack {
  position: relative;
  display: grid;
  flex: 1 1 0;
  min-width: 0;
  margin: 0;
  padding: 0;
  list-style: none;
  aspect-ratio: 4 / 5;
}

.dk-deck__card {
  grid-area: 1 / 1;
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-quiet);
  box-shadow: 0 24px 50px -24px var(--dk-shadow);
  transform-origin: 50% 100%;
  transition: transform 520ms cubic-bezier(.22,.61,.36,1), opacity 420ms cubic-bezier(.22,.61,.36,1);
}

.dk-deck__card[data-pos="0"] { transform: none; opacity: 1; z-index: 5; }

.dk-deck__card[data-pos="1"] { transform: translate(6%, -4%) rotate(4deg) scale(0.92); opacity: 1; z-index: 4; }

.dk-deck__card[data-pos="2"] { transform: translate(11%, -7%) rotate(7.5deg) scale(0.85); opacity: 0.75; z-index: 3; }

.dk-deck__card[data-pos="3"] { transform: translate(-6%, -8%) rotate(-5deg) scale(0.8); opacity: 0.45; z-index: 2; }

.dk-deck__card[data-pos="4"] { transform: translate(-9%, -10%) rotate(-8deg) scale(0.76); opacity: 0.25; z-index: 1; }

.dk-deck__img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

/* Flow order in the one-column band, and the button is gone from it entirely:
   deck 1, counter 2, category 3, headline and standfirst 4, byline 5. Explicit on every one,
   because they are no longer all children of the same wrapper. */
.dk-deck__panel {
  position: relative;
  z-index: 2;
  display: grid;
  align-content: center;
  min-width: 0;
  order: 4;
}

@media (width < 62rem) { .dk-deck__panel { position: relative; align-content: start; } }

/* ================================================ THE OVERLAY HERO, BELOW 62rem
   ⚠⚠ THIS REPLACES BOTH NARROW LAYOUTS. The two-column band and the stacked band are gone,
   and so is the whole family of problems they generated across three review rounds: the fan
   sitting on the copy, the arrows landing at different distances from the card, the card
   shrinking to nothing so the copy could have a column, the byline falling behind the bottom
   bar on short phones, and the impossible three-way choice between a continuous copy block,
   a centred one and a still one.

   Instead the card takes the full width and the copy sits ON it, over a translucent scrim.
   Nothing is beside anything, so nothing has to be balanced against anything: there is one
   column, and its width is the screen's.

   Client's instruction, 2026-08-19, and it is a better idea than either layout it replaces. */

/* One cell. The stage and the copy both live in it; the copy is later in the DOM so it paints
   on top without having to out-rank the fan's z-index 1 to 5. */
@media (width < 62rem) {
  .dk-deck__inner {
    grid-template-columns: minmax(0, 1fr);
    grid-template-rows: minmax(0, 1fr);
    gap: 0;
    /* ⚠ THE INSET HAS TO CLEAR THE FAN, NOT THE CARD. At 0.6rem the card's own edges were
       comfortable and the fanned cards behind it ran straight off the screen, so the deck read
       as cropped rather than stacked. The fan reaches about 8% past the card on each side once
       the rotation is counted, so the inset is sized from that rather than from taste.
       Measured by tools/fit.mjs, which reports the gap from the fan's outermost edge to the
       viewport at every width. */
    padding-inline: clamp(1.9rem, 6vw, 3.25rem);
  }
}

/* ⚠⚠ `z-index: auto`, AND THAT IS WHAT MAKES THE ARROWS CLICKABLE. The stage's base rule is
   `position: relative; z-index: 2`, which makes it a STACKING CONTEXT, so the arrows' own
   `z-index: 7` only ordered them against their siblings inside the stage — it could never lift
   them above the copy block's `z-index: 6`, because the whole stage subtree was flattened to
   layer 2. The copy therefore painted over the arrows and swallowed every click.
   With `auto` the stage stops being a context and its children compete directly in the
   section's: cards 1 to 5, copy 6, arrows 7. Nothing else had to move. */
@media (width < 62rem) { .dk-deck__stage { grid-area: 1 / 1; display: block; z-index: auto; } }

@media (width < 62rem) { .dk-deck__copy { grid-area: 1 / 1; } }

/* ⚠ The legend keeps its `display: contents` here, for the same reason as before: the counter
   and the byline live inside it, the headline lives in the panel, and the overlay needs all
   four in ONE flow so the order can be counter, category, headline, standfirst, byline. */
@media (width < 62rem) { .dk-deck__legend { display: contents; } }

/* ⚠⚠ THE OVERLAY HERO IS A DARK CARD IN BOTH THEMES. The light-theme scrim was a white wash
   over the photograph and the client's read was right: it looked washed out where the dark one
   looks deliberate. So the hero pins our own tokens to their dark-theme values for its own
   subtree, and because custom properties INHERIT, every rule underneath keeps working exactly
   as written — no descendant selector, no second set of colour rules, nothing below this line
   has to know.

   These are not new colours. Every value here is one the palette already carries; the only
   change is that they stop swapping with the theme inside this one section. That is the §5d
   rule applied to a whole surface rather than to a single role: if a colour's legal ground is
   fixed, pin it where it is used and let the name carry the constraint.

   Contrast is measured against the WORST image the card can hold, not against the page:
   tools/contrast.mjs deck carries pure-white and pure-black grounds for every pair here. */
@media (width < 62rem) {
  .dk-deck {
    --dk-paper: #16171A;
    --dk-ink: #F4F3EF;
    --dk-quiet: #22242A;
    --dk-line: #33363D;
    --dk-muted: #ADADAB;
    --dk-border: #9A9A98;
    /* ⚠ A LIGHTER LIFT THAN THE DARK THEME'S, because the ground here is harder than the dark
       theme's ground. The counter's digit sits on the scrim, and the scrim over a bright image
       is #2D2E31 rather than #16171A: the theme's own #987BE6 measures 5.39:1 on the ground and
       only 4.08:1 on that, which fails. Violet lifted 50% toward paper instead of 40% gives
       5.02:1 on the worst image and 6.62:1 on the ground. Still a derived tint of the same
       violet, not a new colour, and it keeps the strict 4.5 body-text floor rather than leaning
       on the large-text exemption the 24px numeral would also qualify for. */
    --dk-accenttext: #A88FE8;
    --dk-accentinv: #5B2BE0;
  }
}

/* THE COPY BLOCK, pinned to the foot of the card and carrying the scrim itself.
   ⚠ The scrim belongs to the COPY, not to the card, and that is what makes it safe. A scrim
   sized as a fraction of the card has to guess where the text will be, and a guess that has
   to predict content is the mistake this project has now made twice (§6f-vi, §6h-vi). Here the
   box hugs its own text, the fade is a FIXED 5.5rem at its top edge, and the padding keeps
   every line below that fade. So the text is always over the plateau, whatever it says and
   however the card is sized.
   The plateau is 90% and not 100%: the client asked for translucent, and 90% is measured
   against the worst image either theme can put behind it. → tools/contrast.mjs deck */
/* ⚠ And the copy does not take pointer events at all. Its box reaches 6rem above its own text
   to carry the fade, so even painted BELOW the arrows it would still sit over the middle of the
   card and swallow the swipe gesture, whose listener is on the stage. Hit testing skips a
   `pointer-events: none` box entirely; the live text block inside it restores `auto` from the
   base rule, so the headline link still works. */
@media (width < 62rem) {
  .dk-deck__copy {
    position: relative;
    z-index: 6;
    pointer-events: none;
    display: flex;
    flex-direction: column;
    align-self: end;
    justify-content: flex-end;
    gap: 0.4rem;
    padding: 3rem clamp(1rem, 4vw, 1.6rem) clamp(1rem, 3.5vw, 1.4rem);
    border-end-start-radius: var(--dk-r);
    border-end-end-radius: var(--dk-r);
    background: linear-gradient(
      to top,
      color-mix(in srgb, var(--dk-paper) 90%, transparent) 0,
      color-mix(in srgb, var(--dk-paper) 90%, transparent) calc(100% - 2.6rem),
      transparent 100%);
  }
}

/* The card is the width of the screen and its height comes from the viewport, so there is no
   empty space at the sides at any width and no aspect ratio to fight. `object-fit: cover` on
   the image is what lets the box be any shape. */
@media (width < 62rem) {
  .dk-deck__stack {
    flex: none;
    width: 100%;
    aspect-ratio: auto;
    /* ⚠ 68vh, not 64. The copy block genuinely needs about 355px on a 390px-wide phone (five
       stacked pieces plus its own padding), and the arrows need a clear band above it, so the
       card has to be taller than the sum. At 64vh on a 640px viewport it came out 410px and the
       arrows overlapped the counter by 4px. Raising it 4vh costs 25px of byline clearance, which
       there is plenty of (+110px measured), and buys the band. */
    height: clamp(24rem, 68vh, 34rem);
  }
}

/* ⚠⚠ THE ARROWS GO TO THE CARD'S TOP CORNERS, NOT ITS VERTICAL CENTRE.
   Centred was the obvious placement and it put them straight on top of the counter and the
   category pill: measured 32px to 174px of overlap at every width and height. The reason is that
   the copy block is TALL — its own padding plus five lines of type is 340px of a 427px card on a
   667px phone — so the card's vertical centre is deep inside the copy, not above it.
   The top corners are the only region of a bottom-anchored overlay that is guaranteed to be
   image, which is the same argument that lets a bookmark float in a card's corner (§6a). The gap
   to the copy is asserted per width and height by tools/fit.mjs, so a longer standfirst than any
   in this demo set cannot quietly reintroduce the collision. */
@media (width < 62rem) {
  .dk-deck__arrow {
    position: absolute;
    top: clamp(0.7rem, 2vw, 1.1rem);
    z-index: 7;
    transform: none;
  }
}

@media (width < 62rem) { .dk-deck__arrow--prev { left: clamp(0.4rem, 1.6vw, 0.8rem); } }

@media (width < 62rem) { .dk-deck__arrow--next { right: clamp(0.4rem, 1.6vw, 0.8rem); } }

@media (width < 62rem) { .dk-deck__arrow--prev:hover { transform: translateX(-3px); } }

@media (width < 62rem) { .dk-deck__arrow--next:hover { transform: translateX(3px); } }

/* ⚠ The arrows now sit over a PHOTOGRAPH rather than over the page ground, so they need their
   own opaque ground. Their base rule is a translucent surface that reads fine on paper and
   disappears over a bright window in a cathedral. */
@media (width < 62rem) {
  .dk-deck__arrow {
    background: color-mix(in srgb, var(--dk-paper) 88%, transparent);
    -webkit-backdrop-filter: blur(10px);
    backdrop-filter: blur(10px);
  }
}

/* The copy reflows: the live block is in flow and drives the height, the rest are taken out of
   it so they contribute none while still being painted for the cross-fade. The block sits at
   the bottom of the card, so growing upward is free and nothing below it can be pushed. That
   is the whole reason the overlay dissolves the continuous-versus-still problem. */
@media (width < 62rem) {
  .dk-deck__text {
    position: absolute;
    inset: auto 0 0 0;
  }
}

@media (width < 62rem) {
  .dk-deck__text[data-pos="0"] { position: relative; inset: auto; }
}

@media (width < 62rem) { .dk-deck__panel { align-content: end; } }

/* ⚠⚠ THE FAN IS TUCKED IN, AND THE ROTATION IS THE PART THAT HAD TO GO.
   Cutting the translate alone was not enough, and the reason is worth keeping: a translate is a
   percentage of the card's WIDTH, but a rotation about the bottom centre throws the top corners
   sideways in proportion to the card's HEIGHT. In the overlay layout the height comes from the
   viewport (clamp 24rem..64vh..34rem) and does NOT scale with the width, so on a narrow phone the
   card is tall relative to its width and the same rotation reaches twice as far proportionally.
   Measured: at 991 the fan reached 6% past the card, at 390 it reached 13% — same CSS.

   So the rotation drops to about a third of the desktop values and the translate does most of
   the work. The stack still reads as a stack; it just stops being cut off square at the screen
   edge, which is what the client saw. Verified by the fan-edge column of tools/fit.mjs at every
   width, which reports the gap from the fan's outermost edge to the viewport. */
@media (width < 62rem) { .dk-deck__card[data-pos="1"] { transform: translate(2.4%, -2%) rotate(0.9deg) scale(0.955); } }

@media (width < 62rem) { .dk-deck__card[data-pos="2"] { transform: translate(4.4%, -3.6%) rotate(1.7deg) scale(0.925); } }

@media (width < 62rem) { .dk-deck__card[data-pos="3"] { transform: translate(-2.4%, -4%) rotate(-1.1deg) scale(0.9); } }

@media (width < 62rem) { .dk-deck__card[data-pos="4"] { transform: translate(-3.8%, -5.2%) rotate(-1.8deg) scale(0.875); } }

/* Type sizes for the overlay. The headline is on an image now, so it carries a little more
   weight than it did on the page ground. */
@media (width < 62rem) { .dk-deck__count { font-size: 1.5rem; } }

@media (width < 62rem) { .dk-deck__title { font-size: clamp(1.55rem, 5.4vw, 2.6rem); } }

@media (width < 62rem) { .dk-deck__stand { margin-bottom: 0; font-size: clamp(0.95rem, 2.1vw, 1.05rem); } }

@media (width < 62rem) { .dk-deck__chip { font-size: 0.625rem; } }

.dk-deck__text {
  grid-area: 1 / 1;
  opacity: 0;
  transform: translateY(14px);
  transition: opacity 280ms cubic-bezier(.22,.61,.36,1), transform 280ms cubic-bezier(.22,.61,.36,1);
  pointer-events: none;
}

.dk-deck__text[data-pos="0"] { opacity: 1; transform: none; pointer-events: auto; transition-delay: 130ms; }

/* Plainly legible. No treatment of any kind on the display type: the client's
   instruction after the carved masthead, and the right call. */
/* ⚠⚠ AN EXPLICIT `color`, AND IT IS LOAD-BEARING. The headline used to take its colour by
   INHERITANCE from the body, and inheritance passes the COMPUTED value: `.dk-body` resolves
   `var(--dk-ink)` once, on the body, and every descendant inherits that pixel value. So when the
   overlay hero re-points `--dk-ink` for its own subtree, every rule that USES the property picks
   the new value up and anything relying on inherited colour does NOT. In the light theme the
   headline stayed the dark ink and went invisible on the dark scrim: the largest type on the page,
   gone, with nothing in the console and the palette matrix still reporting the pair as fine.
   Declaring the colour here makes it re-resolve inside any pinned subtree. Same value at the body
   level, so the desktop layout is unchanged. */
.dk-deck__title {
  color: var(--dk-ink);
  margin: 0 0 0.7rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 88, "wght" 800;
  font-size: clamp(1.9rem, 4.2vw, 3.4rem);
  line-height: 0.98;
  letter-spacing: -0.028em;
}

/* The headline links to the article too: plenty of readers reach for the title rather
   than the button, and making them hunt for the one live target is needless. */
.dk-deck__titlelink {
  color: inherit;
  text-decoration: none;
  transition: color 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-deck__titlelink:hover { color: var(--dk-accenttext); }

.dk-deck__titlelink:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 4px; }

.dk-deck__stand {
  margin: 0 0 1.1rem;
  font-size: clamp(1rem, 1.5vw, 1.15rem);
  line-height: 1.5;
  color: var(--dk-muted);
}


/* ==================================================================== BANDS */

.dk-band {
  max-width: 86rem;
  margin-inline: auto;
  /* ⚠ 1.5rem of inline padding, not 1rem. The bookmark protrudes 18px past the rightmost card, and
     at 390px the old 16px padding left it 2px short: the page's own clip then cut it. Side padding
     stops being decoration once something sticks out into it. */
  padding: clamp(1.6rem, 4vw, 3rem) clamp(1.5rem, 3vw, 2rem) clamp(1rem, 2.4vw, 1.6rem);
}

.dk-band__head {
  position: relative;
  z-index: 1;
  display: flex;
  align-items: center;
  justify-content: space-between;
  flex-wrap: wrap;
  gap: 0.8rem 1.5rem;
  margin-bottom: clamp(1rem, 2.4vw, 1.6rem);
}

.dk-band__head--inset { padding-inline: 0; }

.dk-band__title {
  margin: 0;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 84, "wght" 800;
  font-size: clamp(1.8rem, 4.6vw, 3.2rem);
  line-height: 1;
  letter-spacing: -0.028em;
  text-transform: uppercase;
}

.dk-band__all { text-decoration: none; }

.dk-band__all:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 4px; }

.dk-band__ctrls { display: flex; gap: 0.5rem; }

/* Hidden when the rail cannot actually move: at >= 78rem the rail is a plain grid, and arrows
   over a grid that does not scroll are noise. The JS writes data-scrollable; on this sample it
   had been writing it since round 1 with NO rule reading it, so the arrows sat there enabled at
   every desktop width. Threshold has carried the matching rule all along. → HANDOFF §6h-xv
   ⚠ Restated with the attribute, because an author `display` above defeats any UA hiding. */
.dk-band__ctrls[data-scrollable="false"] { display: none; }

/* ============================================================ BAND: FEATURED */

/* ⚠ The band becomes the positioning context for its own background, and the WRAPPER does the
   clipping. Not the section: `overflow: hidden` on an ancestor makes it a scroll container and
   kills `position: sticky` inside it, and `overflow-x` on a wide element is the other half of the
   trap that widens the document. A dedicated wrapper with `overflow: clip` bounds the shape
   without either side effect. → kit 03 §5b */
.dk-band { position: relative; }

/* ⚠ FULL VIEWPORT WIDTH, so the strokes run in from both screen edges instead of starting at the
   band's own measure. The band is capped at 86rem and centred, so reaching the edges needs a
   viewport unit; there is no fixed inset that works at every width.
   The 100vw is safe here because .dk-main carries `overflow-x: clip` (see below), which bounds it
   without creating a scroll container. On its own, 100vw is a real overflow risk on this page: the
   root reserves a stable scrollbar gutter, so 100vw is WIDER than the content box by the
   scrollbar's width and the document would grow. → kit 03 §5b */
.dk-feat__wavewrap {
  position: absolute;
  top: 0;
  bottom: 0;
  left: 50%;
  width: 100vw;
  transform: translateX(-50%);
  z-index: 0;
  overflow: clip;
  pointer-events: none;
}

/* ⚠ IT LIVES IN THE HEAD ZONE, and that is a correction rather than a preference. Drawn across the
   whole band it was almost entirely hidden: the cards fill the band, so a line behind them showed
   only as stray dashes in the gutters, which reads as a broken graphic rather than as a current.
   The head row is the one place in this band with real open space — between the section title and
   the View all button — so the line runs through there and passes BEHIND the title, which is what
   the client's reference does with its own headline. */
.dk-feat__wave {
  position: absolute;
  /* Still a little wider than its wrapper and pulled left, so neither stroke END lands on screen
     even now that the wrapper reaches the edges. A visible line-end reads as a broken graphic. */
  top: clamp(0.4rem, 1.6vw, 1.4rem);
  left: -4%;
  width: 108%;
  height: clamp(7rem, 15vw, 11rem);
  overflow: visible;
}

/* The stroke is the interface line's own colour, not a new one, and thin enough to read as a drawn
   line rather than as a band of colour. `vector-effect` keeps it 1.6px however far the
   non-uniform scale stretches the path, which is what stops it fattening on a wide monitor. */
.dk-feat__wavepath {
  fill: none;
  stroke: var(--dk-accenttext);
  stroke-width: 1.6;
  stroke-linecap: round;
  vector-effect: non-scaling-stroke;
  opacity: 0.5;
}

.dk-feat__wavepath--two { stroke: var(--dk-border); opacity: 0.38; }

/* The content sits above it. The band's own children need no z-index of their own beyond this,
   because the wrapper is at 0 and everything else is in flow above it. */
.dk-feat {
  position: relative;
  z-index: 1;
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1.6rem, 1.8vw, 1.2rem);
}

@media (width >= 58rem) {
  .dk-feat { grid-template-columns: minmax(0, 1.05fr) minmax(0, 1fr); align-items: stretch; }
}

.dk-feat__block {
  position: relative;
  transition: transform 260ms cubic-bezier(.22,.61,.36,1);
}


/* ⚠ This container is a reveal target and the reveal owns `transform` on it, so
   a plain `:hover` at (0,2,0) would lose to `.dk-reveal[data-in]` and the lift
   would silently never apply. → HANDOFF §6f-vi */


.dk-feat__link {
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-violet);
  display: flex;
  flex-direction: column;
  height: 100%;
  color: #F4F3EF;
  text-decoration: none;
}

.dk-feat__link:focus-visible { outline: 2px solid #F4F3EF; outline-offset: -6px; }

.dk-feat__img {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 16 / 10;
  object-fit: cover;
}

.dk-feat__chip {
  display: inline-block;
  align-self: flex-start;
  margin: clamp(1rem, 2.2vw, 1.4rem) clamp(1rem, 2.2vw, 1.4rem) 0.6rem;
  padding: 0.3rem 0.75rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-feat__title {
  display: block;
  margin: 0 clamp(1rem, 2.2vw, 1.4rem) 0.4rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 88, "wght" 800;
  font-size: clamp(1.5rem, 3vw, 2.3rem);
  line-height: 1;
  letter-spacing: -0.024em;
}

.dk-feat__byline {
  display: block;
  margin: 0 clamp(1rem, 2.2vw, 1.4rem) clamp(1rem, 2.2vw, 1.4rem);
  font-family: "Newsreader", Georgia, serif;
  font-style: italic;
  font-size: 0.9375rem;
  font-weight: 600;
  opacity: 0.85;
}

/* ⚠⚠ ONE `gap`, AND IT USED TO BE TWO. Round 12 added `gap: 1.5rem` at the top of this block and
   left the original `gap: clamp(0.7rem, 1.6vw, 1rem)` four lines below it. Within one declaration
   block the LAST one wins, so the fix never applied and the list shipped on the clamp for two more
   rounds. Measured on the shipped page: the bookmark protrudes 9px above its own card, so the
   clearance to the card above was 5.3px at 895px wide and 2.2px at 600px and below — touching, to
   the eye, which is exactly what the client reported.
   1.5rem gives 24px of gap and therefore about 15px of real clearance at every width.
   A gap stops being spacing the moment something sticks out into it, and a duplicate declaration
   is now a crosscheck failure so this cannot recur. → HANDOFF §6h-xvii */
.dk-feat__list {
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  gap: 1.5rem;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* Content group and control group, each its own track with a real gap, so the
   copy can never run under the bookmark. → kit 03 §6a */
/* ⚠ ONE column now, and the corner is reserved with PADDING instead of a track. The bookmark used
   to be laid out as its own grid track, which is what §6f-vi's grouping fix demanded while the
   control sat in the flow. Now it is at the corner, so the track would collapse to nothing and the
   title would run under the notch — the exact fault that rule exists to prevent. The right-hand
   padding carries the same guarantee, and it has to clear the button plus its halo, not just the
   button. Asserted by the bookmark-over-text check in tools/fit.mjs. */
/* ⚠ The wrapper no longer paints anything: the background, the radius AND the padding all moved to
   the link, because the link is what the notch mask is applied to and the mask has to cut the
   painted surface. The wrapper keeps only its position and its hover transform. */
.dk-feat__row {
  position: relative;
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  align-items: center;
  transition: transform 220ms cubic-bezier(.22,.61,.36,1);
}

/* ⚠ Reveal target, so BOTH halves of the pattern are needed: the hover must out-specify
   `.dk-reveal[data-in]` at (0,3,0), AND the fast transition must hang on [data-settled],
   or the lift inherits the reveal's 620ms entrance timing and a 260ms micro-interaction
   crawls. Measured mid-flight at -4.77 of -5 a full 400ms after the pointer arrived.
   → HANDOFF §6f-vi */



.dk-feat__rowlink {
  display: grid;
  grid-template-columns: 5.5rem minmax(0, 1fr);
  gap: 0.9rem;
  align-items: center;
  min-width: 0;
  color: var(--dk-ink);
  text-decoration: none;
}

.dk-feat__rowlink:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 3px; }

.dk-feat__rowimg {
  width: 100%;
  height: auto;
  aspect-ratio: 1 / 1;
  object-fit: cover;
  border-radius: calc(var(--dk-r) * 0.5);
  background: var(--dk-line);
}

.dk-feat__rowbody { min-width: 0; }

.dk-feat__rowchip {
  display: inline-block;
  margin-bottom: 0.5rem;
  padding: 0.16rem 0.55rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.625rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-feat__rowtitle {
  display: block;
  margin-bottom: 0.25rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 92, "wght" 700;
  font-size: 1.0625rem;
  line-height: 1.16;
  letter-spacing: -0.014em;
}

.dk-feat__rowmeta {
  display: block;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-muted);
}

/* ============================================================== BAND: RAIL */

.dk-rail {
  display: grid;
  grid-auto-flow: column;
  grid-auto-columns: minmax(15rem, 19rem);
  /* ⚠ 1.5rem, not a clamp with a 12.8px floor. Same protrusion as the mosaic: the bookmark
     reaches about 9px past its own card's right edge, so the old floor left 3.8px to the next
     tile. → HANDOFF §6h-xvii */
  gap: 1.5rem;
  align-items: stretch;
  margin: 0;
  /* ⚠ Room at the TOP as well. This is a horizontal scroller, and a box that scrolls on one axis
     clips the other too, so the bookmark protruding above each card's corner is cut off without
     it. Nothing about the rule that clips it mentions the axis you can see. */
  padding: 1.5rem 0 0.6rem;
  list-style: none;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x proximity;
  scrollbar-width: none;
  -ms-overflow-style: none;
}

.dk-rail::-webkit-scrollbar { display: none; }

.dk-rail:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 3px; }

@media (width >= 78rem) {
  .dk-rail {
    grid-auto-flow: row;
    grid-template-columns: repeat(5, 1fr);
    grid-auto-columns: auto;
    overflow-x: visible;
    scroll-snap-type: none;
  }
}

.dk-rail__cell { scroll-snap-align: start; min-width: 0; }

.dk-tile {
  position: relative;
  height: 100%;
  transition: transform 260ms cubic-bezier(.22,.61,.36,1);
}



/* ⚠ THE BACKGROUND HAS TO REACH THE LINK, because the link is what the notch mask cuts. Left on
   the wrapper it painted BEHIND the hole, so every tile's bite showed violet or lime instead of the
   page ground and the notch read as a coloured blob rather than as a gap.
   The colour travels by inherited custom property, because the modifier is on the wrapper and the
   painted element is its child: `.dk-tile--violet .dk-tile__link` is a descendant selector and the
   generator drops those silently. The text colour stays here — it inherits and paints no box.
   → kit 03 §6c */
.dk-tile--violet { --dk-tilebg: var(--dk-violet); color: #F4F3EF; }

.dk-tile--lime { --dk-tilebg: var(--dk-lime); color: #16171A; }

.dk-tile--pink { --dk-tilebg: var(--dk-pink); color: #16171A; }

.dk-tile--quiet { --dk-tilebg: var(--dk-quiet); color: var(--dk-ink); }

.dk-tile__link {
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-tilebg);
  display: flex;
  flex-direction: column;
  height: 100%;
  color: inherit;
  text-decoration: none;
}

.dk-tile__link:focus-visible { outline: 2px solid currentColor; outline-offset: -6px; }

.dk-tile__img {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 4 / 3;
  object-fit: cover;
}

.dk-tile__foot {
  display: flex;
  flex-direction: column;
  flex: 1 1 auto;
  padding: clamp(0.85rem, 1.8vw, 1.15rem);
}

/* ⚠ A SOLID GROUND, at the client's request, and it is the better call. Outlined and transparent,
   this pill inherited the tile's colour and had to read against whatever the tile's foot happened to
   be — four different colours, one of them a photograph's edge. A pill with its own ground reads the
   same on all four and matches the pills in every other band. */
.dk-tile__chip {
  display: inline-block;
  align-self: flex-start;
  margin-bottom: 0.5rem;
  padding: 0.2rem 0.6rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.625rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-tile__title {
  display: block;
  margin-bottom: 0.6rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 90, "wght" 700;
  font-size: 1.15rem;
  line-height: 1.1;
  letter-spacing: -0.018em;
}

.dk-tile__meta {
  display: block;
  margin-top: auto;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  /* ⚠ OPACITY IS A CONTRAST CHANGE. Muting text with opacity composites it toward the
     ground, so the real ratio is whatever the mix measures, not what the solid colour
     measured. These labels sit on violet, lime AND pink, so the floor is set by the
     WORST of the three: pink needs >= 0.81 to clear 4.5:1, violet >= 0.77, lime >= 0.61.
     0.85 for all of them, with headroom. Measured at 0.72 this was 3.88:1 on pink. */
  opacity: 0.85;
}

/* ============================================================ BAND: MOSAIC */

.dk-mosaic {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1.6rem, 1.8vw, 1.2rem);
}

@media (width >= 58rem) {
  .dk-mosaic { grid-template-columns: minmax(0, 1fr) minmax(0, 1.15fr); align-items: stretch; }
}

.dk-mosaic__tall {
  position: relative;
  transition: transform 260ms cubic-bezier(.22,.61,.36,1);
}

/* ⚠ Reveal target, so BOTH halves of the pattern are needed: the hover must out-specify
   `.dk-reveal[data-in]` at (0,3,0), AND the fast transition must hang on [data-settled],
   or the lift inherits the reveal's 620ms entrance timing and a 260ms micro-interaction
   crawls. Measured mid-flight at -4.77 of -5 a full 400ms after the pointer arrived.
   → HANDOFF §6f-vi */



.dk-mosaic__talllink {
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-quiet);
  display: flex;
  flex-direction: column;
  height: 100%;
  color: var(--dk-ink);
  text-decoration: none;
}

.dk-mosaic__talllink:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: -6px; }

.dk-mosaic__tallimg {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 4 / 3;
  object-fit: cover;
}

.dk-mosaic__tallchip {
  display: inline-block;
  align-self: flex-start;
  margin: clamp(0.9rem, 2vw, 1.3rem) clamp(0.9rem, 2vw, 1.3rem) 0.5rem;
  padding: 0.24rem 0.7rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-mosaic__talltitle {
  display: block;
  margin: 0 clamp(0.9rem, 2vw, 1.3rem) 0.4rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 90, "wght" 700;
  font-size: clamp(1.3rem, 2.4vw, 1.8rem);
  line-height: 1.05;
  letter-spacing: -0.02em;
}

.dk-mosaic__tallstand {
  display: -webkit-box;
  margin: 0 clamp(0.9rem, 2vw, 1.3rem) 0.6rem;
  font-size: 0.9375rem;
  line-height: 1.5;
  color: var(--dk-muted);
  -webkit-line-clamp: 3;
  -webkit-box-orient: vertical;
  overflow: hidden;
}

.dk-mosaic__tallmeta {
  display: block;
  margin: auto clamp(0.9rem, 2vw, 1.3rem) clamp(0.9rem, 2vw, 1.3rem);
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-muted);
}

.dk-mosaic__list {
  display: grid;
  grid-template-columns: 1fr;
  /* ⚠ BOTH AXES, ONE VALUE. The bookmark sits in the notch at each card's top-right and is
     translated out, so it protrudes about 9px UP and 9px RIGHT of its own card. Any gap below that
     plus a real margin leaves the control looking like it is touching its neighbour: measured on
     the shipped page, 3.8px vertically in one column and 3.8px horizontally in two.
     → HANDOFF §6h-xvii */
  gap: 1.5rem;
  margin: 0;
  padding: 0;
  list-style: none;
}

@media (width >= 34rem) { .dk-mosaic__list { grid-template-columns: repeat(2, 1fr); } }

.dk-mosaic__cell {
  position: relative;
  transition: transform 240ms cubic-bezier(.22,.61,.36,1);
}

/* ⚠ Reveal target, so BOTH halves of the pattern are needed: the hover must out-specify
   `.dk-reveal[data-in]` at (0,3,0), AND the fast transition must hang on [data-settled],
   or the lift inherits the reveal's 620ms entrance timing and a 260ms micro-interaction
   crawls. Measured mid-flight at -4.77 of -5 a full 400ms after the pointer arrived.
   → HANDOFF §6f-vi */



.dk-mosaic__link {
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-quiet);
  display: flex;
  flex-direction: column;
  height: 100%;
  color: var(--dk-ink);
  text-decoration: none;
}

.dk-mosaic__link:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: -5px; }

.dk-mosaic__img {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: cover;
}

.dk-mosaic__chip {
  display: inline-block;
  align-self: flex-start;
  margin: 0.8rem 0.8rem 0.4rem;
  padding: 0.18rem 0.6rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.625rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-mosaic__title {
  display: block;
  margin: 0 0.8rem 0.4rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 92, "wght" 700;
  font-size: 1.0625rem;
  line-height: 1.14;
  letter-spacing: -0.014em;
}

.dk-mosaic__meta {
  display: block;
  margin: auto 0.8rem 0.8rem;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-muted);
}

/* ========================================================== BAND: AND ALSO
   The one full-width lime block, and the loudest moment on the page. */

.dk-also {
  position: relative;
  max-width: 86rem;
  margin: clamp(1rem, 2.4vw, 1.6rem) auto;
  padding: clamp(1.4rem, 3.4vw, 2.4rem) clamp(1.1rem, 3vw, 2rem) clamp(1.6rem, 3.4vw, 2.4rem);
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-band);
  color: var(--dk-bandink);
}

.dk-also__blob {
  position: absolute;
  bottom: -30%;
  left: -8%;
  z-index: 0;
  width: clamp(14rem, 32vw, 26rem);
  aspect-ratio: 1 / 1;
  border-radius: 58% 42% 50% 50% / 44% 56% 44% 56%;
  background: var(--dk-bandink);
  opacity: 0.06;
  pointer-events: none;
}

.dk-also__grid {
  position: relative;
  z-index: 1;
  display: grid;
  grid-template-columns: 1fr;
  /* ⚠ THE ROW GAP IS SPLIT FROM THE COLUMN GAP, and it is not a tidy-up. The bookmark sits in the
     notch at each card's top-right and is translated out, so it protrudes about 9px ABOVE its own
     card. Every gap below that plus a real margin leaves the control looking like it is touching
     the card above. Measured on the shipped page, worst clearance per group: 5.4px
     The column gap keeps its clamp: the same check measures the horizontal case separately and
     reports it clear at every width, and the horizontal rhythm has been through fourteen review
     rounds. Written as two longhands rather than `gap` plus a `row-gap` override, so it can never
     be mistaken for the duplicate-declaration bug that caused this. → HANDOFF §6h-xvii */
  column-gap: clamp(0.9rem, 2vw, 1.4rem);
  row-gap: 1.5rem;
}

@media (width >= 58rem) {
  .dk-also__grid { grid-template-columns: minmax(0, 1.05fr) minmax(0, 1fr); align-items: stretch; }
}

.dk-also__feature {
  position: relative;
  transition: transform 260ms cubic-bezier(.22,.61,.36,1);
}

/* ⚠ Reveal target, so BOTH halves of the pattern are needed: the hover must out-specify
   `.dk-reveal[data-in]` at (0,3,0), AND the fast transition must hang on [data-settled],
   or the lift inherits the reveal's 620ms entrance timing and a 260ms micro-interaction
   crawls. Measured mid-flight at -4.77 of -5 a full 400ms after the pointer arrived.
   → HANDOFF §6f-vi */



.dk-also__featurelink {
  border-radius: calc(var(--dk-r) * 0.8);
  overflow: hidden;
  background: var(--dk-bandcard);
  display: flex;
  flex-direction: column;
  height: 100%;
  color: var(--dk-bandink);
  text-decoration: none;
}

.dk-also__featurelink:focus-visible { outline: 2px solid var(--dk-bandink); outline-offset: -6px; }

/* ⚠⚠ THE FEATURE'S HEIGHT IS WHAT SET THE GAPS IN THE LIST BESIDE IT, and that is why this
   ratio is a layout value rather than a crop preference. The list is
   `justify-content: space-between` inside a column stretched to the feature's height, so every
   pixel the feature is taller than the four rows need becomes free space DISTRIBUTED INTO THE
   GAPS. Measured at 1440 on 16/10: feature 612px, rows 435px, so 177px of slack came out as three
   59px gaps, which is what the client reported. Below about 1200 it collapsed to the row-gap
   floor and looked right, which is why it read as a wide-screen problem.
   15/7 makes the two columns near enough equal at 1440, so the slack is spent before it reaches
   the gaps. Shortening the feature was the client's own suggestion and it is the better lever:
   capping the gap would have left a hole under the feature instead. → HANDOFF §6h-xix */
.dk-also__featureimg {
  display: block;
  width: 100%;
  /* ⚠ `height: auto` is required alongside `aspect-ratio`, or the width and height ATTRIBUTES
     make both dimensions definite and the ratio is silently ignored. → §3.1 */
  height: auto;
  aspect-ratio: 15 / 7;
  object-fit: cover;
}

.dk-also__featurechip {
  display: inline-block;
  align-self: flex-start;
  margin: 0.9rem 0.9rem 0.5rem;
  padding: 0.24rem 0.7rem;
  border-radius: 999px;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

.dk-also__featuretitle {
  display: block;
  margin: 0 0.9rem 0.4rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 90, "wght" 700;
  font-size: clamp(1.3rem, 2.4vw, 1.8rem);
  line-height: 1.05;
  letter-spacing: -0.02em;
}

.dk-also__featurestand {
  display: -webkit-box;
  margin: 0 0.9rem 0.6rem;
  font-size: 0.9375rem;
  line-height: 1.5;
  color: var(--dk-bandmuted);
  -webkit-line-clamp: 3;
  -webkit-box-orient: vertical;
  overflow: hidden;
}

.dk-also__featuremeta {
  display: block;
  margin: auto 0.9rem 0.9rem;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-bandmuted);
}

.dk-also__list {
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  /* ⚠ THE ROW GAP IS SPLIT FROM THE COLUMN GAP, and it is not a tidy-up. The bookmark sits in the
     notch at each card's top-right and is translated out, so it protrudes about 9px ABOVE its own
     card. Every gap below that plus a real margin leaves the control looking like it is touching
     the card above. Measured on the shipped page, worst clearance per group: 0.6px, the tightest on the page
     The column gap keeps its clamp: the same check measures the horizontal case separately and
     reports it clear at every width, and the horizontal rhythm has been through fourteen review
     rounds. Written as two longhands rather than `gap` plus a `row-gap` override, so it can never
     be mistaken for the duplicate-declaration bug that caused this. → HANDOFF §6h-xvii */
  column-gap: clamp(0.6rem, 1.4vw, 0.9rem);
  row-gap: 1.5rem;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* ⚠ The hover BACKGROUND has to reach the link now, and `.dk-also__row:hover .dk-also__rowlink`
   is a descendant selector, which the generator drops silently. A custom property set on the row
   and read on the link does it with two flat selectors, because custom properties inherit.
   → kit 03 §6c */
.dk-also__row {
  --dk-rowbg: color-mix(in srgb, var(--dk-bandcard) 55%, transparent);
  position: relative;
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  align-items: center;
  transition: transform 220ms cubic-bezier(.22,.61,.36,1);
}

/* ⚠ Reveal target, so BOTH halves of the pattern are needed: the hover must out-specify
   `.dk-reveal[data-in]` at (0,3,0), AND the fast transition must hang on [data-settled],
   or the lift inherits the reveal's 620ms entrance timing and a 260ms micro-interaction
   crawls. Measured mid-flight at -4.77 of -5 a full 400ms after the pointer arrived.
   → HANDOFF §6f-vi */

.dk-also__row[data-in="true"]:hover { --dk-rowbg: var(--dk-bandcard); }

.dk-also__rowlink {
  display: grid;
  grid-template-columns: 4rem minmax(0, 1fr);
  gap: 0.8rem;
  align-items: center;
  min-width: 0;
  color: var(--dk-bandink);
  text-decoration: none;
}

.dk-also__rowlink:focus-visible { outline: 2px solid var(--dk-bandink); outline-offset: 3px; }

.dk-also__rowimg {
  width: 100%;
  height: auto;
  aspect-ratio: 1 / 1;
  object-fit: cover;
  border-radius: 50%;
  background: color-mix(in srgb, var(--dk-bandink) 14%, var(--dk-bandcard));
}

.dk-also__rowbody { min-width: 0; }

/* ⚠ NOT a pill: this one is a bare caps label in a dense row, with no padding and no radius, so the
   shared neutral ground would draw a tight rectangle behind the text rather than a pill. It declares
   its own transparent ground and colour, and being later in the file it wins over the shared rule.
   Its hover stays the underline. Flagged to the client rather than quietly turned into a pill, which
   would have changed the And Also rows' density. */
.dk-also__rowchip {
  background: none;
  display: inline-block;
  margin-bottom: 0.22rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.625rem;
  font-weight: 800;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--dk-bandaccent);
}

.dk-also__rowtitle {
  display: block;
  margin-bottom: 0.2rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 92, "wght" 700;
  font-size: 1.0625rem;
  line-height: 1.16;
  letter-spacing: -0.014em;
}

.dk-also__rowmeta {
  display: block;
  line-height: 1.9;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-bandmuted);
}

/* ====================================================================== ADS
   Labelled, unnumbered, never animated.
   ⚠ CORRECTED 2026-08-19: the advertisers are NOT fictional and there is no footer disclosure.
   Both ads' copy was supplied by the client, who has the relationship with the advertisers, so
   the sample presents them as a real site would. The earlier "fictional and disclosed" note here
   and the matching footer line were both inaccurate and are gone.
   What still holds: the label, no numbering, no motion, and no fabricated product shots — both ad
   images are generic stock, which the media ledger records deliberately. → HANDOFF §6c */

.dk-ad {
  max-width: 86rem;
  margin-inline: auto;
  padding: clamp(0.8rem, 2vw, 1.2rem) clamp(1rem, 3vw, 2rem);
}

.dk-ad--leader { padding-block: clamp(0.6rem, 1.6vw, 1rem); }

.dk-ad__label {
  margin: 0 0 0.5rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.625rem;
  font-weight: 800;
  letter-spacing: 0.24em;
  text-transform: uppercase;
  color: var(--dk-muted);
}

.dk-ad__unit {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1rem, 2.4vw, 1.8rem);
  align-items: center;
  padding: clamp(0.9rem, 2vw, 1.3rem);
  border: 1px solid var(--dk-line);
  border-radius: var(--dk-r);
  background: var(--dk-quiet);
}

@media (width >= 46rem) {
  .dk-ad__unit { grid-template-columns: minmax(0, 1fr) minmax(0, 1.3fr); }
}

@media (width >= 46rem) {
  .dk-ad__unit--leader { grid-template-columns: minmax(0, 0.6fr) minmax(0, 1.6fr) auto; }
}

.dk-ad__img {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: cover;
  border-radius: calc(var(--dk-r) * 0.6);
  background: var(--dk-line);
}

.dk-ad__img--leader { aspect-ratio: 16 / 9; }

.dk-ad__copy { min-width: 0; }

.dk-ad__kicker {
  margin: 0 0 0.35rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--dk-accenttext);
}

.dk-ad__head {
  margin: 0 0 0.45rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 90, "wght" 700;
  font-size: clamp(1.3rem, 2.4vw, 1.9rem);
  line-height: 1.08;
  letter-spacing: -0.02em;
}

.dk-ad__head--leader { font-size: clamp(1.2rem, 1.9vw, 1.6rem); margin-bottom: 0.3rem; }

.dk-ad__sub {
  margin: 0 0 0.8rem;
  font-size: 0.9375rem;
  line-height: 1.55;
  color: var(--dk-muted);
}

.dk-ad__sub--leader { margin-bottom: 0; font-size: 0.875rem; }

.dk-ad__cta { display: inline-block; }

/* ================================================================ SUBSCRIBE */

.dk-sub {
  position: relative;
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1.2rem, 3vw, 2.2rem);
  max-width: 86rem;
  margin: clamp(1rem, 2.4vw, 1.6rem) auto;
  padding: clamp(1.6rem, 4vw, 3rem) clamp(1.1rem, 3vw, 2.4rem);
  border-radius: var(--dk-r);
  overflow: hidden;
  background: var(--dk-violet);
  color: #F4F3EF;
}

@media (width >= 58rem) {
  .dk-sub { grid-template-columns: minmax(0, 1.25fr) minmax(0, 1fr); align-items: center; }
}

/* The drawn squiggle, the second accenting shape. Decorative and never animated. */
.dk-sub__squiggle {
  position: absolute;
  top: 6%;
  right: 2%;
  z-index: 0;
  width: clamp(9rem, 18vw, 15rem);
  color: var(--dk-lime);
  opacity: 0.9;
  pointer-events: none;
}

.dk-sub__body { position: relative; z-index: 1; min-width: 0; }

.dk-sub__title {
  margin: 0 0 0.5rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 84, "wght" 800;
  font-size: clamp(1.8rem, 4.4vw, 3rem);
  line-height: 0.98;
  letter-spacing: -0.028em;
  text-transform: uppercase;
}

.dk-sub__copy {
  margin: 0 0 1.2rem;
  font-size: 1rem;
  line-height: 1.55;
  opacity: 0.88;
}

.dk-sub__form { margin: 0; }

.dk-sub__label {
  display: block;
  margin-bottom: 0.4rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 800;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  opacity: 0.82;
}

.dk-sub__row { display: flex; flex-wrap: wrap; gap: 0.6rem; }

.dk-sub__input {
  flex: 1 1 14rem;
  min-width: 0;
  padding: 0.8rem 1rem;
  background: #F4F3EF;
  border: 1px solid #F4F3EF;
  border-radius: 999px;
  color: #16171A;
  font-family: "Newsreader", Georgia, serif;
  /* 16px floor, or iOS zooms the page on focus. */
  font-size: max(1rem, 0.95rem);
}

.dk-sub__input:focus-visible { outline: 2px solid var(--dk-lime); outline-offset: 2px; }

.dk-sub__btn {
  flex: none;
  padding: 0.8rem 1.4rem;
  background: var(--dk-lime);
  border: 1px solid var(--dk-lime);
  border-radius: 999px;
  color: #16171A;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.9375rem;
  font-weight: 700;
  cursor: pointer;
  transition: background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1);
}

.dk-sub__btn:hover { background: #16171A; border-color: #16171A; color: #F4F3EF; }

.dk-sub__btn:focus-visible { outline: 2px solid #F4F3EF; outline-offset: 3px; }

.dk-sub__small { margin: 0.8rem 0 0; font-size: 0.875rem; opacity: 0.82; }

/* ⚠ A THREE-TRACK GRID THAT HELD NUMERALS WILL NOT HOLD WORDS. "Evangelical" is
   eleven characters and cannot break, so where "409" sat comfortably in a third of a
   narrow column the word simply overflowed its box. Measured, not estimated: one
   column below the breakpoint, three above, and the display size solved so the
   longest lead fits the narrowest track it is ever given. */
.dk-sub__facts {
  position: relative;
  z-index: 1;
  display: grid;
  grid-template-columns: 1fr;
  gap: 0.6rem;
  margin: 0;
  padding: 0;
  list-style: none;
}
@media (width >= 30rem) {
  .dk-sub__facts { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}

.dk-sub__fact {
  padding: clamp(0.9rem, 2vw, 1.3rem);
  border-radius: calc(var(--dk-r) * 0.7);
  background: rgba(244, 243, 239, 0.12);
}

  /* The lead is a WORD now, not a numeral, so the display scale comes down and the
     grid holds three qualities rather than four counts. → HANDOFF §8.33 */
.dk-sub__factlead {
  text-wrap: balance;
  display: block;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 82, "wght" 800;
  font-size: clamp(1rem, 1.6vw, 1.3rem);
  line-height: 1.05;
  letter-spacing: -0.024em;
}

.dk-sub__factlabel {
  display: block;
  margin-top: 0.25rem;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 700;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  opacity: 0.82;
}

/* =================================================================== FOOTER */

.dkc-foot {
  max-width: 86rem;
  margin: 0 auto clamp(1rem, 2.4vw, 1.6rem);
  padding: clamp(1.6rem, 3.4vw, 2.6rem) clamp(1.1rem, 3vw, 2.4rem) clamp(1.1rem, 2.4vw, 1.6rem);
  border-radius: var(--dk-r);
  background: var(--dk-quiet);
}

.dkc-foot__top {
  display: grid;
  grid-template-columns: 1fr;
  gap: clamp(1.2rem, 3vw, 2.4rem);
  margin-bottom: clamp(1.2rem, 3vw, 2rem);
}

@media (width >= 52rem) {
  .dkc-foot__top { grid-template-columns: minmax(0, 1.2fr) minmax(0, 1fr) minmax(0, 1fr); }
}

.dkc-foot__brand { min-width: 0; }

.dkc-foot__word {
  margin: 0;
  font-family: "Archivo", system-ui, sans-serif;
  font-variation-settings: "wdth" 80, "wght" 800;
  font-size: clamp(1.4rem, 3vw, 2rem);
  line-height: 1;
  letter-spacing: -0.024em;
  text-transform: uppercase;
}

.dkc-foot__tag {
  margin: 0.6rem 0 0;
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.6875rem;
  font-weight: 700;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--dk-accenttext);
}

.dkc-foot__addr {
  font-style: normal;
  font-size: 0.9375rem;
  line-height: 1.7;
  color: var(--dk-muted);
}

.dkc-foot__mail {
  color: var(--dk-ink);
  text-decoration: none;
  border-bottom: 1px solid var(--dk-border);
  transition: color 180ms cubic-bezier(.22,.61,.36,1), border-color 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-foot__mail:hover { color: var(--dk-accenttext); border-color: var(--dk-accenttext); }

.dkc-foot__mail:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

.dkc-foot__nav { min-width: 0; }

.dkc-foot__list { margin: 0; padding: 0; list-style: none; columns: 2; column-gap: 1.2rem; }

.dkc-foot__item { margin: 0; break-inside: avoid; }

.dkc-foot__link {
  display: block;
  padding: 0.24rem 0;
  color: var(--dk-muted);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.875rem;
  text-decoration: none;
  transition: color 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-foot__link:hover { color: var(--dk-ink); }

.dkc-foot__link:focus-visible { outline: 2px solid var(--dk-accenttext); outline-offset: 2px; }

@media (pointer: coarse) { .dkc-foot__link { min-height: 44px; display: flex; align-items: center; } }

.dkc-foot__legal {
  margin: 0;
  padding-top: clamp(0.9rem, 2vw, 1.2rem);
  border-top: 1px solid var(--dk-line);
  font-family: "Archivo", system-ui, sans-serif;
  font-size: 0.75rem;
  color: var(--dk-muted);
}

/* =============================================================== BACK TO TOP */

.dkc-top {
  position: fixed;
  right: clamp(0.8rem, 2vw, 1.6rem);
  bottom: clamp(0.8rem, 2vw, 1.6rem);
  z-index: 45;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 48px;
  height: 48px;
  padding: 0;
  font-size: 1.15rem;
  background: var(--dk-violet);
  border: 1px solid var(--dk-violet);
  border-radius: 50%;
  color: #F4F3EF;
  cursor: pointer;
  transition: transform 220ms cubic-bezier(.22,.61,.36,1), background-color 200ms cubic-bezier(.22,.61,.36,1), color 200ms cubic-bezier(.22,.61,.36,1);
}

.dkc-top[hidden] { display: none; }

.dkc-top:hover { background: var(--dk-lime); border-color: var(--dk-lime); color: #16171A; transform: translateY(-4px); }

.dkc-top:focus-visible { outline: 2px solid var(--dk-ink); outline-offset: 3px; }

/* ================================================================== REVEALS
   The animating class is added from JS, so no JS means no class, no hidden
   state, and the page is simply visible. */

.dk-reveal {
  opacity: 0;
  transform: translateY(18px);
  transition: opacity 620ms cubic-bezier(.22,.61,.36,1), transform 620ms cubic-bezier(.22,.61,.36,1);
}

.dk-reveal[data-in="true"] { opacity: 1; transform: none; }

/* Retire the stagger, or every later hover lags by its entrance delay forever.
   The retiring selector must match or beat the specificity it retires. */
.dk-reveal[data-in="true"][data-settled="true"] { transition-delay: 0s !important; }

/* ========================================================== REDUCED MOTION */

@media (prefers-reduced-motion: reduce) {
  .dk-reveal,
  .dk-reveal[data-in="true"] {
    opacity: 1;
    transform: none;
    transition: none !important;
    transition-delay: 0s !important;
  }
}

@media (prefers-reduced-motion: reduce) {
  .dk-body,
  .dk-skip,
  .dkc-nav,
  .dkc-nav__bar,
  .dkc-nav__link,
  .dkc-nav__icon,
  .dkc-nav__toggle,
  .dkc-theme,
  .dkc-theme__sun,
  .dkc-theme__moon,
  .dkc-mega,
  .dkc-mega__inner,
  .dkc-mega__link,
  .dkc-mega__issuecover,
  .dkc-mega__issuelink,
  .dkc-mega__aboutlink,
  .dk-btn,
  .dk-btn__badge,
  .dk-btn__arrow,
  .dk-bm,
  .dk-round,
  .dk-deck__card,
  .dk-deck__text,
  .dk-deck__meta,
  .dk-deck__arrow,
  .dk-feat__block,
  .dk-feat__row,
  .dk-tile,
  .dk-mosaic__tall,
  .dk-mosaic__cell,
  .dk-also__feature,
  .dk-also__row,
  .dk-sub__btn,
  .dkc-top,
  .dkc-foot__link,
  .dkc-foot__mail {
    transition: none !important;
  }
}

/* The transform is what the preference is about. A colour still responding is
   correct feedback, and with transitions killed it is instant. */
@media (prefers-reduced-motion: reduce) {
  .dkc-mega__issuecover:hover,
  .dk-deck__arrow--prev:hover,
  .dk-deck__arrow--next:hover,
  .dkc-top:hover {
    transform: none;
  }
}

/* ============================================================ SHORT SCREENS */

@media (max-height: 560px) { .dkc-top { display: none; } }

/* Short viewports also tighten the wordmark pill and the deck's clearance under it. Those
   rules live with the pill at the END of this file, because they have to beat the
   `width < 60rem` block that sets the full-size values. → THE WORDMARK GOES TO THE TOP */

/* ===================================================================== PRINT */

@media print {
  .dkc-nav,
  .dkc-mega,
  .dkc-top,
  .dk-ad,
  .dk-sub { display: none; }
}

@media print {
  .dk-body { background: #FFFFFF; color: #000000; font-size: 11pt; }
}

/* ==================================================== THE NAV ON SMALL SCREENS
   ⚠ Three clusters in a `1fr auto 1fr` bar need about 390px of content at the smallest
   size and had 353px to put it in, so the wordmark collided with the links either side.
   Rather than shrink everything past legibility, the bar sheds items in order of how
   badly they are needed, and nothing is lost: Subscribe and Sign in are in the menu.

   These rules sit at the END of the file on purpose. `@media (pointer: coarse)` above
   sets `display: flex` on the same links, and both at-rules hoist into that selector's
   own style entry in source order, so a hide written earlier would be undone on exactly
   the touch devices that need it. */

@media (width < 60rem) { .dkc-nav__link { display: none; } }

/* Below 60rem the bar carries icons only: sign in, the colour scheme and search sit
   together on the left, which balances the Sections button once it is a badge on its own. */
.dkc-nav__icon--signin { display: none; }

@media (width < 60rem) { .dkc-nav__icon--signin { display: inline-flex; } }

@media (width < 34rem) { .dkc-nav__togglelabel { display: none; } }

@media (width < 34rem) { .dkc-nav__toggle { padding: 0.3rem; } }

/* ================================================ THE HEADER, AT THE BOTTOM ON A PHONE
   Thumb reach. Below 60rem the bar leaves the top of the document and floats at the foot
   of the viewport, and the menu opens UPWARD out of it. The pill is opaque and carries a
   shadow, so content scrolling past it stays legible without a full-width backdrop. */

@media (width < 60rem) {
  .dkc-nav {
    position: fixed;
    top: auto;
    bottom: 0;
    left: 0;
    right: 0;
    background: transparent;
    padding-block: 0.6rem;
  }
}

@media (width < 60rem) { .dkc-nav[data-stuck="true"] { background: transparent; box-shadow: none; } }

/* The panel hangs off the TOP of the bar and wipes upward, which means the clip has to
   run the other way too: it closes onto the bottom edge instead of the top one. */
@media (width < 60rem) {
  .dkc-mega {
    top: auto;
    bottom: 100%;
    padding-block: 0 0.6rem;
    clip-path: inset(100% -60px 0 -60px);
  }
}

@media (width < 60rem) { .dkc-mega[data-open="true"] { clip-path: inset(-90px -60px 0 -60px); } }

@media (width < 60rem) { .dkc-mega__inner { transform: translateY(1.2rem); } }

@media (width < 60rem) { .dkc-mega__inner[data-open="true"] { transform: none; } }

/* Room at the foot of the document so the bar never covers the last thing on the page. */
@media (width < 60rem) { .dk-body { padding-bottom: 5.5rem; } }

/* And back-to-top clears the bar rather than sitting under it. */
@media (width < 60rem) { .dkc-top { bottom: 5rem; } }


/* ============================================ WHICH CONTROL OPENS THE RIGHT-HAND GROUP
   Source order is Subscribe, Sign in, sign-in icon, theme, search, Sections, and that is
   already the reading order at both sizes. The ONLY thing that changes between them is
   where the gap falls, so a single `margin-left: auto` moves search from one group to the
   other with no duplicated control and no reordering. */

.dkc-nav__icon--search { margin-left: auto; }

@media (width < 60rem) { .dkc-nav__icon--search { margin-left: 0; } }

@media (width < 60rem) { .dkc-nav__toggle { margin-left: auto; } }

/* ======================================================================= THE SCRIM
   The page is dimmed, blurred and taken out of reach while the menu is open. It sits
   inside the nav's stacking context, above the page and below both the bar and the panel. */

.dkc-scrim {
  position: fixed;
  inset: 0;
  z-index: 0;
  background: color-mix(in srgb, var(--dk-paper) 42%, transparent);
  -webkit-backdrop-filter: blur(7px);
  backdrop-filter: blur(7px);
  opacity: 0;
  transition: opacity 200ms cubic-bezier(.4,0,1,1);
}

.dkc-scrim[hidden] { display: none; }

.dkc-scrim[data-open="true"] { opacity: 1; transition: opacity 300ms cubic-bezier(.22,.61,.36,1); }

/* ============================================== THE MENU SCROLLS INSIDE ITS OWN BOX
   ⚠ The max-height and the scroll used to sit on the OUTER positioner, so the rounded
   panel scrolled bodily inside it and its curved top edge slid out of view, leaving a hard
   horizontal cut across the top of the menu. Moving both onto the panel makes the panel a
   fixed, rounded box whose CONTENT moves: the curve is always there. */

.dkc-mega { max-height: none; overflow: visible; }

.dkc-mega__scroll {
  max-height: min(72vh, 42rem);
  overflow-y: auto;
  overscroll-behavior: contain;
  /* ⚠ The standard `scrollbar-width` / `scrollbar-color` are deliberately NOT set here.
     Setting either switches Chrome onto its own thin-scrollbar rendering and it then
     ignores every `::-webkit-scrollbar` rule, so the platform's stepper arrows come back
     and cannot be removed. The webkit pseudo-elements below give full control instead:
     6px, violet thumb, no track, no arrows.
     Firefox does not implement them and falls back to its own scrollbar, which is already
     thin and arrowless, so nothing is lost there. */
  padding-right: 0.35rem;
  /* Content fades out as it reaches the panel's rounded ends rather than being cut by a
     hard horizontal line. The padding is what keeps the first and last blocks clear of the
     fade, so the two work as a pair: mask for the softening, padding for the clearance. */
  padding-block: 0.9rem;
  --dk-fade: 1.4rem;
  -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 var(--dk-fade), #000 calc(100% - var(--dk-fade)), transparent 100%);
  mask-image: linear-gradient(to bottom, transparent 0, #000 var(--dk-fade), #000 calc(100% - var(--dk-fade)), transparent 100%);
}

.dkc-mega__scroll::-webkit-scrollbar { width: 6px; }

.dkc-mega__scroll::-webkit-scrollbar-track { background: transparent; }

.dkc-mega__scroll::-webkit-scrollbar-thumb { background: var(--dk-accenttext); border-radius: 999px; }

/* No stepper arrows: they are the one part of a platform scrollbar that cannot be styled
   into the panel and they read as a foreign control stuck to its edge. */
.dkc-mega__scroll::-webkit-scrollbar-button { display: none; height: 0; width: 0; }

/* ============================================ THE WORDMARK GOES TO THE TOP ON A PHONE
   Branding belongs at the top of a page, and the controls belong under the thumb, so on
   small screens the two separate: the wordmark becomes its own floating pill at the top
   and the bar at the foot carries the controls only.
   This also retires the whole bar-centring problem. A wordmark sharing a row with three
   icons and a badge cannot be centred on the bar below about 412px, because the gap
   between the groups is not centred on the bar; once it leaves the row there is no gap to
   fit into. Measured: the old arrangement first collided at 400px.

   TWO fixed bars would eat the viewport, so the top one LEAVES on the way down and comes
   back on the way up. The bottom bar never moves: it is the one being reached for. */
/* ⚠ THE PILL'S HEIGHT IS DELIBERATELY ARITHMETIC, NOT A CLAMP. The deck below has to clear
   it, and a viewport-relative font size would make the height unpredictable, which is the
   same mistake as a decorative slab guessing the height of the content it covers (§6f-vi).
   Fixed rem values here, and the sum is written out beside the deck's own padding below, so
   the clearance can be checked by reading rather than by hoping.

     0.62rem  padding-block, twice   = 1.24rem
     1.2rem   wordmark, line-height 1
     0.16rem  gap
     0.5rem   tagline, line-height 1
     1px      border, twice
     -------------------------------
     3.10rem  = 49.6px, plus 2px border = 51.6px
     top: 0.7rem (11.2px) puts the pill's bottom edge at about 63px. */
@media (width < 60rem) {
  .dkc-nav__logo {
    position: fixed;
    top: 0.7rem;
    inset-inline: 0;
    z-index: 41;
    max-width: calc(100% - 1.6rem);
    padding: 0.62rem 1.35rem;
    border: 1px solid var(--dk-line);
    border-radius: 999px;
    background: color-mix(in srgb, var(--dk-quiet) 82%, transparent);
    -webkit-backdrop-filter: blur(16px) saturate(1.5);
    backdrop-filter: blur(16px) saturate(1.5);
    box-shadow: 0 8px 26px -16px var(--dk-shadow);
    transform: none;
    /* No transition here any more: the base rule carries the entrance timing and the away
       state carries the exit, and both apply at every width. One pair of timings for the
       wordmark rather than two that can drift apart. */
  }
}

/* Bigger than it was, because the client asked for the branding to carry more weight, and
   fixed rather than fluid so the pill has a knowable height. */
@media (width < 60rem) { .dkc-nav__wordmark { font-size: 1.2rem; } }

/* The device tracks the type: see the arithmetic on .dkc-nav__mark. */
@media (width < 60rem) { .dkc-nav__mark { width: 1.86rem; height: 1.86rem; } }

/* No `translateX(-50%)` any more: the centring is `margin-inline: auto`, so the away state
   only has to move it up. A smaller distance than the desktop one because the pill starts at
   the very top of the viewport rather than centred on a bar. */
@media (width < 60rem) {
  .dkc-nav__logo[data-hidden="true"] {
    transform: translateY(-180%);
    opacity: 0;
  }
}

/* ⚠ THE DECK WAS HUGGING THE PILL. The old value was 2.8rem, which is 44.8px against a
   pill whose bottom edge sat at about 45px, so the clearance was zero: the card's top
   corner started exactly where the pill ended, and with the pill now taller it would have
   started underneath it.
   63px of pill (the sum above) plus a real gap. The card may still pass beneath the pill
   while scrolling, which is correct for a floating overlay; what must never happen is the
   deck STARTING under it. Asserted per width by `tools/fit.mjs` rather than trusted. */
@media (width < 60rem) { .dk-deck { padding-top: 5.6rem; } }

/* ⚠⚠ A SHORT PHONE HAS TO GIVE THE HEIGHT BACK SOMEWHERE, AND THESE ARE THE DIALS.
   The taller pill and the real gap under it cost about 45px at the top of the document, and
   on a 640px or 667px viewport that comes straight off the bottom, where the control bar is
   waiting. Measured before and after against the pre-session page, at 375x640 the byline
   went from 13px clear to 3px behind the bar.

   Three dials, none of which touches anything taller than 700px:
     · the pill loses 0.17rem of padding and 0.15rem of type. Still visibly bigger than the
       one the client asked to grow, and about 8px shorter than the tall version.
     · the clearance under it comes down from 27px to a still-deliberate 15px.
     · the rows close up by 0.1rem each, which is 6px across the four of them.

   MUST come after the `width < 60rem` block above: same specificity, so source order is
   what decides, and written earlier in the file every one of them silently lost. That is
   the same ordering trap the small-screen nav rules carry a comment about. */
@media (max-height: 700px) and (width < 60rem) { .dkc-nav__logo { padding-block: 0.45rem; } }

@media (max-height: 700px) and (width < 60rem) { .dkc-nav__wordmark { font-size: 1.05rem; } }

/* MUST come after the `width < 60rem` device rule above: same specificity, so source order is
   what decides, and written earlier every one of these silently loses. */
@media (max-height: 700px) and (width < 60rem) { .dkc-nav__mark { width: 1.71rem; height: 1.71rem; } }

@media (max-height: 700px) and (width < 60rem) { .dk-deck { padding-top: 4.4rem; } }

/* ⚠ And a fourth dial for the NARROWEST phones, because the `vh` cap above does nothing for
   them. Below about 360px the card is bound by `100%` (the row's leftover width after the
   two arrows), not by the viewport height, so tightening the height cap cannot reach it:
   320x640 sat at 1px of clearance while 360x640 had 21px. A smaller cap at these widths
   only ever binds where the height one does not. Measured: 320x640 goes 1px to 31px. */
@media (prefers-reduced-motion: reduce) { .dkc-nav__logo { transition: none !important; } }

/* ================================================== THE BURGER BECOMES A CLOSE MARK
   The page is unreachable while the menu is open, so the control that opened it has to
   read as the way out. Three separate strokes, rotated about the icon's own centre by one
   inherited custom property; `aria-expanded` is already the state, so nothing new is
   tracked and no descendant selector is needed. */

.dkc-nav__toggle { --dk-x: 0; }

.dkc-nav__toggle[aria-expanded="true"] { --dk-x: 1; }

.dkc-burger__l {
  transform-box: view-box;
  transform-origin: 8px 8px;
  transition: transform 320ms cubic-bezier(.22,.61,.36,1), opacity 180ms cubic-bezier(.22,.61,.36,1);
}

.dkc-burger__l--top { transform: translateY(calc(var(--dk-x) * 3.5px)) rotate(calc(var(--dk-x) * 45deg)); }

.dkc-burger__l--mid { opacity: calc(1 - var(--dk-x)); transform: scaleX(calc(1 - var(--dk-x) * 0.7)); }

.dkc-burger__l--bot { transform: translateY(calc(var(--dk-x) * -3.5px)) rotate(calc(var(--dk-x) * -45deg)); }

@media (prefers-reduced-motion: reduce) { .dkc-burger__l { transition: none !important; } }
