explico 0.7.0 → 0.11.0

package/CHANGELOG.md

@@ -14,6 +14,1410 @@ under **Breaking** below; a PATCH never breaks.
 
 ## [Unreleased]
 
+## [0.11.0] - 2026-09-28
+
+### Breaking
+
+- **Figures and diagrams no longer compact.** A figure or a diagram is laid
+  out as LaTeX lays it out, in every state: its picture, then its caption
+  line (docs/plans/figures-and-short-captions.md, Part 1). The caption
+  line's compaction toggle (`.float-caption__toggle`), the `<details>`
+  around a figure's or a diagram's body (`.keyed-figure__details`,
+  `.diagram__details`, `.float-compact`) and
+  `components/disclosure/float-compaction.ts` are gone, and print never
+  notes a compacted figure. To let a reader fold a float away, put it in a
+  collapsible section.
+- **`disclosure.diagrams` is removed.** A course that still sets it fails
+  the build (`normalizeDisclosure` throws) with the edit to make: delete the
+  key. `disclosure.figures` stays, and now sets whether a lab's tools start
+  open — as `defaultOpen` and `rememberState` on a `<Figure>` now do for one
+  figure's tools (below).
+- **`<Diagram defaultOpen>` and `<Diagram rememberState>` are removed.**
+  Either fails `pnpm validate:content` (`dia-removed-prop`), and a diagram
+  that a wrapper component renders fails when it renders.
+- **The manifest schema is now v24**: `disclosure` loses `diagrams` and
+  gains `folds`; `diagnostics.folds` is new (below). A course script that
+  lists the diagnostic groups it blocks on (`compile-manifest.ts`) should
+  add `folds`.
+
+### Added
+
+- **Rule S9** (guide; docs/plans/figures-and-short-captions.md, Part 7): a
+  float's short caption names it, and its long caption goes on from that
+  name instead of restating it; a figure holds no running text, and a lab's
+  instructions go in its tools (`structure-rules.md#s9`). With the short
+  caption printed as the caption line's title, `components.md` now asks
+  for one on every figure, table and diagram.
+- **`FloatIndex.astro`: the "Figures and tables" page**
+  (docs/plans/figures-and-short-captions.md, Part 6) — LaTeX's
+  `\listoffigures` and `\listoftables` in one. It lists every numbered
+  figure, table and diagram with an `id`, by part and chapter (chapters
+  numbered as their sections are), each as its number, linked to its anchor,
+  and its short caption — or its long caption, muted, without one, or the
+  number alone when the manifest has neither. The sidebar's Reference group
+  lists "Figures and tables" when the course has a top-level
+  `content/docs/figures-and-tables.mdx` (`buildSidebar` takes
+  `{ floatIndex }`).
+- **A lab's tools: `<Figure>`'s `tools` slot**
+  (docs/plans/figures-and-short-captions.md, Part 3). The default slot is
+  the picture; the `tools` slot — an instruction line, the sliders and
+  fields, the live equation — renders after the caption line, in a tray of
+  its own (a thin border, no tint) inside a `<details>`. Only the tools
+  fold: a fold button ⌃ / ⌄ ends the caption line (`.float-tool`, "Hide the
+  controls of Figure 2.1.1"), and folded tools leave a "Hidden here: 2
+  sliders, 1 equation" line that unfolds them
+  (`components/figure/figure-tools.ts`). They start open unless the course's
+  `disclosure.figures` or the figure's `defaultOpen` says otherwise, and the
+  reader's choice is remembered per page (`rememberState`). Print and export
+  show the figure as LaTeX would: the tools never print, and
+  `prepareDisclosures` leaves a `details[data-print-omit]` alone. A figure
+  without the slot has no button and no tray. `global.css` sets a lab's
+  tools island in the tray: `.keyed-figure__tools .lab-shell` brings no
+  margin, a `.lab-tools` root drops its last child's, and `.lab-instruction`
+  is the tools' first line, what to do.
+- **The caption line's live end, and `setFigureState`.** A `<Figure>`'s
+  caption line ends with an empty `span.float-caption__state[data-figure-state]`,
+  outside `.float-caption__text`, where a lab writes the case its plot shows
+  — `setFigureState(element, runs)` in `components/figure/figure-state.ts`,
+  with runs of text, italic and subscript as data, never HTML. It prints
+  with the caption. `FloatCaption.astro` takes `live` for it, and renders
+  its button row only when the slot holds a button.
+- **`<Fold>`: collapsible content with no heading, number or marker**
+  (`components/fold/Fold.astro`; docs/plans/figures-and-short-captions.md,
+  Part 2). It folds like a memo — the section chevron, "Hidden here: 1
+  diagram" while folded, the reader's choice remembered per page, opened by a
+  deep link or find-in-page, printed as shown — but it is the plain tier (no
+  frame or tint), puts no letter in the text, has no `[[…]]` key, is not in
+  "On this page" and takes no outline number. Its bar, semibold at
+  body-text size, is its `label` or, without one, the numbers and short
+  captions of the numbered floats inside ("Diagram 2.2.1 Inputs to the
+  launch-angle search", `components/float-name.ts`). A bar that names the
+  floats is their name: their caption lines inside the fold drop the bold
+  short-caption title, which would repeat it. This is how a figure or a diagram becomes
+  collapsible outside a collapsible section, now that floats do not fold by
+  themselves.
+- **`disclosure.folds`** (`{ defaultOpen }`, closed by default) sets whether
+  a fold starts open; `defaultOpen` on one `<Fold>` overrides it, and
+  `rememberState={false}` keeps the default on every visit.
+- **`fold-unnamed`** (error, the keyed-floats invariant;
+  `reference/folds-validate.ts`): a `<Fold>` with no `label` and no numbered
+  `<Figure>`, `<Table>` or `<Diagram>` inside fails `validate:content`, and
+  the component throws on it when it renders.
+- A fold is transparent to numbering, like a memo: the equations and floats
+  in one keep their places in the lesson's sequence. The scans read one list,
+  `TRANSPARENT_COMPONENTS` in `reference/equations.mjs`.
+- **Explanation cards can sit beside the article.** On a window at least
+  72rem wide, a card's new Side button docks it in a side column to the
+  right of the article, level with its trigger's line
+  (docs/plans/hover-card-consistency.md, Part 2; `components/card-side.ts`).
+  For a reader:
+  - Docked cards are 18–23rem wide, never cover the navigation or the "On
+    this page" rail, stack top down without overlapping, and scroll with the
+    page; one taller than the window scrolls inside. Side again, a click on
+    the card's trigger, × or Escape work as on a pinned card; a click on
+    another occurrence of its item moves the card level with that line.
+  - The room comes from sliding the article left, only while cards are
+    docked and only as far as they need, never past the navigation. When
+    there is not enough room even then, the Side button says "Collapse a
+    side panel to make room"; below 72rem it is hidden.
+  - "Keep the article left", at the top of the side column, keeps the
+    article on the left after the last docked card closes. The reader's
+    choice is remembered across pages and visits.
+  - Pointing at another occurrence of a pinned or docked card's item, or at
+    a docked card itself, draws an arrow from the card to that occurrence;
+    it fades 1.5 s after both are left (`components/card-arrow.ts`).
+  - Moving into or out of the side and the article's slide animate in
+    100 ms, and not at all under reduced motion; neither applies in print.
+  - A card with no free spot next to its trigger now goes to the side
+    column at its line, where there is room, before it would cover another
+    card.
+- `HoverPanel.astro` renders the Side button (`data-card-side`) before Pin,
+  and a note line (`data-card-note`) under the header row.
+- **Explanation cards can be dragged.** A grip at the start of every card's
+  header moves the card anywhere between the sidebars, or into the side
+  column (docs/plans/hover-card-consistency.md, Part 3;
+  `components/card-drag.ts`). For a reader:
+  - Only the grip drags, so text in the card stays selectable; a drag starts
+    after 4 px and keeps the card open. Dropped anywhere else, the card
+    stays there: it scrolls with the page, follows its trigger when the text
+    above reflows, and is never dropped over the navigation or the "On this
+    page" rail. Dropped within 32 px of its spot next to its trigger, it
+    goes back there, pinned.
+  - Where the window has a side column, the docking area is tinted during a
+    drag. A card whose left edge comes within 32 px of the article's edge
+    snaps: a dashed line marks the edge, a dashed outline shows where the
+    card will land, and "Release to pin to the side" says what a drop does.
+    Released, it docks at the height it was dropped at, the article sliding
+    first when the column needs room. It lets go again only past 48 px;
+    holding Alt (Option) turns snapping off.
+  - The grip is a button, "Move card": arrow keys move the card 8 px (48 px
+    with Shift) and Home puts it back next to its trigger. Escape during a
+    drag cancels it; the next Escape closes the card.
+  - Pointing at, or clicking, another occurrence of a moved card's item
+    flashes the card and draws its arrow; the card stays where it is. A
+    moved card, like a docked one, hides its Pin button.
+- `HoverPanel.astro` renders the grip (`data-card-grip`) at the start of
+  the header row; a moved card carries `data-card-mode="moved"`.
+- **A page remembers its cards.** The cards a reader keeps (pinned, docked
+  or moved) come back where they were when the reader returns to the page:
+  through a link, Back or a reload, in another tab, or after the browser
+  restarts, including a card opened from inside another. Hovered cards are
+  not kept, and closing a page's last card forgets the page
+  (`components/card-memory.ts`, in local storage).
+- `PreferenceStore` gains an optional `remove(key)`; the browser and memory
+  stores implement it. A store without it still fits the interface.
+
+### Changed
+
+- **A float's short caption shows** (docs/plans/figures-and-short-captions.md,
+  Part 5):
+  - it opens the caption line of a figure, table or diagram as a bold title,
+    `b.float-caption__title`, with a closing period unless it has its own
+    punctuation — "**Sampled flight data.** Position, …". It sits outside
+    `.float-caption__text`, so every reader of the long caption still reads
+    it alone. `FloatCaption.astro` takes `short`;
+  - a folded section's "Hidden here" line names each numbered float with a
+    short caption, number in bold, before the counts of everything else:
+    "Hidden here: **Figure 2.1.1** Projectile trajectory explorer, 2
+    paragraphs" (`section-summary.ts`: `collectHiddenContent`,
+    `hiddenContentParts`; `countHiddenContent` is gone). A `<Fold>` whose bar
+    names its floats keeps counting them;
+  - every chain icon copies a named link: the confirmation says "Link copied
+    · Figure 2.1.1 · Projectile trajectory explorer" (a section's, check's
+    or example set's title, a memo's short caption), and where the browser
+    has `ClipboardItem`, a `text/html` link reading "Figure 2.1.1,
+    Projectile trajectory explorer" or "§ 1.2.1 Velocity over time" goes on
+    the clipboard beside the URL. The confirmation bubble wraps inside a cap
+    instead of running past the column.
+- **A figure's preview card copies its picture as drawn.** A hydrated
+  island in the picture (a lab's plot) becomes plain markup in the copy, so
+  it never hydrates again inside the card, its controls are disabled, and
+  every id in the copy is prefixed, as a diagram's already were. A lab whose
+  plot is not drawn yet — or is on another page, drawn only in the browser —
+  leaves the card to its caption and number. A lab no longer needs
+  `previewable={false}`.
+- **A diagram's widen button ↔ is a boxed button at the end of its caption
+  line**, the `.float-tool` a table's caption has, shown while the graph is
+  wider than the column; `.diagram-toolbar` and `.diagram-expand-button`
+  are gone. `FloatCaption.astro` wraps its default slot in the caption's
+  `.float-tools` row, rendered only when the slot is filled, and names the
+  float in `data-float-name`; a caption line keeps room for its button row
+  only while a button shows.
+- **The side panels sit above explanation cards.** The navigation and the
+  "On this page" rail, open or peeking while collapsed, now cover a card
+  that reaches them, instead of the card covering them; a reader who needs
+  a panel's room collapses it. The site header stays above both. While a
+  table or diagram is expanded, the panels drop back under it as before.
+- **A slimmer site header.** It is 3rem tall at every width (Starlight's
+  default is 3.5rem, and 4rem from 50rem up), with the site title at
+  `--sl-text-xl`, the logo sized to the height, and a 2rem search box.
+  Everything placed under the header follows `--sl-nav-height`; a course
+  that sizes its own header content should check it still fits.
+- **Every explanation card now works the same way.** Notation symbols and
+  `[[key]]` terms, citations, abbreviations, and references to equations,
+  tables, figures, diagrams and sections used to run on four engines with
+  four sets of rules; one card manager (`components/card-manager.ts`) now
+  runs them all (docs/plans/hover-card-consistency.md, Part 1). For a reader:
+  - Hovering or keyboard-focusing a trigger opens its card, and the card
+    stays open while the pointer travels to it, even from a symbol at the
+    top of a tall equation. A symbol crossed on the way no longer takes
+    over; resting on it for a moment does.
+  - A click (or a tap) on any trigger pins its card and a second click
+    closes it. It never navigates: that is the card's own link, now worded
+    "Go to …" ("Go to the full definition", "Go to the reference list",
+    "Go to equation (1.4)"). A reference whose target is already fully on
+    screen still highlights it in place and navigates, and a standalone
+    export's cross-page references stay plain links. Diagram references pin
+    like the others.
+  - Clicks inside a card never close it, so text in a card can be selected
+    and copied; a click elsewhere never closes a pinned card. Every card
+    has a Pin toggle and a × in its header, and a pinned card shows an
+    accent border. Abbreviation cards can be pinned; the citation card's own
+    Pin button is gone.
+  - Every layer shows several cards at once, one per item; opening a card
+    closes only the hovered cards outside its chain, never a pinned one. A
+    symbol inside a card opens its own card as a child of it, across layers.
+  - Cards are placed clear of each other and of the equation their symbol
+    sits in, never at the top of the window, and scroll with the page.
+  - Escape closes one card per press, the newest first, across all layers.
+  - A `[[key]]` term no longer shows the browser's tooltip on top of its
+    card; the `title` stays in the HTML for readers without JavaScript.
+  - The collapsed-content peeks (a memo marker's preview, a collapsed
+    section's) keep their behaviour but close on the cards' terms: after a
+    short grace, not the moment the pointer steps off them.
+- `HoverPanel.astro` keeps its props but renders a `<template>` that each
+  layer clones per card, with a header row (a `heading` slot, the Pin toggle
+  and ×) above its default slot.
+- **A card's "Go to …" link says where it lands.** It ends in ↑ or ↓ for a
+  place on the same page (above or below the middle of the view), → for
+  another page of the course, and ↗ only for a citation's source, the one
+  link that leaves the site; every one used to end in ↗. A float reference
+  to another lesson names it: "Go to equation (1.1.6) in Position and
+  Coordinate Systems →" (`components/card-jump.ts`, `[data-jump-arrow]`).
+- **Smaller headings, one even step apart.** From 50em up h1–h5 are 36, 28,
+  22, 18 and 16 px (Starlight's 42, 35, 29, 24, 18); below it 30, 24, 20,
+  17 and 16 (35, 29, 24, 20, 18). An h2 fitted some 25 characters of a
+  lesson column. The space above a section (`1.5em`), a folded bar and the
+  section chevron follow the same `--sl-text-h*` tokens, set in
+  `global.css`.
+- **Knowledge-check and worked-example headings.** The kind's icon leads
+  the title, and the kind with the number ("KNOWLEDGE CHECK 1.2.1",
+  "EXAMPLE 1.2.1") is a small label in the card's top-right corner, so the
+  title keeps the whole line and the number no longer reads as a section
+  number. The heading's accessible name is unchanged. Markup:
+  `.block-badge` holds the word and `.block-heading__number`, and the icon
+  is `.block-heading__icon`, before `.block-heading__title` (it was
+  `.block-badge__icon`, inside the badge); course CSS on the badge's inside
+  moves with it.
+- **A `[card=meta]` section is unnumbered**, with every heading inside it,
+  like References: logistics — what a chapter builds on, how to read it —
+  is outside the outline, and the sections after it keep their numbers
+  (`sectionNumbers`' `unnumbered` in `reference/sections.mjs`, read with
+  `headingCardTier` from `reference/rehype-heading-anchors.mjs`, in both the
+  manifest's walk and the page's).
+- **A table's buttons sit together at the top right of its caption line.**
+  A widen button ↔, shown when the table is wider than the column, does
+  what the column at the table's right edge does (that column stays, and
+  so do the collapse buttons on both sides of a widened table); the fold
+  button next to it is a chevron, ⌃ / ⌄, where it was ▴ / ▾. Both use the
+  new boxed `.float-tool` style in a `.float-tools` row (`global.css`); the
+  fold toggle keeps `.keyed-table__pagination-toggle` but is no longer a
+  `.table-overflow-expand-btn`.
+- **Less empty space around a lesson.** Accent and meta cards pad 1rem at
+  the top and bottom and up to 1.25rem at the sides (they were up to 1.5rem
+  all round); the first block under a lesson's title adds no margin to the
+  content panel's padding; Previous / Next sit side by side down to a 26rem
+  column, with 1.125rem titles, where they stacked below 36rem; and the
+  3rem Starlight keeps above its "last updated" and edit links is gone when
+  a course shows neither.
+- **The notation panel's help text is inside the panel**, under its title,
+  shown when the panel opens, instead of three lines under the closed one.
+- **A knowledge check's score** is empty until the first answer, then
+  reads "2 of 3 correct" under the questions, so it never pushes down the
+  question just answered. The "3 questions" line above an unanswered check
+  is gone; the list shows the questions.
+
+### Removed
+
+- `components/hover-panel.ts` (`createHoverPanel`, `claimActiveSurface`,
+  `releaseActiveSurface`) and `components/popup-stack.ts`, internal engines
+  outside the public surface in `docs/VERSIONING.md`. A layer registers a
+  `CardSource` with `registerCardSource` instead, and an overlay that must
+  clear the hovered cards calls `closeTransientCards()`.
+
+### Fixed
+
+- A folded section, memo or fold that the browser opens by itself — to show
+  a find-in-page match or a linked fragment inside it — now opens for real:
+  its bar reads open, "Hidden here" goes, and its body shows even after the
+  reader folded it (the fold animation's `max-height: 0` stayed behind). The
+  reader's choice is saved as open, as a click would save it.
+- A heading's chain icon, including a knowledge check's, a worked
+  example's and a memo's, now says "Copy link" on hover, as a float's
+  already did: a click on it puts the link on the clipboard. The title
+  comes from `HeadingAnchorEnhancer.astro` and only where a click copies:
+  on a page without it, or in a browser without the Clipboard API, the icon
+  still only navigates and has no title.
+- On a phone, or any touch screen, a knowledge check's and a worked
+  example's badge icon was drawn over the first letter of its word
+  ("⊞AMPLE"): the heading's hanging indent reached into the badge.
+- A long table's "… N more rows …" label is centred on the part of the table
+  on screen. It was centred on the whole table, columns scrolled out of view
+  included, so on a table wider than the column it sat far to the right.
+- A worked example's closing display equation kept its bottom margin
+  inside the card: `CompactExample.astro`'s scoped `:last-child` rule never
+  matched slotted content.
+- A reference to an equation, table or figure inside a closed memo or a
+  folded section now opens its preview card. The fold clips its content but
+  keeps its box on screen, so the reference counted it as visible: it stayed
+  a plain link with nothing to show, and a click jumped into the closed memo.
+  While the card is open, the fold's bar is marked (`.float-ref-fold-hint`),
+  so the reader sees where the target lives.
+- A figure's preview card shows the figure: an SVG sized by its `viewBox`
+  alone had no width of its own in the card and collapsed to nothing, leaving
+  only the caption. The card's content now takes the card's width, and a
+  figure at least 22rem of it.
+
+## [0.10.0] - 2026-09-27
+
+### Breaking
+
+- **Float numbers are chapter-scoped: `Figure 2.1` is now `Figure 2.2.1`.**
+  A display equation, `<Table>`, `<Figure>`, `<Diagram>` and knowledge check
+  is numbered `‹part›.‹chapter›.‹n›` and every kind restarts in each chapter,
+  the LaTeX book convention — `2.1` would read as "part 2, chapter 1" once
+  sections carry `part.chapter.section` numbers. `[[…]]` references need no
+  edit: they print from the manifest. What changes for a course is every
+  number a reader sees, the positional anchor of an *unkeyed* float
+  (`#eq-2-4` → `#eq-2-2-4`), and any e2e test or prose that quotes a number.
+  `numbering.floats: "part"` in `course.settings.json` keeps the old
+  `‹part›.‹n›` scheme.
+- **The manifest schema is now v20**: `numbering` carries the course's
+  resolved numbering settings; `lessons[].headings` lists every top-level
+  heading with its anchor (`slug`), `text`, `level` and, when numbered, its
+  `number`; `lessons[].numbering` gains `prefix`, and under the default chapter
+  scope its per-kind counts, which used to carry a part's running total, are
+  all 0. `remarkNotation` reads all of it off the manifest (`sections` and
+  `sectionNumbering` join its options), gives each heading its anchor and
+  `data-sec-number`, and fails the build when a page's top-level headings are
+  not the ones the manifest numbered.
+- **Six overlapping rules are folded into four; their IDs are retired.** Rules
+  N1 (the normal distribution is `\mathcal{N}`), N6 (probability is
+  `\mathbb{P}`) and N7 (the differential is `\mathrm{d}`) are now lines in
+  **rule N2**, which becomes "a reserved spelling means only what it is
+  reserved for, and every other styled letter is a symbol of its own" and
+  carries the table as a course setting, `rules.N2.reserved` (default: the four
+  number systems, `\mathbb{P}`, `\mathcal{N}(\mu, \sigma^2)`, `\mathrm{d}`)
+  — so a course edits its conventions in `course.settings.json` instead of
+  overriding a rule page, and an agent reads the effective table off
+  `build/rules-in-effect.md`. Rule N3 (write a multi-letter label as
+  `\mathrm{…}`) is folded into **rule N10**, which becomes "a multi-letter
+  roman label is written `\mathrm{…}`, and it is universal or it is explained"
+  and is now `partial`: the format half never had a check of its own — rule
+  N4's gate reports a bare `PV` as unresolved one-letter symbols. Rule N16
+  (alternate delimiter shapes for stylistic nesting) is folded into **rule
+  N17**, which becomes "a delimiter's shape carries its meaning and never
+  changes to show nesting: a nest is sized by the engine", also `partial`. The
+  preference for alternating shapes is **reversed**, not just moved: this
+  engine sizes a nest automatically, and a `[` inside a grouping nest reads as
+  an interval, an expectation or a matrix first. N16's "in AI-generated
+  content" scope is gone with it — a rule holds for whoever typed the page.
+  Rule C4 (a release moves `[Unreleased]` and bumps `about.version` together)
+  is folded into **rule C3**, whose `knowledge-changelog-missing` was already
+  the check that fired on a half-finished release; C3 is now `partial`. Each
+  retired ID keeps its number so an older commit message still resolves, but
+  nothing else: `RuleEntry.retired` is **gone**, and a retired rule leaves the
+  catalog for a new compact list (`RETIRED`, read by `retiredRules()` /
+  `retiredRule(id)`) holding only `{ id, title, date, into?, why }`. It has no
+  rule page, no row in the index, no entry in the settings schema and no line on
+  `build/rules-in-effect.md`, so an author or an agent that is drafting never
+  reads it; the one place it is written out is the generated table on the new
+  `docs/authoring/retired.md`, which is where a migration guide links.
+  `gen-rules.mjs` writes and `--check`s that table alongside the index. A course
+  with `rules.N1` / `rules.N3` / `rules.N6` / `rules.N7` / `rules.N16` /
+  `rules.C4` in its settings still gets a `config-retired-rule` warning — now
+  naming the successor and the date — and should move the block to the surviving
+  rule (only N2 takes settings).
+- **Rule N9 catches a unit written as a word.** "a time of 4 seconds", "2
+  meters per second squared", "30 degrees above the horizontal" and
+  "$x = 3$ meters" now fail `pnpm validate:content` with the new code
+  `spelled-unit` (owned by rule N9), in lesson bodies and assessment
+  `prompt` / `explanation`; the message gives the math to write instead
+  (`$4\ \text{s}$`, `$2\ \text{m/s}^{2}$`, `$30^{\circ}$`,
+  `$x = 3\ \text{m}$`). The unit words live in `src/reference/unit-words.ts`
+  (SI-style units and their common prefixes; not calendar time or
+  currency). Flagged: a unit word after a number (digits or words, plain or
+  typeset), before or after `per`, or with `square` / `cubic` / `squared` /
+  `cubed`. A unit named on its own ("measured in meters"), "degrees of
+  freedom" and `second-order` pass. Rule N9's old carve-out for a
+  spelled-out unit in flowing prose is gone. A course with a violation
+  rewrites it, waives a defining sentence with
+  `{/* explico-allow N9: reason */}`, or lists unit words it keeps as words
+  in the new `rules.N9.allow` setting. `proseOnly` takes
+  `{ keepMath: true }`; `gateProseNotation` / `gateProseNotationInAssessments`
+  take `{ allowSpelledUnits }`.
+- **Rule N12 is build-enforced: math never ends in the sentence's own
+  punctuation.** `gate-math-punctuation.ts` (`gateMathPunctuation`,
+  `gateMathPunctuationInAssessments`) reads every `$…$` / `$$…$$` span in a
+  lesson body and in assessment `prompt` / `explanation`. It fails
+  `pnpm validate:content` with `math-trailing-punctuation` when a `.`, `,`,
+  `;` or `:` is the last visible thing in the span, or in a row before a
+  `\\`. It looks through spacing, `\label{…}` / `\tag{…}`, row breaks,
+  `\end{…}` and `\right.`, and into a closing `\text{…}` (`5\ \text{m,}`). A
+  trailing decimal point (`5.`) and a typed `...` fail too; rule N12 no
+  longer lists a decimal point as an exception. An upright dotted
+  abbreviation that is notation passes: the shipped `a.e.`, `a.s.`, `c.c.`,
+  `const.`, `h.c.`, `i.i.d.`, edited with the new `rules.N12.allow` /
+  `rules.N12.deny` settings. A course with a violation fixes the math, waives
+  the place with `{/* explico-allow N12: reason */}`, or turns rule N12 off
+  in `rules`. See `docs/authoring/notation.md#n12`.
+- **A font-styled letter is its own symbol (rule N4).** `\mathbf{x}`,
+  `\boldsymbol{\beta}`, `\bm{x}`, `\mathcal{N}`, `\mathscr{L}`,
+  `\mathfrak{g}`, `\mathbb{E}`, `\mathsf{x}` and `\mathtt{x}` no longer
+  borrow the notation card of the plain letter on the page, and a styled
+  base-library letter (`\mathbf{e}`, `\boldsymbol{\pi}`) no longer passes as
+  Euler's number or π. Each needs its own entry (`latex: \mathbf{x}`) or an
+  `\explain{key}{\mathbf{x}}` wrap, or rule N4's completeness gate fails with
+  `unresolved-glyph` — in lesson bodies, notation formulas, assessments and
+  labs alike; the message says the styled letter is a different symbol.
+  `\mathit` / `\mathnormal` still share the plain letter's card, and
+  `\mathbb{N,Z,R,C}` stay reserved. The wrap for `\boldsymbol`, `\bm`,
+  `\bold`, `\Bbb`, `\frak`, `\mathsf`, `\mathtt` and `\mathnormal` now
+  lands around the command (`\explain{k}{\boldsymbol{\beta}}`), not inside
+  it.
+
+- **Every float is named by one caption pair: a long `caption` and an
+  optional `short` caption** (LaTeX's `\caption[short]{long}`). The other
+  name props are removed outright, with no alias period; each now fails the
+  build with the edit to make:
+  - `<Figure title="…">` → `short="…"` (the title bar is gone; the long
+    `caption` stays required).
+  - `<Diagram label="…">` → `caption="…"`, now shown below the graph; add
+    `short` for a long caption. A `<Diagram title>` — never a prop, but the
+    rule S4 example used it — fails the same way.
+  - `<Memo title="…" description="…">` → `caption="…"` (required: the memo's
+    bar and the head of its preview), plus `short="…"` (optional: the
+    marker's tooltip). A memo with no title is fine; one with no caption
+    fails.
+  - `<CompactExamples summary="…">` → `short="…"`.
+
+  `pnpm validate:content` reports a `<Figure title>` as `fig-removed-prop`
+  and a `<Diagram label>` / `title` as `dia-removed-prop` (errors, owned by
+  the keyed-floats invariant; `tab-removed-prop` is registered for the same
+  shared check); `remarkMemo` fails a `<Memo title>` / `description`; each
+  component throws on its removed prop when it renders.
+- **A figure and a diagram put their number in a caption line below the
+  body, and compacting keeps that line.** The line reads `Figure 2.2.1`
+  (a link to the figure), a chain icon, and the long caption; the compaction
+  toggle sits beside it (in the gutter on a wide screen, at the start of the
+  line on a narrow or touch one), and a compacted float hides only its body —
+  its number, anchor and caption stay (a collapsed figure used to hide its
+  number). A diagram's number leaves its title bar for the same line, and its
+  widen control moves to the end of it; the curriculum map's competency graph
+  gets the same caption line. The float's `<details>` keeps a
+  native `<summary>` that shows only under `(scripting: none)`. Selectors that
+  moved: `.keyed-figure__titlebar`, `.keyed-figure__summary`,
+  `.keyed-figure__title-anchor`, `.diagram__titlebar`, `.diagram__summary`
+  and `.diagram__title-anchor` are gone; `.diagram__number` is now a link;
+  the caption line is `figcaption.float-caption` with `.float-caption__toggle`,
+  `.float-caption__number`, `.float-caption__anchor` and `.float-caption__text`
+  (`src/components/figure/FloatCaption.astro`,
+  `src/components/disclosure/float-compaction.ts`).
+- **A memo's marker is a superscript letter**, `a`, `b`, … per page, in
+  italics — the footnote convention — where it was a bracketed `[1]` that read
+  as a citation. The same letter is the memo's permalink on its bar;
+  `data-memo-number` and the `number` prop `remarkMemo` injects carry the
+  letter (`memoLetter(n)` is exported from `remark-memo.mjs`).
+- **The manifest schema is now v21**: `lessons[].equations` / `.tables` /
+  `.figures` / `.diagrams` entries, and the `labels` of `equations` /
+  `tables` / `figures` / `diagrams`, carry the float's `short` caption and,
+  for a `<Table>` / `<Figure>` / `<Diagram>`, its long `caption`, each when
+  the source states it as a literal (`ManifestLessonFloat`).
+- **Rule S1 measures the short caption, not a title.** It caps every
+  heading, the `short` prop of a `Figure`, `Diagram`, `Table`, `Memo` and
+  `CompactExamples`, a display equation's `\caption{…}`, and a `ShortNote`'s
+  `title`; a long `caption` is never measured. A course whose `Figure title`
+  passed S1 moves it to `short`, where it is measured the same way.
+
+- **Every collapse default is one `disclosure` block: `CourseConfig.disclosure`
+  replaces `CourseConfig.disclosureDefaults`.** It takes the course settings'
+  `disclosure` block in its own shape — `sections` / `subsections` /
+  `knowledgeChecks` as `{ collapsible, defaultOpen }`, `notation` /
+  `references` / `memos` / `figures` / `diagrams` / `workedExamples` as
+  `{ defaultOpen }`, `tables` as `{ truncateAfter }` — and
+  `normalizeDisclosure` (with `DISCLOSURE_DEFAULTS`) replaces
+  `normalizeDisclosureDefaults`. A course passes the block straight through
+  (`course.config.ts` no longer splits it off) and reads it back in
+  `astro.config.mjs` for `rehypeHeadingAnchors` (`defaultCollapsible:
+  courseConfig.disclosure`) and `remarkCitation` (`defaultOpen`); the old
+  `disclosureDefaults: { notation, references }` mapping goes. **The manifest
+  schema is now v22**: `manifest.disclosure` (`NormalizedDisclosure`, every
+  default applied) replaces `manifest.disclosureDefaults`.
+- **A `<Memo>` is a `######`-rank section.** Its bar is an `<h6>` (the
+  `#memo-…` anchor, `role="none"`, carrying the caption and, as generated
+  content, the letter) in a heading wrapper `CollapsibleSections` folds like
+  any section — gutter chevron, hover peek, "Hidden here: …" line, animation,
+  persistence under `section:memo-…`, a chain icon that copies "Link copied ·
+  Memo a". `.memo-block` is now the frame (it was the `<details>`); the
+  `<details>`, `.memo-block__summary`, the letter link `[data-memo-self-link]`
+  and the separate chain link `[data-memo-anchor-link]` are gone. The marker
+  in the prose still opens it, goes there and folds it again. It is not a
+  heading of the lesson: not in the outline, "On this page" or the heading
+  rules.
+
+- **A knowledge check and a set of worked examples draw their own heading;
+  the author writes only the topic.** Both render the new `BlockHeading.astro`
+  `<h2>`: the kind's badge (an icon and "Knowledge check" or "Example"), the
+  number, then the author's title — the assessment file's `title`, the set's
+  `short`. A check's heading was `Knowledge check 1.2.1 — ‹title›` in one
+  span (`.assessment-heading-number` is gone), so an assessment title that
+  repeats the kind ("Velocity check") now reads twice: write the topic alone.
+  **`<CompactExamples>` requires `id` and `short`**: `short` no longer
+  defaults to "Worked examples", and a set without either fails
+  `pnpm validate:content` (`ex-missing-prop`) and its own render, as
+  `summary` does (`ex-removed-prop`, now reported at validation too).
+  **A set is a `##` section**, folded by `CollapsibleSections` like a memo —
+  chevron, peek, "Hidden here: 2 worked examples", print-as-shown — instead of
+  its own `<details>`: `details.compact-examples`,
+  `.compact-examples__summary` and `.compact-examples__title` are gone
+  (`<compact-examples class="compact-examples">` is the accent card, the
+  heading is `#ex-‹id›`), and `hint` has no default ("Open and choose an
+  example." described the old disclosure; the folded bar now says what is
+  inside). Its heading is part of the outline:
+  it ends the section before it, and rule S6 and rule S7 read it as a `##`
+  (rule S7 already counted it as a heading), so a `###` → set → `####` is now
+  a `heading-skip`. `ex-` joins the reserved reference prefixes: a notation
+  key written `[[ex-…]]` is read as a set reference.
+- **The manifest schema is now v23**: `examples` (the `<CompactExamples>`
+  number table, same shape as `figures`), `lessons[].examples`
+  (`ManifestLessonFloat`, `short` the title), `lessons[].numbering.examples`,
+  `diagnostics.examples`; `lessons[].knowledgeChecks` entries gain `title`;
+  `lessons[].titledBlocks` (`ManifestTitledBlock`: each check and set with its
+  heading's `anchor`, `title` and the top-level heading it follows, `after`);
+  and `blockLabels`. A course's own `compile-manifest.ts` that lists the
+  diagnostics groups must add `examples`, or an `ex-…` error does not fail
+  `validate:content` (the page build still fails on it).
+
+### Added
+
+- **Outline numbering.** A lesson's top-level headings are numbered
+  `‹part›.‹chapter›.‹section›[.‹subsection›…]` — `1.1.2`, `1.1.2.1` — down to
+  `####`, printed before the title on a wide screen and in print, and on a
+  collapsed section's bar at every width; an open section on a narrow screen
+  shows none. The number is CSS generated content from `data-sec-number`, so
+  the heading's text, its anchor and the "On this page" entry are unchanged.
+  Configured by the new `numbering` block in `course.settings.json`
+  (`CourseConfig.numbering`): `sections.show` (default `true`),
+  `sections.depth` (`2`–`6`, default `4`), `floats` (`"chapter"`, the
+  default, or `"part"`) and `aliases` (default `true`); a course's settings
+  schema needs the block to offer it in the form editor
+  (`playground/content/course.settings.schema.json` has it). A heading
+  inside a component (`<Memo>`, `<CompactExample>`) is not part of the
+  outline. The manifest decides each top-level heading's anchor — the same
+  slug Astro gives a plain-text heading — and the page takes it from there,
+  so a heading with inline math now gets a slug from its source (`$R$` → `r`)
+  instead of from KaTeX's output.
+- **`[[sec-slug]]` cites a section**, and `[[lesson/slug#sec-slug]]` one on
+  another page: it prints `§ 1.1.2` (the title in quotes when the heading has
+  no number, or the course hides them) and gets the float-reference hover card,
+  with the section's title and first paragraph. `sec-` joins the reserved
+  reference prefixes. A reference to no top-level heading is a
+  `sec-ref-resolves` error (owned by the `keyed-floats` invariant, reported in
+  `diagnostics.math`), and the build fails on it too. `content context
+  --json` lists the lesson's `sections` — anchor, text, level and number — so
+  a drafter can cite one without deriving its slug.
+- **Number aliases.** With `numbering.aliases` on, a fragment a reader types in
+  number form — `#sec-1.1.2`, `#fig-2.2.1`, `#eq-1.1.4`, `#tab-…`, `#dia-…`,
+  `#check-…` — lands on the element that shows that number on the page, and
+  the address bar switches to its named anchor (`KeyedFloatEnhancer` takes an
+  `aliases` prop; `LessonFooter` passes the manifest's). Inbound only: the
+  site links and copies named anchors alone. A knowledge check's heading
+  carries `data-check-number` for this.
+- **A heading's chain icon copies its link.** One click puts the page URL with
+  the heading's named anchor on the clipboard (the page's canonical URL when it
+  declares one) and shows "Link copied · § 1.1.2" under the title, announced
+  through a polite live region; the click still navigates and highlights, and
+  a refused clipboard leaves exactly that. On a narrow screen the icon is
+  always visible, smaller and muted, since it is where the section number
+  surfaces there.
+- **Container tiers.** `explico/styles/surfaces.css` defines the style
+  primitives once — `--ex-surface-*` (`none`, `tint-neutral`,
+  `tint-accent`), `--ex-edge-*` (a 1px border, a 3px left rule),
+  `--ex-depth-*` (`flat`, `raised`) and one `--ex-radius-*` per boxed tier —
+  for both themes, and composes them into `.ex-tier-meta` (grey, bordered,
+  flat), `.ex-tier-accent` (accent tint, bordered, shadowed) and
+  `.ex-tier-aside` (a left rule; `.ex-tier-aside--tinted` adds the accent
+  tint). No class is the **plain** tier. `global.css` imports it, so a
+  course's `customCss` needs no second entry. Tiers are fixed per kind; there
+  is no setting.
+- **`[card]` / `[card=meta]` heading markers.** Appended to a heading like
+  `[collapsed]`, they put the whole section — heading and body, down to the
+  next heading of the same or a higher rank — in one accent or meta card. A
+  heading takes one marker of each kind, in either order
+  (`### Explore the range [collapsed] [card]`). `rehype-heading-anchors.mjs`
+  strips them (from the text, the anchor and the manifest's slug alike) and
+  writes `data-card="accent"|"meta"` on the heading wrapper;
+  `CollapsibleSections.astro` draws the card, after collapsing the section
+  when it is collapsible too. Inside a card, the collapse chevron sits in the
+  card's padding (`--ex-section-gutter`).
+- **Starlight asides render in an explico course: `remarkAsides`**
+  (`explico/reference/remark-asides.mjs`). Starlight turns `:::note` /
+  `:::tip` / `:::caution` / `:::danger` into asides only under its own
+  `src/content/docs/`, so in a course's `content/docs/` they rendered as a
+  bare `<div>`. Add `remarkAsides` last in `markdown.remarkPlugins`: it hands
+  each one to Starlight's `<Aside>` (imported into the page), so Starlight
+  still draws the icon, the translated default title and its check of a named
+  `{icon="…"}`. In a `.md` lesson, which has no JSX, the aside is written out
+  with no icon. `icon=""` — on a directive or on an `<Aside>` — drops the
+  icon, which Starlight itself cannot do.
+- **Rule S8 (guide): prefer `<Memo>` over a Starlight aside** when the
+  content needs an anchor, a caption or collapsing. Review-only; on by
+  default (`rules.S8`).
+- **Rules S6 and S7: heading discipline**, both errors, both new in
+  `src/reference/gate-heading-structure.ts` (`gateHeadingStructure`). Rule S6
+  (`heading-skip`): headings descend one level at a time — a lesson body
+  starts at `##` (the page title is its one `#`, so a `#` in the body fails),
+  and `##` → `####` fails; going back up is free. Rule S7
+  (`heading-adjacent`): a heading is followed by body content, never directly
+  by another heading, and `<AssessmentSet />` and `<CompactExamples>` count as
+  headings since each opens with a title of its own — so `## Try it` straight
+  above a worked-example set fails. Both read a lesson's outline, the same
+  top-level headings the section numbers count (`scanOutlineBlocks`, new in
+  `explico/reference/sections.mjs`); a heading inside a component, and a
+  memo's bar, are not in it. Both are waivable at one place
+  (`{/* explico-allow S7: reason */}` above the heading) and switchable
+  (`rules.S6.enabled`, `rules.S7.enabled`). `docs/authoring/structure.md`
+  gains "Structure from the bottom up": run-in labels and description lists,
+  not deeper headings, for parallel items near the bottom of the outline.
+- **Kind badges** (docs/plans/titles-and-containers.md Q11). A knowledge
+  check's and a worked-example set's heading opens with a badge — the kind's
+  icon and word, small caps on the accent tint — then the number, then the
+  author's topic, all one line of text that wraps word by word. The new
+  `blockLabels` setting (`CourseConfig.blockLabels`, `"icon-word"` by default,
+  or `"icon"` for the icon alone with the word kept for a screen reader)
+  chooses the form; `normalizeBlockLabels` and `BLOCK_LABELS_DEFAULT` are
+  exported from `explico/compiler/course-config`.
+- **Worked-example sets are numbered and citable.** A `<CompactExamples
+  id="…">` is `Example ‹part›.‹chapter›.‹n›`, counted on its own like every
+  float kind (`numbering.floats` applies), anchored `#ex-‹id›`. `[[ex-id]]` and
+  `[[lesson/slug#ex-id]]` print `Example 1.1.1` and get the reference hover
+  card — the set's title and its examples' names. `remarkNotation` numbers
+  the set and passes `number` / `anchorId` to the component, and fails the
+  page on an unresolved reference; `validateExamples`
+  (`explico/reference/examples-validate`) reports `ex-invalid-key`,
+  `ex-duplicate-key`, `ex-ref-resolves`, `ex-key-unused` (info),
+  `ex-removed-prop` and `ex-missing-prop`, owned by the `keyed-floats`
+  invariant. The number-form alias `#ex-1.1.1` resolves, the chain icon says
+  "Link copied · Example 1.1.1", `content status` counts example sets and
+  `content context --json` lists a lesson's `examples`.
+- **"On this page" lists a knowledge check and a worked-example set** (audit
+  §8.7) where each stands, by its title — as a section is listed without its
+  number — with the badge's icon before it: `LayoutPageSidebar.astro` rebuilds
+  Starlight's list with the manifest's `titledBlocks` in it
+  (`tocWithTitledBlocks` in `explico/components/block-heading`), for the
+  desktop and the mobile list alike, and marks those entries
+  `data-block-kind` for the icon. Starlight's scroll-spy marks them like any
+  heading.
+- **`[[check-…]]` previews its check** like every other reference: a hover
+  card with the check's title and its number of questions, a highlight when
+  the check is already on screen, and a pinned card instead of a jump when it
+  is not (the card's link goes there). It is styled like `[[sec-…]]` now.
+- **A course can add rules of its own** — `courseRules` in
+  `course.settings.json`, a list the settings form editor adds to and removes
+  from. IDs are `X1`…`X99`: the `X` area is permanently reserved for a course,
+  so the engine never ships one and no upgrade collides with a classroom's own
+  numbering. A rule is `{ id, title, summary?, elements?, enabled?, severity?,
+  forbid?, unchecked?, doc? }`. With a `forbid` pattern it is **enforced**: each
+  match is a diagnostic carrying the rule's ID as its code
+  (`[X1] content/docs/…:42: …`), at `severity` `error` (fails
+  `pnpm validate:content`) or `warning`. Patterns are matched against the same
+  "is this really prose" surface rule N9 scans — code, math, `[[key]]`,
+  `import` lines, JSX tags and MDX comments blanked first — in one of three
+  scopes: `paragraph` (the default; a block between blank lines, right-trimmed,
+  so `^`/`$` are its ends), `prose` (the whole lesson body) or `heading`.
+  Without a pattern it is a **guide**, listed for an author or an agent to
+  follow; `enabled: false` parks it in the page's "Off" list, where an agent
+  neither applies nor flags it. A course rule is waivable at one place like any
+  other located rule (`{/* explico-allow X1: reason */}`), and a stale waiver
+  still warns. A bad definition fails the build with the setting's path (a
+  regular expression that does not compile or that matches the empty string, an
+  ID outside `X`, a duplicate ID, an unknown key, a `severity` with no pattern
+  to report). `rules.X1` is refused with a message pointing at `courseRules`.
+  Implemented by `explico/rules/course-rules` (`resolveCourseRules`,
+  `courseRuleEntry`, `courseRulesJsonSchema`) and
+  `explico/reference/gate-course-rules` (`gateCourseRules`); `pnpm build` writes
+  `dist/rules/course-rules.schema.json`, which a course points at with
+  `"courseRules": { "$ref": "../node_modules/explico/dist/rules/course-rules.schema.json" }`.
+  See `docs/authoring/README.md` § Rules of your own.
+- **The rule catalog as data** — `explico/rules/catalog` exports `CATALOG`
+  (one entry per authoring rule and per always-on invariant), `ownerOf(code)`,
+  `ruleById`, `enforcementOf`. Every diagnostic code the engine emits now has
+  exactly one owning entry; `tests/rules/catalog.test.ts` scans `src/` and
+  fails on a code no entry claims, or one claimed twice. `content diagnostics`
+  / `content warnings` / `content check` carry the owner as `rule` in `--json`
+  and prefix the console line with it for a lettered rule
+  (`[N9 prose-notation] …`). Six rules name checks that already ran but had
+  no rule page: rule S3 (`raw-table-markdown`, `raw-table-html`), rule S4
+  (`diagram-unkeyed`, `diagram-nested`), rule S5
+  (`convention-single-definition`), rule N19 (`notation-units`,
+  `units-vocab`), rule N20 (`notation-source-locator`), rule N21
+  (`gloss-name-shape`). Design: `docs/plans/rule-catalog.md`.
+- **Per-place waivers.** `{/* explico-allow <ID>[, <ID>]: <reason> */}` on
+  its own line waives the named rules for the next block (to the next blank
+  line). A rule whose checks all report a line — rule N9, rule N14, rule S1,
+  rule N17 — has the covered findings dropped; a guide rule's waiver is the
+  recorded reason and nothing more. `waiver-malformed` / `waiver-invalid`
+  (a locked rule, an invariant, a corpus-level rule, an unknown ID) are
+  errors; `waiver-unused` (a checked rule's waiver that silenced nothing) is
+  a warning; all three are `manifest.diagnostics.waivers`, owned by the new
+  `waivers` invariant (`explico/rules/waivers`: `collectWaivers`,
+  `applyWaivers`, `isWaivable`). The rules-in-effect page marks each waivable
+  rule and shows the syntax. `proseOnly` (rule N9 / rule N14 scans) now blanks
+  MDX comments, so a waiver's reason may quote the text it excuses. A course's
+  own `scripts/compile-manifest.ts` must print `diagnostics.config` and
+  `diagnostics.waivers` and fail on the latter's errors — the playground's
+  shows the two loops — and can print math findings through `diagnosticLine`
+  to get the `[N9 prose-notation]` rule prefix.
+- **The rules-in-effect page and `content rules`.** `pnpm validate:content`
+  writes `build/rules-in-effect.md` (git-ignored, regenerated every run): the
+  rules this course has on, grouped by element, each with its enforcement,
+  diagnostic codes, settings in effect and a one-line summary, then the
+  always-on invariants, the rules turned off, and the locked ones — about a
+  hundred lines, so an agent reads it instead of the rule set. `pnpm content
+  rules [--element <e>[,<e>]] [--enforcement script|partial|guide|locked]
+  [--json]` prints the same page filtered (`explico/rules/in-effect`:
+  `renderRulesInEffect`, `rulesInEffect`, `writeRulesInEffect`;
+  `explico/compiler/cli`: `contentRules`, `parseRulesFilter`).
+  `docs/authoring/agents.md` now sends an agent there first and no longer
+  restates the `P` rules.
+- **A rule turned off stops running.** With `rules.<ID>.enabled: false`
+  the manifest withholds every diagnostic that rule owns (its codes, per the
+  catalog) from every `diagnostics` group, and the whole-rule gates (rule N9,
+  rule N14, rule S1, rule S2) are not run at all; `remarkNotation` honours
+  rule S3 / rule S4 for its render-time raw-float warnings. Switchable:
+  N5, N8, N9, N10, N14, N17, N19, N20, N21, S1–S7, C3 — and every guide
+  rule, which then leaves the rules-in-effect page. `manifest.rules`
+  publishes `disabled` and each rule's effective settings.
+  `tests/rules/one-rule-off.test.ts` holds each switch to exactly its own
+  codes. `MathGateDiagnostic.code` is now required.
+- **Per-rule settings: `CourseConfig.rules`.** One block per rule ID, holding
+  only what differs from the defaults — `{ "P5": { "enabled": false }, "S1":
+  { "maxLength": 72 }, "N14": { "allow": ["GDP"] } }`. `resolveRules`
+  (`explico/rules/settings`) validates it against the catalog at the start
+  of `compileManifest` and fails the build on an unknown rule or key, a
+  value outside its spec, or `enabled: false` on a locked rule (N4, N13,
+  N15). Rule S1 gains `maxLength` (default 65), rule S2 `bridgeMinWords` /
+  `bridgeMaxWords` / `scopeMinWords` / `scopeMaxWords` (30 / 150), rule V5
+  `seeds` (10), rule V6 `minLabels` (3); rules N8, N10, N14 keep their
+  `allow` / `deny` lists, now under `rules.N8` / `rules.N10` / `rules.N14`.
+  `pnpm build` writes `dist/rules/rules.schema.json` — the `rules` block as
+  JSON Schema, properties ordered by element with an `x-element` hint — so a
+  course's `course.settings.schema.json` just points at it:
+  `"rules": { "$ref": "../node_modules/explico/dist/rules/rules.schema.json" }`.
+  The settings form editor (`tools/vscode-settings-editor/`) inlines such a
+  file `$ref` and groups the rules by element. `enabled: false` is recorded
+  now and takes effect in the next change (the gates); the manifest schema
+  is now v18 (`diagnostics.config`).
+- **The rule index is generated.** `scripts/agent/gen-rules.mjs` writes the
+  table in `docs/authoring/README.md` from the catalog — each row now shows
+  the rule's element(s), its settings defaults, and its enforcement with the
+  emitting module and function linked — plus an "Always enforced
+  (invariants)" table. `--check` (in `scripts/agent/verify` and CI) fails on
+  a stale table, a missing `## <ID>` heading, a bold title that differs from
+  the catalog, or an `_Enforcement._` paragraph that does not name every
+  module the catalog lists for that rule. Rules N1, N2, N3, N6, N7 are
+  now stated as Review-only: their earlier "build-enforced" claim rested on
+  the completeness gate (rule N4), which checks that a glyph resolves, not
+  which spelling was chosen.
+- **A part can have its own page.** `content/docs/<dir>/index.mdx` is now a
+  recognised, first-class page: the URL a part's directory already implies
+  (`/<part>/`), which until now was a 404 that nothing linked and nothing
+  could link. It is not a chapter — `isLessonSlug` has always excluded
+  `<dir>/index`, so the page teaches nothing, numbers nothing, and never
+  enters a track or the curriculum graph — and it is opt-in one part at a
+  time. See `docs/authoring/structure.md` § Part pages.
+- **`<PartOverview>`** (`explico/components/PartOverview.astro`) renders that
+  page's body from the manifest: the part's chapters in reading order with
+  their descriptions and float counts, beside a rail carrying the competency
+  outcomes the part delivers and the parts it builds on and leads to. The
+  authored `chain` prop states the part's argument, one step per line, because
+  no manifest field knows why one chapter follows another; `rail={false}`
+  keeps the reading list alone.
+- **The sidebar reaches a part page two ways.** A part whose overview page
+  exists gains an `Overview` row leading its group — in the served HTML, so it
+  is keyboard-operable, crawlable and present without JavaScript, and marked
+  `explico-part-overview` so it carries its own icon (two stacked sheets,
+  filled against a chapter's outlined page in compact mode, and hollowed out
+  again on the part's own page where the row is already an accent tile).
+  `LayoutSidebar.astro` then adds a `»` control at the end of the group
+  header, so the label keeps the collapse it already owned and neither gesture
+  is retrained.
+- **`studyMinutes`** is an optional lesson frontmatter field — `40`, or
+  `[30, 40]`. `manifest.lessons[].studyMinutes` carries it in one shape and
+  `manifest.parts[].studyMinutes` totals a part whose chapters *all* state
+  one, so a half-annotated course reports no misleading sum. It is the
+  reader-facing half of the long-dropped `estimatedMinutes`, back now that
+  part and course pages have somewhere to add it up.
+- **`<CourseContents>`** (`explico/components/CourseContents.astro`) lists
+  every part and chapter for a landing page, each part heading linking its
+  overview page, with per-part and whole-course study totals. A hero that
+  links only chapter one no longer hides the rest of the course, and the list
+  is the manifest's, so it cannot go stale.
+- **Both rails show how far the reader has come.** The navigation rail
+  colours the line beside every chapter already passed — reading order is the
+  sidebar's own — and marks a part whole when all of its chapters are behind
+  the reader; in compact mode the chapter tiles carry it instead. The contents
+  rail does the same down one page, following Starlight's scroll-spy. Without
+  JavaScript both are simply uncoloured.
+
+- **`LayoutPageTitle.astro`** puts the part's name, linked, above every
+  chapter title — the one route to a part page that does not depend on the
+  sidebar, and the answer to "where am I" for a reader who arrived from a
+  search result. Wire it as Starlight's `PageTitle` component override.
+- **`CoursePart.overviewLabel`** renames that sidebar row per part, for a
+  course where `Overview` reads wrong.
+- **Rule N18: a multi-step derivation is one aligned chain.** One step per
+  line in an `aligned` block, `&` directly before each relation so the signs
+  stand in one column, and any justification at the end of its step's line
+  after `\qquad`, as `\text{…}`. A justification names the fact it uses;
+  another display equation is linked with `[[eq-key]]` in the sentence that
+  introduces the chain, because math cannot carry a link and rule N5 forbids
+  hand-typed numbers. Review-only (`docs/authoring/notation.md#n18`).
+- **Rule V6: every quantitative axis shows at least three labelled values.**
+  One value pins a point and two cannot tell a linear axis from a log one;
+  three show the offset, the unit, and the spacing. Covers hand-drawn SVG,
+  Observable Plot, islands, and printed pgfplots figures; a categorical axis
+  shows its categories, and a figure without axes is exempt. Review-only
+  (`docs/authoring/visualizations.md#v6`). The playground's
+  polynomial-shape memo figure now labels both axes.
+- **Prose rules P2–P9: controlled scientific English, adapted from
+  ASD-STE100.** A lesson's main text puts clarity before variety and
+  entertainment. `prose.md` now defines _main text_ (everything a reader must
+  read) and _aside_ (a `<ShortNote>` or `<Memo>` body), and adds rule P2 (one
+  canonical term per concept, repeated; a notation entry's `label` is that
+  term), rule P3 (one meaning per term; no technical term in its everyday
+  sense), rule P4 (use the established term and define it where the argument
+  first needs it), rule P5 (literal main text: no idioms, metaphors,
+  colloquialisms, buzzwords, or entertainment devices; analogies go in an
+  aside), rule P6 (industry jargon only in an optional "Industry jargon"
+  aside that states its approximate meaning, context of use, and lack of a
+  standard definition), rule P7 (one claim per sentence, every logical link
+  stated), rule P8 (relation words match the math exactly), and rule P9 (a
+  display equation's lead-in sentence says what it gives and where it comes
+  from). All review-only (`docs/authoring/prose.md`).
+- **Rule S2: a part page links the earlier parts to this one, then states
+  its own scope.** Every `content/docs/<dir>/index.mdx` carries a
+  `<PartScope>` paragraph on what the part covers, and every part after the
+  first also carries a `<PartBridge>` paragraph before it, on how the earlier
+  parts lead in. Both components are new (`explico/components/PartBridge.astro`,
+  `explico/components/PartScope.astro`) and render their Markdown child as-is.
+  Build-enforced by `gate-part-pages.ts` at `pnpm validate:content`: each slot
+  appears once, holds one paragraph, and falls inside a word range. The range
+  is `rules.S2` (`bridgeMinWords`, `bridgeMaxWords`, `scopeMinWords`,
+  `scopeMaxWords`), 30–150 words for any end left out. A part
+  without an overview page is unaffected
+  (`docs/authoring/structure-rules.md#s2`).
+- **A closed section says so on every screen.** Under its title it now
+  shows what the fold holds — "Hidden here: 2 paragraphs, 1 equation"
+  (subsections, paragraphs, equations, figures, tables, diagrams, lists,
+  code blocks, memos, worked examples, questions) — which folds away once
+  the section opens. On a narrow or touch screen the chevron moves into the
+  title line and stays visible in both states (`›` closed, `⌄` open), and a
+  closed title adds "(tap to expand)" — "(click to expand)" with a mouse.
+  All of it is `aria-hidden` and part of the tap target; the heading alone
+  still names the disclosure. Nothing to author: every collapsible section
+  gets it.
+- **Rule N22: an accent or mark on a symbol is an operator.** A decoration —
+  an accent (`\hat`, `\widehat`, `\bar`, `\tilde`, `\dot`, `\vec`, …),
+  `\overline` / `\underline`, or a superscript `'`, `^*`, `^\dagger` — is
+  on the course's `rules.N22.allow` list (shipped empty,
+  `src/reference/base-accents.mjs`), explained by an operator notation entry
+  (`latex: \hat{}`, `{}'`, `{}^{*}`), or part of a whole-form entry
+  (`latex: \hat{\beta}`), which wins for that exact form. New Tier-3
+  warning `accent-explained` (`consistency.ts` `checkAccentExplained`). The
+  resolver reports each decoration in `resolveMathGlyphs(…).decorations`
+  (`wholeForm`, `operator`); `collectDecorations`, `decorationOfEntry`,
+  `operatorEntryLatex`, `operatorDisplayLatex` and `DECORATION_NAMES` are
+  exported from `math-glyphs.mjs`. See `docs/authoring/notation.md#n22`.
+- **Lesson frontmatter `notation.suspend` (rule N22).** A page can declare
+  that a decoration is not an operator there
+  (`- operator: "'"`, `reason: …`). Every decorated form of it on that page
+  then needs its own entry or a whole-form `\explain`, or the build fails
+  with `suspended-operator-unresolved` (the gate and the render path both
+  check lesson-body math; assessments, labs and notation formulas keep the
+  operator reading). New diagnostics `operator-suspended` (info),
+  `operator-suspension-reason` (warning, no reason given) and
+  `operator-shadowed` (info, a whole form over an operator the page
+  explains). An unknown decoration, one suspended twice, or a
+  `notation.local` operator entry for a suspended decoration fails the load.
+  `resolveMathGlyphs` takes `{ suspended }` as a third argument; an item
+  in `unresolved` may carry `suspended` or `font`.
+- **Hovering an accent explained by an operator entry shows the operator's
+  card; the letter under it keeps its own.** The operator's `\explain` wraps
+  the decorated form around the letter's. A table header built from both
+  reads "Estimate of regression coefficient". An operator entry is drawn
+  over a placeholder square (`\dot{\square}`) wherever its symbol is shown
+  on its own.
+- **The Page notation panel names each suspended decoration** and the reason
+  ("On this page, ′ is not an operator. …"): `NotationLayer` takes
+  `suspended`, and `LessonFooter` passes the page's `notation.suspend`.
+
+- **An equation takes a short caption: `\caption{…}` inside its `$$…$$`**,
+  next to its `\label{eq:…}`. It is stripped before KaTeX exactly like the
+  label (and so by every math gate), heads the `[[eq-…]]` preview card, and
+  names the copy action: the copy button and the click-to-copy tooltip read
+  "Copy LaTeX — Range formula". An equation takes no long caption. A
+  `\caption{}` in inline math, two in one equation, or an empty one fails
+  the page build. `EQ_CAPTION_PATTERN` and `equationCaption(latex)` are
+  exported from `equations.mjs`; `stripEquationLabels` now strips
+  `\caption{…}` too; the equation's container carries `data-eq-short`.
+- **A `short` caption on `<Table>`, `<Figure>` and `<Diagram>`**, carried as
+  `data-tab-short` / `data-fig-short` / `data-dia-short`: the reference
+  preview card (`FloatRefLayer.astro`) heads with it, for every kind that has
+  one.
+- **A float's chain icon copies its link**, the way a heading's does: one
+  click puts the page URL with the float's named anchor on the clipboard and
+  says "Link copied · Figure 2.2.1" (`a[data-copy-link]`, handled by
+  `HeadingAnchorEnhancer.astro`), then navigates and highlights as before.
+  A table's caption line gains the chain icon too, after its number.
+- A notation formula's copy button, and its click-to-copy tooltip, read
+  "Copy LaTeX — ‹entry label›" (`data-copy-title` on the formula).
+
+- **Collapse defaults for every kind**, in the `disclosure` settings block,
+  each at the value it used to have hardcoded: `knowledgeChecks`
+  (`{ collapsible: true, defaultOpen: true }`), `memos` (closed), `figures`
+  (open), `diagrams` (open), `workedExamples` (closed) and
+  `tables.truncateAfter` (6). A `defaultOpen` prop still overrides one
+  `<Figure>` / `<Diagram>`, and is new on `<Memo>` and `<CompactExamples>`;
+  `rememberState` is new on `<CompactExamples>`.
+- **Worked examples remember the reader's choice**, like every other
+  collapsible (`section:ex-‹id›`).
+- `section-parts.ts` markers for a block that is a section of its own:
+  `data-section-to-end` on its heading wrapper (its section is the rest of its
+  container) and `data-section-contained` on its container (it never ends a
+  section around it). `CollapsibleSections` honours
+  `data-remember-state="false"` on a heading wrapper.
+
+### Changed
+
+- **Every container is restyled into a tier** (reader-visible; no markup a
+  course writes changes). No container has a top rule any more, and the shadow
+  never grows with heading depth.
+  - `<Figure>`: a card with an accent top rule, a tint and a shadow → **plain**
+    (no box). A `.lab-shell` loses the same card, inside a figure or not.
+  - Knowledge check: a grey card around the questions → **accent**, one card
+    around the heading and the questions (the check's heading wrapper carries
+    `data-card="accent"`; `.assessment-shell` draws no box of its own).
+  - `<CompactExamples>`: a grey card → **accent**.
+  - The notation panel, a part page's rail, the notation glossary's entries
+    and the curriculum map's cards: grey cards → **meta**. The About popover:
+    an accent top rule on the page background → **meta**, keeping its overlay
+    shadow.
+  - `<Memo>`: a bordered box with a 4px accent left rule → **aside**, tinted:
+    the 3px rule and the tint, no box; its `<details>` no longer draws
+    Starlight's own 2px rule inside it. An opened `<ShortNote>`: a 2px rule →
+    the same 3px rule.
+  - Hover cards (a reference preview, a citation, a notation explanation) lose
+    their accent top rule and keep their overlay shadow.
+  - Starlight asides → **aside**: `note` and `tip` in the course accent,
+    `caution` and `danger` keeping an orange and a red rule, tint and title;
+    Starlight's icon per type stays. A Starlight `<Card>` → **meta**.
+  - References were already plain and are unchanged.
+
+- **A table's caption line is the one every float uses**: `Table 2.2.1`, the
+  chain icon, then the caption, at the caption size a figure uses (it was
+  body size) and with no " — " between number and caption. Minimized, a table
+  still keeps its caption line and its header row (decision Q6).
+- **A knowledge check folds by the course's `disclosure.knowledgeChecks`**
+  instead of a hardcoded "collapsible, open"; a figure, a diagram, a memo and
+  a worked-example set take their first state from their `disclosure` key; the
+  notation panel reads `manifest.disclosure.notation`.
+- **A knowledge check's number follows the section numbers' rules**, as a
+  worked-example set's does: shown on a wide screen, in print and on a folded
+  bar, hidden on a narrow screen, and not at all when
+  `numbering.sections.show` is off — then `data-check-number` is not written
+  (so no `#check-…` alias resolves) and `[[check-…]]` / `[[ex-…]]` print
+  `Knowledge check “‹title›”` / `Example “‹title›”` instead of a number. A
+  float's number stays in its caption at every width.
+- **A truncated table shows up to `truncateAfter` rows, half from each end**
+  (3 and 3 under the default 6, as before).
+- **A lab carries no title or caption of its own**; the `<Figure>` around it
+  names the whole. The engine's `.lab-chart-figure` styles are gone (a lab
+  draws its chart in a plain `.lab-chart`), and the "print as shown" note for
+  a compacted figure or diagram follows its caption line.
+- **Rule V3 no longer asks an author for accessibility work.** An interactive
+  figure needs no accessible name or description (`ariaLabel` /
+  `ariaDescription` / `ariaHidden` on the plot) and no text alternative (a
+  `<details>` block of assumptions and representative values): the
+  `<Figure>`'s caption is its accessible name, since the figure renders a real
+  `<figure>` and `<figcaption>`. Rule V3 keeps the hydrated island, the
+  `labMathScope` / `renderLabMath` / `\slot{}` seam and labelled controls — it
+  is narrowed, not switched off, since switching it off would drop the seam
+  too. What stays automatic is unchanged: the hidden labels
+  `rehype-table-header-labels.mjs` writes into an all-math table header, the
+  names the engine gives its own buttons and links, and the axe checks on the
+  engine's markup. `docs/authoring/README.md` § Accessibility states the
+  posture: accessibility is the engine's job, and nothing asks a course author
+  to write any. A course's existing `aria*` options may stay.
+
+- **`build/rules-in-effect.md` and `content rules` list the course's own rules**
+  beside the engine's, under their element, tagged `course`, with the settings
+  file (or the rule's own `doc`) as the link; the count line says how many are
+  the course's, and a disabled one joins the "Off" list. `content rules --json`
+  gains `source: "engine" | "course"` per rule. A **retired** rule is now left
+  off the page and out of `--json` entirely — it has been folded into another
+  and keeps its ID only so old commit messages resolve. A string-array setting
+  prints its items in backticks rather than as JSON, so
+  `rules.N2.reserved`'s LaTeX reads as the author wrote it (`\mathbb{N} — the
+  natural numbers`, not `"\\mathbb{N} …"`).
+- **The manifest schema is now v19**: `rules.course` carries the course's own
+  rules as validated, in file order, so the rules-in-effect page and the CLI
+  never re-read the settings file. A finding from one is in
+  `diagnostics.math` with the rule's ID as its `code`, and
+  `MathGateDiagnostic.context` gains `'course'` — the one context whose
+  severity the course chooses.
+- **Every math-gate finding carries a `code`.** Rule N9 findings are
+  `prose-notation`, rule N14 `abbreviation-unexplained`, rule S1
+  `title-length`; an unresolved glyph is `unresolved-glyph`; a resolver
+  failure keeps the resolver's own code (`unparenthesized-function`,
+  `invalid-latex`, …) and any other compile crash is `math-compile-error`.
+  They were code-less before, so the CLI labelled them by context
+  (`math:prose`, `math:structure`); `code` in `content … --json` output is
+  now `math:<code>` for all of them, and `MathGateDiagnostic.code` is
+  required in the type.
+- **Print follows the screen ("print as shown").** A printed or
+  PDF-saved lesson keeps every disclosure the reader controls — section,
+  figure, diagram, memo, short note, worked-example set, question, the
+  notation list — as the reader left it: open prints in full, closed prints
+  its title and "(content collapsed — full text: `url`)", linking the item's
+  permalink on the deployed site (`canonicalBaseUrl`). Until now print
+  expanded everything. Rows past a long table's fold and an open example
+  set's other tabs still print in full, since the reader never chose to hide
+  them, and the Markdown export still expands everything. A course without
+  `lessonExports.print` gets the same behaviour from the browser's own print.
+  The shared logic is `explico/components/disclosure/print-as-shown.ts`.
+- **The part caret leads its label instead of trailing the row.** `>` before
+  the name it opens, `v` when open, which is how a disclosure triangle reads
+  and where the eye looks for it; the `»` takes the end of the row.
+- **Both sidebars answer a pointer with a filled row**, not only a colour
+  change — on a list of twenty chapters, a text-colour shift is easy to lose.
+  The part header answers too: it is a control, and it was the one row in the
+  panel that looked inert. It also carries a standing tint while the open page
+  belongs to it, so the three states stay distinct — a solid accent row for
+  the current chapter, a tint for the part holding it, a neutral fill that
+  comes and goes with the pointer.
+- **Manifest schema is now v17** (additive): `parts` carries every part with
+  its ordinal, directory link, chapters in reading order, and overview page
+  where one exists — so a page or a breadcrumb reads a part instead of
+  re-deriving one from lesson slugs. `sidebar[].items` is now one mixed list
+  of lesson slugs and `{ label, link, attrs? }` entries (`SidebarItem`)
+  rather than one kind per group; `SidebarGroup` is a single interface
+  instead of a union, which widens what a consumer may receive and narrows
+  nothing. `lessons[].studyMinutes` and `parts[].studyMinutes` come with it.
+- **A whole-form notation match (`\hat{\beta}`, `b'`, `\theta^{*}`) now
+  wraps the decoration too**, so its hover target includes the accent or
+  prime: `\explain{k}{\hat{\beta}}`, not `\hat{\explain{k}{\beta}}`. The
+  rendered HTML of an existing whole form changes accordingly.
+- **A marked entry no longer lends its card to the bare letter.** `latex: b'`
+  or `\theta^{*}` used to make a bare `b` or `\theta` elsewhere on the page
+  bind to it (the parameterised-symbol fallback meant for `t_k` → `t`). A
+  mark makes a different quantity (rule N22), so the bare letter now needs
+  its own entry.
+
+### Deprecated
+
+- **`CourseConfig.operators`, `romanLabels`, `abbreviations`** — the same
+  `allow` / `deny` blocks now live at `rules.N8`, `rules.N10`, `rules.N14`
+  (rule N8, rule N10, rule N14). The old keys are folded in with a
+  `config-deprecated-key` warning; setting both the old key and its
+  replacement is an error. They go away in a later MINOR. The unreleased
+  `partPages` block became `rules.S2` (`bridgeMinWords` … `scopeMaxWords`)
+  before it shipped, with no alias.
+
+### Fixed
+
+- **Grey boxes had no background in the dark theme.** The knowledge-check,
+  worked-examples, notation-panel, glossary and curriculum-map cards and the
+  knowledge-check feedback read `--sl-color-gray-7`, which Starlight defines
+  for its light theme only; the tier tokens name a colour for each theme.
+- **Rule S1 measures a heading as the reader sees it**: its `[collapsed]` /
+  `[card]` markers no longer count toward `rules.S1.maxLength`.
+
+- **An equation's copy button shows its "Copy LaTeX" tooltip.** The
+  equation-wide copy hint's `mouseout` handler removed every
+  `title="Copy LaTeX"`, the button's own included, so the first time the
+  pointer left the button (or crossed onto its icon) the tooltip was gone
+  for good. It now removes only the hints it added itself, on both a lesson
+  equation and a notation formula.
+- **A collapsed section is visible on a phone.** Its chevron sat left of the
+  title in the content gutter, which a phone doesn't have, so it rendered
+  off-screen and the section looked like a plain heading. On desktop the
+  same fixed offset put the glyph on the sidebar's border line; it is now
+  centred in the gutter at every width, level with the title's first line.
+- **The copy-link icon beside a section title shows on touch screens.** It
+  was hidden unconditionally (Starlight hides it only where a hover can
+  reveal it), yet stayed a live tap target — so a tap near the end of a
+  title changed the URL instead of opening the section.
+- **Labs hydrate under `astro dev` again.** `katex-delimiters.mjs` imported
+  `node:fs` at the top level and rewrote KaTeX's bundle on import; a lab
+  island reaches it through `render-lab-math.ts`, so the dev server evaluated
+  it in the browser, where Vite's `node:fs` stub throws — and the island
+  never hydrated. The Node imports are now lazy and the rewrite installs only
+  outside a browser. Builds and server rendering are unchanged: they still
+  get the N17 sizing and still fail loudly when it can't be installed.
+- **A build no longer warns about `katex-delimiters.mjs`.** A lab island that
+  imported `slotPlaceholder` from `render-lab-math.ts` pulled the server-only
+  KaTeX chain into the browser graph, so Vite warned that `node:fs` and
+  `node:module` were externalized. The island-facing half (`slotPlaceholder`,
+  `RenderedLabMath`) now also lives in `explico/reference/lab-math-slot`,
+  which imports nothing. `render-lab-math` still re-exports both, so no
+  import breaks, but an island should switch to `lab-math-slot` to drop the
+  warning. The SSR warning about the rewritten bundle's data-URL `import()`
+  is silenced with `/* @vite-ignore */`.
+- **Printed square roots keep their radical sign.** The print stylesheet's
+  `svg { height: auto }` reached KaTeX's own SVGs and collapsed the `\sqrt`
+  radical (and stretchy arrows and accents) to zero height.
+- **`<Diagram>` formulas render in Safari and every iOS browser.** WebKit
+  paints HTML inside an SVG `foreignObject` that gets its own render layer —
+  every KaTeX `position: relative` span — without the SVG's internal
+  transforms. So each node formula was drawn at the SVG origin, piled onto
+  the first node, while its box and plain-text label stayed in place. Nodes
+  are now positioned with `x`/`y` on the `<rect>` and `<foreignObject>`
+  instead of a `transform` on their `<g>`. Printing had the same fault
+  through the `viewBox` scale that fits a diagram to the page: WebKit
+  dropped the formulas from a printed or PDF-saved lesson. Where CSS can
+  divide lengths, the print stylesheet now keeps the SVG at its build-time
+  size and scales the HTML canvas with a CSS `transform` instead. Browsers
+  without that CSS support keep the `viewBox` scaling. No course changes.
+- **Lesson display equations are no longer clipped at the bottom.** A
+  display equation scrolls sideways inside a box that hides vertical
+  overflow, and that box had no padding, so it ended exactly at KaTeX's
+  metric strut. Glyph ink overshoots those metrics by up to about 0.1em, which
+  cut off the bottom of a denominator's `g` or a stretched `\right]`.
+  `.sl-markdown-content .katex-display` now has `0.25em` block padding, so
+  each lesson equation takes about 8px more vertical space. No course changes.
+- Rules N8 and N10 skipped every labelled display equation: the
+  `\label{eq:…}` made the span fail KaTeX's parse, and the scans treated
+  that as "nothing here". `consistency.ts` now strips the label first, so an
+  unexplained `\operatorname{…}` or `\mathrm{…}` in a labelled equation is
+  reported.
+- `x^\prime` failed the completeness gate as an unresolved `\prime`. A
+  prime is a mark on the symbol before it, never a symbol.
+- An accent's glyph box, a full line tall, took every hover on the letter
+  under it: pointing at the `x` of `\hat{\explain{k}{x}}` showed nothing,
+  or the accent's card. The glyph box now lets the pointer through, and a
+  strip across the top of the decorated form is the accent's hit area.
+
+## [0.9.0] - 2026-09-19
+
+### Added
+
+- **The reader sets each desktop panel's width.** The navigation sidebar and
+  the "On this page" rail each carry a drag handle on their inner edge
+  (`.layout-edge-resizer`, `role="separator"`, also arrow keys plus
+  `Home`/`End` from the keyboard). The navigation's width is written to
+  Starlight's own `--sl-sidebar-width`, so the header's title column, the
+  article's inline start and the `.main-pane` formula all follow it with no
+  second source of truth; the contents rail, which has no such token, takes
+  `--layout-contents-width`, honoured only while `data-contents-resized` says
+  the reader has set one. Both persist per reader through the existing
+  `PreferenceStore` seam (`explico:layout:navigation-width`,
+  `explico:layout:contents-width`) and are dropped again outside the layout
+  they belong to, so a desktop width never follows the page down to a phone.
+- **Dragging a panel below three characters of width collapses it** — `3ch`
+  measured in the panel's own font, so a course that changes `--sl-font` gets
+  the threshold its own text implies. The panel's control then reopens it at
+  the width the reader last chose, not at the sliver the collapsing drag
+  happened to pass through.
+- **A peek now waits out `--layout-peek-delay` (40ms) before it opens.** The
+  rails sit on the two edges of the window, so a pointer on its way to the
+  scrollbar, the tab strip, or across the article crosses one without meaning
+  anything by it, and the panel swung open behind it every time. The CSS keeps
+  `:hover` as the trigger and reads a new `data-navigation-peek-armed` /
+  `data-page-sidebar-peek-armed` attribute as the gate in front of it, so
+  peeking still has one description rather than two. Nothing is lost without
+  JavaScript: a panel is only ever collapsed because that same script
+  collapsed it.
+- **A panel narrowed past its own labels scrolls sideways** rather than
+  wrapping every chapter title into a column of single words. The contents
+  rail's scrollbar, which Starlight hides outright (`scrollbar-width: none`),
+  comes back as `thin` while that panel is reader-sized.
+
+### Changed
+
+- **The collapse controls are rectangles docked into the corner the header
+  and the panel's separator line make**, reading `<<<` / `>>>` for the
+  direction their panel travels, instead of circled carets floating near that
+  corner. Both panels' controls take the same block start, so the pair reads
+  as one row across the page; both are narrow enough to leave the first
+  chapter's own expand caret alone; and each panel now reserves that corner
+  (`--layout-edge-toggle-reserve`) instead of running its first row under the
+  control. New tokens: `--layout-edge-toggle-width`,
+  `--layout-edge-toggle-height`, `--layout-edge-toggle-gap` (one number for
+  both of the control's edges, `2px`), `--layout-edge-toggle-radius` (applied
+  to the one corner free of them) and `--layout-navigation-width`.
+- **While a collapsed panel peeks open over the article, its control grows to
+  meet the separator rather than travelling to it.** Hovering the rail is both
+  what opens the peek and what a reader does on the way to clicking the
+  control, so moving the control at that moment takes it out from under the
+  pointer that was coming for it — 260px away, across the panel. Its outer
+  edge, and the glyph inside it, now stay exactly where the pointer found
+  them while its inner end reaches the separator the open panel puts there.
+  The glyph sits in a box the width of the resting control, pinned to that
+  outer edge, so it does not shift at all.
+- Layout preferences moved from the `credit-playground:layout:*` storage keys
+  to `explico:layout:*`. The old keys are still read once as a fallback, so a
+  returning reader keeps the layout they left.
+
+### Fixed
+
+- **A compact chapter's lesson tooltip is no longer cut off at the navigation
+  panel's edge.** That panel is a scroll container (`overflow-y: auto`, which
+  forces `overflow-x` to match), so an absolutely positioned tooltip could not
+  leave it: any lesson title longer than the panel is wide simply ended there.
+  A showing tooltip is now `position: fixed`, placed from its anchor's own
+  viewport rect and kept on screen at either edge, with its cap raised to
+  `min(22rem, 45vw)`. It is still the link's accessible name in the markup —
+  only where it is painted changed.
+
+### Breaking
+
+- `--layout-edge-toggle-size` is gone, replaced by the separate
+  `--layout-edge-toggle-width` and `--layout-edge-toggle-height`. A course
+  that overrode the old token to resize the control sets the two new ones.
+- The control's inner markup is `span.layout-edge-glyph` (with `-hide` and
+  `-restore` variants) rather than `svg.layout-edge-icon`. A course that
+  styled `.layout-edge-icon` retargets it.
+
+## [0.8.0] - 2026-09-19
+
+### Breaking
+
+- **Rule N17 is inverted: a nested delimiter is sized by the engine, never by
+  hand.** The engine now installs its own KaTeX delimiter sizing
+  (`src/reference/katex-delimiters.mjs`), changing one constant in
+  `makeLeftRightDelim` — `delimiterExtend`, TeX's `\delimitershortfall`, from
+  `5.0` to `-1.0` points.
+  Stock TeX and stock KaTeX let a `\left … \right` pair fall up to 5pt short of
+  its content, so two pairs at different depths around similar content round to
+  the same glyph and the nesting vanishes; N17 used to repair that by making
+  authors hand-pick `\bigl` → `\Bigl` → `\biggl` → `\Biggl` outward. Those are
+  *fixed* glyphs: they stop tracking the content they wrap, they run out after
+  four levels, and editing an inner expression silently invalidates every size
+  above it. With a negative shortfall a pair is always strictly taller than its
+  content, so each enclosing level grows on its own, at any depth, by exactly
+  what it needs. `\left … \right` at every level is now the rule, and
+  hand-sizing a pair inside a nest is the warning.
+
+  Consequences for a course:
+  - The Tier-3 diagnostic code is renamed `delimiter-size-hierarchy` →
+    **`delimiter-manual-size`**; a `lint-ignore.yml` entry or a script matching
+    the old code must be updated. Its diagnostic shape changed too: the
+    `outerSize`/`nestedSize` fields are replaced by a single `size` (the
+    hand-picked size found), and `suggestion` is now always present and always
+    a `\left`/`\right` pair — it no longer carries a `size` field.
+  - Math that was N17-compliant now warns. A ladder such as
+    `\Biggl[a+\biggl(b+\Bigl[c+\left(d+e\right)\Bigr]\biggr)\Biggr]` reports one
+    finding per hand-sized level; the repair is `\left`/`\right` at every level.
+    A *lone* hand-sized pair that is not part of a nest — `\bigl(x,\ y\bigr)`
+    for a tuple — is deliberately left alone.
+  - **A course needs no install step for this.** `delimiterExtend` is a
+    function-local `const`, so nothing KaTeX exports reaches it and the change
+    has to happen in the module's own source. Rather than a `patches/` file —
+    which pnpm records per project and so cannot travel inside the npm artifact
+    — the engine reads KaTeX's ESM bundle, rewrites that constant, and moves
+    the render entry points onto the shared `katex` object. `rehype-katex`
+    reads `katex.renderToString` at call time and KaTeX's default export is
+    mutable, so lesson-body math inherits it without the plugin being forked or
+    aliased. `astro.config.mjs` already imports
+    `explico/reference/katex-options.mjs`, which installs it, so an existing
+    course picks this up on upgrade with no edit. The installer verifies itself
+    — a KaTeX upgrade that moves the constant, or anything that renders first,
+    fails the build with an explicit message instead of silently reverting to
+    stock spacing. [`docs/katex-bracket-scaling.md`](docs/katex-bracket-scaling.md)
+    derives the change and documents the mechanism and its trade-offs.
+
+### Added
+
+- **A math diagnostic now names the equation it belongs to.** Every finding
+  the math gate reports from a `$$…$$` block that carries a `\label{eq:…}`
+  gains an `equation` field — `{ key, href }`, where `href` is the anchor the
+  rendered page gives that equation (`/l1-ar/ar1-basics/#eq-ar1-variance`) —
+  and `diagnosticLine()` appends it, so the console line, the run log, and
+  `pnpm content diagnostics` all read
+  `[code] file:line:column: message (eq:<key> -> <href>)`. A size-only
+  `delimiter-manual-size` finding inside a six-line `aligned` block was
+  otherwise anonymous: the message names delimiters, never the result they
+  belong to, so an author had to reconstruct which equation was meant from a
+  line number alone. `CliDiagnostic` carries the same optional field, so a
+  course's own `scripts/content.ts` gets it without change. The manifest
+  schema is now **v16** (additive: v15 → v16); nothing existing changed shape.
+
+- **The About panel publishes the identity it shows.** `AboutPanel.astro` now
+  stamps `data-knowledge-version`, `data-knowledge-date` (omitted when the
+  content changelog has no date) and `data-engine-version` on its
+  `details[data-about-panel]` element, and marks the rendered version line with
+  `data-knowledge-line`. The two versions the panel exists to publish were
+  readable only as prose — and as a `version · date` join — so a course's build
+  check had to match that text, which pins the check to one version string and
+  turns every routine bump into a test edit; this repo's own
+  `playground/tests/e2e/about.spec.ts` was asserting `0.4.0` against a
+  playground long since at `0.5.2`. A bare version substring is not scoped to
+  the panel either, so the engine version printed one row below can satisfy it.
+  The attributes are additive: nothing rendered changed, and the existing
+  `data-about-panel` hook is untouched.
+
+### Fixed
+
+- **A glossary heading's accessible name is the term again.** The notation
+  glossary's per-entry anchor link moved *inside* its `<h2>` when the entry
+  header was rebuilt for smooth scrolling, so the `aria-label` on that link
+  ("Link to “Velocity”") joined the heading's accessible name — a screen reader
+  announced "Velocity Link to Velocity", and any check for the heading by name
+  stopped matching. `NotationGlossary.astro` now wraps the heading and its
+  anchor in a `.glossary-heading` flex row, the shape
+  `rehype-heading-anchors` already gives a lesson heading (`<h2>` and
+  `a.sl-anchor-link` as siblings). Nothing visual changed; the anchor still
+  reveals on hover and focus.
+
+- **A diagnostic's `line` now addresses the file it names.** Every gate scans
+  `lesson.body`, which Astro's `parseFrontmatter` hands over with the
+  frontmatter already removed, but each finding is reported against
+  `lesson.source.file` — so every `file:line:column` the engine has ever
+  emitted for a lesson was short by the height of that lesson's frontmatter.
+  It failed silently in the worst way: the number stayed plausible, so an
+  editor, a VS Code problem matcher, or an author following
+  `pnpm content diagnostics` jumped confidently to the wrong line, and a
+  size-only N17 finding could not be located at all. `parseDocument` now
+  records the body's start line, `NotationLessonInput` carries it as an
+  optional `bodyLine`, and the new `lessonLine()` helper applies it — so
+  `gate-math` (including every `delimiter-manual-size` column),
+  `gate-prose-notation` (N9), `gate-abbreviations` (N14), and
+  `gate-heading-length` (S1) are all corrected at once. A hand-built lesson
+  input that omits `bodyLine` behaves exactly as before.
+
+- **`equationAnchorId({ key })` type-checks without a `number`.** Its JSDoc
+  required both properties although `number` is read only when there is no
+  `key`, so a keyed caller had to pass a value the function ignores.
+
+- **A notation `formula` can use a manual delimiter size, an accent, a box, or
+  a color without failing the build.** `render-notation-math.ts` sanitizes
+  KaTeX's output against an attribute allowlist that had only ever grown to
+  cover what the corpus happened to use, so ordinary math threw
+  `Unexpected KaTeX property` with no author-side workaround: `\Bigl`/`\biggl`/
+  `\Biggl` (`minsize`, `maxsize`), `\xrightarrow` (`minsize`), `\boxed`
+  (`notation`), and `\colorbox` (`voffset`, `mathbackground`). Rule N17 asks
+  authors for exactly those delimiter commands, so a card that followed the
+  engine's own advice could not build. The allowlist is now KaTeX's whole inert
+  presentation surface — `columnlines`, `depth`, `display`, `largeop`,
+  `linebreak`, `linethickness`, `mathbackground`, `mathcolor`, `mathsize`,
+  `maxsize`, `minsize`, `notation`, `rowlines`, `valign`, and `voffset` join the
+  set — with `alt`, `href`, `src`, and `title` explicitly denied, and a new test
+  scans KaTeX's own `setAttribute` calls so a KaTeX upgrade that adds an
+  attribute fails here instead of in a downstream course. Hex colors are
+  accepted in an attribute or style value; no attribute that can carry a URL is
+  allowed through.
+
+- **`\vec` (and every other accent) renders again.** The style sanitizer
+  required each CSS declaration to end in `;`, but KaTeX does not always
+  terminate the last one — `\vec` emits `style="width:0.471em"` — and the
+  rejection then fell through to the misleading
+  `Unexpected KaTeX property: style`. Declarations are now validated one at a
+  time, and an unsafe `style` or `d` value says so instead of reporting an
+  unknown property.
+
+- **A macro in a formula no longer invents a source span.** KaTeX gives a node
+  it produced by expanding a macro a `loc` from the lexer over the *macro
+  body*, so those offsets index that body and not the source being scanned —
+  and they are still valid indices into a longer source, so the glyph resolver
+  read them as a real span over unrelated text. `\vdots` expands to
+  `{\varvdots\rule{0pt}{15pt}}`, whose atom claims characters 1–10: in
+  `M=\begin{pmatrix}…` that is `"=\begin{p"`, and because no author can wrap
+  that slice in an `\explain`, a matrix showing a column ellipsis failed the
+  build with `Unresolved notation ""`. Where the stray span instead collided
+  with a glyph in scope, the binding was injected at the macro body's offsets
+  and split the source mid-command — `\varSigma=\operatorname{Cov}(X)` became
+  `\varSigm\explain{cov-matrix}{a=\ope}ratorname{Cov}(X)`, a corrupt formula no
+  gate rejected. `nodeSpan` now believes a `loc` only when it belongs to the
+  string this pass parsed. 79 of KaTeX's 282 macros emit such a node, among
+  them `\argmax`, `\argmin`, `\plim`, `\limsup`, `\liminf`, `\bmod`, `\pmod`,
+  `\R`, `\N`, `\Z` and every upright `\varGamma`-style capital. A macro's
+  *argument* keeps the author's own locs and still binds normally. One limit
+  remains: a macro-expanded glyph has no authored span, so canonical matching
+  and the completeness gate cannot see it — annotate it with an explicit
+  `\explain{key}{\varSigma}`, which works and is unaffected by this change.
+
+- **A malformed `\explain` / `\slot` key fails the build instead of reaching
+  the reader.** KaTeX does not treat a denied `trust` callback as a parse
+  error: it renders the command name in `errorColor` and continues, so
+  `\explain{Not A Key}{\Omega}` produced red `\htmlData` text on the page with
+  the build green. (Until now this was masked by `mathcolor` — the attribute
+  KaTeX's error rendering carries — not being in the allowlist.)
+  `renderNotationMath` now checks both marker macros against
+  `trustNotationMarker` before KaTeX runs and throws naming the offending key.
+  `renderNotationFormula` still degrades to inert-but-correct math rather than
+  costing a reader the equation.
+
 ## [0.7.0] - 2026-09-18
 
 ### Breaking
@@ -722,7 +2126,11 @@ under **Breaking** below; a PATCH never breaks.
   system with its completeness gate, the curriculum-graph validator, the
   Astro/Starlight UI, the LMS / session / analytics seams, and the `content` CLI.
 
-[Unreleased]: https://github.com/danieltuzes/explico/compare/v0.7.0...HEAD
+[Unreleased]: https://github.com/danieltuzes/explico/compare/v0.11.0...HEAD
+[0.11.0]: https://github.com/danieltuzes/explico/compare/v0.10.0...v0.11.0
+[0.10.0]: https://github.com/danieltuzes/explico/compare/v0.9.0...v0.10.0
+[0.9.0]: https://github.com/danieltuzes/explico/compare/v0.8.0...v0.9.0
+[0.8.0]: https://github.com/danieltuzes/explico/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/danieltuzes/explico/compare/v0.6.0...v0.7.0
 [0.6.0]: https://github.com/danieltuzes/explico/compare/v0.5.0...v0.6.0
 [0.5.0]: https://github.com/danieltuzes/explico/compare/v0.4.0...v0.5.0