/* The Chronicle — generated from src/tokens.mjs by src/style.mjs.
   Do not hand-edit: the next build discards it. To change a colour, change the
   hex in src/tokens.mjs and the ratio beside it; test/design.test.mjs
   recomputes every ratio from the hexes and fails on a mismatch.

   AN UNLISTED PAIRING IS NOT APPROVED. Every colour below is var(--token), and
   every token used as a colour has a row in PAIRINGS for both themes. */

:root {
  color-scheme: light dark;
  --paper: #ffffff; /* the declared ground: every ratio above is measured against this */
  --ink: #15171a; /* 17.96:1 on --paper, min 7:1 — body prose, headlines, the digest at parity with the claim it proves */
  --sub: #53585e; /* 7.18:1 on --paper, min 7:1 — deks, metadata, breadcrumbs, footer */
  --rule: #8e9095; /* 3.19:1 on --paper, min 3:1 — the 1px structural divider — non-text, carries no information */
  --verified: #0a5c33; /* 8.1:1 on --paper, min 7:1 — the verified status label and its rail */
  --unverified: #4f545a; /* 7.64:1 on --paper, min 7:1 — the unverified status label and its rail */
  --unbacked: #6b4506; /* 8.47:1 on --paper, min 7:1 — the unbacked status label and its rail */
  --mismatch: #8c1a12; /* 9.24:1 on --paper, min 7:1 — the mismatch status label and its rail */
  --font-serif: 'Iowan Old Style','Palatino Linotype',Palatino,'Book Antiqua',Baskerville,'Bitstream Charter',Charter,Georgia,'Times New Roman',serif;
  --font-mono: ui-monospace,SFMono-Regular,'SF Mono',Menlo,Consolas,'Liberation Mono','DejaVu Sans Mono',monospace;
  /* The reading column. It was 44rem, which put a story's longest rendered line
     at 83 non-space glyphs — about 96 characters with spaces, measured on the
     render at 1440 on 2026-11-18. That is well past the 45-75 a text face is cut
     for, and the cost lands on the return sweep at 1.6 line-height. 34rem puts
     the same paragraph at roughly 73 characters. Changing the TYPE SIZE instead
     does not fix it: 19px across a 664px column is still ~81 characters. */
  --measure: 34rem;
  /* The SHEET: the page itself, and the width the register needs. A six-column
     table wants more than a reading measure, and 68rem leaves the STORY column
     enough room for a headline to read as a headline once the five machine
     columns have taken their fixed widths; below that the region scrolls, and
     the caption says so. Every box on the page — masthead, article, rail,
     footer — is laid out inside one sheet of this width, which is what gives
     them one left edge (see "The sheet" below). */
  --measure-wide: 68rem;
  /* The gutter between the reading column and the rail beside it. */
  --rail-gap: 3rem;
}

/* Dark, from the reader's own setting. The [data-theme="light"] guard lets a
   pinned light theme win over the system preference without a script. */
@media (prefers-color-scheme: dark) {
  :root:not([data-theme="light"]) {
  --paper: #101214; /* the declared ground: every ratio above is measured against this */
  --ink: #eae8e3; /* 15.33:1 on --paper, min 7:1 — body prose, headlines, the digest at parity with the claim it proves */
  --sub: #a8acb2; /* 8.23:1 on --paper, min 7:1 — deks, metadata, breadcrumbs, footer */
  --rule: #5d636a; /* 3.09:1 on --paper, min 3:1 — the 1px structural divider — non-text, carries no information */
  --verified: #6fdc9b; /* 11.07:1 on --paper, min 7:1 — the verified status label and its rail */
  --unverified: #b0b4ba; /* 9.01:1 on --paper, min 7:1 — the unverified status label and its rail */
  --unbacked: #e0a73c; /* 8.73:1 on --paper, min 7:1 — the unbacked status label and its rail */
  --mismatch: #ff9f95; /* 9.52:1 on --paper, min 7:1 — the mismatch status label and its rail */
  }
}
:root[data-theme="dark"] {
  --paper: #101214; /* the declared ground: every ratio above is measured against this */
  --ink: #eae8e3; /* 15.33:1 on --paper, min 7:1 — body prose, headlines, the digest at parity with the claim it proves */
  --sub: #a8acb2; /* 8.23:1 on --paper, min 7:1 — deks, metadata, breadcrumbs, footer */
  --rule: #5d636a; /* 3.09:1 on --paper, min 3:1 — the 1px structural divider — non-text, carries no information */
  --verified: #6fdc9b; /* 11.07:1 on --paper, min 7:1 — the verified status label and its rail */
  --unverified: #b0b4ba; /* 9.01:1 on --paper, min 7:1 — the unverified status label and its rail */
  --unbacked: #e0a73c; /* 8.73:1 on --paper, min 7:1 — the unbacked status label and its rail */
  --mismatch: #ff9f95; /* 9.52:1 on --paper, min 7:1 — the mismatch status label and its rail */
}

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

body {
  margin: 0;
  /* The declared ground. This was the system keyword Canvas, so the paper was
     whatever the browser chose and no ratio above could be computed. */
  background: var(--paper);
  color: var(--ink);
  font: 17px/1.6 var(--font-serif);
  -webkit-text-size-adjust: 100%;
}

/* ── The two voices ──────────────────────────────────────────────────────── */
.masthead-name,
h1,
h2,
h3,
.dek,
.edition-dek,
.body,
.claim-text,
.devlog-summary,
.register-title {
  font-family: var(--font-serif);
}
.byline,
.meta,
.devlog-empty,
.crumbs,
.claim-receipt,
.claim-digest,
.claim-status,
.devlog-meta,
.register th,
.register td,
.sitefoot,
.pagenav,
code,
.leaflink,
.masthead-strap,
.provenance,
.state-key,
.verdict,
.disclosure,
.standing,
.correction,
.claim-anchor,
.cite-rows,
.related,
.tally th,
.tally td,
.tally-figure,
.spec-table th,
.spec-table td,
.spec-code {
  font-family: var(--font-mono);
}

/* ── The sheet, the column, and ONE left edge ────────────────────────────── */
/* ONE left edge, everywhere — and this is the second attempt at it.

   The first version had the masthead and the footer on --measure-wide while the
   reading column sat on --measure, so the logotype and the colophon were 112px
   left of the headline on three page types and flush with it on the fourth.
   Measured at 1440 on 2026-11-18: masthead 276, h1 388 on /, /story/ and
   /changelog/; both 276 on /archive/. "Concentric" was the stated intent and it
   read as a layout bug, because which edge you got depended on the page.
   The fix then was to put EVERYTHING on the reading measure — which cured the
   two edges and cost the publication its desktop presence: measured at 1440 on
   2026-11-18, the whole site was a 544px ribbon centred in a 1440px viewport,
   a story ran 4,450px tall in one column and the front page 2,100px for two
   stories. A phone page, stretched.

   The sheet is the fix for both at once. There is now ONE box — .wrap for the
   chrome, .sheet for the page — at --measure-wide, centred, with one padding
   edge. Everything that carries prose sits at --measure flush against that
   edge, so the logotype, the breadcrumb, the headline and the colophon share a
   left edge BY CONSTRUCTION rather than by two boxes agreeing on a number. What
   the sheet buys is the room to the right of the reading column, which is where
   a story's standing matter goes (see .rail).

   Below the breakpoint nothing changes: the sheet never reaches 68rem, .story
   never reaches 34rem, and the page is the single column it was. */
.wrap, .sheet { max-width: var(--measure-wide); margin: 0 auto; padding: 0 20px; }
.story { max-width: var(--measure); }
/* The register is the one element that takes the whole sheet. */
.story--wide { max-width: none; }
.story { padding-top: 28px; padding-bottom: 28px; }
.story + .story { padding-top: 0; }
main { display: block; }

/* The rail: a story's standing matter, beside the story rather than below it.
   What is in it is APPARATUS — what a live reading found, the leaf on the
   estate log, how to cite this story, what else rests on the same records. What
   is NOT in it is the article, the claims and their receipts: the claims are the
   story, not furniture around it. The independence disclosure stays with them
   too, because src/render.mjs emits it so that no page can carry a story
   without it, and moving it here would mean moving it out of the renderer.

   Source order is article, then rail, so with the stylesheet off — or on a
   phone, where this rule does not apply — a reader gets the story and then its
   record, which is the order the page is written in. */
.rail .story { max-width: none; }

@media (min-width: 64rem) {
  /* 64rem is the first width at which --measure + --rail-gap and a rail wide
     enough to read a digest in both fit inside the sheet. */
  .sheet--story {
    display: grid;
    grid-template-columns: var(--measure) minmax(0, 1fr);
    column-gap: var(--rail-gap);
    align-items: start;
  }
  /* Two children, so auto-placement puts both on row 1: the article in the
     reading column, the rail in what is left. Neither is positioned by hand. */
}

.skip {
  position: absolute; left: -9999px; top: 0; z-index: 10;
  padding: 10px 14px; background: var(--paper); color: var(--ink);
  border: 1px solid var(--rule); font: 13px/1.4 var(--font-mono);
}
.skip:focus { left: 8px; top: 8px; }

/* ── The masthead ────────────────────────────────────────────────────────── */
.masthead { border-bottom: 1px solid var(--rule); padding: 18px 0 12px; }
/* The nameplate. It rendered at 22px — near body size — so the one
   element that tells a reader which publication they are standing in was the
   quietest thing above the fold. On paper this is the masthead; it is set like
   one at desktop and left near its old size on a phone, where 34px would
   take most of the first viewport before any news. */
.masthead-name {
  font-size: 22px; letter-spacing: .01em; margin: 0;
  display: flex; align-items: center; min-height: 44px;
}
@media (min-width: 64rem) {
  .masthead-name { font-size: 34px; letter-spacing: -.015em; }
}
/* The 44px target goes on the ANCHOR, not on the box around it. WCAG 2.5.8
   measures the thing that responds to the pointer: a 35px link centred in a
   44px row is a 35px target with dead space around it, which is what this was
   (measured 129x35 at 390 on 2026-11-18). */
.masthead-name a {
  color: var(--ink); text-decoration: none;
  display: inline-flex; align-items: center; min-height: 44px;
}
.masthead-name a:hover { text-decoration: underline; }
.masthead-strap { font-size: 13px; color: var(--sub); margin: 0; }

/* ── Prose ───────────────────────────────────────────────────────────────── */
h1 { font-size: clamp(28px, 5vw, 40px); line-height: 1.12; letter-spacing: -.01em; margin: 0 0 12px; }
h2 { font-size: 22px; line-height: 1.2; margin: 32px 0 10px; }
.dek, .edition-dek { font-size: 19px; color: var(--sub); margin: 0 0 10px; }
.body { font-size: 17px; margin: 0 0 1em; }
.byline { font-size: 13px; color: var(--sub); margin: 0 0 4px; }
.meta, .devlog-empty { font-size: 13px; color: var(--sub); margin: 0 0 6px; line-height: 1.6; }
.provenance { font-size: 13px; color: var(--sub); }
a { color: var(--ink); }
.body a, .meta a, .dek a, .provenance a { text-underline-offset: 2px; }
/* Mono carries a larger x-height than serif at the same em, so a <code> token
   inside a serif paragraph bulges out of the line and breaks its colour —
   measured on /changelog/, where the package name in the dek computed to 19px
   mono inside a 19px serif paragraph and stood 22px tall in a 30.4px line. The
   correction is scoped to the serif contexts: mono inside mono needs none, and
   applying it everywhere would shrink the register's ids to 11.7px. */
.dek code, .edition-dek code, .body code, .claim-text code, .devlog-summary code { font-size: .9em; }

/* ── Receipts: the claim, and the digest that proves it ──────────────────── */
.receipts { border-top: 1px solid var(--rule); margin-top: 32px; padding-top: 18px; }
.receipts h2 { font-size: 13px; text-transform: uppercase; letter-spacing: .1em; color: var(--sub); margin: 0 0 12px; font-family: var(--font-mono); }
.claims { list-style: none; padding: 0; margin: 0; display: grid; gap: 16px; }
.claim { padding: 2px 0 2px 16px; }
.claim-text { font-size: 17px; margin: 0 0 8px; }
.claim-receipt { margin: 0; display: flex; flex-wrap: wrap; gap: 6px 16px; align-items: baseline; font-size: 14px; }
/* The digest sits at PARITY with the claim it proves: ink, not --sub; 600, not
   400; one pixel below the claim because mono renders optically smaller than
   serif at the same em. It used to be the smallest, faintest thing in the row. */
/* The WHOLE digest, on screen, wrapping onto its own line. It was a
   12-character prefix with the full 64 in a 'clip-path' span that also carried
   'aria-hidden="true"' — so the page told a reader to "confirm its digest
   matches" and then put the value out of reach of their eyes AND of a screen
   reader, revealing it only in print. A receipt a reader cannot read is not a
   receipt, and that instruction is this publication's central one. */
.claim-digest {
  font-size: 16px; font-weight: 600; color: var(--ink);
  flex: 1 1 100%; overflow-wrap: anywhere;
}
.claim-status { font-size: 14px; }
.claim-mark { font-weight: 700; padding-right: 2px; }
/* The receipt row carries TWO controls now — the record's own source and the
   claim's own anchor — so it is a pair of controls rather than a link inside a
   sentence, and WCAG 2.5.8's inline exception stops covering it. The same three
   declarations .devlog-meta a already carries for the same reason. */
.claim-receipt a { display: inline-flex; align-items: center; min-height: 44px; }
.claim-anchor { color: var(--sub); }
.claim-anchor:hover { color: var(--ink); }

/* The four states, rail first. Width and border style before colour, so they
   survive greyscale, a monochrome printer and a reader who sees no hue. */
.claim--verified { border-left: 5px solid var(--verified); }
.claim--verified .claim-status { color: var(--verified); }
.state-key--verified .state-rail { border-left: 5px solid var(--verified); }
.claim--unverified { border-left: 5px dotted var(--unverified); }
.claim--unverified .claim-status { color: var(--unverified); }
.state-key--unverified .state-rail { border-left: 5px dotted var(--unverified); }
.claim--unbacked { border-left: 5px dashed var(--unbacked); }
.claim--unbacked .claim-status { color: var(--unbacked); }
.state-key--unbacked .state-rail { border-left: 5px dashed var(--unbacked); }
.claim--mismatch { border-left: 7px double var(--mismatch); }
.claim--mismatch .claim-status { color: var(--mismatch); }
.state-key--mismatch .state-rail { border-left: 7px double var(--mismatch); }

/* The key that names the encoding, so a reader learns it once.

   The swatch is 44px tall, not 1em. A border STYLE is a pattern along an
   edge and a pattern needs room to repeat: at 1em (13px) a 5px 'dashed' border
   drew one unbroken dash, pixel-identical to 'solid', so the legend taught that
   'verified' and 'unbacked' are the same mark the moment colour was removed.
   src/tokens.mjs STATE_KEY has the measurement. */
.state-key { list-style: none; margin: 18px 0 0; padding: 12px 0 0; border-top: 1px solid var(--rule); display: grid; gap: 8px; font-size: 13px; color: var(--sub); }
.state-key li { display: flex; align-items: center; gap: 8px; }
.state-rail { flex: 0 0 auto; width: 0; height: 44px; }

/* Related, by citation: the rows the generated graph produced. A list of
   relations is not a list of claims, so it gets its own box rather than
   borrowing .claims — and it wraps, because a related row carries a headline
   somebody wrote beside the record refs both stories cite. */
.related-rows { list-style: none; padding: 0; margin: 0 0 10px; display: grid; gap: 8px; }
.related-rows code { overflow-wrap: anywhere; }

/* ── The edition ─────────────────────────────────────────────────────────── */
.edition { list-style: none; padding: 0; margin: 0; }
.edition-item { border-top: 1px solid var(--rule); padding: 20px 0; }
.edition-item h2 { font-size: clamp(20px, 3.5vw, 26px); line-height: 1.2; margin: 0 0 6px; }
/* The lead. Every row rendered at one size, so an edition of two stories had no
   front page — a reader was handed two equal headlines and left to work out
   which was the news. The newest story leads; the size comes from SIZES so it
   is checkable beside every other size rather than a number typed in a rule. */
.edition-item--lead h2 { font-size: clamp(26px, 4.4vw, 34px); line-height: 1.14; letter-spacing: -.01em; }
/* A headline was the only link on this site with NO affordance: 'text-decoration:
   none' and a colour computing to exactly --ink, identical to body prose, while
   every other link is underlined. The focus ring was the first evidence they
   were links at all. A quiet rule-coloured underline that goes to ink on hover
   keeps the restraint and tells the truth. */
.edition-item h2 a {
  color: var(--ink);
  text-decoration: underline; text-decoration-color: var(--rule); text-underline-offset: 4px;
  display: inline-flex; align-items: center; min-height: 44px;
}
.edition-item h2 a:hover { text-decoration-color: var(--ink); }
/* The computed verdict, beside the row it belongs to. It is the same word and
   the same glyph the claim rows use, so the four states are one vocabulary
   across the site; the glyph is the non-colour channel here (a rail belongs to
   a claim, not to a summary line). */
.verdict { font-size: 14px; }
/* FOUR MALFORMED RULES SHIPPED HERE. This line was written with a SINGLE-quoted
   string inside the template, so the state was never interpolated and the
   emitted stylesheet carried the literal selector .verdict--(dollar){s} four
   times — invalid CSS a browser drops, so the computed verdict on the edition
   and the archive had no state colour at all and the sheet shipped four dead
   rules. The colour-token test could not see it: it scans for var(--token) and
   that literal names no token. The states were still told apart by glyph and
   word, which is why nothing looked broken. The guard is now "the stylesheet
   interpolates every token it means to" in test/design.test.mjs, which fails
   on an unexpanded interpolation marker anywhere in the output. */
.verdict--verified { color: var(--verified); }
.verdict--unverified { color: var(--unverified); }
.verdict--unbacked { color: var(--unbacked); }
.verdict--mismatch { color: var(--mismatch); }

/* ── The disclosure, the correction notices, the cite rows ───────────────── */
/* The disclosure is rendered by the RENDERER (src/render.mjs), not by a
   template, so no page can carry a story without it. It is set in the machine
   voice and sits under its own rule, beneath the receipts it qualifies. */
.disclosure { border-top: 1px solid var(--rule); margin-top: 28px; padding-top: 16px; }
.disclosure h2 { font-size: 13px; text-transform: uppercase; letter-spacing: .1em; color: var(--sub); margin: 0 0 10px; font-family: var(--font-mono); }
.standing { color: var(--ink); }

/* A correction notice is the one thing on a story page that must be read before
   the story: it sits above the article, ruled on both edges so it cannot be
   skimmed past as metadata. It carries no colour — a reader with no hue
   perception gets the rule, the bold lead and the words. */
.correction {
  border-top: 2px solid var(--ink); border-bottom: 1px solid var(--rule);
  margin: 0 0 18px; padding: 12px 0; font-size: 14px; color: var(--ink);
}
.correction strong { font-weight: 700; }

.cite-rows { margin: 0 0 10px; font-size: 14px; display: grid; grid-template-columns: minmax(0, 14rem) minmax(0, 1fr); gap: 6px 16px; }
.cite-rows dt { color: var(--sub); }
.cite-rows dd { margin: 0; overflow-wrap: anywhere; }

/* ── The measure and role tables ─────────────────────────────────────────── */
/* Same shape as the register, and so the same scroll region rather than a
   second implementation of one. */
.tally { border-collapse: collapse; width: 100%; font-size: 13px; min-width: 46rem; }
.tally th, .tally td { text-align: left; vertical-align: top; padding: 10px 12px 10px 0; border-bottom: 1px solid var(--rule); }
.tally th { font-weight: 600; text-transform: uppercase; letter-spacing: .06em; color: var(--sub); }
.tally td { color: var(--ink); }
.tally-figure { font-size: 14px; font-weight: 600; color: var(--ink); }

/* ── The rendered specification ──────────────────────────────────────────── */
.spec-code {
  background: var(--paper); border: 1px solid var(--rule);
  padding: 12px; overflow-x: auto; font-size: 13px; line-height: 1.5; margin: 0 0 1em;
}
.spec-code code { font-size: inherit; }
.spec-list { margin: 0 0 1em; padding-left: 1.4em; }
.spec-list li { margin: 0 0 .4em; }
.spec-table { border-collapse: collapse; width: 100%; font-size: 13px; margin: 0 0 1em; }
.spec-table th, .spec-table td { text-align: left; vertical-align: top; padding: 8px 12px 8px 0; border-bottom: 1px solid var(--rule); }
.spec-table th { font-weight: 600; text-transform: uppercase; letter-spacing: .06em; color: var(--sub); }
.spec-table td { color: var(--ink); overflow-wrap: anywhere; }

/* ── The register ────────────────────────────────────────────────────────── */
/* ONE table for the whole archive, not one per month.
   A table sizes its own columns, so a table per month gave the archive a
   different grid per month on one page: measured at 1440 on 2026-11-18, the ID
   column started at x=1156 in November and x=1091 in September, the header row
   repeated for every month, and each month was its own focusable scroll region.
   A register of record with two grids on one page reads as a bug. 'table-layout:
   fixed' plus a <colgroup> gives every month the same columns, and the month is
   a row-group heading inside the one table. */
.register { border-collapse: collapse; width: 100%; font-size: 13px; table-layout: fixed; }
.register caption { text-align: left; color: var(--sub); font-size: 13px; padding-bottom: 8px; font-family: var(--font-mono); }
.register th, .register td { text-align: left; vertical-align: top; padding: 10px 12px 10px 0; border-bottom: 1px solid var(--rule); }
.register th { font-weight: 600; text-transform: uppercase; letter-spacing: .06em; color: var(--sub); }
.register td { color: var(--ink); }
.register-month { padding-top: 26px; font-size: 13px; text-transform: none; letter-spacing: .08em; color: var(--ink); }
/* A five-column register cannot be squeezed into a phone: letting the cells
   wrap to fit turned a person id into eight stacked fragments, which is
   worse than a scrollbar. The TABLE scrolls instead of the page, inside a
   focusable, named region so a keyboard can reach it (WAI: a scrollable
   region needs keyboard access and an accessible name).

   min-width was 36rem — 576px — which the table never reached, because it laid
   out at 888px at 1440 and 1024 and 728px at 768. So the scroll hatch engaged
   only below phone width and at EVERY desktop width the cells were starved
   instead: 'person/michael' rendered as 'person' / '/micha' / 'el' in a 66px
   cell. 52rem is wide enough for five columns to be read. */
.register-scroll { overflow-x: auto; }
/* The hint sits above the scroller, not in the table's caption: a caption is
   as wide as its table, so inside the scroller it scrolled away with the
   columns it was warning about. */
.register-scroll-hint { margin: 0 0 8px; }
/* The caption names the table for assistive technology; the hint above is what
   a reader sees. Hiding it visually keeps the two from saying the same thing
   twice to an eye while both still reach a screen reader. */
.register caption { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); white-space: nowrap; }
.register-scroll:focus-visible { outline: 3px solid var(--ink); outline-offset: 3px; }
.register { min-width: 52rem; }
/* 'overflow-wrap: anywhere' belongs to the ID alone. It was on every <code> in
   the register, which is how it shattered the short, atomic ids in the BY
   column — the very failure the comment above claimed to have fixed. */
.register-id { overflow-wrap: anywhere; }
.register-atomic { white-space: nowrap; }
.register td a { color: var(--ink); display: inline-flex; align-items: center; min-height: 44px; }
.register-title { font-size: 17px; }

/* ── The changelog ───────────────────────────────────────────────────────── */
.devlog-head h1 { font-size: clamp(26px, 5vw, 36px); margin: 0 0 10px; }
.devlog-day { margin: 26px 0; }
.devlog-day h2 { font-size: 13px; text-transform: uppercase; letter-spacing: .08em; color: var(--sub); margin: 0 0 8px; font-family: var(--font-mono); }
.devlog-entries { list-style: none; margin: 0; padding: 0; border-top: 1px solid var(--rule); }
.devlog-entry { display: flex; flex-wrap: wrap; gap: 6px 24px; padding: 12px 0; border-bottom: 1px solid var(--rule); align-items: baseline; }
.devlog-summary { flex: 1 1 20rem; min-width: 0; font-size: 17px; }
.devlog-meta { margin-left: auto; white-space: nowrap; font-size: 13px; color: var(--sub); }
.leaflink { color: var(--ink); }
/* The sha and its leaf are a PAIR OF CONTROLS, not a link inside a sentence, so
   the inline exception to WCAG 2.5.8 does not cover them: they measured 94x15
   each, eighteen of them on /changelog, and the leaf link is the reason that
   page exists. */
.devlog-meta a { display: inline-flex; align-items: center; min-height: 44px; }

/* ── Chrome: breadcrumbs, prev/next, the footer ──────────────────────────── */
/* A control a finger has to hit is at least 44px tall (WCAG 2.5.8); a link
   inside a sentence is exempt by that rule's own inline exception, and the
   receipts above are sentences. */
.crumbs { font-size: 13px; color: var(--sub); margin: 0 0 18px; }
.crumbs ol { list-style: none; display: flex; flex-wrap: wrap; gap: 0 8px; margin: 0; padding: 0; }
.crumbs li { display: inline-flex; align-items: center; gap: 8px; min-width: 0; }
/* The 44px target is on the ANCHOR and on the current-page span, not on the
   row. The comment here used to claim "the whole crumb is the 44px row"; the
   anchors measured 101x21 and 55x21 inside a 44px li at 390, so the claim was
   not true of the render and the real target was less than half the stated
   height. Same three declarations .sitefoot ul a and .pagenav a already carry. */
.crumbs a, .crumbs [aria-current="page"] {
  display: inline-flex; align-items: center; min-height: 44px; min-width: 0;
}
.crumbs a { color: var(--sub); }
/* The separator LEADS the crumb it precedes instead of trailing the one before
   it. Trailing, it orphaned at the end of a line whenever the current crumb
   wrapped — "The Chronicle / Archive /" with half the line empty and the
   headline alone beneath it, on every story page. */
.crumbs li + li::before { content: '/'; color: var(--sub); }
/* The current crumb is a story's whole headline, which is an indivisible
   inline-flex unit and so wrapped as a block. One line, with the full name
   still in the DOM for the accessible trail and the BreadcrumbList. */
.crumbs [aria-current="page"] {
  color: var(--ink); display: block; max-width: 100%;
  white-space: nowrap; overflow: hidden; text-overflow: ellipsis; line-height: 44px;
}
.pagenav { border-top: 1px solid var(--rule); margin-top: 32px; padding-top: 12px; display: flex; flex-wrap: wrap; gap: 6px 28px; font-size: 13px; }
/* One line. The label is a whole 24-word headline, which ran to two lines at
   1440 and four at 390 and became the heaviest element at the foot of a story,
   above the receipts it was competing with. The full headline stays in the DOM,
   so the accessible name still contains every visible glyph (WCAG 2.5.3). */
.pagenav a {
  color: var(--ink); flex: 1 1 14rem; min-width: 0;
  display: block; line-height: 44px; white-space: nowrap; overflow: hidden; text-overflow: ellipsis;
}

.sitefoot { border-top: 1px solid var(--rule); margin-top: 40px; padding: 18px 0 40px; font-size: 13px; color: var(--sub); line-height: 1.7; }
.sitefoot h2 { font-size: 13px; text-transform: uppercase; letter-spacing: .08em; color: var(--sub); margin: 0 0 6px; font-family: var(--font-mono); font-weight: 600; }
.sitefoot ul { list-style: none; margin: 0 0 14px; padding: 0; }
/* Only the LIST links are controls that want a 44px target. A link inside a
   footer sentence is a link in a sentence — WCAG 2.5.8 exempts it, and giving
   it a 44px box blows the line spacing of the paragraph around it. */
.sitefoot ul a { display: inline-flex; align-items: center; min-height: 44px; }
.sitefoot a { color: var(--sub); }
.sitefoot a:hover { color: var(--ink); }
.sitefoot p { margin: 0 0 12px; }
.foot-group { margin: 0 0 18px; }
/* The doors are a long list; columns keep the footer from being longer than
   the page it ends. */
/* 'gap: 0 24px' meant NO row gap, and a two-line 13px/1.7 anchor fills exactly
   the 44px row — so two consecutive two-line doors touched while single-line
   neighbours sat in 23px of air. The rows were mathematically regular and
   looked jumbled. */
.sitefoot ul.foot-cols { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 8px 24px; align-items: start; }

/* The twelve machine doors fold away. Measured at 1440 on 2026-11-18 the
   footer was 896px against a 727px edition — the colophon outweighed the
   publication, and at 390 a reader scrolled two screens of edition and four of
   machine directory. A <details> needs no script, so it holds on a site whose
   nav must work with scripting off, and every door is still in the markup, in
   llms.txt and in the sitemap. */
/* The same fold, now carrying the colophon's prose groups as well as the doors.
   Measured at 1440 on 2026-11-18 the footer was still roughly half the front
   page once the doors had folded: four blocks of institutional prose under a
   two-story edition. What this press refuses to do, who is accountable and the
   state of the fold are each a thing a reader goes looking for rather than
   reads on the way past, so each is a disclosure. Nothing is removed: every
   word is in the markup, in llms.txt and in the sitemap, and the licence line
   and the vocabulary citations stay open, because the term-map rule is about
   what this page HANDS OUT and a reader should not have to open a fold to find
   out who owns a word it used. */
.foot-group > summary {
  display: flex; align-items: center; gap: 10px; min-height: 44px; cursor: pointer;
  text-transform: uppercase; letter-spacing: .08em; font-weight: 600; color: var(--sub);
}
/* A fold needs an affordance, and a flex summary takes the default disclosure
   marker away — so with four of these the colophon rendered as four headings
   with nothing under them and no sign that anything opened. Measured at 1440 on
   2026-11-18. The marker is drawn here instead: a glyph that CHANGES with the
   state, so it is not a decoration that happens to sit beside a control. */
.foot-group > summary::before {
  content: '+'; font-family: var(--font-mono); font-weight: 700;
  width: 1ch; text-align: center; flex: 0 0 auto;
}
.foot-group[open] > summary::before { content: '\2212'; }
.foot-group[open] > summary { margin-bottom: 6px; }

@media (min-width: 64rem) {
  /* The colophon has the whole sheet at desktop, so its lists take three
     columns rather than two. This override sits HERE, after the rule it
     modifies, rather than up with the grid: both selectors have the same
     specificity, so the one declared later wins, and the first version of this
     was written above and silently lost. */
  .sitefoot ul.foot-cols { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}

a:focus-visible, summary:focus-visible, [tabindex]:focus-visible {
  outline: 3px solid var(--ink); outline-offset: 3px;
}

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: .01ms !important; animation-iteration-count: 1 !important;
    transition-duration: .01ms !important; scroll-behavior: auto !important;
  }
}

/* ── Print is the archive copy ───────────────────────────────────────────── */
/* A story printed is the copy that outlives the deployment, so it carries the
   WHOLE receipt: the full 64-character digest rather than the prefix, and the
   full URL of every link in the content — including the explorer link, whose
   href is where the leaf hash lives. Navigation chrome prints nothing: a
   breadcrumb trail and a prev/next pair are ways to move, and paper does not
   move. */
@media print {
  @page { margin: 18mm; }
  :root {
    --paper: #ffffff; --ink: #000000; --sub: #333333; --rule: #666666;
    --verified: #000000; --unverified: #333333; --unbacked: #333333; --mismatch: #000000;
  }
  body { font-size: 11pt; }
  /* 'body { font-size }' reached NOTHING, because every text class carries an
     explicit px size that is more specific than the element selector — so the
     archive copy printed its headline at ~24.7pt and its prose at screen size.
     The print sizes are scoped to the classes that set them. h1's screen size
     is a clamp on 5vw, which is not a meaningful unit against paper. */
  h1 { font-size: 18pt; }
  h2 { font-size: 12pt; }
  .dek, .edition-dek { font-size: 12pt; }
  .body, .claim-text, .devlog-summary, .register-title { font-size: 11pt; }
  .claim-digest { font-size: 10pt; }
  .claim-status, .byline, .meta, .provenance, .state-key, .register th, .register td { font-size: 10pt; }
  .skip, .crumbs, .pagenav, .sitefoot, .masthead-strap, #bolt-1 { display: none !important; }
  .masthead { border-bottom: 1px solid var(--rule); }
  .story, .wrap, .sheet, .masthead .wrap, .sitefoot .wrap { max-width: none; padding-left: 0; padding-right: 0; }
  /* Paper has one column. The grid and the rail are a screen affordance, and a
     printed story carries its record below itself rather than beside it. */
  .sheet--story { display: block; }
  /* There is deliberately NO rule here opening the footer's folds for print.
     One was written, on the reasoning that an archive copy should carry the
     refusals rather than a row of closed triangles — and measuring it in
     Chromium showed the reasoning rested on a false premise: .sitefoot is in
     the display:none list above, so the colophon has never printed, before the
     folds or after them. Folding it costs the archive copy nothing, because the
     archive copy never had it. (The attempted rule used ::details-content, and
     for the record it did not open them in Chromium either.) */
  /* Paper carries the URL of the page it is a copy of. Navigation chrome prints
     nothing, so without this the archive copy names neither its own address nor
     a way back; the renderer puts the canonical on the byline as a data
     attribute for exactly this rule to print. */
  .byline[data-canonical]::after { content: "\A" attr(data-canonical); white-space: pre; font-size: 9pt; }
  /* The .meta links carry the explorer leaf link, whose href is the only place the
     full leaf hash lives: the visible text must stay the prefix so it sits
     inside the accessible name (WCAG 2.5.3), so print is where the whole hash
     reaches the archive copy. */
  .body a::after, .claim-receipt a::after, .devlog-entry a::after, .provenance a::after, .meta a::after, .dek a::after {
    content: " <" attr(href) ">"; font-family: var(--font-mono); font-size: 9pt; word-break: break-all;
  }
  .claim { break-inside: avoid; }
  .receipts { break-before: auto; }
}
