@taloswork/ose-shared 0.1.2 → 0.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taloswork/ose-shared",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "Talos cross-OSE shared library — skills + MCP servers auto-loaded into every OSE (P93 2026-07-27).",
   "type": "module",
   "files": [
@@ -10,6 +10,6 @@
   "publishConfig": {
     "access": "public"
   },
-  "_talosPublishHash": "sha256-T36gm46DynkzOQOg4I0N8sK_-SP1h0kOm1929zOwv9U",
-  "_talosPublishedAt": "2026-09-02T17:54:52.828Z"
+  "_talosPublishHash": "sha256-7or_mcdSHbKlZLnkDnnjf-71hdL7A895HrWVqUGALOo",
+  "_talosPublishedAt": "2026-09-03T17:22:12.823Z"
 }

package/skills/document/SKILL.md

@@ -40,56 +40,59 @@ script only when:
   document files via these scripts — never hand-write a python / ReportLab /
   LibreOffice script for document output.
   **Any deck/presentation(路演/汇报/评审/宣讲/pitch/roadshow/介绍 PPT)**:
-  **CLARIFY FIRST — HARD GATE (applies to EVERY deck).** Before authoring
-  anything, UNLESS the user already gave them or said "你决定/you decide", you
-  MUST ask — in **ONE AskUserQuestion call with these FOUR questions** — and wait
-  for answers (the tool allows up to 4 questions per call — use all four; do NOT
-  split into a second call and do NOT drop the style question):
-  **(1) content source** (提供材料 / 联网调研 / 自由创作); **(2) scenario** (pitch /
-  内审 / 销售 / 讲座 / 发布会 / 培训 / 大会 — sets tone, density, required sections);
-  **(3) style — pick ONE skin.** By DEFAULT show **ALL 13 skins as image-card options**
-  (anthropic · apple · black-gold · branding · cinereel · cool · hand-drawn · ivory-gold ·
-  magazine-ink · mckinsey · mono · olive-gold · swiss-grid) — **never a 3–5 shortlist.**
-  Image-card picks are capped at **16**, so the 4-option TEXT cap that governs Q2 does NOT
-  apply here; emit **one card per skin, all 13, every time** (+ the template card below =
-  14 cards). If you catch yourself sending fewer than 13 skin cards, you mis-applied the
-  text cap — send all 13.
-  One option per skin `{ label: skin 名, description: <the skin's **picker one-liner**
-  from styles/README.md, copied VERBATIM — one short line, must NOT wrap, no 首选/风/
-  keynote padding>, imagePath: <absolute path to styles/_samples/<skin>.webp under the
-  skill dir> }`. **The `适用场景` column is for MATCHING a skin to the scenario ONLY —
-  never copy it (or synthesize from it) into the shown `description`; the description is
-  the fixed picker one-liner, nothing else.** Those sample images are
-  **PRE-RENDERED** WebP (a fixed cover + content page stacked per skin, all the same size)
-  and shipped with the skill — pass them straight through as `imagePath`; do NOT
-  render anything at question time. (The picker UI lays the cards out itself; the skill
-  only supplies the options + images.) `styles/README.md` lists each skin's 适用场景 +
-  light/dark; order the cards best-fit-for-scenario first, but show them all.
-  **ALSO add one more option AFTER the skins** so the user can bring their OWN template:
-  `{ label: "使用我的模板文件", description: "复用现成 PPT 的版式/风格", filePick: "file" }`
-  (no imagePath — it renders as a folder card). Clicking it opens a native file picker
-  and the chosen **path** becomes the Q3 answer; when the answer is a path (not a skin
-  name), route to the reuse path — `pptx-tokenize`/`pptx-theme` (rewrite.md B2), NOT one
-  of the skins.
-  This custom-template card is required both for the initial four-question gate and
-  whenever the user later asks to reselect/change the PPT style; never omit it from
-  a skin gallery.
-  **(4) slide count.**
-  **Keep the call LEAN — it streams in full before the panel becomes interactive,
-  so every extra token is dead wait.** Questions (1)(2)(4) pass options as **bare
-  label strings** (e.g. `["提供材料","联网调研","自由创作"]`) — NO per-option
-  `description`/`detail` objects; each question stem is ONE short sentence. The ONLY
-  descriptions in the whole call are Q3's fixed skin one-liners. Skip any chat
-  preamble before the tool (or keep it to a single short line) — the questions speak
-  for themselves.
-  Every question carries an implicit "其他/自定义" free-text escape (the panel adds
-  it). If they respond with a question/correction instead of a pick, answer it,
-  then re-ask. Do NOT drop the style question or waive the gate by judging the deck
-  "small/quick" — only an explicit user spec or "你决定" skips it.
-
-  **Pick the skin** (in this order): a remembered deck-skin preference → user named
-  a style → match `styles/README.md` by 适用场景 → **otherwise default to `cool`**
-  (酷炫深色). Use `mckinsey` / `mono` when the user asks clean/formal/light. Never
+  **CLARIFY FIRST — HARD GATE (applies to EVERY deck).** Before authoring, collect
+  three brief fields: **(1) content source** (提供材料 / 联网调研 / 自由创作);
+  **(2) scenario** (pitch / 内审 / 销售 / 讲座 / 发布会 / 培训 / 大会 — sets tone,
+  density, required sections); **(3) slide count.** Ask only for fields the user did
+  not already supply, in **ONE AskUserQuestion call with at most THREE questions**, and
+  wait for the answers. If all three are already known, do not ask them again.
+
+  **STYLE PICKER — ONE RESULT PER IMAGE, SCENARIO-RANKED.** After the scenario is
+  known, read the skill directory's **current `catalog.json` from disk immediately
+  before building the picker**. Never reuse a catalog listing from earlier conversation
+  context and never infer pack availability by scanning `packs/`. If the current catalog
+  cannot be read or parsed, stop and report that exact error instead of presenting stale
+  options.
+
+  Unless the user already named an entry id/name, supplied a template file, or explicitly
+  said **"无需展示模板，直接替我选定风格"**, send one single-question image-card picker:
+
+  - Rank **entries**, not groups, against the confirmed scenario and the user's requested
+    tone. Show at most 8 recommended entries. A scenario-matching `kind === "pack"` ranks
+    before matching skins; include at least one matching pack whenever one exists.
+  - Every image card maps to exactly one final entry and uses
+    `{ label: entry.kind === "pack" ? "PACK · " + entry.name_cn : entry.name_cn,
+    description: entry.oneliner, imagePath: <skill目录下entry.sample的绝对路径> }`.
+    Copy `entry.oneliner` verbatim. Never use `group.sample` in this default picker.
+  - Append `{ label: "查看全部风格", description: "一次查看全部模板" }`, then
+    `{ label: "使用我的模板文件", description: "复用现成 PPT 的版式/风格",
+    filePick: "file" }` as the final option.
+
+  **"按场景推荐/你推荐" means rank the cards and still ask.** It does NOT waive the
+  picker. Only the explicit no-picker wording above authorizes automatic selection.
+  Do not waive this gate because the deck is small or quick.
+
+  If the user chooses **查看全部风格**, immediately show **every current
+  `catalog.entries` item in one single-question image-card picker** using the same label,
+  description, and imagePath rule above. Preserve catalog order, keep `PACK ·` visible,
+  and append the custom-template file card. Do not ask for a group, paginate, or return to
+  any category/second-level picker; the browse-all action must expose final selectable
+  templates directly.
+
+  Samples are pre-rendered WebP files shipped with the skill: pass their absolute paths
+  directly and do not render anything during the question. The selected `entry.id` is the
+  `--style` value: `html2pptx deck.html out.pptx --style <id>`. Skin and pack use the same
+  render command; `catalog.json` resolves their different asset directories.
+
+  **Keep both calls LEAN.** The content/scenario/count questions use bare label strings,
+  no per-option descriptions; every question stem is one short sentence. Skip chat
+  preambles or keep one short line. Every question has the panel's implicit custom-text
+  escape. If the user responds with a correction or question, handle it and re-ask.
+
+  **Automatic choice, only when explicitly authorized:** rank by a remembered preference,
+  an exact user-named style, scenario match, a matching pack before a matching skin, then
+  `entry.mode` when the user asked for clean/formal/light/dark. Never hardcode a family id:
+  `catalog.json` is the only roster; `styles/README.md` is explanatory only. Never render
   unstyled. After the user confirms, save the preference to memory.
 
   **Custom style (user picked 其他/自定义 on Q3)** — clarify which route, **prefer B
@@ -101,9 +104,9 @@ script only when:
     palette → fill the class contract; see deck-design "build a skin from a reference
     image"). *(A deck given here is for its STYLE — distinct from a deck given as
     content, which is text-only; see content-pipeline Q1.)*
-  - **A — map to the nearest of the 13 skins** (they only described a vibe): pick the
+  - **A — map to the nearest of catalog 里的族** (they only described a vibe): pick the
     closest, render its sample, confirm.
-  - **C — tweak an existing skin** ("cool 但换绿色"): clone it, swap accent/palette or
+  - **C — tweak an existing skin** ("刚才那个族但换绿色"): clone it, swap accent/palette or
     flip light↔dark.
   Then render a cover+content sample of the result and confirm (same image-card step as
   a normal pick) before authoring; save the resulting preference to memory.
@@ -218,7 +221,7 @@ Fidelity-decision self-correct, but pointed at your OWN output:
 - `bin/xlsx-recalc.cjs <in.xlsx> <out.xlsx>` — re-evaluate all formulas (HyperFormula) and cache the results, keeping the formulas. Use when a spreadsheet's formula cells show stale/blank values.
 - `bin/doc-run.cjs <script.js> [args…]` — run a custom Node script with the engine's libraries bundled in (`require("pptxgenjs"|"docx"|"xlsx"|"pdf-lib"|"jszip"|"pizzip"|"hyperformula")` guaranteed on any machine; `--list` prints the registry). The long-tail escape hatch when no verb fits — see rewrite.md "Custom scripts"; ALWAYS doc-validate the output.
 - `bin/html2pptx.cjs <deck.html|snapshot.layout.json> <out.pptx> [--style <skin>] [--backdrop <variant>] [--theme <theme.json>] [--editable] [--rasterize]` — **THE deck path**: write slide HTML (`<section class="slide" data-layout="…">` on a 1280×720 canvas), Chromium lays it out → NATIVE editable pptx. **Compose from `layouts/*.tpl` (structure) + `--style <skin>` (paint)** — the preferred structure/skin split (`styles/README.md`); `--style` injects the skin's CSS, fills each `.slide-backdrop`, colors `data-chart` from the skin. `--backdrop <variant>` picks a signature backdrop. **DEFAULT = hybrid**: each slide's visuals bake into a full-fidelity raster backdrop with native EDITABLE text on top; auto-falls back to plain native if backdrop capture is unavailable. `--editable` = plain native only (effects flatten). `--rasterize` = full image slides (ZERO editability — tell the user). Advisory warnings on hardcoded brand colors + repeated layouts (P3). Runs in the app's Chromium OR bundled headless Chromium (Playwright) — works off-app (CI/cloud); layout JSON works anywhere. **Tailwind + `size="1".."7"` scale available** (vendored offline). See deck-design.md + layouts/README.md. `[--theme <theme.json>]` is the legacy path (superseded by `--style`). **Don't confuse the two `--style` flags:** html2pptx's `--style` = the whole deck **skin** (backgrounds, cards, the lot); doc-gen's `--style` on **docx/pdf** is a different, narrower flag that borrows only the skin's ONE accent color onto black-text paper (a document, not a deck).
-- `bin/deck-build.cjs <spec.json> <deck.html>` — **THE FAST deck path** for catalog slides: emit a COMPACT spec (per slide a `layout` id + its content `slots` `{…}`, plus `rows` for list/figure layouts and an optional `chart`) and this reads each `layouts/<id>.tpl`, fills it, and assembles `deck.html` — so you stream ~content only, not ~40KB of boilerplate HTML (much faster). Then `html2pptx deck.html out.pptx --style <spec.style>` as usual. **What each layout takes is in `layouts/slots.json`** (`slots` + `rows` per layout; `"chart":"derived"` means the layout BUILDS its chart from its rows — pass rows, never `chart`). Un-filled slots fall back to the template default, but a spec the catalog can't satisfy (unknown layout/slot/field, a `rows` block with no data, a figure row missing its numbers) **exits 1 and writes nothing** — fix the spec rather than shipping demo data. For a **bespoke** slide the catalog can't express, hand-author that ONE `<section>` and append it to deck.html (deck-build handles the catalog slides). spec: `{ "style":"cool", "slides":[ {"layout":"cover","slots":{"title":"…"}}, {"layout":"chart-kpi","slots":{…},"chart":{…}}, {"layout":"gantt","slots":{…},"rows":{"cols":[{"label":"Q1"}],"tasks":[{"name":"调研","from":1,"to":2}]}} ] }`.
+- `bin/deck-build.cjs <spec.json> <deck.html>` — **THE FAST deck path** for catalog slides: emit a COMPACT spec (per slide a `layout` id + its content `slots` `{…}`, plus `rows` for list/figure layouts and an optional `chart`) and this reads each `layouts/<id>.tpl`, fills it, and assembles `deck.html` — so you stream ~content only, not ~40KB of boilerplate HTML (much faster). Then `html2pptx deck.html out.pptx --style <spec.style>` as usual. **What each layout takes is in `layouts/slots.json`** (`slots` + `rows` per layout; `"chart":"derived"` means the layout BUILDS its chart from its rows — pass rows, never `chart`). Un-filled slots fall back to the template default, but a spec the catalog can't satisfy (unknown layout/slot/field, a `rows` block with no data, a figure row missing its numbers) **exits 1 and writes nothing** — fix the spec rather than shipping demo data. For a **bespoke** slide the catalog can't express, hand-author that ONE `<section>` and append it to deck.html (deck-build handles the catalog slides). spec: `{ "style":"<catalog entry id>", "slides":[ {"layout":"cover","slots":{"title":"…"}}, {"layout":"chart-kpi","slots":{…},"chart":{…}}, {"layout":"gantt","slots":{…},"rows":{"cols":[{"label":"Q1"}],"tasks":[{"name":"调研","from":1,"to":2}]}} ] }`.
 
 All scripts are Node and print a machine-readable result plus a human note. On a
 missing dependency or unreadable file they exit non-zero with a clear message —

package/skills/document/assets/fonts/fonts.json

@@ -0,0 +1,316 @@
+{
+  "_comment": "Single source of truth for the skill's bundled font set. Consumed by bin-src/html2pptx.mjs (base64 @font-face injection at render) and by scripts/deck-skin-samples.mjs + scripts/deck-fidelity.mjs (served from disk via page.route). Add a face HERE, drop the .woff2 beside it, and every renderer picks it up — never inline a base64 @font-face into a skin.css. `substitutesInvisibly: true` marks a neutral grotesque: it is NOT on any OS, so the native pptx text layer swaps it for Helvetica/Arial, but the swap differs by a hair and no reader would name it — such a face may lead a skin unbaked. A serif or display face is the opposite call: bake every rule that uses it, or the audience sees a different font (deck-layouts.test.ts enforces both directions, and gen-skin refuses a family that gets it wrong).",
+  "cjkUnicodeRange": "U+2E80-2EFF,U+3000-303F,U+3040-30FF,U+3200-4DBF,U+4E00-9FFF,U+F900-FAFF,U+FE30-FE4F,U+FF00-FFEF",
+  "cjk": [
+    {
+      "file": "NotoSansSC.woff2",
+      "families": [
+        "PingFang SC",
+        "Hiragino Sans GB",
+        "Microsoft YaHei",
+        "Noto Sans SC",
+        "Noto Sans CJK SC",
+        "Source Han Sans SC",
+        "WenQuanYi Zen Hei"
+      ]
+    },
+    {
+      "file": "NotoSerifSC.woff2",
+      "families": [
+        "Songti SC",
+        "STSong",
+        "SimSun",
+        "Noto Serif SC",
+        "Noto Serif CJK SC",
+        "Source Han Serif SC"
+      ]
+    }
+  ],
+  "latin": [
+    {
+      "file": "Anton-Regular.woff2",
+      "families": [
+        "Anton"
+      ],
+      "note": "Ultra-condensed display face. cinereel + ivory-gold use it for --font-head and BAKE their titles, which is why it survives into the pptx. Also staged into the xhs skill by scripts/build-xhs-skills.mjs.",
+      "license": "SIL OFL 1.1 (Google Fonts)"
+    },
+    {
+      "file": "Inter-Regular.woff2",
+      "families": [
+        "Inter"
+      ],
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "Neutral UI grotesque. swiss-grid asks for it as its whole type system, ivory-gold as --font-body. Neither OS ships it, so before this entry even the backdrop/preview render fell back to Helvetica/Arial. Their native text still does — see _scope.",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "GochiHand-Regular.woff2",
+      "families": [
+        "Gochi Hand"
+      ],
+      "license": "Apache License 2.0 (Google Fonts)",
+      "note": "Handwriting face, hand-drawn's signature marker-pen heading. Latin-only, so a CJK deck barely shows it; and hand-drawn does NOT bake its titles, so the native text layer still resolves the stack's `cursive` keyword (LibreOffice → Snell Roundhand). Bundling fixes the backdrop/preview render only — see _scope."
+    },
+    {
+      "file": "BigShouldersDisplay-Bold.woff2",
+      "families": [
+        "Big Shoulders Display"
+      ],
+      "weight": "700",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "Ultra-condensed display face, narrower and more open-countered than Anton. cinereel's --font-head; picked to match the slidescarnival music-video template this skin is modelled on. Every rule that uses it is baked."
+    },
+    {
+      "file": "Jost-Regular.woff2",
+      "families": [
+        "Jost"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "Geometric sans, cinereel's --font-body. Body copy is NOT baked (it must stay editable/searchable), so the native pptx text layer still substitutes — this face governs the backdrop and previews. See deck-design.md § Fonts.",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Jost-SemiBold.woff2",
+      "families": [
+        "Jost"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "The 600 companion, so bold body runs (.toc-title etc.) use a real semibold instead of a synthesised smear.",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Fraunces-SemiBold.woff2",
+      "families": [
+        "Fraunces"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "anthropic 标题。有机人文衬线,替下与 black-gold/branding 共用的 Georgia。"
+    },
+    {
+      "file": "PublicSans-Regular.woff2",
+      "families": [
+        "Public Sans"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "anthropic 正文。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Manrope-Regular.woff2",
+      "families": [
+        "Manrope"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "apple 正文。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Manrope-Bold.woff2",
+      "families": [
+        "Manrope"
+      ],
+      "weight": "700",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "apple 标题。几何圆润无衬线,产品发布会的舞台感。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "BodoniModa-SemiBold.woff2",
+      "families": [
+        "Bodoni Moda"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "black-gold 标题。高反差 didone,金融年报/奢侈品的经典。"
+    },
+    {
+      "file": "Lora-Regular.woff2",
+      "families": [
+        "Lora"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "black-gold 正文衬线。"
+    },
+    {
+      "file": "CormorantGaramond-SemiBold.woff2",
+      "families": [
+        "Cormorant Garamond"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "branding 标题。低反差优雅 garalde,品牌手册/美妆。"
+    },
+    {
+      "file": "Karla-Regular.woff2",
+      "families": [
+        "Karla"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "branding + olive-gold 正文。带点个性的 grotesque。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Sora-Regular.woff2",
+      "families": [
+        "Sora"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "cool 正文。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Sora-SemiBold.woff2",
+      "families": [
+        "Sora"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "cool 标题。几何科技感,替下与 olive-gold 共用的 Avenir Next。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "IBMPlexSans-Regular.woff2",
+      "families": [
+        "IBM Plex Sans"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "mckinsey 正文。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "IBMPlexSans-SemiBold.woff2",
+      "families": [
+        "IBM Plex Sans"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "mckinsey 标题。企业/咨询语气,替下与 apple/mono 共用的 Helvetica Neue。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Archivo-Regular.woff2",
+      "families": [
+        "Archivo"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "mono 正文。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Archivo-SemiBold.woff2",
+      "families": [
+        "Archivo"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "mono 标题。骨架清晰的中性 grotesque,极简报告。",
+      "substitutesInvisibly": true
+    },
+    {
+      "file": "Marcellus-Regular.woff2",
+      "families": [
+        "Marcellus"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "olive-gold 标题。古典罗马体大写,证书/招商的仪式感。"
+    },
+    {
+      "file": "SpaceGrotesk-500.woff2",
+      "families": [
+        "Space Grotesk"
+      ],
+      "weight": "500",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "substitutesInvisibly": true,
+      "note": "Neutral-with-a-quirk grotesque (flat-sided o, angled terminals). dark-glass 的 --font-head。落到 Helvetica 只丢那点怪味,不烤。"
+    },
+    {
+      "file": "Syne-700.woff2",
+      "families": [
+        "Syne"
+      ],
+      "weight": "700",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "Extended geometric display,字宽与字重都反常规 —— memphis 的招牌。展示体,必烤。"
+    },
+    {
+      "file": "DMSerifDisplay-400.woff2",
+      "families": [
+        "DM Serif Display"
+      ],
+      "weight": "400",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "High-contrast display serif,retro-press 的标题脸。展示衬线,必烤。"
+    },
+    {
+      "file": "Quicksand-600.woff2",
+      "families": [
+        "Quicksand"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "substitutesInvisibly": true,
+      "note": "Rounded geometric sans,pastel-saas 的柔和标题。圆角是它唯一的怪味,落到 Helvetica 不至于换风格,不烤。"
+    },
+    {
+      "file": "ChakraPetch-600.woff2",
+      "families": [
+        "Chakra Petch"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "Squared techno face,neon-grid 一类硬科技族的标题脸。展示体,必烤。"
+    },
+    {
+      "file": "Lexend-500.woff2",
+      "families": [
+        "Lexend"
+      ],
+      "weight": "500",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "substitutesInvisibly": true,
+      "note": "为可读性设计的中性无衬线(字宽略放)。campus-teal 的标题脸;落到 Helvetica 只丢那点从容,不烤。"
+    },
+    {
+      "file": "Nunito-700.woff2",
+      "families": [
+        "Nunito"
+      ],
+      "weight": "700",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "substitutesInvisibly": true,
+      "note": "圆角人文无衬线,clinic-care 的标题脸。圆角是它唯一的怪味,不至于换风格,不烤。"
+    },
+    {
+      "file": "PlayfairDisplay-600.woff2",
+      "families": [
+        "Playfair Display"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "高反差过渡期衬线,wedding-blush 的标题脸。展示衬线,必烤。"
+    },
+    {
+      "file": "ZillaSlab-600.woff2",
+      "families": [
+        "Zilla Slab"
+      ],
+      "weight": "600",
+      "license": "SIL OFL 1.1 (Google Fonts)",
+      "note": "板衬线,bistro-warm 的标题脸 —— 菜单/招牌的口吻。衬线,必烤。"
+    }
+  ],
+  "_scope": "These faces are injected as @font-face and therefore apply to the BROWSER render only — the raster backdrop, any --talos-bake:1 text, --rasterize output and styles/_samples previews. They do NOT reach the NATIVE pptx text layer: there a run carries only a typeface NAME, and the consuming app (PowerPoint / LibreOffice) substitutes whatever it has. So bundling a face makes a skin's own rendering correct, but a native title still needs --talos-bake:1 (see cinereel) or an OOXML embed via bin/pptx-embed-fonts.cjs to survive into the deck the audience opens."
+}