@taloswork/ose-shared 0.1.12 → 0.1.14

package/skills/document/deck-design.md

@@ -16,7 +16,8 @@ content and outline → `content-pipeline.md`.
 
 ## Workflow
 
-1. **Plan, then fill.** Write the approved outline as a plan and run
+1. **Plan, then fill.** The approved `plan.json` IS the outline (content-pipeline.md
+   Phase 3 — written once, `--outline` renders what the user approved) and runs
    ```
    node <skill>/bin/deck-plan.cjs plan.json spec.json   # → per slide: pick · alternatives · rejected[{layout, why}]
    node <skill>/bin/deck-build.cjs spec.json deck.html
@@ -29,9 +30,15 @@ content and outline → `content-pipeline.md`.
    4", "card2_body is ~58 wide but holds ≤42 — cut ~16"), or pin `layout` + `slots`, and
    re-plan; do NOT render to find out. Edit `spec.json` freely afterwards — `deck-build`
    re-checks capacity on every build, and its warnings (unfilled slot → demo copy) are
-   defects. Put the confirmed `scenario` in the plan (it decides motion, below).
-2. **Bespoke slides, only where no layout fits** (below): hand-author that `<section>`
-   and insert it into `deck.html` at its position.
+   defects. Put the confirmed `scenario` in the plan (it decides motion, below). A
+   `\n` in a value is a line break (a typed `<br>` ships as text); a slide's `source`
+   ("IDC，2026") is its one short source line, in the footer.
+2. **Bespoke slides** (no layout fits, or approved generated-visual pages): author one
+   `<section class="slide">` in its own file and give the plan slide `file` — deck-build
+   puts it at its position (its `notes` too); every other slide stays catalog. **Never patch the built `deck.html`
+   with a script or regex**: capacity checks cannot see those edits. Change content
+   or slots and re-plan, or replace
+   that ONE slide with a bespoke `file`. Speaker notes are each slide's `notes`.
 3. **Preview, build, sign off** — "Verify before delivering" below.
 
 Hand-pasting a `layouts/<id>.tpl` skips the capacity check; a layout with a `{{#rows}}`
@@ -70,10 +77,11 @@ Violations fail loudly; nothing degrades silently.
 - **Tailwind utilities** are vendored offline (`grid grid-cols-2 gap-16`, `p-16`,
   `rounded-3xl`…) and map to native pptx — use them for layout/spacing, tokens for
   colour. Type scale: `size="1".."7"` → 12/14/16/24/32/48/72px.
-- **Images**: write `src="./hero.png"` (relative to deck.html) or an https URL —
-  html2pptx inlines each as a `data:` URI before render (the render sandbox has no
-  network); an image it cannot fetch or read is dropped. Generate figures with the
-  media-generation tool into local files.
+- **Images**: `src` accepts an absolute path, a path relative to deck.html, or HTTPS;
+  html2pptx inlines assets before rendering. Mark required content with
+  `<img data-required-image src="…" alt="…">`: unreadable or undecodable images fail
+  export and previews. Unmarked images retain best-effort loading. For useful `gen`
+  pages, follow generated-visuals.md.
 - **Icons = inline `<svg>` only** (lucide/heroicons path data, or a
   `data:image/svg+xml` URI at worst). An icon `<img>` that fails to load bakes a
   broken-image glyph into the backdrop.
@@ -99,8 +107,8 @@ Violations fail loudly; nothing degrades silently.
 
 The catalog is a palette, not a cage: a structure no layout expresses (a specific
 architecture diagram, a custom flow/topology, a signature hero moment) earns a
-hand-authored slide. Only then — a deck that hand-authors every slide is the #1
-"AI-generated" tell. A bespoke slide must:
+hand-authored slide. Approved generated-visual pages also use this route; other pages
+stay catalog. A bespoke slide must:
 
 - be one `<section class="slide" style="position:relative;width:1280px;height:720px">`,
   positioned with `absolute`, text native, diagram parts inline `<svg>`;
@@ -243,8 +251,9 @@ that genuinely continue each other. An unknown name degrades to `fade`.
 Every `font-size` and gutter in `layouts/*.tpl` is `calc(Npx * var(--type-scale,1))` /
 `calc(Npx * var(--space-scale,1))`; a skin sets the two scales in `:root` and the whole
 deck retimes with its hierarchy intact (from `mckinsey` 0.86 to `apple` 1.22; both
-default 1). A bespoke slide writes its sizes the same way. **Changed a scale? Re-run
-`deck-qa`** — scaling reflows text and can push it off-canvas; never eyeball it.
+default 1). A bespoke slide writes its sizes the same way. **Changed a scale? Re-export
+(`html2pptx deck.html out.pptx`) and read its `qa`** — scaling reflows text and can push
+it off-canvas; never eyeball it. (`deck-qa` takes the .pptx only.)
 
 ## Fonts — bundled faces reach the render, not the native text layer
 
@@ -279,7 +288,7 @@ The catalog layouts bake most of this in; on a bespoke slide it is yours.
   by weight or family. Catalog layouts already set the ladder — don't override their
   sizes. Bespoke: title `size 6–7` (48–72px), section headings `size 5–6`, body 14–24px,
   labels ≥13px; `qa` flags anything under 10pt as `tiny-font`. Never shrink type to fit
-  — split or cut instead (≤6 bullets of ≤6 words; past that, cards or a graphic).
+  — split or cut instead (≤6 items, each ≤2 lines; past that, cards or a graphic).
 - **Alignment.** Snap to a grid; one alignment per zone; never centre running body
   text. Siblings share radius, border and accent placement (use the skin's classes);
   filled boxes keep ≥0.15" inner padding, siblings ≥0.25" apart.
@@ -304,11 +313,21 @@ neon/corner-frame→tech). Exception: meaning-bearing ramps (`neural-net` layers
 When the user picks 其他/自定义 or 使用我的模板文件 in the style picker, clarify the route —
 **prefer B**:
 
-- **B — derive a bespoke look (PREFERRED).** From an **existing deck**: keep its EXACT
-  layouts/master/brand as a fillable template (`pptx-tokenize` → `doc-fill`, rewrite.md
-  "Reuse an uploaded deck"), OR take just its palette into a new skin. From a
-  **reference image / brand color**: sample the palette into a new skin. *(A deck given
-  here is for its STYLE — distinct from a deck given as content, which is text-only.)*
+- **B — derive a bespoke look (PREFERRED).** From an **existing deck** (the picker's
+  使用我的模板文件): learn its STYLE — what every page shows (logo, bars, footer,
+  page number, palette, fonts) — with `template-skin <deck.pptx> <name> --label "<a short name the user would recognise, e.g. 太平洋证券研报>"`, not its
+  photos/tables/text. The template's look **is** the style: it overrides an earlier
+  深色/浅色 ask — do not ask how to blend them. Confirm the two `samples` + `uncertain`
+  list as an image card (relay any `warnings`); a fix is a re-run: `--exclude <kept key>`
+  — a brand logo, a disclaimer (read `kept[].hint`), a photo taken as logo —
+  `--include <uncertain key>`, `--content-page N`. Never rebuild the look as a
+  hand-written skin and never set `TALOS_DOC_STYLES_DIR` yourself (2026-10-09 a deck
+  dropped its learned template for a patched mckinsey copy). Then
+  author with `style: "<name>"`: titles go in the template's title bar, content in its
+  free area (a bespoke slide starts at top ≥210px); `deck-plan --layouts --style <name>`
+  lists what fits. Refilling its
+  ORIGINAL PAGES is a separate route, if asked (rewrite.md "Reuse an uploaded
+  deck"). From a **reference image / brand color**: sample the palette into a new skin.
 - **A — map to the nearest catalog family** (they only described a vibe): pick the
   closest, render its sample, confirm.
 - **C — tweak an existing skin** ("刚才那个族但换绿色"): clone it, swap accent/palette or
@@ -341,8 +360,9 @@ Do not launch LibreOffice after every edit.
 1. **Author against the HTML preview.** `html2pptx.cjs deck.html --preview-dir <dir>
    --style <id> …` renders every slide the first time; after a fix,
    `--preview-pages 3,7-8` renders only the changed ones. Iterate until clean.
-   **Look at each preview once:** every slide after the first render (a contact sheet
-   of several slides is fine), then only the pages you re-rendered. Never re-read an
+   **Look at each preview once:** after the first render read `sheet.png` (every slide
+   as a 640×360 tile, one image), then open a single `slide-NNN.png` only where the
+   sheet shows something to check, then only the pages you re-rendered. Never re-read an
    image you already looked at — `deck-qa --final` (step 3) is the final check.
 2. **Build and fix the build's findings.** Every `html2pptx … out.pptx` prints `valid`
    (`false` exits 1 — never deliver) and `qa: {ok, findings}` — deck-qa's lint (codes in
@@ -352,21 +372,17 @@ Do not launch LibreOffice after every edit.
    exits 1), the lint, a cached Office render and its `render-overflow` /
    `render-collision` check. It returns `review` (slides with a finding or a native
    chart, which only Office draws) and `previews` (≈72dpi images of those).
-   **Read only `previews`.** Every other slide already passed your eyes in the HTML
-   preview, and its hybrid visuals were baked from that same render. Office re-wrapping
-   at a different word, spacing CJK and Latin apart or substituting a Latin face is
-   normal, not a defect.
+   **Read only `previews`.** For hybrid PPTX QA, other slides already passed the HTML
+   preview; their visuals come from that render. PDF delivery needs the final check below.
    - **Read every slide instead** (`pdf-render.cjs <deck>.office.pdf all 1`) when
      html2pptx reported a `layout (fallback)` engine, or you changed the PPTX after
      building it (`doc-xml`, `pptx-slide`, a script).
-   - `office.unavailable` (no LibreOffice here): no Office layout to check — the HTML
-     preview stands; say so when delivering. A LibreOffice that ran and FAILED exits 1
-     (never a Chromium stand-in): rerun `--final`. `--require-office` fails both.
-4. **Vision critic.** Judge the HTML previews (step 1) and the `previews` of step 3 —
-   never a second full pass. LOOK at every image you critique. Either you critique a
-   slide or a sub-agent does, not both: with sub-agents, hand slides to fresh-eyes
-   critics in parallel with each slide's findings (so they are not re-reported) and read
-   their verdicts. Judge what a machine can't: balance and whitespace, hierarchy and
+   - `office.unavailable`: PPTX has no Office layout check; disclose this. A running
+     LibreOffice that fails exits 1; rerun `--final`. `--require-office` fails both.
+4. **Vision critic — you, not a sub-agent.** Judge the HTML previews (step 1) and the
+   `previews` of step 3; PDF delivery also requires the check below. LOOK at every image you critique.
+   Never dispatch the visual review to sub-agents: they may not see images at all, and
+   one deck lost 10 minutes to critics reading placeholders. Judge what a machine can't: balance and whitespace, hierarchy and
    focal point, a real anchor, palette/motif consistency, image quality, crowding and
    uneven gaps, misaligned sibling columns, decorative lines sized for one-line text when
    the title wrapped, leftovers the lint can't phrase-match (`{{tokens}}`, "undefined",
@@ -380,6 +396,13 @@ Images are the most token-expensive step (≈ w×h∕750 tokens; a 1280×720 sli
 previews and `--final` images are ≈72dpi; `pdf-render … 2` only when fine print must be
 legible. **Do not declare done before one complete build → sign-off → critic cycle.**
 
+**PDF delivery:** convert the exact final PPTX with `doc-convert.cjs deck.pptx out.pdf`,
+or reuse its final QA Office PDF if the PPTX is unchanged. Inspect every delivered PDF
+page once. If Office is unavailable or fails, do not deliver a substitute PDF.
+Use matching fonts in the Office environment; font substitution and different viewers
+can change wrapping. Fix visible differences in the source or font environment and
+re-export. HTML previews guide authoring; they are not the final PDF.
+
 ## CJK notes
 
 - html2pptx drops the typeface from CJK runs on purpose (any pinned family can render

package/skills/document/generated-visuals.md

@@ -0,0 +1,99 @@
+# Generated visuals inside a deck
+
+Assess whether generated scenes, product concepts or illustrations will help the
+deck explain its message. The user need not explicitly request image generation.
+Choose about 2–3 useful visual pages, not a quota; use fewer or none for a short or
+data-heavy deck, and respect a request to avoid generated images.
+
+The agent calls the actual available `gen` tools; `deck-plan` and `deck-build` only
+assemble existing assets, so rebuilding a deck never regenerates images. The gen
+connector is enabled by default. Call its discovered MCP tool directly using the
+exposed schema for model parameters and references; do not invent tool names or
+duplicate provider-specific rules. Respect a manually disabled connector. If no
+generation tool is available, report that limitation rather than enabling a connector
+or promising an image.
+
+## Plan before generating
+
+Include selected visual pages in the confirmed slide count. In `plan.json`, give each
+its conclusion, visual purpose, mode, notes and a `file` path. The outline
+can reference a file that does not exist yet; `deck-build` needs it after generation.
+Use the existing outline/style confirmation before generation, with no separate image authorization.
+Supporting visuals that preserve an approved outline's message and slide count need no
+new approval, even when chosen later during production.
+
+Default to **generated image + HTML text**: scene, product concept or illustration in
+the image; title, conclusion, accurate figures and sources in the HTML. Native text
+remains editable unless the selected skin bakes that class (`--talos-bake:1`).
+**Whole-page image** is an option for a poster or visual story; its internal text and
+objects cannot be edited separately. Keep evidence-based charts in the chart tools;
+describe a generated concept as a concept, not a photo of a real event or a source.
+
+Example slide entry among the ordinary slides in `plan.json`:
+
+```json
+{
+  "role": "content",
+  "title": "One workspace brings the team together",
+  "image": true,
+  "file": "visuals/workspace.html",
+  "narrative": "Generated visual: a shared workspace concept, image plus HTML text; make the proposed experience concrete.",
+  "notes": "Concept illustration. Explain how shared context reduces handoffs."
+}
+```
+
+Keep plan and spec in the same directory: `file` is resolved relative to the spec.
+Planning keeps the slide's position and notes; write its visible text in the HTML,
+since file slides do not fill catalog slots. Do not put `<img>` into ordinary `slots`
+(they escape HTML), and `image: true` alone does not supply an asset.
+
+## Generate for the actual image box
+
+Once approved, prepare each prompt for the intended box: message, subject/action,
+selected palette and photographic/illustration style, subject placement, crop
+tolerance and text space. Set size and aspect ratio in the tool fields for the actual
+image box. Keep titles and exact numbers outside the image by default. For related scenes, carry the same product/person references and visual
+direction through the supported `gen` reference mechanism.
+
+Keep a small working record of slide number, prompt file, references and returned
+image path. Use the **exact absolute path returned by `gen`** in the HTML; do not
+rename or move the image. The assembled deck may be in a different directory from
+the per-slide file. Escape HTML attribute characters in the path (`&`, `"`, `<`).
+Inspect each generated result before assembling. Reuse it for text/layout revisions;
+regenerate only when the image needs to change.
+
+If gen is unavailable, or a login or network failure prevents generation, report the
+actual error and affected pages. Do not claim a placeholder was generated. If a
+non-generated layout is a suitable fallback, disclose the change and revise the plan
+and slide together; never silently substitute an image already committed in the outline.
+Keep required-image checks on every generated image that remains in the deck.
+
+## Assemble through the existing file route
+
+Write exactly one `section.slide` per file. Example split page (replace the example
+image path with the real tool result and match the selected skin's type/spacing):
+
+```html
+<section class="slide" style="position:relative;width:1280px;height:720px">
+  <h2 class="deck-title" style="position:absolute;left:64px;top:80px;width:1152px;margin:0;color:var(--title);font-size:calc(48px * var(--type-scale,1))">One workspace brings the team together</h2>
+  <p style="position:absolute;left:64px;top:250px;width:420px;color:var(--body);font-size:calc(28px * var(--type-scale,1))">Shared context makes the next step visible.</p>
+  <img data-required-image src="/absolute/path/returned-by-gen.png" alt="Concept illustration of a shared team workspace" style="position:absolute;left:552px;top:210px;width:656px;height:420px;object-fit:cover">
+</section>
+```
+
+`data-required-image` is a presence marker: even `="false"` means required. Use it on
+every generated content image. Local read, fetch or browser decode failure blocks
+previews and PPTX export. Repair the path or asset; never silently replace
+a required image with a placeholder, drop the page, or remove the marker to deliver.
+
+An uploaded template keeps its title bar, logo and footer: use `h2.deck-title` and
+keep content at top ≥210px in its content zone. A whole-page image must also fit that
+zone; only use full bleed when the selected style permits it. Preserve the deck's
+export mode: a few generated images do not require global `--rasterize`.
+
+Build with the usual `deck-build` → `html2pptx` commands and the same style flags.
+Follow deck-design.md's preview and final QA once per image: verify page order and
+notes, image presence, subject crop, image text, contrast, template chrome and style
+consistency across the generated pages. Fix and recheck only changed pages.
+Deliver a PDF by converting the final PPTX through `doc-convert`, including its embedded
+images; do not separately print the slide HTML.

package/skills/document/layouts/MAINTAINERS.md

@@ -0,0 +1,33 @@
+# Maintaining the layout library
+
+Not read while making a deck — this is for whoever edits a `.tpl`, a skin's geometry or
+the catalog.
+
+- **Slot index.** Regenerate `layouts/slots.json` with `node scripts/deck/gen-slots.mjs`
+  after touching a `.tpl`.
+- **Capacity is measured, not written down.** `layouts/capacity.json` holds, per layout ×
+  catalog style, how wide each slot's text may get (CJK = 1, Latin ≈ 0.5), how many rows
+  each `{{#rows}}` block holds, and each chart's box — measured in headless Chromium by
+  `node scripts/deck/gen-capacity.mjs` (≈5 min). Re-run it after touching a `.tpl`, a
+  skin's geometry (sizes, spacing, `--type-scale`) or the catalog;
+  `tests/unit/deck-capacity.test.ts` fails until you do (colour-only edits are ignored).
+- **Optional lines** (2026-10-09): `subhead` (one line at `top:246px`, under a one-line
+  title) and `takeaway` (one line at `bottom:56px`, above the footer rule) are offered only
+  by layouts whose content clears them in every catalog style — measured: content top
+  ≥ 282px for `subhead`, content bottom ≤ 620px at the designed 3-row fill for
+  `takeaway`. Both render nothing when empty (`.deck-subhead:empty`,
+  `.deck-takeaway:empty` in `styles/_contract-defaults.css`).
+
+**不要给可变内容写死容器高度**（`.tpl` 与 bespoke 页都适用）。皮肤给 `.card` 设了
+`overflow:hidden` 时，`.card{height:…px}` 会把超出的文字**静默裁掉**（`blocks-2x2` 就这样
+带病出厂过）。让高度由内容决定：网格用 `grid-auto-rows:min-content`（必须显式写
+`min-content`——`1fr`/`auto` 的自动下限对 `overflow` 非 visible 的网格项一律归零），余量
+交给外层 `justify-content:space-between`。这样超量内容会顶出页面，被 `deck-qa` 的
+`off-canvas`/`overlap` 抓到。PPTX walker 不保留祖先的裁切，原来在 HTML 中被裁掉的字可能
+完整画到容器外；版式生产线的 `scripts/deck/deck-qa-sweep.mjs` 用 `clipped` 阻断裁切。
+
+`spill` measures in-flow text outside its nearest painted container. It remains
+advisory until the capacity probe uses the same measure; `decor-overlap` remains
+blocking. Explicitly positioned or transformed elements are excluded because a
+badge may intentionally cross its parent edge. Keep both clipped and visible
+overflow fixtures when changing the measurement.

package/skills/document/layouts/README.md

@@ -61,33 +61,31 @@ Plain list layouts take rows too: `team-row.members{name,role}` ·
 `brand-values.values{name,body}` · `color-palette.swatches{name,hex}` ·
 `steps-vertical.steps{name,body}` · `toc-panel.entries{name,desc}`.
 
+**Optional lines** — a slide's `subtitle` (口径 / why it matters) and `takeaway` (启示) fill
+`subhead` (under a one-line title) and `takeaway` (above the footer), offered by
+cards-3 · three-kpi · two-kpi · steps · steps-vertical · timeline · icon-row ·
+ring-progress · versus · data-table · image-grid · gantt (both) and funnel · pyramid ·
+matrix-2x2 (subtitle) · comparison (takeaway). Left out, they render nothing; written for
+a layout without the line, `deck-plan` warns `dropped` and ranks a layout that has it.
+
 Anything the spec gets wrong — unknown layout/slot/field, a repeat block with no rows, a
 figure row missing its numbers — **fails the build** (exit 1, nothing written) rather than
-shipping the template's demo content. Regenerate the index with `node scripts/deck/gen-slots.mjs`
-after touching a `.tpl`.
-
-**Capacity is measured, not written down.** `layouts/capacity.json` holds, per layout ×
-catalog style, how wide each slot's text may get (CJK = 1, Latin ≈ 0.5), how many rows
-each `{{#rows}}` block holds, and each chart's box — measured in headless Chromium by
-`node scripts/deck/gen-capacity.mjs` (≈5 min). `deck-plan` picks layouts with it and
-`deck-build` rejects overflow / un-filled numbered slots with it. Re-run the generator
-after touching a `.tpl`, a skin's geometry (sizes, spacing, `--type-scale`) or the
-catalog; `tests/unit/deck-capacity.test.ts` fails until you do (colour-only edits are
-ignored). The density column below feeds `deck-plan` too: a rows layout is not offered
-for fewer items than its `(n–m)` names.
-
-**不要给可变内容写死容器高度**（`.tpl` 与 bespoke 页都适用）。皮肤给 `.card` 设了
-`overflow:hidden` 时，`.card{height:…px}` 会把超出的文字**静默裁掉**（`blocks-2x2` 就这样
-带病出厂过）。让高度由内容决定：网格用 `grid-auto-rows:min-content`（必须显式写
-`min-content`——`1fr`/`auto` 的自动下限对 `overflow` 非 visible 的网格项一律归零），余量
-交给外层 `justify-content:space-between`。这样超量内容会顶出页面，被 `deck-qa` 的
-`off-canvas`/`overlap` 抓到。被祖先 `overflow:hidden` 裁掉的字不进 pptx 几何，运行时
-`deck-qa` 看不到，只有版式生产线的 `scripts/deck/deck-qa-sweep.mjs`（`clipped` 硬失败）拦得住。
+shipping the template's demo content. **Capacity is measured** (`layouts/capacity.json`,
+per layout × style: slot widths, row ceilings, chart boxes): `deck-plan` picks with it,
+`deck-build` rejects overflow with it. The density column below feeds `deck-plan` too: a
+rows layout is not offered for fewer items than its `(n–m)` names. A bespoke slide never
+fixes a card's height around variable text (`overflow:hidden` clips it silently) — use
+`grid-auto-rows:min-content`. Maintaining layouts: `layouts/MAINTAINERS.md`.
+
+QA: `clipped` and `decor-overlap` block; `spill` is advisory. The PPTX walker does
+not reproduce ancestor clipping, so inspect the exported deck too.
 
 ## Catalog
 
 Each slide carries `data-layout="<id>"` (drives the diversity lint + traceability).
 
+**Theme V2 only:** `pitch-problem` · `pitch-solution` · `market-rings` · `product-device` · `traction-milestones` · `business-model` · `pricing-tiers` · `funding-ask` · `customer-proof` · `team-founders` (profiles.json `themeV2Layouts`). A style in the `classic-v1` collection (cool, mckinsey, apple …) renders V1 and cannot use them — `deck-plan --layouts --style <id>` lists exactly what a style can use and the content each layout takes.
+
 | layout-id | role | structure (P1) | density (P2) | has-image (P1) | pick when |
 |---|---|---|---|---|---|
 | `cover` | cover | hero · left-title | — | text-only (bg) | 封面 / 开场 |
@@ -120,6 +118,8 @@ Each slide carries `data-layout="<id>"` (drives the diversity lint + traceabilit
 | `image-left` | content | image-left + text-right | medium (3) | **photo/diagram slot** | 图文案例(图在左) |
 | `image-grid` | content | 3-up image gallery + captions | medium (3) | **photo slots** | 三图并列 / 图库 |
 | `concept-hub` | content | center concept + satellites | medium (4) | text-only | 核心框架(中心+维度) |
+| `hub-flow` | content | 3 inputs → core → result | medium (3) | text-only | 多源汇聚→核心→产出(产品原理/数据流) |
+| `mock-qa` | content · product | interface sketch: question → cited answer + 2 sources | light (2) | text-only | 产品问答/证据链示意(无截图时) |
 | `image-full` | content | full-bleed image + overlay caption | light | **full-bleed photo** | 全出血大图 + 压字说明 |
 | `cover-image` | cover | full-bleed image + overlay title | — | **full-bleed photo** | 图片封面(压字) |
 | `timeline` | content | horizontal dated timeline | medium (4–5) | text-only | 时间轴 / 发展历程 |

package/skills/document/layouts/big-stat.tpl

@@ -1,4 +1,4 @@
 <!-- layouts/big-stat — structure-only (paint via styles/<skin>/skin.css). data-layout drives P1/P2/P3 + dedup. -->
 <section class="slide" data-layout="big-stat" style="position:relative;width:1280px;height:720px;overflow:hidden"><div class="slide-backdrop"></div><div class="eyebrow-row" style="position:absolute;left:calc(96px * var(--space-scale,1));top:132px;display:flex;align-items:center;gap:14px"><span class="accent-bar" style="width:30px;height:1px;display:inline-block"></span><span class="eyebrow" style="font-size:calc(13px * var(--type-scale,1));letter-spacing:.28em">{{eyebrow|KEY METRIC}}</span></div><h2 class="deck-title" style="position:absolute;left:calc(92px * var(--space-scale,1));top:158px;font-size:calc(48px * var(--type-scale,1));letter-spacing:-.4px">{{title|}}</h2>
- <div class="stat-num" style="position:absolute;left:90px;top:250px;font-weight:800;line-height:1;font-size:calc(216px * var(--type-scale,1));letter-spacing:-2px">{{stat|585}}<span class="stat-unit" style="font-size:calc(64px * var(--type-scale,1))">{{unit| 单位}}</span></div><div class="stat-lead" style="position:absolute;left:100px;top:520px;font-size:calc(30px * var(--type-scale,1));font-weight:600">{{lead|一句结论,数字说明了什么}}</div><p class="stat-note" style="position:absolute;left:100px;top:580px;width:900px;font-size:calc(17px * var(--type-scale,1));line-height:1.6">{{note|一句支撑说明,给上下文与来源。}}</p>
+ <div class="stat-num" style="position:absolute;left:calc(90px * var(--space-scale,1));top:250px;font-weight:800;line-height:1;font-size:calc(216px * var(--type-scale,1));letter-spacing:-2px">{{stat|585}}<span class="stat-unit" style="font-size:calc(64px * var(--type-scale,1))">{{unit| 单位}}</span></div><div class="stat-lead" style="position:absolute;left:calc(100px * var(--space-scale,1));top:520px;font-size:calc(30px * var(--type-scale,1));font-weight:600">{{lead|一句结论,数字说明了什么}}</div><p class="stat-note" style="position:absolute;left:calc(100px * var(--space-scale,1));top:580px;width:900px;font-size:calc(17px * var(--type-scale,1));line-height:1.6">{{note|一句支撑说明,给上下文与来源。}}</p>
 <div class="rule rule-foot" style="position:absolute;left:calc(96px * var(--space-scale,1));right:calc(96px * var(--space-scale,1));bottom:40px;height:1px"></div><div class="deck-footer" style="position:absolute;left:calc(96px * var(--space-scale,1));bottom:17px;font-size:calc(12px * var(--type-scale,1));letter-spacing:.1em">{{footer|报告标题 / 章节}}</div><div class="deck-pageno" style="position:absolute;right:calc(96px * var(--space-scale,1));bottom:17px;font-size:calc(12px * var(--type-scale,1))">{{pageno|01}}</div></section>