explico 0.13.1 → 0.15.0

package/CHANGELOG.md

@@ -14,6 +14,993 @@ under **Breaking** below; a PATCH never breaks.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-10-12
+
+### Added
+
+- **Rule D11: a deck is flagged when its chapter changed after it did.**
+  `deck-stale`, an info diagnostic, names a lesson's own deck whose chapter's
+  rule C5 version is newer than the deck's — two files mean the chapter and
+  the deck can drift apart with nothing else to notice it. Scoped to a
+  lesson's own deck; a part's deck covers more than one chapter, so it has
+  none to compare against and is never flagged. `page-versions.ts` gains
+  `deckStaleDiagnostics`; the diagnostic joins `diagnostics.math` beside
+  D1–D10's frame codes. No manifest shape change.
+- **`content help <verb> [--json]`: each verb's contract, machine-readable.**
+  `content help symbol` prints the verb's usage, what it is for, its flags,
+  what it writes, when it exits 1, and the shape of its `--json` as a tree of
+  named types; `--json` prints the same with a self-contained JSON Schema
+  (draft 2020-12). `content help --json` prints the whole reference. The verb
+  table is one source, `src/compiler/cli-verbs.ts` (`CONTENT_VERBS`, from which
+  `CONTENT_USAGE` is now derived, every line ending in `[--json]`);
+  `scripts/agent/gen-cli.mjs` reads the TypeScript report types with the
+  compiler API and writes `docs/authoring/cli-reference.json` and
+  `docs/authoring/cli.md`, both shipped, `--check` in verify and CI. New
+  module `explico/compiler/cli-reference` (`loadCliReference`, `verbHelp`,
+  `schemaOf`, `formatVerbHelp`, `cliReferenceMarkdown`, and
+  `jsonShapeErrors`, which checks a value against one of the schemas).
+  `cli-main` exports the named `--json` types its verbs print beside the
+  reports: `RulesJson`, `EditPlanJson`, `NewJson`, `ErrorJson`.
+- **`content verify [--e2e] [--force]`: a course's one gate before handing
+  work back.** `validate:content` → `content check --changed` → `astro check`
+  (skipped, by name, when `@astrojs/check` is not installed) → the course's
+  `test` script → `astro build`, and with `--e2e` its `test:e2e` script (or
+  `playwright test`). Each step is its own process with its whole output in
+  `node_modules/.cache/explico/verify/<step>.log`; the run prints one line per
+  step, the tail of each failed step's log, and exits 1 on a failure. A pass
+  records the tree it left (git HEAD, the diff against it, the untracked
+  files), and a rerun on the same tree that asks for no more answers from the
+  record without running anything. New module `explico/compiler/cli-verify`
+  (`runVerify`, `VerifyReport`).
+- `runContentCli` takes an optional fifth argument, a manifest already
+  compiled for the course, so a test running many verbs compiles once.
+- **`content release [major|minor|patch] [--write]`: a content release in
+  every course.** `## [Unreleased]` in `content/CHANGELOG.md` becomes a dated
+  `## [x.y.z]` heading and `about.version` becomes `x.y.z` (rule C3), shown as
+  a diff and written with `--write`, like `move`, `rename` and `fix`; the bump
+  defaults to what the section's headings imply (rule C2), and the date is the
+  local one. It was the playground's own `scripts/release-content.ts`, which
+  the shipped `release-content` skill called as `pnpm release:content` in
+  courses that never had it. The playground's `release:content` script is now
+  `content release --write`. New module `explico/compiler/content-release`
+  (`releaseEdit`, `planContentRelease`); new error code `no-changelog`.
+
+### Changed
+
+- `content init-agent` says `new` or `differs from the engine's copy` for each
+  file, where a dry run used to say `installed`; after `--write` every edit
+  verb prints what to run next.
+- `content status` lists at most six of the pages with unreleased changes and
+  counts the rest; `content context` says how many of a lesson's diagnostics
+  sit in its own file and how many in the shared cards it shows (the first is
+  what `diagnostics --lesson` lists).
+- The shipped procedures (`docs/course-agent/`) survive a course's prettier:
+  no inline code span crosses a line break, which prettier re-indented out of
+  its list item. `gen-map --check` fails on one.
+- `migrating.md`, 0.13.1 → 0.14.0, corrected where upgrading
+  credit-and-derivatives found it wrong: the patch goes before `pnpm add`
+  (pnpm refuses with `ERR_PNPM_UNUSED_PATCH`) and its entry may sit in
+  `pnpm-workspace.yaml`; pnpm 11's `minimumReleaseAgeExclude`; a course that
+  commits `build/resolution/` fails its first run after the upgrade; stale
+  `lint-ignore.yml` lines and a course's own tier guidance (step 20); the 404
+  page without a raw `<div>` (step 24); tests comparing sidebar and page
+  colours (step 25). Upgrading time-series added two more: pnpm can instead
+  stop with `ERR_PNPM_NO_MATURE_MATCHING_VERSION` (step 1), and the first
+  `content/versions.json` goes in before the upgrade's own changelog bullet,
+  or every page reads "not yet released" (step 10).
+- `content fix` takes several lessons, or `--all`, as one plan: the lessons
+  with nothing to fix are counted, not listed. A course upgrading to 0.14.0
+  can have a thousand redundant `\explain` wraps (data-science-I: 1193).
+- `content check` lists a lesson's errors and warnings line by line and
+  counts its info by code, with the command that lists them; `--json` is
+  unchanged.
+- `definition-repeated` on a local entry whose glyph a shared card already
+  owns no longer says "move one copy to `content/notation/`": promoting it
+  would put two shared cards on one glyph. It says the entry is a reused
+  letter (rule N4) and how to acknowledge the copies; `content move` prints a
+  caution when the glyph is taken (time-series: 9 of its 34).
+- `dia-too-wide` on `<CurriculumMap>`'s competency graph names the map's own
+  props (`graph="per-part"`, `direction`, `warnAboveWidth`) instead of a node
+  `width` and a shorter label, which the author does not write there.
+- The rules-in-effect page says the course's `rules` and `courseRules` live
+  in `course.settings.json` or `course.config.ts`, not only the first.
+
+### Fixed
+
+- `content move` wrote the new card a placeholder body ("Extend this body
+  with what a glossary reader needs."), which the glossary would publish, and
+  `domain: general` for a key without a prefix. The card now has no body, its
+  domain is the key's prefix when the course has that domain, else the one
+  most of the lesson's cards have; the plan says that the body is the
+  author's to write, and when the entry had no `label`.
+- `validate:content`'s run log recorded each consistency warning
+  (`definition-repeated`, `glyph-unique-in-corpus`, …) at INFO and their
+  one-line digest as the only WARNING, so its `Run log: (… warning(s))` count
+  disagreed with `content status`. Each finding is recorded at WARNING now,
+  the digest at INFO.
+- `ContextReport`'s `equations`, `tables`, `figures` and `diagrams` are typed
+  `ManifestLessonFloat[]`: `content context --json` always printed each
+  float's `short` and `caption`, which the type left out. The playground's
+  new `--json` contract test runs every read-only verb against the schemas and
+  caught it.
+
+## [0.14.0] - 2026-10-11
+
+### Breaking
+
+- **A symbol no entry binds in a notation entry's body fails `validate:content`
+  (rule N4), and the build fails on an entry whose body did not render.** The
+  Markdown body of a `content/notation/*.md` entry was the one rendered-math
+  context no gate read. `remarkNotation` rejected an unbound `$w_3$` there, but
+  Astro's content layer only logs a render error (`[ERROR] [glob-loader]`) and
+  keeps the entry without its body, so `astro build` ended green and the
+  glossary showed the entry with no text. `gateContentMath` now resolves every
+  `$…$` / `$$…$$` and currency `$` in an entry's body (`unresolved-glyph`,
+  `invalid-latex`, `currency-dollar`, …, context `body`) at the file's own
+  line, against the table the render uses: every shared entry, built by the new
+  `registry-scope.mjs` for both. `NotationGlossary.astro` throws, naming the
+  files, when an entry with a body has none rendered, whatever the cause. No
+  diagnostic code is new. Measured on the three downstream courses and the
+  playground (109 body spans), nothing fails.
+- **Each chapter and part page carries the knowledge version its content
+  last changed in (rule C5), kept in `content/versions.json`, which
+  `validate:content` writes and the course commits.** `MANIFEST_SCHEMA_VERSION`
+  is now v32. The course's version moves at every release, whatever the
+  release touched, so stamped on a chapter it said only "built after 0.4.0",
+  and in every PDF six times over, so a content release changed every LaTeX
+  cache key. Now a chapter's PDF, its source zip's README, its Markdown and
+  the `[?]` panel (a new "This page" row, `data-page-since`) say "unchanged
+  since version 0.2.0", the release its content last changed in, or "with
+  changes after version 0.4.0, not yet released" while `## [Unreleased]`
+  holds a change; a part's and the course's PDF and Markdown carry the newest
+  among their pages. A document unchanged since an earlier release keeps
+  that release's date (`SOURCE_DATE_EPOCH`, its figures' dates) and its
+  trailer `/ID`, so with `EXPLICO_LATEX_CACHE` a release recompiles only the
+  documents it changed. What counts as the page: its file, its `.checks.yml`
+  and assessments, the shared notation entries its text uses, the sources it
+  cites and its numbers. `content/versions.json` is a record like a lockfile:
+  `compileManifest` reads the committed one and works the next out
+  (`page-versions.ts`: a release takes every pending change; an unchanged
+  page keeps its version; a change waits while `## [Unreleased]` has
+  bullets), `validate:content` writes it on a developer's machine
+  (`syncPageVersions`) and in CI (`CI` set) fails with `page-versions-stale`
+  until the committed file is the one it would write — **so a course's first
+  build after upgrading needs one `pnpm validate:content` and a commit of
+  `content/versions.json`**. A file that is not such a record warns
+  `page-versions-invalid` and is rebuilt. The manifest gains
+  `lessons[].since`, `parts[].overview.since`, `about.knowledge.releases`
+  (every released entry with its date) and `about.knowledge.unreleased`, and
+  `pageVersions`; `content status` reports `pageVersions` (`tracked`,
+  `unreleased`), `content context` a lesson's `since`.
+  `explico.cls`: `\ExplicoSource`'s second argument and `\ExplicoTitlePage`'s
+  third are the phrase, printed as given ("From *Course*, unchanged since
+  version 0.2.0."; "Content unchanged since version 0.2.0"), where they were
+  a bare version. Rule off (`rules.C5.enabled: false`): nothing is read or
+  written, and every page carries the course's version as before.
+
+- **The course asks each reader before it keeps their reading in their
+  browser, and keeps to the answer.** A small, non-blocking question at the
+  bottom of the window ("Remember your reading?", `ReadingMemoryNotice.astro`,
+  rendered by the header on every page) offers "Remember" and "Don't
+  remember", the same size and weight. Reading memory is what records what a
+  reader did across visits: the chapters they opened (the sidebar marks, and
+  the note under a changed page's title), the cards they keep open on a page
+  (`card-memory.ts`) and the course's last set of carried cards
+  (`card-carry.ts`). Until the reader says yes, and after a no, none of it
+  outlives the tab: no visit is recorded and no mark shown, and kept and
+  carried cards live in the tab's session storage, so Back, a reload and a
+  link still bring them back until the tab closes. **Kept and carried cards
+  therefore no longer come back after a browser restart, or in a new tab,
+  unless the reader said yes**; before, they always did. Settings a reader
+  chooses (theme, text size, panel layout, a folded section or part, the
+  "Carry cards" switch) are kept as before and need no answer. The answer is
+  kept per course (`explico-reading-memory:<base path>`) for 13 months, then
+  asked again; a no deletes the course's reading memory at once. The `[?]`
+  panel gains an "In this browser" section: a "Remember my reading" switch,
+  every copy of the panel in step, and "Forget what this course stored",
+  which deletes every key of the course (and the settings explico courses on
+  the site share, and Starlight's theme) and asks again. Nothing explico
+  stores is a cookie, and nothing leaves the browser. The new
+  `readingMemory` setting (`"ask"`, default, or `"off"`: never ask, never
+  keep reading memory, no marks) is in the manifest as `readingMemory`
+  (v32). `session/reading-memory.ts` holds the logic; `PreferenceStore`
+  gains an optional `keys()`.
+
+### Added
+
+- **The docs point at two downloadable courses.** The README, the shipped
+  agent guide, the rule index and the course `AGENTS.md` baseline link
+  https://danieltuzes.github.io/explico/start/, where the playground (at the
+  engine's latest release, standalone) and credit-and-derivatives are
+  downloadable at their newest version, with a machine-readable
+  `sources.json`; a `playground/…` path in the docs is a file of that
+  download.
+- **The agent procedures ship to courses, and `content init-agent` installs
+  them.** `docs/course-agent/` (in the package) holds the `draft-lesson`,
+  `migrate-course` and `release-content` skills, the `rules-reviewer`
+  sub-agent and a baseline course `AGENTS.md` that points at the engine's
+  guide; `pnpm content init-agent [--write]` copies the skills and the agent
+  into the course's `.claude/` and writes the baseline only where the course
+  has no `AGENTS.md`. `content status` says whether the course's `AGENTS.md`
+  points at `docs/authoring/agents.md` and whether the procedures are
+  installed (`agentGuide` in the JSON). `docs/authoring/agents.md` replaces its
+  paragraph of verbs with a table: what you want to know, the verb, what it
+  prints.
+- **The `content` CLI and `validate:content` ship in the engine.**
+  `runContentCli(courseConfig, argv?, io?)` (`explico/compiler/cli-main`) is
+  the whole router — every verb, the usage text (`CONTENT_USAGE`, printed by
+  `pnpm content help`), the flag parsing (`parseContentArgs`), the text output
+  and the exit code — and `runValidateContent(courseConfig)`
+  (`explico/compiler/validate-content`) the whole validate run. A course's
+  `scripts/content.ts` and `scripts/compile-manifest.ts` become three-line
+  shims, so a verb added to the engine reaches every course with the package;
+  the playground's two scripts are those shims.
+- **The `appearance` setting: how the page tells its parts apart, and how a
+  deck's slides sit on it.** `zones` is `tonal` (the default: both sidebars
+  one step of Starlight's neutral grey, the header a step further, the
+  reading column unchanged), `accent-header` (the header a deep band of the
+  course accent in both themes, drawn on dark-theme colours, and the
+  dark-theme logo on it; its menus and the search dialog keep the page's
+  colours), `paper` (header and sidebars a desk, the reading column a sheet
+  on it whose edge casts a soft shadow, a step lighter than the desk in the
+  dark theme) or `none` (Starlight's colours). `slides` is `lifted` (the
+  default: an edge and a drop shadow, and in the dark theme a sheet a step
+  lighter than the page), `edge` (the edge and shadow on the page's colour)
+  or `sorter` (the deck on a tinted well). `LayoutHeader.astro` writes the
+  choice on `[data-explico-zones]` / `[data-explico-slides]`, and the new
+  `src/styles/zones.css` and `deck.css` select it with `:root:has(…)`, so it
+  is right in the first painted frame; each style is a set of `--ex-zone-*`
+  / `--deck-stage-*` tokens per theme that a course can retune. Screen only:
+  print, Present mode and a figure captured for the exports are unchanged.
+  `normalizeAppearance` validates it; the manifest carries it as
+  `appearance`, and the manifest schema is now v37.
+- **Released courses now receive copy-ready 404-page instructions** in the
+  README, the structure guide and the current migration section: add
+  `content/docs/404.mdx` as a splash page, use Astro's `BASE_URL` to get home
+  from any missing path, and set Astro's `site` origin so Starlight can emit its
+  sitemap without a warning. The playground turns the missing URL into a
+  trajectory that misses its plotted page and exercises an actually missing
+  route.
+- **The contents list and a part's page show each lesson's slides**, when the
+  course has a deck. A slides column ends every row of `<CourseContents>` and
+  of `<PartOverview>`'s reading list: a lesson's own deck is a tile on its
+  title line, and a part's deck is one bar along the chapters it covers, from
+  the first covered title to the last, each cell a link to that chapter's
+  section of the deck, named and described as the sidebar names it ("Slides:
+  Velocity Under Constant Acceleration" / "Slides 17–25 of the part's
+  slides"). A part's deck that skips a chapter breaks into runs; one that
+  covers a chapter with its own deck runs in a second column. Each title
+  starts with the glyph of what it opens (a chapter's sheet, a slides-only
+  lesson's frame), a part's heading with Overview's two sheets
+  (`--explico-part-glyph`, `global.css`), and the contents list's counts gain
+  the decks ("4 slide decks") and a key to the glyphs. A slides-only lesson's
+  tile is out of the tab order and hidden from assistive technology: its
+  title opens the same page. A course with no deck renders both lists as
+  before; `slides={false}` on either component turns it all off. The cells
+  come from `deck-lane.ts` (`deckLanes`, `laneLink`).
+- **The glossary lists page-bound meanings.** Under its index, "On one page
+  only" lists every `notation.local` entry (linking to its lesson) and every
+  gloss (linking to the card whose formula names it), so a reader who looks a
+  letter up always finds it and sees which meanings are course-wide and which
+  are page-bound; the cards themselves stay the shared entries.
+- **`content move`, `content rename` and `content fix`: the refactors as
+  verbs, dry-run by default.** `move <lesson>:<key> [--to <key>]` turns a
+  `notation.local` entry into a shared card written from the entry's own
+  fields, removes the copy from every lesson that declares the key (reporting
+  a copy that differed) and, with a new key, rewrites every `[[key]]` and
+  `\explain{key}`; `rename <old> <new>` renames a shared card and everything
+  that names it, `seeAlso` and `lint-ignore.yml` included; `fix <lesson>`
+  unwraps every `\explain` the gate reports as redundant. Each prints its
+  plan as a unified diff and changes nothing without `--write`. `planMove`,
+  `planRename`, `planFix`, `renderEditPlan`, `applyEditPlan`,
+  `removeLocalItem`, `rewriteKeyReferences` and `sharedCardFromLocal` are
+  exported from `explico/compiler/cli`.
+- **`definition-repeated` (warning), `meaning-repeated` (info) and
+  `explain-redundant` (info), under rule N4.** One local key declared in two
+  lessons, saying whether the copies agree and that moving one copy to
+  `content/notation/<key>.md` keeps every `[[key]]` working; one symbol and
+  name defined at two sites in any tier (a local card and a gloss, two
+  glosses, a local card beside the shared card that already says it); and an
+  `\explain{key}{…}` in page math whose bare symbol already resolves to the
+  same card with nothing left over. The first two come from `consistency.ts`
+  (`checkDefinitionRepeated`, `checkMeaningRepeated`), the third from the
+  completeness gate, located at the span; `explainCalls` and
+  `redundantExplainWraps` are exported from `explico/reference/gate-math`.
+- **`content equation "<latex>" [--lesson <id>]` resolves one expression the
+  way the gate will.** Against the lesson's scope (its `notation.local` and
+  the shared cards it introduces, with its suspended decorations) or, with no
+  lesson, against every shared card as a notation entry's body is; prints
+  each glyph's card, redundant `\explain` wraps, unresolved glyphs with where
+  they are defined, and exits 1 when the build would refuse the span. A few
+  lines, while drafting. `contentEquation` and `formatEquationReport` are
+  exported from `explico/compiler/cli`.
+- **`content migrate [--from <v>] [--to <v>]` prints the migration an
+  upgrade needs.** The guide's `## <from> → <to>` sections from the version
+  `package.json` pins at HEAD to the one installed (either end overridable),
+  oldest first, each section whole; a `0.4.x` range on the left matches its
+  patch versions, `Unreleased` is allowed on the right, and a hole in the
+  chain is an error that names the version no section continues from. One
+  or two sections instead of the forty-thousand-token file. `content status`
+  sizes that migration among the agent surfaces when the pin and the install
+  differ. `contentMigrate`, `parseMigrationSections`, `selectMigrationPath`,
+  `installedEngineVersion`, `pinnedEngineVersion` and `formatMigrateReport`
+  are exported from `explico/compiler/cli`.
+- **`content bindings <lesson>` shows what a lesson's math binds before a
+  build.** Span by span: each glyph and its card with how it resolved
+  (`canonical`, `family`, `derived`, `base`, `operator`, or an explicit
+  wrap), every `\explain{key}{…}` whose bare symbol resolves to the same card
+  (a redundant wrap), and every unresolved glyph with where `content symbol`
+  finds it defined; the counts first. The same resolver and scope the
+  completeness gate uses. `contentBindings`, `spanBindings` and
+  `formatBindingsReport` are exported from `explico/compiler/cli`.
+- **`content rule <ID>` prints one rule whole.** The catalog entry as this
+  course has it (kind, elements, enforcement, editions, on or off, waivable,
+  codes, settings in effect, summary) and the rule page's own section sliced
+  by heading, example included, about half a thousand tokens where opening
+  the page costs twenty thousand; an invariant by its slug, a retired rule
+  with its date and successor, an unknown ID lists the rules in effect and
+  exits 1. `contentRule`, `formatRuleReport`, `ruleSection` and
+  `authoringDocsDir` are exported from `explico/compiler/cli`.
+- **A lesson can have a deck: its slide edition, `<lesson>.deck.mdx`**
+  (`docs/authoring/deck.md`). A deck sits beside its chapter, served at
+  `/<part>/<lesson>/slides/` and listed under the chapter in the sidebar, or
+  alone, as a slides-first lesson at the lesson's own URL. `##` opens a section
+  (a divider frame), `###` is a frame whose heading is its title,
+  `<Pause />` is a step, `<Notes>` holds the speaker notes and
+  `<Recall ref="eq-…" />` (`fig-`, `tab-`, `dia-`) shows the chapter's float with
+  the chapter's number; none needs an `import`. The engine writes the title
+  frame, the outcomes frame (`deck.outcomesFrame`) and the references frame, and
+  a legend line on each frame naming the symbols it introduces. A deck shows its
+  lesson's symbols: its math binds in the chapter's scope, its notation bundle
+  holds the chapter's, and a lab recalled onto it reads the lesson's scope
+  (`labMathScope`). Its own figures, tables and diagrams are unnumbered and an
+  equation it labels numbers (1), (2) within it; `Figure`, `Table` and
+  `Diagram` read that from the manifest (`components/deck/deck-context.ts`), so a
+  course's wrapper forwards nothing new. Area **D** joins the rule set: rule D1
+  (sections of frames, locked), rule D2 (a frame fits its canvas), rule D3 (a
+  frame makes one claim), rule D4 (notes on a frame with text), rule D5 (a frame
+  title fits one line), rule D6 (at most `maxSteps` steps, each adding), rule D7
+  (one picture per frame), rule D8 (recall, never retype), rule D9 (at most
+  `maxNewSymbols` new symbols) and rule D10 (generated title and outcomes
+  frames), with the new invariant `decks` (`deck-frontmatter`,
+  `deck-outside-part`, `recall-unresolved`, `pause-invalid`). A catalog entry
+  now says which edition of a lesson it is about (`editions`): V7, V8, S1, S6 and
+  S7 are about a chapter's page, and a `D` rule says the same of a frame, so a
+  course's own `X` rule may name its edition too. `build/rules-in-effect.md` is
+  the chapter's page, as before; a course with a deck also gets
+  `build/rules-in-effect-deck.md` (`content rules --edition deck`).
+  `content new deck <lesson>` drafts a deck from the chapter. The course setting
+  `deck` sets the canvas (`aspectRatio`: `16:9`, `16:10` or `4:3`), the legend
+  line, who sees the notes, the outcomes frame and the handout PDF.
+  `MANIFEST_SCHEMA_VERSION` is now v33 (additive): `decks`, `deck` and
+  `lessons[].editions`. `explico` depends on `github-slugger` 2.0.0 (the id
+  Astro gives a deck's page). On a chapter, Next and Previous still step
+  from chapter to chapter, past a chapter's slides row; on a deck's page they
+  step from deck to deck, a part's and a slides-first lesson's included, each
+  named "Slides: *title*" (`deckNeighbours` in `deck-context.ts`). The
+  glossary names a chapter once, not its deck as a second page, and a deck's
+  "On this page" names each frame by its title as it reads, math included.
+- **A deck's page presents.** It reads as a study page, every frame on a
+  canvas of fixed size (`deck.aspectRatio`: 800×450, 720×450 or 600×450 CSS
+  pixels) scaled to the column, each in its final step with its notes under it.
+  Its Present button shows one frame at a time, full screen: → ↓ Space PageDown
+  step, ← ↑ PageUp Backspace step back, Home and End, a number and Enter jump,
+  `F` full screen, `N` the notes beside the frame, `P` a presenter window (the
+  frame, the next, the notes, a clock, kept in step through a
+  `BroadcastChannel`), `B` a black screen, Esc leaves; the address is
+  `#slide-N`. A step can drive a lab (`<Pause control="Launch angle" from="15"
+  to="75" seconds="5" />` moves its control), light a symbol up
+  (`highlight="key"`), and a frame titled `### … [morph]` morphs from the one
+  before through View Transitions. A figure on a frame scales its tools down
+  and narrows its picture to fit, to no less than 60 %. After the build, each deck page is
+  laid out in the course's Chromium and a frame that still runs past its canvas
+  fails the build: `frame-overflow` (rule D2; a warning without a browser,
+  an error in CI). The deck offers "Continue at slide N", for the tab and,
+  with the reader's yes to reading memory, on later visits
+  (`explico:decks:<base>`, `docs/privacy.md`). Print gives one frame per
+  page.
+- **A deck downloads as slides, a handout, LaTeX, offline HTML and Marp
+  Markdown.** With `lessonExports.latex`, each deck compiles in beamer with
+  explico's theme: `downloads/<lesson>-slides.pdf`, one page per step, every
+  symbol on a frame linked to its entry on the notation frames that close the
+  deck; `downloads/<lesson>-slides-notes.pdf`, each frame in its final state
+  followed by its notes and its check's answers (with `deck.handoutPdf`, and
+  `deck.notes` not `off`); and their source, `downloads/<lesson>-slides-latex.zip`
+  (`main.tex`, `handout.tex`, `deck.tex`, `beamerthemeexplico.sty`). The build
+  fails when the PDF numbers a frame differently from the page, and warns when
+  a frame runs over its slide on paper. `explico.cls` now loads
+  `explico-common.sty` (fonts, colours, figures, diagrams, notation markers),
+  which the theme shares; a chapter's and a book's LaTeX folder carry it.
+  Beamer cannot write a tagged PDF, so a deck's PDFs are untagged. With
+  `standaloneHtml`, `downloads/<lesson>-slides.html` presents offline; with
+  `markdown`, `downloads/<lesson>-slides-markdown.zip` holds the deck in Marp's
+  dialect. The Download menu has a row for the deck on its page and its
+  chapter's (`deck` scope, a `handout` column). A part's and the course's book
+  keep a slides-first lesson's place with a short chapter (its outcomes and a
+  link to its slides), so later chapters keep their numbers. `decks[].since`
+  dates a deck (rule C5): its PDFs' date, title frame and cache key. The CI
+  package list (`texlive-packages.txt`) adds `beamer` and `translator`.
+- **Every diagnostic line names its rule and page.** Text output reads
+  `info consistency:weak-local [N4 · notation.md#n4]: …`, and the JSON carries
+  `doc` next to `rule`, so finding what a code answers to needs no second
+  step. `formatCliDiagnostic` and `ownerTag` are exported from
+  `explico/compiler/cli`; the playground wrapper prints through them.
+- **`content status` sizes the agent surfaces.** One line with the estimated
+  tokens of `AGENTS.md` (the course's, and the repository's one level up) and
+  of the rules-in-effect page (`agentSurfaces` in the JSON): a budget to
+  watch.
+- **A page that changed since the reader last opened it says so under its
+  title**: "This page changed since you last opened it.", with a "What
+  changed" link to the course's `changelogHref` when it has one, and the
+  sidebar's accent dot beside it. It shows once, on the visit that finds the
+  change, only with the reader's yes to reading memory, and not with
+  `sidebarMarks.changed` off. `LayoutPageTitle.astro` renders it hidden on
+  every chapter and part page; the sidebar's script shows it.
+- **[`docs/privacy.md`](docs/privacy.md)**, shipped in the package: every key
+  an explico site keeps in a reader's browser, when it is written, which of
+  them need the reader's yes, and what a course's own privacy notice should
+  add (its host, anything it loads from another site).
+- **`content symbol <latex | key>` says where a symbol is already defined.**
+  The shared card, every `notation.local` entry with its lesson and every
+  gloss with its card, matched on the latex as written, a shared card's
+  `aliases` or the key, then the entries whose notation contains it as a
+  glyph (`v` in `v_0`), each with label, units, the first sentence of its
+  meaning and, for a shared card, the lessons that bind it. One call before
+  declaring a symbol, so an author references what exists instead of copying
+  it. Read-only; `--json` for the full report. `contentSymbol` and
+  `formatSymbolReport` are exported from `explico/compiler/cli`; a course
+  adds the verb to its `scripts/content.ts`.
+- **`<CurriculumMap>` takes `graph`, `direction` and `warnAboveWidth`.** A
+  course with many competencies got a `dia-too-wide` warning (rule V8) on the
+  map's one competency graph and could not act on it. `graph="per-part"` draws
+  one diagram per part (`competency-graph-<part dir>`), each with the
+  competencies its lessons teach first and the earlier ones they build on as
+  boxes labelled with their part, and a last group for competencies no lesson
+  teaches; `direction` and `warnAboveWidth` reach every competency diagram.
+  The default, `graph="whole"`, renders exactly what it did.
+- **The sidebar marks, for each reader, the chapters and part pages they
+  have not opened yet and those that changed since they last opened them.**
+  A quiet ring for "not opened yet", an accent dot for "changed since you
+  last opened it". A labelled row carries its mark in the panel's margin just
+  past the row's end, so a title keeps its width; a compact part's tile
+  carries it on its corner, and the tile's tooltip names it under the title;
+  a closed part (the phone's menu) carries its strongest mark after its
+  label; and with the panel folded away, its restore control carries a
+  change. A line under the chapter list says what the marks mean and offers
+  "Mark all as seen". "Changed" compares the page's rule C5 hash (the
+  current one, `pending ?? source`, cut to 12 hex digits) with the one the
+  reader saw, so an unreleased change on the live site counts and a release
+  that only stamps a version on a page does not. What a reader has seen is
+  view state kept in their browser through the `PreferenceStore`, under
+  `explico-page-marks:<base path>`, so courses that share an origin keep
+  their own; it is reading memory (above), so it is recorded, and marks
+  shown, only after the reader's yes; without storage nothing is marked. Each marked link names its
+  mark as its description (`aria-describedby`). The new `sidebarMarks`
+  setting (`unopened`, `changed`, both on by default) turns either off; the
+  manifest carries it as `sidebarMarks` (v32). `page-marks.ts` holds the
+  logic, `LayoutSidebar.astro` the wiring, `global.css` the marks.
+- **`withNoneSeen` and `DECK_LESSON_CLASS`.** `page-marks.ts` names both
+  resets of a reader's record: `withNoneSeen()`, the record with no page
+  seen ("Mark all as unseen", below under Changed), beside `withAllSeen`.
+  `lesson-derivation.ts` exports `DECK_LESSON_CLASS` (`explico-deck-lesson`),
+  the class of a slides-first lesson's sidebar item, beside `DECK_ROW_CLASS`,
+  and `sidebarLessonSlug(item)`, the lesson a sidebar item lists (a chapter's
+  slug, or a slides-first lesson's item), which the manifest's chapter
+  numbering reads. `buildSidebar` takes `slidesFirst`, the lessons whose only
+  edition is a deck.
+- **`sidebarEditions`, and two controls in the sidebar's foot that switch
+  it.** A lesson with a chapter and a deck is one sidebar row (below, under
+  Changed); the setting says which edition the row opens, `lead: "chapter"`
+  (default) or `"slides"`, and whether it lists the other, `other: "listed"`
+  (default) or `"hidden"` (`normalizeSidebarEditions`,
+  `SIDEBAR_EDITIONS_DEFAULTS` in `course-config.ts`; any other value fails
+  the build, naming the field). Each reader switches both under the chapter
+  list: "Lessons open as" Chapter or Slides, a pair of radios drawn as one
+  control, and "List the other edition too", a checkbox. Their choice is a
+  setting, like a compact part, kept in their browser whatever they answered
+  about reading memory, under `explico-sidebar-editions` (one key for the
+  courses on a site, listed in `docs/privacy.md`, reset by "Forget what this
+  course stored" with the other shared settings), and kept field by field, so
+  a field they never set follows the course's default. A course without a
+  deck shows no controls. The manifest carries the setting as
+  `sidebarEditions`, and `MANIFEST_SCHEMA_VERSION` is now v34.
+  `sidebar-editions.ts` holds the logic, `LayoutSidebar.astro` the wiring.
+- **A deck's page shows which slides Present mode has shown the reader, and
+  presents from any of them** (`docs/plans/deck-navigation/`, phase 3, and
+  the "Seen slides and glyphs" decisions). Each frame Present mode shows, at
+  any step, in the room's window or the presenter's, is kept as it was. A
+  line above each frame, outside its canvas and in the page's own type
+  (`.deck-frame__line`), says "Slide N" and "Shown", "Not shown yet" (the
+  sidebar's ring) or "Changed since shown" (its dot), and ends on a button:
+  "Continue here", filled and always shown, on the frame to continue at;
+  "Present from here" on every other (`button.deck-frame__present`, named
+  "Present from here, slide N"), shown while the pointer is on the frame or
+  the keyboard's focus is in it, with an accent ring round the frame, and
+  always, as its icon, on a screen without hover. Under the title, the slide
+  map (`nav.deck-map`) shows every frame as a numbered square linking to it:
+  filled once shown, outlined before, dotted when changed since, the frame to
+  continue at ringed and the one in view underlined (`aria-current`). It
+  stays under the header while the deck scrolls (`data-stuck`), and a frame
+  a link lands on keeps its line clear of it (`--deck-map-height`). A deck
+  too long for the map's line keeps its first and last frames, the frames
+  before and after the one to continue at and round the one in view, as many
+  as the line has room for, with a gap for each run left out that links to
+  the frame in its middle (`components/deck/deck-map.ts`: `slideMap`,
+  `slideMapKeeping`). "Not shown yet" and "Changed since shown" are the
+  sidebar's two marks, which `sidebarMarks` turns off here too; with
+  `unopened` off, no frame says "Shown" either. Each frame names its state as
+  its description (`aria-describedby`). A line under Present counts them
+  ("14 slides not shown yet", "2 slides changed since shown") and offers
+  "Mark all as seen" and "Mark all as unseen" for the deck, with a
+  `role="status"` line that says what a button did. Every frame of
+  `decks[].frames` carries `id`, 12 hex digits of a SHA-256 over what it
+  shows (an authored frame's source, notes included, and the chapter's
+  number for each float it recalls; the title frame's title, course and
+  authors, not its version; the outcomes frame's outcomes; the references
+  frame's sources), stamped on the frame as `data-frame-id`, so a frame moved
+  by one added before it is still the frame the reader saw.
+  `MANIFEST_SCHEMA_VERSION` is now v35. `buildDecks` takes `course` (the
+  title frame's course and authors) and each lesson's `outcomes`. The record
+  under `explico:decks:<base>` is now `{ "v": 2, "decks": { slug: { at,
+  step, seen } } }`: the frame and the step Present mode stopped at, and the
+  frames it showed; a version 1 record (`{ slug: frame }`) reads as one with
+  no frame seen. "Continue at slide N" presents from the frame the reader
+  stopped at, unless they were shown its every step, then from the frame
+  after it, following that frame to its number now when frames were added
+  before it. Before the reader answers the reading-memory question, the
+  frames shown are kept, and marked, for the tab alone, as kept cards are;
+  "Remember" keeps them for later visits (`mergeDeckMemory`), and "Don't
+  remember" clears them, keeps only where each deck stopped for the tab, and
+  records no frame after. With `readingMemory: "off"` no frame is recorded and
+  nothing is marked. The question itself now names the slides it keeps. The
+  resume button, the lines, the map and the marks' line are the reader's own
+  (`data-explico-export-chrome`): Present mode, print and a downloaded deck
+  show none of them. `session/deck-memory.ts` holds the logic
+  (`decodeDeckMemory`, `encodeDeckMemory`, `withPosition`, `withShown`,
+  `withAllSeen`, `withNoneSeen`, `withEveryDeckSeen`, `withEveryDeckUnseen`,
+  `mergeDeckMemory`, `frameMark`, `resumeAt`, `DECK_MEMORY_EVENT`),
+  `deck-controller.ts` the wiring.
+- **A part can have a deck: `<part>/index.deck.mdx`, served at
+  `/<part>/slides/`** (`docs/authoring/deck.md`, "A deck for a part";
+  `docs/plans/deck-navigation/`, phase 4). It sits beside the part's page,
+  sets only `title` and `description`, and each `##` section may name the
+  chapter it covers, `## Title [chapter: <name>]`, the marker stripped from
+  the divider. A chapter may run over several sections in a row, each naming
+  it, as a chapter's own deck does; the first one's divider is the chapter's
+  address in the deck (`#slide-N`). Its symbols bind in the scope of the part's chapters, a key
+  two of them define binding to the first in reading order; `<Recall ref>`
+  shows a covered chapter's float with that chapter's number, linked to it,
+  the section's own chapter first; `[[eq-…]]`, `[[fig-…]]` and `[[sec-…]]`
+  fall back to the one covered chapter that has the key; `<AssessmentSet />`
+  asks the checks of its section's chapter (the engine passes `lesson`, a new
+  prop); the outcomes frame lists every covered chapter's competencies; the
+  title frame falls back to the part's label. In the sidebar it is a row of
+  its own right after the part's Overview, `explico-deck-row
+  explico-part-deck`, the deck's glyph before "Slides" and a tile of its own in a
+  compact part; a chapter it covers that has no deck of its own carries
+  `data-deck-href`, and the sidebar's script makes that address the
+  chapter's other edition, "Slides: *title*", unmarked (`data-deck-section`):
+  a lesson's own deck wins. "Slides for this chapter" goes to that section
+  when the chapter has no deck; the part's page offers "Slides for this
+  part" and the deck's page "Open the part". It downloads as every deck does,
+  named after its part (`downloads/motion-slides.pdf`, `-notes.pdf`,
+  `-latex.zip`, `-markdown.zip`, `.html`), on its page, on its part's and,
+  as "Its slides", on each chapter it covers that has no deck of its own;
+  `deckFileStem` takes the owner's slug, and `deckOwnerSlug`, `deckSaveName`
+  (`exports/export-pages.ts`) and `deckCheckItems` (`latex/document.ts`) name
+  and fill it. Its page has a version of its own (rule C5), which counts the
+  number, captions and equation each recalled float has in its chapter. The
+  `decks` invariant gains `deck-chapter-unknown`, `deck-chapter-repeated` (a
+  chapter named again after a section of another chapter or of the deck's
+  own), `deck-chapter-outside-part`, `deck-marker-misplaced`,
+  `deck-check-no-chapter` and `deck-route-taken`. `content new deck <part>`
+  drafts it from the part's chapters (a section per chapter in track order, a
+  frame per section, a `<Recall>` per numbered float), and `content check`
+  takes a deck's page, `<part>/slides` or `<part>/<lesson>/slides`
+  (`findCheckTarget`). `MANIFEST_SCHEMA_VERSION` is now v36: `decks[]` gains
+  `part`, `covers` (every deck; empty on a lesson's), `recalledFrom` and
+  `frames[].chapter`, and `lessonId` is absent on a part's deck. In the
+  engine, `DeckFile` is `LessonDeckFile | PartDeckFile` (`scope`, `partDir`),
+  `NotationLessonInput.scopeLessonIds` lists the lessons a deck's page binds
+  in (`resolvePageReferenceId`, `pageScopeLessonIds` in
+  `reference/references.ts`; `scopeLessonsOf` in `page-notation.ts`), and
+  `lesson-derivation.ts` gains `isPartDeckSlug`, `partDeckDir`,
+  `partDeckRouteSlug`, `partDeckPageId` and `PART_DECK_CLASS`. A course with
+  no part's deck sees no change but the manifest's shape.
+- **`EXPLICO_LATEX_CACHE=<directory>` reuses a compiled PDF whose source did
+  not change.** The LaTeX export recompiled every document on every build:
+  43 LuaLaTeX compiles, 685 s on a two-core CI runner, for a course of 37
+  chapters. With the variable set, `latex/cache.ts` keys each document by a
+  SHA-256 over every file of its folder, the engine, the TeX installation
+  (`texFingerprint`: the engine's and latexmk's banners, the LaTeX kernel's
+  date), the epoch and `EXPLICO_LATEX_CACHE_SALT`, and keeps its PDF, `.aux`
+  and log. A reused document is checked like a compiled one: its numbers
+  against the website's, its log for characters no font set. A failed
+  compile stores nothing, an entry that does not read back whole is a miss,
+  and entries unused for a week are deleted. The summary line says
+  "7 compiled, 36 reused from …". Unset, the build is unchanged. With rule
+  C5 (above) a document's version line and date are its own, so a content
+  release, too, recompiles only the documents it changed.
+- **`pnpm check:dist-imports`, run by `prepack`.** It parses every module in
+  `dist/` and fails on a relative import whose target the package does not
+  ship. The repository never loads `dist/`, so such a gap (below) passes the
+  build, the playground and the tests.
+
+- **[`docs/diagram-scaling.md`](docs/diagram-scaling.md)**, shipped in the
+  package like `docs/katex-bracket-scaling.md`: how a diagram follows the
+  phone's text size (below, under Changed), why it is scaled through the HTML
+  canvas and never the SVG, the rules for changing it, and what to check on a
+  real iPhone, which the end-to-end suite (Chromium) cannot.
+
+### Changed
+
+- **The header, the two sidebars and the reading column are told apart by
+  colour, and every slide on a deck's page has a visible edge and a drop
+  shadow** (`appearance`, above, at its defaults). Before, the light theme
+  drew all three columns white, and the dark theme gave the header and the
+  course sidebar one colour and the contents sidebar the article's. A dark
+  slide had no visible edge: its border was `hairline-shade`, which in the
+  dark theme is the page's own colour, and its shadow was black on
+  near-black. The part holding the open page is tinted with the sidebar's
+  own accent tint (`--ex-zone-rail-accent`), a step darker than
+  `accent-low`, so it differs from the grey by lightness as well as hue.
+  The course's title in the header is its accent a step toward the text
+  colour (`--ex-zone-title`), which keeps it at 4.5:1 on the tinted header.
+  `"zones": "none"` keeps the old frame.
+- **A part's deck shares the part's row with its Overview.** It was a row of
+  its own under the Overview, listed whatever the sidebar's two controls
+  said, with a chapter's deck glyph and the tooltip "Slides". The sidebar's
+  script now makes the two one row, as a lesson's chapter and deck are, and
+  it follows "Lessons open as" and "List the other edition too" the same way,
+  Overview standing for the chapter: "Overview" with the deck as the icon at
+  its end, or "Slides for this part" with Overview's two sheets there, or
+  one of them alone (an unlisted one still shows while it is the open page).
+  In a part with no Overview the deck keeps a row of its own, unlisted only
+  while chapters lead with the other edition unlisted. Both links keep their
+  glyph in every state, and a compact part joins their tiles, both in the
+  accent. The deck's glyph is two frames, its own in front with an outlined
+  frame behind (`--explico-part-deck-glyph`, `deck.css`). Its tooltip names
+  the part, then on a quieter second line its chapters and slides ("Slides
+  for this part: Motion in the plane" / "Chapters 1–2 · 26 slides"), and a
+  chapter's section of it names its slides ("Slides 17–25 of the part's
+  slides"); the second line is the link's `aria-description` and a
+  `small.layout-edition-detail` in its name's span, shown only where the
+  span is a tooltip. `buildSidebar` adds `data-part` and `data-part-edition`
+  to the Overview's item and the deck's, `data-title` and `data-chapters`
+  (the covered chapters' ordinals, `1–2`, `1, 3`) to the deck's, and the new
+  `withPartDeckFrames` adds, once `buildDecks` has run, `data-frames` to the
+  deck's item and `data-deck-range` to each chapter that links into its
+  section (its frames, `2–16`). `sidebar-editions.ts` gains `partRow`,
+  `partEditionLabel`, `partDeckDetail`, `sectionDetail`,
+  `PART_EDITION_ATTRIBUTE`, `PART_ROW_CLASSES` and `EDITION_DETAIL_CLASS`;
+  `lesson-derivation.ts` gains `numberList`. Without scripts the sidebar is as
+  before. No schema bump: the attributes are additive.
+- **A formula's "Symbols" list names every symbol the formula names.** The
+  cards an entry's `formula` wraps with `\explain{key}{…}` are listed with its
+  glosses, in formula order, each card linked to its own entry on the
+  glossary page (`cards` on `<NotationFormula>`; `data-notation-card` marks
+  one); the list used to show the glosses alone, so a formula read as
+  half-explained without hover and in the exports.
+- **Rule N4's lints follow the tier model: a letter is declared once.**
+  `glyph-unique-in-corpus` now warns only when two *shared* cards claim one
+  glyph; a `notation.local` entry or a gloss that reuses a letter is the
+  declared exception and is never reported, so the acknowledgements courses
+  wrote for every reused index letter can go. N4's summary and its page say
+  which tier a symbol takes in one question — is this letter already
+  defined? — and `content symbol` answers it.
+- **`content diagnostics` counts by default and lists on request.** The text
+  output is a severity line, then counts by code (with each code's rule and
+  page) and by file, most frequent first and the file list capped at 25;
+  `--all` lists every line as before, and `--code <code>`, `--lesson <id>` or
+  `--changed` list a part. The JSON report is the same shape it was, filtered
+  when a flag is given. `summarizeDiagnostics`, `filterDiagnostics` and
+  `formatDiagnosticsSummary` are exported from `explico/compiler/cli`.
+- **`validate:content` passes on its first run.** It still rewrites
+  `build/resolution/*`, but it fails only on a report git tracks that it had
+  to rewrite (the committed-report contract a course that tracks `build/`
+  relies on) and lists the rest as refreshed (`refreshed` on
+  `syncResolutionReports`' result). A course whose `build/` is git-ignored no
+  longer fails and asks for a commit of files git ignores; a "run it twice"
+  instruction can go. `scripts/agent/verify` runs it once.
+- **The LaTeX export starts the longest documents first**: the course, then
+  the parts, then the chapters, the largest folder first within each. The
+  course took longest and started last, so it ran alone at the end while the
+  other cores had nothing left to do. Output is unchanged.
+- **The README and the wiring errors show `markdown.processor: unified({ … })`.**
+  Astro 7.3 deprecates the flat `markdown.remarkPlugins` / `rehypePlugins`
+  lists. `assertRemarkPluginsWired` still reads both surfaces; only its
+  messages and the README sketch name the processor form.
+  `docs/authoring/migrating.md` has the step to move a course's lists.
+- **The Download button's tooltip names what its menu offers.** It said
+  "Download this page" everywhere, but the menu lists the scopes that contain
+  the page: this chapter, this part and the whole course on a chapter; this
+  part and the whole course on a part's page; the whole course on any other
+  page, which has no download of its own. The `title` now reads "Download this
+  chapter, this part or the whole course", "Download this part or the whole
+  course" or "Download the whole course", in the menu's own words. The
+  accessible name is still "Download this page", so a browser test that finds
+  the button by role and name keeps working.
+
+- **The text size on touch screens runs from 50% to 100% in five geometric
+  steps**: 50, 59, 71, 84 and 100%, each 2^(1/4) (about 1.19) times the one
+  below, listed smallest first. It was 100, 90, 80 and 70%. `global.css` has
+  one `:root[data-text-size='…']` rule per step and
+  `TextSizeControl.astro` builds the list. A size the earlier release saved
+  (90, 80 or 70) is ignored: the page opens at 100% until the reader picks a
+  new one. `<html>` now also carries `--explico-text-scale`, the choice as a
+  number from 0.5 to 1, for what is drawn in px.
+
+- **A diagram follows the text size as a whole**, boxes and text together, so
+  a wide diagram can be made to fit a phone: the phone menu's 50% takes a
+  687 px diagram to 344 px. It is scaled the way print already scales it:
+  the SVG stays at its build-time size (WebKit does not scale a
+  `foreignObject`'s HTML with the `viewBox`) and the HTML canvas around it
+  takes a `transform`. `Diagram.astro` therefore has a new
+  `div.diagram-frame` between `.diagram-scroll` and `.diagram-canvas`; it
+  holds `--diagram-width` and `--diagram-height` (the canvas inherits them)
+  and takes the scaled size, which is what the scroller measures, so the
+  widen button ↔ appears or goes with the size
+  (`DiagramEnhancer.astro` watches the frame). Course CSS or tests that
+  select `.diagram-scroll > .diagram-canvas` as a child must use a
+  descendant selector. Only a diagram in the lesson (also when expanded)
+  scales; one in a preview card keeps its size and the card its 12 px text.
+  With no size chosen, and on a screen with hover, nothing changes.
+
+- **The sidebar draws a chapter, a part and a deck differently.** A compact
+  part's chapter tile is one sheet with lines of text on it (it was two
+  plain sheets, as the part's Overview tile still is). A deck is a filled
+  slide frame with a play mark cut out of it, on its "Slides" row and its
+  tile; a slides-first lesson's row carries it before its title, as the
+  Overview row carries its sheets, and its tile shows it in place of a
+  sheet. The manifest's `sidebar` lists a slides-first lesson as
+  `{ slug, attrs: { class: "explico-deck-lesson" } }` rather than its bare
+  slug, so `deck.css` can find it; it keeps its place and its chapter
+  number. The chapter's and the deck's glyphs are one SVG mask each over
+  the link's own colour (`--explico-chapter-glyph` in `global.css`,
+  `--explico-deck-glyph` in `deck.css`), the part's two sheets a border and
+  a shadow, so each takes the link's colour hovered, open or covered; the
+  Overview's second sheet now follows the tile's fill in those states.
+- **A chapter's tile and its deck's tile touch**, one pair in a compact
+  part: square where they meet, with one line between them that lights with
+  whichever tile is hovered, and accent around the open page's tile. The
+  sidebar's script makes the two one row (below), and `li[data-editions="pair"]`
+  joins them; without the script, `:has()` does, and a browser without it
+  keeps the gap.
+- **A lesson is one row in the sidebar.** A lesson with a chapter and a deck
+  was two rows, the chapter and a "Slides" row under it. It is one row now:
+  the row opens the lead edition under the lesson's title, and the other
+  edition is an icon at the row's end, as `»` ends a part's header, or, in a
+  compact part, the second of two joined tiles, the lead first
+  (`docs/plans/deck-navigation/`, phase 2). The icon's accessible name,
+  and its tooltip, is "Slides: *title*" or "Chapter: *title*", so a browser
+  test that finds a sidebar link by a lesson's title without `exact: true`
+  now finds two. A lesson with one edition carries its glyph before its title
+  only when that edition does not lead: a slides-first lesson while chapters
+  lead, as before, and a chapter-only lesson while slides lead
+  (`explico-chapter-lesson`, a sheet). A hidden edition is listed while it is
+  the open page. The row's own link carries its mark at the row's end, as
+  before; the icon carries its own on its corner
+  (`a.layout-edition-other[data-page-mark]`, drawn by `i.layout-edition-mark`),
+  and the progress rail counts rows, the row holding the open page being the
+  reader's place. The two controls (above, under Added) and the marks' line
+  share the panel's foot, `.explico-sidebar-foot`, which draws the separator
+  the line drew. Without scripts the sidebar is what the compiler emits: each
+  chapter, then its "Slides" row. In the manifest's `sidebar`, every item of
+  a lesson names its edition, lesson and title (`data-edition`,
+  `data-lesson`, `data-title` in `attrs`), so a chapter is `{ slug, attrs }`
+  where it was a bare slug; `sidebarLessonSlug` reads an item's lesson as its
+  `data-lesson` when that is its own `slug`, and `buildSidebar` takes
+  `titleOf`, the lesson titles.
+- **Pointing at a part's `»` lights its Overview row**, or its compact tile,
+  as a pointer on the row would: both open the part's page. Keyboard focus
+  on `»` counts.
+- **The marks' line stays, and offers "Mark all as unseen" beside "Mark all
+  as seen".** The line under the chapter list is there whenever the reader's
+  record is kept, with a mark on screen or none, so either reset can be
+  undone; "Mark all as unseen" forgets every page but the open one, which is
+  open. What a button did is said in a `role="status"` line inside it
+  ("Every page is marked as seen." / "… as not opened yet."), where
+  "Mark all as seen" used to replace the line with that sentence and leave
+  no way back. A button with nothing to change is `aria-disabled`: it keeps
+  its place, and focus.
+- **The sidebar's "Mark all as seen" and "Mark all as unseen" cover every
+  deck's frames too** (D9 of `docs/plans/deck-navigation/`), so a deck's
+  page shows them all seen, or none, at once and on its next load. In a
+  course with a deck, the status they leave says so: "Every page and slide
+  is marked as seen." and "Every page is marked as not opened yet, and every
+  slide as not shown yet." The marks' payload (`PageMarksPayload.decks`)
+  carries each deck's frame ids, and a button is in use while a deck's frame
+  has something to change, as a page does. A deck's page now holds a
+  "Present from here, slide N" button in every frame's line, so a browser
+  test that finds the deck's Present button by name adds `exact: true`.
+
+### Fixed
+
+- **A hovered row in either sidebar shows its fill in the dark theme.** The
+  fill was `--sl-color-gray-6`, which is the dark course sidebar's own
+  colour, so a hovered chapter or part there changed only its text colour.
+  The fill is now each sidebar's colour with 10 % ink mixed in
+  (`--ex-row-hover`), whatever colour the sidebar is.
+- **A single-language course no longer warns that Starlight's `i18n`
+  collection is missing or empty.** `explico/content-config` now exports the
+  collection with Starlight's schema and an empty English in-memory fallback;
+  authored JSON or YAML translations under `content/i18n/` replace it. The
+  playground also declares its canonical Astro `site`, clearing the sitemap
+  warning alongside its new `404.mdx`.
+- **With a part's deck open, the chapter on screen lights its slides in the
+  sidebar, and the rail follows it.** Opened at a chapter's section
+  (`/motion/slides/#slide-17`) only the part's deck was lit, not the
+  chapter's slides icon that opened it, and the rail stopped at the part's
+  row. Each frame of a covered section now carries its chapter
+  (`data-chapter`, from `frameChapters` in `file.data.explicoDeck`), and the
+  deck's page tells the sidebar the chapter of the frame in view on the
+  study page, or shown in Present mode and the presenter
+  (`DECK_FRAME_EVENT`, `explico:deck-frame`, with `{ deck, chapter }`, and
+  `data-deck-chapter` on `<html>`). The sidebar lights that chapter's section
+  link with `aria-current="location"`, as the open page lights its own, and
+  the rail covers every row before it; the title and outcomes frames, which
+  belong to no chapter, light none.
+- **"Continue at slide N" is offered whenever a reader left a deck past its
+  first frame, and presents from there.** Present mode writes `#slide-N`
+  into the address so a slide can be shared, and the offer was made only on
+  a page opened without one, once: after Esc, and after a reload of that
+  address, it was missing. `refreshResume` in `deck-controller.ts` now
+  renders it as the page opens and again whenever Present mode ends,
+  whatever the address says: a button (`data-deck-resume`) beside Present,
+  where it was a link to the frame, that presents from the frame to continue
+  at (above). Once the reader was shown all of the last frame it reads
+  "Present again" and presents from the first.
+  It is the reader's own (`data-explico-export-chrome`), so a deck's
+  standalone HTML and Markdown never carry it. A link to `#slide-N` still
+  opens the study page at that frame.
+- **Opening a page no longer writes its sections' state to the browser.**
+  `wirePersistedDetails` meant to save only a section the reader folded or
+  opened, but restoring a section's default state fired a `toggle` of its
+  own, which it saved too: every page with collapsible sections left one
+  `disclosure:<path>:<section>` entry per section on a mere visit, a list of
+  the pages a reader opened. Only a state the reader moved a section to is
+  saved now.
+- **A notation entry's body honours `fixedIndex` (rule N23).** Its glyph table
+  dropped the flag that a lesson's keeps, so in the glossary `r_2` took the
+  card of the family `r_m` although `m` was marked `fixedIndex: true`. The
+  entry's body and a lesson now agree; the error names the card that fixed the
+  index. The render's message for an entry's body no longer suggests
+  `notation.local`, which an entry does not have.
+- **`astro build` reports a notation entry's error at the file's own line.**
+  Astro's glob loader renders an entry from its body alone, so the line in
+  `entry.md:1:43` (the message, and the loader's `Failed to parse Markdown file`
+  header) counted from the end of the frontmatter. `remark-notation.mjs` now
+  finds where the body sits in the file (`source-lines.mjs`, read only while a
+  failure or warning is reported) and moves the location, so the build and
+  `validate:content` agree. A lesson is compiled whole and was already right.
+- **An unresolved-glyph error quotes the math it is in** (`… "w", in $w_3$.`),
+  in `astro build` and in `validate:content`, so a symbol can be searched for
+  whatever the line says. The sentence before `Introduce the symbol …` gains
+  `, in $…$`; a test matching the text up to the token is unaffected.
+- **The published package loads again.** 0.13.0 and 0.13.1 shipped
+  `dist/compiler/exports/{latex,markdown}/serialize.js` importing
+  `dist/components/float-name.js`, which no one built, so `astro build`,
+  `astro dev` and `astro check` stopped with "Unable to load your Astro
+  config". `float-name.ts` (no Astro, no DOM beyond the `Element` that
+  `floatOf` takes) moved from `src/components/` to `src/reference/`, which
+  tsup compiles. It was never a documented author-facing export; a course
+  that patched the module in (`patches/explico@0.13.1.patch`) deletes the
+  patch.
+- **`migrating.md`'s 0.13.0 → 0.13.1 section said the manifest schema stays
+  v29.** It is v31.
+- **A figure no longer fails on `e`, `\pi`, `i` or `d`.** `renderLabMath`
+  leaves a plain base-library atom without a card, as a lesson's math does, but
+  `assertFigureSymbolsBound` / `unboundFigureSymbols` (`figure-symbols.ts`)
+  then failed the build on it ("figure symbols without a notation card"). The
+  check now exempts the same library (`isBaseLibraryGlyph`,
+  `base-library.mjs`), in a power too (`e^{i\pi}`). An index (`e_i`, rule N23),
+  a decorated (`\hat{e}`, rule N22) or a styled (`\mathbf{e}`) letter is
+  another symbol and is still reported.
+- **The build reports every page with a figure symbol that has no card, or a
+  notation trigger with no popup entry, at once.** `astro:build:done` threw on
+  the first page and never reached the later ones or the exports. It now checks
+  all pages and throws once with the whole list (`assertNoUnboundFigureSymbols`
+  is new in `figure-symbols.ts`; `assertFigureSymbolsBound` is unchanged). The
+  standalone, part, course and LaTeX exports still wait for a clean check.
+- **`lab-katex-direct` is reported per lesson.** A helper that imports `katex`
+  was reported once, against the first lesson that reached it, so
+  `content check <lesson>` could not tell whether another lesson was clean. It
+  is now reported once for each lesson whose imports reach it, with that
+  lesson's own chain, and a lesson that reaches none is clean. The code and
+  severity are unchanged. `validate:content` prints one error per lesson while
+  several share a helper.
+- **A card only a lab template uses now reaches the page.** The package serves
+  `explico/reference/*` from `dist/`, but `LessonFooter.astro` imports the
+  TypeScript source of `page-notation`, so the two copies had separate
+  registries. A key bound by `labMathScope` or `renderLabMath` in a template
+  (and a derived N23 card it registered) was never in the card payload, and the
+  hover opened nothing. The registries now live on `globalThis` under
+  `Symbol.for('explico.reference.page-notation')`, one per process.
+- **Rule N23 no longer asks for the set of a letter that is not an index.**
+  `index-range` named `b` in `\nabla_{b_n}` (the base of the carded symbol
+  `b_n`, whose own index `n` is checked in its own right) and `g` in
+  `\mathbb{E}_{Z \sim g}` (a density in a condition), and asked for a `range`
+  on the card of `b_n` as "the set of the running index b". A letter that sits
+  inside a larger symbol with a card of its own, and every letter of a
+  subscript slot that holds a relation (`\sim`, `=`, `\in`, …), is no longer a
+  running index. A letter with a card of its own, and one inside an author's
+  `\explain`, is checked as before.
+- **A family whose index is juxtaposed letters now reaches its instances.** The
+  entry `x_{ij}` (`K_{ij}`, `r_{ik}`) gave its card to the exact form only, so
+  `x_{i1}`, `x_{12}` and `K_{ji}` failed rule N4 as unresolved and the message
+  said the entry "explains its own instances only". A slot of two or more
+  lowercase letters is now a double index: the family matches a run of as many
+  letters and digits (`x_{i1}`, `x_{12}`, `x_{ji}`), as `x_{i,j}` always did,
+  and never `x_i`, `x_{ijk}` or `x_{i+1}`. A page that has both `x_{ij}` and
+  `x_k` as entries now fails `ambiguous-base-fallback` on `x_{12}`, which both
+  fit; wrap that instance in `\explain`.
+- **An `\explain` inside a family instance's index no longer unbinds the
+  family.** `\beta_{\explain{count}{K}}` and `x_{\explain{iter}{k}}` left the
+  base unresolved, because the match was dropped for enclosing the author's
+  wrap. A symbol that holds an `\explain` in its own subscript now keeps its
+  card, and the two wraps nest: `\explain{beta-j}{\beta_{\explain{count}{K}}}`.
+  A match that only straddles a wrap's braces is still dropped.
+- **A wrapped family instance is not re-bound inside.** On a page with the
+  family `\sigma_k` and a plain `\sigma`, `\explain{component-sd}{\sigma_1}`
+  became `\explain{component-sd}{\explain{population-sd}{\sigma}_1}`, so hovering
+  the σ opened the population standard deviation. The wrap names the indexed
+  symbol, so its base takes no other entry's card; this holds under a power
+  (`\sigma_1^2`), for a two-letter family and for a font-styled base. A wrap
+  around a symbol whose key has another base still binds the glyphs inside.
+- **An active prose link no longer falls below AA contrast.** 0.13.1 blended
+  the highlight of every active notation target (`mix-blend-mode: multiply`
+  in the light theme, `screen` in the dark one), but the blend exists for a
+  symbol in math, whose KaTeX boxes paint over the glyph to their left. On a
+  prose term link (`a.notation-term`), `multiply` darkened the tint over a
+  glossary row's panel and the engine's own link colour dropped from 4.75:1
+  to 4.4:1, which axe reports as `color-contrast`. The blend is now scoped to
+  `.katex-html`; a prose link keeps the opaque tint it had before 0.13.1. A
+  course that added `a.notation-term.is-notation-active { color: … }` to pass
+  axe deletes it.
+- **`unresolved-glyph` names the card that fixed a family's index.** Marking
+  the card of `m` `fixedIndex: true` turns the family `r_m` into a single
+  symbol (rule N23), so `r_2` stops being its instance. The error then blamed
+  "a bare r" and offered `\explain{periodic-rate}{r}`, which is the wrong
+  repair. For a subscripted symbol that a family would have explained, it now
+  says "`r_2` would be an instance of `periodic-rate`, but `m` is marked
+  `fixedIndex` on `compounding-frequency`", and to give that card a `range`
+  if `m` runs over a set. The same holds for an entry that carries
+  `fixedIndex` itself, and for an index entry that fixes the subscript. A
+  truly bare `r` keeps its message. The error `astro build` throws for the
+  same symbol says it too. `index-range`'s offer of `fixedIndex: true` now
+  says that a family indexed by that letter then explains none of its
+  instances. `resolveMathGlyphs` returns `instance` and `fixedLenders` on such
+  an unresolved item, and `math-glyphs.mjs` exports `fixedLenderMessage`.
+
+- **The `[?]` About panel opens on screen in the phone menu.** The menu's
+  copy of the butto
+### Removed
+
+- **`gloss-wants-promoting`.** It fired on three identical glosses and never
+  did in any course; `meaning-repeated` reports the same copy at two. A
+  `lint-ignore.yml` line for it can be deleted.
+n starts its row, and the panel hung from the button's end,
+  so it ran off the screen's start edge and past the end of the menu. Below
+  50rem it is now a sheet fixed under the header, centred, at most 21rem
+  wide.
+
+- **The `[?]` button is round in the phone menu.** The sidebar's rules for a
+  part's header (`.layout-navigation-content summary`) are unlayered and
+  reached it, making it a rounded square with the `?` at its start; they now
+  skip `.about-toggle`.
+
+- **A hover peek no longer overwrites a collapsed section's saved state.** A
+  collapsed section peeks (its content floats open) when the pointer is on its
+  title, and a peek has to set `details.open = true` to render, which fired the
+  native `toggle` that `wirePersistedDetails` saves as "open". A reader who
+  collapsed a section and reloaded with the pointer still on its title (the
+  browser sends the pointer's `pointerenter` after the reload) found it open
+  from then on: `open` was stored over `closed`. A peek now carries
+  `data-explico-temporary-open`, which `persisted-disclosure.ts` already skips,
+  from its first `open = true` until the `toggle` its closing fires; a click
+  that commits the peek removes it. `CollapsibleSections.astro`'s module
+  comment already said a peek "never persists anything".
+
 ## [0.13.1] - 2026-10-07
 
 ### Fixed
@@ -3446,7 +4433,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.13.1...HEAD
+[Unreleased]: https://github.com/danieltuzes/explico/compare/v0.15.0...HEAD
+[0.15.0]: https://github.com/danieltuzes/explico/compare/v0.14.0...v0.15.0
+[0.14.0]: https://github.com/danieltuzes/explico/compare/v0.13.1...v0.14.0
 [0.13.1]: https://github.com/danieltuzes/explico/compare/v0.13.0...v0.13.1
 [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