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(generate): preserve Quick capabilities and bound workflow audits
hugohe3bb54c96ce4f9
diff --git a/README.md b/README.mdindex 3cf2c8a1..faa14def 100644--- a/README.md+++ b/README.md@@ -322,9 +322,9 @@ The AI handles everything — content analysis, visual design, SVG generation, aYou: Quickly generate a 5-page deck from projects/q3-report/sources/report.pdf — no need to confirm with me```-Whatever you state explicitly is followed; whatever you leave unspecified the agent decides on its own instead of asking. It still converts sources, fills factual gaps, and prepares images/icons/formulas — it drops the strategy and confirmation phase, not the material. There is no `svg_final/` preview in this mode. Full guide → [Quick mode](./docs/getting-started.md#quick-mode).+Whatever you state explicitly is followed; whatever you leave unspecified the agent decides on its own instead of asking. It still converts sources, fills factual gaps, applies the shared visual baseline, and uses images/icons/native shapes/charts/tables/formulas as needed — it drops interaction and durable planning, not presentation capability. It is one-pass and non-resumable, and there is no `svg_final/` preview. Full guide → [Quick mode](./docs/getting-started.md#quick-mode).-> **Output:** The SVG pipeline has one PPTX converter: it reads `svg_output/` and writes a directly editable native DrawingML deck to `exports/<name>_<timestamp>.pptx`. The default Generate flow runs `finalize_svg.py` and produces self-contained previews in `svg_final/`; PowerPoint's manual **Convert to Shape** command is outside the supported contract. Explicit [quick generation](./skills/ppt-master/workflows/profiles/quick-generate.md) skips the Strategist analysis and the confirmation stage: whatever you state explicitly is followed, and whatever you leave unspecified the agent decides directly instead of asking. It still converts sources, researches factual gaps, and prepares required images, icons, formulas, and resource manifests when needed, skips `design_spec.md`, `spec_lock.md`, and `finalize_svg.py`, then hand-authors the SVG pages, passes the lockless Quick final quality check, and exports the final PPTX. Ordinary export capabilities remain available as needed, including native chart/table replacement, notes, motion, narration, and diagnostics; notes, custom object animation, and narration start off, and the agent may enable them when the request or deck needs them. A default-path Quick export writes the normal postflight report and snapshots `svg_output/` to `backup/<timestamp>/svg_output/`; an explicit output path keeps the ordinary no-backup behavior. By default charts and tables export as individually editable SVG-derived DrawingML shapes, which prioritize cross-app visual consistency. Pass `--native-charts-and-tables` to replace eligible groups with PowerPoint-native Chart/Table objects backed by data, which provide **Edit Data** and object-specific controls but may render differently across apps; this variant is saved as `exports/<name>_<timestamp>_native_charts_tables.pptx`. Both chart/table export variants are editable—the distinction is the PowerPoint object model, not editability itself.+> **Output:** The SVG pipeline has one PPTX converter: it reads `svg_output/` and writes a directly editable native DrawingML deck to `exports/<name>_<timestamp>.pptx`. The default Generate flow runs `finalize_svg.py` and produces self-contained previews in `svg_final/`; PowerPoint's manual **Convert to Shape** command is outside the supported contract. Explicit [quick generation](./skills/ppt-master/workflows/profiles/quick-generate.md) skips Strategist, confirmation, `design_spec.md`, `spec_lock.md`, and `finalize_svg.py`: whatever you state explicitly is followed, and whatever you leave unspecified the agent decides directly in one active context. It still converts sources, researches factual gaps, applies shared mode/style/aesthetic guidance, prepares required images/icons/formulas, considers native shapes and data visualizations, hand-authors SVG, passes the lockless Quick final quality check, and exports the final PPTX. It writes no substitute plan and cannot resume after context loss. Ordinary export capabilities remain available as needed, including native chart/table replacement, notes, motion, narration, and diagnostics; notes, custom object animation, and narration start off, and the agent may enable them when the request or deck needs them. A default-path Quick export writes the normal postflight report and snapshots `svg_output/` to `backup/<timestamp>/svg_output/`; an explicit output path keeps the ordinary no-backup behavior. By default charts and tables export as individually editable SVG-derived DrawingML shapes, which prioritize cross-app visual consistency. Pass `--native-charts-and-tables` to replace eligible groups with PowerPoint-native Chart/Table objects backed by data, which provide **Edit Data** and object-specific controls but may render differently across apps; this variant is saved as `exports/<name>_<timestamp>_native_charts_tables.pptx`. Both chart/table export variants are editable—the distinction is the PowerPoint object model, not editability itself.> **Already have a `.pptx` you want to reuse?** Hand the AI that deck plus your material and ask it to "fill this deck with the new content" — it fills text, table, and chart data into your existing design and exports only the pages you pick, staying natively editable. See the [FAQ](./docs/faq.md) and [template-fill workflow](./skills/ppt-master/workflows/template-fill-pptx.md).diff --git a/README_CN.md b/README_CN.mdindex 5aa6b6ec..9b6e5cfd 100644--- a/README_CN.md+++ b/README_CN.md@@ -331,9 +331,9 @@ AI 全程处理——内容分析、视觉设计、SVG 生成、PPTX 导出。你:用 projects/q3-report/sources/report.pdf 快速生成一份 5 页 PPT,不用跟我确认```-你明确提的照做,你没提的由 AI 直接定,不再回来问你。它仍会转换来源、补齐事实、准备图片 / 图标 / 公式——省掉的是策略与确认阶段,不是材料本身。这种模式下不会生成 `svg_final/` 预览。完整说明 → [快速模式](./docs/zh/getting-started.md#快速模式)。+你明确提的照做,你没提的由 AI 直接定,不再回来问你。它仍会转换来源、补齐事实、应用共享视觉基线,并按需使用图片 / 图标 / 原生形状 / 图表 / 表格 / 公式——省掉的是交互与持久规划,不是 PPT 能力。它是不可续接的一次性生成,也不会产生 `svg_final/` 预览。完整说明 → [快速模式](./docs/zh/getting-started.md#快速模式)。-> **输出说明:** SVG 管线统一由项目转换器读取 `svg_output/`,生成可直接编辑的原生 DrawingML `.pptx`,保存至 `exports/<name>_<timestamp>.pptx`。默认 Generate 流程会运行 `finalize_svg.py` 并生成自包含预览 `svg_final/`;PowerPoint 手工“转换为形状”不在支持范围。用户可显式启用[快速生成](./skills/ppt-master/workflows/profiles/quick-generate.md):它跳过策略师分析与确认阶段——你明确提出的要求照做,你没提的由 Agent 直接决定,不再回来问你;仍按需转换来源、研究事实缺口,并准备图片、图标、公式和资源 manifest,跳过 `design_spec.md`、`spec_lock.md` 与 `finalize_svg.py`,随后按规范手写 SVG,通过无锁的 Quick 最终质量检查,再导出最终 PPTX。原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时启用。Quick 使用默认输出路径时仍会生成普通 postflight 报告,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;显式指定输出路径时沿用普通流程不创建备份的行为。图表和表格默认导出为 SVG 派生、可逐形状编辑的 DrawingML 对象,优先保证 PowerPoint / Keynote / WPS 间的视觉一致性;可加 `--native-charts-and-tables`,把符合合同的组替换为带数据源和对象专属编辑能力的 PowerPoint 原生 Chart/Table 对象,跨软件渲染可能略有差异,保存为 `exports/<name>_<timestamp>_native_charts_tables.pptx`。这两种图表/表格导出变体都可编辑,区别在于 PowerPoint 对象模型,而不是“能否编辑”。+> **输出说明:** SVG 管线统一由项目转换器读取 `svg_output/`,生成可直接编辑的原生 DrawingML `.pptx`,保存至 `exports/<name>_<timestamp>.pptx`。默认 Generate 流程会运行 `finalize_svg.py` 并生成自包含预览 `svg_final/`;PowerPoint 手工“转换为形状”不在支持范围。用户可显式启用[快速生成](./skills/ppt-master/workflows/profiles/quick-generate.md):它跳过 Strategist、确认、`design_spec.md`、`spec_lock.md` 与 `finalize_svg.py`——你明确提出的要求照做,你没提的由 Agent 在一次有效上下文中直接决定;仍按需转换来源、研究事实缺口、应用共享 mode / visual style / 美学规范、准备图片 / 图标 / 公式,并考虑原生形状与数据可视化,随后按规范手写 SVG,通过无锁的 Quick 最终质量检查,再导出最终 PPTX。它不写替代计划,上下文丢失后不能续接。原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时启用。Quick 使用默认输出路径时仍会生成普通 postflight 报告,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;显式指定输出路径时沿用普通流程不创建备份的行为。图表和表格默认导出为 SVG 派生、可逐形状编辑的 DrawingML 对象,优先保证 PowerPoint / Keynote / WPS 间的视觉一致性;可加 `--native-charts-and-tables`,把符合合同的组替换为带数据源和对象专属编辑能力的 PowerPoint 原生 Chart/Table 对象,跨软件渲染可能略有差异,保存为 `exports/<name>_<timestamp>_native_charts_tables.pptx`。这两种图表/表格导出变体都可编辑,区别在于 PowerPoint 对象模型,而不是“能否编辑”。> **已有一份想复用的 `.pptx`?** 把那份 deck 连同素材给 AI,说「套模板」即可——它会把新内容(文字、表格、图表数据)填进你现有的设计,只导出你挑选的页面,且保持原生可编辑。详见 [常见问题](./docs/zh/faq.md) 与 [套模板工作流](./skills/ppt-master/workflows/template-fill-pptx.md)。diff --git a/docs/faq.md b/docs/faq.mdindex bd6c2b5c..209e030f 100644--- a/docs/faq.md+++ b/docs/faq.md@@ -77,7 +77,7 @@ Be clear on what this buys you: **web search only finds *a* relevant, downloadab## Q: Can I edit the generated presentations?-Yes. The only PPTX converter in the SVG pipeline is PPT Master's own `svg_output/` → DrawingML conversion. It saves a timestamped native PowerPoint deck to `exports/`, with text, graphics, and colors directly editable as PowerPoint objects. With the default output path, both Default Generate and Quick Generate copy the authored `svg_output/` to `backup/<timestamp>/svg_output/`, so the deck can be rebuilt without re-running the LLM.+Yes. The only PPTX converter in the SVG pipeline is PPT Master's own `svg_output/` → DrawingML conversion. It saves a timestamped native PowerPoint deck to `exports/`, with text, graphics, and colors directly editable as PowerPoint objects. With the default output path, both Default Generate and Quick Generate copy the authored `svg_output/` to `backup/<timestamp>/svg_output/`, so the same authored deck can be re-exported without re-running the LLM. For Quick this is package reconstruction, not a recoverable record of the AI's design decisions.`finalize_svg.py` remains a mandatory Step 7 operation in the default Generate flow even though native PPTX export reads `svg_output/`. It produces self-contained files in `svg_final/` for visual inspection and for manual insertion into another deck as SVG pictures. The explicit quick-generate profile skips this preview artifact, but still retains the normal postflight report and default-path backup after its lockless final quality check. PowerPoint's manual **Convert to Shape** command is not a supported round-trip path; use the generated native PPTX when you need editable shapes.@@ -219,14 +219,16 @@ decides directly and continues, without coming back for approval.** Statenothing, and the agent decides everything. It also skips `finalize_svg.py`, soQuick creates no `svg_final/` preview.-It does not skip preparation. Source conversion, research on identified factual-gaps, and every resource the deck needs still run when required: supplied or-extracted images, AI/web/sliced images, project icons, rendered formulas, and-the required manifests or provenance records. If a required asset is not ready,-it still stops and asks you for it instead of substituting unrelated material.-After preparation, the current agent hand-authors `svg_output/` to the shared-standards, runs the lockless Quick final quality checker, fixes every blocking-error, and only then exports the final PPTX.+It does not skip preparation or design capability. Source conversion, research+on identified factual gaps, shared aesthetic references, and every resource the+deck needs still run when required: supplied or extracted images,+AI/web/sliced images, project icons, native shapes, charts/tables, rendered+formulas, and the required operational manifests or provenance records. If a+required asset is not ready, it still stops and asks you for it instead of+substituting unrelated material. After preparation, the current agent+hand-authors `svg_output/` to the shared standards, runs the lockless Quick+final quality checker, fixes every blocking error, and only then exports the+final PPTX.Ordinary exporter capabilities remain available as needed, including nativechart/table replacement, notes, motion, narration, and diagnostics. Notes,@@ -239,8 +241,10 @@ generation.Because the whole planning phase no longer happens, token usage is materiallylower than the default flow; per-page SVG authoring is the dominant cost of a-run and it does not shrink. So this is a planning shortcut, not a wall-clock or-default-quality-equivalence promise.+run and it does not shrink. Quick keeps the same visual/resource authoring+capabilities and final blocking standard. It does not promise the same design+decisions or wall-clock time as Default because it has no confirmed design+contract, first-page calibration, or resumable decision history.## Q: Will long decks blow out the context window in one shot?diff --git a/docs/getting-started.md b/docs/getting-started.mdindex a85e5bd4..6108ee01 100644--- a/docs/getting-started.md+++ b/docs/getting-started.md@@ -90,9 +90,9 @@ A bare template name or style phrase is still only a design brief. Quick keepsits lockless flat export, so Layout / Deck prototypes guide the authored pagesbut do not compile into reusable native Master / Layout objects.-It does not skip preparation: source conversion, research on identified factual gaps, and image / icon / formula preparation still run as needed. If a required asset is missing, it still stops and asks you for it instead of substituting unrelated material.+It does not skip capabilities: source conversion, research on identified factual gaps, shared aesthetic guidance, and image / icon / native-shape / chart / table / formula preparation and authoring still run as needed. If a required asset is missing, it still stops and asks you for it instead of substituting unrelated material.-Because the whole planning phase no longer happens (Strategist analysis, `design_spec.md` / `spec_lock.md` authoring, the staged confirmation round trip), token usage is materially lower than the default flow. Per-page SVG authoring is unchanged, so this is neither a wall-clock promise nor a promise of quality equivalence with the default flow.+Quick is a one-pass profile, not a shortened resumable workflow. It creates no Strategist record, `design_spec.md`, `spec_lock.md`, or substitute page plan; its content/design/resource decisions exist only in the active AI context. If that context is lost before delivery, start Quick again. Operational manifests, quality reports, postflight, and the cold Python audit log may remain, but they cannot reconstruct why the AI designed the deck that way. The profile reduces interaction and durable planning, not the available presentation toolbox or the intended quality bar.Full guide → [quick-generate profile](../skills/ppt-master/workflows/profiles/quick-generate.md)diff --git a/docs/roadmap.md b/docs/roadmap.mdindex 51a0e23b..c0c7415b 100644--- a/docs/roadmap.md+++ b/docs/roadmap.md@@ -92,8 +92,10 @@ lockless final quality gate, and exports the final PPTX. Because the wholeplanning phase no longer happens — the Strategist reference load, the`design_spec.md` / `spec_lock.md` artifacts, and the staged confirmation roundtrip — its token cost disappears with it, while per-page SVG authoring is-unchanged. It is not a default quality-preserving speed optimization, and it-makes no wall-clock or quality-equivalence promise.+unchanged. It keeps the same visual/resource capabilities and final blocking+standard, but without a confirmed design contract, first-page calibration, or+resumable decision history it does not promise the same design decisions or+wall-clock time as Default.The default Generate pipeline continues to prefer quality over speed.diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 8be1a500..8d33c6d1 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -33,7 +33,7 @@ responsibilities and cannot substitute for one another:| Prompts, templates, and examples | State the project-canonical spelling precisely and reduce drift and warnings at the source | They are not a correctness or safety boundary || `svg_quality_checker.py` | Enforce the project contract on authoring state; errors block and non-blocking warnings pass | It does not silently rewrite pages or guess design intent || `svg_to_pptx.py` | Defensively validate compiler mappings and the package, normalize supported compatible forms, require a current matching final quality report for formal release, and link it into postflight | It does not rerun the complete `svg_quality_checker.py` or treat file creation as proof that the upstream quality gate passed |-| `workflow_transcript.py` / `workflow_log.py` | Automatically mirror project-scoped Python text stdout/stderr and explicitly append important non-Python audit events | They do not interpret output, infer readiness, rerun another tool, or alter the owning tool's result |+| `workflow_transcript.py` / `workflow_log.py` | Record project-scoped Python command envelopes plus bounded material outcomes, and explicitly append important non-Python audit events | They do not retain the full console stream, infer readiness, rerun another tool, or alter the owning tool's result |The automatic recorder resolves the project from `PPT_MASTER_PROJECT_PATH`, apath-bearing argument, or the current working directory, in that order. The@@ -100,7 +100,7 @@ Output:└── <project_name>_<timestamp>_narrated.pptx ← --recorded-narration or --narration-audio-dir variantvalidation/- ├── workflow.log ← Automatic Python-output transcript + important manual audit events+ ├── workflow.log ← Compact Python command/outcome audit + important manual audit events├── svg_quality_report.json ← Blocking/introduced/inherited/source-import SVG findings└── <output_stem>.report.json ← Postflight package/resource audit linked to the final SVG quality report@@ -115,16 +115,18 @@ the inputs or resources needed to build the deck:```textSource material or topic-> convert/read sources and research identified factual gaps as needed- -> decide content, page structure, visual system, and resources in active context- -> prepare required images/icons/formulas and resource manifests+ -> resolve mode/style and decide content, page structure, and carriers in active context+ -> prepare selected images/icons/formulas and operational manifests-> hand-author svg_output/ under the shared SVG standards+ -> verify data-driven chart coordinates when present-> svg_quality_checker.py --quick-generate --stage final --json-> svg_to_pptx.py --quick-generate-> exports/<name>_<timestamp>.pptx```These decisions are made automatically by the current agent without Strategist,-Confirm UI, `design_spec.md`, or `spec_lock.md`.+Confirm UI, `design_spec.md`, `spec_lock.md`, or a substitute plan. They cannot+be reconstructed or resumed after the active context is lost.In the default flow, without an explicit `-o`, the native-object and narrationflags may combine into@@ -205,9 +207,12 @@ Post-processing scripts convert supported SVG vector elements to DrawingML. Textneeded by the deck, but skips the separate Strategist planning/confirmationphase, first-page gate, and `finalize_svg.py`. The current agent follows everyexplicit user requirement and makes the remaining content, page, visual, and-resource decisions automatically in active context, then authors under the-shared SVG standards, runs one lockless final quality gate, and uses the same-DrawingML converter and postflight.+resource decisions automatically in one active context. It resolves a mode and+visual style, considers the complete image/icon/native-shape/chart/table/formula+carrier menu, then authors under the shared SVG standards, runs any selected+capability-specific preparation, passes one lockless final quality gate, and+uses the same DrawingML converter and postflight. It writes no substitute plan+or resumable design history; context loss restarts the Quick run.---@@ -236,9 +241,10 @@ design_spec.md + spec_lock.md + images/ + icons/ + templates/Quick Generate:source material or topic└─> conversion/read + factual-gap research [as needed]- └─> active-context content/page/visual/resource decisions+ └─> active-context mode/style + content/page/carrier decisions└─> images/ + icons/ + formula/resource manifests [as needed]└─> hand-authored svg_output/+ ├─> verify-charts [only for data-driven chart geometry]└─> svg_quality_checker.py --quick-generate --stage final --json└─> svg_to_pptx.py --quick-generate -> exports/*.pptx+ validation/<output_stem>.report.json@@ -315,14 +321,16 @@ Two converter design choices still shape the system:`project_manager.py init` creates the standard project working directories;`--quick-generate` creates `svg_output/` plus the cold-`validation/workflow.log` transcript, omits the project README, and leaves+`validation/workflow.log` audit log, omits the project README, and leavesother directories on demand. The explicit[`quick-generate`](../skills/ppt-master/workflows/profiles/quick-generate.md)profile omits planning artifacts and `svg_final/`, but its project may stillcontain converted sources, analysis, images, icons, rendered formulas, andrequired resource manifests. It hand-authors `svg_output/`, writes a locklessfinal quality report, and retains the ordinary postflight and default-path-backup around the final PPTX. The default delivery lifecycle is:+backup around the final PPTX. The audit log and reports preserve tool outcomes,+not the AI's design reasoning or a resumable stage state. The default delivery+lifecycle is:| Directory | Role ||---|---|@@ -335,7 +343,7 @@ backup around the final PPTX. The default delivery lifecycle is:| `svg_final/` | mandatory normal-flow derived visual-preview SVGs; supported bitmap/SVG resources are inlined when possible, while EMF/WMF retain an external-reference exception; used for IDE/browser preview or manual insertion as SVG pictures || `live_preview/` | preview server state, edit history, and annotation logs || `notes/` | `total.md` and split per-slide speaker notes |-| `validation/` | cold workflow transcript, SVG quality reports, and PPTX postflight audit reports |+| `validation/` | cold workflow audit log, SVG quality reports, and PPTX postflight audit reports || `exports/` | timestamped native PPTX deliverables || `backup/<timestamp>/` | default export creates the timestamped directory, then attempts a frozen `svg_output/` copy; copy failure does not fail export, but directory-creation failure is not currently downgraded |@@ -353,7 +361,7 @@ These invariants are stronger than ordinary implementation preferences. If a cha|---|---|| `sources/` content-type files are the Generate content contract | text, tables, and chart values come from content-type files in `sources/` (Markdown is primary, but `.txt` / `.csv` / `.json` / `.yaml` / … count too); known sidecars (`*.conversion_profile.json`, `*_files/image_manifest.json`) are excluded || `analysis/` stores machine facts, not design contracts | `source_profile.json` and intake artifacts inform Strategist in the default pipeline and the current agent in `quick-generate`; they do not lock page count/order except in workflows that say so |-| `design_spec.md` explains the design; `spec_lock.md` executes it in the default pipeline | both remain owning artifacts there; `quick-generate` persists neither, and the current agent follows explicit user requirements while keeping every remaining content, page, visual, and resource decision in active context |+| `design_spec.md` explains the design; `spec_lock.md` executes it in the default pipeline | both remain owning artifacts there; `quick-generate` persists neither or any substitute plan, and the current agent follows explicit user requirements while keeping every remaining content, page, visual, and resource decision only in active context; context loss restarts Quick || Planning context is retained until invalidated | continuous execution reuses the complete Design Spec, lock, and triggered references; fresh/resumed/restarted or compacted execution reloads them once || `page-context` is on demand | the read-only projector supports diagnostics, deterministic routing checks, and optional usage telemetry; it is not a pre-page gate || `svg_output/` is the only hand-authored SVG directory | quality checks, manual edits, re-export, and `update_spec.py` target authored source |@@ -474,7 +482,7 @@ evidence. In particular, enabling narration may enable the effective SpeakerNotes outcome in the Design Spec, but it never rewrites the raw speaker-noteschoice.-**Image analysis is metadata-first, with a narrow visual fallback.** When images exist, `analyze_images.py` supplies the regenerated measured facts in `analysis/image_analysis.csv`; the CSV is a view over the live `images/` folder, not a durable cache. In the default pipeline, Strategist first resolves supplied images from source placement and nearby prose, captions / alt text / titles, filenames, user notes, existing resource records, and that metadata. It may inspect one specific image only when a material ambiguity remains about selection, factual identity, page role, crop safety, or focal placement—never as a bulk inventory scan. The answer is written into Design Spec §VIII, after which Executor uses the plan and measured geometry without reopening source pixels for semantic discovery. In `quick-generate`, the current agent applies the same bounded analysis while automatically preparing the resource roster in active context; no Design Spec projection is written. User images, extracted images, web images, AI outputs, formulas, and sliced elements still converge into the same measured fact table.+**Image analysis is metadata-first, with a narrow visual fallback.** When images exist, `analyze_images.py` supplies the regenerated measured facts in `analysis/image_analysis.csv`; the CSV is a view over the live `images/` folder, not a durable cache. In the default pipeline, Strategist first resolves supplied images from source placement and nearby prose, captions / alt text / titles, filenames, user notes, existing resource records, and that metadata. It may inspect one specific image only when a material ambiguity remains about selection, factual identity, page role, crop safety, or focal placement—never as a bulk inventory scan. The answer is written into Design Spec §VIII, after which Executor uses the plan and measured geometry without reopening source pixels for semantic discovery. In `quick-generate`, the current agent applies the same bounded analysis while preparing the selected resources from active-context decisions; no Design Spec projection or general resource roster is written. User images, extracted images, web images, AI outputs, formulas, and sliced elements still converge into the same measured fact table.**Retained planning context** carries continuity; the on-demand page projector is only a diagnostic described below.@@ -529,28 +537,31 @@ Strategist and confirmation layer; it does not remove preparation.| Cook | Executor | Uses only prepared project-local assets and realizes the plan through geometry, composition, hierarchy, spacing, and treatment without changing the selected “dish” or acquiring/substituting ingredients; chooses suitable prepared icons per page and may adapt fields explicitly labeled as suggestions or References || Quality inspector | `svg_quality_checker.py` | Reads authoring state and reports contract findings; it does not edit pages, own the page roster, or package the deck || Packager | `svg_to_pptx.py` | After a matching final report passes, compiles the authored SVG, validates the package, and publishes the receipt; it does not repair SVG or rerun the checker |-| Run recorder | `workflow_transcript.py`, `workflow_log.py`, and `validation/workflow.log` | Automatically mirrors project-scoped Python text stdout/stderr and accepts explicitly selected important non-Python events; it does not decide what the output means or whether the workflow may advance |+| Run recorder | `workflow_transcript.py`, `workflow_log.py`, and `validation/workflow.log` | Records Python command envelopes, material tagged outcomes, bounded status samples, and omission counts, then accepts explicitly selected important non-Python events; it does not decide whether the workflow may advance |**Quick generation collapses planning into the current agent.** Source conversion,factual-gap research, and resource preparation still run when needed. The agent-automatically selects the content, page roster, visual system, and resource-needs in active context, prepares supplied/extracted/AI/web/sliced images,-icons, and formulas with their required manifests or provenance records, and-then hand-authors SVG. It does not invoke Strategist, Confirm UI,-`design_spec.md`, or `spec_lock.md`.+automatically selects the content, page roster, mode, visual style, and resource+needs in active context; scans images, icons, native shapes, charts/tables,+formulas, and simple typography/geometry as available carriers; prepares the+selected supplied/extracted/AI/web/sliced images, icons, and formulas with their+required operational manifests or provenance records; and then hand-authors+SVG. It does not invoke Strategist, Confirm UI, `design_spec.md`,+`spec_lock.md`, or a substitute planning artifact. These decisions are not+recoverable after context loss.One agent may therefore perform several creative stages in sequence, but theirownership boundaries do not merge; checker, exporter, and transcript recorderremain separate deterministic tools.**Default preparation has two clocks.** Topic Research supplies facts before final confirmation: it starts immediately for topic-only input, or after supplied material is converted/read when planning-critical factual gaps remain. It supplements only those gaps and acquires no images. When the current AI editor provides an isolated worker with web/fetch access and write access to the declared outputs, the main agent defines the gaps and the worker writes the existing research/provenance artifacts, returning only a receipt; otherwise research runs in the main context. AI / web / slice image acquisition runs only after final confirmation and the completed `design_spec.md §VIII` / `spec_lock.md`, then reaches a terminal status before Executor starts. Strategist also resolves, syncs, and validates a curated project icon pool while authoring the final plan. Image_Generator, Image_Searcher, and icon-sync tooling are preparation mechanisms under Strategist ownership, not independent decision owners. Quick generation uses those preparation mechanisms as needed under the current agent's in-context decisions, without inserting a confirmation gate.-**Prepared project-local assets are the boundary.** In the default pipeline, images and other declared resources remain available only when Strategist has selected them, recorded them in the planning artifacts, and made their project paths resolvable or explicitly `Needs-Manual`. Icons are prepared when their SVG files exist under `<project>/icons/`; `spec_lock.icons.inventory` indexes the Strategist's curated synced bundled pool but neither assigns page usage nor exhaustively whitelists execution. Executor chooses among prepared icons per page. In quick generation, the active-context resource roster and its project-local files/manifests replace that planning projection; the current agent may acquire and prepare those resources before SVG authoring. Files elsewhere on disk are not authorized. Missing material returns to the owning preparation step; SVG authoring never silently substitutes it.+**Prepared project-local assets are the boundary.** In the default pipeline, images and other declared resources remain available only when Strategist has selected them, recorded them in the planning artifacts, and made their project paths resolvable or explicitly `Needs-Manual`. Icons are prepared when their SVG files exist under `<project>/icons/`; `spec_lock.icons.inventory` indexes the Strategist's curated synced bundled pool but neither assigns page usage nor exhaustively whitelists execution. Executor chooses among prepared icons per page. In quick generation, active-context resource decisions and their project-local files/manifests replace that planning projection; no general roster or page assignment is written. The current agent may acquire and prepare those resources before SVG authoring. Files elsewhere on disk are not authorized. Missing material returns to the owning preparation step; SVG authoring never silently substitutes it.**Specificity controls freedom.** “Make Mapo tofu” fixes the result's identity: technique and presentation may vary, but tomato-and-eggs or tofu soup is a substitution. “Make a tofu dish” leaves an in-class choice. In the default pipeline, Strategist may resolve that choice; if the Design Spec deliberately leaves a dimension broad, Executor may realize it within that envelope. Once the Design Spec names a binding choice, execution cannot reopen it. In quick generation, the current agent resolves the equivalent choice in active context and keeps it stable while authoring. Fields explicitly labeled as suggestions or References—including a preferred page-local image pattern—remain expression guidance that may be adapted without changing content, resources, identity, or explicit constraints.**Garnish remains local.** Sparse page-local font or color accents may add hierarchy, differentiation, or atmosphere without becoming a second visual system. In the default pipeline, structural/recurring fonts, palette roles, resources, or recurring cross-page identity patterns remain Strategist decisions and require an upstream Design Spec/lock update before reuse; in quick generation, the current agent establishes those anchors in active context and preserves them across pages. A default-pipeline page-local §VIII image pattern remains a preferred composition reference.-**Prompt-refactor invariant.** In the default pipeline, compression must preserve initial materials, user confirmation, Strategist-owned preparation, planning ownership, and execution freedom as separate layers. Moving acquisition into Executor, turning permission into quota, flexible realization into silent resource/identity reselection, or an exact binding plan into an approximate target is a semantic regression. The explicit quick profile consolidates the first layers under the current agent; it does not erase source or resource work. Default runtime authority lives in [`strategist.md`](../skills/ppt-master/references/strategist.md) and [`executor-base.md`](../skills/ppt-master/references/executor-base.md); Quick runtime authority starts at [`quick-generate.md`](../skills/ppt-master/workflows/profiles/quick-generate.md) and conditionally loads the same resource references. Prompt-writing governance lives in [`prompt-style.md`](./rules/prompt-style.md).+**Prompt-refactor invariant.** In the default pipeline, compression must preserve initial materials, user confirmation, Strategist-owned preparation, planning ownership, and execution freedom as separate layers. Moving acquisition into Executor, turning permission into quota, flexible realization into silent resource/identity reselection, or an exact binding plan into an approximate target is a semantic regression. The explicit quick profile consolidates the first layers under the current agent; it does not erase source, resources, aesthetics, data visualization, or native-shape capability. Default runtime authority lives in [`strategist.md`](../skills/ppt-master/references/strategist.md) and [`executor-base.md`](../skills/ppt-master/references/executor-base.md); Quick runtime authority starts at [`quick-generate.md`](../skills/ppt-master/workflows/profiles/quick-generate.md) and directly loads the applicable shared and conditional execution references without inheriting Default's persisted-plan prerequisites. Prompt-writing governance lives in [`prompt-style.md`](./rules/prompt-style.md).---@@ -660,13 +671,14 @@ The post-processing and export stages keep authoring, validation, preview, deliv| `backup/<ts>/svg_output/` (default output path only; copy is best-effort after directory creation) | re-export from frozen SVG sources without rerunning the LLM | after successful conversion the exporter creates the backup directory and attempts the copy; explicit `-o` creates none, copy failure does not block export, prints a warning outside quiet mode, and leaves postflight `backup_path` empty, while directory-creation failure remains fatal |Validation JSON files and `validation/workflow.log` are cold audit artifacts,-not routine model inputs. The workflow transcript is opened only when the user-explicitly requests a run review. It can reconstruct observed commands and-their text output, plus selected non-Python details such as a material stage-handoff or rework reason, user-approved exception, or manual recovery choice.-These manual entries are optional and never duplicate artifacts, routine-progress, or private reasoning; current artifacts still establish the stage-and readiness. The+not routine model inputs. The workflow log is opened only when the user+explicitly requests a run review. It reconstructs observed commands and a+bounded material outcome selection—not the complete console stream—plus+selected non-Python details such as a material stage handoff or rework reason,+user-approved exception, or manual recovery choice. Each command footer reports+how many output lines were retained or omitted. These manual entries are+optional and never duplicate artifacts, routine progress, or private reasoning;+current artifacts still establish the stage and readiness. Theexporter reads the SVG quality report programmatically and, in the defaultnon-quiet flow, prints a compact `[POSTFLIGHT]` receipt with the status,quality-gate result, Slide count, warning-category counts, and artifact paths.diff --git a/docs/zh/faq.md b/docs/zh/faq.mdindex 1704a75d..7e77d124 100644--- a/docs/zh/faq.md+++ b/docs/zh/faq.md@@ -79,7 +79,7 @@ python3 skills/ppt-master/scripts/update_repo.py## Q: 生成的 PPT 可以编辑吗?-可以。SVG 管线统一由项目转换器读取 `svg_output/` 并生成原生 DrawingML `.pptx`;文字、图形和颜色无需额外转换即可编辑,文件以时间戳命名保存至 `exports/`。使用默认输出路径时,Default Generate 与 Quick Generate 都会把作者源 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重建 PPTX,无需再走 LLM。+可以。SVG 管线统一由项目转换器读取 `svg_output/` 并生成原生 DrawingML `.pptx`;文字、图形和颜色无需额外转换即可编辑,文件以时间戳命名保存至 `exports/`。使用默认输出路径时,Default Generate 与 Quick Generate 都会把作者源 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重新导出 PPTX,无需再走 LLM。对 Quick 而言,这只是包重建,不是可恢复的 AI 设计决策记录。默认 Generate 流程的 Step 7 仍会强制生成 `svg_final/`。其中每页都是自包含的视觉预览 SVG,可直接在浏览器或 IDE 中打开,也可作为 SVG 图片手动插入 PowerPoint;显式快速生成会跳过这项预览产物,但在无锁最终质量检查通过后,仍保留普通 postflight 报告和默认输出路径下的备份。项目只保证 `svg_final/` 作为预览或图片显示,不保证 PowerPoint 手工“转换为形状”后的结果。需要可编辑形状时,请使用 `exports/` 中由项目转换器生成的原生 PPTX。@@ -210,11 +210,11 @@ python3 skills/ppt-master/scripts/svg_to_pptx.py <project> -a auto --animation-t**它跳过的是策略师分析、`design_spec.md` / `spec_lock.md` 落盘和分步确认停顿:你明确提出的要求照做;你没提的,当前 Agent 直接决定并继续,不再回来征求同意。** 什么都不提,才是全部由 Agent 决定。它同时跳过 `finalize_svg.py`,因此不生成 `svg_final/` 预览。-它不跳过备料:来源转换、已识别事实缺口的研究,以及生成 deck 所需的资源仍按需准备——用户提供或源文件抽取的图片、AI / 网络 / 切片图片、项目图标、渲染公式,以及对应的必要 manifest 或来源记录。必需素材未就绪时它仍会停下来跟你要,不会拿无关材料顶替。备料完成后,当前 Agent 按共享规范手写 `svg_output/`,运行无锁的 Quick 最终质量检查并修复所有阻塞错误,之后才导出最终 PPTX。+它不跳过备料或设计能力:来源转换、已识别事实缺口的研究、共享美学参考,以及生成 deck 所需的资源仍按需准备——用户提供或源文件抽取的图片、AI / 网络 / 切片图片、项目图标、原生形状、图表 / 表格、渲染公式,以及对应的必要运行 manifest 或来源记录。必需素材未就绪时它仍会停下来跟你要,不会拿无关材料顶替。备料完成后,当前 Agent 按共享规范手写 `svg_output/`,运行无锁的 Quick 最终质量检查并修复所有阻塞错误,之后才导出最终 PPTX。原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时自动启用,不会打开确认流程。使用默认输出路径时会生成普通 postflight 报告,并把 `svg_output/` 备份到 `backup/`;显式指定输出路径时沿用普通流程不创建备份的行为。页数本身既不会自动触发,也不会阻止快速生成。-由于整个规划阶段不再发生,token 消耗明显低于默认流程;逐页 SVG 生成是一次 run 的主要开销,这部分并不减少。因此它是规划阶段的短路,不承诺具体耗时,也不承诺与默认流程质量等价。+由于整个规划阶段不再发生,token 消耗明显低于默认流程;逐页 SVG 生成是一次 run 的主要开销,这部分并不减少。Quick 保留同一套视觉 / 资源创作能力和最终阻塞标准,但没有已确认的设计契约、首屏校准或可恢复的决策历史,因此不承诺与 Default 作出相同设计,也不承诺具体耗时。## Q: 长 PPT 一次生成会不会上下文爆掉?diff --git a/docs/zh/getting-started.md b/docs/zh/getting-started.mdindex 80958663..cc00d4d9 100644--- a/docs/zh/getting-started.md+++ b/docs/zh/getting-started.md@@ -89,9 +89,9 @@ Brand / Style / Layout / Deck 工作区 root,它会直接校验、安装并使Quick 保持无锁 flat 导出,因此 Layout / Deck 原型会指导页面创作,但不会编译成可复用的原生 Master / Layout 对象。-它不跳过备料:来源转换、事实缺口研究、图片 / 图标 / 公式准备仍按需运行。必需素材缺失时它会停下来跟你要,不会拿无关材料顶替。+它不跳过能力:来源转换、事实缺口研究、共享美学规范,以及图片 / 图标 / 原生形状 / 图表 / 表格 / 公式的准备和创作仍按需运行。必需素材缺失时它会停下来跟你要,不会拿无关材料顶替。-整个规划阶段不再发生(策略师分析、`design_spec.md` / `spec_lock.md` 落盘、分步确认往返),因此 token 消耗明显低于默认流程;逐页 SVG 生成的开销不变,所以这既不是耗时承诺,也不承诺与默认流程质量等价。+快速模式是一次性生成,不是缩短后的可续接流程。它不产生 Strategist 记录、`design_spec.md`、`spec_lock.md` 或替代性的页面计划;内容、设计和资源决策只存在于 AI 的当前上下文。交付前一旦丢失该上下文,就重新运行 Quick。资源 manifest、质量报告、postflight 与冷 Python 审计日志可以保留,但无法还原 AI 为什么这样设计。该 profile 省掉的是交互和持久规划,不是 PPT 能力或预期质量标准。完整说明 → [快速模式 profile](../../skills/ppt-master/workflows/profiles/quick-generate.md)diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.mdindex 39caaf72..da8a69c5 100644--- a/docs/zh/roadmap.md+++ b/docs/zh/roadmap.md@@ -86,7 +86,7 @@ Generate PPTX 路线围绕完全可控的新形状、文字与版式创作。结会做:通过 prompt 精简 / 缓存命中率提升带来的间接改善。-显式 `quick-generate` 是用户主动选择的工作流短路:它跳过 Strategist、确认和首屏 gate,随后创作 SVG、运行一次无锁最终质量门,再导出最终 PPTX。由于整个规划阶段不再发生——Strategist 系 reference 的加载、`design_spec.md` / `spec_lock.md` 的写入、分步确认往返——这部分 token 开销随之消失,而逐页 SVG 创作的开销不变。它不是默认流程的保质提速,也不承诺具体耗时或与默认流程质量等价。+显式 `quick-generate` 是用户主动选择的工作流短路:它跳过 Strategist、确认和首屏 gate,随后创作 SVG、运行一次无锁最终质量门,再导出最终 PPTX。由于整个规划阶段不再发生——Strategist 系 reference 的加载、`design_spec.md` / `spec_lock.md` 的写入、分步确认往返——这部分 token 开销随之消失,而逐页 SVG 创作的开销不变。它保留同一套视觉 / 资源能力和最终阻塞标准,但没有已确认的设计契约、首屏校准或可恢复的决策历史,因此不承诺与 Default 作出相同设计,也不承诺具体耗时。默认 Generate 流程仍坚持质量优先。diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 62ebd5f7..21768305 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -32,7 +32,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使| 提示词、模板与示例 | 精确表达项目规范写法,从源头减少偏差和 warning | 不作为正确性或安全边界 || `svg_quality_checker.py` | 在作者状态上执行项目合同;error 阻塞,非阻塞 warning 放行 | 不静默改写页面,也不猜测设计意图 || `svg_to_pptx.py` | 对编译映射与 package 执行防御校验;归一化已支持的兼容形式;正式发布前要求当前匹配的 final 质量报告,并把它关联进 postflight | 不重跑完整 `svg_quality_checker.py`,也不以“文件已生成”替代前置质量门 |-| `workflow_transcript.py` / `workflow_log.py` | 自动转录项目级 Python 工具的文本 stdout/stderr,并显式追加重要的非 Python 审计事项 | 不解释输出、推断就绪状态、重跑其他工具,也不改变所属工具的结果 |+| `workflow_transcript.py` / `workflow_log.py` | 记录项目级 Python 命令信封与有限的重要结果,并显式追加重要的非 Python 审计事项 | 不保留完整控制台输出、不推断就绪状态、不重跑其他工具,也不改变所属工具的结果 |自动记录器依次从 `PPT_MASTER_PROJECT_PATH`、带路径的命令参数和当前工作目录解析项目。只有不携带项目路径、以 stdout 为主要输出的 helper 才需要在同一条 Python 命令前设置该环境信号;它不会再启动包装进程。@@ -89,7 +89,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使└── <project_name>_<timestamp>_narrated.pptx ← --recorded-narration 或 --narration-audio-dir 变体validation/- ├── workflow.log ← 自动 Python 输出转录与重要人工审计事项+ ├── workflow.log ← 精简的 Python 命令/结果审计与重要人工审计事项├── svg_quality_report.json ← blocking / introduced / inherited / source-import 分类结果└── <output_stem>.report.json ← 关联最终 SVG 质量报告的 package / 资源审计@@ -103,16 +103,17 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使```text来源材料或主题-> 按需转换 / 阅读来源,并研究已识别的事实缺口- -> 在当前上下文决定内容、页结构、视觉系统和资源- -> 准备所需图片 / 图标 / 公式与资源 manifest+ -> 在当前上下文解析 mode / style,并决定内容、页结构和载体+ -> 准备实际选中的图片 / 图标 / 公式与操作 manifest-> 按共享 SVG 规范手写 svg_output/+ -> 存在数据驱动图表时校准坐标-> svg_quality_checker.py --quick-generate --stage final --json-> svg_to_pptx.py --quick-generate-> exports/<name>_<timestamp>.pptx```这些决策由当前 Agent 自动完成,不进入 Strategist、Confirm UI、-`design_spec.md` 或 `spec_lock.md`。+`design_spec.md`、`spec_lock.md` 或替代计划。有效上下文丢失后无法重建或续接。默认流程未显式指定 `-o` 时,native 与 narration 标记可以组合成`<project_name>_<timestamp>_native_charts_tables_narrated.pptx`;显式 `-o`@@ -188,7 +189,7 @@ Executor 角色逐页生成演示文稿的视觉内容,输出为 SVG 文件。**第三阶段:工程化转换**后处理脚本将受支持的 SVG 向量元素转换为 DrawingML。文本和向量形状会保持为 PowerPoint 原生对象——可点击、可编辑、可改样式;位图资源则复制为 PPT picture media,而不是把整页压平成一张图片。-`quick-generate` 保留 deck 所需的来源理解与资源准备,但跳过独立的 Strategist 规划 / 确认阶段、首屏 gate 与 `finalize_svg.py`。当前 Agent 照做用户明确提出的要求,并在有效上下文中自动完成其余的内容、页结构、视觉和资源决策,随后仍按共享 SVG 规范创作,运行一次无锁最终质量门,并使用同一个 DrawingML 转换器与 postflight。+`quick-generate` 保留 deck 所需的来源理解与资源准备,但跳过独立的 Strategist 规划 / 确认阶段、首屏 gate 与 `finalize_svg.py`。当前 Agent 照做用户明确提出的要求,并在一次有效上下文中自动完成其余的内容、页结构、mode、visual style 与资源决策;图片、图标、原生形状、图表 / 表格、公式和纯字体 / 几何都进入同一轮载体判断。随后仍按共享 SVG 规范创作,执行已选能力所需的准备,通过一次无锁最终质量门,并使用同一个 DrawingML 转换器与 postflight。它不写替代计划或可续接的设计历史;上下文丢失后重新运行 Quick。---@@ -217,9 +218,10 @@ design_spec.md + spec_lock.md + images/ + icons/ + templates/Quick Generate:来源材料或主题└─> 转换 / 阅读 + 事实缺口研究 [按需]- └─> 当前上下文中的内容 / 页结构 / 视觉 / 资源决策+ └─> 当前上下文中的 mode / style + 内容 / 页结构 / 载体决策└─> images/ + icons/ + 公式 / 资源 manifest [按需]└─> 手写 svg_output/+ ├─> verify-charts [仅数据驱动图表几何]└─> svg_quality_checker.py --quick-generate --stage final --json└─> svg_to_pptx.py --quick-generate -> exports/*.pptx+ validation/<output_stem>.report.json@@ -295,13 +297,14 @@ SVG 也是唯一同时满足流程中所有角色需要的格式:**AI 能可## 项目结构与生命周期`project_manager.py init` 默认创建标准项目工作目录;使用-`--quick-generate` 时创建 `svg_output/` 与冷转录+`--quick-generate` 时创建 `svg_output/` 与冷审计日志`validation/workflow.log`,省略项目 README,其他目录按需产生。显式[`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md)profile 省略规划产物与 `svg_final/`,但项目中仍可按需存在已转换来源、分析结果、图片、图标、渲染公式及必要资源 manifest;它会手写 `svg_output/`,生成无锁最终-质量报告,并围绕最终 PPTX 保留普通 postflight 与默认路径备份。默认交付生命周期如下:+质量报告,并围绕最终 PPTX 保留普通 postflight 与默认路径备份。审计日志和报告只保留+工具结果,不记录 AI 的设计理由,也不构成可续接的阶段状态。默认交付生命周期如下:| 目录 | 职责 ||---|---|@@ -314,7 +317,7 @@ profile 省略规划产物与 `svg_final/`,但项目中仍可按需存在已| `svg_final/` | 强制派生的视觉预览 SVG;尝试内联受支持位图 / SVG,保留 EMF/WMF 外链例外;服务 IDE / 浏览器,也可手动作为 SVG 图片插入 PowerPoint || `live_preview/` | 预览服务状态、直接编辑历史和注解日志 || `notes/` | `total.md` 与拆分后的逐页讲稿 |-| `validation/` | 冷流程转录、SVG 质量报告与 PPTX postflight 审计报告 |+| `validation/` | 冷流程审计日志、SVG 质量报告与 PPTX postflight 审计报告 || `exports/` | 带时间戳的 native PPTX 交付物 || `backup/<timestamp>/` | 默认导出先创建时间戳目录,再尝试复制冻结的 `svg_output/`;复制失败不令导出失败,但目录创建失败当前不会降级处理 |@@ -332,7 +335,7 @@ CLI 支持 `--move`、`--copy` 和自动默认,但共享同一条固定的所|---|---|| `sources/` 内容型文件是 Generate 内容契约 | 文本、表格和图表数值来自 `sources/` 内容型文件(Markdown 为主,`.txt` / `.csv` / `.json` / `.yaml` 等同样计入);已知 sidecar(`*.conversion_profile.json`、`*_files/image_manifest.json`)排除在外 || `analysis/` 存机器事实,不存设计契约 | `source_profile.json` 和 intake artifact 在默认流程中辅助 Strategist,在 `quick-generate` 中辅助当前 Agent;除非工作流明确规定,否则不锁定页数 / 页序 |-| 默认流程由 `design_spec.md` 解释设计、`spec_lock.md` 执行设计 | 两者在默认流程中始终是权威产物;`quick-generate` 不落盘二者,用户明确提出的要求照做,其余内容、页结构、视觉和资源决策由当前 Agent 保留在上下文中 |+| 默认流程由 `design_spec.md` 解释设计、`spec_lock.md` 执行设计 | 两者在默认流程中始终是权威产物;`quick-generate` 不落盘二者或任何替代计划,用户明确提出的要求照做,其余内容、页结构、视觉和资源决策只由当前 Agent 保留在上下文中;上下文丢失后重新运行 Quick || 规划上下文有效时持续复用 | 连续执行直接使用完整 Design Spec、lock 与已触发引用;fresh/resumed/restarted 或压缩后才重新读取一次 || `page-context` 按需调用 | 只读投影器用于诊断、确定性路由检查和可选的用量统计,不是逐页门禁 || `svg_output/` 是唯一手写 SVG 目录 | 质量检查、手工编辑、重导出和 `update_spec.py` 都面向作者源 |@@ -420,7 +423,7 @@ Stage-1 沟通推荐的编写不得读取这些候选或任何模板内容。UI尤其是,启用旁白可以在 Design Spec 中启用 Speaker Notes 的最终有效结果,但绝不会改写原始的备注选择。-**图片分析以重算元数据为先,只保留小范围视觉兜底。** 当项目里存在图片时,`analyze_images.py` 把可度量事实重算到 `analysis/image_analysis.csv`;该 CSV 是实时 `images/` 目录的派生视图,不是持久缓存。默认流程中,Strategist 先根据图片在源文中的位置与前后文、图注 / alt / 标题、文件名、用户说明、已有资源记录和这些元数据判断。只有当某一张具体图片在选用、事实身份、页面角色、裁剪安全或焦点放置上仍有实质歧义时,才可单独查看它,绝不得扫描整个图片目录。结论写入 Design Spec §VIII 后,Executor 只消费该计划与几何数据,不会重新打开源图进行语义探索。`quick-generate` 则由当前 Agent 在上下文中自动准备资源清单时采用同样的有界分析,不写 Design Spec 投影。用户图、抽取图、网络图、AI 图、公式图和切片图仍统一汇入同一张可度量事实表。+**图片分析以重算元数据为先,只保留小范围视觉兜底。** 当项目里存在图片时,`analyze_images.py` 把可度量事实重算到 `analysis/image_analysis.csv`;该 CSV 是实时 `images/` 目录的派生视图,不是持久缓存。默认流程中,Strategist 先根据图片在源文中的位置与前后文、图注 / alt / 标题、文件名、用户说明、已有资源记录和这些元数据判断。只有当某一张具体图片在选用、事实身份、页面角色、裁剪安全或焦点放置上仍有实质歧义时,才可单独查看它,绝不得扫描整个图片目录。结论写入 Design Spec §VIII 后,Executor 只消费该计划与几何数据,不会重新打开源图进行语义探索。`quick-generate` 则由当前 Agent 根据当前上下文决策准备实际选中的资源,并采用同样的有界分析;不写 Design Spec 投影或通用资源清单。用户图、抽取图、网络图、AI 图、公式图和切片图仍统一汇入同一张可度量事实表。**保留的规划上下文**负责跨页连续性;按需逐页投影只承担下文所述的诊断用途。@@ -473,20 +476,20 @@ Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workfl| 厨师 | Executor | 只使用项目中已备好的材料,以几何、构图、层级、间距和视觉处理实现方案;不得改变所选“菜品”,也不得自行找料、换料;按页选择适合的已备图标,并可调整明确标为 suggestion 或 Reference 的字段 || 质检员 | `svg_quality_checker.py` | 只读取作者状态并报告合同问题;不改页面、不拥有页面清单,也不打包 deck || 打包员 | `svg_to_pptx.py` | 匹配的 final 报告通过后,编译已创作 SVG、校验 package 并发布回执;不修 SVG,不重跑 Checker |-| 运行记录员 | `workflow_transcript.py`、`workflow_log.py` 与 `validation/workflow.log` | 自动转录项目级 Python 工具的文本 stdout/stderr,并接收显式选定的重要非 Python 事项;不解释输出,也不决定流程是否可以前进 |+| 运行记录员 | `workflow_transcript.py`、`workflow_log.py` 与 `validation/workflow.log` | 记录 Python 命令信封、重要标记结果、有限状态样本和省略计数,并接收显式选定的重要非 Python 事项;不决定流程是否可以前进 |-**快速生成把规划职责合并到当前 Agent。** 来源转换、事实缺口研究和资源准备仍按需运行。当前 Agent 在上下文中自动选择内容、页面清单、视觉系统和资源需求,准备用户提供 / 来源抽取 / AI / 网络 / 切片图片、图标和公式及其必要 manifest 或来源记录,随后手写 SVG;不进入 Strategist、Confirm UI、`design_spec.md` 或 `spec_lock.md`。+**快速生成把规划职责合并到当前 Agent。** 来源转换、事实缺口研究和资源准备仍按需运行。当前 Agent 在上下文中自动选择内容、页面清单、mode、visual style 和资源需求;把图片、图标、原生形状、图表 / 表格、公式与纯字体 / 几何作为完整载体菜单进行一次判断;准备实际选中的用户提供 / 来源抽取 / AI / 网络 / 切片图片、图标和公式及其必要操作 manifest 或来源记录,随后手写 SVG;不进入 Strategist、Confirm UI、`design_spec.md`、`spec_lock.md`,也不创建替代规划产物。这些决策在上下文丢失后无法恢复。因此同一 Agent 可以顺序承担多个创作阶段,但阶段权责不会合并;Checker、Exporter 与运行记录器仍是独立的确定性工具。**默认备料有两个时点。** Topic Research 在最终确认前补充规划所需的事实:只有主题时立即运行;已有材料时先转换 / 阅读,仅在仍有关键事实缺口时补齐,而且不获取任何图片。当前 AI 编辑器若能提供具备网页检索 / 抓取能力并可写入声明输出路径的隔离研究子代理,由主代理定义缺口,子代理写入现有研究及来源产物并只返回回执;否则研究仍在主上下文运行。AI / web / slice 图片只能在最终确认以及完整的 `design_spec.md §VIII` / `spec_lock.md` 之后获取,并在 Executor 开始前进入终态。Strategist 还会在编写最终方案时解析、同步并验证精选项目图标池。Image_Generator、Image_Searcher 与图标同步工具只是 Strategist 负责的备料机制,不是独立决策者。快速生成则由当前 Agent 根据上下文决策按需使用这些备料机制,不插入确认门禁。-**项目中已备好的材料就是边界。** 默认流程中,图片和其他声明型资源须由 Strategist 选定、写入规划产物,并保证项目路径可解析或明确标为 `Needs-Manual`。图标 SVG 只要已位于 `<project>/icons/` 就属于已备材料;`spec_lock.icons.inventory` 是 Strategist 已同步精选内置图标池的索引,既不分配具体页面,也不是穷尽式执行白名单。Executor 按页从已备图标中选择。快速生成以当前上下文中的资源清单及其项目级文件 / manifest 代替该规划投影;当前 Agent 可以在手写 SVG 前获取并准备这些资源。其他目录中的文件不构成使用许可。缺料必须回到所属备料步骤;SVG 创作阶段不得静默换料。+**项目中已备好的材料就是边界。** 默认流程中,图片和其他声明型资源须由 Strategist 选定、写入规划产物,并保证项目路径可解析或明确标为 `Needs-Manual`。图标 SVG 只要已位于 `<project>/icons/` 就属于已备材料;`spec_lock.icons.inventory` 是 Strategist 已同步精选内置图标池的索引,既不分配具体页面,也不是穷尽式执行白名单。Executor 按页从已备图标中选择。快速生成以当前上下文中的资源决策及其项目级文件 / manifest 代替该规划投影,不写通用资源清单或逐页分配;当前 Agent 可以在手写 SVG 前获取并准备这些资源。其他目录中的文件不构成使用许可。缺料必须回到所属备料步骤;SVG 创作阶段不得静默换料。**具体程度决定自由度。** “做麻婆豆腐”锁定成品身份:火候、口感和摆盘可以发挥,但不能换成番茄炒蛋或豆腐汤。“做一道豆腐菜”则保留了品类内选择空间。默认流程中,Strategist 可以把这个开放要求收敛成具体方案;如果 Design Spec 有意保留某个维度的开放性,Executor 可以在该范围内实现。一旦 Design Spec 已经选定具有约束力的结果,执行阶段不得重新打开选择。快速生成则由当前 Agent 在上下文中解决同等选择,并在手写 SVG 时保持稳定。明确标为 suggestion 或 Reference 的字段——包括页面级首选图片 pattern——仍是表达建议;只要不改变内容、资源、身份和显式约束,就可以调整。**点缀只能保持局部。** 零星的页面级字体或颜色可以用于增加层级、区分和氛围,但不能发展成第二套视觉系统。默认流程中,结构性或重复出现的字体、色板角色、资源与跨页身份 pattern 仍属于 Strategist 决策,复用前必须先更新 Design Spec/lock;快速生成由当前 Agent 在上下文中建立这些锚点,并在跨页创作中保持。默认流程的页面级 §VIII 图片 pattern 仍是首选构图参考。-**提示词重构不变量。** 默认流程压缩提示词时,必须继续区分初始材料、用户确认、Strategist 负责的备料、策略规划和执行自由。把材料获取下放给 Executor、把许可变成配额、把灵活实现变成静默更换资源 / 身份,或把精确的约束计划降级成近似目标,均属于语义回归。显式快速生成 profile 会把前几层合并到当前 Agent,但不会删除来源处理或备料。默认流程的运行时权威位于 [`strategist.md`](../../skills/ppt-master/references/strategist.md) 与 [`executor-base.md`](../../skills/ppt-master/references/executor-base.md);快速生成从 [`quick-generate.md`](../../skills/ppt-master/workflows/profiles/quick-generate.md) 开始,并按需加载同一组资源参考。提示词编写规则位于 [`prompt-style.md`](../rules/prompt-style.md)。+**提示词重构不变量。** 默认流程压缩提示词时,必须继续区分初始材料、用户确认、Strategist 负责的备料、策略规划和执行自由。把材料获取下放给 Executor、把许可变成配额、把灵活实现变成静默更换资源 / 身份,或把精确的约束计划降级成近似目标,均属于语义回归。显式快速生成 profile 会把前几层合并到当前 Agent,但不会删除来源、资源、美学、数据可视化或原生形状能力。默认流程的运行时权威位于 [`strategist.md`](../../skills/ppt-master/references/strategist.md) 与 [`executor-base.md`](../../skills/ppt-master/references/executor-base.md);快速生成从 [`quick-generate.md`](../../skills/ppt-master/workflows/profiles/quick-generate.md) 开始,直接加载适用的共享与条件执行参考,不继承 Default 的持久计划前置条件。提示词编写规则位于 [`prompt-style.md`](../rules/prompt-style.md)。---@@ -595,7 +598,7 @@ SVG 与 DrawingML 的表达模型并不等价,因此主编译路径不把“| `exports/<narrated_stem>.mp4`(可选,经 `powerpoint_video.py`) | Windows PowerPoint 2016+ 下保留动画与旁白的视频交付物 | 委托 PowerPoint 原生编码器并等待完成;它是 PPTX 后处理集成,不是第二套 deck 渲染器 || `backup/<ts>/svg_output/`(仅默认输出路径;目录创建后复制为 best-effort) | 在不重跑 LLM 的前提下从冻结 SVG 源重建 pptx | 转换成功后先创建备份目录再尝试复制;显式 `-o` 不创建,复制失败不阻断导出,非 quiet 模式打印 warning,postflight 的 `backup_path` 为空,但目录创建失败仍会中断 |-校验 JSON 与 `validation/workflow.log` 都是冷审计产物,不是常规模型输入。只有用户明确要求复核运行过程时才打开转录。它可以还原项目级 Python 工具及其文本输出,也允许选择性记录重要阶段交接或返工原因、用户批准的例外及人工恢复选择等非 Python 事项;这些人工记录不重复制品内容、常规页面进度或私有推理,也不能替代当前制品对阶段与就绪状态的判定。导出器在程序内部读取 SVG 质量报告,并在默认非 quiet 流程打印紧凑的 `[POSTFLIGHT]` 回执,包含状态、质量门结果、Slide 数量、warning 类别计数和产物路径。成功流程只消费该回执,不加载两份完整 JSON;只有失败排查或用户明确要求审计时才定向提取报告字段。+校验 JSON 与 `validation/workflow.log` 都是冷审计产物,不是常规模型输入。只有用户明确要求复核运行过程时才打开日志。它可以还原项目级 Python 命令及有限的重要结果,而不是完整控制台输出;每条命令的尾部会记录保留与省略的输出行数。日志也允许选择性记录重要阶段交接或返工原因、用户批准的例外及人工恢复选择等非 Python 事项;这些人工记录不重复制品内容、常规页面进度或私有推理,也不能替代当前制品对阶段与就绪状态的判定。导出器在程序内部读取 SVG 质量报告,并在默认非 quiet 流程打印紧凑的 `[POSTFLIGHT]` 回执,包含状态、质量门结果、Slide 数量、warning 类别计数和产物路径。成功流程只消费该回执,不加载两份完整 JSON;只有失败排查或用户明确要求审计时才定向提取报告字段。### SVG 预处理器有**两种使用形态**diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.mdindex bf84f4a6..5cb4e9ba 100644--- a/skills/ppt-master/references/artifact-ownership.md+++ b/skills/ppt-master/references/artifact-ownership.md@@ -7,12 +7,15 @@ profile may explicitly omit an artifact without erasing its facts.**Quick Generate projection**: Quick omits confirmation, Design Spec, and lock.Its current main agent reads source/analysis facts, keeps routine decisions in-active context, and prepares images/icons/formulas plus required manifests-before SVG authoring. Exact template workspace roots supplied for the run are-validated and installed directly; Quick reads only that project-local state and-creates no Confirm UI selection artifacts. Those artifacts retain their-factual/provenance roles. Quick writes the same final SVG quality provenance and-package postflight as the default profile, but it does not create `svg_final/`.+active context, and prepares the selected images/icons/formulas plus required+operational manifests before SVG authoring. It may also realize charts, tables,+native shapes, and other ordinary authoring capabilities directly from that+context. Exact template workspace roots supplied for the run are validated and+installed directly; Quick reads only that project-local state and creates no+Confirm UI selection artifacts. Those artifacts retain their factual/provenance+roles. Quick writes the same final SVG quality provenance and package postflight+as the default profile, but it does not create `svg_final/`, a detailed design+history, or resumable planning state. Context loss restarts the Quick run.---@@ -52,7 +55,7 @@ package postflight as the default profile, but it does not create `svg_final/`.| `notes/total.md` | Conditional speaker-note source | Complete notes before splitting | Step 6 writes only when the effective Speaker Notes outcome is enabled; Step 7.1 splits || `notes/slide_*.md` | Conditional split notes | Per-slide notes generated from `total.md` | Derived by `total_md_split.py` only when speaker notes are enabled || `svg_final/` | Default-only derived visual preview | Self-contained post-processed SVGs that may be opened directly or inserted as SVG pictures | Default rebuilds it from `svg_output/` with `finalize_svg.py`; Quick omits it. Never use it as a supported PPTX source. |-| `validation/workflow.log` | Cold workflow transcript | Append-only Python command envelopes with tagged stdout/stderr, plus selective manual entries for important details with no owning Python output | `project_manager.py init` creates the log and records its milestone. Later project-scoped Python tools find that existing log through the shared CLI bootstrap and mirror their own text output without a wrapper command. A helper whose arguments/cwd do not identify the active project receives `PPT_MASTER_PROJECT_PATH=<project_path>` on the same Python command. A role may run `workflow_log.py` once for a material non-Python stage handoff or rework reason, user-approved exception, or manual recovery choice; never duplicate artifacts, routine progress, or private reasoning. Detached services retain detailed output in their component logs. Never read this transcript during normal generation/resume or use it as stage, artifact, or quality authority; inspect it only for an explicit user-requested run review. |+| `validation/workflow.log` | Cold workflow audit log | Append-only Python command envelopes, material tagged outcomes, bounded warning/OK/stderr samples, per-run omission counts, and selective manual entries for important details with no owning Python output | `project_manager.py init` creates the log and records its milestone. Later project-scoped Python tools find that existing log through the shared CLI bootstrap and record the bounded audit selection without a wrapper command; their full console output is not copied. A helper whose arguments/cwd do not identify the active project receives `PPT_MASTER_PROJECT_PATH=<project_path>` on the same Python command. A role may run `workflow_log.py` once for a material non-Python stage handoff or rework reason, user-approved exception, or manual recovery choice; never duplicate artifacts, routine progress, or private reasoning. Detached services retain detailed output in their component logs. Never read this log during normal generation/resume or use it as stage, artifact, or quality authority; inspect it only for an explicit user-requested run review. In Quick it remains an incomplete operational audit, not a design history or resume source. || `validation/svg_quality_report.json` | Final SVG quality provenance | Final SVG gate split into blocking / introduced / inherited / source-import categories, bound to the checked SVG bytes by SHA-256 | Default runs `svg_quality_checker.py --stage final --json`; Quick adds `--quick-generate` so the checker ignores Design Spec/lock and validates the lockless flat roster. Export links the report only when fingerprints match; Quick requires that link to pass before PPTX creation. || `validation/<output_stem>.report.json` | Published-package audit | PPTX package/resource postflight status, part counts, and quality-gate linkage | Both Generate profiles write it and emit `[POSTFLIGHT]` after package validation. || `exports/` | Delivery artifacts | Native DrawingML PPTX and explicit native-object/narration variants | Default Step 7.3 or Quick direct export writes final deliverables from `svg_output/`. |@@ -79,7 +82,7 @@ package postflight as the default profile, but it does not create `svg_final/`.| Page-design closure | On SVG-authoring routes, every visible exported-slide object exists in the corresponding page SVG or an explicitly referenced visual asset. || Package-behavior separation | Speaker notes, animations, transitions, narration, and direct native-PPTX workflows keep their owning artifacts; do not force them into SVG metadata. || Post-processed SVG | In Default Generate, `svg_final/` is disposable, must be rebuilt in Step 7.2, and serves only as a self-contained visual preview / manually insertable SVG picture. Quick omits it. |-| Workflow transcript | `validation/workflow.log` automatically records text written through a project-scoped Python tool's configured `sys.stdout` / `sys.stderr`, plus explicitly selected manual audit entries. It does not automatically capture direct file-authoring actions, host-native tools, pre-project conversion, binary-buffer writes, hidden child output, or detached-service activity; absence of a line proves nothing about those stages. Automatic transcript failure is advisory and never changes the owning tool's outcome; a failed explicit manual append reports failure because no entry was recorded. |+| Workflow audit log | `validation/workflow.log` automatically records each project-scoped Python command envelope, all explicit error/failure and receipt/report lines, bounded warning/OK/stderr samples, summary context, and omission counts, plus explicitly selected manual audit entries. It does not retain the full console stream or automatically capture direct file-authoring actions, host-native tools, pre-project conversion, binary-buffer writes, hidden child output, or detached-service activity; absence of a detail line proves nothing about those stages. Automatic recording failure is advisory and never changes the owning tool's outcome; a failed explicit manual append reports failure because no entry was recorded. || Export source | The only supported generated-PPTX route reads `svg_output/` through the project SVG-to-DrawingML converter. A diagnostic `-s final` override does not change ownership or create a supported release route. || Shape-conversion boundary | PowerPoint's manual Convert-to-Shape operation on `svg_final/` is outside the project compatibility contract. || Confirmation | Final UI/chat confirmation overrides recommendations and is consumed once into `design_spec.md`. Enabled refinement applies arbitrary revisions there and requires approval; only then may active-decision fidelity release lock authoring. |@@ -93,8 +96,9 @@ package postflight as the default profile, but it does not create `svg_final/`.## 3. Regeneration RulesThe table names each owning command. Generate profiles invoke these commands-directly; project-scoped Python stdout/stderr is recorded automatically after-initialization. Other routes retain their own invocation contract.+directly; the bounded project-scoped Python command/outcome audit is recorded+automatically after initialization. Other routes retain their own invocation+contract.| Derived artifact | Regenerate from | Command / owner ||---|---|---|diff --git a/skills/ppt-master/references/executor-chart.md b/skills/ppt-master/references/executor-chart.mdindex c86e0ae5..5c4769d6 100644--- a/skills/ppt-master/references/executor-chart.md+++ b/skills/ppt-master/references/executor-chart.md@@ -1,32 +1,48 @@-> See [`executor-base.md`](./executor-base.md) for the always-loaded Executor core and [`native-data-interface.md`](./native-data-interface.md) for native chart/table metadata schemas.+> Default Generate also loads [`executor-base.md`](./executor-base.md); Default and Quick load [`native-data-interface.md`](./native-data-interface.md) when native chart/table metadata is selected.# Executor Chart and Table BranchConditional Executor authority for data charts, chart-catalog adaptations, chart verification markers, and eligible native chart/table replacement metadata.-**Trigger**: load when `design_spec.md §VII` contains a selected chart/table reference, `spec_lock.md page_charts` contains any row, or the current §IX page block carries any data-encoded chart or text-grid table. Mini charts, sparklines, inset charts, and small multiples count even when they are absent from `page_charts` or the chart catalog.+**Trigger**: load when `design_spec.md §VII` contains a selected chart/table reference, `spec_lock.md page_charts` contains any row, the current §IX page block carries any data-encoded chart or text-grid table, or Quick Generate resolves such an object in active context. Mini charts, sparklines, inset charts, and small multiples count even when they are absent from `page_charts` or the chart catalog.++**Profile authority**: Default follows the Design Spec/lock and returns missing or conflicting planning decisions upstream. Quick has no plan artifact: the current main agent resolves the data object, optional catalog key, fallback design, and native-readiness immediately in active context, writes the selected semantics into the SVG itself, and does not create a substitute roster or mapping file.## 1. Reference Loading and Per-page Selection-For each selected `templates/charts/<key>.svg`, use its Skill-relative `reference_set` path + SHA: read once before first use or after change, otherwise reuse it. Never load the full catalog.+For each selected `templates/charts/<key>.svg`, use its Skill-relative path and+read once before first use or after a known change, otherwise reuse it. Never+load the full catalog.++**Per-page chart reference**:-**Per-page chart reference — `page_charts` section**:+| Active profile | Selection authority |+|---|---|+| Default Generate | Look up whether `spec_lock.md page_charts` supplies a page-local key, then read its §VII Usage and SVG for that page only |+| Quick Generate | Use bounded `chart_recall.py` only when a reusable visualization reference would help; keep the selected key and purpose in active context for that page only, or retain `no-template-match` and design from scratch |-Before drawing each page, look up whether `page_charts` supplies a page-local reference:+Before drawing each page, apply the matching branch:-- Entry present (e.g., `P09: timeline_horizontal`) → read its §VII Usage and SVG for that page only; realize §IX without copying it or loading the catalog.-- No entry for this page → no catalog reference was selected. Follow the current §IX `Visualization` / `Layout`; design any declared custom visualization from scratch without inventing a §VII reference.-- Whole section absent → no catalog references were selected; §IX may still contain custom data charts or tables.+- Selected key present (e.g., `timeline_horizontal`) → read that SVG for the current page only and realize the active page intent without copying it or loading the catalog.+- No selected key → design the declared visualization/table from scratch; do not invent a catalog reference after drawing begins.+- Quick never persists its selection into §VII, `page_charts`, or another mapping artifact.---## 2. Chart and Native-data Authoring-### 2.1 Chart Plot-Area Marker (MANDATORY on planned data-chart pages)+### 2.1 Chart Plot-Area Marker (MANDATORY on active data-chart pages)-> The [`verify-charts`](../workflows/stages/verify-charts.md) stage enumerates data-driven chart pages from `design_spec.md §IX`, cross-checks selected §VII references when present, then reads each page's plot-area marker to feed `svg_position_calculator.py`. A missing marker invokes that stage's declared fallback and adds avoidable derivation work.+> The [`verify-charts`](../workflows/stages/verify-charts.md) stage enumerates Default data-driven chart pages from `design_spec.md §IX`; Quick runs it from the still-active page decisions and cross-checks those decisions against plot-area markers. A missing marker invokes that stage's declared fallback and adds avoidable derivation work.-**Hard rule**: every page whose §IX `Visualization` declares data-driven chart geometry includes a plot-area marker inside `<g id="chartArea">`, placed **after axis lines** and **before the first data element** (bar, line, area, point). A legacy §VII data-chart row counts when its page block lacks that declaration. An incidental microvisual not promoted in §IX needs no marker; if its geometry must enter `verify-charts`, return upstream and update the owning §IX page block first.+**Hard rule**: every Default page whose §IX `Visualization` declares+data-driven chart geometry, and every Quick page the current agent resolves as+data-driven, includes a plot-area marker inside `<g id="chartArea">`, placed+**after axis lines** and **before the first data element** (bar, line, area,+point). A legacy §VII data-chart row counts when its page block lacks that+declaration. An incidental microvisual needs no marker unless the current+profile promotes it to a coordinate-verified data object; Default repairs §IX,+while Quick resolves that decision immediately before drawing.**Rectangular plot area** (bar / horizontal_bar / grouped_bar / stacked_bar / line / area / stacked_area / scatter / waterfall / pareto / butterfly):@@ -53,7 +69,7 @@ Before drawing each page, look up whether `page_charts` supplies a page-local re| `cx, cy` | Center point of pie/donut/radar (accounting for `transform="translate()"`) || `r` | Outer radius of the chart |-**Per-page verification** — after writing each planned data-chart SVG, confirm the marker exists:+**Per-page verification** — after writing each active data-chart SVG, confirm the marker exists:```bashrg -n "chart-plot-area" <project_path>/svg_output/<current_page>.svg@@ -65,15 +81,31 @@ rg -n "chart-plot-area" <project_path>/svg_output/<current_page>.svg> the same library do not use a plot-area marker.Technical SVG/PPT constraints remain in [`shared-standards-core.md`](./shared-standards-core.md).-### 2.2 PowerPoint-Native Chart/Table Replacement Marker (MANDATORY on planned native-ready objects)+### 2.2 PowerPoint-Native Chart/Table Replacement Marker (MANDATORY on selected native-ready objects)-> `svg_to_pptx.py --native-charts-and-tables` replaces marked groups with PowerPoint-native Chart/Table objects (charts get an embedded Excel workbook). Markers stay dormant in the default export, whose SVG children become independently editable DrawingML shapes. Prepare this optional capability for planned independent data objects, not every numeric embellishment.+> `svg_to_pptx.py --native-charts-and-tables` replaces marked groups with PowerPoint-native Chart/Table objects (charts get an embedded Excel workbook). Markers stay dormant in the default export, whose SVG children become independently editable DrawingML shapes. Prepare this optional capability for selected independent data objects, not every numeric embellishment.-**Hard rule**: load [`native-data-interface.md`](./native-data-interface.md) for each independent data chart or pure text-grid table whose §IX page block says `Native-ready: yes`. A supported data chart then gets `data-pptx-replace-with="chart"` plus one JSON `<metadata>` child; a pure text-grid table gets the table form, transcribing all plotted data or visible cells. `no` stays ordinary SVG even when a catalog reference contains a marker. For legacy specs only, use the matching §VII value when §IX has no field. Missing, conflicting, or invalid values return upstream; Executor never infers eligibility. The parent marker selects the schema.+**Hard rule**: load [`native-data-interface.md`](./native-data-interface.md) for+each independent data chart or pure text-grid table selected as native-ready.+Default reads that decision from the current §IX page block (`yes`/`no`; legacy+§VII fallback only). Quick decides in active context before drawing based on+whether the PowerPoint Chart/Table object model is useful enough to accept its+normalization risk. A supported selected chart gets+`data-pptx-replace-with="chart"` plus one JSON `<metadata>` child; a selected+pure text-grid table gets the table form, transcribing all plotted data or+visible cells. An object not selected stays ordinary SVG even when a catalog+reference contains a marker. The parent marker selects the schema.**MUST — atomic authoring**: For each native-ready object, treat the visible SVG fallback, the parent `data-pptx-replace-with` marker, and its JSON `<metadata>` child as one object. Write all three in the same SVG edit while the data is in context. Do not defer the marker or metadata to `verify-charts`, the final quality gate, or export.-**Hard rule — eligibility follows the plan**: A two-point line or small multiple gets metadata only when its §IX page block explicitly plans it as an independent object with `Native-ready: yes`. A sparkline, inset, KPI-card trend, or other incidental microvisual stays ordinary SVG even when values are recoverable. Changing eligibility requires upstream repair.+**Hard rule — eligibility follows the active profile authority**: In Default, a+two-point line or small multiple gets metadata only when its §IX page block+plans it as an independent object with `Native-ready: yes`; changing eligibility+requires upstream repair. In Quick, the current agent makes that independent-+object decision before drawing and expresses it atomically through the marker,+metadata, and fallback. A sparkline, inset, KPI-card trend, or other incidental+microvisual stays ordinary SVG unless Quick deliberately promotes it before+authoring.Generated authoring MUST omit `data-pptx-import-source` and`data-pptx-fallback-sha256`: those attributes record imported-PPTX provenance@@ -82,9 +114,9 @@ catalog or reusable template; normal content edits would make it stale.`data-pptx-replace-with` is a **data-backed replacement claim**, not a generic label for a group that contains numbers and not a marker for ordinary PowerPoint shapes or connectors. Add it only when the matching JSON payload can be written in the same edit; if the object is meant to remain SVG geometry, do not add the marker.-- Chart types absent from that list and conceptual/diagrammatic graphics (process flows, cycles, quadrant cards, timelines, or a KPI card container) get **no marker** — `svg_quality_checker.py` rejects unsupported marker types. A supported data chart nested inside one of those compositions gets its own marker only when its §IX page block explicitly plans that object as `Native-ready: yes`.+- Chart types absent from that list and conceptual/diagrammatic graphics (process flows, cycles, quadrant cards, timelines, or a KPI card container) get **no marker** — `svg_quality_checker.py` rejects unsupported marker types. A supported data chart nested inside one of those compositions gets its own marker only when Default §IX or the Quick active-context decision selects that object as native-ready.- Canonical rectangular merged text cells may carry a table marker by putting anchor-only `row_span` / `col_span` in metadata and leaving covered cells blank. Nonrectangular/overlapping merges, nonblank covered cells, and graphical cells (icons, harvey balls, rating dots) get **no table marker** and stay on the SVG fallback route.-- Transcribe, don't restyle: `categories` / `series[].values` are the numbers just plotted; `style.colors` copies the series HEX values already rendered on the page, whether they use a recurring `spec_lock.colors` anchor or a contextual page-local color.+- Transcribe, don't restyle: `categories` / `series[].values` are the numbers just plotted; `style.colors` copies the series HEX values already rendered on the page, whether they use a recurring Default `spec_lock.colors` anchor or a Quick/contextual page-local color.- Data-point color: when a single column/bar series uses data-point colors in the fallback, copy those fills into `series[].point_colors` in category order.- Data labels: when visible point values are part of the fallback chart, write `data_labels` instead of companion text; use `data_labels.points` for selected labels, and use `number_format`, `font_size`, `font_family`, and per-point `colors` / `color` when the fallback labels carry suffixes or color-coded text.- Line markers: when the fallback line chart draws visible point nodes, set `line_style: "lineMarker"`; leave the default `line` only for line charts without nodes.@@ -93,11 +125,11 @@ catalog or reusable template; normal content edits would make it stale.- Value-axis labels: when the fallback keeps category labels but intentionally omits numeric value-axis tick labels, set `show_value_axis_labels: false`.- Freeform chart text: transcribe center labels, source notes, and other in-chart annotations as companion `caption` / `note` / `notes` entries with explicit slide-coordinate bounds; do not rely on fallback `<text>` children to survive native export.- Native chart typography mirrors the SVG fallback. Copy the fallback's shared chart font into `style.font_family` and visible chart text sizes into the matching metadata fields (`title_font_size`, `subtitle_font_size`, `axis_font_size`, `note_font_size`, etc.) only when role sizes differ; otherwise let the exporter infer them from visible fallback text. When a visible chart title, subtitle, or axis title needs its own size/color/font, write that field as an object with `text`, `font_size`, `font_family`, and `color`. Use `axis_title_font_size`, `legend_font_size`, or companion per-entry `font_size` only when the fallback visibly uses a separate size.-- Native table typography mirrors the SVG fallback. Write `style.font_family` and `style.font_size` from the visible table text; use `header_font_size` or per-cell `font_size` only when the fallback visibly does so. If the fallback has no explicit table font, fall back to the deck body family and declared body anchor from `spec_lock.md typography`.+- Native table typography mirrors the SVG fallback. Write `style.font_family` and `style.font_size` from the visible table text; use `header_font_size` or per-cell `font_size` only when the fallback visibly does so. If the fallback has no explicit table font, Default uses the deck body family and declared `spec_lock.md` body anchor; Quick uses the concrete body family/size already resolved in active context.- The marker group's transform stays translate/scale only (no rotate / matrix / skew).- Visual parity is not a goal: the SVG drawing remains the designed visual and exports as editable DrawingML shapes; the native object is the data-backed counterpart with PowerPoint's chart/table-specific model. Never simplify the SVG design to match what a native object could show.-**Per-page verification** — after writing a page with planned native-ready objects, enumerate those objects and confirm a one-to-one match: every object has one parent marker and exactly one JSON metadata child. Finding one marker somewhere on a page is insufficient when the page contains multiple planned objects.+**Per-page verification** — after writing a page with selected native-ready objects, enumerate those objects and confirm a one-to-one match: every object has one parent marker and exactly one JSON metadata child. Finding one marker somewhere on a page is insufficient when the page contains multiple selected objects.```bashrg -n 'data-pptx-replace-with="(chart|table)"|<metadata type="application/json">' <project_path>/svg_output/<current_page>.svg@@ -108,27 +140,37 @@ rg -n 'data-pptx-replace-with="(chart|table)"|<metadata type="application/json">## 3. Visualization Reference-§1 loads the `page_charts` SVG. Usage gives page-local intent; §IX remains authoritative. Legacy wider rows keep Usage and ignore path/summary fields.+§1 loads only a selected page-local SVG. Default takes Usage/semantics from+§VII/§IX; Quick takes them from the current active-context page decision.-**Hard rule**: treat the loaded SVG as a page-local reference, not a required base. §IX and source data own the final information structure; never replicate the preview verbatim.+**Hard rule**: treat the loaded SVG as a page-local reference, not a required base. Default §IX or the Quick active-context page decision plus source data own the final information structure; never replicate the preview verbatim.**Adaptation rules**:-- **Preserve**: planned information relationships, data encoding, and every content obligation in the active Design Spec+- **Preserve**: Default-planned or Quick-resolved information relationships, data encoding, and every active content obligation- **Page-local only**: a reference row applies only to its mapped page; never spread it across the deck- **Flexible realization**: borrow, recombine, or depart from the preview's type and geometry when the current page is better served another way-- **Carry forward**: every planned label, value, unit, status, source, and explanatory block; never shorten or drop content to imitate a lighter catalog preview+- **Carry forward**: every authoritative label, value, unit, status, source, and explanatory block; never shorten or drop content to imitate a lighter catalog preview- **Adapt**: project data and labels, dimensions, axes, legend, and spacing as the authored content requires- **Project-owned**: palette, typography, container treatment, effects, background, and page chrome; catalog preview values are fallbacks, never defaults- **Bound final body modules**: add or revise root-coordinate `data-pptx-bounds` on every visible direct root `<g>` copied into the final page; nested groups need none, chart geometry and local references are not content-boundary inputs, and catalog reference warnings never waive the final-page contract- **Adjust with fidelity**: composition, axis ranges, grouping, and grid may change when the actual content, relationships, hierarchy, and data encoding remain complete-- **Forbidden**: treating preview structure as the page specification; omitting planned data points, labels, relationships, or explanatory content to fit it+- **Forbidden**: treating preview structure as the page specification; omitting authoritative data points, labels, relationships, or explanatory content to fit it> Templates: `templates/charts/`. `page_charts` maps one optional reference to one page; execution opens only that SVG.### 3.1 Chart Coordinate Calibration-Coordinate calibration runs as a **conditional post-generation stage**, not inside the Executor authoring loop. After SVG generation completes, if the deck contains data charts, run [`verify-charts`](../workflows/stages/verify-charts.md) before post-processing.--The executor's only obligation here is upstream: embed the `<!-- chart-plot-area ... -->` marker on each §IX-planned data-chart page during initial draft (§2.1). Verify-charts enumerates those pages from the authoritative page roster and uses the marker to feed `svg_position_calculator.py`.+Coordinate calibration runs as a **conditional post-generation stage**, not+inside the SVG authoring loop. After SVG generation completes, if the deck+contains data-driven charts, run+[`verify-charts`](../workflows/stages/verify-charts.md). Default follows its+declared gate order; Quick runs calibration before its one lockless final+checker.++The authoring obligation is upstream: embed the+`<!-- chart-plot-area ... -->` marker on every active data-chart page during the+initial draft (§2.1). Verify-charts enumerates Default pages from the Design+Spec; Quick enumerates them from the still-active page decisions and cross-checks+the markers before feeding `svg_position_calculator.py`.> 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/references/executor-image.md b/skills/ppt-master/references/executor-image.mdindex 7cefe9bf..b9a48d28 100644--- a/skills/ppt-master/references/executor-image.md+++ b/skills/ppt-master/references/executor-image.md@@ -6,13 +6,13 @@Conditional Executor authority for image status handling, placement, crop behavior, formula images, and template-bundled images.-**Trigger**: load for any image/formula in §VIII, the lock, a Quick Generate roster, or a selected template.+**Trigger**: load for any image/formula in §VIII, the lock, Quick Generate's active-context resource decisions, or a selected template.## 1. Image HandlingHandle images by status; enum and lifecycle: [`svg-image-embedding.md`](svg-image-embedding.md).-**Mode boundary**: Default keeps Strategist → Executor with no downstream acquisition/reselection. Quick substitutes the main agent's prepared transient roster for §VIII/lock below; the same boundary starts at SVG authoring.+**Mode boundary**: Default keeps Strategist → Executor with no downstream acquisition/reselection. Quick substitutes the main agent's prepared active-context resources for §VIII/lock below; the same boundary starts at SVG authoring.| Status | Source | Handling ||--------|--------|----------|diff --git a/skills/ppt-master/references/image-base.md b/skills/ppt-master/references/image-base.mdindex d48474a7..aa5765cb 100644--- a/skills/ppt-master/references/image-base.md+++ b/skills/ppt-master/references/image-base.md@@ -13,14 +13,14 @@ Active when at least one resource row has `Acquire Via: ai` / `web` / `slice`. R| Mode | Trigger ||---|---|| Default Generate | `generate-ppt` workflow, `design_spec.md §VIII` image rows present |-| Quick Generate | [`quick-generate`](../workflows/profiles/quick-generate.md) is active and its transient resource roster contains image rows |+| Quick Generate | [`quick-generate`](../workflows/profiles/quick-generate.md) is active and the current main agent has resolved one or more required images in active context || Standalone | Direct request against an existing project |---## 2. Image Resource List Format-Default Generate uses Strategist-owned `design_spec.md §VIII` plus its lock projection. Quick Generate substitutes a transient active-context roster; it creates neither planning artifact. Status enum: [`svg-image-embedding.md`](svg-image-embedding.md).+Default Generate uses Strategist-owned `design_spec.md §VIII` plus its lock projection. Quick Generate substitutes active-context resource decisions plus required operational manifests; it creates no planning artifact or general resource roster. Status enum: [`svg-image-embedding.md`](svg-image-embedding.md).| Filename | Dimensions | Purpose / Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference ||---|---|---|---|---|---|---|---|@@ -53,7 +53,7 @@ For each row with `Status: Pending`:Before processing any row:-1. Read the Default Design Spec/lock, or reuse Quick's transient roster and active visual/page decisions+1. Read the Default Design Spec/lock, or reuse Quick's active-context resource and visual/page decisions2. Group resource list rows by `Acquire Via`3. Confirm `project/images/` exists4. Materialize explicit user assets, render declared formulas, and finish triggered ai/web/slice acquisition before SVG authoring begins@@ -116,7 +116,7 @@ Executor reads the manifest per slide and renders inline credits when needed —## 8. Intent Ownership-The `Reference` field is **intent**, not a query. Strategist owns it by default; Quick's main agent owns it in the transient roster. The receiving role translates without reopening it.+The `Reference` field is **intent**, not a query. Strategist owns it by default; Quick's main agent resolves it in active context. The receiving role translates without reopening it.| ✅ Intent | ❌ Pre-processed ||---|---|@@ -127,7 +127,7 @@ The `Reference` field is **intent**, not a query. Strategist owns it by default;## 9. Handoff with SVG Authoring-SVG authoring consumes the resource roster plus:+SVG authoring consumes the active profile's resource authority plus:| Artifact | Path | Purpose ||---|---|---|diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.mdindex 4d98a63f..0d6a9590 100644--- a/skills/ppt-master/references/image-generator.md+++ b/skills/ppt-master/references/image-generator.md@@ -4,7 +4,7 @@Role definition for the **AI image generation path**: convert each active `Acquire Via: ai` row into an optimized prompt, generate the image, and save it to `project/images/`; also defines the `slice` derivation path for AI-generated illustration sheets.-**Trigger**: the Default Generate resource list or Quick Generate transient roster contains `Acquire Via: ai` or `slice`. The role is loaded only when at least one such row exists.+**Trigger**: the Default Generate resource list contains `Acquire Via: ai` or `slice`, or Quick Generate has resolved a required AI/sliced image in active context. Load only when at least one such resource exists.---@@ -120,11 +120,11 @@ Derive color behavior from the available roles and image context: background / s### Step 3 — Per-image type + assembly-For each `Acquire Via: ai` row, use Strategist-owned §VIII/lock by default or the main agent's transient Quick roster. Explicit values remain binding; Quick resolves omissions automatically.+For each `Acquire Via: ai` row, use Strategist-owned §VIII/lock by default or the main agent's active-context Quick resource decision. Explicit values remain binding; Quick resolves omissions automatically.-`Layout pattern` is a page-realization preference and is not copied wholesale into the bitmap prompt. Any generation-time subject direction, focal placement, quiet region, or overlay-safety requirement must therefore be present in the row's `Reference`, the matching §IX block, or the Quick roster's visual intent.+`Layout pattern` is a page-realization preference and is not copied wholesale into the bitmap prompt. Any generation-time subject direction, focal placement, quiet region, or overlay-safety requirement must therefore be present in the row's `Reference`, the matching §IX block, or Quick's active-context visual intent.-1. **Determine `page_role`** — the owning row's explicit value wins; a blank or omitted value resolves to `local`. In Default Generate, `hero_page` must be Strategist-explicit; in Quick Generate, the main agent may resolve it while building the transient roster.+1. **Determine `page_role`** — the owning row's explicit value wins; a blank or omitted value resolves to `local`. In Default Generate, `hero_page` must be Strategist-explicit; in Quick Generate, the main agent may resolve it before acquisition in active context.2. **Determine `text_policy`** — the owning row's value wins when set. **Declared-inference fallback for a blank or omitted value**: pick `none` or `embedded` from the row's `Purpose`, `Reference`, and page intent based on whether in-image text serves the page. Long body / data / lists stay in SVG.3. **Determine type or free composition** — an Illustration Sheet omits manifest `type` and follows §4.3's grid composition. For another local structural infographic, use one of the 11 types only when the `_index.md` offers a real match; otherwise omit type and author the intended structure directly with §4.1 E. A local single-subject/portrait image omits type and uses §4.1 A/B inside its actual region. A `hero_page` omits type and uses §4.1 A/B/C/D/E.4. `read_file references/image-type-templates/<type>.md` only when a type was selected (and only if not already read).@@ -132,7 +132,7 @@ For each `Acquire Via: ai` row, use Strategist-owned §VIII/lock by default or t- The rendering's style paragraph (from Step 2)- Color-role instructions anchored by the deck HEX values and refined for the image context (from Step 2)- The selected type's structural layout, or the no-type composition prose (from Step 3)- - The image's specific `Reference` intent (from `design_spec.md §VIII` or the Quick Generate transient roster)+ - The image's specific `Reference` intent (from `design_spec.md §VIII` or the Quick Generate active-context decision)- Container sizing from the selected type file, or the row's Dimensions for no-type prose- The hard rules from §5 below (HEX-not-as-text, rendering-aligned human depiction and likeness authorization, text policy)@@ -254,7 +254,7 @@ An illustration sheet can produce several small **spot illustrations** in one ge**Default — one sheet for a compatible spot family (may override when separate generation serves the assets better)**: Prefer a sheet when several elements share similar proportions, detail, quality, and semantic precision. Generate elements separately when those needs differ materially; quantity alone neither requires nor forbids a sheet. A single hero/local image stays with the normal one-row-per-image flow (§4.1).-**Hard rule**: a spot sheet is a generation source, not a slide asset. In Default Generate, keep the sheet row out of `spec_lock.md images`; in Quick Generate, mark it generation-only in the transient roster. The sheet is never referenced from SVG. Only sliced element rows are placed.+**Hard rule**: a spot sheet is a generation source, not a slide asset. In Default Generate, keep the sheet row out of `spec_lock.md images`; in Quick Generate, retain its generation-only status in active context and the operational manifest. The sheet is never referenced from SVG. Only sliced element rows are placed.**Sheet prompt convention** (one manifest item, `page_role: local`, `text_policy: none`, `image_size` chosen from final placement size):@@ -280,7 +280,7 @@ Use that deliberately. On a wide sheet (`16:9`, `21:9`, `4:1`, `8:1`), `1xN` makIf one deck needs mixed shapes, create separate sheets per shape family unless one carefully designed grid gives every element enough room. Keep the visual family consistent through the same `deck_rendering` and `color_scheme`, not by forcing all cells into one square sheet.-**Resource contract — the sheet and its elements are different row kinds.** A sliced element can only be placed if it exists in the active placeable-resource authority: `spec_lock.md images` in Default Generate or the transient roster in Quick Generate. Default Generate keeps both row kinds in §VIII under [`strategist-image.md`](./strategist-image.md); Quick Generate resolves the same distinction in active context without creating planning artifacts:+**Resource contract — the sheet and its elements are different row kinds.** A sliced element can only be placed if it exists in the active placeable-resource authority: `spec_lock.md images` in Default Generate or the current agent's prepared resource decision in Quick Generate. Default Generate keeps both row kinds in §VIII under [`strategist-image.md`](./strategist-image.md); Quick Generate resolves the same distinction in active context and its operational manifest without creating planning artifacts:- **Sheet row** — `Acquire Via: ai`, `Type: Illustration Sheet`, the intent prompt, named as the slice source with its intended cell shape and placement purpose (`Reference: landscape footer-vignette spot set`). It is generated in Step 5 but **never placed on a slide** — keep it **out of** `spec_lock.md images`. Image_Generator resolves the exact `aspect_ratio`, grid, and slice command from this intent.- **Element rows** — one per used element, `Acquire Via: slice`, filename matching a `--names` output, `Reference` naming the parent sheet + cell/element. These **are** placed — list every one in the active placeable-resource authority, normally with `crop=no-crop` (a tight-trimmed transparent spot should be fit, not cover-cropped). Their dimensions are filled in after slicing (the preparation pass re-runs `analyze_images.py`). Each row carries an owner-resolved layout recommendation; SVG authoring may realize it as a direct cutout or inside an appropriate container while preserving the resource and crop/content constraints.@@ -593,14 +593,16 @@ Triggered automatically when `IMAGE_BACKEND` is not configured (or Path A fails)- Filenames awaiting manual generation- Pointer to `images/image_prompts.md` (paste-ready `### Image N:` block per item) or `image_prompts.json` (`items[].prompt`)- Target placement: `project/images/<filename>` matching the resource list exactly- - Resume: Default Generate re-runs Step 7; Quick Generate re-runs its resource gate, final checker, then `--quick-generate`+ - Continuation: Default Generate re-runs Step 7; Quick may validate the supplied file, rerun its resource gate and final checker, then use `--quick-generate` only while the original active context remains available — otherwise start a clean Quick run**User-initiated**: When Strategist Step 4 captured `manual` in Default Generate, or the user explicitly requested `manual` in the Quick Generate active context, Path A is skipped from the start.> Default Generate tolerates `Needs-Manual` rows through authoring and resumes-> at Step 7. Quick Generate preserves the same manifest and handoff but does not-> run `--quick-generate` while a required row still says `Needs-Manual`; validate-> a later supplied file and update it to `Generated` first.+> at Step 7. Quick Generate preserves the same operational manifest and handoff+> but does not run `--quick-generate` while a required row still says+> `Needs-Manual`. If the original active context remains available, validate a+> later supplied file and update it to `Generated`; otherwise start a clean+> Quick run rather than treating the manifest as a resumable design record.#### AI-specific Failure Handling (extends image-base.md §6)diff --git a/skills/ppt-master/references/image-searcher.md b/skills/ppt-master/references/image-searcher.mdindex 6be8cbaf..d8687b1a 100644--- a/skills/ppt-master/references/image-searcher.md+++ b/skills/ppt-master/references/image-searcher.md@@ -4,7 +4,7 @@Role definition for the **web image acquisition path**: translate the active resource owner's intent into keyword queries, search openly-licensed providers, download a license-cleared image into `project/images/`, and record provenance + license metadata into `image_sources.json`.-**Trigger**: the Default Generate resource list or Quick Generate transient roster contains `Acquire Via: web`. The role is loaded only when at least one such row exists.+**Trigger**: the Default Generate resource list contains `Acquire Via: web`, or Quick Generate has resolved a required web image in active context. Load only when at least one such resource exists.---@@ -70,12 +70,12 @@ Keep two layers distinct:| Layer | Owner and grammar ||---|---|| Default Generate `design_spec.md §VIII Reference` | Strategist's complete visual intent: exact subject, desired view/mood, focal or quiet region, and crop-safety constraints. Positive quality cues are valid here. |-| Quick Generate transient `Reference` | Current main agent's active-context intent after honoring explicit user assets, URLs, subjects, and constraints; unspecified choices are resolved automatically without confirmation. |+| Quick Generate active `Reference` | Current main agent's active-context intent after honoring explicit user assets, URLs, subjects, and constraints; unspecified choices are resolved automatically without confirmation. || `image_queries.json.items[].query` / positional query | Image_Searcher's concrete entity/identity keyword string. Start with the shortest phrase that preserves identity; keep exact multi-word names and necessary disambiguators even when they exceed four words. Omit mood, quality, composition, HEX, and negative wording. |Web APIs match metadata, not semantic intent. Providers try the original query first, then progressively simplified four/three/two/one-word variants. A pipeline manifest should therefore use a concise query without pre-truncating exact names. For Chinese landmarks, use the precise Chinese name with Wikimedia; for stock providers, use compact English identity terms when they retain the subject.-Image_Searcher consumes the active Reference and never rewrites its owner. In Default Generate, that means no rewrite of `design_spec.md` or `spec_lock.md`; in Quick Generate, the transient Reference remains fixed for the run. A candidate either satisfies that existing subject/focal/crop intent, or the role tries materially different query/provider/permitted-license strategies until no untried strategy remains, then marks `Needs-Manual`. Never loosen `required_terms`, the license policy, or the active intent to manufacture a match.+Image_Searcher consumes the active Reference and never rewrites its owner. In Default Generate, that means no rewrite of `design_spec.md` or `spec_lock.md`; in Quick Generate, the active-context Reference remains fixed for the run. A candidate either satisfies that existing subject/focal/crop intent, or the role tries materially different query/provider/permitted-license strategies until no untried strategy remains, then marks `Needs-Manual`. Never loosen `required_terms`, the license policy, or the active intent to manufacture a match.When the subject is an exact entity (landmark / person / company / product / venue), write `required_terms` at the same time you write the row's `query`. Use one required group per identity anchor and `|` for aliases / translations, e.g. `["Chongqing|重庆", "Jiefangbei|解放碑|Liberation Monument"]`. This keeps the query short for provider search while preventing metadata-ranked wrong entities from being accepted.@@ -318,7 +318,7 @@ CLI exit: `0` when all attempted rows resolve; `1` while any row remains `FailedReference field is **intent description**, not a query. See [`image-base.md`](./image-base.md) §8 for the rule.-Keep it intact as the acceptance contract. In Default Generate the owner is Strategist; in Quick Generate it is the current main agent's transient roster. Derive a separate concise provider query that preserves exact names and necessary disambiguation; do not pass the Reference verbatim or rewrite it after search.+Keep it intact as the acceptance contract. In Default Generate the owner is Strategist; in Quick Generate it is the current main agent's active-context resource decision. Derive a separate concise provider query that preserves exact names and necessary disambiguation; do not pass the Reference verbatim or rewrite it after search.---diff --git a/skills/ppt-master/references/modes/_index.md b/skills/ppt-master/references/modes/_index.mdindex e119ad6d..34026dd7 100644--- a/skills/ppt-master/references/modes/_index.md+++ b/skills/ppt-master/references/modes/_index.md@@ -1,14 +1,14 @@# Modes — Index-A **mode** is the deck's **narrative + persuasion skeleton** — how the argument is organized and advanced across pages. Lock **one mode per deck**; it shapes page sequencing, title voice, page-structure tendencies, and speaker-notes register.+A **mode** is the deck's **narrative + persuasion skeleton** — how the argument is organized and advanced across pages. Resolve **one mode per deck**; Default locks it, while Quick keeps it only in active context. It shapes page sequencing, title voice, page-structure tendencies, and speaker-notes register.-> A mode is *not* a visual style. **Mode = how you argue; visual style = how it looks** (see [`visual-styles/_index.md`](../visual-styles/_index.md)). The two are locked independently — any mode pairs with any visual style (a `pyramid` deck can look `swiss-minimal` or `dark-tech`).+> A mode is *not* a visual style. **Mode = how you argue; visual style = how it looks** (see [`visual-styles/_index.md`](../visual-styles/_index.md)). Resolve the two independently — any mode pairs with any visual style (a `pyramid` deck can look `swiss-minimal` or `dark-tech`).---## 1. Catalog (5 modes)-Each mode has its own file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. A preset lock reads that one file. A catalog-based `custom` reads every preset named in `mode_references`; a novel `custom` may omit references. Never glob the directory.+Each mode has its own file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. Default reads the locked preset file; Quick reads the preset it resolves in active context. A catalog-based `custom` reads every preset actually used as a basis; a novel `custom` reads none. Never glob the directory.| Mode | Narrative skeleton | Best for ||---|---|---|@@ -18,9 +18,9 @@ Each mode has its own file with: narrative skeleton, page-structure tendencies,| [`showcase`](./showcase.md) | Visual-led impact; big imagery / numbers; emotional rhythm | Launches, brand reveals, event / promo decks || [`briefing`](./briefing.md) | Neutral, complete, scannable; topic titles, even weight, no thesis | Status updates, reference decks, catalogs, meeting packs, FAQs |-> The five are **argument strategies, not a taxonomy of communication purposes**. A presentation may inform + align + request a decision at once; that composite intent stays as open prose in the Stage-1 communication contract. Stage 2 chooses the mode that best carries the dominant body-page spine, or one concrete `custom` act sequence when no preset can serve the stated priority / sequence.+> The five are **argument strategies, not a taxonomy of communication purposes**. A presentation may inform + align + request a decision at once; that composite intent stays as open prose in Default's Stage-1 communication contract or Quick's active brief. Default Stage 2 or the Quick main agent chooses the mode that best carries the dominant body-page spine, or one concrete `custom` act sequence when no preset can serve the stated priority / sequence.>-> **A mode is a lens, not a mandate over an explicitly preserved structure.** Apply the confirmed `content_divergence` to a user-supplied outline. An ordinary source outline is a Reference that the mode may regroup, reorder, or retitle while preserving its facts and intended relationships. Preserve page order, titles, or wording only when the user presents the outline as the final page plan or explicitly requests that boundary. When the user gives no structure, the mode does the structural lifting. To keep reshaping light, `briefing` imposes the least skeleton.+> **A mode is a lens, not a mandate over an explicitly preserved structure.** Default applies the confirmed `content_divergence`; Quick applies the equivalent user-stated or active-context boundary to a supplied outline. An ordinary source outline is a Reference that the mode may regroup, reorder, or retitle while preserving its facts and intended relationships. Preserve page order, titles, or wording only when the user presents the outline as the final page plan or explicitly requests that boundary. When the user gives no structure, the mode does the structural lifting. To keep reshaping light, `briefing` imposes the least skeleton.---@@ -51,12 +51,12 @@ Each mode has its own file with: narrative skeleton, page-structure tendencies,## 3. How to use-1. Strategist reads this index at confirmation `d. Layer 1`.-2. Preselect one mode from the auto-selection table + the confirmed communication contract and source structure; separately author the visible AI custom candidate required by §4.-3. Record the confirmed mode and rationale in `design_spec.md`, then project `- mode: <name>` into `spec_lock.md`.-4. Executor reads `modes/<locked-mode>.md` for a preset. For `custom`, it reads every file listed in `mode_references` before applying `mode_behavior`; with no references, it applies the novel behavior directly. Never glob this directory.+| Active profile | Use |+|---|---|+| Default Generate | Strategist reads this index at confirmation `d. Layer 1`, authors the required candidate set, records the confirmed mode in `design_spec.md`, and projects it to `spec_lock.md`; Executor reads the locked preset or exact custom references |+| Quick Generate | The current main agent reads this index, resolves the best-fit preset or one warranted custom behavior without interaction, reads only the exact preset source(s) actually used, and keeps the result in active context without Design Spec/lock |-**Lock scope**: deck-wide (one mode per deck). The five are the catalog you select from; if the structure is genuinely mixed, pick the mode of the body pages and let pages vary within it, or recommend a `custom` blend (§4). Recommend the best fit; the user confirms.+**Resolution scope**: deck-wide (one mode per deck). The five are the catalog you select from; if the structure is genuinely mixed, pick the mode of the body pages and let pages vary within it, or use a warranted `custom` blend (§4). Default recommends and confirms; Quick decides directly.---@@ -64,12 +64,14 @@ Each mode has its own file with: narrative skeleton, page-structure tendencies,`custom` holds **any bespoke narrative direction the five don't give as-is** — and what *kind* of thing it is doesn't matter. It might be a nameable cadence (dialectic 正反合, myth-vs-reality, countdown / Top-N, Socratic), a deliberate multi-act fusion of several modes, or the user's own feel for how the deck should carry (confrontational here, detached there). Don't try to taxonomize it.-**Always author the candidate; select it only when warranted.** Stage 2 includes one visible, non-empty AI custom proposal beside the five presets, spelling out the cadence / fusion / posture in plain language. It is initially unselected and does not replace the best-fit preset recommendation unless the user already supplied that exact custom direction; with a template, it must fit available prototype capacity. When the user selects it, the editable prose is saved as `mode: custom` plus `mode_behavior`; otherwise it remains recommendation-only. The Strategist crystallizes a selected custom direction in the Design Spec first, then projects the behavior and any actual catalog basis to `spec_lock.md`. The Executor reads every listed basis file before following that prose, or follows it directly when the direction is novel. (This records the intent so it survives 20 pages of generation — the Executor only ever reads `spec_lock.md`, never the chat.)+**Default candidate**: Stage 2 includes one visible, non-empty AI custom proposal beside the five presets, spelling out the cadence / fusion / posture in plain language. It is initially unselected and does not replace the best-fit preset recommendation unless the user already supplied that exact custom direction; with a template, it must fit available prototype capacity. When the user selects it, the editable prose is saved as `mode: custom` plus `mode_behavior`; otherwise it remains recommendation-only. The Strategist crystallizes a selected custom direction in the Design Spec first, then projects the behavior and any actual catalog basis to `spec_lock.md`. The Executor reads every listed basis file before following that prose, or follows it directly when the direction is novel.-**Mandatory — read every catalog source actually used**: If the proposal combines or borrows an existing mode, name its exact catalog id in the visible proposal and read that mode file before writing the synthesis. A `pyramid` + `narrative` fusion therefore reads both [`pyramid.md`](./pyramid.md) and [`narrative.md`](./narrative.md), then writes `mode_references: pyramid, narrative` beside `mode_behavior`. Do not add loosely related references after the fact. A genuinely new cadence with no catalog source writes no `mode_references` and may proceed from its standalone behavior.+**Quick custom**: do not author or display a candidate set. Use `custom` only when no single preset supplies the dominant spine, resolve its behavior directly in active context, and read every catalog source actually used as a basis. Persist nothing.-> **One value per deck — fusion is *one* `custom`, not several modes.** A deck always locks a single `mode`. A multi-mode blend is expressed as **one** `mode: custom` whose `mode_behavior` paragraph describes the acts — never by locking several modes.+**Mandatory — read every catalog source actually used**: If a custom direction combines or borrows an existing mode, name its exact catalog id and read that mode file before writing the synthesis. A `pyramid` + `narrative` fusion therefore reads both [`pyramid.md`](./pyramid.md) and [`narrative.md`](./narrative.md). Default writes `mode_references: pyramid, narrative` beside `mode_behavior`; Quick retains those bases only in active context. Do not add loosely related references after the fact. A genuinely new cadence reads no catalog source.++> **One value per deck — fusion is *one* `custom`, not several modes.** A deck always resolves a single `mode`. A multi-mode blend is expressed as **one** custom behavior whose paragraph describes the acts — never as several simultaneous modes.>-> **First ask whether it's really fusion.** A locked mode is a *tendency*, not a cage: a `narrative` deck can still carry one analytical (pyramid-style) page, an `instructional` deck one showcase reveal — that is leaning within a dominant mode, and needs **no** `custom`. Reach for `custom` only when there is genuinely no single dominant spine.+> **First ask whether it's really fusion.** A resolved mode is a *tendency*, not a cage: a `narrative` deck can still carry one analytical (pyramid-style) page, an `instructional` deck one showcase reveal — that is leaning within a dominant mode, and needs **no** `custom`. Reach for `custom` only when there is genuinely no single dominant spine.-**The one thing to avoid**: selecting `custom` as a *dodge* — defaulting to it because picking among the five takes judgment. The custom candidate is mandatory; a custom lock is not. When a preset genuinely fits, keep that preset selected. A user-stated direction remains authoritative the same way a user-supplied outline is — see the lens-not-mandate note in §1.+**The one thing to avoid**: selecting `custom` as a *dodge* — defaulting to it because picking among the five takes judgment. Default's custom candidate is mandatory; selecting it is not. Quick creates no candidate. When a preset genuinely fits, keep that preset selected. A user-stated direction remains authoritative the same way a user-supplied outline is — see the lens-not-mandate note in §1.diff --git a/skills/ppt-master/references/native-data-interface.md b/skills/ppt-master/references/native-data-interface.mdindex aaa8779f..53982ac0 100644--- a/skills/ppt-master/references/native-data-interface.md+++ b/skills/ppt-master/references/native-data-interface.md@@ -40,9 +40,18 @@ this enum.## 2. PowerPoint-Native Chart / Table Replacement Markers (Opt-in)-Native PowerPoint tables and Excel-backed charts activate at export time only. Generated pages prepare dormant replacement metadata for independently planned native-ready objects while keeping hand-authored SVG geometry pixel-stable across PowerPoint / Keynote / LibreOffice / WPS.--**Hard rule — planned-object authoring**: Executor writes the marker and JSON metadata in the same edit only for a supported chart or pure text-grid table whose `design_spec.md §IX` page block says `Native-ready: yes` ([`executor-chart.md`](./executor-chart.md) §2.2). `no` and incidental microvisuals stay on the SVG fallback route. For legacy specs only, a matching §VII value may supply the decision when §IX has no field. Canonical rectangular merged text cells may use the narrow `row_span` / `col_span` contract below; graphical cells stay unmarked. The marker group supplies visible SVG fallback children for browser/live-preview rendering and JSON metadata for `svg_to_pptx` native export.+Native PowerPoint tables and Excel-backed charts activate at export time only. Generated pages prepare dormant replacement metadata for independently selected native-ready objects while keeping hand-authored SVG geometry pixel-stable across PowerPoint / Keynote / LibreOffice / WPS.++**Hard rule — selected-object authoring**: write the marker and JSON metadata in+the same edit only for a supported chart or pure text-grid table selected as+native-ready under [`executor-chart.md`](./executor-chart.md) §2.2. Default reads+`Native-ready: yes` from §IX (legacy §VII fallback only); Quick makes the+decision in active context before drawing. Default `no`, a Quick decision not to+use the native object model, and incidental microvisuals stay on the SVG+fallback route. Canonical rectangular merged text cells may use the narrow+`row_span` / `col_span` contract below; graphical cells stay unmarked. The+marker group supplies visible SVG fallback children for browser rendering and+JSON metadata for `svg_to_pptx` native export.**Hard rule — activation is the opt-in, dormant unless exported with `--native-charts-and-tables`**: A marker only declares that a group is eligible for PowerPoint-native Chart/Table replacement. Normal `svg_to_pptx.py` runs keep the fallback SVG children and convert them into independently editable DrawingML shapes. Pass `--native-charts-and-tables` only when the data source and chart/table-specific object model matter more than cross-renderer layout fidelity: it emits the PowerPoint Chart/Table object and skips the fallback children to avoid duplicates. Native styling preserves the core palette, text, axis, grid, and background colors where possible, but it is still a PowerPoint Chart/Table object rather than a pixel-identical SVG drawing.@@ -137,8 +146,8 @@ materialized alternating row fills. Native table typography mirrors thevisible SVG fallback: put `style.font_family` and `style.font_size` on themarker from the table text already drawn, then use `style.header_font_size` orper-cell `font_size` only when the fallback visibly differs. If the fallback-has no explicit table font, use the deck body family and declared body anchor from-`spec_lock.md`.+has no explicit table font, Default uses the deck body family and declared body+anchor from `spec_lock.md`; Quick uses its active-context body family and size.**Hard rule — table metadata is the native source of truth**: Every row,summary line, value, and cell-level style that must survivediff --git a/skills/ppt-master/references/svg-image-embedding.md b/skills/ppt-master/references/svg-image-embedding.mdindex 50c5bbf5..8c0ce506 100644--- a/skills/ppt-master/references/svg-image-embedding.md+++ b/skills/ppt-master/references/svg-image-embedding.md@@ -16,7 +16,7 @@ and filter/clip contracts.| Mode | Resource authority and preparation timing ||---|---|| Default Generate | `design_spec.md §VIII` plus its lock projection; when user-provided images are selected, run `analyze_images.py` after Strategist confirmation and complete the list before Executor |-| Quick Generate | Current main agent's transient active-context roster; materialize explicit user paths first, resolve unspecified acquisition decisions automatically, and finish user/ai/web/slice/formula preparation before SVG authoring without confirmation |+| Quick Generate | Current main agent's active-context resource decisions; materialize explicit user paths first, resolve unspecified acquisition decisions automatically, and finish user/ai/web/slice/formula preparation before SVG authoring without confirmation or a persisted roster |```markdown| Filename | Dimensions | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference |@@ -45,7 +45,7 @@ and filter/clip contracts.```1. Resolve image needs:- Default Generate → Strategist-owned resource list + lock projection- - Quick Generate → current main agent builds a transient roster in active context; explicit user paths/URLs/choices win, unspecified choices use automatic resolution, no interaction+ - Quick Generate → current main agent resolves the required resource in active context; explicit user paths/URLs/choices win, unspecified choices use automatic resolution, no interaction or persisted roster2. Prepare project-local resources before SVG authoring:- user → materialize the explicit source under project/images/ → Existing- formula → write formula_manifest.json and run latex_render.py → Rendereddiff --git a/skills/ppt-master/references/visual-styles/_index.md b/skills/ppt-master/references/visual-styles/_index.mdindex 6f702f15..b837ec1d 100644--- a/skills/ppt-master/references/visual-styles/_index.md+++ b/skills/ppt-master/references/visual-styles/_index.md@@ -1,18 +1,18 @@# Visual Styles — Index-A **visual style** is how the deck **looks** — shape language, decoration density, whitespace rhythm, typographic character, texture / elevation. Lock **one per deck**; it anchors the aesthetic of the SVG layout itself (cards, dividers, spacing, corner radius, shadow use).+A **visual style** is how the deck **looks** — shape language, decoration density, whitespace rhythm, typographic character, texture / elevation. Resolve **one per deck**; Default locks it, while Quick keeps it only in active context. It anchors the aesthetic of the SVG layout itself (cards, dividers, spacing, corner radius, shadow use).-> **Styles carry NO fixed HEX and lock no palette.** Core color identity and recurring role behavior live in `design_spec.colors` / `spec_lock.colors` (confirmation `e`). A visual style describes how those anchors behave in SVG composition and may call for contextual tints, gradients, effects, or material transitions; it does not substitute an unrelated palette. Generated images follow the same anchor model through [`image-renderings/`](../image-renderings/). [`image-palettes/`](../image-palettes/) is legacy compatibility material only.+> **Styles carry NO fixed HEX and define no palette.** Default core color identity and recurring role behavior live in `design_spec.colors` / `spec_lock.colors` (confirmation `e`); Quick resolves equivalent palette anchors in active context. A visual style describes how those anchors behave in SVG composition and may call for contextual tints, gradients, effects, or material transitions; it does not substitute an unrelated palette. Generated images follow the same anchor model through [`image-renderings/`](../image-renderings/). [`image-palettes/`](../image-palettes/) is legacy compatibility material only.>-> A visual style is *not* a mode. **Visual style = how it looks; mode = how you argue** (see [`modes/_index.md`](../modes/_index.md)). Locked independently — any style pairs with any mode.+> A visual style is *not* a mode. **Visual style = how it looks; mode = how you argue** (see [`modes/_index.md`](../modes/_index.md)). Resolve them independently — any style pairs with any mode.---## 1. Catalog-Each style has its own file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. A preset lock reads that one file. A catalog-based `custom` reads every preset named in `visual_style_references`; a novel `custom` may omit references. Never glob the directory. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.+Each style has its own file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. Default reads the locked preset file; Quick reads the preset it resolves in active context. A catalog-based `custom` reads every preset actually used as a basis; a novel `custom` reads none. Never glob the directory. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.-> The **`visual_style` value is only ever a first-column `id`** (`swiss-minimal`, `editorial`, …). The "Paired rendering" column lists **§h image-rendering** names (`flat`, `minimalist-swiss`, `digital-dashboard`, …) — never lock one of those as the `visual_style`; they belong to confirmation h.+> The **`visual_style` value is only ever a first-column `id`** (`swiss-minimal`, `editorial`, …). The "Paired rendering" column lists **image-rendering** names (`flat`, `minimalist-swiss`, `digital-dashboard`, …) — never treat one of those as the `visual_style`. Default records rendering under confirmation h; Quick keeps the selected rendering only in active context and any required image manifest.>> The **`Illus.`** column is each style's spot-illustration propensity — `core` (illustration is intrinsic to the look), `supportive` (use where it lifts, restrained), or `sparse` (the style's lead visual competes; default off). It sets the **default lean** only, for when the user gives no steer: an explicit user request to use / skip illustrations overrides it either way, and `image_usage: none` always writes no illustration rows. Full per-style rule in each file's §6.@@ -92,17 +92,19 @@ Each style has its own file with: shape & decoration, typography character, colo## 3. Escape hatch — `custom`-Stage 2 always authors one visible, non-empty AI custom proposal beside the preset spectrum. Its paragraph names shape language, composition geometry (page-scale moves), decoration density, whitespace, typographic character, and texture — **no HEX, no color names as values**. The proposal is initially unselected and remains recommendation-only unless the user chooses it; a template-backed proposal must stay inside the inherited identity and confirmed application plan. When selected, record the edited aesthetic in the Design Spec first, then project `- visual_style: custom` plus `- visual_style_behavior:` to `spec_lock.md`. The candidate is mandatory; selecting `custom` remains a tail-case, not the default.+Default Stage 2 always authors one visible, non-empty AI custom proposal beside the preset spectrum. Its paragraph names shape language, composition geometry (page-scale moves), decoration density, whitespace, typographic character, and texture — **no HEX, no color names as values**. The proposal is initially unselected and remains recommendation-only unless the user chooses it; a template-backed proposal must stay inside the inherited identity and confirmed application plan. When selected, record the edited aesthetic in the Design Spec first, then project `- visual_style: custom` plus `- visual_style_behavior:` to `spec_lock.md`. The candidate is mandatory; selecting `custom` remains a tail-case, not the default.-**Mandatory — read every catalog source actually used**: If a custom proposal combines or borrows existing styles, name their exact ids in the visible proposal and read each corresponding file before synthesizing its shape, composition, typography, whitespace, and texture rules. Persist those ids as `visual_style_references`. Do not attach references merely because they are adjacent in the catalog. A genuinely new aesthetic with no catalog source omits `visual_style_references` and proceeds from its standalone behavior.+Quick does not author or display a candidate spectrum. It resolves the best-fit preset directly, or one custom behavior only when no preset fits, reads every catalog source actually used as a basis, and persists nothing.++**Mandatory — read every catalog source actually used**: If a custom direction combines or borrows existing styles, name their exact ids and read each corresponding file before synthesizing its shape, composition, typography, whitespace, and texture rules. Default persists those ids as `visual_style_references`; Quick retains them only in active context. Do not attach references merely because they are adjacent in the catalog. A genuinely new aesthetic reads no catalog source.---## 4. How to use-1. Strategist reads this index at confirmation `d. Layer 2`.-2. Preselect one style from the auto-selection table + the deck's vibe; separately author the visible AI custom proposal from §3.-3. Record the confirmed style and rationale in `design_spec.md`, then project `- visual_style: <name>` into `spec_lock.md`.-4. Executor reads `visual-styles/<locked-style>.md` for a preset. For `custom`, it reads every file listed in `visual_style_references` before applying `visual_style_behavior`; with no references, it applies the novel behavior directly. Never glob this directory.+| Active profile | Use |+|---|---|+| Default Generate | Strategist reads this index at confirmation `d. Layer 2`, authors the required spectrum/custom candidate, records the confirmed style in `design_spec.md`, and projects it to `spec_lock.md`; Executor reads the locked preset or exact custom references |+| Quick Generate | The current main agent reads this index, resolves the best-fit preset or one warranted custom behavior without interaction, reads only the exact preset source(s) actually used, and keeps the result in active context without Design Spec/lock |-**Lock scope**: deck-wide (one style per deck). It anchors taste as a **reference**, not a whitelist — pages may deviate with reason.+**Resolution scope**: deck-wide (one style per deck). It anchors taste as a **reference**, not a whitelist — pages may deviate with reason.diff --git a/skills/ppt-master/scripts/README.md b/skills/ppt-master/scripts/README.mdindex 3939d842..1f32e13d 100644--- a/skills/ppt-master/scripts/README.md+++ b/skills/ppt-master/scripts/README.md@@ -35,9 +35,10 @@ python3 scripts/animation_config.py scaffold <project_path> # optional object-lpython3 scripts/svg_to_pptx.py <project_path>```-After `init`, project-scoped Python CLIs automatically mirror their text-stdout/stderr into `<project_path>/validation/workflow.log`; invoke them-directly, without a logging wrapper.+After `init`, project-scoped Python CLIs automatically record their command+envelopes and bounded material outcomes in+`<project_path>/validation/workflow.log`; invoke them directly, without a+logging wrapper. The log does not copy the full console stream.Repository update:diff --git a/skills/ppt-master/scripts/docs/chart-recall.md b/skills/ppt-master/scripts/docs/chart-recall.mdindex 5f1352a7..9d78b8a8 100644--- a/skills/ppt-master/scripts/docs/chart-recall.md+++ b/skills/ppt-master/scripts/docs/chart-recall.md@@ -1,6 +1,6 @@# Chart Candidate Recall-`chart_recall.py` gives the Strategist a bounded deterministic shortlist. It exposes the full live catalog only when the caller explicitly requests semantic review. It reads `templates/charts/charts_index.json` on every invocation, so the catalog remains the only template registry.+`chart_recall.py` gives Default Strategist or the Quick Generate main agent a bounded deterministic shortlist. It exposes the full live catalog only when the caller explicitly requests semantic review. It reads `templates/charts/charts_index.json` on every invocation, so the catalog remains the only template registry.## Recall candidates@@ -28,23 +28,24 @@ Semantically review the bounded candidates. At `high` / `medium`, retain `no-tem| `semantic_fallback` | Full live catalog, present only with `--semantic-fallback`; requires semantic comparison || `no_template_match` | Explicit fallback; `allowed` stays false for `low` / `none` until `--semantic-fallback` is used |-The scorer treats the key and the summary's Pick clause as positive evidence and the Skip clause as negative evidence. A term found only in Skip cannot make a candidate eligible, and Skip matches explicitly reduce a candidate's score. Unicode input is NFKC-normalized before matching. The Strategist still applies semantic judgment: inspect the returned candidates, reject candidates whose Skip clause matches, and prefer the most specific valid structure. An empty or low-confidence shortlist requires one `--semantic-fallback` review only when the Strategist is about to keep `no-template-match`.+The scorer treats the key and the summary's Pick clause as positive evidence and the Skip clause as negative evidence. A term found only in Skip cannot make a candidate eligible, and Skip matches explicitly reduce a candidate's score. Unicode input is NFKC-normalized before matching. The active profile owner still applies semantic judgment: inspect the returned candidates, reject candidates whose Skip clause matches, and prefer the most specific valid structure. An empty or low-confidence shortlist requires one `--semantic-fallback` review only when the owner is about to keep `no-template-match`.## Validate selected keys-Validate every selected template key before writing `design_spec.md §VII` or `spec_lock.md page_charts`:+Validate every selected template key before Default writes `design_spec.md §VII` / `spec_lock.md page_charts` or Quick opens that key for immediate use:```bashpython3 skills/ppt-master/scripts/chart_recall.py validate line_chart quadrant_text_bullets```-The command is read-only. It exits `0` when every key exists and `1` when any key is absent. A `no-template-match` page appears in neither §VII nor `page_charts`; record its chosen fallback in the page's §IX `Visualization` / `Layout` instead.+The command is read-only. It exits `0` when every key exists and `1` when any key is absent. A Default `no-template-match` page appears in neither §VII nor `page_charts`; record its chosen fallback in the page's §IX `Visualization` / `Layout`. Quick keeps the fallback only in active context and writes no mapping artifact.## Selection boundary- Preserve the two-lens review: numeric/data pages and structural-information pages.-- Keep §VII as a positive selection list: record `Page | Template | Usage` for each selected key, and omit the whole section when no candidate is selected.-- Make `Usage` one concise page-local purpose, not geometry or execution instructions; derive `templates/charts/<key>.svg` from the key and keep detailed adaptation in §IX.+- Default keeps §VII as a positive selection list: record `Page | Template | Usage` for each selected key, and omit the whole section when no candidate is selected.+- Default makes `Usage` one concise page-local purpose, not geometry or execution instructions; derive `templates/charts/<key>.svg` from the key and keep detailed adaptation in §IX.+- Quick retains the selected key and immediate page purpose only in active context; do not create §VII, `page_charts`, or a substitute mapping file.- Never serialize `no-template-match`, an empty table, or a no-reference explanation into §VII.- Do not serialize returned summaries, paths, or runners-up into new §VII tables. Legacy wider tables remain readable.- Open the selected `<key>.svg` only as a reference for its mapped page; it does not lock type or geometry. Do not load unrelated catalog SVGs.diff --git a/skills/ppt-master/scripts/docs/project.md b/skills/ppt-master/scripts/docs/project.mdindex 1ea15c41..e04ea7bc 100644--- a/skills/ppt-master/scripts/docs/project.md+++ b/skills/ppt-master/scripts/docs/project.md@@ -157,15 +157,16 @@ python3 scripts/<tool>.py <project_path> <args...>```Their shared CLI bootstrap discovers the existing project log from the working-directory or command arguments. `workflow_transcript.py` mirrors text written-through configured `sys.stdout` / `sys.stderr` as tagged logical lines under a-UTC Python-command envelope; no outer launcher or second Python process is-used. Commands before project initialization are not backfilled. Binary-buffer-writes, hidden child output, and detached service activity are not copied;-Confirm UI and live preview retain detailed output in their component-`server.log` files. Their shared detached-process launcher disables automatic-workflow transcription in the long-running child while preserving the short-foreground launcher's own record.+directory or command arguments. `workflow_transcript.py` records a UTC command+envelope plus explicit error/failure and receipt/report lines, bounded+warning/OK/stderr samples, limited summary context, and per-run omission counts;+no outer launcher or second Python process is used. It leaves full output on+the original console instead of copying it into the audit log. Commands before+project initialization are not backfilled. Binary-buffer writes, hidden child+output, and detached service activity are not recorded; Confirm UI and live+preview retain detailed output in their component `server.log` files. Their+shared detached-process launcher disables automatic workflow recording in the+long-running child while preserving the short foreground launcher's own record.For a Python helper whose arguments and working directory do not identify theactive project, set the routing signal on the same command:@@ -188,11 +189,11 @@ Suitable notes include a material stage handoff or rework reason, auser-approved exception, or a manual recovery choice. Do not duplicateartifact contents, routine page progress, or private reasoning.-The transcript is append-only audit evidence. It is not a stage, quality, or-artifact authority and is not read during normal generation or resume. Inspect-it only when the user explicitly requests a run review. An automatic transcript-failure emits a warning but does not change the Python tool's result; an-explicit manual entry that cannot be written exits non-zero.+The log is append-only audit evidence. It is not a complete console transcript,+stage, quality, or artifact authority and is not read during normal generation+or resume. Inspect it only when the user explicitly requests a run review. An+automatic recording failure emits a warning but does not change the Python+tool's result; an explicit manual entry that cannot be written exits non-zero.## `project_utils.py`diff --git a/skills/ppt-master/scripts/project_management/cli.py b/skills/ppt-master/scripts/project_management/cli.pyindex 29e1cccd..dc2b0f7b 100644--- a/skills/ppt-master/scripts/project_management/cli.py+++ b/skills/ppt-master/scripts/project_management/cli.py@@ -314,7 +314,7 @@ class ProjectManager:"- `live_preview/`: browser preview runtime files and history (lock.json, server.log, edits.jsonl, annotations.jsonl)\n""- `sources/`: source materials and normalized markdown\n""- `analysis/`: machine-extracted intermediate analysis (PPTX intake, image_analysis.csv) — the pipeline's canonical must-read source/asset facts\n"- "- `validation/`: cold workflow transcript, SVG quality reports, and PPTX postflight audit reports\n"+ "- `validation/`: cold workflow audit log, SVG quality reports, and PPTX postflight audit reports\n""- `exports/`: final native DrawingML pptx deliverables only (timestamped); `_native_charts_tables.pptx` name with `--native-charts-and-tables`, `_narrated.pptx` name when narration audio is embedded\n""- `backup/<timestamp>/`: svg_output/ archive (always written in default-flow mode; safe to delete old timestamps)\n"),@@ -1081,7 +1081,7 @@ def build_parser() -> argparse.ArgumentParser:"--quick-generate",action="store_true",help=(- "Create svg_output plus the validation workflow transcript and "+ "Create svg_output plus the validation workflow audit log and ""omit README.md"),)@@ -1182,7 +1182,7 @@ def main(argv: list[str] | None = None) -> int:)except OSError as exc:print(- f"[WARN] Workflow transcript unavailable: {exc}",+ f"[WARN] Workflow audit unavailable: {exc}",file=sys.stderr,)return 0diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 065b1ebb..ec50ea96 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -187,7 +187,7 @@"max_tokens": 70000},"route.generate.quick-generate": {- "description": "Explicit non-interactive Generate path with conditional source/resource/template preparation and the complete flat SVG visual-construction authorities.",+ "description": "Explicit one-pass Generate path with active-context mode/style selection, conditional source/resource preparation, and complete flat SVG visual-construction authorities.","scope": "cumulative","include": ["bootstrap.routing"@@ -198,9 +198,30 @@"skills/ppt-master/references/artifact-ownership.md","skills/ppt-master/references/shared-standards-core.md","skills/ppt-master/references/svg-effects.md",- "skills/ppt-master/references/native-shape-authoring.md"+ "skills/ppt-master/references/native-shape-authoring.md",+ "skills/ppt-master/references/semantic-svg.md",+ "skills/ppt-master/references/modes/_index.md",+ "skills/ppt-master/references/visual-styles/_index.md",+ {+ "glob": "skills/ppt-master/references/modes/*.md",+ "exclude": [+ "*/_index.md"+ ],+ "select": 3,+ "load_event": "quick-mode",+ "registry": "modes"+ },+ {+ "glob": "skills/ppt-master/references/visual-styles/*.md",+ "exclude": [+ "*/_index.md"+ ],+ "select": 3,+ "load_event": "quick-visual-style",+ "registry": "visual-styles"+ }],- "max_tokens": 61000+ "max_tokens": 80000},"route.generate.quick-generate.template-fusion": {"description": "Quick Generate with the maximum Brand, Style, Layout, and Deck exact-root fusion loaded for flat authoring.",@@ -210,7 +231,7 @@"stage.generate.template.fusion-brand-style-layout-deck"],"files": [],- "max_tokens": 80000+ "max_tokens": 88000},"route.generate.quick-generate.topic-research": {"description": "Quick Generate with gap-targeted factual research before direct resource preparation and SVG authoring.",@@ -220,7 +241,7 @@"stage.generate.topic-research"],"files": [],- "max_tokens": 63000+ "max_tokens": 74000},"route.generate.quick-generate.icon": {"description": "Quick Generate with project-local bundled icon selection and synchronization.",@@ -231,7 +252,7 @@"files": ["skills/ppt-master/templates/icons/README.md"],- "max_tokens": 63000+ "max_tokens": 74000},"route.generate.quick-generate.in-hand-image": {"description": "Quick Generate with supplied, extracted, or placeholder image resources prepared before SVG authoring.",@@ -241,7 +262,7 @@"stage.generate.executor.image"],"files": [],- "max_tokens": 74000+ "max_tokens": 84000},"route.generate.quick-generate.formula": {"description": "Quick Generate with manifest-driven formula rendering and formula-image realization.",@@ -253,7 +274,7 @@"files": ["skills/ppt-master/scripts/docs/image.md"],- "max_tokens": 78000+ "max_tokens": 87000},"route.generate.quick-generate.ai-two-types": {"description": "Quick Generate with AI resource preparation, representative rendering inputs, and two local image types.",@@ -264,7 +285,7 @@"stage.generate.executor.image"],"files": [],- "max_tokens": 100000+ "max_tokens": 110000},"route.generate.quick-generate.web-image": {"description": "Quick Generate with web resource preparation, provenance, attribution, and image execution.",@@ -275,7 +296,22 @@"stage.generate.executor.web-image"],"files": [],- "max_tokens": 83000+ "max_tokens": 92000+ },+ "route.generate.quick-generate.chart": {+ "description": "Quick Generate with bounded chart recall, chart/table authoring, optional native-data metadata, and in-context coordinate verification before the final checker.",+ "scope": "cumulative",+ "include": [+ "route.generate.quick-generate",+ "stage.generate.executor.chart",+ "stage.generate.executor.native-data",+ "stage.generate.chart-authoring",+ "stage.generate.verify-charts"+ ],+ "files": [+ "skills/ppt-master/scripts/docs/chart-recall.md"+ ],+ "max_tokens": 105000},"route.generate.planning-image": {"description": "Generate-PPTX planning context after a non-none image source is proposed or confirmed, including the compact layout math and vocabulary.",@@ -1297,10 +1333,6 @@"glob": "skills/ppt-master/references/shared-standards.md","reason": "Compatibility router only; runtime load sets select the core and triggered modules directly."},- {- "glob": "skills/ppt-master/scripts/docs/chart-recall.md",- "reason": "Maintainer command contract; Strategist core carries the complete runtime recall procedure."- },{"glob": "skills/ppt-master/templates/scaffolds/*.md","reason": "Optional versioned tool-copy assets; normal Generate authoring reads the reference guides and writes complete artifacts from scratch."diff --git a/skills/ppt-master/scripts/workflow_transcript.py b/skills/ppt-master/scripts/workflow_transcript.pyindex 3b2a61bd..6fb846d0 100644--- a/skills/ppt-master/scripts/workflow_transcript.py+++ b/skills/ppt-master/scripts/workflow_transcript.py@@ -2,8 +2,8 @@"""PPT Master - Automatic Workflow Transcript-Internal runtime helper that mirrors a project-scoped Python tool's text-stdout/stderr into an existing project workflow log.+Internal runtime helper that records a project-scoped Python tool's command+envelope and material text outcomes in an existing project workflow log.Dependencies:None (standard library only)@@ -18,6 +18,7 @@ import sysimport threadingimport timeimport uuid+from collections import dequefrom collections.abc import Iterablefrom datetime import datetime, timezonefrom pathlib import Path@@ -27,6 +28,24 @@ WORKFLOW_LOG_RELATIVE_PATH = Path("validation/workflow.log")PROJECT_PATH_ENV = "PPT_MASTER_PROJECT_PATH"DISABLE_TRANSCRIPT_ENV = "PPT_MASTER_DISABLE_WORKFLOW_TRANSCRIPT"_EXCLUDED_ENTRYPOINTS = {"workflow_log.py"}+_CRITICAL_MARKERS = ("[ERROR]", "[FAIL]")+_ALWAYS_RETAIN_MARKERS = (+ "[POSTFLIGHT]",+ "[PPTX]",+ "[REPORT]",+ "[Done]",+ "[OK] Done",+)+_SUMMARY_MARKER = "[SUMMARY]"+_SUMMARY_STOP_MARKERS = ("[TIP]",)+_WARNING_MARKERS = ("[WARN]", "[WARNING]")+_OK_MARKER = "[OK]"+_WARNING_SAMPLE_LIMIT = 4+_OK_SAMPLE_LIMIT = 1+_STDERR_SAMPLE_LIMIT = 8+_STDERR_TAIL_LIMIT = 4+_CRITICAL_CONTEXT_LIMIT = 4+_SUMMARY_CONTEXT_LIMIT = 12_ACTIVE_TRANSCRIPT: _AutomaticTranscript | None = None@@ -74,7 +93,7 @@ def _find_project_root(argv: list[str]) -> Path | None:class _AutomaticTranscript:- """Append tagged logical lines without changing the owning tool."""+ """Append a bounded command/outcome audit without changing the owning tool."""def __init__(self,@@ -88,6 +107,16 @@ class _AutomaticTranscript:self.run_id = uuid.uuid4().hex[:12]self.started_clock = time.monotonic()self.pending = {"stdout": "", "stderr": ""}+ self.observed_lines = 0+ self.retained_lines = 0+ self.omitted_lines = 0+ self.warning_samples = 0+ self.ok_samples = 0+ self.stderr_samples = 0+ self.stderr_tail: deque[str] = deque(maxlen=_STDERR_TAIL_LIMIT)+ self.critical_context_remaining = 0+ self.summary_context_remaining = 0+ self.current_record_stream: str | None = Noneself.lock = threading.RLock()self.enabled = True@@ -96,14 +125,14 @@ class _AutomaticTranscript:self.enabled = Falsetry:self.original_stderr.write(- f"[WARN] Workflow transcript stopped: {exc}\n"+ f"[WARN] Workflow audit recording stopped: {exc}\n")self.original_stderr.flush()except (OSError, ValueError):passdef _write(self, text: str) -> None:- """Append and flush one complete transcript record."""+ """Append and flush one complete audit record."""if not self.enabled:returntry:@@ -120,6 +149,68 @@ class _AutomaticTranscript:f"argv: {json.dumps(self.argv, ensure_ascii=False)}\n")+ @staticmethod+ def _is_decoration(line: str) -> bool:+ """Return whether a non-empty line is only visual separator glyphs."""+ stripped = line.strip()+ return bool(stripped) and set(stripped) <= {"-", "=", "_"}++ def _should_retain(self, stream_name: str, line: str) -> bool:+ """Select a bounded set of explicit outcomes for the cold audit log."""+ stripped = line.strip()+ if not stripped or self._is_decoration(stripped):+ return False++ if _SUMMARY_MARKER in stripped:+ self.summary_context_remaining = _SUMMARY_CONTEXT_LIMIT+ return True+ if any(marker in stripped for marker in _SUMMARY_STOP_MARKERS):+ self.summary_context_remaining = 0+ return False+ if self.summary_context_remaining > 0:+ self.summary_context_remaining -= 1+ return True+ if any(marker in stripped for marker in _CRITICAL_MARKERS):+ self.critical_context_remaining = _CRITICAL_CONTEXT_LIMIT+ return True+ if self.critical_context_remaining > 0:+ self.critical_context_remaining -= 1+ return True+ if any(marker in stripped for marker in _ALWAYS_RETAIN_MARKERS):+ return True+ if any(marker in stripped for marker in _WARNING_MARKERS):+ if self.warning_samples < _WARNING_SAMPLE_LIMIT:+ self.warning_samples += 1+ return True+ return False+ if _OK_MARKER in stripped:+ if self.ok_samples < _OK_SAMPLE_LIMIT:+ self.ok_samples += 1+ return True+ return False+ if stream_name == "stderr" and self.stderr_samples < _STDERR_SAMPLE_LIMIT:+ self.stderr_samples += 1+ return True+ return False++ def _record_line(self, stream_name: str, line: str) -> None:+ """Record one material logical line or account for its omission."""+ if not line.strip():+ return+ self.observed_lines += 1+ if not self._should_retain(stream_name, line):+ self.omitted_lines += 1+ if stream_name == "stderr" and not self._is_decoration(line):+ self.stderr_tail.append(line)+ return+ if stream_name == "stderr":+ self.stderr_tail.clear()+ self.retained_lines += 1+ if self.current_record_stream != stream_name:+ self._write(f"{stream_name}:\n")+ self.current_record_stream = stream_name+ self._write(f" {line}\n")+def write_stream(self, stream_name: str, text: str) -> None:"""Buffer fragments and write complete logical lines."""if not text or not self.enabled:@@ -128,10 +219,7 @@ class _AutomaticTranscript:pending = self.pending[stream_name] + textwhile "\n" in pending:line, pending = pending.split("\n", 1)- self._write(- f"{_utc_timestamp()} "- f"[run={self.run_id} {stream_name}] {line}\n"- )+ self._record_line(stream_name, line)self.pending[stream_name] = pendingdef flush_stream(self, stream_name: str) -> None:@@ -142,10 +230,7 @@ class _AutomaticTranscript:returnpending = self.pending[stream_name]if pending:- self._write(- f"{_utc_timestamp()} "- f"[run={self.run_id} {stream_name}] {pending}\n"- )+ self._record_line(stream_name, pending)self.pending[stream_name] = ""def close(self) -> None:@@ -155,10 +240,17 @@ class _AutomaticTranscript:returnself.flush_stream("stdout")self.flush_stream("stderr")+ if self.stderr_tail:+ self._write("stderr-tail:\n")+ for line in self.stderr_tail:+ self._write(f" {line}\n")+ self.retained_lines += len(self.stderr_tail)+ self.omitted_lines -= len(self.stderr_tail)elapsed_ms = int((time.monotonic() - self.started_clock) * 1000)self._write(f"=== {_utc_timestamp()} END run={self.run_id} "- f"elapsed_ms={elapsed_ms} ===\n"+ f"elapsed_ms={elapsed_ms} output_lines={self.observed_lines} "+ f"retained={self.retained_lines} omitted={self.omitted_lines} ===\n")self.enabled = Falsetry:@@ -168,7 +260,7 @@ class _AutomaticTranscript:class _TeeTextIO:- """Mirror text writes while preserving the original stream interface."""+ """Forward text writes while offering them to the audit recorder."""def __init__(self,@@ -189,7 +281,7 @@ class _TeeTextIO:return writtendef writelines(self, lines: Iterable[str]) -> None:- """Mirror a sequence through the ordinary write path."""+ """Forward a sequence through the ordinary write path."""for line in lines:self.write(line)@@ -204,7 +296,7 @@ class _TeeTextIO:def install_auto_transcript(argv: list[str] | None = None) -> Path | None:- """Mirror a project-scoped Python command when its project log exists."""+ """Record a project-scoped Python command when its project log exists."""global _ACTIVE_TRANSCRIPTeffective_argv = list(sys.argv if argv is None else argv)@@ -231,7 +323,7 @@ def install_auto_transcript(argv: list[str] | None = None) -> Path | None:except OSError as exc:try:original_stderr.write(- f"[WARN] Workflow transcript unavailable ({log_path}): {exc}\n"+ f"[WARN] Workflow audit unavailable ({log_path}): {exc}\n")original_stderr.flush()except (OSError, ValueError):diff --git a/skills/ppt-master/templates/charts/README.md b/skills/ppt-master/templates/charts/README.mdindex b1c335a5..41330974 100644--- a/skills/ppt-master/templates/charts/README.md+++ b/skills/ppt-master/templates/charts/README.md@@ -6,11 +6,11 @@ This directory contains the standardized SVG visualization templates used by PPT[`charts_index.json`](./charts_index.json) is the single source of truth for the library: total count + one selection-rule `summary` per template (format: `"Pick for X. Skip if Y (use other_key)."`). [`chart_recall.py`](../../scripts/chart_recall.py) can recall a bounded candidate set from this live registry without maintaining a second category or keyword index.-For one planned page, provide 3-8 English semantic content-shape tags, then inspect the positive-scoring summaries plus the explicit `no-template-match` option. The requested limit is a cap, not a padding target, and lexical confidence never expands the output automatically. At `high` / `medium`, the Strategist may keep `no-template-match` when no bounded candidate fits. At `low` / `none`, a fitting candidate needs no expansion, but the Strategist must rerun the same query once with `--semantic-fallback` before keeping `no-template-match`. A selected result creates one `Page | Template | Usage` row in §VII and one matching `page_charts` entry; its path is derived from the key, while Usage is concise page-local intent and detailed adaptation remains in §IX. The negative result stays inside planning: it creates no §VII row or `page_charts` entry, and the chosen fallback is described in the page's §IX block. See [`chart-recall.md`](../../scripts/docs/chart-recall.md). The Generate workflow remains the authority for when Strategist uses this helper; maintainers may still open the registry directly when editing or auditing the catalog.+For one page, provide 3-8 English semantic content-shape tags, then inspect the positive-scoring summaries plus the explicit `no-template-match` option. The requested limit is a cap, not a padding target, and lexical confidence never expands the output automatically. At `high` / `medium`, retain `no-template-match` when no bounded candidate fits. At `low` / `none`, a fitting candidate needs no expansion, but rerun the same query once with `--semantic-fallback` before keeping `no-template-match`. In Default Generate, a selected result creates one `Page | Template | Usage` row in §VII and one matching `page_charts` entry; its path is derived from the key, while Usage is concise page-local intent and detailed adaptation remains in §IX. Quick Generate keeps the selected key/purpose only in active context and writes no mapping artifact. A negative result creates no row in either profile. See [`chart-recall.md`](../../scripts/docs/chart-recall.md). The Generate workflow remains the authority for when the active profile uses this helper; maintainers may still open the registry directly when editing or auditing the catalog.## Authoring contract-[`CHART_STYLE_GUIDE.md`](./CHART_STYLE_GUIDE.md) owns readable standalone SVG, semantic and structural fidelity, root-group bounds, data encoding, and neutral previews. The active Design Spec §IX and source data own the generated page's semantics; `spec_lock.md` owns stable project anchors. A selected SVG is a page-local structural reference, while its type, styling, frames, grouping, item count, capacity, and geometry remain adaptable.+[`CHART_STYLE_GUIDE.md`](./CHART_STYLE_GUIDE.md) owns readable standalone SVG, semantic and structural fidelity, root-group bounds, data encoding, and neutral previews. Default Design Spec §IX or the Quick active-context page decision plus source data own the generated page's semantics; Default `spec_lock.md` owns stable project anchors. A selected SVG is a page-local structural reference, while its type, styling, frames, grouping, item count, capacity, and geometry remain adaptable.## Visualization output model@@ -52,7 +52,7 @@ below. Conceptual diagrams and frameworks are never labeled as native charts.## Native Chart/Table replacement markers-Supported data chart templates include a `<g data-pptx-replace-with="chart">` marker by default, and pure text-grid table templates include the table form. These are capability examples, not project decisions: a generated page keeps and rewrites the marker only when its Design Spec §IX page block says `Native-ready: yes`; `no` omits it. Legacy specs may supply the decision in the matching §VII row when the page block has no field. The default SVG export path remains shape-based DrawingML. With `--native-charts-and-tables`, prepared groups become native PowerPoint Chart/Table objects from their JSON metadata. The legacy `--native-objects` spelling remains a compatibility alias.+Supported data chart templates include a `<g data-pptx-replace-with="chart">` marker by default, and pure text-grid table templates include the table form. These are capability examples, not project decisions: Default keeps and rewrites the marker only when its Design Spec §IX page block says `Native-ready: yes` (legacy §VII fallback only); Quick makes the same independent-object decision in active context before drawing. Otherwise omit it. The default SVG export path remains shape-based DrawingML. With `--native-charts-and-tables`, prepared groups become native PowerPoint Chart/Table objects from their JSON metadata. The legacy `--native-objects` spelling remains a compatibility alias.`--native-charts-and-tables` is an explicit native-object opt-in and may be lossy or visually normalized. Replacement-local value labels, center KPIs, callouts, quadrant notes, fixed axis ranges, and custom binning/splits may not survive native replacement unless represented by the payload. ChartEx palette entries do survive when supplied through valid payload colors, but this does not preserve every ChartEx style detail. Detectable information-loss risks should be reported as warnings, not handled by disabling an otherwise supported replacement marker. Review those warnings and compare the native-object export with the default shape-based export before delivery.@@ -71,4 +71,4 @@ Replacement payloads must include explicit `name`, `x`, `y`, `width`, and `heigh## Usage-Execution loads only selected keys under [`executor-chart.md`](../../references/executor-chart.md) §1 and reuses unchanged path + SHA. Files are named after the `key` field in `charts_index.json` (e.g. `column_chart.svg`, `quadrant_bubble_scatter.svg`). Templates are named by visual structure, not by business-model name — terms like SWOT, BCG, PEST, OKR, Porter's Five Forces, and Value Chain are translated into semantic content-shape tags before candidate recall.+Execution loads only selected keys under [`executor-chart.md`](../../references/executor-chart.md) §1 and reuses an unchanged file within the active context. Files are named after the `key` field in `charts_index.json` (e.g. `column_chart.svg`, `quadrant_bubble_scatter.svg`). Templates are named by visual structure, not by business-model name — terms like SWOT, BCG, PEST, OKR, Porter's Five Forces, and Value Chain are translated into semantic content-shape tags before candidate recall.diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex a4de1cf9..a7302fab 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -20,10 +20,11 @@ description: Generate PPTX route authority for source intake, planning, SVG authFor an explicit quick/fast, skip-strategy, or direct-SVG request, follow[`quick-generate.md`](./profiles/quick-generate.md). It runs applicable sourceconversion/research and project-local resource preparation, lets the current-agent decide content/visual/resource details in active context, then-hand-authors SVG, runs one lockless final checker, and exports the final PPTX.-It skips Strategist, Confirm UI, Design Spec/lock, the first-page gate, and-`finalize_svg.py`.+agent decide content/visual/resource details in one active context, then+hand-authors SVG, runs any selected capability-specific preparation, passes one+lockless final checker, and exports the final PPTX. It skips Strategist, Confirm+UI, Design Spec/lock, the first-page gate, and `finalize_svg.py`; it creates no+resumable design history, so context loss restarts the Quick run.Quick never enters Steps 3–4. When the request supplies at most one exact currentworkspace root for each Brand/Style/Layout/Deck kind, or the current@@ -34,12 +35,14 @@ uses free design. It never launches `confirm_ui/server.py`, reads the templatecatalog to choose on the user's behalf, or creates template-selection receipts;a bare template name, brand mention, or style description remains brief text.-**Hard rule — no implicit downgrade or page cap**: page count neither selects-nor blocks quick generation. Source preparation, images, icons, formulas, and-their manifests remain valid. All exporter capabilities remain available when-requested or agent-selected; use their existing prerequisites. Structured-Master/Layout template compilation still requires the default lock-backed-pipeline; Quick applies templates while authoring complete flat pages.+**Hard rule — no implicit capability downgrade or page cap**: page count neither+selects nor blocks quick generation. Source preparation, images, icons, native+shapes, charts/tables, formulas, mode/style references, and their triggered+operational manifests remain available. All exporter capabilities remain+available when requested or agent-selected; use their existing prerequisites.+Structured Master/Layout template compilation still requires the default+lock-backed pipeline; Quick applies templates while authoring complete flat+pages.### SVG Page-Design Boundary@@ -129,7 +132,8 @@ python3 ${SKILL_DIR}/scripts/project_manager.py init <project_name> --format <foProject initialization creates `<project_path>/validation/workflow.log` andrecords the initialization milestone. After the project exists, run eachproject-scoped Python tool normally. The shared CLI bootstrap automatically-mirrors its text stdout/stderr into that log; no wrapper command is required.+records its command envelope and a bounded set of material outcome lines in+that log; no wrapper command is required. Full console output is not copied.Detached Confirm UI and live-preview processes retain their detailed output intheir existing component logs.diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdindex 43957963..1e3c3da0 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -1,12 +1,13 @@----description: Generate profile for agent-decided source and resource preparation, direct SVG authoring, and final PPTX delivery without Strategist or confirmation artifacts.+description: One-pass Generate profile for agent-decided preparation, direct SVG authoring, and final PPTX delivery without durable planning or confirmation artifacts.---# Quick Generate Profile-> Generate-PPTX profile, not a top-level route. It removes the separate-> Strategist and confirmation phase; it does not remove the facts, resources,-> or export capabilities needed to build the final deck.+> Generate-PPTX profile, not a top-level route. The current main agent completes+> one uninterrupted run without a separate Strategist/confirmation handoff or a+> resumable design record. This removes interaction and traceability, not the+> facts, resources, or authoring capabilities needed to build the final deck.**Trigger**: the user explicitly requests quick/fast generation, asks to skipstrategy/confirmation, or directs the agent to proceed to SVG and export.@@ -20,16 +21,18 @@ Page count alone never activates or blocks this profile.|---|---|| Authority | Follow every explicit user requirement as stated; decide every unspecified choice directly without asking || Interaction | The current main agent decides content, design, resources, and implementation without Strategist, Confirm UI, or approval stops |+| Execution memory | Keep routine page, visual, and resource decisions only in the current active context; losing that context restarts Quick instead of reconstructing a plan from project files || Inputs | Any supported Generate input; convert/import sources and run bounded factual research when the input requires them || Templates | Directly validate and install at most one exact workspace root per kind supplied for this run; when none are supplied, use free design without catalog selection or Confirm UI || Resources | Prepare every project-local image, icon, formula, and required provenance/manifest artifact before the referencing SVG is authored |-| Planning artifacts | Do not author a root project `design_spec.md`, `spec_lock.md`, confirmation payloads, or a second persisted strategy; an installed `templates/design_spec.md` remains template input |+| Planning artifacts | Do not author a root project `design_spec.md`, `spec_lock.md`, confirmation payloads, or any substitute planning artifact; an installed `templates/design_spec.md` remains template input |+| Traceability | Operational resource manifests, checker reports, postflight, and bounded Python command/outcome audit entries may remain, but they do not record the AI's design reasoning or form a resumable generation history || Delivery | Hand-author the resolved SVG roster, run one lockless final checker, skip `finalize_svg.py`, and export the final native PPTX through `--quick-generate` |-**Hard rule — speed removes interaction, not material**: all ordinary source,-research, resource-preparation, analysis, and export capabilities remain-available when needed; the missing planning contract relaxes design constraints-only.+**Hard rule — speed removes interaction and durable planning, not capability**:+all ordinary source, research, visual-carrier, resource-preparation, analysis,+authoring, and export capabilities remain available when they serve the deck.+This is capability availability, not a requirement to use every carrier.Explicit user facts, wording, choices, exclusions, and permission boundariesstill win. For every unspecified routine choice, decide directly and continue;@@ -92,12 +95,13 @@ python3 ${SKILL_DIR}/scripts/project_manager.py init <project_name> \```It creates `svg_output/` plus the cold-`validation/workflow.log` Python-output transcript, and no root README. After+`validation/workflow.log` command/outcome audit log, and no root README. Afterthis command, run project-scoped Python tools directly; their shared CLI-bootstrap automatically mirrors stdout/stderr into the existing log. A concise-manual entry is allowed only for a material non-Python audit detail under-Generate Step 2's selective policy. Never read the transcript during ordinary-Quick execution; open it only for an explicit user-requested run review. Add+bootstrap records command envelopes, material tagged outcomes, bounded status+samples, and omission counts. A concise manual entry is allowed only for a+material non-Python audit detail under Generate Step 2's selective policy.+Never read the log during ordinary Quick execution; open it only for an+explicit user-requested run review. Addcapability inputs only when triggered; later tools create `exports/` and thedefault-path `backup/`. With source files, continue with Step 2`import-sources`; it creates the triggered input directories. Never scaffold a@@ -105,7 +109,11 @@ Design Spec or lock. Use a new path, or verify that an existing path's`svg_output/` is empty; Quick ignores any existing `design_spec.md` or`spec_lock.md`.-For the direct-template branch, resume+The audit log is an operational tool record only. It does not capture direct+SVG authoring, active-context design choices, or private reasoning and cannot be+used to resume or reconstruct a Quick run.++For the direct-template branch, continue with[`apply-template-workspace`](../stages/apply-template-workspace.md) afterinitialization against only the preflighted roots. The user's request is theselection authority; there is no template confirmation receipt or handoff. The@@ -114,13 +122,17 @@ the project-local asset pools. All later reads use that installed state, neverthe original roots.Before writing P01, read the installed template spec once and, for Layout/Deck,-inspect the relevant SVG prototypes. Resolve one transient application plan in-active context: apply Brand identity, Style direction/method, the selected-structure owner's useful prototype geometry, and Deck application context under-the existing segment precedence. Follow explicit instructions about literal or-visual-only use; otherwise decide which prototypes to use, skip, repeat,-reorder, or adapt from the current content. Persist no second plan. If no-template was installed, resolve the same design choices freely.+inspect the relevant SVG prototypes. Apply Brand identity, Style+direction/method, the selected structure owner's useful prototype geometry,+and Deck application context directly in the active context under the existing+segment precedence. Follow explicit instructions about literal or visual-only+use; otherwise decide which prototypes to use, skip, repeat, reorder, or adapt+while authoring. Persist no separate template-application artifact. If no+template was installed, make the same design choices freely.++**One-pass decision boundary**: resolve only what is needed to author this deck+in the current context. Do not print a strategy summary, create a planning+checkpoint, or persist a page/resource plan.Before writing P01, resolve in active context:@@ -129,26 +141,41 @@ Before writing P01, resolve in active context:- an ordinary body-content frame and a density judgment for every page, adapted to the canvas and any user / template / style geometry; use `anchor`, `dense`, `breathing`, or an equivalent active-context distinction instead of one uniform fill level;- for each page not bound to literal supplied geometry, a primary visual zone and page-scale composition direction tied to its core message; use cards or equal grids when the content relationship calls for them, not as the automatic page grammar;- when useful, one transient deck-level visual motif with an identity or- communication job, a recognizable invariant, and planned variation across+ communication job, a recognizable invariant, and deliberate variation acrossapplicable page roles; omit it when restraint serves the deck better;-- a transient resource roster with page, filename, purpose, visual intent,- acquisition path, crop behavior, and status. For an image/formula, include- its page relationship plus any subject position, focus, quiet region, or- overlay-safety cue that must exist before SVG authoring;+- the resource decisions needed for immediate preparation. Required operational+ image/formula manifests may carry filenames, page relationship, status, and+ generation/crop/focal cues, but do not create a general resource roster or an+ icon-to-page assignment;- the implementation path for each resource. An explicit user path wins;otherwise choose the registered automatic/default path without anotherinteraction.-Prepare only the resource paths that the roster triggers:+**Mandatory — capability scan, not a coverage quota**: for every page, consider+the complete carrier menu once and choose only the forms that communicate its+content best. A decision to use none of a carrier is valid; skipping the scan+because Quick is expected to be faster is not.++| Communication job | Available carrier |+|---|---|+| Real subject, place, product, evidence, atmosphere, or scene benefits from visual grounding | Supplied/extracted, web, AI, or sliced image |+| A compact semantic cue clarifies a category, process, KPI, state, navigation item, or real brand | Prepared project-local icon |+| Editable geometry can express a relationship, flow, emphasis, callout, symbol, or diagram | Basic SVG primitive, exact Office preset, Boolean result, then necessary freeform |+| Values encode comparison, trend, distribution, composition, relationship, or a text grid | Data chart or table, with optional native Chart/Table metadata when its object model is useful |+| Mathematical notation is clearer as typeset math than ordinary text | Rendered formula asset |+| Typography, spacing, and simple geometry already carry the message | Use no additional visual carrier |++Prepare only the resource paths needed by the decided pages:| Resource | Required preparation ||---|---|| Supplied/extracted image | Copy the selected file into `images/`; preserve its factual/provenance context and use the measured file rather than an invented substitute |-| Bundled/custom icon | Follow the [icon library contract](../../templates/icons/README.md), resolve the selected SVG under project `icons/`, and use `icon_sync.py` for bundled icons |+| Bundled/custom icon | Follow the [icon library contract](../../templates/icons/README.md), choose one coherent primary library, sync a useful project pool covering recurring semantics and likely page-local needs without assigning icons to pages, and choose from that prepared pool during SVG authoring || Formula | Follow the [`latex_render.py` contract](../../scripts/docs/image.md), write `images/formula_manifest.json`, run the renderer, and keep the rendered PNG under `images/` || AI image | Follow `image-base.md` + `image-generator.md`; keep `image_prompts.json` and its human-readable sidecar || Web image | Follow `image-base.md` + `image-searcher.md`; keep query/status data and `image_sources.json`, including any required on-slide attribution || Illustration slice | Generate or obtain the parent sheet, run `slice_images.py`, and place only the resulting element files |+| Data chart/table | Keep source values and the chosen page treatment in active context; load the chart/table authorities in §3 before drawing and write native replacement metadata only when selected |After image resources change, run `analyze_images.py` so`analysis/image_analysis.csv` reflects the files that SVG authoring will use.@@ -169,10 +196,20 @@ silently replace it with unrelated material.Always read the following fixed authoring references directly in one batch; donot route among them one file at a time:[`shared-standards-core.md`](../../references/shared-standards-core.md),-[`svg-effects.md`](../../references/svg-effects.md), and-[`native-shape-authoring.md`](../../references/native-shape-authoring.md). Do-not load `executor-base.md`: its persisted-plan prerequisites do not apply to-this profile. For any image/formula, always read+[`svg-effects.md`](../../references/svg-effects.md),+[`native-shape-authoring.md`](../../references/native-shape-authoring.md),+[`semantic-svg.md`](../../references/semantic-svg.md),+[`modes/_index.md`](../../references/modes/_index.md), and+[`visual-styles/_index.md`](../../references/visual-styles/_index.md). Resolve+one narrative mode and one visual style from explicit user/template requirements+or the current content, keep that choice only in active context, and read every+exact preset source actually used once. A genuinely novel custom direction+follows its resolved behavior without inventing a nearby preset.++Do not load `executor-base.md`: it owns Default's persisted-plan handoff,+first-page gate, and completion routing. Excluding that file is not a capability+exclusion; Quick loads the shared and conditional execution authorities here+directly. For any image/formula, always read[`executor-image.md`](../../references/executor-image.md),[`image-layout-spec.md`](../../references/image-layout-spec.md),[`image-layout-patterns.md`](../../references/image-layout-patterns.md), and@@ -181,9 +218,15 @@ this profile. For any image/formula, always readweb image. Load [`canvas-formats.md`](../../references/canvas-formats.md) onlyfor a non-default canvas.+| Deterministic trigger | Additional authority |+|---|---|+| Any data chart or text-grid table, including mini/inset charts and sparklines | [`executor-chart.md`](../../references/executor-chart.md); use bounded [`chart_recall.py`](../../scripts/docs/chart-recall.md) only when a reusable visualization reference would help |+| Preset pattern or selected PowerPoint-native Chart/Table replacement | [`native-data-interface.md`](../../references/native-data-interface.md) before drawing the object |+| Any data-driven chart geometry | [`verify-charts.md`](../stages/verify-charts.md) after the complete roster and before the one final checker |+Keep the core's shared visual-quality / leading defaults and `svg-effects.md` §6.1 Visual Job Router active while authoring. Explicit user/template requirements and the resolved style override compatible aesthetic defaults, never technical Required / Forbidden boundaries.-**Per-page execution anchors**: apply the transient core-message, typography-role, body-frame, density, and composition anchors resolved in §2 throughout the roster; they guide authoring without creating a persisted planning artifact.+**Per-page execution anchors**: apply the transient core-message, typography-role, body-frame, density, and composition anchors resolved in §2 while authoring; they guide the current run without creating a persisted planning artifact.Use one zero-padded filename width sized for the resolved roster, such as`01_cover.svg` through `12_end.svg` or `001_cover.svg` through `120_end.svg`.@@ -216,16 +259,22 @@ order. Use P01 as the visual anchor and continue directly through the remainingpages without a first-page checker or confirmation stop. When a motif wasresolved, reuse it selectively and vary scale, crop, density, position, orcontent interaction instead of cloning one ornament. Keep this choice only in-active context; create no planning artifact or approval stop. After the complete-roster exists, run the one final checker below. Apply other supporting tools and+active context; create no planning artifact or approval stop. After every page+exists, run the one final checker below. Apply other supporting tools andstages only when their capability is actually needed.+This is not a resume protocol. If the active context is lost before delivery,+start a clean Quick run rather than inferring an unfinished plan from the files+already present.+---## 4. Export-After every page and required referenced resource exists, run the lockless-final SVG check:+After every page and required referenced resource exists, run the Quick branch+of [`verify-charts`](../stages/verify-charts.md) when any data-driven chart was+authored. Complete all coordinate repairs first; then run the one lockless final+SVG check:```bashpython3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> \@@ -256,9 +305,11 @@ or lock.## ✅ Quick Generate Complete- [x] All required source/resource preparation is complete+- [x] One mode and visual style were resolved, and every catalog source actually used was read+- [x] Every page considered the complete visual-carrier menu without a coverage quota- [x] Resolved SVG pages and their project-local references exist+- [x] Every triggered capability-specific preparation and pre-checker verification completed- [x] The lockless final SVG quality report passes and matches the current SVGs-- [x] Every selected optional export capability completed- [x] One native PPTX exists under `exports/` or the explicit output path- [x] No Strategist, confirmation, root project Design Spec, or lock artifact was created- [ ] **Next**: Report the PPTX pathdiff --git a/skills/ppt-master/workflows/stages/apply-template-workspace.md b/skills/ppt-master/workflows/stages/apply-template-workspace.mdindex 11be3ec8..e36f3ae0 100644--- a/skills/ppt-master/workflows/stages/apply-template-workspace.md+++ b/skills/ppt-master/workflows/stages/apply-template-workspace.md@@ -84,7 +84,7 @@ Before copying a Deck or Layout workspace, inspect every SVG root and slot. Bran|---|---|| `brand` | Install `templates/` plus existing `images/` and `icons/`; ignore `exports/`. Identity is constrained; structure remains free. || `style` | Install `templates/design_spec.md` only. Ignore sibling project scaffolding and reject a library Style carrying asset/review payloads. Expose reusable direction/method without identity truth, page prototypes, or native structure. Default Style-only and Style + Brand derive `template_reuse_scope: style` and stay flat; Style + Layout/Deck follows the selected structure plan. Quick always realizes the resolved combination as flat pages. A Style workspace never activates visual review. |-| `layout` | Install the same portable roots. Expose the actual reusable structure; Default Strategist later inspects the prototypes, while Quick's current agent uses them to derive its transient flat authoring plan. |+| `layout` | Install the same portable roots. Expose the actual reusable structure; Default Strategist later inspects the prototypes, while Quick's current agent uses them for immediate flat authoring decisions in active context. || `deck` | Install the same portable roots. Expose descriptive application context, identity, structure, and the actual prototype roster; Default Strategist or Quick's current agent compares them with the current communication contract and content, then derives the applicable plan. |For a compatible legacy-flat package, route SVG/spec/non-bitmaps to project `templates/`, bitmaps to project `images/`, and declared icons to project `icons/`. Do not infer legacy Master/Layout semantics from the flat directory shape.@@ -131,7 +131,7 @@ Before Layout overrides Deck structure, compare Deck's reusable roles with LayouBefore Style overlays Deck guidance, verify that its method serves Deck's reusable context and fits the selected structure. On mismatch, require omitting Style or choosing a compatible Style/structure; never silently weaken a segment. Default final Stage 2 separately checks the result against the confirmed project contract; Quick checks it against the current request/content before authoring.-Field-level micro-adjustments such as a primary-color override are not workspace fusion. Default carries them into the normal final Stage-2 confirmation fields; Quick treats explicit adjustments as direct transient authoring constraints.+Field-level micro-adjustments such as a primary-color override are not workspace fusion. Default carries them into the normal final Stage-2 confirmation fields; Quick treats explicit adjustments as direct active-context authoring constraints.### 5.2 Same Kinddiff --git a/skills/ppt-master/workflows/stages/resume-execute.md b/skills/ppt-master/workflows/stages/resume-execute.mdindex a2188cac..0a237d58 100644--- a/skills/ppt-master/workflows/stages/resume-execute.md+++ b/skills/ppt-master/workflows/stages/resume-execute.md@@ -8,12 +8,12 @@ description: Main-pipeline control stage for resuming execution in a fresh chatThis stage is **context-independent**: it owns the execution session starting from a fresh chat — no upstream conversation context required. Persisted project artifacts replace the planning session's confirmation dialogue and image-acquisition history.-`validation/workflow.log` is a cold Python-output transcript with optional+`validation/workflow.log` is a cold command/outcome audit log with optionalimportant manual entries, not persisted planning state. Do not open or replayit while resuming. Use the real artifacts in Step 1 to establish current state;-inspect the transcript only when the user explicitly asks to review the prior-run. Run inherited Python commands normally; their shared CLI bootstrap records-stdout/stderr automatically.+inspect the log only when the user explicitly asks to review the prior run. Run+inherited Python commands normally; their shared CLI bootstrap records a+bounded material outcome selection automatically, not the full console stream.## When to Rundiff --git a/skills/ppt-master/workflows/stages/verify-charts.md b/skills/ppt-master/workflows/stages/verify-charts.mdindex db2b3ea0..09ec600c 100644--- a/skills/ppt-master/workflows/stages/verify-charts.md+++ b/skills/ppt-master/workflows/stages/verify-charts.md@@ -6,23 +6,49 @@ description: Conditional quality-gate stage for chart coordinate verification.> Conditional Generate-PPTX quality stage. 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 stage is **context-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.+In Default Generate this stage is **context-independent**: it reads+`design_spec.md` and the generated SVGs, then runs the calculator script. The+lockless Quick branch is deliberately context-dependent: run it in the same+active session from the page decisions just authored. If that context is lost,+restart Quick rather than inventing a page plan from finished files.## When to Run- The deck contains one or more data visualization charts where source values determine SVG geometry: bar lengths/heights, point positions, arc angles, polygon vertices, connector endpoints, bubble centers/radii, or flow widths/paths.-- SVGs are generated to `<project_path>/svg_output/` and `svg_quality_checker.py` has passed.+- SVGs are generated to `<project_path>/svg_output/`. Default enters from its declared quality-gate order; Quick runs this stage before its one lockless final checker.- Post-processing (`finalize_svg.py`, `svg_to_pptx.py`) has **not yet** run.The calculator has direct CLI models for simple bars, lines/scatter, pie/donut, radar, and grid layouts. Composite/derived charts are **not automatically out of scope**: if their geometry reduces to repeated direct calculations, include them as `decomposable-calc`; if the calculator has no layout model but the SVG geometry is still data-driven, include them as `manual-verify` so they are not silently skipped.----## Step 1: Build the page list from the design spec+## Step 1: Build the page list from the active profile authority-Read `<project_path>/design_spec.md` §IX Content Outline as the authoritative page roster and include every page whose `Visualization` explicitly declares SVG geometry driven by data values. Cross-check §VII when present to resolve a selected catalog key; absence from §VII means only that no reusable reference was selected. For legacy specs, a real §VII data-chart row may enumerate the page when its §IX block predates the explicit data-driven declaration. Classify each included page into exactly one mode:+| Active profile | Page-list authority |+|---|---|+| Default Generate | `design_spec.md §IX` plus the legacy §VII fallback below |+| Quick Generate | The still-active page decisions that produced the SVGs, cross-checked against every `chart-plot-area` marker; no Design Spec, lock, or substitute planning artifact is created |-Incidental microvisuals not promoted in the §IX page plan are not inferred into this list. If one requires coordinate verification, repair that page's §IX `Visualization` first so the Strategist-owned plan remains authoritative.+For Default, read `<project_path>/design_spec.md` §IX Content Outline as the+authoritative page roster and include every page whose `Visualization`+explicitly declares SVG geometry driven by data values. Cross-check §VII when+present to resolve a selected catalog key; absence from §VII means only that no+reusable reference was selected. For legacy specs, a real §VII data-chart row+may enumerate the page when its §IX block predates the explicit data-driven+declaration.++For Quick, enumerate every page the current agent just authored with+value-driven geometry, then search `svg_output/` once for `chart-plot-area` and+compare the marker pages one-for-one with that active list. Add a missing marker+before continuing; investigate an unexpected marker instead of silently adding+or dropping a page. Keep the list in active context only.++Classify each included page into exactly one mode:++Incidental microvisuals not promoted under the active profile authority are not+inferred into this list. Default repairs that page's §IX `Visualization` first;+Quick makes the promotion decision immediately in active context and updates+the SVG marker before verification.| Mode | `charts_index.json` keys | Notes ||------|--------------------------|-------|@@ -50,9 +76,13 @@ P11 11_share_split.svg type=pie mode=direct-calcP15 15_pareto.svg type=pareto mode=decomposable-calc```-If §VII is absent, continue from §IX; this is the normal state when all chart pages use custom structures. Do NOT guess from SVG content when §IX declares no data-driven page—that reintroduces the silent-skip failure this stage was built to eliminate.+In Default, if §VII is absent, continue from §IX; this is the normal state when+all chart pages use custom structures. Do not guess from SVG content when §IX+declares no data-driven page. In Quick, do not treat marker search as a+replacement for the still-active authoring decisions; use it as the required+cross-check.-If the filtered list is empty, output `verify-charts: spec declares no data-driven chart geometry, nothing to verify` and stop.+If the filtered list is empty, output `verify-charts: active profile declares no data-driven chart geometry, nothing to verify` and stop.---@@ -102,12 +132,17 @@ For each page in the Step 1 list:6. **Scale-aware comparison.** Compare calculator output against the SVG's existing coordinates. Before declaring a mismatch, verify that every calculator invocation used the same axis range, plot area, center/radius, start angle, or size scale that the SVG visually declares. For `calc bar`, the output header must show `Value scale: axis ticks (...)` when the SVG has explicit ticks; if it shows `auto (max*1.1)`, go back to step 4 and re-run with the correct `--value-range`. **Do NOT update the SVG with mismatched-scale output.** Only update SVG attributes when the scale is confirmed to match and coordinates genuinely differ. Update 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:+After updating any page, follow the active profile's checker order. Default+reruns its quality checker to confirm nothing broke:```bashpython3 skills/ppt-master/scripts/svg_quality_checker.py <project_path>```+Quick completes every chart comparison/repair first, then returns to+`quick-generate.md` §4 and runs its one lockless final checker. Do not insert a+checker call between Quick chart pages.+---## Stacked recipe@@ -211,7 +246,7 @@ python3 skills/ppt-master/scripts/svg_position_calculator.py calc line \**Bubble chart / quadrant bubble scatter** — partial calculator support:1. Use `calc line` to verify bubble centers (`cx/cy`) from the X/Y values and axis ticks.-2. Verify radius only if `design_spec.md`, `spec_lock.md`, or SVG comments declare a size scale such as `radius = sqrt(value) * k` or explicit min/max radius mapping.+2. Verify radius only if `design_spec.md`, `spec_lock.md`, the Quick active-context decision, or SVG comments declare a size scale such as `radius = sqrt(value) * k` or explicit min/max radius mapping.3. If the size scale is missing, record `radius=manual (scale missing)` and inspect relative ordering by hand.**Progress bar / gauge / funnel — formula-verify** (no calc call needed):@@ -231,7 +266,9 @@ python3 skills/ppt-master/scripts/svg_position_calculator.py calc line \## 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.+Output one line per page from the Step 1 list. Receipt count MUST equal Step 1+list length — that is the gate-closing evidence. Quick does not persist these+lines as a generation plan or resume record.```verify-charts: 03_market_share.svg | type=bar | mode=direct-calc | scale=0-100 (from ticks) | calc=ran | svg=updated@@ -258,5 +295,7 @@ verify-charts: 19_flow.svg | type=sankey | mode=manual-verify | link widths cons## After verification-Continue with [`generate-pptx`](../generate-pptx.md) Step 7. That authority owns-the serial commands, gates, and success criteria for post-processing and export.+Default continues with [`generate-pptx`](../generate-pptx.md) Step 7. Quick+returns to [`quick-generate`](../profiles/quick-generate.md) §4 for its one final+checker and direct export. Those authorities own the remaining serial commands,+gates, and success criteria.