@brandon_m_behring/book-scaffold-astro 4.16.0 → 4.18.0

package/CLAUDE.md

@@ -96,7 +96,7 @@ Two callout families coexist. Authors import what they need.
 
 **Tools family** (`src/components/callouts/`, 8 components): `SkillBox`, `CaseStudy`, `ConceptBox`, `KeyIdea`, `TryThis`, `Recovery`, `Convergence`, `Divergence`.
 
-**Academic family** (`src/components/callouts/`, 10 components): `NoteBox`, `ExampleBox`, `DynConnect`, `InsightBox`, `WarnBox`, `CounterBox`, `TipBox`, `OpenQuestion`, `PaperBox`, `ResultBox`. Plus `Theorem` (unified for theorem/proposition/lemma/corollary/definition/example/exercise/remark/proof). **Props (v4.14.3, #121):** `kind=` is canonical; `type=` is accepted as a legacy alias (likewise `title=`/`label=` alias `name=`). An absent or unknown kind **throws at build** (via `src/lib/theorem-label`) rather than rendering an empty label; `book-scaffold validate` flags a `<Theorem>` with neither `kind=` nor `type=` even earlier.
+**Academic family** (`src/components/callouts/`, 10 components): `NoteBox`, `ExampleBox`, `DynConnect`, `InsightBox`, `WarnBox`, `CounterBox`, `TipBox`, `OpenQuestion`, `PaperBox`, `ResultBox`. Plus `Theorem` (unified for theorem/proposition/lemma/corollary/definition/example/exercise/remark/proof). **Props (v4.14.3, #121):** `kind=` is canonical; `type=` is accepted as a legacy alias (likewise `title=`/`label=` alias `name=`). An absent or unknown kind **throws at build** (via `src/lib/theorem-label`) rather than rendering an empty label; `book-scaffold validate` flags a `<Theorem>` with neither `kind=` nor `type=` even earlier. **Numbering (v4.18.0, #126):** a theorem with an `id` auto-numbers from `labels.json` — the same index `<XRef>` reads — so the heading number equals every cross-reference to it by construction; explicit `n=` is a fallback for un-id'd theorems. `build-labels` indexes the kind-accurate word (`Proposition 8.1`, not a kind-blind `Theorem 8.1`) and throws on an unknown kind.
 
 **Pedagogy family** (v4.1.0+, any profile, 3 components): `Pitfall` (rose; "common mistake" — distinct from `WarnBox`'s preemptive warning), `WorkedExample` (plum; collapsible `<details>` block with `#worked-example-{id}` anchor for deep links), `YouWillLearn` (gold; chapter-opener with optional `prerequisites` prop). Slot bullets/code freely; render at any preset.
 
@@ -104,6 +104,8 @@ Two callout families coexist. Authors import what they need.
 
 **Provenance** (v4.8.0, any profile, **auto-injected by the chapter route — not author-imported**): per-chapter "How this was made" audit-trail block, rendered from the optional `provenance` frontmatter (`ai_tools`, `prompts_archive`, `decisions_log`, `audit_history`, `citation_backstop`). **Opt-out**: a chapter with no `provenance` shows a fallback ("Audit history not yet recorded"). Distinct from `AICollaborationDisclosure` (book-level, manual model+role disclosure). Repo-relative path fields render as `<code>`; only `http(s)` values link.
 
+**Study-guide (v4.17.0+, #112; opt-in).** A schema-validated `questions` content collection drives an exam-prep "question bank". Author questions under `src/content/questions/**.{md,mdx}` — frontmatter `id` (unique, required) / `type` (`mcq`|`free`|`cloze`) / `chapter` / `domain` (+ optional `part`/`bloom_level`/`objective_id`/`difficulty`), MDX body = the stem. MCQ carries `options: [{ id, text, correct }]` (exactly one `correct: true`); free-response carries an `answer` (model answer). An MCQ must **not** set `answer` — its answer is the option marked `correct`, and explanations for any type go in a `<Rationale>` body block. Declare the per-book domain taxonomy in `defineBookConfig({ examDomains: ['…'] })` — a question whose `domain` isn't registered **throws at build** (fail-loud, like `<BookLink>`'s `siblingBooks`). Enable the static `/practice-exam` route with `defineBookConfig({ routes: { practiceExam: true } })` (renders the bank grouped by domain with answers behind a `<details>` reveal; `cloze` is reserved/render-deferred). `<ObjectiveMap />` renders the exam-domain → chapter coverage matrix auto-derived from the collection (no separate data file). `<Rationale>` is a collapsible answer/explanation marker for a question's MDX body. (Scoring + diagnostics + appendix + flashcards are later increments — see `docs/plans/active/study-guide-epic_*.md`.)
+
 Full reference in `recipes/04-component-library.md`.
 
 ### Theme-change event (v4.14.2)
@@ -168,6 +170,7 @@ For monorepo Astro projects (Astro project in subdir), prefix build + deploy com
 - Unknown `<XRef id>` — id not in `labels.json` (XRef silently renders `[?label]` otherwise)
 - Missing `<Figure src>` files under `public/`
 - Internal markdown links that don't resolve
+- Study-guide questions (v4.17.0, #112) — a question whose frontmatter `domain` isn't in `examDomains`, and duplicate question `id`s
 
 See `recipes/09-validation.md` to extend.
 

package/components/ObjectiveMap.astro

@@ -0,0 +1,113 @@
+---
+/**
+ * <ObjectiveMap> — exam-domain → chapter coverage matrix (v4.17.0, Tier 3 #117).
+ *
+ * The reader-facing twin of a CompTIA/Cisco objective-coverage table. AUTO-
+ * DERIVED from getCollection('questions'): for each configured exam domain
+ * (defineBookConfig({ examDomains })), it shows which chapters carry ≥1 question
+ * in that domain. There is no separate coverage data file — the matrix is
+ * computed from the question bank, so it cannot drift from reality (and it can't
+ * render at all unless the per-book examDomains taxonomy is populated and
+ * consistent, which is the cheapest proof that taxonomy pays off).
+ *
+ * A domain with no questions renders an honest "—" gap rather than being
+ * omitted, so the table never implies coverage the bank doesn't have (same
+ * coverage-honesty discipline as /convergence).
+ *
+ * Drop into a front-matter / intro page. Any profile. Twin-gated: with no
+ * questions collection, renders an honest note instead of touching the
+ * collection (which would throw when unregistered).
+ */
+import bookConfig from 'virtual:book-scaffold/book-config';
+import { getCollection } from 'astro:content';
+import { deriveObjectiveMap, distinctChaptersSorted } from '../src/lib/questions';
+import { assertKnownDomain } from '../src/lib/exam-domains';
+
+interface Props {
+  /** Heading above the table. Defaults to "Exam objective coverage". */
+  title?: string;
+}
+const { title = 'Exam objective coverage' } = Astro.props;
+
+// Presence-gate: only touch the collection when the directory holds files.
+const questionModules = import.meta.glob('/src/content/questions/**/*.{md,mdx}', {
+  query: '?raw',
+  import: 'default',
+  eager: true,
+});
+const hasQuestions = Object.keys(questionModules).length > 0;
+
+const entries = hasQuestions
+  ? await getCollection('questions', (e) => !e.data.draft)
+  : [];
+// Fail loud (like /practice-exam): a question with an unregistered / typo'd
+// domain must throw at build, not silently vanish from the coverage matrix.
+for (const e of entries) {
+  assertKnownDomain(bookConfig.examDomains, e.data.domain, { id: e.data.id });
+}
+const coverage = deriveObjectiveMap(entries);
+const domains = bookConfig.examDomains ?? [];
+// Column set: chapters that carry ≥1 question, in numeric-aware order
+// (distinctChaptersSorted — a bare .sort() would order "10" before "2").
+const chapters = distinctChaptersSorted(entries);
+---
+{domains.length === 0 ? (
+  <p class="objective-map-empty">
+    No <code>examDomains</code> configured. Declare them in
+    <code>defineBookConfig({'{'} examDomains: [&hellip;] {'}'})</code> to render the coverage map.
+  </p>
+) : chapters.length === 0 ? (
+  <p class="objective-map-empty">
+    No questions found under <code>src/content/questions/</code> yet — the coverage map
+    populates as you add questions tagged with these domains.
+  </p>
+) : (
+  <figure class="objective-map">
+    <figcaption class="objective-map-title">{title}</figcaption>
+    <table class="objective-map-table">
+      <thead>
+        <tr>
+          <th scope="col">Domain</th>
+          {chapters.map((c) => <th scope="col">{c}</th>)}
+        </tr>
+      </thead>
+      <tbody>
+        {domains.map((domain) => {
+          const covered = coverage.get(domain) ?? new Set();
+          const isGap = covered.size === 0;
+          return (
+            <tr class={isGap ? 'objective-map-gap' : undefined}>
+              <th scope="row">{domain}</th>
+              {chapters.map((c) => (
+                <td aria-label={covered.has(c) ? `${domain} covered in ${c}` : undefined}>
+                  {covered.has(c) ? '✓' : '—'}
+                </td>
+              ))}
+            </tr>
+          );
+        })}
+      </tbody>
+    </table>
+  </figure>
+)}
+
+<style>
+  .objective-map { margin-block: 1.5rem; overflow-x: auto; }
+  .objective-map-title { font-weight: 600; margin-block-end: 0.5rem; }
+  .objective-map-empty { color: var(--color-text-muted, #6b7280); }
+  .objective-map-table { border-collapse: collapse; width: 100%; font-size: 0.9rem; }
+  .objective-map-table th,
+  .objective-map-table td {
+    border: 1px solid var(--color-border, #e5e7eb);
+    padding: 0.35rem 0.55rem;
+    text-align: center;
+  }
+  .objective-map-table th[scope='row'] {
+    text-align: start;
+    text-transform: capitalize;
+    white-space: nowrap;
+  }
+  .objective-map-table td { color: var(--color-accent, #4f46e5); }
+  .objective-map-gap th[scope='row'] { color: var(--color-text-muted, #6b7280); }
+  .objective-map-gap td { color: var(--color-text-muted, #6b7280); }
+</style>

package/components/Rationale.astro

@@ -0,0 +1,38 @@
+---
+/**
+ * <Rationale> — collapsible answer/explanation for a study-guide question
+ * (v4.17.0, Tier 3). Renders its slot inside a <details> so the answer stays
+ * hidden until the reader chooses to reveal it (Bjork desirable-difficulties:
+ * delayed feedback aids retention). Authored in a question's MDX body; the
+ * answer-rationale back-appendix (#114) will later hoist these into an appendix
+ * using this same marker — so a rich, cited rationale has a stable home now.
+ *
+ * Any profile. Register it in src/mdx-components.ts (defineMdxComponents) to use
+ * inside src/content/questions/**.mdx. Slot freely: prose, math, <Cite>, code.
+ */
+interface Props {
+  /** Summary label for the reveal. Defaults to "Answer & rationale". */
+  title?: string;
+}
+const { title = 'Answer & rationale' } = Astro.props;
+---
+<details class="question-rationale">
+  <summary>{title}</summary>
+  <div class="question-rationale-body"><slot /></div>
+</details>
+
+<style>
+  .question-rationale {
+    margin-block: 0.75rem;
+    border-inline-start: 3px solid var(--color-accent, #4f46e5);
+    padding-inline-start: 0.75rem;
+  }
+  .question-rationale > summary {
+    cursor: pointer;
+    font-weight: 600;
+    color: var(--color-accent, #4f46e5);
+  }
+  .question-rationale-body {
+    margin-block-start: 0.5rem;
+  }
+</style>

package/components/Theorem.astro

@@ -10,29 +10,54 @@
  * (ssm-foundations ch1–11 + the LaTeX-env mental model pass `type=`). `name`
  * is canonical with `title=`/`label=` accepted. An absent or unknown kind
  * THROWS at build (see `src/lib/theorem-label`) — it never renders an empty
- * label. Pass `n` to number the environment.
+ * label.
  *
- * Auto-numbering note: the LaTeX preamble shares a counter between
- * theorem/proposition/lemma/corollary and gives definition/example/exercise/
- * remark their own; in MDX the author passes `n` explicitly when it matters.
+ * Auto-numbering (#126): when the theorem has an `id`, its number is read from
+ * `src/data/labels.json` — the same map <XRef> resolves — so the heading number
+ * EQUALS every cross-reference to it by construction. No hand-passed `n=`, no
+ * drift; inserting a theorem renumbers the chapter from one counter
+ * (`book-scaffold build-labels`). Explicit `n=` stays a fallback for an un-id'd
+ * theorem (or before labels.json is built); when an id resolves, the labels.json
+ * number wins so the two surfaces can never disagree.
  *
  * Usage:
- *   <Theorem kind="theorem" n="4.2" name="Stable continuous-time eigenvalues" id="thm-w4-stability">
- *     For …
+ *   <Theorem kind="theorem" name="Stable continuous-time eigenvalues" id="thm-w4-stability">
+ *     For …                      // number auto-resolved from labels.json
  *   </Theorem>
  *
  *   <Theorem kind="definition" n="4.1" name="HiPPO-LegS">
- *     The HiPPO-LegS state matrix …
+ *     The HiPPO-LegS state matrix …   // explicit n= (un-cross-referenced)
  *   </Theorem>
  */
-import { theoremLabel, type TheoremLabelProps } from '../src/lib/theorem-label';
+import { theoremLabel, resolveTheoremNumber, type TheoremLabelProps } from '../src/lib/theorem-label';
 
 interface Props extends TheoremLabelProps {
   id?: string;
 }
 
+// #126: resolve THIS theorem's number from the same labels.json that <XRef>
+// reads, so the heading number == the cross-reference display by construction.
+// build-labels.mjs writes { href, display, number } keyed by id. Mirror XRef's
+// project-root glob (Vite resolves `/` to the consumer root, not the package);
+// a missing file → empty map → fall back to explicit n= (the same soft-degrade
+// path as XRef — the validator catches unknown ids at CI).
+type LabelEntry = { href: string; display: string; number?: string | null };
+const labelsModules = import.meta.glob<{ default: Record<string, LabelEntry> }>(
+  '/src/data/labels.json',
+  { eager: true },
+);
+const labelsMap = (labelsModules['/src/data/labels.json']?.default ?? {}) as Record<
+  string,
+  LabelEntry
+>;
+
 const { id } = Astro.props;
-const { kind, fullLabel } = theoremLabel(Astro.props);
+// labels.json (by id) is the number source; explicit n= is the fallback when no
+// id resolves. When both exist the shared source wins — that is what guarantees
+// heading == xref (a stale n= can't reintroduce drift).
+const entry = id ? labelsMap[id] : undefined;
+const resolvedN = resolveTheoremNumber(entry, Astro.props.n);
+const { kind, fullLabel } = theoremLabel({ ...Astro.props, n: resolvedN });
 ---
 <div class="theorem" data-kind={kind} id={id}>
   <span class="theorem-label">{fullLabel}.</span>

package/dist/index.d.ts

@@ -1,6 +1,7 @@
 import { AstroUserConfig, AstroIntegration } from 'astro';
-import { c as BookConfigOptions, f as BookScaffoldIntegrationOptions, Y as volatilityLevels, h as ChaptersRenderer, r as academicParts, o as Style } from './types-BmBIV5qD.js';
-export { A as AcademicChapter, B as BOOK_PRESETS, a as BOOK_PROFILES, b as BookConfigError, d as BookPreset, e as BookProfile, g as BookSchemasOptions, C as ChapterFor, i as CourseNotesChapter, F as FreshnessAffordance, j as FrontmatterRouteConfig, M as MinimalChapter, P as PartKey, k as PartialRouteToggles, l as ProfileDefinition, m as Provenance, R as ResearchPortfolioChapter, n as RouteToggles, S as StatusBadge, p as StyleInput, T as ToolsChapter, V as VolatilityBadge, q as academicChapterSchema, s as changeKinds, t as changelogSchema, u as chapterStatus, v as citationBackstops, w as composeStyles, x as courseNotesChapterSchema, y as defineProfile, z as defineStyle, D as minimalChapterSchema, E as normalizeFrontmatterConfig, G as patternCategories, H as patternsSchema, I as provenanceObject, J as provenanceSchema, K as researchPortfolioChapterSchema, L as resolvePreset, N as resolveProfile, O as sourceTiers, Q as sourceTiersResearch, U as sourcesSchema, W as toolSlugs, X as toolsChapterSchema } from './types-BmBIV5qD.js';
+import { d as BookConfigOptions, g as BookScaffoldIntegrationOptions, a5 as volatilityLevels, i as ChaptersRenderer, t as academicParts, Q as Question, q as Style } from './types-CMPuyZGP.js';
+export { A as AcademicChapter, B as BOOK_PRESETS, a as BOOK_PROFILES, b as BloomLevel, c as BookConfigError, e as BookPreset, f as BookProfile, h as BookSchemasOptions, C as ChapterFor, j as CourseNotesChapter, F as FreshnessAffordance, k as FrontmatterRouteConfig, M as MinimalChapter, P as PartKey, l as PartialRouteToggles, m as ProfileDefinition, n as Provenance, o as QuestionType, R as ResearchPortfolioChapter, p as RouteToggles, S as StatusBadge, r as StyleInput, T as ToolsChapter, V as VolatilityBadge, s as academicChapterSchema, u as bloomLevels, v as changeKinds, w as changelogSchema, x as chapterStatus, y as citationBackstops, z as composeStyles, D as courseNotesChapterSchema, E as defineProfile, G as defineStyle, H as minimalChapterSchema, I as normalizeFrontmatterConfig, J as patternCategories, K as patternsSchema, L as provenanceObject, N as provenanceSchema, O as questionDifficulties, U as questionSchema, W as questionTypes, X as refineQuestion, Y as refinedQuestionSchema, Z as researchPortfolioChapterSchema, _ as resolvePreset, $ as resolveProfile, a0 as sourceTiers, a1 as sourceTiersResearch, a2 as sourcesSchema, a3 as toolSlugs, a4 as toolsChapterSchema } from './types-CMPuyZGP.js';
+export { KIND_LABEL, ResolvedTheoremLabel, THEOREM_KINDS, TheoremKind, TheoremLabelProps, resolveTheoremNumber, theoremLabel } from './lib/theorem-label.js';
 import 'astro/zod';
 
 /**
@@ -204,54 +205,6 @@ declare function academicPartOrdinal(part: string): number;
  */
 declare function academicPartHeading(part: string): string;
 
-/**
- * theorem-label — resolve a `<Theorem>` component's label from its props,
- * failing loud instead of rendering a silent empty label (#121).
- *
- * Vocabulary: `kind` is canonical; `type` is an accepted **legacy alias** (many
- * consumer books — ssm-foundations ch1–11 — and the LaTeX `\begin{<env>}`
- * mental model pass `type=`). Likewise `name` is canonical with `title`/`label`
- * accepted as aliases. Aliases keep existing content valid; they are synonyms,
- * not deprecations, so they neither warn nor throw.
- *
- * Failure mode: an absent or unrecognized kind THROWS a build-failing,
- * actionable error rather than computing `KIND_LABEL[undefined]` → a bare "."
- * (the v4.8–4.14 silent defect, live across 32+ ssm-foundations theorems). A
- * typo'd kind — silent before — now stops the build with the offending value.
- *
- * Extracted from the `Theorem.astro` frontmatter so the contract is unit-tested
- * in the pure `node --test` suite (see tests/theorem-label.test.mjs) — the same
- * single-source-of-truth move as `academic-parts.ts` (#95).
- */
-declare const THEOREM_KINDS: readonly ["theorem", "proposition", "lemma", "corollary", "definition", "example", "exercise", "remark", "proof"];
-type TheoremKind = (typeof THEOREM_KINDS)[number];
-declare const KIND_LABEL: Record<TheoremKind, string>;
-interface TheoremLabelProps {
-    /** Canonical environment selector. */
-    kind?: string;
-    /** Legacy alias for `kind` (LaTeX-env mental model; ssm-foundations ch1–11). */
-    type?: string;
-    /** Explicit number, e.g. "4.2"; omit for an unnumbered environment. */
-    n?: string;
-    /** Canonical display name shown in parentheses. */
-    name?: string;
-    /** Legacy aliases for `name`. */
-    title?: string;
-    label?: string;
-}
-interface ResolvedTheoremLabel {
-    /** The validated, canonical kind (for `data-kind`). */
-    kind: TheoremKind;
-    /** The composed "Kind N (Name)" label (never empty). */
-    fullLabel: string;
-}
-/**
- * Resolve a `<Theorem>`'s `kind` (canonical or legacy `type=`) and compose its
- * full label. Throws — never returns an empty label — when the kind is absent
- * or not one of {@link THEOREM_KINDS}.
- */
-declare function theoremLabel(props: TheoremLabelProps): ResolvedTheoremLabel;
-
 /**
  * repo-url — resolve and build GitHub source links for CodeRef / CodeBlock.
  *
@@ -337,6 +290,72 @@ declare function assertEnumProp<T extends string>(value: unknown, allowed: reado
  */
 declare function resolveBookHref(siblingBooks: Record<string, string> | null | undefined, book: string, to: string): string;
 
+/**
+ * exam-domains — validate a question's `domain` against the consumer's closed
+ * `examDomains` taxonomy (Tier 3, #112).
+ *
+ * Exam domains are PER-BOOK (Cisco security domains ≠ CompTIA objectives ≠ a
+ * math syllabus's topics), so they can't be a hardcoded `z.enum` in the schema.
+ * The consumer declares them once — `defineBookConfig({ examDomains: [...] })`,
+ * threaded through the `virtual:book-scaffold/book-config` module — and a
+ * question whose `domain` is not in that list THROWS at build rather than
+ * silently mis-weighting a blueprint or dropping a row from the objective-map.
+ *
+ * Membership can't be a Zod invariant: `questionSchema` is constructed at
+ * package-load time, outside any consumer context, so it can't see
+ * `examDomains` (the same constraint that put `siblingBooks` validation in
+ * lib/book-link.ts rather than the schema). So Zod checks `domain` is a
+ * non-empty string; THIS runs at the route/build layer where the resolved
+ * config is available. Mirrors `resolveBookHref` (lib/book-link.ts).
+ */
+declare function assertKnownDomain(examDomains: readonly string[] | null | undefined, domain: string, ctx: {
+    id: string;
+}): string;
+
+/**
+ * src/lib/questions-derive.ts — PURE grouping + objective-map derivation for the
+ * study-guide `questions` collection (Tier 3, #112).
+ *
+ * No `astro:content` import, so this is safe in the Node-loaded main entry and
+ * unit-tested directly from dist/ (tests/questions.test.mjs). The Astro-context
+ * `getCollection` wrapper lives in questions.ts — same split as
+ * chapter-sort.ts (pure) / chapters.ts (Astro wrapper).
+ */
+
+/** Stable string label for a chapter ref (number or academic-style string). */
+declare function chapterLabel(chapter: number | string): string;
+/** Sort questions by chapter then id (stable, deterministic). Pure. */
+declare function sortQuestions<T extends {
+    data: Pick<Question, 'chapter' | 'id'>;
+}>(entries: readonly T[]): T[];
+/** Group entries by `domain`, preserving input order within each bucket. */
+declare function groupByDomain<T extends {
+    data: Pick<Question, 'domain'>;
+}>(entries: readonly T[]): Map<string, T[]>;
+/** Group entries by `chapter` (string label), preserving input order. */
+declare function groupByChapter<T extends {
+    data: Pick<Question, 'chapter'>;
+}>(entries: readonly T[]): Map<string, T[]>;
+/**
+ * Domain → set of chapter labels that have ≥1 question in that domain. The data
+ * backbone of `<ObjectiveMap>` (#117): the coverage matrix is *derived* from the
+ * question bank, so it can't drift from a separately-maintained table — the
+ * cheapest proof the per-book `examDomains` taxonomy is populated + consistent.
+ */
+declare function deriveObjectiveMap<T extends {
+    data: Pick<Question, 'domain' | 'chapter'>;
+}>(entries: readonly T[]): Map<string, Set<string>>;
+/**
+ * Distinct chapter labels across the entries, in numeric-aware order (numeric
+ * chapters before string slugs, each ordered) — the column set for
+ * `<ObjectiveMap>`. Dedupes by label, sorts the underlying chapter values via
+ * the same `chapterOrder` as `sortQuestions`, then labels. A bare `.sort()` on
+ * the labels would put "10" before "2" (the chapter-column sort bug).
+ */
+declare function distinctChaptersSorted<T extends {
+    data: Pick<Question, 'chapter'>;
+}>(entries: readonly T[]): string[];
+
 /**
  * src/styles/built-in.ts — toolkit-shipped Styles, one per BookPreset (v4.0.0).
  *
@@ -438,4 +457,4 @@ type TipsConfigInput = Omit<TipsConfig, typeof TipsConfigBrand | '__tipsConfigVe
  */
 declare function defineTips(opts: TipsConfigInput): TipsConfig;
 
-export { ACADEMIC_PART_NAMES, BRANDON_PORTFOLIO_DEFAULT, BUILTIN_STYLES, BookConfigOptions, BookScaffoldIntegrationOptions, ChaptersRenderer, DEFAULT_GITHUB_BRANCH, type Freshness, type FreshnessStatus, KIND_LABEL, type ResolvedTheoremLabel, Style, THEOREM_KINDS, type TheoremKind, type TheoremLabelProps, type TipsConfig, type TipsConfigInput, UNKNOWN_PART_ORDINAL, type VolatilityLevel, academicChaptersRenderer, academicPartHeading, academicPartName, academicPartOrdinal, academicParts, academicStyle, assertEnumProp, bookScaffoldIntegration, buildGithubUrl, chapterSortKey, courseNotesStyle, defineBookConfig, defineMdxComponents, defineTips, fallbackChaptersRenderer, freshnessLabel, getFreshness, minimalStyle, originUrlFromGitConfig, parseRepoSlug, researchPortfolioStyle, resolveBookHref, resolveGithubRepo, theoremLabel, toolsChaptersRenderer, toolsStyle, volatilityLevels };
+export { ACADEMIC_PART_NAMES, BRANDON_PORTFOLIO_DEFAULT, BUILTIN_STYLES, BookConfigOptions, BookScaffoldIntegrationOptions, ChaptersRenderer, DEFAULT_GITHUB_BRANCH, type Freshness, type FreshnessStatus, Question, Style, type TipsConfig, type TipsConfigInput, UNKNOWN_PART_ORDINAL, type VolatilityLevel, academicChaptersRenderer, academicPartHeading, academicPartName, academicPartOrdinal, academicParts, academicStyle, assertEnumProp, assertKnownDomain, bookScaffoldIntegration, buildGithubUrl, chapterLabel, chapterSortKey, courseNotesStyle, defineBookConfig, defineMdxComponents, defineTips, deriveObjectiveMap, distinctChaptersSorted, fallbackChaptersRenderer, freshnessLabel, getFreshness, groupByChapter, groupByDomain, minimalStyle, originUrlFromGitConfig, parseRepoSlug, researchPortfolioStyle, resolveBookHref, resolveGithubRepo, sortQuestions, toolsChaptersRenderer, toolsStyle, volatilityLevels };