/* GENERATED by tools/blog/build-blog.mjs. Do not edit.
   Colours are COPIED from src/styles/taskeen-ux.scss and src/styles/tokens.scss on every build,
   so the blog cannot drift from the product's palette. Layout below is the blog's own.

   LIGHT ONLY, matching the rest of the public site. The html.public-scope literals are emitted
   last because that is the order that makes them win in the application too. */

@import url('./fonts/manrope.css');

:root {
  color-scheme: light;

  /* the --ax-* primitives, light */
  --ax-blue: #1f71ff;
  --ax-blue-hover: #1560e8;
  --ax-blue-press: #0f4fc4;
  --ax-blue-ring: rgba(31, 113, 255, 0.16);
  --ax-blue-wash: rgba(31, 113, 255, 0.08);
  --ax-red: #ff3b30;
  --ax-red-ring: rgba(255, 59, 48, 0.16);
  --ax-green: #34c759;
  --ax-orange: #ff9500;
  --ax-surface: #FBFCFD;
  --ax-surface-sunken: #F7F8F9;
  --ax-surface-raised: #ffffff;
  --ax-fill: rgba(118, 118, 128, 0.08);
  --ax-fill-hover: rgba(118, 118, 128, 0.08);
  --ax-fill-press: rgba(118, 118, 128, 0.12);
  --ax-hairline: rgba(60, 60, 67, 0.16);
  --ax-hairline-strong: rgba(60, 60, 67, 0.30);
  --ax-hairline-soft: rgba(60, 60, 67, 0.08);
  --ax-label: rgba(0, 0, 0, 0.88);
  --ax-label-secondary: rgba(0, 0, 0, 0.72);
  --ax-label-tertiary: rgba(0, 0, 0, 0.56);
  --ax-label-quaternary: rgba(0, 0, 0, 0.56);
  --ax-r-xs: 6px;
  --ax-r-sm: 8px;
  --ax-r-field: 12px;
  --ax-r-md: 14px;
  --ax-r-panel: 16px;
  --ax-r-lg: 20px;
  --ax-r-dialog: 22px;
  --ax-r-card: 24px;
  --ax-r-pill: 980px;
  --ax-e1: 0 1px 2px rgba(0,0,0,.04), 0 1px 1px rgba(0,0,0,.03);
  --ax-e2: 0 2px 6px rgba(0,0,0,.05), 0 1px 2px rgba(0,0,0,.04);
  --ax-e3: 0 8px 24px rgba(0,0,0,.08), 0 2px 6px rgba(0,0,0,.05);
  --ax-e4: 0 16px 48px rgba(0,0,0,.12), 0 4px 12px rgba(0,0,0,.06);
  --ax-e5: 0 32px 84px rgba(0,0,0,.18), 0 8px 20px rgba(0,0,0,.08);
  --ax-ease: cubic-bezier(0.4, 0.0, 0.2, 1);
  --ax-ease-out: cubic-bezier(0.16, 1, 0.3, 1);
  --ax-spring: cubic-bezier(0.34, 1.56, 0.64, 1);
  --ax-t-fast: 140ms;
  --ax-t-base: 220ms;
  --ax-t-slow: 340ms;
  --ax-vibrancy: saturate(180%) blur(20px);
  --ax-vibrancy-heavy: saturate(180%) blur(30px);
  --ax-glass: rgba(255, 255, 255, 0.95);
  --ax-glass-chrome: rgba(231, 233, 238, 0.70);
  --ax-glass-chrome-e: 0 1px 10px rgba(0, 0, 0, .05);
  --ax-gloss-rim: rgba(255, 255, 255, .78);
  --ax-gloss-sheen: rgba(255, 255, 255, .16);
  --ax-vibrancy-gloss: saturate(200%) brightness(1.06) blur(30px);
  --ax-font: inherit !important;

  /* the --t-* aliases over them */
  --t-font-sans: "Manrope", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
  --t-font-display: "Manrope", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
  --t-font-mono: ui-monospace, "SF Mono", "Menlo", "Fira Code", monospace;
  --t-fs-2xs: 11px;
  --t-fs-xs: 12px;
  --t-fs-sm: 13px;
  --t-fs-base: 14px;
  --t-fs-md: 15px;
  --t-fs-lg: 17px;
  --t-fs-xl: 20px;
  --t-fs-2xl: 24px;
  --t-fs-3xl: 30px;
  --t-fs-4xl: 36px;
  --t-fs-5xl: 48px;
  --t-lh-tight: 1.2;
  --t-lh-snug: 1.35;
  --t-lh-normal: 1.5;
  --t-lh-relaxed: 1.65;
  --t-fw-regular: 400;
  --t-fw-medium: 500;
  --t-fw-semibold: 600;
  --t-fw-bold: 700;
  --t-tracking-tight: -0.01em;
  --t-tracking-normal: 0;
  --t-tracking-wide: 0.02em;
  --t-text: var(--ax-label,           rgba(0, 0, 0, 0.88));
  --t-text-2: var(--ax-label-secondary, rgba(0, 0, 0, 0.72));
  --t-text-3: var(--ax-label-tertiary,  rgba(0, 0, 0, 0.56));
  --t-text-muted: var(--ax-label-quaternary,rgba(0, 0, 0, 0.56));
  --t-on-brand: #ffffff;
  --t-text-inverse: #ffffff;
  --t-brand: #1d1d1f;
  --t-brand-hover: #424245;
  --t-brand-press: #000000;
  --t-brand-wash: rgba(0, 0, 0, 0.05);
  --t-brand-border: #1d1d1f;
  --t-brand-ring: var(--t-focus-ring);
  --t-focus: var(--ax-blue,      #1f71ff);
  --t-focus-ring: var(--ax-blue-ring, rgba(31, 113, 255, 0.16));
  --t-link: #1d4ed8;
  --t-secondary: var(--ax-label-secondary, rgba(60, 60, 67, 0.62));
  --t-secondary-wash: var(--ax-fill,            rgba(118, 118, 128, 0.08));
  --t-bg: #FFFFFF;
  --t-surface: var(--ax-surface);
  --t-surface-2: var(--ax-surface-raised);
  --t-surface-sunken: var(--ax-surface-sunken);
  --t-surface-overlay: var(--ax-glass, rgba(255, 255, 255, 0.72));
  --t-fill: var(--ax-fill,        rgba(118, 118, 128, 0.05));
  --t-fill-hover: var(--ax-fill-hover,  rgba(118, 118, 128, 0.08));
  --t-fill-press: var(--ax-fill-press,  rgba(118, 118, 128, 0.12));
  --t-row-hover: rgba(118, 118, 128, 0.045);
  --t-border: var(--ax-hairline,        rgba(60, 60, 67, 0.16));
  --t-border-strong: var(--ax-hairline-strong, rgba(60, 60, 67, 0.30));
  --t-border-soft: var(--ax-hairline-soft,   rgba(60, 60, 67, 0.08));
  --t-success: var(--ax-green);
  --t-success-bg: rgba(52, 199, 89, 0.10);
  --t-success-border: rgba(52, 199, 89, 0.28);
  --t-warning: var(--ax-orange);
  --t-warning-bg: rgba(255, 149, 0, 0.10);
  --t-warning-border: rgba(255, 149, 0, 0.28);
  --t-danger: var(--ax-red);
  --t-danger-bg: rgba(255, 59, 48, 0.10);
  --t-danger-border: rgba(255, 59, 48, 0.28);
  --t-danger-text: #b91c1c;
  --t-warning-text: #b45309;
  --t-success-text: #15803d;
  --t-purple-text: #6d28d9;
  --t-brand-text: #1d1d1f;
  --t-r-xs: var(--ax-r-xs);
  --t-r-sm: var(--ax-r-sm);
  --t-r-field: var(--ax-r-field);
  --t-r-md: var(--ax-r-md);
  --t-r-panel: var(--ax-r-panel);
  --t-r-lg: var(--ax-r-lg);
  --t-r-card: var(--ax-r-card);
  --t-r-pill: var(--ax-r-pill);
  --t-e1: var(--ax-e1, 0 1px 2px rgba(0,0,0,.04));
  --t-e2: var(--ax-e2, 0 2px 6px rgba(0,0,0,.05));
  --t-e3: var(--ax-e3, 0 8px 24px rgba(0,0,0,.08));
  --t-e4: var(--ax-e4, 0 16px 48px rgba(0,0,0,.12));
  --t-e5: var(--ax-e5, 0 32px 84px rgba(0,0,0,.18));
  --t-ease: var(--ax-ease,     cubic-bezier(0.4, 0, 0.2, 1));
  --t-ease-out: var(--ax-ease-out, cubic-bezier(0.16, 1, 0.3, 1));
  --t-spring: var(--ax-spring,   cubic-bezier(0.34, 1.56, 0.64, 1));
  --t-t-fast: var(--ax-t-fast);
  --t-t-base: var(--ax-t-base);
  --t-t-slow: var(--ax-t-slow);
  --t-space-1: 4px;
  --t-space-2: 8px;
  --t-space-3: 12px;
  --t-space-4: 16px;
  --t-space-5: 20px;
  --t-space-6: 24px;
  --t-space-8: 32px;
  --t-space-10: 40px;
  --t-space-12: 48px;
  --t-gutter: 16px;
  --t-dialog-inset: 32px;
  --t-dialog-h: calc(100dvh - var(--t-dialog-inset) * 2);

  /* and the public site's own light literals, which override both */
  --t-text: rgba(0, 0, 0, 0.98);
  --t-text-2: rgba(0, 0, 0, 0.75);
  --t-text-3: rgba(0, 0, 0, 0.56);
  --t-text-muted: rgba(0, 0, 0, 0.56);
  --t-text-inverse: #ffffff;
  --t-on-brand: #ffffff;
  --t-brand: #1d6af0;
  --t-brand-hover: #1560e8;
  --t-brand-press: #0f4fc4;
  --t-brand-ring: rgba(31, 113, 255, 0.16);
  --t-brand-wash: rgba(31, 113, 255, 0.08);
  --t-brand-border: #1d6af0;
  --t-focus: #1f71ff;
  --t-focus-ring: rgba(31, 113, 255, 0.16);
  --t-link: #1d4ed8;
  --t-secondary: rgba(60, 60, 67, 0.62);
  --t-secondary-wash: rgba(118, 118, 128, 0.08);
  --t-bg: #FFFFFF;
  --t-surface: #ffffff;
  --t-surface-2: #ffffff;
  --t-surface-sunken: #f5f5f7;
  --t-surface-overlay: rgba(255, 255, 255, 0.72);
  --t-fill: rgba(214, 214, 214, 0.05);
  --t-fill-hover: rgba(118, 118, 128, 0.08);
  --t-fill-press: rgba(118, 118, 128, 0.12);
  --t-row-hover: rgba(118, 118, 128, 0.045);
  --t-border: rgba(60, 60, 67, 0.16);
  --t-border-strong: rgba(60, 60, 67, 0.30);
  --t-border-soft: rgba(60, 60, 67, 0.08);
  --t-success: #34c759;
  --t-success-bg: rgba(52, 199, 89, 0.10);
  --t-success-border: rgba(52, 199, 89, 0.28);
  --t-warning: #ff9500;
  --t-warning-bg: rgba(255, 149, 0, 0.10);
  --t-warning-border: rgba(255, 149, 0, 0.28);
  --t-danger: #ff3b30;
  --t-danger-bg: rgba(255, 59, 48, 0.10);
  --t-danger-border: rgba(255, 59, 48, 0.28);
  --t-danger-text: #b91c1c;
  --t-warning-text: #b45309;
  --t-success-text: #15803d;
  --t-purple-text: #6d28d9;
  --t-brand-text: #1d4ed8;
  --t-e1: 0 1px 2px rgba(0,0,0,.04);
  --t-e2: 0 2px 6px rgba(0,0,0,.05);
  --t-e3: 0 8px 24px rgba(0,0,0,.08);
  --t-e4: 0 16px 48px rgba(0,0,0,.12);
  --t-e5: 0 32px 84px rgba(0,0,0,.18);
}

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

/* ══ THE SAME TYPOGRAPHIC SETUP THE APPLICATION GIVES html ══

   Copied from src/styles/taskeen-ux.scss section 2, and font-synthesis-weight is the one that
   matters. THIS was the owner's "bold text is not looking correct", and his "what i have on
   taskeen nav header is correct, what you have on blog header is incorrect":

   Manrope is clamped at 500 on purpose. When a rule asks for 600 -- as the compiled nav does for
   the selected item -- Chrome does not simply use 500. It SYNTHESISES the missing weight by
   stroking the 500 glyphs thicker, which is the smeared, too-heavy look. The application never
   shows it because taskeen-ux.scss turns synthesis off on html, so 600 resolves to the real 500
   cut. blog.css did not carry that line, so the identical markup rendered differently in the two
   places: /pricing drew a clean "Pricing", /blog/ drew a fattened "Blog".

   ── AND WHY I MISSED IT TWICE ────────────────────────────────────────────────────────────────

   I measured advance widths and found 500, 600, 700 and 800 identical, and concluded Chrome was
   CLAMPING. That conclusion was wrong and the instrument was why: Chrome's synthetic bold adds
   stroke to the glyph and leaves the advance width alone. A width probe cannot tell clamping from
   faking -- they look the same in every number it reports. The thing that showed it was putting
   the two headers side by side in one screenshot, which is what the owner had been doing. */
html {
  -webkit-text-size-adjust: 100%;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
  text-rendering: optimizeLegibility;
  font-synthesis-weight: none;
}

body {
  margin: 0;
  background: var(--t-bg);
  color: var(--t-text);
  font-family: var(--t-font-sans);
  font-size: 1.0625rem;
  line-height: 1.7;
  -webkit-font-smoothing: antialiased;
}

.skip {
  position: absolute; left: -9999px;
  background: var(--t-surface); color: var(--t-text);
  padding: .75rem 1rem; border-radius: var(--t-r-sm); z-index: 10;
}
.skip:focus { left: 1rem; top: 1rem; }


/* ── the post ──
   The top padding clears the nav, which taskeen-nav.component.scss fixes to the viewport at
   --nav-height. Without it the fixed bar sits on top of the post's date line, which is what it
   did the first time the real chrome went in. Expressed in terms of the token rather than as
   52px, so a change to the nav's height carries here. */
.post {
  max-width: 44rem;
  margin: 0 auto;
  padding: calc(var(--nav-height, 52px) + 2.5rem) 1.5rem 4rem;
}

.post__meta {
  display: flex; gap: .75rem; flex-wrap: wrap;
  margin: 0 0 1rem; font-size: .8125rem; letter-spacing: .02em;
  text-transform: uppercase; color: var(--t-text-3);
}
.post__by::before { content: "·"; margin-right: .75rem; }
.post__by { color: var(--t-text-2); }

.post h1 {
  margin: 0 0 2rem;
/* ── WEIGHT STOPS AT 500, AND THAT IS THE DESIGN ──
   Owner, 2026-11-08: "font-weight should be 200 500; it is a purpose."

   The self-hosted Manrope is a variable font whose axis is clamped at 500 deliberately, so 500 is
   the heaviest cut that exists. With font-synthesis-weight: none on html -- which this stylesheet
   now sets, as the application does -- a rule asking for 600 or 700 resolves to the real 500 cut
   and draws nothing heavier.

   CORRECTION, and it cost two wrong answers: WITHOUT that line Chrome does not clamp, it FAKES
   the weight by stroking the glyphs thicker. I measured advance widths (200: 274.92, 300: 280.09,
   400: 285.23, then 500/600/700/800 all 290.41) and read the identical numbers as proof of
   clamping. Synthetic bold preserves the advance width, so a width probe cannot tell the two
   apart. The owner could see it; my instrument could not.

   These headings therefore ask for 500, which is both what they get and what they say. Emphasis
   comes from size, colour and spacing against 400 body text. A rule asking for a weight the font
   does not have is a rule describing an intention nobody can see -- and, until the synthesis line
   landed, one the browser answered by inventing it. */
  font-family: var(--t-font-display, var(--t-font-sans));
  font-size: clamp(2rem, 5vw, 2.75rem);
  line-height: 1.12;
  letter-spacing: -.03em;
  font-weight: var(--t-fw-medium, 500);
}

/* ── the deck ──
   The four cards that went out on LinkedIn, as a scroll-snap carousel. CSS ONLY: these pages
   carry no JavaScript, which is what keeps script-src 'self' sufficient and leaves nothing for
   the policy to hash. A swipe on a handset and a horizontal scroll on a desktop both land on a
   card edge, and the track is focusable so a keyboard can move it too.

   The cards are 4:5, so a full-width card would be taller than most screens. Sizing by viewport
   height keeps a whole card visible with the next one showing at the edge, which is also the cue
   that there is more to see. */
.deck { margin: 0 0 2.5rem; }

.deck__frame { position: relative; }

.deck__track {
  display: flex;
  gap: 1rem;
  margin: 0;
  padding: 0;
  list-style: none;
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  overscroll-behavior-x: contain;
  scroll-behavior: smooth;
  /* NO SCROLLBAR: the arrows are the affordance now. The track stays scrollable because a
     trackpad and a thumb use it regardless of whether a button exists. */
  scrollbar-width: none;
  -ms-overflow-style: none;
}
.deck__track::-webkit-scrollbar { width: 0; height: 0; display: none; }
.deck__track:focus-visible { outline: 2px solid var(--t-text); outline-offset: 4px; border-radius: 4px; }

/* ── the arrows ──
   Over the track rather than beside it, so the cards keep the full column width. Sized for a
   finger (44px) and given a solid fill, because they sit on top of artwork that is nearly black
   and an outline button would vanish into it. */
.deck__arrow {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  z-index: 2;
  display: grid;
  place-items: center;
  width: 2.75rem;
  height: 2.75rem;
  padding: 0;
  border: 1px solid var(--t-border);
  border-radius: 50%;
  background: var(--t-surface);
  color: var(--t-text);
  cursor: pointer;
  box-shadow: 0 2px 10px rgba(0, 0, 0, .14);
  transition: opacity .15s ease, background .15s ease;
}
.deck__arrow svg { width: 1.25rem; height: 1.25rem; }
.deck__arrow--prev { left: -.75rem; }
.deck__arrow--next { right: -.75rem; }
.deck__arrow:hover { background: var(--t-surface-sunken); }
.deck__arrow:focus-visible { outline: 2px solid var(--t-text); outline-offset: 2px; }

/* At an end the button stays in place and stops responding, rather than disappearing and
   shifting what is under the cursor. */
.deck__arrow[disabled] { opacity: .3; cursor: default; box-shadow: none; }
.deck__arrow[hidden] { display: none; }

.deck__slide {
  flex: 0 0 auto;
  width: min(19rem, 72vw);
  scroll-snap-align: center;
  border: 1px solid var(--t-border);
  border-radius: var(--t-r-md, 12px);
  overflow: hidden;
  line-height: 0;
}
.deck__slide svg { display: block; width: 100%; height: auto; }

@media (min-width: 60rem) {
  .deck { margin-inline: -4rem; }
  .deck__frame { padding-inline: 4rem; }
  .deck__arrow--prev { left: 1.75rem; }
  .deck__arrow--next { right: 1.75rem; }
}

@media (prefers-reduced-motion: reduce) {
  .deck__track { scroll-behavior: auto; }
  .deck__arrow { transition: none; }
}

/* ══ THE ENTRANCE ══

   Owner, 2026-11-08: "add animations to page load in /blog/ and when i opened individual blog
   item."

   ── CSS ONLY, AND THAT IS THE LOAD-BEARING DECISION ──────────────────────────────────────────

   The obvious build is a script that hides everything and reveals it on scroll. Three reasons not
   to, on this site in particular:

     1. IF THE SCRIPT NEVER RUNS, THE PAGE IS BLANK. A reveal-on-scroll pattern writes the hidden
        state and then owes you the un-hiding. A 404 on the script, a parse error, a browser that
        gave up on it, and the post is a nav above an empty page. A CSS animation cannot fail that
        way: it ends at the to-state whatever happens, and animation-fill-mode both only holds the
        from-state while it waits its turn.
     2. THE CRAWLERS. GPTBot, ClaudeBot, PerplexityBot and CCBot read raw HTML and run nothing.
        Google renders, but its renderer is not a promise. Every one of them sees finished markup
        here, because nothing is withheld pending an event.
     3. script-src is 'self' with hashes. An inline script to set a no-flash class before paint
        would need its own hash in the host's CSP, and a header change on the Ubuntu box is a poor
        price for a fade.

   So: no script, no observer, no hidden state that something has to come back and undo.

   ── AND IT IS OFF WHEN THE READER SAYS SO ────────────────────────────────────────────────────

   The whole block sits inside prefers-reduced-motion: no-preference, which is the correct
   polarity: a browser that never heard of the query matches NEITHER, so it gets no animation at
   all rather than one it cannot turn off. Vestibular disorders are the reason this setting
   exists, and the default here is stillness. */
@media (prefers-reduced-motion: no-preference) {
  @keyframes tk-rise {
    from { opacity: 0; transform: translateY(14px); }
    to   { opacity: 1; transform: none; }
  }

  /* One curve for everything: a soft deceleration, nothing bouncing. 480ms is long enough to read
     as deliberate and short enough that a second visit does not feel like waiting. */
  .listing__head,
  .cards > .card,
  .post__meta,
  .post h1,
  .deck,
  .post__body,
  .post__tags,
  .post__cta {
    animation: tk-rise .48s var(--t-ease-out, cubic-bezier(.22, .61, .36, 1)) both;
  }

  /* ── /blog/ ──
     The head, then the cards in sequence. Capped at the tenth: a stagger that keeps counting puts
     the hundredth card six seconds into its own page, and by then the delay is not a flourish,
     it is a fault. Everything past the cap arrives with the tenth. */
  .listing__head { animation-delay: .02s; }
  .cards > .card { animation-delay: .14s; }
  .cards > .card:nth-child(1) { animation-delay: .08s; }
  .cards > .card:nth-child(2) { animation-delay: .12s; }
  .cards > .card:nth-child(3) { animation-delay: .16s; }
  .cards > .card:nth-child(4) { animation-delay: .20s; }
  .cards > .card:nth-child(5) { animation-delay: .24s; }
  .cards > .card:nth-child(6) { animation-delay: .28s; }
  .cards > .card:nth-child(7) { animation-delay: .32s; }
  .cards > .card:nth-child(8) { animation-delay: .36s; }
  .cards > .card:nth-child(9) { animation-delay: .40s; }
  .cards > .card:nth-child(n+10) { animation-delay: .44s; }

  /* ── a post ──
     The order a reader meets it: the date and byline, the headline, the carousel, then the prose.
     The BODY animates as one block rather than paragraph by paragraph, because a post is one
     piece of writing and lines arriving separately reads as a slideshow.
     The headline carries no delay of its own: it is the LCP element on this page, and holding the
     largest paint back by a quarter second to look tidy is paying for the flourish with the
     measurement Google takes. */
  .post__meta  { animation-delay: .04s; }
  .post h1     { animation-delay: 0s; }
  .deck        { animation-delay: .12s; }
  .post__body  { animation-delay: .18s; }
  .post__tags,
  .post__cta   { animation-delay: .22s; }

  /* Nothing below animates on load: the pager and the footer are where a reader arrives after
     scrolling, and an element that finished its entrance before anyone looked at it has animated
     for no one. */
}

.post__body > p:first-of-type { font-size: 1.1875rem; color: var(--t-text); }

.post h2 {
  margin: 2.75rem 0 1rem;
  font-size: 1.4375rem; line-height: 1.25; letter-spacing: -.02em; font-weight: var(--t-fw-medium, 500);
}
.post h3 { margin: 1.75rem 0 .5rem; font-size: 1.0625rem; font-weight: var(--t-fw-medium, 500); }
.post p { margin: 0 0 1.25rem; color: var(--t-text-2); }

/* ── the cited block. Named sources are the strongest signal this corpus has, so they are
      given their own surface rather than left in paragraph four. ── */
.evidence {
  margin: 3rem 0 0; padding: 1.5rem 1.75rem;
  background: var(--t-surface-sunken);
  border: 1px solid var(--t-border);
  border-radius: var(--t-r-md, 12px);
}
.evidence__h { margin: 0 0 1rem !important; font-size: .8125rem !important; text-transform: uppercase; letter-spacing: .06em; color: var(--t-text-3); }
.evidence ul { margin: 0; padding: 0; list-style: none; }
.evidence li + li { margin-top: 1rem; padding-top: 1rem; border-top: 1px solid var(--t-border); }
.evidence__claim { display: block; color: var(--t-text); }
.evidence cite { display: block; margin-top: .375rem; font-size: .875rem; font-style: normal; color: var(--t-text-3); }

/* ── the FAQ, which is the part an assistant lifts ── */
.faq { margin-top: 3rem; padding-top: 2rem; border-top: 1px solid var(--t-border); }
.faq > h2 { margin-top: 0; }

.post__foot { margin-top: 3rem; padding-top: 1.5rem; border-top: 1px solid var(--t-border); }
.post__tags { display: flex; gap: .5rem; flex-wrap: wrap; margin: 0 0 1rem; font-size: .8125rem; color: var(--t-text-3); }
.post__cta { margin: 0; color: var(--t-text-2); }
/* ── NO BLUE ON A LINK (owner, 2026-11-08) ──
   tokens.scss sets --t-brand to #1d1d1f at :root and to #1f71ff under html.public-scope, and
   this stylesheet emits public-scope last because that is how the application resolves it. So
   every rule written as color: var(--t-brand) came out blue. The real chrome never does that:
   .nav__link and .footer__link take var(--ink-muted) and hover to var(--ink). Prose links here
   use the same scale, with an underline carrying the affordance instead of a colour. */
.post__body a,
.post__cta a,
.evidence a {
  color: var(--t-text);
  text-decoration: underline;
  text-underline-offset: .15em;
  text-decoration-thickness: 1px;
  text-decoration-color: var(--t-text-3);
}
.post__body a:hover,
.post__cta a:hover,
.evidence a:hover { text-decoration-color: var(--t-text); }

.pager {
  display: flex; justify-content: space-between; gap: 1rem; flex-wrap: wrap;
  margin-top: 2.5rem; padding-top: 1.5rem; border-top: 1px solid var(--t-border);
  font-size: .9375rem;
}
.pager a { color: var(--t-text-2); text-decoration: none; max-width: 20rem; }
.pager a:hover { color: var(--t-text); }
.pager__r { text-align: right; margin-left: auto; }


a:focus-visible, button:focus-visible {
  outline: 2px solid var(--t-text); outline-offset: 2px; border-radius: 2px;
}

/* ══ THE INDEX IS A CARD GRID, AND IT IS NOT ON THE READING MEASURE ══

   Owner, 2026-11-08: "blog/ items can be list or cards. currently it is only list and very narrow
   leaving so much empty space on the left and right side."

   The index was inheriting .post, which is a READING MEASURE: about 34rem, the width that keeps a
   line of prose at 65-75 characters. That width is a decision about reading one article, and it
   was never a decision about this page -- it just came along with the wrapper. On a 1568px screen
   it left roughly two thirds of the page empty on either side of a single thin column.

   A card is also the right shape for what each row already carries: the 1200x628 social image, a
   date, a title and a sentence. In a column that image had to be shrunk to a 11rem stamp; in a
   card it is the card.

   auto-fill with a 20rem minimum rather than a fixed column count, so the number of columns is a
   consequence of the window and there is no breakpoint to maintain: three up on a desktop, two on
   a laptop, one on a phone, and nothing to change when the next size of screen arrives. */
/* 8% side padding, which is what the public home page uses -- .hero and every section there are
   padding: 140px 8% 100px against a 1920px inner maximum, so the gutter is a share of the window
   rather than a fixed box. Measured at 1920: the home page's content is 1604 wide, and so is this.
   The first version used a 78rem centred column, which was narrower than the rest of the site at
   every width above 1248 and made the blog look like a different property. */
.listing {
  max-width: 1920px;
  margin: 0 auto;
  padding: calc(var(--nav-height, 52px) + 3rem) 8% 5rem;
}
.listing__head { max-width: 42rem; margin: 0 0 2.5rem; }
.listing__head h1 { margin: 0 0 .5rem; }
.listing__head p { margin: 0; color: var(--t-text-2); }

.cards { display: grid; grid-template-columns: repeat(auto-fill, minmax(20rem, 1fr)); gap: 1.5rem; list-style: none; margin: 0; padding: 0; }

/* The whole card is ONE link. A card with a linked image and a linked title beside it is two
   stops on the same destination for anyone using a keyboard or a screen reader, which is why the
   list version had to mark the thumb aria-hidden; with one anchor the problem does not arise. */
.card { display: flex; }
.card__link {
  display: flex; flex-direction: column; width: 100%;
  background: var(--t-surface);
  border: 1px solid var(--t-border);
  border-radius: var(--t-r-card, 12px);
  overflow: hidden;
  text-decoration: none;
  color: inherit;
  transition: border-color var(--t-t-base, .2s) var(--t-ease, ease), box-shadow var(--t-t-base, .2s) var(--t-ease, ease), transform var(--t-t-base, .2s) var(--t-ease, ease);
}
.card__link:hover { border-color: var(--t-border-strong); box-shadow: var(--t-e2); transform: translateY(-2px); }
.card__link:focus-visible { outline: 2px solid var(--t-focus); outline-offset: 2px; }

/* aspect-ratio on the frame and object-fit on the image: the frame then has a height of its own
   and cannot inherit one from the text beside it. A bordered box 60px taller than its picture is
   what the list version drew before align-self fixed it, and this shape cannot do it at all. */
.card__thumb { aspect-ratio: 1200 / 628; background: var(--t-surface-sunken); border-bottom: 1px solid var(--t-border); }
.card__thumb img { display: block; width: 100%; height: 100%; object-fit: cover; }

.card__body { display: flex; flex-direction: column; gap: .5rem; padding: 1.25rem; }
.card time { font-size: .75rem; letter-spacing: .04em; text-transform: uppercase; color: var(--t-text-3); }
.card h2 {
  margin: 0; font-size: 1.1875rem; line-height: 1.3; letter-spacing: -.015em;
  font-weight: var(--t-fw-medium, 500);           /* 500 is the heaviest cut the font pack has */
  color: var(--t-text);
}
.card__link:hover h2 { text-decoration: underline; text-underline-offset: .15em; text-decoration-color: var(--t-text-3); }
.card p { margin: 0; color: var(--t-text-2); font-size: .9375rem; line-height: 1.55; }

.index__draft { padding: .75rem 1rem; margin-bottom: 2rem; border-radius: var(--t-r-sm, 8px); background: var(--t-surface-sunken); border: 1px solid var(--t-border); }

@media (max-width: 640px) {
  .listing { padding: calc(var(--nav-height, 52px) + 1.5rem) 1.25rem 3rem; }
  .cards { grid-template-columns: 1fr; gap: 1.25rem; }
}

@media (max-width: 640px) {
  .post { padding: calc(var(--nav-height, 52px) + 1.5rem) 1.25rem 3rem; }
  .evidence { padding: 1.25rem; }
  .pager__r { text-align: left; margin-left: 0; }
}

