explico 0.11.1 → 0.13.0

package/CHANGELOG.md

@@ -14,6 +14,1295 @@ under **Breaking** below; a PATCH never breaks.
 
 ## [Unreleased]
 
+## [0.13.0] - 2026-10-07
+
+### Breaking
+
+- **A float's caption has no chain icon, and an equation's Copy LaTeX
+  button moved to its bottom border.** The toolbar on a float's number
+  (Added, below) copies the link instead. `a.float-caption__anchor` is gone
+  from `FloatCaption.astro` (figures, diagrams) and `Table.astro`, and
+  `button.keyed-equation__copy` is now a child of `.keyed-equation` rather
+  than of `.keyed-equation__controls`. Course CSS or browser tests that
+  target either need the new place: hover the number, then use
+  `a.float-toolbar__link` (it carries the same `data-copy-link` name).
+
+- **A course with `lessonExports.standaloneHtml` on needs
+  `canonicalBaseUrl`** once its landing page or a part's page links anywhere
+  else in the course, which a splash hero's actions always do. Those pages
+  are exported now (below), and an exported page that links out without the
+  base fails the build, as a lesson always did. Set
+  `lessonExports.canonicalBaseUrl` to the deployed course root.
+
+- **Astro 7.3, Starlight 0.42 and `@astrojs/react` 7.** The exact
+  `peerDependencies` pins move: `astro` 7.2.7 → 7.3.5, `@astrojs/starlight`
+  0.41.9 → 0.42.4, `@astrojs/react` 6.0.4 → 7.0.0 and
+  `@astrojs/markdown-remark` 7.2.4 → 7.3.1. A course moves the same four in
+  its own `package.json`, together: Starlight 0.42 requires `astro` 7.2.10
+  and `@astrojs/markdown-remark` 7.3.0 or later. What moved upstream that a
+  course can depend on:
+  - Starlight 0.42 drops support for browsers older than Chrome 116,
+    Safari 17 and Firefox 125.
+  - Its mobile menu is a `#starlight__sidebar` popover opened by a plain
+    `button.sl-menu-button`: the `<starlight-menu-button>` wrapper, its
+    `aria-expanded` and `body[data-mobile-menu-expanded]` are gone. Course
+    CSS or scripts that target them match nothing; use `.sl-menu-button`
+    and `:popover-open` (`body:has(#starlight__sidebar:popover-open)`).
+  - Starlight's unused top-level `tagline` option is removed (a splash
+    page's `hero.tagline` is unaffected).
+  - `@astrojs/react` 7 removes the `babel` option. A course that passes
+    `react({ babel: … })` moves those plugins to `@rolldown/plugin-babel`
+    in `vite.plugins`.
+  - `astro build` now prints `[WARN] [content] The collection "i18n" does
+    not exist or is empty` (twice). It is harmless: Starlight silences it
+    through `console.warn`, which Astro 7.3's logger no longer goes
+    through.
+
+- **A page that is not a chapter no longer downloads on its own** (D8),
+  reversing the per-page downloads added earlier in this cycle (no release
+  wrote them, but a site deployed from `main` has): the build stops
+  writing `downloads/index.html` (the landing page),
+  `downloads/<part>/index.html` (a part's page), `downloads/glossary.html`,
+  `downloads/curriculum-map.html` and `downloads/figures-and-tables.html`.
+  Their content is in `downloads/part/<dir>.html` (a part's page, then its
+  chapters) and `downloads/course.html` (all of them). A link to one of the
+  old files now 404s; point it at the part's or the course's file. The
+  Download menu lists the scopes that contain the page: "This chapter" on a
+  chapter, "This part" on a chapter or its part's page, "Whole course" on
+  every page, each with the chapter's, part's or course's name; the course
+  file is saved under the course's name (`explico-playground-motion.html`).
+  A download's accessible name names its scope ("Download this chapter as
+  standalone HTML", "… this part …", "… the whole course …"). During
+  `astro dev` only a chapter's HTML builds on request.
+
+- **`editorialStatus` is retired.** Lessons are reviewed continuously, so
+  the draft / in-review / reviewed flag never meant a page was finished; it
+  only put a label in front of readers. No collection reads it now and
+  nothing shows it: the part page's chapter list, the notation card, the
+  glossary entry, the reference list and the citation card lose their
+  status label. What a course changes:
+  - **Delete the key from every content file.** A page, notation entry,
+    abbreviation, competency, assessment, source or track that still sets
+    it fails the build with `retired-key`, once per file, with the file and
+    line. The check is the new `retired-keys` invariant
+    (`reference/gate-retired-keys.ts`), reported under `curriculum` so a
+    course's own `validate:content` script fails on it unchanged. In a JSON
+    record the key is often the last one, so deleting its line leaves a
+    trailing comma.
+  - **The manifest schema is now v29**: `lessons[].status`, the
+    `editorialStatus` of the notation definitions under `lessons[]` and
+    `pages[]`, and the `status` of `notation.definitions[]` and
+    `notation.bundles[]` are removed.
+  - **The `content` CLI:** `content status` no longer counts drafts
+    (`--json` loses `draftDebt`), `content context` loses `lesson.status`,
+    and `content new lesson` / `content new term` no longer write the key.
+    A course's own `scripts/content.ts` that prints `report.draftDebt` or
+    `report.lesson.status` must stop: `tsx` does not type-check, so
+    `report.draftDebt.lessons` throws at run time.
+  - **Diagnostic codes:** `review-state` and `alignment-review-state` are
+    removed with the checks that compared review states. The unrelated
+    check that shared `review-state`, a lesson that `teaches` but declares
+    no `assumptions`, now reports `missing-assumptions`.
+  - **Exports:** `EditorialStatus` and the `status` field of
+    `SharedNotationDefinitionInput`, `NotationLessonInput`, the notation
+    definition records and `NotationPageBundle` (`explico/reference/types`);
+    `LessonDefinition.status` and `SourceDefinition.editorialStatus`
+    (`explico/curriculum/validation`); the per-definition `editorialStatus`
+    of `NotationLayer`. A course test that builds these inputs drops
+    `status`.
+  - **CSS hooks:** `.notation-status`, `.glossary-status`,
+    `.citation-status` and `.citation-panel-status` no longer exist, and a
+    glossary entry's header has two columns, not three.
+
+- **`estimateBoxSize` is gone from `explico/reference/diagram-layout`.**
+  Diagram boxes are measured now (Changed, below); `nodeBoxSize` takes the
+  label and the formula's measured box (`measureFormula`) in its place.
+- **A quoted prop holding `$…$`, `[[…]]` or `[@…]` fails
+  `validate:content`** (`markup-in-prop`, invariant `prop-text`). A prop
+  reaches the page as plain text, so `short="Speed $v$"` showed its dollars
+  in the caption line, the preview card and the "Figures and tables" page,
+  and a `[[…]]` or `[@…]` printed as typed; meanwhile the math gate demanded
+  a notation entry for the symbol. Write a symbol in a prop in Unicode or
+  words, and reference or cite from the prose next to the component. The
+  math gates no longer read prop strings. None of the four courses on the
+  maintainer's machine has such a prop.
+- **A second `\label{eq:…}` in one display block fails `validate:content`**
+  (`eq-label-repeated`). A `$$…$$` block is one numbered equation: only its
+  first label named it, and a `[[eq-…]]` to a later one failed with "no
+  display equation on the page carries" a label the block visibly holds.
+  Give each equation you refer to its own block.
+- **A notation key that starts with a reference prefix fails where it is
+  defined.** `[[eq-…]]`, `[[tab-…]]`, `[[fig-…]]`, `[[dia-…]]`, `[[ex-…]]`,
+  `[[check-…]]`, `[[sec-…]]` and `[[memo-…]]` are routed by prefix before
+  notation keys are looked at, so an entry keyed `ex-ante` or `eq-fake` could
+  never be referenced, and its use failed with a float error that never said
+  the key was a notation entry. The registry now reports `invalid-key` at
+  the definition, naming the prefixes, and `content new term` refuses such
+  a key. None of the four courses on the maintainer's machine has one.
+- **A worked-example set or a knowledge check inside a memo or a short
+  note fails rule S6** (`heading-nested`). Its own `<h2>` landed under the
+  memo's `<h6>`, the heading order jumped, and "On this page" never listed
+  it, with no diagnostic. None of the courses on the maintainer's machine
+  has one.
+- **A `<Table>` holding two tables fails `validate:content`**
+  (`tab-several-tables`). The page showed both under one number and
+  caption, and the PDF, LaTeX and Markdown exports kept only the first,
+  silently. None of the courses on the maintainer's machine has one.
+- **A citation in a link's text fails `validate:content`**
+  (`citation-in-link`). `[as measured in [@id]](https://…)` printed the
+  citation as typed on the page and in every export, while the manifest
+  counted the source as cited. The lesson's sources are now read the way
+  the page reads them, and the message says to cite after the link. None of
+  the courses on the maintainer's machine has one.
+- **Rule N23: an index is part of the symbol**
+  (`docs/authoring/notation.md#n23`). A subscript on a symbol must be
+  explained by the indexed symbol's own entry (`latex: v_0`), a family entry
+  whose index runs (`latex: x_k` explains `x_1`, `x_{k+1}`), or an index entry
+  for the subscript (`latex: "{}_0"`, Added below); a card on the base alone
+  no longer passes. Arithmetic on an index letter with its own card passes
+  (`X_{t-1}`), and a subscript on an operator or a bracket is not an index
+  (`\sum_{i=1}`). `validate:content` fails with four errors
+  (`gate-indices.ts`), in a lesson body located and once per form per page
+  (per letter for `index-range`), in a shared formula once per formula:
+  `index-explained` (a digit, a label or a base-library `i`, `e`, `d`
+  explained by nothing), `index-swallowed` (`\explain{key}{v_x}` where `key`'s
+  `latex` has no index), `index-range` (a running index — a lowercase letter
+  not marked `fixedIndex` — whose set is stated neither as `range` on its card
+  or its family entry nor after a `\quad` on the first display line that uses
+  it) and `derived-key-taken`. Notation formulas and assessments get the first
+  two from `validate:content` too; lab math (`renderLabMath`) and `<Diagram>`
+  formulas fail `astro build` with the same findings as they render. A course
+  fixes each form, or waives one place in a lesson body with `{/*
+  explico-allow N23: <reason> */}`; `rules.N23.enabled: false` turns all of it
+  off. `docs/authoring/migrating.md` has the one-pass migration.
+- **An indexed entry no longer lends its card to other symbols** (rule N4).
+  An entry with a fixed index — digits or a `\mathrm{…}` label, `v_0`,
+  `H_0`, `T_{\mathrm{opt}}` — lent its card to the bare base and to every
+  other index: `H_1` opened "Null hypothesis". It lends to nothing now. A
+  family entry (`\alpha_i`) lent its card to the bare symbol (`\alpha`, a
+  different object); it lends only to its own instances now. A function form
+  still lends by its head: `D(0,t)` explains a bare `D`, and `V_0(1_t)`
+  explains `V_0(1_2)` but no longer a bare `V`. A symbol that had a card only
+  by borrowing one fails `unresolved-glyph`, and the message names the
+  indexed entry with that base: give it its own entry, or an
+  `\explain{key}{\alpha}` where it really is the family's shorthand. An
+  entry with a superscript only (`j^{(m)}`) still lends to its base.
+- **The manifest schema is now v31 (additive)**: the `notation` bundle of
+  `lessons[]` and `pages[]` gains `derived`, the derived cards (Added below)
+  its body math uses; a notation definition record carries `reads`, `range`,
+  `fixedIndex` and an index entry's `formulaTemplate` when they are set; a
+  bundle definition carries `range`. `diagnostics.math` carries the N23
+  codes.
+- **`resolveMathGlyphs` resolves an indexed symbol differently**, which
+  changes a card a reader sees without a content edit; a course records it
+  in its own changelog (rule C1). Under a power or a mark, a whole form
+  still wins (`v_0^{2}` is `v_0` squared; Fixed, below). An instance takes
+  its family's card ahead of a plain entry for its base (`x_1` opens the
+  `x_k` card, not the `x` card), through a font-styled family too
+  (`\mathbf{v}_k` explains `\mathbf{v}_1`), and only through a family whose
+  index has the same shape — the same number of comma-separated slots, and
+  no fixed label in a running slot (`x_{\mathrm{e}}` is not an instance of
+  `x_k`). The whole instance is one target. Two families on one base that
+  both fit an instance fail `ambiguous-base-fallback`, as two lending
+  entries did before.
+- **Rule S5 is retired into rule N4, and `CourseConfig.conventions` is no
+  longer read.** Its check (`convention-single-definition`) matched one
+  finance course's wording and one key per course, and never fired in any
+  course. A `conventions` block now does nothing and warns
+  `config-deprecated-key`; the type keeps it as a deprecated `unknown` until
+  the next MINOR. `CourseConventions` is gone, and `runConsistencyChecks`
+  no longer takes `catalog` or `conventions`. Rule N4 says how to write a
+  convention instead: on its notation entry, `meaning` names the other
+  choice and the body says how to convert.
+
+### Added
+
+- **A toolbar on every float's number.** Hovering or focusing the number of
+  an equation, a figure, a table or a diagram shows Pin and Dock just above
+  it and Copy link just below it, none of them over the number. Pin and
+  Dock keep the float's own reference card, pinned next to the float or
+  docked beside the article; Copy link copies the float's named link, as
+  the chain icon did. A click on the number itself still only puts its
+  anchor in the address bar. An equation's Copy LaTeX sits on its bottom
+  border, under the number, or slid along the border in an equation too
+  short for both, and shows while the equation is hovered. A touch screen
+  has no toolbar. The toolbar is `components/float-toolbar.ts`; it opens
+  the card through the new `keepCardFor(layer, anchor, mode)` in
+  `card-manager.ts`, and a card source can name an item's own anchor
+  (`CardSource.ownAnchor`), so a card pinned from a number comes back after
+  a reload like any kept card.
+
+- **A docked card widens from its right edge, and a width menu sizes
+  them all.** A card beside the article has a handle along its right edge:
+  drag it, or focus it and use the arrow keys (Shift for bigger steps);
+  Home or a double click gives the card back the column's width. It may
+  reach past the "On this page" rail: the rail then goes under the cards
+  (`data-card-over-rail` on `<html>`), and its `>>>` collapses it. Once a
+  reader has resized a card, a width menu joins the switch at the top of
+  the side column: Default, Wide (65 characters a line) or Very wide (90),
+  counted in the card's own text so they follow the text size; it lists a
+  size only when it fits beside the article with both panels collapsed. A
+  size applies to every docked card and the next ones; a card resized by
+  hand reads "Custom". The width is remembered with the card, and the
+  size per reader (`card-side.ts`, `card-manager.ts`, `HoverPanel.astro`,
+  `card-memory.ts`).
+- **A lab's picture is in the built page, or the build says so** (rule
+  V3). A lab draws its plot in the browser, after the page loads; until
+  then the page held an empty box, so a reference card from another page,
+  print without JavaScript and the HTML export had no picture. The lab's
+  wrapper now draws its default picture at build time and hands it to the
+  island as children, which the island shows until it has drawn its own
+  (the playground's `content/labs/still-plot.ts` shows the pattern). The
+  build warns about a figure whose picture is an island with nothing drawn
+  in the built page: `lab-picture-undrawn`, a warning
+  (`reference/figure-pictures.ts`, run by `compiler/astro.ts`). A reference
+  card copies the build's picture until the island has drawn
+  (`FloatRefLayer.astro`, `cloneFigureBody`, which used to drop an
+  island's children), and `global.css` hides it the moment the live plot
+  in `.lab-chart-live` exists.
+
+- **A text size on touch screens**: 100%, 90%, 80% or 70%, beside the
+  theme switch in the phone menu (and in the header of a tablet held wide).
+  A PC has the browser's zoom; a phone's text-size settings are buried in
+  its browser's menus. The choice scales the root font size
+  (`data-text-size` on `<html>`, `styles/global.css`), so the text, the
+  math, the spacing and the cards follow; it is remembered per reader and
+  applied before the page first paints, by an inline script that
+  `PreferenceStore.ts` builds (`inlineRootAttributeScript`), so storage is
+  still touched in that file alone. It shows only where there is no hover,
+  never in print, and a card's text keeps a 12 px floor
+  (`TextSizeControl.astro`, rendered by `LayoutSocialIcons.astro`, which a
+  course already wires as its `SocialIcons` override).
+
+- **Carried cards stay on screen** (rules K2–K4). With carrying on, a kept
+  card — pinned, docked or moved — scrolls with its trigger until it
+  reaches the top edge of the window (under the header, and in the side
+  column under its controls row) or the bottom edge, then stays there,
+  and follows its trigger again once its place comes back. Cards at one
+  edge stack outward from it in the order they were opened, only those
+  over each other; when the cards held over each other are taller than the
+  window, the older ones collapse to their header row, and a click or the
+  keyboard's focus opens one again. A card opened from inside a held card
+  moves with it. `heldAt` in `card-placement.ts` is the rule, pure; the
+  card manager fixes a held card at its edge (`data-card-held="top"` or
+  `"bottom"`, `data-card-collapsed`) from one scroll listener, on only
+  while carrying is on and a card is kept. A held card does not print.
+
+- **A "Carry cards" switch** (K1, D6–D8). It joins "Article left" in
+  the side column's controls row while the column is in use; otherwise it
+  shows alone at the article's top right, while a card is kept. Its
+  tooltip says what it does. It is off until a reader turns it on, and the
+  reader's choice is remembered (`card-carry.ts`, through
+  `PreferenceStore`). A course can start every reader with it on: the new
+  `cards.carry` course setting (`CourseConfig.cards`, `normalizeCards`),
+  default `false`. The manifest schema is now v26: `cards`, the course's
+  card settings with the defaults applied, which `LessonFooter.astro`
+  hands the page in a hidden `[data-explico-card-config]` element.
+
+- **Carried cards come along to every page of the course** (K5, D9):
+  by a link, the sidebar, search, Next and Previous, Back and Forward, a
+  reload or a typed address. On the page a card was opened on it attaches
+  to its trigger again, at its place; anywhere else it is rebuilt from that
+  page, fetched once, and held at the window edge it was at, at the same
+  place across the window. A figure card brings its plot as it was drawn.
+  Closing a card ends its journey; turning carrying off closes the cards
+  from other pages. Each tab keeps its own carried set in session storage,
+  and every change also writes it as the course's last set in local
+  storage, which a tab with no set of its own (a new tab, a browser
+  restarted without its tabs) takes. A page the browser brings back from
+  its cache takes the set as another page left it. While cards from other
+  pages sit on the bottom edge, the page grows by their height, so its
+  Next and Previous links scroll clear of them. Card memory per page rests
+  while carrying is on. New: `CardSource.build(item, page)` and
+  `CardSource.awayItem(item, page)` in `card-manager.ts`, which every card
+  layer implements; `card-fetch.ts`, the fetch-once page cache that
+  `FloatRefLayer.astro` kept to itself until now; the carried set's
+  decoder in `card-carry.ts`; and `createSessionPreferenceStore` in
+  `PreferenceStore.ts`, still the one module that touches browser storage.
+
+- **A page's own symbol, carried, says where it means what it says**
+  (K6, D4). Away from its page, its card opens with "Defined in
+  *‹page title›* · means this only there", and its definition link goes
+  back to that page. When the reader points at a symbol on the new page
+  whose notation entry has the same LaTeX, the carried card's arrow to it
+  is dashed and grey: the same letters, defined elsewhere. A shared
+  symbol's arrow to the same symbol on another page stays solid, and
+  pointing at a carried card shows the nearest such place on the page.
+  Notation entries carry `data-notation-scope` and `data-notation-latex`,
+  a notation card `data-card-scope` and `data-card-glyph`; a source tells
+  the manager a trigger's glyph (`CardSource.glyphOf`) and the triggers
+  with a glyph (`CardSource.lookalikes`), and the arrow overlay draws the
+  dashed kind (`ArrowOverlay.show(…, { lookalike: true })`,
+  `.explico-card-arrow.is-lookalike`).
+
+- **With carrying on, every kept card links back to where it was opened**
+  (K7, D15): "Opened at § 2.1.1" beside its "Go to …", or "Opened at
+  (2.1.3)" when it was opened from inside a numbered equation, the worked
+  example or knowledge check it was in ("Opened at Example 1.2.1"), or
+  "Opened at the start" before a page's first section. A fold's bar and a
+  memo are no sections. With carrying off, a kept card stays by its
+  trigger and shows no such link. Its arrow says where that is (↑ ↓
+  on this page, → on another), and its tooltip says it in full: "Back to
+  where you opened this card: Projectile Range, § 2.1.1 From launch to
+  landing". The link is the section's or the equation's anchor, so it works
+  in a new tab and without JavaScript; with it, the page scrolls to the
+  trigger itself and lights it a moment (`.is-card-origin`), after loading
+  when the card was opened on another page. A card opened from inside
+  another goes back to where the outermost one was opened. The link is an
+  `a.hover-panel-action[data-card-opened-at]` the card manager adds; where
+  a card was opened travels in the carried set.
+
+- **A carried card says whether it means the same everywhere** (K8,
+  plan §4). While carrying is on, a kept card shows, at the left of its
+  header's buttons, a globe — shared notation, citations, abbreviations,
+  numbered references — or a page and "this page", for one of a page's own
+  symbols; its tooltip says which. `HoverPanel.astro` renders the mark
+  (`[data-card-mark="global"|"page"]`), hidden until the manager shows it.
+
+- **LaTeX source and PDF of every chapter** (`lessonExports.latex`). After
+  Astro's static build, each chapter's LaTeX folder is zipped to
+  `downloads/<slug>-latex.zip`: `main.tex`, explico's book class
+  `explico.cls`, the chapter as readable source (named environments for
+  memos, short notes, worked examples and knowledge checks; `\label` and
+  `\ref` for every cross-reference; the author's `\explain` markers kept
+  in the math, printed by the class), its figures, a `latexmkrc` and a
+  README. The same folder is compiled with `latexmk` to
+  `downloads/<slug>.pdf`, a tagged PDF 2.0 with each chapter's answer key
+  at its end. Under LuaLaTeX it is PDF/UA-2 with MathML for every formula
+  (veraPDF passes every playground chapter); pdfLaTeX tags less (no
+  MathML, table rules untagged, a box broken across pages leaves its
+  marked content unbalanced, which poppler reports as "Mismatched EMC
+  operator"), so its PDF claims no standard.
+  - **Numbers are LaTeX's own.** The class counts parts, chapters,
+    sections, equations, floats, worked examples and knowledge checks the
+    way the website does, so an edited download renumbers itself. When the
+    source is compiled unchanged, every printed number is checked against
+    the website's, and a difference fails the build.
+  - **Figures stay vector.** A lab or other figure a browser draws is
+    captured from the finished site with the course's own Playwright
+    Chromium and included as a vector PDF, its caption's live clause
+    filled in. explico's `<Diagram>` is drawn as TikZ from the layout Dagre
+    gave it, so LaTeX sets its text and math.
+  - **A float inside a memo or a worked example** is set where it stands
+    with the `float` package's `[H]` (`ExplicoHere` in `explico.cls`), so
+    tagging gives the float its own caption. The minipage and `\captionof`
+    used before passed PDF/UA-2 under TeX Live 2025, but TeX Live 2026 tags
+    the minipage as a Div, which leaves the caption mid-way through the
+    box's text (veraPDF, ISO 14289-2 rule 8.2.5.27). Without `float` the
+    class falls back to the minipage. CI needs `float` in its TeX Live
+    packages.
+  - **Reproducible.** The same source compiles to the same bytes, and two
+    builds write identical downloads. `main.tex` fixes TeX's random seed
+    before tagging loads (tagpdf names a structure namespace with random
+    digits) and sets the PDF's file identifier, which the engines would
+    derive from the output file's path; a captured figure's PDF carries the
+    course's content date, not the moment Chromium printed it. A figure's
+    alt text keeps its punctuation (`45°, where`), which its braces
+    protect.
+  - **Figure labels match the book.** A captured figure's SVG labels are
+    set in KaTeX's Computer Modern, which explico's stylesheet loads on
+    every page, so any machine draws the same figure, and they are sized
+    so the most common one prints at 9 pt (`\footnotesize`) once LaTeX
+    fits the figure to the page. An Observable Plot axis title moves clear
+    of its grown tick labels; no label grows into another. A figure that
+    still draws text in one of the machine's fonts is named in a warning.
+  - **Engine.** LuaLaTeX by default (TeX Live 2025 or later);
+    `EXPLICO_LATEX_ENGINE=pdflatex` switches to pdfLaTeX. In CI (`CI` set)
+    or with `EXPLICO_LATEX_STRICT=1`, a missing engine or browser fails the
+    build; elsewhere the build warns, still writes the source zips, and
+    leaves an uncaptured figure as a placeholder. explico ships the TeX
+    Live package list as `src/compiler/exports/latex/texlive-packages.txt`.
+  - `lessonExports.latexPaper` sets the paper size: `letter` (default,
+    LaTeX's own) or `a4`.
+  - **Each part and the course as a book** (plan step 6):
+    `downloads/part/<dir>-latex.zip` and `.pdf`, `downloads/course-latex.zip`
+    and `.pdf` (`bookSource`), with cells in the Download menu. A title page
+    from About (the course or part, the content version, the authors, the
+    website), the contents (parts, chapters, sections) and the lists of
+    figures, tables and diagrams that have entries; then each part, opening
+    on its own page (`\ExplicoPart`, numbered as on the website) followed by
+    its page's text and objectives, and its chapters in order; then the
+    appendices: the book's notation, in order of first appearance (a symbol
+    one chapter defines says so), and the course's abbreviations. A
+    reference between chapters is a `\ref`; each chapter keeps its own
+    reference list, numbered as on its page, its citation keys prefixed with
+    the chapter; its notation is in the appendix, and under its title only
+    the link to its live version. Every number in a book is checked against
+    the website. Contents and lists are black, their number columns wide
+    enough for `2.1` and `2.1.10`.
+  - **Every document compiles at once**, up to one per core. On the
+    playground's 8 cores the LaTeX step takes 31 s for its 7 documents, where
+    the 4 chapters alone took about 55 s one after another; the books add
+    79 s of compile time (parts 48 s, course 31 s), and the course book sets
+    the wall time. The build logs these times.
+- **The manifest schema is now v27**: `lessonExports.latex` and
+  `lessonExports.latexPaper`, and every `assessmentContent` item carries
+  its `type`, a choice item's `options` and `correctOptionId`, and a
+  numeric item's `answer`.
+- **Every part and the whole course download as one offline HTML file**
+  (`lessonExports.standaloneHtml`; `compiler/exports/combined-html.ts`):
+  `downloads/part/<dir>.html` is the part's page, then its chapters;
+  `downloads/course.html` is the landing page, the curriculum map, the
+  figures and tables, every part and the glossary last. Each opens with a
+  list of contents. They are assembled from the pages the build wrote, not
+  rendered again, so each page keeps its own notation, citation and
+  float-reference cards, labs and checks. Every id in a page gains the page
+  as a suffix (`eq-range--projectiles-projectile-range`), with every
+  reference to it (links, ARIA id lists, `for`, `popovertarget`,
+  `url(#…)`); a suffix keeps the `eq-`, `fig-` and `cite-` prefixes the card
+  layers read. A link to another page of the same file becomes a link into
+  it, so its hover preview works offline. A React island whose `prefix`
+  an earlier page used gets its own, with the ids React renders from it, so
+  hydration matches. Each page is a section with `content-visibility: auto`
+  and starts a new sheet when printed.
+  - The notation layers of a page share one card source, so a document
+    with several (each page's) serves every page's symbols; a citation
+    card finds its reference through the marker's link instead of building
+    `#cite-<n>`, so a file with several reference lists numbered from 1
+    shows the right one. A kept citation card is remembered by its
+    reference-list item, not its number.
+  - The print controller moved out of the header into the page's footer
+    (`PrintController.astro`, `print-controller.ts`), inside `<main>`: a
+    downloaded page keeps only `<main>`, and lost Ctrl+P's lab loading with
+    the header.
+- **Markdown of every chapter, part and the course** (`lessonExports.markdown`;
+  `compiler/exports/markdown-export.ts`, `markdown/serialize.ts`), built with
+  the site (D2) from the same reading trees as the LaTeX export:
+  `downloads/<slug>-markdown.zip` holds `<name>-markdown/lesson.md` and its
+  `assets/`; `downloads/part/<dir>-markdown.zip` an `index.md` (the part's
+  page, then its contents) and one file per chapter
+  (`02-01-projectile-range.md`); `downloads/course-markdown.zip` an
+  `index.md`, each part's page and every chapter, with shared `assets/` and
+  relative links between the files. The Download menu gains a Markdown
+  column.
+  - GitHub's flavour with `$…$` and `$$…$$` math for remark-math, KaTeX or
+    MathJax, the author's `\explain` markers stripped. Headings keep their
+    numbers, a display equation its `\tag{…}`, each float its number and
+    captions, and every anchor an `<a id>`; a reference into the download
+    is a link into its file, any other goes to the website. A bar in table
+    math is `\vert`/`\Vert`, which a pipe table can hold. Memos, notes,
+    examples and checks are titled quotes, always open; Starlight's asides
+    are GitHub alerts (`[!NOTE]`, `[!TIP]`, `[!WARNING]`, `[!CAUTION]`).
+    Each chapter ends with its references, its notation and the answers to
+    its checks (D3).
+  - A figure a browser draws is a PNG at two device pixels per CSS pixel,
+    taken from the same clean page as its vector PDF; an image is the
+    site's own file; an explico `<Diagram>` is a PNG with its boxes and
+    arrows listed as text. The capture now also draws a diagram, and the
+    LaTeX and Markdown exports share one reading of the chapters and one
+    capture of their figures (`compiler/exports/export-chapters.ts`).
+  - New dependencies: `mdast-util-to-markdown`, `mdast-util-gfm-table`,
+    `mdast-util-math`, the versions Astro already installs.
+  - A part's page in print exports leaves out its generated stats line and
+    chapter list (the export's own contents replace them) and keeps its
+    objectives.
+- **The manifest schema is now v28**: `lessonExports.markdown`.
+- **`downloads/index.json`** lists every file the exports wrote, by its
+  path below `downloads/`, with its size in bytes
+  (`compiler/exports/download-index.ts`). The Download menu reads it.
+- **Ctrl+P and Cmd+P load the labs before printing**, as the Print button
+  does: the page catches the shortcut, loads every lab that will be on
+  paper, and then opens the print dialog. A downloaded page keeps this.
+  The browser's own File → Print cannot wait, so a lab that never loaded
+  prints a one-line note saying how to include it.
+
+- **Rule V7: a figure's picture fits on one screen.** The default slot of a
+  `<Figure>` (plot, key and tables) takes at most `maxPercent` of the
+  viewport height, 80% unless the course sets `rules.V7.maxPercent`, so the
+  reader sees the picture and its caption line together. The height is
+  only known in a laid-out page, so the check runs in a course's Playwright
+  suite: `explico/reference/figure-fit` exports `checkFigureFit(page,
+  { maxPercent?, allow? })`, which opens folded figures, waits for islands
+  to hydrate and the height to settle, and returns a `figure-too-tall`
+  finding (warning) per picture over the budget; `lessonsWithFigures(manifest)`
+  lists the pages to open, and `allow` exempts a figure by anchor with a
+  stated reason. The rule page shows the test to add; the playground runs it
+  at a laptop and a phone viewport.
+
+- **Rule V8: a diagram is no wider than the lesson column.** A `<Diagram>`
+  that lays out wider than `columnWidth` px (707 unless the course sets
+  `rules.V8.columnWidth`: the lesson column at a 1366px-wide window) gets a
+  `dia-too-wide` warning naming the lesson file and the diagram `id`. Only
+  the rendered page knows a diagram's width (a wrapper component's nodes
+  never reach the manifest walk), so `Diagram.astro` marks a diagram over
+  its limit with `data-diagram-too-wide`, `astro build` reports each mark
+  as it finishes (`oversizedDiagrams` in `explico/reference/diagram-fit`)
+  and writes them to `build/render-diagnostics.json`, and `astro dev`
+  prints the same warning as the page renders. `content warnings`,
+  `content diagnostics`, `content status`, `content context` and
+  `content check` list the last build's findings beside the manifest's,
+  under the `render:` source (`render:dia-too-wide`). `warnAboveWidth={false}`
+  still opts a diagram out, and a number in it still sets that diagram's
+  own limit.
+
+- **Build-time measurement of a formula and of a label.**
+  `explico/reference/katex-measure` exports `measureFormula(latex, fontPx)`:
+  the width, height and depth of notation LaTeX as KaTeX lays it out, from
+  KaTeX's own layout tree and font metrics plus the widths `katex.css`
+  adds, each glyph rounded up to a whole pixel as Chromium on Linux draws
+  it. It is never narrower than Chromium's width and at most a few pixels
+  wider, which `tests/reference/katex-measure.test.ts` holds against 92
+  formulas measured in Chromium (`playground/scripts/measure-katex-widths.ts`).
+  `explico/reference/text-measure` exports `textWidth` and `wrapText`,
+  which measure text in DejaVu Sans, the widest common system font, from
+  an advance-width table generated from the font
+  (`scripts/gen-text-widths.mjs`). `renderNotationFormula` also returns the
+  `latex` it rendered, glyphs bound.
+- **A page-local notation key that equals a shared one warns**
+  (`local-shadows-shared`). The local entry wins on its page, so
+  `[[motion.range]]` meant "Length of the field" there and "Range" in the
+  glossary and on every other page, and nothing said so. None of the
+  courses on the maintainer's machine has such a key.
+- **`contentCheck` takes `lessons`, several ids each checked.** The
+  playground's `content check a b` checked `a` alone and exited 0 with `b`
+  silently ignored, so an agent could take both as passed; its wrapper now
+  passes every id, and `context`, `status`, `rules`, `warnings` and `new`
+  refuse an argument they do not take. A course's own `scripts/content.ts`
+  can do the same by passing `lessons: args.positionals`.
+- **A symbol in a card from another lesson explains itself, even one this
+  page never uses.** The equation a `[[lesson/slug#eq-…]]` reference
+  previews brought its symbols along, but only those this page explained
+  opened a card: on "Projectile Range", ρ and φ in equation (1.1.3) of
+  "Position and Coordinate Systems" did nothing. Each now opens the card
+  that lesson gives it, read off the page the preview came from, and one of
+  that lesson's own symbols says "Defined in … · means this only there", as
+  a carried card always did (K6). Such a card is kept, remembered and
+  carried like any other: a shared symbol becomes the page's own card
+  wherever a page explains it. A kept card of a page's own symbol now names
+  the page it was read off in its carrying mark (K8), not the page it
+  was opened on. `card-fetch.ts` `markForeign` marks a card built from
+  another page (`data-card-from`, `data-card-from-slug`); nothing in a
+  course changes (`NotationLayer.astro`, `FloatRefLayer.astro`,
+  `card-manager.ts`).
+- **Index entries and derived cards** (rule N23). A notation entry whose
+  `latex` is a subscript on an empty group (`"{}_0"`, `"{}_x"`, quoted in
+  YAML) explains that subscript on every symbol of the page that has a card of
+  its own: `\mathbf{v}_0` becomes one target with a **derived card**, composed
+  by the build (`derived-notation.mjs`) and keyed `<base>.sub.<index>`. Its
+  title is the index entry's new `reads` with `{base}` replaced by the base's
+  label ("Velocity vector evaluated at t = 0"; the default is "`<label>` of
+  `{base}`"), its summary the index entry's `meaning`, its formula the index
+  entry's `formula` with `{base}` bound to the base symbol, so the base's card
+  is one level deeper, and its units the base's. A derived card is never
+  listed; an index entry is listed with a square for the symbol (`\square_0`,
+  like an operator entry) and takes no `units`, `dimensionless`, `range` or
+  `fixedIndex` — the loader rejects them, and rule N19 skips it; `reads`
+  belongs to an index entry only, names the symbol with `{base}`, and is plain
+  prose (no `$`, `\` or backtick). A table header's screen-reader label reads
+  the derived title, so `v_x` and `v_y` columns differ. A whole form or a
+  family still wins over an index entry.
+- **`range` and `fixedIndex` on a notation entry** (rule N23). `range` is
+  the set a running index letter runs over, as LaTeX (`"1, \\dots, n"`); the
+  card and the glossary show it as "Runs over …". `fixedIndex: true` says a
+  letter, as an index, is a label (a component, a size), or that an indexed
+  entry's index is fixed, so it is no family and lends nothing.
+- **Derived cards wherever page math renders**: a lesson body, an
+  assessment, lab math and a `<Diagram>` formula; never a notation formula,
+  which resolves against its own card's table. A lab composes them when it
+  passes the table `labMathScope` returned to `renderLabMath` unchanged:
+  `labMathScope` ties the table to its page (`bindScopeToPage`), and
+  `renderLabMath` and `Diagram.astro` register the derived cards they use
+  (`registerPageDerivedNotation`), which `derivedNotationForPage` composes
+  for the page's payload. `renderNotationFormula` takes `{ derive }` and
+  returns `derived` and `indices`; `splitMixedContent` takes `{ derive,
+  derived }`.
+- `resolveMathGlyphs` takes `derive` (page math sets it) and returns
+  `indices`, how each indexed symbol is explained, and `derived`, the derived
+  cards it used; an unresolved item carries `lenders`, the indexed entries
+  with its base, and a decoration `wholeFormExplicit`. `math-glyphs.mjs`
+  exports `derivedNotationKey`, `indexOfEntry`, `indexDisplayLatex`,
+  `entryHasIndex`, `baseSymbolLatex`, `derivedNotationLatex` and
+  `isRunningIndexLetter`; a glyph-table row may carry `fixedIndex`.
+- **`accent-swallowed`** (rule N22, a warning): an `\explain{beta}{\hat{\beta}}`
+  around a decorated form counted as its whole form even though the `beta`
+  card never mentions the hat. It is reported now, the decoration twin of
+  N23's `index-swallowed` (`consistency.ts` `checkAccentExplained`).
+
+### Changed
+
+- **A symbol of a page's own has a card key scoped to its page**: the card
+  for `notation.local`'s `theta-star` on "The Optimal Launch Angle" is
+  `[data-card-key="notation:theta-star@projectiles/optimal-launch-angle"]`,
+  not `notation:theta-star`, so a carried card (K5) never stands for
+  another page's symbol of the same name (K6). A shared symbol's key
+  is unchanged. Browser tests that select a local symbol's card by its key
+  need the scoped form; the page's slug comes from `NotationLayer`'s new
+  `page` prop, which `LessonFooter.astro` passes. A card's memory saved
+  under the old key is not restored.
+
+- **Every card layer registers on every course page**, with nothing of its
+  own to show or not, so a card carried in can be built there: the
+  citation and abbreviation layers no longer wait for a marker on the page,
+  the reference layer for a reference or a numbered float, and a page
+  without notation still renders the notation card's template, in a
+  hidden `.notation-layer`. The page's notation layers — the page's own and
+  the glossary's panel — share one card source. A symbol in a card cloned
+  from another page opens this page's card only for a shared symbol, never
+  for one of this page's own.
+
+- **A reference card's "Go to …" link sits in a row of its own**,
+  `p.float-ref-panel-links`, which a kept card's "Opened at" link joins
+  (K7). Course CSS that placed `.float-ref-panel-jump` as a grid item of
+  `.float-ref-panel-body` targets the row instead.
+
+- **The side controls row's switches share one class**,
+  `.explico-side-switch` (its knob `.explico-side-switch-knob`), which
+  replaces `.explico-keep-left` and `.explico-keep-left-switch`. Course CSS
+  that styled "Article left" by those names targets the new ones; the
+  `[data-keep-article-left]` hook is unchanged, and "Carry cards" has
+  `[data-carry-cards]`.
+
+- **A reference card names its float by its number in the title**:
+  "Equation (1.1.3)", "Figure 2.2.1 · Range vs. launch angle explorer". The
+  column that repeated the number beside the content is gone, an equation's
+  too, so the content takes the card's width, and the "Go to …" link no
+  longer repeats the number either: "Go to the equation in Position and
+  Coordinate Systems", "Go to the table". A course's browser test that reads
+  the link by its old name ("Go to figure 2.1.1", "Go to equation (1.1.3)")
+  needs the new one; `[data-panel-number]` moved into the title and keeps
+  its text, except an equation's, which reads "Equation (1.1.3)" instead of
+  "(1.1.3)" (`FloatRefLayer.astro`).
+- **A figure card's picture is 80% of its width in the article**, and the
+  card is as wide as the picture: the caption wraps under it instead of
+  widening the card. A figure from another page is laid out unseen in this
+  page's article and measured there (`FloatRefLayer.astro`,
+  `figureCardWidth`).
+- **Every card's text is 14 px** (`--sl-text-sm`, the article's caption
+  size). The notation card alone was 90% of the article's text, 14.4 px;
+  its units line is now 13 px (`--sl-text-xs`), a step below the text
+  (`NotationLayer.astro`).
+- **"Keep the article left" reads "Article left"**, so it and the width
+  menu fit one row at the top of a 1920 px window's side column; its
+  tooltip still says it in full. The switch keeps
+  `[data-keep-article-left]`, inside a new row, `.explico-side-controls`,
+  which now holds the fixed position.
+- **A heading's chain icon shows on hover in a narrow window too.** Below
+  `50em` it used to show on every heading, a rule meant for phones that a
+  narrow PC window matched as well. It now shows on every heading only on a
+  touch screen (`hover: none`); with a mouse it appears on hover at any
+  width (`styles/global.css`).
+- **A card's footer links are outline buttons in the site's accent
+  colour.** "Go to the full definition", "Go to the source", "Go to the
+  reference list", "Go to the glossary" and a reference card's "Go to …"
+  lose their underline and take a hairline border, tinted on hover. The
+  card layer sits outside the article, so these links never got the site's
+  link colour and showed the browser's default blue. They are still links,
+  with the shared class `hover-panel-action` (`HoverPanel.astro`). A link
+  inside a card's text keeps its underline.
+
+- **The header's download link is a Download menu** (`LessonExportActions.astro`).
+  The Download button opens a native popover listing the scopes that
+  contain the page, one row each ("This chapter", "This part", "Whole
+  course", with the chapter's, part's or course's name), and the formats in
+  columns (HTML, and a chapter's PDF and LaTeX source with
+  `lessonExports.latex`), each with its size from `downloads/index.json`; a
+  download the build did not write is left out. The Print button stays
+  beside it. A link's accessible name names its scope and format
+  ("Download this chapter as standalone HTML"); the button is "Download
+  this page". During `astro dev` every cell but a chapter's HTML says it is
+  built when the site is deployed.
+
+- **Every page offers the print button and the Download menu**, not only
+  the chapters: the landing page, each part's page, the glossary and every
+  other page in the manifest's `pages` (`LayoutSocialIcons.astro`). Such a
+  page downloads as part of its part's and the course's files (see
+  Breaking). Ctrl+P on those pages now also gets the print preparation:
+  links moved onto `canonicalBaseUrl`, off-screen figures drawn. The print
+  button's accessible name says "this page" instead of "this lesson"
+  ("Print or save this page as PDF"), and the group's is "Page exports".
+  The `lessonExports` setting keeps its name.
+
+- **A diagram's boxes are sized from what they hold.** A node is as wide
+  as its formula or its label, whichever is wider, plus an inset. The label
+  is measured in DejaVu Sans and wrapped evenly to a box of at most 220px;
+  the formula is measured from KaTeX's layout at the size it renders
+  (KaTeX's own 1.21em of the 13.6px label; `katex.css` is unlayered, so the
+  component's `font-size: 1em` for it never applied and is gone) and never
+  wraps, so a wide one widens its box and the label wraps to it. Each glyph
+  counts as the wider of the two ways a browser draws it: hinted at a
+  whole-pixel size and rounded, as Chromium on Linux does, or at its exact
+  advance, as macOS and iOS do. Glyphs KaTeX has no metrics for (`\iint`,
+  `\iiint`, `\oiint`, …) are measured too. The height follows from the
+  lines of text and the formula's own height. Before, the box was
+  estimated from the formula's character count alone, ignoring the label,
+  so a label could wrap past its box or spill out of it in a wide system
+  font. A node's `width` without a `height` now takes effect: the label
+  wraps inside it and the height follows (both used to be needed). A
+  `width` narrower than the node's formula, or a `height` shorter than what
+  it holds, is raised to fit; either used to cut the formula off. A
+  diagram wider than its V8 limit is laid out again with its labels wrapped
+  narrower, down to 120px boxes, before it is reported. Diagrams change
+  size, so screenshots of them need re-shooting. The node label carries
+  `text-wrap: balance`.
+
+- **`<Diagram warnAboveWidth>` defaults to the course's column (rule V8),
+  707px, instead of 800px**, and its warning is a `dia-too-wide` diagnostic
+  with the lesson file rather than an untagged `console.warn`.
+- **The manifest schema is now v30 (additive).** `lessons[].headings[].text`
+  is the text a reader sees — a formula as it reads, a `[[key]]` term as its
+  label — and `math: true` marks a heading with inline math. Slugs are
+  unchanged. Each choice option in `assessmentContent` carries
+  `labelSegments`, its label split into text and math like
+  `promptSegments`.
+- **The anchor of a heading with math reads as the heading does.**
+  `## The range $\explain{motion.range}{R}$ in a heading` was anchored
+  `#the-range-explainmotionranger-in-a-heading`, in the address bar, a copied
+  link, a `[[sec-…]]` reference and both exports; it is now
+  `#the-range-r-in-a-heading`. A Greek letter slugs as LaTeX names it, so a
+  heading whose math holds no markup keeps its anchor
+  (`$e^{\lambda\cos(u)}$` is still `…elambdacosu`); one with `\explain`,
+  `\frac` or the like gets a new one. No heading in the courses on the
+  maintainer's machine changes.
+- **Two notation formulas may name each other, local or shared.** A cycle
+  through `notation.local` formulas failed with `reference-cycle`, while the
+  same cycle through shared formulas passed. Formulas no longer count toward
+  a cycle for either kind: `confidence-level` (γ = 1 − α) and
+  `significance-level` (α = 1 − γ) are both right, and so are three entries
+  that each show the one model equation they appear in (data-science-I and
+  time-series do both). A cycle through meanings and bodies still fails.
+
+
+### Fixed
+
+- **A nest of `\left … \right` brackets grows outward in the LaTeX book and
+  PDF, as it does on the website.** The KaTeX patch behind rule N17 sets
+  `\delimitershortfall` to `-1pt`, but `explico.cls` kept TeX's 5pt, so the
+  exports drew nested pairs at one size. The class now sets it too; rebuild
+  the PDF to pick it up.
+
+- **A formula's notation marker links to its entry in the LaTeX book.** A
+  `\explain{key}{tex}` in a part or course PDF now links to the key's entry in
+  the book's notation appendix, when the book has one; a chapter's own PDF,
+  which has no appendix, still prints the TeX. An entry's defining formula in
+  the appendix links the other entries it names, not its own symbol. Where
+  markers nest, as the resolver writes `\dot{x}`, only the outermost with an
+  entry links, since a link inside a link breaks the PDF's tagging. A marker
+  in a heading, caption or title, or inside a link, prints its TeX without a
+  link, since a link there breaks the build; a diagram's labels print theirs
+  too. The class defines `\ExplicoNotation` (`explico.cls`).
+
+- **A card wider than the article column stays clear of the side panels.**
+  A figure card is up to `80ch` wide, which is wider than the article
+  column at 1200–1280 px with both panels open. Such a card was centred in
+  the whole window, and the navigation painted over its left part. Cards
+  are now placed between the navigation and the rail, the room a dragged
+  card already kept to, and a card wider than that room is narrowed to it
+  (`components/card-placement.ts`, `cardBand`).
+- **The splash hero prints its light image.** Print is always light, but a
+  reader in dark mode printed the hero's dark image, whose pale strokes
+  vanish on white paper (`styles/global.css`).
+- **A declared operator's card binds only that operator.** The glyph
+  resolver fingerprinted every `\operatorname{…}` and `\mathop{…}` by its
+  node type alone, so they all looked alike (`reference/math-glyphs.mjs`,
+  `signatureParts`). A page's one operator card wrapped every other declared
+  operator on the page: `\operatorname{Cov}` opened the
+  `\operatorname{Var}` card, with no diagnostic. Two operator cards on one
+  page failed the build with `ambiguous-canonical-notation`. A declared
+  operator is now fingerprinted by its letters with spacing dropped, the
+  name rule N8 already uses, so `\operatorname{arg\,max}` and
+  `\operatorname{argmax}` are still one operator. `\mathop{\mathrm{Var}}`
+  and `\operatorname{Var}` stay distinct. A course that put a name on
+  `rules.N8.allow` only because its card was refused can give the card back
+  and drop the name.
+- **The engine's two hooks into Starlight's mobile menu follow the 0.42
+  markup**, where the old selectors would match nothing: the menu button
+  rises above the raised header as `.sl-menu-button` (`global.css`), and
+  open cards hide while the menu is open through
+  `body:has(#starlight__sidebar:popover-open)` (`HoverPanel.astro`).
+
+
+- **Copy LaTeX no longer glues a command to the next letter.**
+  `stripNotationMarkers` (`reference/math-glyphs.mjs`) joined the two sides
+  of a removed `\explain{…}{…}` or `\slot{…}{…}` marker with nothing
+  between them, so `\times\explain{k}{m}` copied as `\timesm`,
+  `\left\lVert\explain{k}{X}` as `\left\lVertX` and
+  `\explain{a}{\lambda}\explain{b}{u}` as `\lambdau`: undefined commands to
+  any TeX that pasted them. A space now separates a control word from a
+  letter on either edge of a removed marker. Every copy button (an
+  equation's, a notation card's, a lab's) and the `data-latex` of inline
+  math take the fix.
+- **The Print button no longer waits forever for a lazy image** the reader
+  never scrolled to: it switches such images to load now and opens the
+  print dialog after at most five seconds of waiting for images.
+- **`content check` points a render error at its line in the file.** It
+  rendered a lesson's body with the frontmatter removed and its `import`
+  lines deleted, so an error was reported that many lines too early
+  (line 4 for an error on line 16, which `astro build` reports as 16).
+  The frontmatter is now blanked with spaces, as Astro's MDX plugin does,
+  and an `import` line is emptied, not removed (`compiler/cli.ts`,
+  `lessonSource`).
+- **`validate:content` and `content check` reject what `astro build`'s
+  collection schemas reject.** The manifest walk read content with its own
+  checks and never applied the schemas in `content-config.ts`, so a notation
+  `meaning` with a `$`, a source `type` of `web` or `studyMinutes: [10, 5]`
+  passed both and then failed the build with `InvalidContentEntryDataError`.
+  The schemas now live in `explico/compiler/content-schemas`, which
+  `content-config.ts` and the manifest both use, and every record that does
+  not match is a `content-schema` error at the field's line (invariant
+  `content-schema`). In the other direction, a shared notation entry may now
+  leave out `aiAssisted` and `alignment`, as the schema already allowed: the
+  walk threw "aiAssisted must be a boolean" where the build used the
+  defaults. The plain-prose message for a notation `meaning` also says how
+  to write an amount of money.
+- **An equation or a float in a list item, a quote or a `:::note` aside
+  is numbered the same way by the manifest and the page.** The manifest
+  counted every `$$…$$` in a lesson's text, and every `<Table>`, `<Figure>`
+  and `<Diagram>`, while the page numbered only those at the top level and
+  in a `<Memo>`, `<ShortNote>` or `<Fold>`. One unlabelled equation in a
+  list item, a `>` quote or an aside, or an inline `$$x$$` in a sentence,
+  made the next labelled equation fail the build with "Inconsistent equation
+  numbering … recompile the manifest", which never helped. Now both count
+  the lesson's flow, list items and quotes included, and neither counts an
+  aside, which is illustrative like `<Aside>` (a `<Table>` or `<Figure>` in
+  one fails the build, naming the aside). A display equation is a `$$`
+  block whose fences sit on lines of their own, as remark-math reads it;
+  `$$x$$` inside a sentence is inline math (`reference/equations.mjs`,
+  `reference/keyed-jsx-floats.mjs`). `content check` now parses `:::`
+  directives as the build does, through the new `remark-directive`
+  dependency.
+- **The PDF numbers citations as the page does.** The page lists a source
+  once per locator it is cited with (`[@s]`, `[@s; ch. 3]` and
+  `[@s; eq. (4.21)]` are three entries, [1], [2] and [4]), but the LaTeX
+  export gave every entry of a source the same `\bibitem` key: LuaLaTeX
+  reported it multiply defined, and every `\cite` of it printed the last
+  entry's number, so the PDF read [4] where the page read [1]. A source
+  cited with several locators now gets one key per entry (`s/cite-4`), a
+  source cited once keeps its id, and `\cite` no longer repeats the
+  locator, which the entry already gives (`exports/latex/serialize.ts`).
+- **A heading can no longer take an anchor the page already uses.**
+  `## References` on a page that cites a source gave the page two
+  `id="references"` elements (the author's heading and the generated
+  References section), and `## Tab totals` beside `<Table id="totals">` two
+  `#tab-totals`: every link went to the first, "On this page" listed
+  References twice, and the LaTeX export defined the label twice. Such a
+  heading now fails `validate:content` as `heading-anchor-collision`
+  (keyed-floats invariant), naming what holds the anchor: a keyed equation,
+  table, figure, diagram, example set or knowledge check, a `<Memo>` or
+  `<ShortNote>`, or the generated References section
+  (`reference/sections-validate.ts`, `validateHeadingAnchors`).
+- **A heading with math reads as it renders everywhere it is named.**
+  Astro lists a heading by all the text in it, and KaTeX writes a formula
+  three times (MathML, its LaTeX annotation, its glyphs), so
+  `## The range $\explain{motion.range}{R}$` showed as "The range
+  R\explain{motion.range}{R}R" in "On this page", the heading link's
+  screen-reader label, the "Link copied" bubble and the copied link. Each
+  now reads "The range R": "On this page" takes the manifest's text for a
+  heading with math (`LayoutPageSidebar.astro`), the link's label skips the
+  annotation and the glyph copy (`rehype-heading-anchors.mjs`), and the
+  copied link and a card's "Opened at" read the heading through
+  `readableText`. The manifest's `lessons[].headings[].text` is the text a
+  reader sees, a `[[key]]` term as its label, and is what an unnumbered
+  `[[sec-…]]` quotes; a heading's anchor is unchanged. Rule S1 measures the
+  same text: `\explain{…}{…}` no longer counts against the limit.
+- **The site search indexes a formula once, as it reads.** Pagefind indexed
+  KaTeX's MathML and its LaTeX annotation beside the glyphs, so a search for
+  `dfrac` or `explain` matched every page with a formula and the excerpts
+  read "…35.3 m\explain{motion.range}{R} = \dfrac{…". KaTeX's MathML copy is
+  now `data-pagefind-ignore`, in lesson math (`rehypeFailKatexErrors`, the
+  pass after KaTeX), in notation cards and diagrams (`renderNotationMath`)
+  and in lab math (`renderLabMath`).
+- **A knowledge check's options render their math.** An option label went
+  to the page as plain text, so `"$30^{\circ}$"` showed its dollars and
+  LaTeX, and nothing warned. A label's math is now resolved and typeset like
+  the prompt's: rule N4 checks it, `AssessmentRunner` renders it, and the
+  LaTeX and Markdown answer keys typeset it (`assessmentContent` options
+  carry `labelSegments`). Rule N9 still does not apply to a label, so
+  "30 degrees" stays valid.
+- **A reference or a citation in a knowledge check's text fails
+  `validate:content`.** A check renders its prompt, explanation and options
+  as text and math, so `[[projectiles/projectile-range#eq-range]]` or
+  `[@source]` there reached students exactly as written, with no
+  diagnostic. Each is now an `invalid-assessment` error naming the item and
+  the field. The error for a numeric answer's tolerance also says what is
+  wrong: it must be greater than 0, and an exact whole-number answer takes
+  one below one half.
+- **A diagram's labels fit their boxes at any browser font size.** The
+  boxes are measured at build time for 13.6px text, but a label was
+  `0.85rem`, so a reader with a larger default font size (Chrome's "Large",
+  20px) got labels that outgrew their boxes and were cut off, in the
+  playground's own diagrams too. A label is now set in px at the size its
+  box was measured for (`Diagram.astro`); browser zoom still enlarges it.
+  Scaling the whole drawing with the font size was ruled out: WebKit on iOS
+  scales an SVG's geometry but not the HTML in its `foreignObject`.
+- **A part with nothing in it yet no longer fails the build.** A part
+  listed in `course.settings.json` before its directory existed took an
+  ordinal in `parts[]` and a sidebar group, while lessons were numbered as
+  if it were absent; every page built, then the LaTeX export failed with
+  "LaTeX numbers part/… differently from the website". Such a part is now
+  left out of the sidebar and of every part number until it has a chapter
+  or an overview page, with a `part-empty` warning; a part with only an
+  overview page counts in both.
+- **A lesson in a directory no part lists fails `validate:content`** as
+  `lesson-outside-parts`, naming the `parts` entry to add. It used to pass
+  and then fail the build with a message about `remarkNotation` wiring.
+- **A lesson's `draft: true` fails `validate:content`** as
+  `unsupported-key`, with the advice to keep the lesson outside
+  `content/docs/`: Starlight dropped the page from the production build
+  while the sidebar still named it, so the build crashed with "The slug …
+  specified in the Starlight sidebar config does not exist". A chapter's
+  `sidebar.order`, which does nothing, warns as `ignored-key`.
+- **The marker of an open memo the reader cannot see goes to it.** A
+  memo's marker toggles the memo, so on an open memo off screen (one with
+  `defaultOpen`, under `disclosure.memos.defaultOpen: true`, or one the
+  reader left open) a click closed it out of sight: no scroll, no URL
+  change, as if nothing happened. The marker now scrolls to such a memo and
+  sets `#memo-…`; it folds a memo only while some of it is on screen
+  (`Memo.astro`).
+- **A number alias into a short note opens it.** A deep link such as
+  `#eq-2.2.3` to an equation inside a closed `<ShortNote>` was rewritten to
+  the equation's named anchor after the short note had already looked at
+  the address, so the note stayed closed and the target had no size; the
+  named anchor itself worked. The short note now looks again once every
+  script has run (`ShortNote.astro`).
+- **The build warns when a PDF leaves characters blank.** The LaTeX
+  export's fonts have no Greek, CJK or emoji glyphs, and LuaLaTeX only logs
+  a `Missing character` line and leaves a blank, so a chapter with
+  "Ελληνικά" or "中文" in its prose shipped a PDF reading "Ε𝜆𝜆" and "��"
+  with no warning. Each chapter whose PDF misses characters is now named in
+  a build warning with the characters (`exports/latex/compile.ts`,
+  `missingCharacters`).
+- **Pandoc's `[@a; @b]` cites both sources.** The second source was read
+  as the first one's locator, so the page showed one `[1]` and its entry
+  read "Ling et al., … @openstax-college-physics-2e.", with no diagnostic.
+  A `;`-separated part that is only `@id` now starts another citation with
+  its own marker and entry; any other part is still the locator, so
+  `[@a; §1.2; eq. 3]` reads as before. The page, the manifest's citations
+  and the lesson's derived sources share one parser
+  (`citation-format.mjs`, `bracketCitations`).
+- **A diagram edge from a node to itself fails the build** with a message
+  saying how to draw the repetition instead. The layout drew it as a stray
+  line out of the node.
+- **A diagram formula that cannot be bound says why.** The error quoted
+  the same two guesses for every failure; it now gives the resolver's own
+  message (an unknown glyph, a shared base, a parse error). A diagram
+  written straight into MDX gets no notation scope, so none of its symbols
+  can resolve; the error now says so and names `labMathScope`.
+- **An equation in a reference card sits flush in it.** The card's
+  `margin-block: 0` for a displayed equation was inside `@layer
+  starlight.components`, and `katex.css` is unlayered, so KaTeX's `1em`
+  margins won and left air above and below every `[[eq-…]]` preview. An
+  engine test now fails on any layered rule aimed at a KaTeX class.
+- **The LaTeX and Markdown exports punctuate a short caption as the page
+  does.** Each added its own period unless the short caption ended in one,
+  so `short="Is it zero?"` printed "Is it zero?." in the PDF's caption,
+  the Markdown caption line and both alt texts. They now use the page's
+  `captionTitle`, which keeps a closing `!`, `?`, `…`, `:` or `;`.
+- **LaTeX's numbering and reference habits fail with the explico form.**
+  The gate parses every span as inline math, so `\begin{align}`,
+  `\begin{equation}` or `\tag{A}` in a `$$…$$` block was reported as "can
+  be used only in display mode". The error now says the block already is
+  the display, numbered from its `\label{eq:key}`, and names the inner
+  environment to use (`aligned`, `gathered`, `alignedat`) or says to drop
+  the wrapper or the `\tag`. An unprefixed `\label{…}` names
+  `\label{eq:key}`, and `\eqref{eq:first}` or `\ref{…}` in math names
+  `[[eq-first]]`. In prose, where MDX failed on its braces with "Could not
+  parse expression with acorn", `validate:content` now reports it first
+  (`eq-latex-ref`).
+- **The N8, N10 and N14 messages name the setting to use.** Each told an
+  author to allowlist a term in `operators.allow`, `romanLabels.allow` or
+  `abbreviations.allow` "in course.config.ts", keys that raise
+  `config-deprecated-key`. They now name `rules.N8.allow`,
+  `rules.N10.allow` and `rules.N14.allow` in the course config
+  (`course.config.ts`, or the `course.settings.json` it reads), as the
+  README and the doc comments do.
+- **A course rule reads what a reader sees: a link's text, not its
+  address, and a caption.** A `forbid` pattern matched inside
+  `[a page](https://example.org/basically/)` and skipped
+  `<Table caption="This caption says basically.">`. Link destinations and
+  `[ref]: https://…` definitions are now blanked from the prose surface
+  (so N9 and N14 no longer read an address either), and the text of a
+  `caption`, `short`, `title` or `label` prop is matched as a paragraph of
+  its own under the `paragraph` and `prose` scopes.
+- **`content check <lesson>` fails on a fault in a shared notation entry
+  the lesson shows**, as `validate:content` does. A formula of a shared
+  entry naming an unknown key is reported against the entry's own file, so
+  the per-lesson check left it out and printed `ok` for every page that
+  showed the card.
+- **Money that remark-math would read as math fails `validate:content`**
+  (`currency-dollar`). remark-math pairs any two `$` on a line, so
+  `pay $5 ~ $6` showed "pay 5 6" with every gate passing (the gate's own
+  span scan follows Pandoc and skipped the pair), and "between $5 and $6"
+  failed the build on the letters of "and". A pair whose content starts with
+  a digit and ends in a space or runs into a digit is now an error that says
+  to write `\$5 to \$6`. None of the courses on the maintainer's machine
+  has one.
+- **A table one row over `truncateAfter` shows whole.** Truncating it hid
+  that one row behind a "… 1 more row …" line just as tall, and the reader
+  had to click to see it. A table now starts truncated only when that hides
+  two rows or more (`table-truncation.ts`).
+- **A pinned card whose section the reader collapses waits out of sight.**
+  It stayed where it stood, over the text that moved up into its section's
+  place, and scrolled with the page as if still attached. It now hides,
+  keeping its size, while its trigger is folded away, and comes back beside
+  the trigger when the section or fold opens. A closed `<details>` keeps
+  its content's last boxes in current browsers (`content-visibility:
+  hidden`), so the card manager asks `checkVisibility()`, not
+  `getClientRects()`, whether the trigger is folded.
+- **N9 quotes a hand-typed sub/superscript whole.** The pattern took three
+  characters, so `2^10` was reported as "2^1" and `e^{i t}` as "e^{". It
+  now takes the whole runs on both sides, or a braced group.
+- **A folded section counts the numbered floats and equations inside a
+  short note.** Everything in a `<ShortNote>` counted as part of the note,
+  and the note itself was never counted, so a section whose table or display
+  equation sat in one said only "Hidden here: 1 paragraph". A numbered float
+  or equation in a short note now counts, and a float with a short caption
+  is named, as in a `<Fold>`; the note's prose still belongs to its
+  paragraph.
+- **Three notation errors say what to write.** A glyph two page entries
+  share ("structurally identical LaTeX") now cites rule N4 and says to write
+  one of them differently or keep one off the page, and that `\explain`
+  does not lift the clash (it never did). An invalid key says what it most
+  likely meant: `[[motion.range|reach]]` that a reference takes no link
+  text (write `[[motion.range]]`), `[[dia-My_Diagram]]` that a diagram's
+  id is lower-case kebab-case, anything else the key grammar.
+- **An unclosed `[[` fails `validate:content`** (`malformed-reference`, at
+  its line). Only the render caught it, and `content check` printed Astro's
+  whole error object (its syntax tree, `cause`, `place`) above its own
+  line; `renderLesson` now drops that log and carries the error's line and
+  column into its diagnostic.
+- **"Opened at" quotes a section the course shows unnumbered**, as a
+  reference to it prints: `Opened at “What this chapter uses”`, not the
+  bare title (`sectionPlace`).
+- **A caption prop written as an expression warns**
+  (`fig-unread-prop`, `tab-…`, `dia-…`, `ex-…`). `<Figure short={"…"}>`
+  rendered its short caption, but the manifest reads only a quoted prop, so
+  the float's `[[…]]` card, a copied link, a folded section's line and the
+  "Figures and tables" page named it without one, silently.
+- **A float id the manifest rejects is named as such at render.**
+  `<Diagram id="My_Diagram">` failed `validate:content` with
+  `dia-invalid-key`, and then the render (and `content check`) said "Stale
+  Explico manifest … Recompile the manifest before rendering", which no
+  recompile fixes. It now says the id is not a valid key and to fix it.
+- **A section reference to a part's page says why it cannot resolve.**
+  `[[motion#sec-…]]` failed with "names lesson motion, which does not
+  exist", though the page exists. It now says the page is not a chapter, a
+  section reference reaches a chapter's top-level headings only (rule S10),
+  and how to link the heading with a Markdown link instead.
+- **`remark-citation.mjs` is a text file again.** It used a literal NUL
+  character as a key separator, so git showed every change to it as
+  `Bin … bytes` and grep skipped it. It now writes `\u0000`, and a test fails
+  on a NUL byte in any source, doc or content file.
+- **A PDF table's caption no longer sits on the table.** With
+  `\DocumentMetadata`, which every export's `main.tex` has, the kernel's
+  tagging code sets each caption itself, so none of the class's
+  `\captionsetup` applied: a table's caption, set above it, kept the
+  kernel's space above and none below, and its top rule ran about 1pt under
+  the caption's descenders. A table's caption now gets the same space on both
+  sides (8pt), and every caption the class's form: small type, and a quad
+  after "Table 2.1.1" instead of a colon, as on the web page.
+- **Prose in another script reaches the PDF.** Under LuaLaTeX, a Greek
+  word, Cyrillic, Chinese, Japanese, Korean and emoji come from fallback
+  fonts, the first the build machine has (CMU Serif from TeX Live's
+  `cm-unicode`, now in `texlive-packages.txt` as optional, then Noto Serif or
+  DejaVu Serif; Noto CJK or Fandol; Noto Color Emoji), loaded only for a
+  document that needs them (the class option `scripts`). A Greek word was set
+  in math italic, letter by letter, and an accented letter, Chinese and emoji
+  were blank. A Greek letter on its own stays a math symbol, as in a caption's
+  "polar coordinates ρ and φ".
+- **pdfLaTeX no longer fails the whole build on a character it cannot set.**
+  `EXPLICO_LATEX_ENGINE=pdflatex` stopped at "Unicode character έ not set up
+  for use with LaTeX" after every page had rendered. The character now stays
+  blank and the build warns, as under LuaLaTeX without a fallback font.
+- **A LaTeX compile no longer reruns until it gives up.** latexmk counted
+  luaotfload's shared font caches as inputs; the build's parallel compiles
+  rewrite them, so a compile could see its inputs change on every run and fail
+  with "'lualatex' needed too many passes". The build and the shipped
+  `latexmkrc` ignore them, and a failure latexmk reports itself now shows
+  latexmk's words instead of the log's last lines.
+- **Braces in prose fail `validate:content`, at their line** (`mdx-expression`,
+  invariant `prop-text`). MDX reads `{a}` as JavaScript; both checks passed
+  it, and the build failed with "a is not defined" in a compiled chunk, with
+  no file or line. The message says to write `\{a\}`, or `$\{a\}$` for a set.
+  None of the courses on the maintainer's machine has one.
+- **An equation wider than the column shows that it goes on.** On a phone a
+  wide display equation scrolls sideways inside its box with no scrollbar,
+  and it simply stopped mid-formula beside its number. The edge it is cut
+  at now fades (`data-overflow` on `.katex-display`, set while it overflows
+  and kept current as it scrolls); focus and print show it whole.
+- **A part page's stats read apart in search and to a screen reader.** They
+  were spans in a row, separated only by space on screen, so the search
+  index read "Part 1 of 23 chapters8 numbered equations". They are a list
+  now (`PartOverview.astro`), and search reads "Part 1 of 2. 3 chapters."
+- **A power or a mark no longer breaks a whole form** (rule N23).
+  KaTeX parses `v_0^{2}` as one node with the power, so it never matched the
+  entry `v_0`: only the letter was highlighted, and where the letter had an
+  entry of its own the card was wrong (`\sigma_k^2` opened the population
+  standard deviation). The whole form is matched and wrapped now, the power
+  outside it; a mark (`v_0'`) stays rule N22's. A whole form inside another
+  whole form's subscript keeps its own card too: `T_{\mathrm{opt}}` in
+  `B_{T_{\mathrm{opt}}}^{\mathrm{dirty}}` is one target, not a highlighted `T`.
+  Authors' `\explain{key}{v_0}^{2}` workarounds still work.
+
+
+## [0.12.0] - 2026-09-28
+
+### Breaking
+
+- **Every symbol a figure shows opens its notation card, and the build
+  checks it** (rule V3, rule N4). Two checks fail a lab that draws math with
+  KaTeX itself, whose symbols have no card:
+  - **`lab-katex-direct`** (error, rule V3; `reference/lab-katex-validate.ts`,
+    in `diagnostics.figures`): `pnpm validate:content` follows each lesson's
+    relative imports to the course's components and fails a file that
+    imports `katex` (not a type-only import, not the stylesheet), naming the
+    chain of imports that reaches it. V3 now has a check, so it counts as
+    partly enforced.
+  - **`astro build` fails a figure's unbound symbol**: at `astro:build:done`,
+    every letter KaTeX drew inside a `figure.keyed-figure` (its tools
+    included) must sit in a `[data-notation-key]`; upright text
+    (`\text{}`, `\mathrm{}`, a named operator such as `\sin`) is exempt
+    (`reference/figure-symbols.ts`, `assertFigureSymbolsBound`).
+- **`setFigureState` takes no symbol typed as text.** A run is a string or
+  `{ math }`; the italic (`{ text, italic: true }`), plain `{ text }` and
+  subscript (`{ sub }`) runs are gone, and one passed anyway throws, naming
+  the fix. `FigureStateRun` is `string | { math: RenderedLabMath }`, so
+  `astro check` fails an old run.
+- **A page that is not a chapter numbers nothing, and `validate:content` says
+  so** (rule S10, locked). On the landing page, a part's overview page, or
+  any other page outside a part directory, `pnpm validate:content`
+  (`reference/gate-non-chapter-pages.ts`) fails `<Table>`, `<Figure>`,
+  `<Diagram>`, `<CompactExamples>`, `<AssessmentSet>`, a lab (a component
+  imported from a `labs/` module, or any `client:*` island) and
+  `\label{eq:…}` (`non-chapter-float`); `notation.local` and
+  `notation.suspend` (`non-chapter-local-notation`); and `$…$` or `[[…]]` in
+  `hero.title`, `hero.tagline` or a `<PartOverview chain>` step, which print
+  literally (`non-chapter-plain-text`). A `<Diagram>` rendered there
+  unnumbered before, and `<Table>` and `<Figure>` threw at render;
+  `remarkNotation` now fails the same blocks and labels at render, naming
+  S10. Link the chapter's float instead: `[[<chapter>#tab-<key>]]` shows it
+  in its card.
+- **Math on a page that is not a chapter binds like a chapter's** (rule N4,
+  rule S10). Every symbol needs a `[[key]]` or an `\explain` on the page, or
+  the build fails; plain `$v$` on a part page used to render with no card
+  and no check. The text and math gates (rule N4, rule N8, rule N9,
+  rule N10, rule N12, rule N14, rule N22, and a course's `X` rules) and
+  per-place waivers now scan these pages too.
+
+### Added
+
+- **`renderLabMath(template, scope, { display: false })`** renders inline lab
+  math — a `.katex` with no `.katex-display` — for a formula that sits in a
+  line: a legend entry, an axis title, a control label. It never scrolls.
+  `RenderLabMathOptions` is exported; the default stays a display equation.
+- **A `{ math }` run for the caption's live clause.** `setFigureState`
+  writes a `RenderedLabMath` from `renderLabMath(…, { display: false })` as
+  `span.float-caption__math`, so "Shown for v₀ = 20 m/s" names the lesson's
+  own `v₀`, which opens its card.
+- **`unboundFigureSymbols(html)`** (`explico/reference/figure-symbols`) lists
+  the figures in an HTML string, and the symbols in each, that KaTeX drew
+  outside a notation binding. A course's browser test runs it on a hydrated
+  figure's `outerHTML`, which also holds what an island draws only in the
+  browser; the playground's `labs.spec.ts` does.
+- **A link to a chapter shows the chapter's full title as its tooltip.** A
+  Markdown link or a JSX `<a href>` the author wrote to another chapter —
+  root-relative, relative, or under the course's `base`, with or without a
+  `#` anchor — gets the chapter's `title` as its `title` attribute
+  (`remarkNotation`, from the manifest's lessons). A link with a title of its
+  own, a same-page anchor, and a `[[…]]` reference, which opens a card of its
+  own, are left alone.
+- **Cards on a page that is not a chapter** (rule S10). A `[[key]]` term,
+  bound math, a citation, an abbreviation and a `[[chapter#tab-key]]`
+  reference open their cards on the landing page and on a part's overview
+  page: `LessonFooter` mounts the notation, citation, abbreviation and
+  float-reference layers there, from the page's own notation bundle (shared
+  entries only). The manifest schema is now v25: `pages` lists every such
+  page with its `id` (`index`, `motion.index`), `slug`, `file` and a
+  `notation` bundle of the lesson shape, and `notation.bundles` and
+  `notation.backlinks` carry those pages' ids too.
+
+### Changed
+
+- **The operator baseline drops `\limsup` / `\liminf` and the
+  category-theory `\injlim` / `\projlim` / `\varlimsup` / `\varliminf` /
+  `\varinjlim` / `\varprojlim`.** Only `\lim` stays in `BASE_OPERATORS`
+  (`reference/base-operators.mjs`): the other eight are not "everyone knows
+  this" the way a plain limit, `\max`, or `\min` is, so rule N8's
+  `operator-explained` warning now asks a course that uses one for a
+  notation entry, like any other domain operator. A course that relies on
+  the old baseline can restore it with `rules.N8.allow: ['limsup',
+  'liminf', 'injlim', 'projlim', 'varlimsup', 'varliminf', 'varinjlim',
+  'varprojlim']` in its settings.
+- **A lab's math wrapper never scrolls.** `.lab-math` loses its
+  `overflow-x: auto`, `overflow-y: hidden` and `padding-block`: a display
+  template's `.katex-display` scrolls sideways when it is wider than its
+  box, like a lesson equation, and carries the padding. `.lab-math` keeps
+  its `margin-block` only when it holds display math.
+- **A float's caption line is at least as tall as its buttons**
+  (`min-block-size: 1.5rem` while a `.float-tool` shows, reset in print), so
+  the row never hangs below the line — past a figure's body, or into a
+  table's header — even when a course hides the caption's text.
+- **The local-notation mismatch names what it compared.**
+  `assertLocalNotationParity` says "notation mismatch", names the page's
+  frontmatter `notation.local` and the manifest's bundle for the page, and
+  gives both causes left: a stale manifest, or an entry `validate:content`
+  rejected.
+- **`notationDefinitionsForRenderedPage(manifest, pageId, dependencies)`**
+  takes a lesson's id or a non-chapter page's (`manifest.pages[].id`), and
+  its errors say "on page" instead of "in lesson". The `<Table>` and
+  `<Figure>` missing-number errors name rule S10.
+
+### Fixed
+
+- **An abbreviation glossary entry can be scrolled to.** Its anchor
+  (`#abbr-…`) sat on a `display: contents` wrapper, which has no box, so a
+  direct URL, a full navigation and a same-page click all left the reader
+  where they were. The `id` is on the entry's `<dt>`, with the
+  `scroll-margin-block-start: 5rem` the other anchor targets carry.
+- **On a narrow screen, the header no longer covers Starlight's menu
+  button**, so the navigation opens again on a phone: the button sits one
+  level above the raised header (`starlight-menu-button > button`).
+- **Links on a part overview page and in `<CourseContents>` use the course
+  accent** (`--sl-color-text-accent`) instead of the browser's default link
+  colour, which `.not-content` let through.
+- **Printing no longer breaks a knowledge check that hydrates while the page
+  is prepared for print** (React error #418). A collapsed-content note never
+  goes inside an Astro island: a closed disclosure inside one gets its note
+  after the outermost island, once per target URL, so the folded questions
+  of one check share one note after the check.
+- **A `notation.local` entry that a page uses only by shape** — an operator
+  entry `{}'` for `w'`, as rule N22 suggests — **no longer fails the build
+  as a stale manifest.** A page's own local entries seed its notation bundle
+  (`buildNotationRegistry`), so none is `unused-definition` any longer; the
+  `weak-local` advice still names one the page barely uses.
+- **A `lint-ignore.yml` `<detail>` can name a hyphenated notation key.**
+  `parseLintIgnore`'s line grammar excluded `-` from the detail segment, so
+  `- notation-units:arg-min — …` (or any acknowledgement keyed to a
+  kebab-case notation key, the shape every key in a course that follows the
+  authoring docs' own naming convention takes) never matched the line
+  pattern and `validate:content` threw "expected `- <code>[:<detail>] —
+  <reason>`" instead of loading the file. Only whitespace and the em-dash
+  separator are excluded from `<detail>` now; a bare `-`, `--`, or ` - ` was
+  never valid *inside* a detail on its own (the separator needs the em dash,
+  or the ASCII forms flanked the way the grammar already required), so this
+  only admits what the docstring already promised: "a notation key".
+- **A table inside a worked example no longer reports rule S3's
+  `raw-table-markdown`** (or `raw-table-html`): such a table is
+  illustrative, like an equation there. The scan counts a table only where a
+  `<Table>` would number it, at the lesson's top level or in a `<Memo>`,
+  `<ShortNote>` or `<Fold>` (`scanRawFloats`, `collectRawFloats`), as
+  `structure-rules.md#s3` always said.
+- **A `<Table>` or `<Figure>` nested in a worked example fails with the real
+  reason.** `remarkNotation` names the component it sits in and the edit to
+  make, at its line; the components' own guards name the nesting before the
+  Astro configuration.
+- **A figure never draws a vertical scrollbar.** `.keyed-figure__body` kept
+  `overflow-x: auto`, which computes `overflow-y` to `auto` as well, so a
+  fractional height at a browser zoom scrolled by a pixel; it now clips
+  vertically (`overflow-y: hidden`).
+- **A display equation that just fits no longer scrolls by 2 px.** KaTeX's
+  stacked scripts hang a 2 px spacer outside their box; `.katex-display` (in
+  lesson content and in `.lab-math`) reserves it with `padding-inline: 2px`
+  on both sides, which keeps a centred equation centred.
+- **A `[[key]]` or an `\explain` on a part overview page no longer fails
+  `astro build` after `validate:content` passed.** The page had no notation
+  entries, so the payload invariant found a trigger with no card. Rule S2's
+  "its math and `[[key]]` references render" now holds.
+- **An indented `[[key]]` inside a component of an `.mdx` page reaches the
+  page's bundle.** The reference extractor masked a line indented by four
+  spaces as an indented code block, which MDX does not have, so text
+  indented inside `<Card>` or `<Memo>` rendered a trigger its bundle lacked,
+  and the build failed. A `.md` file keeps CommonMark's indented code.
+
 ## [0.11.1] - 2026-09-28
 
 ### Fixed
@@ -2143,7 +3432,9 @@ 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.11.1...HEAD
+[Unreleased]: https://github.com/danieltuzes/explico/compare/v0.13.0...HEAD
+[0.13.0]: https://github.com/danieltuzes/explico/compare/v0.12.0...v0.13.0
+[0.12.0]: https://github.com/danieltuzes/explico/compare/v0.11.1...v0.12.0
 [0.11.1]: https://github.com/danieltuzes/explico/compare/v0.11.0...v0.11.1
 [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