@brandon_m_behring/book-scaffold-astro 3.6.0 → 3.6.1

package/LATEX_TO_MDX_MAPPING.md

@@ -24,7 +24,7 @@ The scaffold ships **38 components**. Without this map, a `.tex → .mdx` conver
 | `\begin{tipbox}` | `TipBox` | `…/components/TipBox.astro` | `title?: string` | Pro tips / shortcuts |
 | `\begin{dynconnect}` | `DynConnect` | `…/components/DynConnect.astro` | `title?: string` | Cross-domain connection |
 | `\begin{theorem}` / `\begin{proposition}` / `\begin{lemma}` / `\begin{corollary}` / `\begin{definition}` / `\begin{remark}` / `\begin{proof}` | `Theorem` | `…/components/Theorem.astro` | `kind, n?, name?, id?` | amsthm family — single component dispatches via `kind` prop |
-| `\marginnote{}` | `MarginNote` | `…/components/MarginNote.astro` | — | Side commentary |
+| `\marginnote{}` / `\marginnotebox{}` / `\marginwarning{}` / `\margintip{}` | `MarginNote` | `…/components/MarginNote.astro` | `variant?: 'note' \| 'warning' \| 'tip'; label?: string` | `\marginnotebox` → `variant="note"` (blue), `\marginwarning` → `variant="warning"` (rose), `\margintip` → `variant="tip"` (green). `label` overrides the variant's default badge text. Body has a 25-word soft cap. |
 | `\sidenote{}` | `Sidenote` | `…/components/Sidenote.astro` | — | Auto-numbered marginalia (Tufte) |
 | `\includegraphics + \caption` | `Figure` | `…/components/Figure.astro` | `src, caption?, id?` | XRef-registered |
 | `\cite{}` / `\parencite{}` | `Citation` | `…/components/Citation.astro` | `src, as?` | Resolves `sources` collection |
@@ -41,6 +41,7 @@ Component subset table for tools-profile-specific UI (volatility dashboards, con
 | Construct | Component | Use case |
 |---|---|---|
 | Volatility badge | `Tag` | `volatility` enum chip in chapter meta |
+| Practice tag (`\official{}` / `\practitioner{}` / `\convergence{}`, also `\tagofficial{}` / `\tagpractitioner{}` / `\tagconvergence{}`) | `Tag` | `kind="official" \| "practitioner" \| "convergence"` — inline assertion of source authority. Both the bare and `\tag*` prefixed LaTeX forms map to the same component (see `package/components/Tag.astro`). |
 | Tool comparison | `ToolFilter` (island) | Interactive comparison gate |
 | Version selector | `VersionSelector` (island) | Switch between tool versions |
 | Convergence event | `Convergence` | "All tools converged here" timeline marker |

package/components/XRef.astro

@@ -6,10 +6,19 @@
  * (Phase 2.6). For each known id, the map provides:
  *   { href: "/chapters/week04#thm-w4-stability", display: "Theorem 4.2" }
  *
- * Phase 2.2 (now): labels.json ships empty. An unknown id renders an
- * inline "[?label]" placeholder so the build doesn't fail before we
- * have chapters with labels. Once Phase 2.6 lands, the validator
- * promotes "unknown label" from a warning to a build error.
+ * Runtime: renders `<a href>` for known ids; renders an inline `[?id]`
+ * placeholder for unknown ids so the Astro dev server stays running while
+ * chapters are being authored or labels are being added.
+ *
+ * CI: `book-scaffold validate` (Phase 2.6, shipped) catches unknown ids
+ * and **fails the build with a non-zero exit code** before unresolved
+ * placeholders can reach production. The placeholder is a dev-ergonomic
+ * affordance, not a soft-degradation path on the deploy critical line.
+ *
+ * Bootstrapping note: when porting a book chapter-by-chapter, early
+ * chapters that reference yet-to-be-ported targets need either plain-prose
+ * substitutes or a temporarily-commented `{/* <XRef …/> */}` until the
+ * target chapter (and its `id="…"` attributes) exists.
  *
  * Usage:
  *   By <XRef id="thm:w4:stability" />, the discretized eigenvalues …

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@brandon_m_behring/book-scaffold-astro",
   "description": "Astro 6 + MDX toolkit for long-form technical books. Profile-aware (academic / tools / minimal); ships Tufte typography, KaTeX, BibTeX citations, Pagefind, Cloudflare Workers deploy. See PACKAGE_DESIGN.md for the API contract.",
-  "version": "3.6.0",
+  "version": "3.6.1",
   "type": "module",
   "license": "MIT",
   "author": "Brandon Behring",

package/recipes/00-getting-started.md

@@ -2,19 +2,21 @@
 
 **Profile**: any (the recipe picks one based on your answer below).
 
-**TL;DR**: Pick a profile (`academic` / `tools` / `minimal`). Set `BOOK_PROFILE` in your shell or `.env`. Edit content under `src/content/chapters/`. `npm run dev` to preview.
+**TL;DR**: Pick a preset (`academic` / `tools` / `minimal` / `course-notes` / `research-portfolio`). Set `BOOK_PROFILE` in your shell or `.env`. Edit content under `src/content/chapters/`. `npm run dev` to preview.
 
-## 1. Choose a profile
+## 1. Choose a preset
 
-The scaffold ships three profiles. `BOOK_PROFILE` is read at startup by `astro.config.mjs` and `src/content.config.ts`.
+The scaffold ships **five presets** as of v3.5.0. `BOOK_PROFILE` (or its canonical alias `BOOK_PRESET`, v3.4.0+) is read at startup by `astro.config.mjs` and `src/content.config.ts`.
 
-| Profile | Use when | Frontmatter schema | Default callouts | Math | Bibliography |
+| Preset | Use when | Frontmatter schema | Default callouts | Math | Bibliography |
 |---|---|---|---|---|---|
-| `academic` | Textbook, research report, lecture notes | `week`, `part`(enum), `status`(7-state) | NoteBox, Theorem family, ExampleBox … | KaTeX with 36 macros | BibTeX → `src/data/references.json` |
+| `academic` | Textbook, research report, lecture notes | `week`, `part`(enum), `status`(7-state) | NoteBox, Theorem family, ExampleBox … | KaTeX with 36 macros (consumer can extend via `katexMacros`, v3.6.0+) | BibTeX → `src/data/references.json` |
 | `tools` | Comparative practitioner book (multiple tools tracked) | `chapter`, `part`(numeric), `volatility`, `tools_compared`, `sources` | SkillBox, KeyIdea, Convergence, Divergence … | off | YAML manifest at `sources/manifest.yaml` |
-| `minimal` | Single-author manifesto, essays, mixed-form work | falls back to `tools` schema (pick `tools` and ignore the fields you don't use) | tools-family | off | manual references page |
+| `minimal` | Single-author manifesto, essays, mixed-form work | falls back to `tools` schema | tools-family | off | manual references page |
+| `course-notes` (v3.3.0, #4) | Course-derived study notes (DLAI, Coursera, Manning) | `chapter`+`part`(numeric), `course`, `instructor`, `learning_outcomes`, freeform `tags` | tools-family | off | freeform `sources` array |
+| `research-portfolio` (v3.5.0, #6) | Research portfolio with mixed prose + experiments | optional `week` OR `chapter`, `status`, `freshness`(evidence-type enum), T1–T4 inline sources | both families | KaTeX on by default | structured inline `sources` (no separate collection) |
 
-Most academic books pick `academic`; most "Agentic Coding" style books pick `tools`. If unsure: pick `minimal` and switch later — schemas are forgiving as long as required fields are set.
+If unsure: pick `minimal` and switch later — schemas are forgiving as long as required fields are set.
 
 ## 2. Set the profile
 

package/recipes/12-where-to-file-issues.md

@@ -40,7 +40,10 @@ Each batch of cross-consumer issues drives a minor toolkit release:
 - **v3.0–v3.2** absorbed Phase B/C/D feedback from `post_transformers` + `book-template-astro`.
 - **v3.3.0** closed 5 issues surfaced from the DLAI knowledge-graphs-rag pilot (course-notes profile + defineMdxComponents + per-route override + LaTeX migration doc).
 - **v3.4.0** closed 8 more (preset vocabulary + propagation + frontmatter helper + validate root fix + CI hygiene + docs).
-- **v3.5.0** (future) is expected to add the `research-portfolio` preset per issue #6 once cross-repo coordination with `prompt-injection-portfolio` is ready.
+- **v3.5.0** added the `research-portfolio` preset (#6) driven by cross-repo coordination with [`prompt-injection-portfolio`](https://github.com/brandon-behring/prompt-injection-portfolio).
+- **v3.5.2 / v3.5.3 / v3.6.0** (the [`double-ml-time-series`](https://github.com/brandon-behring/double-ml-time-series) pilot batch) closed three more issues surfaced within 24 hours of the first non-SSM academic book hitting the scaffold: `/chapters` schema-aware for academic profile (#24), `validate` honors `.env BOOK_PROFILE` (#20), and `katexMacros` extension point for non-SSM math notation (#22). Same release cycle introduced OIDC trusted publishing via [`.github/workflows/publish.yml`](../../.github/workflows/publish.yml).
+
+The next consumer-pilot batch lands as v3.7+. File issues against [`brandon-behring/book-scaffold-astro`](https://github.com/brandon-behring/book-scaffold-astro/issues) tagged with `consumer:<your-book-name>` so the batching shows up in the issue tracker.
 
 Profile-by-profile growth is the explicit strategy: the toolkit gets a new profile when a real consumer needs one, not before.
 

package/recipes/14-port-latex-book.md

@@ -0,0 +1,250 @@
+# Recipe 14 — Port a LaTeX book into the scaffold
+
+**Profile**: typically `academic` (textbooks, research manuscripts). Adapt for `research-portfolio` if your LaTeX book also tracks freshness/volatility.
+
+**TL;DR**: Bootstrap a `web/` subdirectory inside the LaTeX repo. Share the canonical `bibliography.bib` via `BOOK_BIB_PATH`. Smoke-test the bib pipeline *before* writing chapter content. Pick one chapter as the pilot; port it manually (do not script the conversion) so the friction surfaces. File each gap upstream the moment it surfaces — with a real receipt — and consume the fix via a `file:` dependency until it publishes. Defer chapters 2..N until the pilot ships.
+
+See [`LATEX_TO_MDX_MAPPING.md`](../LATEX_TO_MDX_MAPPING.md) for the component-mapping reference table (which scaffold component replaces which LaTeX environment).
+
+This recipe is the operational *process* that goes around that table.
+
+## When to use this recipe
+
+Use it when you already have a working LaTeX manuscript (`main.tex` + `chapters/*.tex` + `bibliography.bib`) and want a web companion that:
+
+- Builds in parallel with the existing PDF build (you keep LaTeX canonical during the migration window).
+- Reuses the same `bibliography.bib` so citations don't drift.
+- Surfaces the friction points specific to your book so they become upstream improvements to the scaffold, not consumer-side workarounds that rot.
+
+If you are *starting* a new book from scratch, prefer [Recipe 00](00-getting-started.md) — no LaTeX baggage to migrate.
+
+## 1. Pre-flight (before any code)
+
+These two steps are deliberately *not* code changes. They make the work inheritable across sessions and visible to collaborators.
+
+### 1a. File a tracking issue in your LaTeX repo
+
+```bash
+gh issue create \
+  --repo <you>/<your-book> \
+  --label tracked --label P2 --label feature \
+  --title "pilot: port <your-book> to book-scaffold-astro" \
+  --body "Link to plan, acceptance bar (functional parity), upstream-first strategy"
+```
+
+The issue gives every commit a number to link back to, and shows up on cross-repo project boards.
+
+### 1b. Record the strategic context
+
+If you have a memory store (Claude `MEMORY.md`, Obsidian, etc.), note:
+
+- The scaffold version you targeted (e.g. `^3.6.0`).
+- The fact that you intend to file upstream issues as friction surfaces, *not* work around consumer-side.
+- The pilot's acceptance bar — typically **functional parity** for one chapter: every LaTeX construct has a working MDX equivalent, visual styling may differ.
+
+A future session (yours, or another author taking the same approach) inherits the strategy without re-discovering it.
+
+## 2. Bootstrap a `web/` subdirectory
+
+From inside your LaTeX repo root:
+
+```bash
+npx @brandon_m_behring/create-book web --profile=academic
+cd web && npm install
+```
+
+You will get 11 scaffolded files in `web/`. Edit these four immediately:
+
+**`web/package.json`** — set the package name, and override `build:bib` so it consumes the canonical bibliography at the repo root:
+
+```diff
+- "name": "web",
++ "name": "my-book-web",
+
+- "build:bib": "book-scaffold build-bib",
++ "build:bib": "BOOK_BIB_PATH=../bibliography.bib book-scaffold build-bib",
+```
+
+**`web/astro.config.mjs`** — set the deploy URL and make the profile explicit (the env-driven fallback fails in Cloudflare's build container because `.env` is gitignored):
+
+```js
+export default await defineBookConfig({
+  site: 'https://my-book.<your-cloudflare-account>.workers.dev',
+  profile: 'academic',
+});
+```
+
+**`web/src/content.config.ts`** — same reasoning: explicit `profile: 'academic'`.
+
+**`web/wrangler.toml`** — Cloudflare project name.
+
+Delete the scaffolded `web/bibliography.bib` placeholder (the `BOOK_BIB_PATH` override makes it dead weight).
+
+## 3. Bib smoke test (before chapter content)
+
+**Do not write a single line of MDX until the bibliography parses cleanly.** Bib bugs cascade into chapter content and are then conflated with "MDX problems."
+
+```bash
+cd web && npm run build:bib
+```
+
+You should see, e.g., `build-bib: 34 entries -> src/data/references.json`. Sanity-check the output:
+
+```bash
+# Total entry count matches the raw .bib
+jq 'keys | length' src/data/references.json
+# Should equal: grep -c '^@' ../bibliography.bib
+
+# Spot-check 5 entries: surname + year + title + container
+jq '.["chernozhukov2018double"] | {author, "issued.date-parts": ."issued"."date-parts", title, "container-title"}' \
+  src/data/references.json
+```
+
+Watch for biblatex-only fields silently dropped (`date`, `journaltitle`, `eventtitle`), `[object Object]` artifacts, or UTF-8 mishandling (umlauts, em-dashes). If any entries mistranslate, that's your first organic upstream issue. File it with the failing entry as evidence, *then* keep going.
+
+## 4. The inline-upstream-PR loop
+
+The pilot's core discipline. Whenever the port surfaces real friction (a missing macro, a schema mismatch, a component gap, a crashing build):
+
+1. **Stop the port.** Capture the receipt: the LaTeX snippet that's hard to translate + what the scaffold currently offers + the proposed API.
+2. **File the issue** at `brandon-behring/book-scaffold-astro` with labels `consumer:<your-book>` + `kind:enhancement` / `kind:api-friction` / `kind:bug` / `kind:doc-drift`. Create labels if they don't exist.
+3. **Implement the upstream PR.** Branch from `v3.0` (or the current dev branch), make the fix, run the scaffold's tests (`cd package && node --test tests/*.test.mjs`), bump the version, document in `CHANGELOG.md`. Add a regression test where one is missing.
+4. **Consume the fix via a `file:` dependency** so the pilot is unblocked before the registry version exists:
+
+   ```json
+   "dependencies": {
+     "@brandon_m_behring/book-scaffold-astro": "file:../../book-scaffold-astro/package"
+   }
+   ```
+
+   Run `npm install` again. The local scaffold's built `dist/` is what the consumer now resolves.
+5. **Log it** in a running `web/UPSTREAM_ISSUES.md` — issue link, PR link, version bumped, receipt. Future sessions reading the log understand why the consumer carries any leftover workaround.
+6. **Resume the port** using the now-fixed upstream API. Delete consumer-side workarounds that the upstream PR superseded — those deletions are part of the proof.
+
+When the PR merges and the registry version publishes, swap the `file:` dependency back to `^<version>` and rerun `npm install`.
+
+> **Triage rule.** If the upstream fix is small (one-line, one-file) and has a clear API, do steps 1–6 inline before the next chapter section. If it's large (cross-cutting, requires API design), file the issue with the receipt, fall back to a consumer-side workaround for the pilot, and mark the PR as Phase-2 work in `UPSTREAM_ISSUES.md`. The slow path is the point — the scaffold improves with every consumer book — but not at the cost of pilot momentum on a single bug.
+
+## 5. Wire the build pipeline
+
+Per [Recipe 09](09-validation.md), the scaffold ships `book-scaffold validate` to catch authoring errors (bad cite keys, dangling XRef ids, missing figure files). Wire it into `prebuild`:
+
+```json
+"scripts": {
+  "predev": "npm run build:bib && npm run build:labels --if-present",
+  "prebuild": "npm run build:bib && npm run build:labels --if-present && npm run validate --if-present",
+  "build:bib": "BOOK_BIB_PATH=../bibliography.bib book-scaffold build-bib",
+  "build:labels": "book-scaffold build-labels",
+  "validate": "book-scaffold validate",
+  "dev": "astro dev",
+  "build": "astro build && pagefind --site dist"
+}
+```
+
+Use `<XRef id="..." />` for cross-references from the first chapter onward — do not fall back to plain markdown anchors with the intent to "retrofit later." The retrofit is more expensive than wiring labels from the start.
+
+## 6. Consumer-side KaTeX macros
+
+If your LaTeX preamble defines `\newcommand{\Var}{\mathrm{Var}}` style shortcuts, list the *actually used* ones (not the full preamble!) in `astro.config.mjs`:
+
+```js
+katexMacros: {
+  '\\Var': '\\mathrm{Var}',
+  '\\Cov': '\\mathrm{Cov}',
+  // Add macros as the port surfaces real uses. Do not preemptively
+  // import every \newcommand from the LaTeX preamble.
+},
+```
+
+`katexMacros` is shallow-merged on top of `ssmMacros`. Consumer wins on key collision. The scaffold runs KaTeX with `strict: 'error'`, so any undefined macro fails the build — a forcing function that keeps the macro set honest.
+
+If you discover a macro pattern that's clearly cross-book (most causal-inference books need `\ate`, `\att`, `\cate`, `\propensity`; most RL books need `\bellman`, `\argmin`), that is an upstream-issue-worthy signal. File it and shift the consumer-side bridge to an upstream preset.
+
+## 7. Pilot port
+
+Pick one chapter — ideally Chapter 1, since later chapters depend on its conventions. Port manually.
+
+**Manual is the point.** A scripted conversion (pandoc, custom AST walk) misses the friction. The friction is the deliverable.
+
+For each LaTeX environment, consult [`LATEX_TO_MDX_MAPPING.md`](../LATEX_TO_MDX_MAPPING.md) and translate. A few hot-spots that consistently produce upstream issues:
+
+- **Theorem numbering**. The scaffold's `<Theorem kind="theorem" n="1.3" name="...">` accepts manual `n=` until a counter API lands. Pass the number explicitly; do not assume auto-numbering. (This is open work — see [Recipe 09](09-validation.md) for current status.)
+- **Margin notes**. Map `\marginnote[Title]{body}` → `<MarginNote title="Title">body</MarginNote>` and `\sidenote{...}` → `<Sidenote>...</Sidenote>`. Lean on `<MarginNote>` for Tufte sidebars; `<Sidenote>` is auto-numbered footnote-style.
+- **Citations**. Map `\cite{key}` → `<Cite key="key" />`. The `<Cite>` component validates `key` against the parsed bibliography at build time — broken bibkeys fail `book-scaffold validate`.
+- **Proof blocks**. `\begin{proof}…\end{proof}` → `<Theorem kind="proof">…</Theorem>`. Same component, different `kind`.
+
+Frontmatter status: every chapter that already has prose + working code gets `status: implemented`. Do not invent finer-grained migration states (`status: porting` etc.) — if a real distinction emerges, file the upstream issue.
+
+## 8. Verify the build
+
+```bash
+cd web
+npm run build:bib && npm run build:labels && npx book-scaffold validate && npm run build
+```
+
+Acceptance bar (recommended): **functional parity**.
+
+- Every LaTeX construct in the pilot chapter has a working MDX equivalent.
+- KaTeX strict mode passes — no undefined macros.
+- Validate passes — no unknown cite keys, no dangling XRef ids, no missing figures.
+- The Astro build produces the auto-injected routes (`/print`, `/references`, `/search`) and your chapter renders inside `/print`.
+
+Visual styling may differ from the LaTeX PDF — the scaffold owns visual design; the pilot owns content fidelity.
+
+## 9. Known pitfalls (from past pilots)
+
+These are real friction discovered by consumer pilots. Some are fixed, some open.
+
+### Academic profile and `routes.chapters`
+
+The `defineBookConfig` option `routes: { chapters: true }` *appears* to opt an academic book into per-chapter URLs but currently crashes the build — the shipped `pages/chapters.astro` is hardcoded to the tools schema (`volatility`, `tools_compared`, `last_verified`, `chapter`). Track [issue #24](https://github.com/brandon-behring/book-scaffold-astro/issues/24). For now, the academic profile's chapter access point is `/print` (which aggregates all chapters into one Paged.js-friendly page).
+
+### Scaffolded demo content is occasionally drifty
+
+The `week01-hello-world.mdx` demo created by `create-book` ships with a placeholder cite (`example-key2024`) that's not in the placeholder bibliography. It also uses `<Theorem type="theorem">` (the deprecated prop name) instead of `<Theorem kind="theorem">`. Delete or rewrite the demo before running `validate` for the first time. If the drift recurs across versions, file a `kind:doc-drift` issue.
+
+### `BOOK_PROFILE` and `.env`
+
+`book-scaffold validate` reads `BOOK_PROFILE` from `.env` per [Issue #20](https://github.com/brandon-behring/book-scaffold-astro/issues/20), fixed in 3.5.2. If you see `profile=minimal` reported despite an academic `.env`, you're on an older scaffold version — upgrade or set the env var explicitly in your npm scripts.
+
+### Bibkeys flagged as secrets
+
+If your repo has a `gitleaks` pre-commit hook, BibTeX cite keys like `chernozhukov2018double` (high-entropy author-year strings) will trip the default `generic-api-key` rule. Add a repo-level `.gitleaks.toml`:
+
+```toml
+title = "my-book"
+
+[extend]
+useDefault = true
+
+[allowlist]
+description = "Human-authored chapter MDX and the BibTeX bibliography."
+paths = [
+  '''web/src/content/.*\.mdx$''',
+  '''^bibliography\.bib$''',
+]
+```
+
+Use the singular `[allowlist]` form (not the newer plural `[[allowlists]]`) — older gitleaks releases installed by `pre-commit` don't honor the plural syntax.
+
+### `npm install` after `file:` dependency
+
+When you switch `web/package.json` to `"@brandon_m_behring/book-scaffold-astro": "file:../../book-scaffold-astro/package"`, `npm install` resolves the local path. The scaffold's `dist/` must be present (run `npm run build` inside the scaffold once). When you later switch back to a registry version, run `npm install` again to drop the file resolution.
+
+## 10. Phase 2: chapters 2..N
+
+Only after the pilot ships:
+
+- Has the manual port pace matched LaTeX authoring? If yes, green-light the full migration. If not, evaluate pandoc-assisted drafts as a 30% time saver on bulk prose; hand-edit minted blocks / margin notes / custom commands (pandoc mangles all three).
+- Did upstream-first investment produce a net gain? It should: each PR makes the *next* chapter port cheaper.
+- Are there scaffold gaps that still warrant inline PRs, or is the remaining work entirely consumer-side?
+- Schema upgrades that were deferred during the pilot (e.g. parameterized `parts` per-book) ship now if they unblock chapter 2's frontmatter.
+
+## See also
+
+- [Recipe 00 — Getting started](00-getting-started.md) — for new books, not migrations.
+- [Recipe 01 — Add math](01-add-math.md) — KaTeX details + the `katexMacros` consumer option.
+- [Recipe 02 — Bibliography pipeline](02-bibliography-pipeline.md) — `BOOK_BIB_PATH`, `build-bib`, `<Cite>`.
+- [Recipe 09 — Validation](09-validation.md) — `book-scaffold validate` and its checks.
+- [Recipe 12 — Where to file issues](12-where-to-file-issues.md) — consumer-pilot issue template.
+- [`LATEX_TO_MDX_MAPPING.md`](../LATEX_TO_MDX_MAPPING.md) — component mapping reference card.

package/recipes/README.md

@@ -17,6 +17,9 @@ Terse pointers into canonical code for the most common book-authoring workflows.
 | 08 | [Decisions ledger](08-decisions-ledger.md) | any | 15 design decisions explained |
 | 09 | [Pre-flight validation](09-validation.md) | any | `validate.mjs` catches bibkey/XRef/Figure typos |
 | 10 | [Custom domain](10-custom-domain.md) | any | Cloudflare dashboard, apex vs subdomain |
+| 12 | [Where to file issues](12-where-to-file-issues.md) | any | Consumer-pilot issue template, label conventions |
+| 13 | [Research-portfolio getting started](13-research-portfolio-getting-started.md) | research-portfolio | When to use the preset, frontmatter shape, the 4 new components |
+| 14 | [Port a LaTeX book](14-port-latex-book.md) | typically academic | Operational playbook for porting an existing LaTeX manuscript — bib sharing, inline-upstream-PR loop, common pitfalls |
 
 ## How to read recipes