AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He
refactor(charts): extract chart calibration into standalone verify-charts workflow
hugohe3c1ea7deb5d76
diff --git a/AGENTS.md b/AGENTS.mdindex 64d5a106..85e47d35 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -8,7 +8,9 @@ Before any PPT generation task, **you MUST first read [`skills/ppt-master/SKILL.PPT Master is an AI-driven presentation generation system. Multi-role collaboration (Strategist → Image_Generator → Executor) converts source documents (PDF/DOCX/URL/Markdown) into natively editable PPTX with real PowerPoint shapes (DrawingML).-**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Chart Calibration → Post-processing → Export PPTX`+**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`++> Decks containing data charts: run the standalone [`verify-charts`](skills/ppt-master/workflows/verify-charts.md) workflow between the executor and post-processing steps to calibrate chart coordinates.## Execution Requirements@@ -47,20 +49,27 @@ python3 skills/ppt-master/scripts/analyze_images.py <project_path>/imagespython3 skills/ppt-master/scripts/image_gen.py "prompt" --aspect_ratio 16:9 --image_size 1K -o <project_path>/imagespython3 skills/ppt-master/scripts/svg_quality_checker.py <project_path>-# Chart coordinate calibration (MANDATORY after quality check, before notes)-# Step 1: find pages with charts-grep -l "chart-plot-area" <project_path>/svg_output/*.svg-# Step 2: run calculator per chart type and update SVG coordinates-python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar --data "L1:V1,L2:V2" --area "x_min,y_min,x_max,y_max" --bar-width 120-python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie --data "A:35,B:25" --center "cx,cy" --radius 200-python3 skills/ppt-master/scripts/svg_position_calculator.py calc line --data "x1:y1,x2:y2" --area "x_min,y_min,x_max,y_max" --y-range "0,max"-# Post-processing pipeline: run sequentially, one command at a timepython3 skills/ppt-master/scripts/total_md_split.py <project_path>python3 skills/ppt-master/scripts/finalize_svg.py <project_path>python3 skills/ppt-master/scripts/svg_to_pptx.py <project_path> -s final```+### Chart calibration (standalone — run on demand, not part of main pipeline)++For decks containing data charts. Full workflow: [`workflows/verify-charts.md`](skills/ppt-master/workflows/verify-charts.md).++```bash+# Step 1: enumerate chart pages by their plot-area markers+grep -l "chart-plot-area" <project_path>/svg_output/*.svg++# Step 2: run calculator per page (chart type drives the subcommand)+python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar --data "L1:V1,L2:V2" --area "x_min,y_min,x_max,y_max" --bar-width 120+python3 skills/ppt-master/scripts/svg_position_calculator.py calc line --data "x1:y1,x2:y2" --area "x_min,y_min,x_max,y_max" --y-range "0,max"+python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie --data "A:35,B:25" --center "cx,cy" --radius 200 [--inner-radius 120]+python3 skills/ppt-master/scripts/svg_position_calculator.py calc radar --data "D1:V1,D2:V2,D3:V3" --center "cx,cy" --radius 200+```+## Core Directories- `skills/ppt-master/SKILL.md` — main workflow authority.diff --git a/CLAUDE.md b/CLAUDE.mdindex f688b81b..b06537c6 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -8,7 +8,9 @@ Before any PPT generation task, **you MUST first read [`skills/ppt-master/SKILL.PPT Master is an AI-driven presentation generation system. Multi-role collaboration (Strategist → Image_Generator → Executor) converts source documents (PDF/DOCX/URL/Markdown) into natively editable PPTX with real PowerPoint shapes (DrawingML).-**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Chart Calibration → Post-processing → Export PPTX`+**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`++> Decks containing data charts: run the standalone [`verify-charts`](skills/ppt-master/workflows/verify-charts.md) workflow between the executor and post-processing steps to calibrate chart coordinates.## Execution Requirements@@ -46,20 +48,27 @@ python3 skills/ppt-master/scripts/analyze_images.py <project_path>/imagespython3 skills/ppt-master/scripts/image_gen.py "prompt" --aspect_ratio 16:9 --image_size 1K -o <project_path>/imagespython3 skills/ppt-master/scripts/svg_quality_checker.py <project_path>-# Chart coordinate calibration (MANDATORY after quality check, before notes)-# Step 1: find pages with charts-grep -l "chart-plot-area" <project_path>/svg_output/*.svg-# Step 2: run calculator per chart type and update SVG coordinates-python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar --data "L1:V1,L2:V2" --area "x_min,y_min,x_max,y_max" --bar-width 120-python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie --data "A:35,B:25" --center "cx,cy" --radius 200-python3 skills/ppt-master/scripts/svg_position_calculator.py calc line --data "x1:y1,x2:y2" --area "x_min,y_min,x_max,y_max" --y-range "0,max"-# Post-processing pipeline: run sequentially, one command at a timepython3 skills/ppt-master/scripts/total_md_split.py <project_path>python3 skills/ppt-master/scripts/finalize_svg.py <project_path>python3 skills/ppt-master/scripts/svg_to_pptx.py <project_path> -s final```+### Chart calibration (standalone — run on demand, not part of main pipeline)++For decks containing data charts. Full workflow: [`workflows/verify-charts.md`](skills/ppt-master/workflows/verify-charts.md).++```bash+# Step 1: enumerate chart pages by their plot-area markers+grep -l "chart-plot-area" <project_path>/svg_output/*.svg++# Step 2: run calculator per page (chart type drives the subcommand)+python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar --data "L1:V1,L2:V2" --area "x_min,y_min,x_max,y_max" --bar-width 120+python3 skills/ppt-master/scripts/svg_position_calculator.py calc line --data "x1:y1,x2:y2" --area "x_min,y_min,x_max,y_max" --y-range "0,max"+python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie --data "A:35,B:25" --center "cx,cy" --radius 200 [--inner-radius 120]+python3 skills/ppt-master/scripts/svg_position_calculator.py calc radar --data "D1:V1,D2:V2,D3:V3" --center "cx,cy" --radius 200+```+## Architecture- `skills/ppt-master/SKILL.md` — main workflow authority.diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 0f6673e2..d610ae83 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -74,6 +74,7 @@ For complete tool documentation, see `${SKILL_DIR}/scripts/README.md`.| Workflow | Path | Purpose ||----------|------|---------|| `create-template` | `workflows/create-template.md` | Standalone template creation workflow |+| `verify-charts` | `workflows/verify-charts.md` | Chart coordinate calibration — run after SVG generation if the deck contains data charts |---@@ -262,22 +263,6 @@ python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path>- `warning` entries (low-res image, non-PPT-safe font tail, etc.): fix when straightforward, otherwise acknowledge and release.- Run against `svg_output/` (not after `finalize_svg.py` — finalize rewrites SVG and masks violations).-**Chart Coordinate Calibration Gate** ⚠️ (MANDATORY) — after quality check passes, BEFORE Logic Construction:--> **STOP — This is a separate gate, not part of the quality check. Do NOT skip.**--1. **Scan-1 — find marked chart pages**:- ```bash- grep -l "chart-plot-area" <project_path>/svg_output/*.svg- ```-2. **Scan-2 — independently verify chart-like structures exist** (catches pages where the marker was forgotten):- ```bash- grep -l "barGrad\|bar-[0-9]\|groupGrad\|stackShadow\|donut-sectors\|sector-[0-9]\|pieChart\|radarChart\|areaGrad\|lineGrad\|dotShadow\|pointShadow\|hbarGrad\|waterfallGrad\|paretoGrad" <project_path>/svg_output/*.svg- ```-3. **If scan-2 finds pages NOT in scan-1**: those pages contain chart visuals but are MISSING the `<!-- chart-plot-area -->` marker. Go back, read the SVG's axis coordinates, add the marker per `executor-base.md §3.1`, then proceed to step 4.-4. **If scan-1 is non-empty**: run `svg_position_calculator.py` per page and update SVG coordinates (see `executor-base.md §5.1`).-5. **If both scans are empty**: no chart pages exist. Confirm and proceed.-**Logic Construction Phase**: generate speaker notes → `<project_path>/notes/total.md`**✅ Checkpoint — Confirm all SVGs and notes are fully generated and quality-checked. Proceed directly to Step 7 post-processing**:@@ -285,12 +270,11 @@ python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path>## ✅ Executor Phase Complete- [x] All SVGs generated to svg_output/- [x] svg_quality_checker.py passed (0 errors)-- [x] Chart Calibration Gate: ran `grep -l "chart-plot-area"` → ran- `svg_position_calculator.py calc <type>` for each result and updated- SVG coordinates (or confirmed: no calculator-supported charts)- [x] Speaker notes generated at notes/total.md```+> **Chart pages?** If this deck contains data charts (bar / line / pie / radar / etc.), run the standalone [`verify-charts`](workflows/verify-charts.md) workflow before Step 7 to calibrate coordinates. AI models routinely introduce 10–50 px errors when mapping data to pixel positions; verify-charts eliminates that class of error. Skip if no chart pages.+---### Step 7: Post-processing & Exportdiff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex c4ce5542..15666130 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -78,16 +78,15 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`- **Main-agent ownership**: SVG generation must run in the main agent (not sub-agents) — pages share upstream context for cross-page visual continuity- **Generation rhythm**: lock global design context first, then generate pages sequentially in one continuous context. No batched groups (e.g., 5 at a time).- **Phased batch generation** (recommended):- 1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Do NOT run `svg_position_calculator.py` during the initial draft — use layout judgment for chart marks. **MUST embed calibration markers** per §3.1 below on every chart page.+ 1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Use layout judgment for chart marks during the draft. **MUST embed plot-area markers** per §3.1 below on every chart page — coordinate calibration is a post-generation step (see [`workflows/verify-charts.md`](../workflows/verify-charts.md)) that depends on these markers.2. **Quality Check Gate**: run `python3 scripts/svg_quality_checker.py <project_path>` on `svg_output/`. Any `error` (banned features, viewBox mismatch, spec_lock drift, non-PPT-safe font, etc.) MUST be fixed on the offending page before proceeding — regenerate and re-check. Address `warning`s when straightforward. Do NOT defer to after `finalize_svg.py` — finalize rewrites SVG and masks some violations.- 3. **Chart Calibration Gate** ⚠️ (MANDATORY, do NOT skip): after quality check passes, run `svg_position_calculator.py` for every page containing a `<!-- chart-plot-area -->` marker. See §5.1 for the full workflow: `grep → calc → compare → update SVG`. AI models routinely introduce 10–50 px coordinate errors; this gate eliminates that class of error. If no calculator-supported charts exist, explicitly confirm skip.- 4. **Logic Construction Phase**: after SVGs pass quality check AND calibration, batch-generate speaker notes for narrative continuity.+ 3. **Logic Construction Phase**: after SVGs pass the quality check, batch-generate speaker notes for narrative continuity.### 3.1 Chart Plot-Area Marker (MANDATORY on every chart page)-> ⚠️ **Without this marker, the Chart Calibration Gate (§5.1) cannot enumerate chart pages and calibration is silently skipped. This is the #1 root cause of inaccurate chart coordinates.**+> The [`verify-charts`](../workflows/verify-charts.md) workflow enumerates chart pages from `design_spec.md §VII`, then reads each page's plot-area marker to feed `svg_position_calculator.py`. Missing marker → verify-charts has to re-derive the plot area from axis lines, paying the cost on every run.-Every SVG page that contains a data visualization chart MUST include a calibration marker inside `<g id="chartArea">`, placed **after axis lines** and **before the first data element** (bar, line, area, point).+Every SVG page that contains a data visualization chart MUST include a plot-area marker inside `<g id="chartArea">`, placed **after axis lines** and **before the first data element** (bar, line, area, point).**Rectangular plot area** (bar / horizontal_bar / grouped_bar / stacked_bar / line / area / stacked_area / scatter / waterfall / pareto / butterfly):@@ -221,44 +220,13 @@ When the Design Spec includes **VII. Visualization Reference List**, read the re> Templates: `templates/charts/` (70 types). Index: `templates/charts/charts_index.json`-### 5.1 Chart Coordinate Calibration (After SVG Quality Checker)+### 5.1 Chart Coordinate Calibration-> For chart types supported by `svg_position_calculator.py`, run calibration **after** `svg_quality_checker.py` passes and **before** Logic Construction. Calibrates already-generated SVG against the plot area. Do NOT run during initial draft. Only applies to calculator-supported types.+Coordinate calibration runs as a **standalone post-generation workflow**, not inside the executor pipeline. After SVG generation completes, if the deck contains data charts, run [`workflows/verify-charts.md`](../workflows/verify-charts.md) before post-processing.-**Workflow after `svg_quality_checker.py` passes:**+The executor's only obligation here is upstream: embed the `<!-- chart-plot-area ... -->` marker on every chart page during initial draft (§3.1). Verify-charts enumerates chart pages from `design_spec.md §VII` (authoritative deck plan) and uses the marker to feed `svg_position_calculator.py`.-1. **Confirm chart type is supported** — calculator covers: `bar`, `pie`/`donut`, `radar`, `line`/`area`/`scatter`. Area has no separate mode — use `calc line` for the top boundary, then close to `y_max`. Grid layout is optional. Other visualizations (timeline, process, framework, maps, pictograms…) skip this step.--2. **Identify the plot area** — the data drawing rectangle only; excludes title, legend, axis labels, footnotes, annotations.-- REQUIRED SVG marker on every calculator-supported chart page (added during initial Visual Construction, not retrofitted later) — calibration enumerates pages by `grep -l "chart-plot-area"`:- ```xml- <!-- chart-plot-area: x_min,y_min,x_max,y_max -->- ```--3. **Calculate the expected coordinates** — run the calculator for the chart type and manually compare the output with the SVG's existing mark coordinates:- ```bash- # Bar chart- python3 scripts/svg_position_calculator.py calc bar \- --data "Label1:Value1,Label2:Value2" --area "x_min,y_min,x_max,y_max" --bar-width 120-- # Line / area chart- python3 scripts/svg_position_calculator.py calc line \- --data "x1:y1,x2:y2,..." --area "x_min,y_min,x_max,y_max" --y-range "0,max"-- # Pie / donut chart- python3 scripts/svg_position_calculator.py calc pie \- --data "Slice1:Value1,Slice2:Value2" --center "cx,cy" --radius 200- ```-- For an area chart, use the line output as the top boundary. The filled SVG path should close to the plot area's bottom edge:- ```svg- M first_x,first_y ... L last_x,last_y L last_x,y_max L first_x,y_max Z- ```--4. **If coordinates differ** — manually update SVG attributes from calculator output, rerun `svg_quality_checker.py`, repeat. Do NOT use regex or bulk replacement.--> AI models routinely introduce 10-50 px errors when mapping data to pixel positions. Errors compound across bars/lines/arcs, distorting proportions. The calculator eliminates this class of error.+> Do NOT run `svg_position_calculator.py` during the initial draft. The calculator calibrates already-generated SVGs against their declared plot areas; running it before the SVG exists has nothing to compare against.---diff --git a/skills/ppt-master/workflows/verify-charts.md b/skills/ppt-master/workflows/verify-charts.mdnew file mode 100644index 00000000..d6773d3e--- /dev/null+++ b/skills/ppt-master/workflows/verify-charts.md@@ -0,0 +1,149 @@+---+description: Verify chart coordinates against the design spec using svg_position_calculator.py+---++# Verify Charts Workflow++> Standalone post-generation step. Run after a deck containing data charts has finished SVG generation, before post-processing & export. Catches the 10–50 px coordinate errors AI models routinely introduce when mapping data to pixel positions.++This workflow is **independent**: it reads `design_spec.md` and the generated SVGs, then runs the calculator script — no upstream conversation context required. Safe to invoke in a fresh session.++## When to Run++- The deck contains one or more data visualization charts of types supported by a **single** `svg_position_calculator.py calc` invocation. The supported set is fixed by the calculator's CLI subcommands (`bar`, `line`, `pie`, `radar`) and their single-series model — see Step 1 for the exact `charts_index.json` keys.+- SVGs are generated to `<project_path>/svg_output/` and `svg_quality_checker.py` has passed.+- Post-processing (`finalize_svg.py`, `svg_to_pptx.py`) has **not yet** run.++Composite/derived chart types (multi-series, stacked, signed-delta, mirrored, dual-axis, cumulative-overlay) cannot be calibrated by one calc call and are out of scope. Same for non-XY visualizations (treemap / gauge / funnel / heatmap / matrix / bubble / box plot) and infographics / diagrams / frameworks / maps.++---++## Step 1: Build the page list from the design spec++Read `<project_path>/design_spec.md` §VII Visualization Reference List (authoritative deck plan; cross-check against §IX page outline) and **filter strictly to the calculator-supported set below**. Anything outside this set is out of scope — do NOT include it in the list, even if §VII labels it as a chart.++| Calculator subcommand | In-scope `charts_index.json` keys | Notes |+|-----------------------|-----------------------------------|-------|+| `calc bar` | `bar_chart`, `horizontal_bar_chart` | Use `--horizontal` for the latter. Single series only. |+| `calc line` | `line_chart`, `area_chart`, `scatter_chart` | Area uses line output as the top boundary, then closes to `y_max`. |+| `calc pie` | `pie_chart`, `donut_chart` | Donut: pass `--inner-radius`. |+| `calc radar` | `radar_chart` | Separate subcommand — not under `calc pie`. |++**Verifiable via repeated calls + cumulative precompute** (see [Stacked recipe](#stacked-recipe) below):++- `stacked_bar_chart`, `stacked_area_chart` — include in the Step 1 list, mark `type=stacked-bar` / `type=stacked-area`, and verify per the recipe.++**Out of scope** (no single-call model and no clean repeat-call recipe — skip silently):++- Multi-series / signed / paired / dual-axis bar & line: `grouped_bar_chart`, `butterfly_chart`, `waterfall_chart`, `bullet_chart`, `dumbbell_chart`, `pareto_chart`, `dual_axis_line_chart`+- Non-XY data visualizations: `treemap_chart`, `gauge_chart`, `progress_bar_chart`, `funnel_chart`, `matrix_2x2`, `bubble_chart`, `heatmap_chart`, `box_plot_chart`, `kpi_cards`+- Everything in the `process` / `strategy` / `architecture` / `infographic` / `table` categories of `charts_index.json`++Resulting list:++```+P03 03_market_share.svg type=bar+P07 07_growth.svg type=line+P11 11_share_split.svg type=pie+```++If §VII is absent (legacy project / free-structure deck), skip this workflow and report: "design_spec.md has no §VII — chart pages cannot be enumerated authoritatively, verify-charts skipped". Do NOT fall back to guessing from SVG content; that reintroduces the silent-skip failure this workflow was built to eliminate.++If the filtered list is empty, output `verify-charts: spec declares no calculator-supported chart pages, nothing to verify` and stop.++---++## Step 2: Per page — read SVG, run calculator, compare, update++For each page in the Step 1 list:++1. Read `<project_path>/svg_output/<page>.svg`.+2. Locate the plot-area definition:+ - Preferred: `<!-- chart-plot-area: ... -->` marker placed by Executor (see [executor-base.md §3.1](../references/executor-base.md)). Read coordinates directly.+ - If missing: derive the plot area from the SVG's axis lines (rectangular charts) or center/radius elements (radial charts). Then **add the marker back to the SVG** so future runs are not paying this cost again.+3. Read the data series from the SVG's `<text>` label/value elements.+4. Run the matching calculator command:++ ```bash+ # bar_chart / horizontal_bar_chart (add --horizontal for the latter)+ python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar \+ --data "Label1:Value1,Label2:Value2" --area "x_min,y_min,x_max,y_max" --bar-width 120++ # line_chart / area_chart / scatter_chart — area uses line output as the top boundary, then closes to y_max+ python3 skills/ppt-master/scripts/svg_position_calculator.py calc line \+ --data "x1:y1,x2:y2,..." --area "x_min,y_min,x_max,y_max" --y-range "0,max"++ # pie_chart+ python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie \+ --data "Slice1:Value1,Slice2:Value2" --center "cx,cy" --radius 200++ # donut_chart (pie with inner-radius)+ python3 skills/ppt-master/scripts/svg_position_calculator.py calc pie \+ --data "Slice1:Value1,Slice2:Value2" --center "cx,cy" --radius 200 --inner-radius 120++ # radar_chart (separate subcommand)+ python3 skills/ppt-master/scripts/svg_position_calculator.py calc radar \+ --data "Dim1:Value1,Dim2:Value2,Dim3:Value3" --center "cx,cy" --radius 200+ ```++ Area chart fill path closes to the bottom edge of the plot area:++ ```svg+ M first_x,first_y ... L last_x,last_y L last_x,y_max L first_x,y_max Z+ ```++5. Compare calculator output against the SVG's existing coordinates. If they differ, update the SVG attributes by hand (do NOT use regex / bulk replacement — coordinates are positional and easy to swap incorrectly).++After updating any page, re-run the quality checker on the project to confirm nothing broke:++```bash+python3 skills/ppt-master/scripts/svg_quality_checker.py <project_path>+```++---++## Stacked recipe++`stacked_bar_chart` and `stacked_area_chart` are not single-call but reduce cleanly to repeated calls on existing primitives. The operator already had to compute cumulative values to draw the SVG — verify-charts reuses them.++**Stacked bar** — for N stacked series on the same x categories, run `calc bar` N times. Pass each segment's **height** as the data value, and shift `--area`'s `y_max` down by the sum of all lower segments for that category. Compare each segment's `(x, y, width, height)` against the SVG.++```bash+# Example: two-series stack at category "Q1" with bottom=30, top=20, plot area y from 100 to 500+# Run 1 — bottom segment (origin = baseline)+python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar \+ --data "Q1:30,Q2:..." --area "x_min,100,x_max,500" --bar-width 80+# Run 2 — top segment (origin shifted up by bottom segment's height in pixels)+python3 skills/ppt-master/scripts/svg_position_calculator.py calc bar \+ --data "Q1:20,Q2:..." --area "x_min,100,x_max,<500 - bottom_height_px>" --bar-width 80+```++**Stacked area** — for N stacked series, run `calc line` N times on **cumulative** y-values (series 1 raw; series 2 = series1+series2; …). Each call yields the top boundary of one band. Each band's SVG path closes to the **previous** band's top boundary (not to `y_max`).++If a stack page's segment positions don't reduce to this recipe (e.g., negative segments, percent-stacked with non-100 totals), mark it `manual-verify` in the receipt and inspect by hand — do not silently pass.++---++## Step 3: Per-page receipt++Output one line per page from the Step 1 list. Receipt count MUST equal Step 1 list length — that is the gate-closing artifact.++```+verify-charts: 03_market_share.svg | type=bar | calc=ran | svg=updated+verify-charts: 07_growth.svg | type=line | calc=ran | svg=unchanged (already accurate)+verify-charts: 11_share_split.svg | type=pie | calc=ran | svg=updated | marker=added (was missing)+verify-charts: 14_revenue_mix.svg | type=stacked-bar | calc=ran×3 | svg=updated (per Stacked recipe)+verify-charts: 15_unit_economics.svg | type=stacked-area | manual-verify | reason=percent-stacked, recipe does not apply+```++---++## After verification++Continue with post-processing & export ([SKILL.md Step 7](../SKILL.md)):++```bash+python3 skills/ppt-master/scripts/total_md_split.py <project_path>+python3 skills/ppt-master/scripts/finalize_svg.py <project_path>+python3 skills/ppt-master/scripts/svg_to_pptx.py <project_path> -s final+```