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
docs(generate): define context-authored execution locks
hugohe31f12d459b443
diff --git a/docs/powerpoint-svg-mapping.md b/docs/powerpoint-svg-mapping.mdindex 60458483..e4e65e3a 100644--- a/docs/powerpoint-svg-mapping.md+++ b/docs/powerpoint-svg-mapping.md@@ -45,7 +45,7 @@ Each row owns one PowerPoint capability. The mapping cardinality is not always o| Object position and size | Absolute SVG coordinates and element bounds | `a:xfrm` offsets and extents | `Native-normalized` through coordinate conversion | Values must be finite and use the registered coordinate grammar || Z-order | SVG source order, back to front | PowerPoint shape-tree order | Reconstructed in shape-tree order | Do not rely on browser-only stacking behavior || Rotation, scale, translation, and mirror | Supported SVG transform forms | DrawingML transform or normalized geometry | `Native-normalized`; matrices may be decomposed | Skew and shear outside the registered transform contract are not accepted |-| Theme colors and fonts | Roles locked in `spec_lock.md`; canonical SVG uses the resolved values | Theme-aware tokens where an exact locked role can be retained; otherwise direct DrawingML values | `Native-stable` for registered roles | New pages must not invent unlocked colors, fonts, or text sizes |+| Theme colors and fonts | Stable roles anchored in `spec_lock.md`; canonical SVG uses those roles plus contextual page values | Theme-aware tokens where an exact anchor role can be retained; otherwise direct DrawingML values | `Native-stable` for registered roles/direct values | Core roles and structural sizes stay stable; contextual colors and export-safe one-off fonts are allowed, while invalid/unavailable values fail || PowerPoint-only package identity | `spec_lock.md` structure declarations and the package builder | Presentation, Master, Layout, relationship, and content-type registrations | Read back from package structure, not inferred from page appearance | Final-package read-back must match the declared roster |See [`canvas-formats.md`](../skills/ppt-master/references/canvas-formats.md) for supported canvases and [`shared-standards-core.md` §4.1](../skills/ppt-master/references/shared-standards-core.md#41-semantic-svg-marker-contract) for the normative root-`viewBox` contract.@@ -120,7 +120,7 @@ preset selection and authoring behavior are documented in| Mixed formatting within a line | Non-positioned `<tspan>` runs | DrawingML runs in one text frame | `Native-normalized`; registered run formatting remains editable | Positioning that changes frame geometry may split the result || Multiple paragraphs | Mergeable text/tspan structure | Multiple `a:p` paragraphs in one text frame | `Native-normalized` | Strict independently positioned lines may remain separate text boxes || Significant text whitespace | Exact `xml:space="default"` or `xml:space="preserve"` on `<text>`/`<tspan>` | Normalized or preserved U+0020 text in editable DrawingML runs | `Native-normalized`; inline run ownership is retained | Uses the project Chromium/SVG2 contract: LF/TAB become spaces, `default` collapses across runs, `preserve` retains them, and Unicode spacing characters remain literal; CSS `white-space` and legacy SVG 1.1 newline deletion are outside the mapping |-| Font family | Canonical `font-family` resolved against the project lock | Direct typeface or registered theme font | `Native-stable` within installed/font-substitution limits | Unlocked or unavailable fonts are reported by validation |+| Font family | Canonical `font-family` resolved as a structural lock role or contextual export-safe choice | Direct typeface or registered theme font | `Native-stable` within installed/font-substitution limits | Unavailable/unsafe fonts are reported; a contextual safe family is informational, not a lock failure || Font size | Finite unitless SVG pixels, for example `font-size="24"` | DrawingML hundredths of a point; `1 px = 0.75 pt` | `Native-stable` after unit conversion | Generated authoring uses only unitless px; registered legacy units are compatible input and warn, while unknown units error; DrawingML minimum is 1 pt || Font weight | Registered `font-weight` on `<text>`/`<tspan>` | DrawingML regular/bold run switch | `Native-normalized`; numeric weights collapse to the DrawingML boolean boundary | The exact value grammar and aliases belong to [`svg-effects.md` §6.7](../skills/ppt-master/references/svg-effects.md#67-advanced-text-treatments) || Italic, underline, and strike | Registered `font-style` / `text-decoration` on `<text>`/`<tspan>` | DrawingML italic, underline, and strike run properties | `Native-stable` for registered tokens | Unknown tokens are rejected; the exact grammar belongs to [`svg-effects.md` §6.7](../skills/ppt-master/references/svg-effects.md#67-advanced-text-treatments) |@@ -153,7 +153,7 @@ preset selection and authoring behavior are documented in| PowerPoint feature | Project representation | PPTX result | Import and fidelity | Validation boundary ||---|---|---|---|---|| No fill | `fill="none"` | `a:noFill` | `Native-stable` | Use lowercase canonical spelling in generated SVG |-| Solid fill | Locked canonical `fill="#RRGGBB"` | `a:solidFill`, with a theme token when the locked role is exactly reusable | `Native-stable` | Compatible color spellings may warn; malformed or unlocked generated values fail |+| Solid fill | Canonical `fill="#RRGGBB"`, either a named lock anchor or contextual page paint | `a:solidFill`, with a theme token when an anchor role is exactly reusable | `Native-stable` | Compatible spellings may warn; malformed colors fail, while valid contextual colors are informational || Fill transparency | Opaque fill plus `fill-opacity` | Native alpha | `Native-stable` | Generated values are finite unitless numbers from 0 to 1 || Linear gradient fill | Registered `<linearGradient>` in `<defs>` | Native `a:gradFill` | `Native-normalized` | Stops, coordinates, transforms, and references must follow the closed contract || Radial gradient fill | Registered `<radialGradient>` | Centered circular DrawingML gradient | `Approximate` | Review focal/radius-sensitive designs |diff --git a/docs/rules/prompt-style.md b/docs/rules/prompt-style.mdindex d9b2b01c..51e65dab 100644--- a/docs/rules/prompt-style.md+++ b/docs/rules/prompt-style.md@@ -49,7 +49,7 @@ Role definition for the **web image acquisition path**: translate Strategist int| `Run X.` | `You should typically run X because ...` || `Output: Y` | `The role outputs Y, which is important because ...` || `MUST come from Z` | `It is recommended to source from Z` |-| `Forbidden — values outside the lock` | `Anti-pattern: using values outside the lock` |+| `Forbidden — unresolved image references` | `Anti-pattern: broken image links` |**Hard rule**: if a sentence explains *why*, demote it to a single `> Note` blockquote line OR cut it. The agent does not need motivation, only behavior.@@ -77,9 +77,9 @@ Begin substantive paragraphs with a bolded short label. Reuse this fixed vocabul**Hard rule**: Before generating **each** SVG page, run:`python3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage`.-**Forbidden — values outside the lock**:-- Colors (fill / stroke / stop-color) MUST come from `colors`+**Forbidden — unresolved asset references**:- Icons MUST come from `icons.inventory`+- Images MUST resolve to declared project assets```**Choosing the strength** — before labeling a constraint, ask: *if a page violates it, does it objectively fail (text overlaps, overflows, misaligns, becomes unreadable, loses information, breaks across renderers), or could it merely look worse?*diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 9d3c9603..53c140b7 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -166,7 +166,7 @@ analysis/image_analysis.csv ────┘design_spec.md + spec_lock.md + images/ + icons/ + templates/└─> project_manager.py page-context <project> P<NN>- + [bounded repeated lock projection]+ + [bounded repeated anchor set]+ [current-page delta]+ [Design Spec / prototype / chart path + SHA fingerprints]├─> Executor -> svg_output/@@ -350,11 +350,11 @@ PPT Master uses **role switching within one main agent** rather than parallel su**Why role-specialized references, not one mega prompt.** Strategist runs in "negotiate with user" mode (open-ended, conversational, willing to back up); Executor runs in "produce strict XML" mode (no improvisation, no missing attributes). Mixing both into one prompt forces the model to hold incompatible discipline in the same turn — every prompt-engineering pathology of mode-mixing shows up. Splitting into per-role files lets each role load only what it needs and discard the rest.-**Strategist confirmation stage as the only blocking gate.** Strategist ends with one gate delivered in three dependency-ordered stages. Stage 1 confirms an open communication contract and canvas. Its prose boxes contain editable recommendations, but none requires a non-empty answer: confirmation persists the current text exactly, and a cleared value stays empty instead of falling back to the recommendation. Stage 2 is authored once from that contract and confirms the complete deck solution: reading mode, narrative mode, page count, coordinated visual system, image sources, and generated-image rendering. When a template is installed, Strategist also derives its page/prototype application plan from the actual workspace and current content and exposes that plan as editable natural-language prose; only the internal reuse/adherence modes stay hidden. Reading mode decides how meaning is carried by page, visuals, presenter, and notes; its cards do not present px values. The browser may apply the deterministic `reading mode → body baseline → unpinned role sizes` dependency locally, while manual size edits pin visible values. It never regenerates Stage 2. Stage 3 is authored once and contains production mechanics only: conditional AI acquisition, formula policy, generation mode, and spec refinement. The compatibility key `delivery_purpose` means reading mode. Generated images inherit the selected deck color roles directly; there is no independent image-palette choice. The final visible state in `confirm_ui/result.json` is authoritative—there is no hidden post-confirm repair. The complete communication contract remains in `result.json` and `design_spec.md`; project validation requires the compact `audience` / `objective` / `core_message` projection under `spec_lock.md ## communication` plus an `Audience move` in every §IX Slide block.+**Strategist confirmation stage as the only blocking gate.** Strategist ends with one gate delivered in three dependency-ordered stages. Stage 1 confirms an open communication contract and canvas. Its prose boxes contain editable recommendations, but none requires a non-empty answer: confirmation persists the current text exactly, and a cleared value stays empty instead of falling back to the recommendation. Stage 2 is authored once from that contract and confirms the complete deck solution: reading mode, narrative mode, page count, coordinated visual system, image sources, and generated-image rendering. When a template is installed, Strategist also derives its page/prototype application plan from the actual workspace and current content and exposes that plan as editable natural-language prose; only the internal reuse/adherence modes stay hidden. Reading mode decides how meaning is carried by page, visuals, presenter, and notes; its cards do not present px values. The browser may apply the deterministic `reading mode → body baseline → unpinned role sizes` dependency locally, while manual size edits pin visible values. It never regenerates Stage 2. Stage 3 is authored once and contains production mechanics only: conditional AI acquisition, formula policy, generation mode, and spec refinement. The compatibility key `delivery_purpose` means reading mode. Generated images inherit the selected deck color anchors directly; there is no independent image-palette choice. After the final wait, the final visible state in `confirm_ui/result.json` is read exactly once and consumed into `design_spec.md`, including production mechanics. Normal lock authoring and downstream execution do not reopen it. Project validation requires the compact `audience` / `objective` / `core_message` anchor set under `spec_lock.md ## communication` plus an `Audience move` in every §IX Slide block.**Image analysis goes through regenerated metadata, not pixels.** When images exist, Strategist and Executor use `analyze_images.py` output (`analysis/image_analysis.csv`) rather than directly opening image files. The CSV is a regenerated view over the live `images/` folder, not a durable cache. Re-running it before image-sensitive decisions is the staleness strategy: user images, extracted images, web images, AI outputs, formulas, and sliced elements all converge into the same measured fact table.-**Per-page context projection** is the long-deck anti-drift mechanism — full rationale in § Spec Propagation below.+**Per-page context projection** carries stable continuity anchors plus the current page delta — full rationale in § Spec Propagation below.---@@ -370,24 +370,24 @@ The Role Switching Protocol (mandated read of `references/<role>.md` before mode----## Spec Propagation: spec_lock.md as Execution Contract+## Spec Propagation: spec_lock.md as Contextual Execution ContractThe Strategist phase produces two artifacts that look redundant but serve different masters:- `design_spec.md` — human-readable narrative; the "why" of the deck (communication intent, audience outcome, narrative / template / visual rationale, page outline)-- `spec_lock.md` — machine-readable execution contract; the compact `audience` / `objective` / `core_message` communication projection plus the exact values Executor must literally use (HEX colors, font stacks, icon library, image resources, and structure mappings)+- `spec_lock.md` — machine-readable execution contract; the compact `audience` / `objective` / `core_message` communication anchors plus stable identity/reuse roles and routing values (core HEX/font roles, icon library, image resources, and structure mappings)-Why both? Without `spec_lock.md`, the Executor would derive exact values from narrative prose and context-compression drift would gradually mutate colors and fonts mid-deck. [Generate PPTX Step 6](../skills/ppt-master/workflows/generate-pptx.md#step-6-executor-phase) instead rebuilds a read-only `page-context` view before every page. The projector reads the current lock and the matching `design_spec.md` page block, then emits only the global execution values and current-page routing facts needed for authoring.+Why both? `design_spec.md` preserves the complete confirmed solution and rationale; `spec_lock.md` names the subset that must remain stable or routable across pages. It is authored from that Design Spec plus the page/resource/template context, not copied field by field from `result.json`. [Generate PPTX Step 6](../skills/ppt-master/workflows/generate-pptx.md#step-6-executor-phase) rebuilds a read-only `page-context` view before every page. The projector emits the stable anchors and current-page routing facts needed for authoring. Contextual tints, gradient/effect paints, and one-off export-safe display families remain page decisions; they need a lock row only after becoming a recurring semantic role.The view omits universal SVG/icon prohibitions already owned by the always-loaded Executor core and retains only project-specific forbidden rows. It selects images from the current page brief, explicit image-resource page assignments, and mirror prototype references. Images assigned elsewhere are excluded; any unresolved legacy image remains in a compatibility subset, and `confirmed-none` appears only when every locked image has a deterministic assignment elsewhere.The lock is also the per-page routing table. Beyond global colors and typography, it carries `page_rhythm` (`anchor` / `dense` / `breathing`), `page_charts` (which chart template should be adapted), image rows with placement/cropping contracts, and the locked `mode` / `visual_style` references that decide which execution rule files are loaded. A selected custom direction also carries its resolved `mode_behavior` / `visual_style_behavior`, and page-context projects those fields instead of leaving Executor with only the literal `custom` ids. `template_reuse_scope: mirror|layout` projects additionally carry `page_layouts` (which input template SVG each page inherits), unique `pptx_masters` / `pptx_layouts` definitions, and `page_pptx_layouts` assignments. `template_reuse_scope: style`, free-design, and brand-only projects use `pptx_structure.mode: flat` and omit those sections entirely rather than writing empty values. Empty entries elsewhere are meaningful signals: no chart or no image is often a design decision rather than missing data.-`page-context v2` separates bounded consistency state from large references. It deliberately repeats the compact global lock projection on every page as an anti-drift guard and binds it to `lock_source.sha256`. The current §IX brief, rhythm, image choice, and template/chart assignment form the page delta. The project/template Design Specs plus selected prototype and `templates/charts/<key>.svg` files appear only as scoped path/SHA fingerprints. Executor reads one of those files only when that fingerprint is absent from the active context or changed, then reuses the retained understanding. Flat pages have no prototype reference; structured pages reference the authoritative complete SVG. Manifests and text-slot sidecars remain derived tool diagnostics and are never injected into page authoring.+`page-context v2` separates bounded continuity state from large references. It deliberately repeats the compact global anchor set on every page and binds it to `lock_source.sha256`; that set is not a color/font allowlist. The current §IX brief, rhythm, image choice, and template/chart assignment form the page delta. The project/template Design Specs plus selected prototype and `templates/charts/<key>.svg` files appear only as scoped path/SHA fingerprints. Executor reads one of those files only when that fingerprint is absent from the active context or changed, then reuses the retained understanding. Flat pages have no prototype reference; structured pages reference the authoritative complete SVG. Manifests and text-slot sidecars remain derived tool diagnostics and are never injected into page authoring.`--record-usage` writes a derived, input-hashed compact-output snapshot for that page under `analysis/page-context/`. Token counting lazily uses `o200k_base`; a missing `tiktoken` installation records `tokens: null` without blocking execution. `page-context-report` excludes stale snapshots, reports compact page-context totals, and lists unique reference fingerprints. The once-loaded reference payloads and other session context remain intentionally unmeasured.-`update_spec.py` propagates a post-generation change in two coordinated steps: write the new value to `spec_lock.md`, then literal-replace it across every `svg_output/*.svg`. The tool's scope is deliberately narrow — only `colors.*` (HEX values, case-insensitive replacement) and `typography.font_family` (attribute-scoped). Other fields (font sizes, icons, images, canvas) are intentionally **not supported** because their replacements would need attribute-scoped or semantic awareness whose risk/benefit doesn't justify bulk propagation. For those, edit `spec_lock.md` and re-author the affected pages.+`update_spec.py` propagates an intentional deck-wide anchor change in two coordinated steps: write the new value to `spec_lock.md`, then literal-replace it across every `svg_output/*.svg`. The tool's scope is deliberately narrow — only `colors.*` (HEX values, case-insensitive replacement) and `typography.font_family` (attribute-scoped). Other fields (font sizes, icons, images, canvas) are intentionally **not supported** because their replacements would need attribute-scoped or semantic awareness whose risk/benefit doesn't justify bulk propagation. This reverse lock update is also valid when repeated contextual use is deliberately promoted into a named semantic role; it must not be used merely to empty an informational checker comparison. For unsupported fields, edit the owning artifact and re-author the affected pages.The tool refuses to back up: it relies on git for revert. Adding a backup mechanism would just duplicate git's job and create stale snapshots.@@ -409,7 +409,7 @@ Several architectural decisions shape this phase:**External refs during development, two divergent embedding strategies for derived outputs.** While editing in `svg_output/`, images are external file references — fast iteration, single-source-of-truth replacement. Step 7 always creates both downstream forms: `svg_final/` Base64-inlines assets into self-contained SVGs that an IDE or browser can inspect and users may manually insert as SVG pictures; native pptx instead reads `svg_output/`, copies bitmaps into the PPTX media folder, and uses `<a:srcRect>` to express cropping. The split exists because Base64 inside DrawingML works but bloats file size 3-4×, while file-referenced bitmaps are PowerPoint's native idiom for which `<a:srcRect>` is the canonical crop expression. Manual PowerPoint Convert to Shape is not a third conversion route and is not covered by the project contract.-**One rendering lock, inherited deck colors, and per-image composition.** When a deck includes AI-generated images, Stage 2 confirms the deck-wide `rendering` inside each coordinated design direction. Exact image colors are not a second decision: Image_Generator reads the ordinary HEX roles already locked in `spec_lock.md colors`. It then combines that single rendering and shared color truth with a per-image `type` or hero-page composition derived from each resource's purpose. This keeps style and color coherent without asking the user to approve the same color system twice. A rendering whose material language cannot work with the selected deck roles should not be offered; after confirmation it may change texture, lighting, and color proportions, but it must not replace, tint, warm-grade, or invent HEX values.+**One rendering lock, inherited deck anchors, and per-image composition.** When a deck includes AI-generated images, Stage 2 confirms the deck-wide `rendering` inside each coordinated design direction. Image colors are not a second user decision: Image_Generator starts from the core HEX roles in `spec_lock.md colors`, then interprets them with the completed Design Spec and each resource's `type` or hero-page composition. Rendering may derive coherent tints, material colors, lighting transitions, and atmospheric hues while preserving the core role meanings; it must not replace the deck identity with an unrelated image-only palette. A repeated derived tone may be promoted into a named lock role.---diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 70cb378b..177e8d4f 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -167,7 +167,7 @@ analysis/image_analysis.csv ────┘design_spec.md + spec_lock.md + images/ + icons/ + templates/└─> project_manager.py page-context <project> P<NN>- + [有界重复的 lock 投影]+ + [有界重复的执行锚点集]+ [当前页 delta]+ [Design Spec / 原型 / 图表的路径与 SHA 指纹]├─> Executor -> svg_output/@@ -346,7 +346,7 @@ PPT Master 用的是**单主代理内的角色切换**,不是并行子代理**为什么是角色专属 reference 而不是一个超大 prompt。** Strategist 跑的是「跟用户协商」模式(开放式、对话式、可以回退),Executor 跑的是「产出严格 XML」模式(不准即兴、不准漏属性)。把两者塞进同一个 prompt,强迫模型在同一个 turn 里持守相互矛盾的纪律——所有混合模式的 prompt 工程病灶都会出现。按角色拆开,每个角色只加载它需要的、扔掉其他。-**策略师确认阶段是唯一的阻塞 gate。** Strategist 阶段以一个按依赖排序的三阶段 gate 作为核心决策点。第一阶段确认开放式沟通契约与画布。其中的文本框承载可编辑推荐,但没有任何一项要求非空:确认时按当前文本原样保存,清空后的值保持为空,不会回退到推荐内容。第二阶段只从该契约计算一次并确认完整 PPT 方案:阅读模式、叙事 mode、页数、成套视觉系统、图片来源和生成图渲染。存在模板时,Strategist 还会根据真实工作区和当前内容推导页面/原型应用计划,并以可编辑的自然语言文本展示;只有内部复用/遵循模式保持隐藏。阅读模式决定信息由页面、视觉、讲者和备注如何共同承担,其选项卡不展示 px 数值。浏览器可以在本地执行确定性的「阅读模式 → 正文基准 → 未锁定角色字号」联动;手动编辑字号即锁定可见值,不会重新计算第二阶段。第三阶段也只计算一次,并且只处理生产机制:条件式 AI 图片获取路径、公式策略、生成模式与规范精修。JSON 为兼容保留 `delivery_purpose` 键,但用户侧统一称为阅读模式。生成图直接继承已选 PPT 色彩角色,不再单设图片调色选择。最终 `confirm_ui/result.json` 中的可见状态是权威输入,不存在确认后的隐藏修正。完整沟通契约继续保留在 `result.json` 与 `design_spec.md`;项目校验要求 `spec_lock.md ## communication` 下存在紧凑的 `audience` / `objective` / `core_message` 投影,并要求 §IX 每个 Slide block 都有 `Audience move`。+**策略师确认阶段是唯一的阻塞 gate。** Strategist 阶段以一个按依赖排序的三阶段 gate 作为核心决策点。第一阶段确认开放式沟通契约与画布。其中的文本框承载可编辑推荐,但没有任何一项要求非空:确认时按当前文本原样保存,清空后的值保持为空,不会回退到推荐内容。第二阶段只从该契约计算一次并确认完整 PPT 方案:阅读模式、叙事 mode、页数、成套视觉系统、图片来源和生成图渲染。存在模板时,Strategist 还会根据真实工作区和当前内容推导页面/原型应用计划,并以可编辑的自然语言文本展示;只有内部复用/遵循模式保持隐藏。阅读模式决定信息由页面、视觉、讲者和备注如何共同承担,其选项卡不展示 px 数值。浏览器可以在本地执行确定性的「阅读模式 → 正文基准 → 未锁定角色字号」联动;手动编辑字号即锁定可见值,不会重新计算第二阶段。第三阶段也只计算一次,并且只处理生产机制:条件式 AI 图片获取路径、公式策略、生成模式与规范精修。JSON 为兼容保留 `delivery_purpose` 键,但用户侧统一称为阅读模式。生成图直接继承已选 PPT 色彩锚点,不再单设图片调色选择。最终等待结束后,流程只读取一次 `confirm_ui/result.json` 的完整最终状态,并把全部确认值(含生产机制)写入 `design_spec.md`;正常的 lock 编写与下游执行不再回读它。项目校验要求 `spec_lock.md ## communication` 下存在紧凑的 `audience` / `objective` / `core_message` 锚点,并要求 §IX 每个 Slide block 都有 `Audience move`。**图片分析走重算元数据,不读像素。** 当项目里存在图片时,Strategist 和 Executor 使用 `analyze_images.py` 的输出(`analysis/image_analysis.csv`),而不是直接打开图片文件。这个 CSV 是基于当前 `images/` 目录重算出来的视图,不是持久缓存。每次做图片敏感决策前重跑分析,就是它的防陈旧策略:用户图、抽取图、网络图、AI 图、公式图和切片图最终都会汇入同一张可度量事实表。@@ -366,24 +366,24 @@ Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workfl----## 设计规范的传播:spec_lock.md 作为执行契约+## 设计规范的传播:spec_lock.md 作为上下文执行契约Strategist 阶段产出两份看起来冗余但服务不同对象的产物:- `design_spec.md` —— 人类可读叙述;deck 的「为什么」(沟通意图、受众变化、叙事 / 模板 / 视觉理由、页面大纲)-- `spec_lock.md` —— 机器可读执行契约;包含紧凑的 `audience` / `objective` / `core_message` 沟通投影,以及 Executor 必须**字面照搬**的精确值(HEX 颜色、字体栈、图标库、图片资源与结构映射)+- `spec_lock.md` —— 机器可读执行契约;包含紧凑的 `audience` / `objective` / `core_message` 沟通锚点,以及跨页稳定的身份/复用角色和路由值(核心 HEX/字体角色、图标库、图片资源与结构映射)-为什么两份都要?没有 `spec_lock.md`,Executor 就会从叙述文本推导精确值,上下文压缩漂移会在长 deck 中逐渐扭曲色值和字体。[Generate PPTX Step 6](../../skills/ppt-master/workflows/generate-pptx.md#step-6-executor-phase) 改为每页生成前重建只读 `page-context` 视图:投影器读取当前 lock 和 `design_spec.md` 中对应的页面 block,只输出创作该页所需的全局执行值和逐页路由事实。+为什么两份都要?`design_spec.md` 保存完整的确认方案与理由;`spec_lock.md` 只命名必须跨页稳定或参与路由的子集。它根据 Design Spec 与页面/资源/模板上下文编写,不再逐字段复制 `result.json`。[Generate PPTX Step 6](../../skills/ppt-master/workflows/generate-pptx.md#step-6-executor-phase) 会在每页生成前重建只读 `page-context` 视图,只输出稳定锚点与逐页路由事实。局部色阶、渐变/效果色与一次性的可导出展示字体属于页面判断;只有形成复用语义后才需要写入 lock。该视图省略 Executor core 已经恒定加载的通用 SVG/图标禁令,只保留项目专属 forbidden 行。图片从当前页 brief、图片资源表中的显式页分配和 mirror 原型引用中选择;已分配给其他页面的图片会被排除,仍无法归属的 legacy 图片保留在兼容子集中,只有所有锁定图片都能确定归属到其他页面时才记录 `confirmed-none`。这份 lock 同时也是逐页路由表。除了全局配色和字体,它还承载 `page_rhythm`(`anchor` / `dense` / `breathing`)、`page_charts`(某页应适配哪个图表模板)、带放置/裁剪契约的图片行,以及决定加载哪些执行规则文件的 `mode` / `visual_style`。选定 custom 方向时,lock 还承载已消解的 `mode_behavior` / `visual_style_behavior`,page-context 会把它们投影给 Executor,而不是只留下字面上的 `custom` id。`template_reuse_scope: mirror|layout` 项目额外承载 `page_layouts`(每页继承哪个输入模板 SVG)、唯一的 `pptx_masters` / `pptx_layouts` 定义,以及 `page_pptx_layouts` 页面分配;`template_reuse_scope: style`、自由设计和 brand-only 项目使用 `pptx_structure.mode: flat`,那些段整段省略,而不是写成空值。其余字段的空值本身仍是信号:没有图表、没有图片,很多时候是设计选择,而不是漏填。-`page-context v2` 把有界的一致性状态与大型引用分开。它有意在每页重复紧凑的全局 lock 投影,作为防漂移护栏,并用 `lock_source.sha256` 绑定版本。当前 §IX brief、节奏、图片选择和模板/图表分配构成逐页 delta。项目/模板 Design Spec、选中的原型,以及 `templates/charts/<key>.svg` 只以带 scope 的路径/SHA 指纹出现。只有该指纹不在当前执行上下文中或 SHA 已变化时,Executor 才读取文件一次;后续页面直接复用已有理解。flat 页面没有原型引用;structured 页面引用权威的完整 SVG。manifest 与 text-slot sidecar 只保留为派生工具诊断,不注入页面创作上下文。+`page-context v2` 把有界的连续性状态与大型引用分开。它有意在每页重复紧凑的全局锚点集,并用 `lock_source.sha256` 绑定版本;这个集合不是颜色/字体白名单。当前 §IX brief、节奏、图片选择和模板/图表分配构成逐页 delta。项目/模板 Design Spec、选中的原型,以及 `templates/charts/<key>.svg` 只以带 scope 的路径/SHA 指纹出现。只有该指纹不在当前执行上下文中或 SHA 已变化时,Executor 才读取文件一次;后续页面直接复用已有理解。flat 页面没有原型引用;structured 页面引用权威的完整 SVG。manifest 与 text-slot sidecar 只保留为派生工具诊断,不注入页面创作上下文。`--record-usage` 在 `analysis/page-context/` 下写入当前页的派生快照,记录输入 hash 和紧凑 stdout 的实测大小。token 计数按需加载 `o200k_base`;没有安装 `tiktoken` 时写入 `tokens: null`,但不阻塞执行。`page-context-report` 排除过期快照,汇总紧凑 page-context,并列出唯一引用指纹;一次加载的大型引用 payload 与其他会话上下文有意不纳入统计。-`update_spec.py` 把生成后的修改用两个协调步骤传播:把新值写入 `spec_lock.md`,然后字面替换到每一份 `svg_output/*.svg`。工具的范围**故意收得很窄**——只支持 `colors.*`(HEX 值,大小写不敏感替换)和 `typography.font_family`(属性级)。其他字段(字号、图标、图片、画布)**有意不支持**——它们的替换需要属性级或语义级理解,风险/收益不值得做批量传播。这些情况手动改 `spec_lock.md` 然后重做受影响的页面。+`update_spec.py` 用两个协调步骤传播一次有意的 deck 级锚点修改:把新值写入 `spec_lock.md`,然后字面替换到每一份 `svg_output/*.svg`。工具的范围**故意收得很窄**——只支持 `colors.*`(HEX 值,大小写不敏感替换)和 `typography.font_family`(属性级)。其他字段(字号、图标、图片、画布)**有意不支持**——它们的替换需要属性级或语义级理解,风险/收益不值得做批量传播。当重复出现的上下文值被明确提升为具名语义角色时,反向回写 lock 同样合理;但不能只为了清空 checker 的信息提示而扩充 lock。其他字段应修改其权威产物并重做受影响页面。工具拒绝做备份:依赖 git 回滚。加备份机制只是重复 git 的工作,还会留下过时快照。@@ -405,7 +405,7 @@ Strategist 阶段产出两份看起来冗余但服务不同对象的产物:**开发期外部引用,下游分叉成预览与原生导出两套嵌入策略。** 在 `svg_output/` 里编辑时,图片是外部文件引用——快速迭代、单点替换。随后分成两种表达:`svg_final/` 走 Base64 内联,产出一组不依赖外部位图文件的自包含 SVG,供 IDE、浏览器和手工插入为 SVG 图片;native PPTX 则把位图复制进 PPTX 的 media 文件夹,用 `<a:srcRect>` 表达裁剪。分叉的理由是职责不同:前者服务视觉预览,后者服务项目转换器生成的可编辑 DrawingML。`svg_final/` 不作为 PowerPoint 手工“转换为形状”的兼容源。-**一份渲染锁、直接继承 PPT 色彩、逐图确定构图。** 当 deck 包含 AI 生成图片时,Stage 2 会在每套成套设计方向中确认 deck 级 `rendering`。图片颜色不再形成第二次决策:Image_Generator 直接读取 `spec_lock.md colors` 已锁定的普通 PPT 色彩角色,再把统一渲染、统一色彩真相与每项资源按用途推导的 `type` 或 hero-page 构图组合起来。这样既能保持风格与色彩一致,也不会让用户重复确认同一套颜色。若某种渲染的材质语言无法由已选 PPT 色彩角色支撑,就不应成为候选;一旦确认,它可以改变纹理、光照与颜色占比,但不得替换、调暖、调冷或另造 HEX。+**一份渲染锁、继承 PPT 色彩锚点、逐图确定构图。** 当 deck 包含 AI 生成图片时,Stage 2 会在每套成套设计方向中确认 deck 级 `rendering`。图片颜色不再形成第二次用户决策:Image_Generator 从 `spec_lock.md colors` 的核心 HEX 角色出发,再结合完整 Design Spec 与每项资源按用途推导的 `type` 或 hero-page 构图。渲染可以在不改变核心角色语义的前提下,按上下文派生色阶、材质色、明暗过渡与氛围色;不得用一套无关的图片专属调色替换 deck 身份。重复使用的派生色可以提升为具名 lock 角色。---diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.mdindex 6b42bd20..51404c75 100644--- a/skills/ppt-master/references/artifact-ownership.md+++ b/skills/ppt-master/references/artifact-ownership.md@@ -18,9 +18,9 @@ Global artifact ownership rules for PPT Master projects.| `analysis/<stem>.identity.json` | Native deck identity facts | Canvas, theme palette/fonts, observed usage | Read selectively when detailed identity facts are needed || `analysis/<stem>.slide_library.json` | Native PPTX structure facts | Text slots, geometry, native tables, native chart caches, SmartArt nodes/connections | Direct PPTX workflows use as native fill/structure contract || `analysis/image_analysis.csv` | Regenerated image fact view | Measured facts about the current `images/` folder | Re-run `analyze_images.py` before reading image facts after changes |-| `design_spec.md` | Strategist design authority | Human-readable design intent, outline, rationale, and resource plan authored from the final confirmation plus source analysis | Strategist writes and audits it against every confirmed field before lock projection; humans and later roles read it for intent |-| `spec_lock.md` | Execution projection | Machine-readable colors, typography, icons, images, page rhythm, charts, `template_reuse_scope`, and the route's PowerPoint structure mode; mirror/layout template routes additionally own input prototypes, the Master roster, and the complete page-to-Master/Layout mapping | Strategist projects the route-specific contract from the audited Design Spec without making another design decision; `page-context` deliberately repeats its compact global projection per page as an anti-drift guard and adds current-page routing values. Executor may add a new adaptive Layout identity only on a structured mirror/layout route while authoring the page that first needs it. |-| `project_manager.py page-context` stdout | Derived per-page context | Read-only model-facing lock projection + current-page delta + fingerprints for large references | Generate immediately before each page without `--bundle`; never edit or persist it as a replacement source of truth. `global` is the bounded repeated lock guard. `reference_set` carries path/SHA/load policy for project/template Design Specs and selected prototype/chart SVGs, but never appends their payloads. |+| `design_spec.md` | Strategist design authority | Human-readable design intent, outline, rationale, resource plan, and confirmed production mechanics authored from the final confirmation plus source analysis | Strategist consumes the final confirmation once, writes and audits every confirmed field here, then later roles read this artifact instead of reopening `result.json` |+| `spec_lock.md` | Execution anchor and routing contract | Machine-readable stable color/type roles, icons, images, page rhythm, charts, `template_reuse_scope`, and the route's PowerPoint structure mode; mirror/layout template routes additionally own input prototypes, the Master roster, and the complete page-to-Master/Layout mapping | Strategist authors the route-specific anchors from the audited Design Spec plus current project/page/template context. `page-context` repeats that compact anchor set per page and adds current-page routing values. Page-local color/font choices need no lock row; Executor may promote a recurring semantic color/type role or add a new adaptive Layout identity while authoring the first page that establishes the reuse. |+| `project_manager.py page-context` stdout | Derived per-page context | Read-only model-facing anchor set + current-page delta + fingerprints for large references | Generate immediately before each page without `--bundle`; never edit or persist it as a replacement source of truth. `global` is the bounded repeated anchor set, not a whitelist of every valid page-local value. `reference_set` carries path/SHA/load policy for project/template Design Specs and selected prototype/chart SVGs, but never appends their payloads. || `analysis/page-context/P<NN>.usage.json` | Derived context telemetry | Actual compact page-context size plus hashes of owning inputs/references | `page-context --record-usage` deterministically replaces that page's snapshot; `page-context-report` summarizes current snapshots and unique references. Use token data to evaluate context cost, never as content or an execution contract. || `images/` | Runtime image pool | User, extracted, AI, web, formula, slice, EMF/WMF assets | Step 5 writes here; `analysis/image_analysis.csv` derives from current contents || `icons/` | Project icon inventory | Icons copied by `icon_sync.py` for this project | Executor uses locked project icons; exporter may fall back to global library only as documented |@@ -34,7 +34,7 @@ Global artifact ownership rules for PPT Master projects.| `<import_workspace>/authoring-svg-flat/` | Optional complete-page verification IR | Self-contained page composition view with its own summary and provenance manifest | Generate only from an explicitly requested `svg-flat/`; use to verify composition, while layered `authoring-svg/` remains the canonical editable source || `<import_workspace>/icons/imported/` | Imported vector pool | One canonical copy of every factored vector subtree | Authoring SVGs reference `data-icon="imported/<name>"`; vector inventories retain source refs so expansion re-establishes IR identity || `confirm_ui/recommendations.json` | Confirmation proposal | Strategist-authored confirmation payload | Confirm UI reads; rewritten between Stage 1, Stage 2, and Stage 3 |-| `confirm_ui/result.json` | Confirmation result | User-confirmed values | Strategist treats final result as authoritative over recommendations |+| `confirm_ui/result.json` | Confirmation result | Persisted user-confirmed input evidence | Generate Step 4 reads the final object once into active context; Strategist consumes it completely into `design_spec.md`. Normal downstream work does not reopen it; fresh recovery may read it once when no retained final state exists. || `svg_output/` | Page-design author source | Main-agent handwritten SVG pages containing the complete visible design | Quality checker and native PPTX export read this as the canonical visual/page-layout source; templates and locks do not add missing visible objects at export || `notes/total.md` | Speaker-note source | Complete notes before splitting | Step 6 writes; Step 7.1 splits || `notes/slide_*.md` | Split notes | Per-slide notes generated from `total.md` | Derived by `total_md_split.py` |@@ -54,7 +54,7 @@ Global artifact ownership rules for PPT Master projects.| Content values | Main pipeline text, tables, chart values, and SmartArt node wording come from content-type files in `sources/` (`.md` / `.markdown` / `.txt` / `.csv` / `.tsv` / `.json` / `.jsonl` / `.yaml` / `.yml`), not from `slide_library.json`. || Sources read policy | In `sources/`, read content-type files (`.md` / `.markdown` / `.txt` / `.csv` / `.tsv` / `.json` / `.jsonl` / `.yaml` / `.yml`) and judge by content — a `.json` / `.csv` may be core content or just data. Exclude known sidecars: `*.conversion_profile.json` and `*_files/image_manifest.json`. `analysis/` facts (`source_profile.json`, `<stem>.slide_library.json`) are read per Step 4 / direct-PPTX workflow, not in the `sources/` content scan. || PPTX structure | `slide_library.json` owns native geometry, slot facts, and SmartArt layout/relationships for direct PPTX workflows. |-| Design contract | Final confirmation → audited `design_spec.md` → projected `spec_lock.md`. Executor may apply projected `Template Application` prose to visible template content, but never infer lock values from it. On divergence, repair the lock from the Design Spec unless the Design Spec itself fails confirmation fidelity. |+| Design contract | Final confirmation is read once → complete audited `design_spec.md` → context-authored `spec_lock.md` anchors/routing. Executor may apply projected `Template Application` prose to visible template content, but never replace confirmed identity with an independent direction. On divergence, repair the lock from the Design Spec/current context unless the Design Spec itself fails confirmation fidelity. || Flat packaging authority | Free-design, brand-only, and `template_reuse_scope: style` declare `pptx_structure.mode: flat` and omit `pptx_masters`, `pptx_layouts`, `page_pptx_layouts`, and `page_layouts`. `svg_output/` owns the complete Slide-local visual design without root Master/Layout identity, fixed-layer ownership, or placeholder metadata. Export materializes one clean project-owned Master plus one Blank Layout, applies the locked theme defaults, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. || Template structure authority | `template_reuse_scope: mirror|layout` uses `page_layouts` for each page's authoring-input prototype. `pptx_masters` / `pptx_layouts` own the unique reusable output definitions, while `page_pptx_layouts` owns page assignment. Strict keeps the prototype contract; adaptive may create a new Layout definition during page authoring and updates its assignment immediately. Mirror additionally preserves literal visuals/text topology; layout allows project-controlled reflow/re-skinning. Unused definitions may register without a published Slide. Templates validate provenance but never add missing visible page objects during export. || Fact classes | External facts resolve through `sources/*.facts.json`; invented demo KPIs/targets/internal ratios are labeled `scenario` in `design_spec.md §IX` and visibly in the page. Never promote scenario data into the external fact registry. |@@ -67,7 +67,7 @@ Global artifact ownership rules for PPT Master projects.| Post-processed SVG | `svg_final/` is disposable, must be rebuilt in Step 7.2, and serves only as a self-contained visual preview / manually insertable SVG picture. || 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 `confirm_ui/result.json` or chat confirmation overrides recommendations and is the mandatory input contract for `design_spec.md`; `spec_lock.md` is derived only after that Design Spec passes confirmation-fidelity review. |+| Confirmation | Final `confirm_ui/result.json` or chat confirmation overrides recommendations and is consumed once as the mandatory input contract for `design_spec.md`; `spec_lock.md` is authored only after that Design Spec passes confirmation-fidelity review. |**Forbidden - mixed ownership**: Do not copy chart values from Markdown into `analysis/` by hand, do not edit `svg_final/` as the source of a fix, do not edit imported lossless SVGs instead of their authoring IR, and do not treat `design_spec.md` prose as a replacement for `spec_lock.md`.diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 72acc6cf..7ba6eace 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -39,9 +39,9 @@ Before the first SVG, retain `design_spec.md`: continuous execution reuses plannpython3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage```-`global` deliberately repeats the sub-1000-token lock projection as an anti-drift guard; `lock_source.sha256` binds its version. `page_context` is the current §IX/resource/template/chart delta. For every `reference_set` entry—project/template Design Spec or selected prototype/chart SVG—reuse an in-context path + SHA; read it once only when absent or changed.+`global` deliberately repeats the sub-1000-token cross-page anchor set; `lock_source.sha256` binds its version. These anchors preserve identity and recurring semantics but do not enumerate every legal color or font. `page_context` is the current §IX/resource/template/chart delta. For every `reference_set` entry—project/template Design Spec or selected prototype/chart SVG—reuse an in-context path + SHA; read it once only when absent or changed.-Use lock values literally and optional `Template Application` from the retained Design Spec. The delta overrides neither facts nor constraints. After an approved change, rerun the command and reload only changed references. Deprecated `--bundle` is a compatibility no-op.+Use named lock roles literally when that role applies, and use optional `Template Application` from the retained Design Spec. Choose contextual page-local values from the Design Spec, style, content, and current composition rather than forcing every object into a lock row. The delta overrides neither facts nor constraints. After an approved change, rerun the command and reload only changed references. Deprecated `--bundle` is a compatibility no-op.**Source facts**: The page delta carries page intent and routing facts, not the complete source corpus. Read the relevant `sources/` content and resolve listed `Fact IDs` from `sources/*.facts.json` when the page needs concrete claims, quotes, names, or data.@@ -69,11 +69,11 @@ The §IX wording and sourced facts remain authoritative. Do not rewrite, drop, o**Missing field in an existing lock**: follow [`failure-recovery.md`](../workflows/governance/failure-recovery.md) §2.-**Forbidden — values outside the lock**:+**Execution anchors and contextual values**:-- Colors (fill / stroke / stop-color) MUST come from `colors`- Icons MUST come from `icons.inventory`; library MUST equal `icons.library`-- Font family from `typography`: use role override (`title_family` / `body_family` / `emphasis_family` / `code_family`) if declared, else fall back to `font_family`+- Core color roles in `colors` retain their confirmed meaning. Use them directly for recurring semantic roles. Page-local tints, gradient stops, shadow/glow paints, transparency composites, and one-off illustration colors may be chosen from context when they preserve the deck's visual identity, contrast, and semantic color behavior.+- Structural title/body typography uses its declared role override (`title_family` / `body_family` / `emphasis_family` / `code_family`) or `font_family` fallback. A page-local display treatment may use another installed/export-safe family when the content and locked visual style justify it; promote it to a named `*_family` role only when it recurs.- Font sizes follow a ramp anchored on `typography.body`. Structural roles use their locked size deck-wide; recurring feature roles such as lead, pull quote, or hero number need their own lock slot. Never resize one role page by page or inherit a template placeholder size.- **Core message ≥ `body`**: map the page's primary claim to locked `lead` / `subtitle`, never below body. Footnotes, page numbers, and credits use locked `footnote` / `annotation`; do not invent smaller sizes.- **Write locked px verbatim, with at most two decimals.** Do not substitute familiar pt-style numbers or emit long precision tails.@@ -81,7 +81,7 @@ The §IX wording and sourced facts remain authoritative. Do not rewrite, drop, o- Images MUST reference files listed under `images`; no invented filenames- Formula PNGs are images with `Acquire Via: formula`; place a `Rendered` file only from its listed path, use the normal placeholder for `Needs-Manual`, and never recreate the formula as text.-If a page needs a value not in `spec_lock.md`, surface it — do not silently invent one. When an intentional deck-wide or recurring color, type role/size, icon, or image is approved, extend `spec_lock.md` **before** drawing the first affected object, regenerate that page's context bundle, and only then author the page; do not draw with a temporary hardcoded value and retroactively silence drift warnings.+When an intentional value becomes deck-wide or gains a recurring semantic role, extend `spec_lock.md` **before the next affected page**, regenerate that page's context, and use the named role thereafter. A genuinely page-local color, gradient/effect paint, or export-safe display family stays in the SVG and does not require a lock edit. Never expand the lock merely to silence the checker's informational anchor comparison. Icons, images, structural font roles, and recurring type sizes keep their explicit inventory/role rules.**Per-page layout rhythm — `page_rhythm` section**:@@ -116,8 +116,8 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, consider one page-specific polygon/path that expresses the relationship before stacking generic arrows. This does not override §3.0 when one literal stock shape is the semantic object.- **Reference — create depth with restraint**: use rhythm, spacing, typography, accent bars, and subtle tints before shadows. Reserve lift for a few genuinely floating elements; keep peer grids, dividers, and body containers flat.- **Phased generation** (recommended):- 1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Use layout judgment for chart marks during the draft. **MUST embed plot-area markers** per [`executor-chart.md`](./executor-chart.md) §2.1 on every chart page — coordinate calibration is a post-generation step (see [`verify-charts`](../workflows/stages/verify-charts.md)) that depends on these markers — and **native object metadata** per [`executor-chart.md`](./executor-chart.md) §2.2 on every eligible data-chart page. **Reach for native presets** per §3.0 as you draw each page: a block arrow, chevron, banner/ribbon, callout, standard flowchart node, or star is authored through `preset_shape_svg.py` at draw time — decided by the object's intent as you create it, never by scanning finished paths, and never committed to a bare `<path>`/`<polygon>` when a preset expresses it (a gradient fill/stroke or a pattern fill is the one paint exception — keep those ordinary SVG). **First-page gate (Mandatory)**: after completing the first page, run `python3 scripts/svg_quality_checker.py <project_path> --stage first-page` and fix every error before drawing page 2. This mode checks P01 only. After it passes, draw P02 through the last page without checker calls.- 2. **Quality Check Gate**: only after every planned SVG exists, run `python3 scripts/svg_quality_checker.py <project_path> --stage final --json` on `svg_output/`. Any `error` (banned/unsupported features, invalid values, unresolved references, viewBox mismatch, etc.) MUST be fixed on the offending page before proceeding — regenerate and re-check. Every `warning` is advisory: it never sends the page back for required modification, never authorizes automatic rewriting of compatible user syntax, and needs no acknowledgement/disposition line. Recommendation warnings describe the generated-SVG default; fidelity/quality warnings may be surfaced when material, while the existing input remains releasable. Prototype-identical diagnostics are recorded as `inherited`, source conversion losses as `source-import`, changed/new advisories as `introduced`, and release failures as `blocking` in `validation/svg_quality_report.json`. If release truly depends on a condition, it belongs in `errors`. On success, use the exit status and terminal summary; do not open or `cat` the complete JSON into model context. Read only targeted fields for failure investigation or an explicit audit request. Do NOT defer error handling to after `finalize_svg.py` — finalize rewrites SVG and masks some violations.+ 1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Use layout judgment for chart marks during the draft. **MUST embed plot-area markers** per [`executor-chart.md`](./executor-chart.md) §2.1 on every chart page — coordinate calibration is a post-generation step (see [`verify-charts`](../workflows/stages/verify-charts.md)) that depends on these markers — and **native object metadata** per [`executor-chart.md`](./executor-chart.md) §2.2 on every eligible data-chart page. **Reach for native presets** per §3.0 as you draw each page: a block arrow, chevron, banner/ribbon, callout, standard flowchart node, or star is authored through `preset_shape_svg.py` at draw time — decided by the object's intent as you create it, never by scanning finished paths, and never committed to a bare `<path>`/`<polygon>` when a preset expresses it (a gradient fill/stroke or a pattern fill is the one paint exception — keep those ordinary SVG). **First-page gate (Mandatory)**: after completing the first page, run `python3 scripts/svg_quality_checker.py <project_path> --stage first-page --json` without output filtering. Review the whole P01 issue set, make one consolidated edit pass for every error and any selected warnings, then perform one verification rerun. If it still fails, treat that complete output as the next batch; never check between individual fixes. After it passes, draw P02 through the last page without checker calls.+ 2. **Quality Check Gate**: only after every planned SVG exists, run `python3 scripts/svg_quality_checker.py <project_path> --stage final --json` on `svg_output/` without `tail` / `head` / `grep` filtering. One run already reports all pages. Review its complete issue set, fix every `error` plus any selected advisory warnings in one consolidated edit pass, then perform one verification rerun. If it still fails, its complete output begins the next batch cycle; never use checker calls to discover or fix one next issue at a time. Every `warning` is advisory: it never sends the page back for required modification, never authorizes automatic rewriting of compatible user syntax, and needs no acknowledgement/disposition line. Recommendation warnings describe the generated-SVG default; fidelity/quality warnings may be surfaced when material, while the existing input remains releasable. Prototype-identical diagnostics are recorded as `inherited`, source conversion losses as `source-import`, changed/new advisories as `introduced`, and release failures as `blocking` in `validation/svg_quality_report.json`. If release truly depends on a condition, it belongs in `errors`. On success, use the exit status and terminal summary; do not open or `cat` the complete JSON into model context. If terminal output is truncated on failure, read only the relevant issue arrays from the report written by that same run. Do NOT defer error handling to after `finalize_svg.py` — finalize rewrites SVG and masks some violations.3. **Logic Construction Phase**: after SVGs pass the quality check, batch-generate speaker notes for narrative continuity.### 3.0 Native Preset Shape Selection@@ -253,7 +253,7 @@ ls skills/ppt-master/templates/icons/simple-icons/ | grep github## 5. Font Usage-Source of truth: `spec_lock.md typography`. Use `font_family` as default; override per role with `title_family` / `body_family` / `emphasis_family` / `code_family` if declared. LaTeX formulas that Strategist rendered are PNG images, not a `code_family` text role.+Structural typography anchors come from `spec_lock.md typography`. Use `font_family` as default; override recurring roles with `title_family` / `body_family` / `emphasis_family` / `code_family` if declared. Contextual one-off display type remains allowed under §2.1 when export-safe. LaTeX formulas that Strategist rendered are PNG images, not a `code_family` text role.**Missing required field — `typography.font_family`** → stop and return to Generate Step 4 / [`strategist.md`](strategist.md) §6.2 to repair `spec_lock.md`; do not infer a stack from `design_spec.md`.diff --git a/skills/ppt-master/references/executor-chart.md b/skills/ppt-master/references/executor-chart.mdindex ac929775..08be54d4 100644--- a/skills/ppt-master/references/executor-chart.md+++ b/skills/ppt-master/references/executor-chart.md@@ -84,7 +84,7 @@ catalog or reusable template; normal content edits would make it stale.- 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 visually inside one of those compositions still gets its own marker.- 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` carries the series HEX values already used on the page (from `spec_lock.colors`).+- 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.- 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.diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.mdindex f3fbea94..620c550f 100644--- a/skills/ppt-master/references/image-generator.md+++ b/skills/ppt-master/references/image-generator.md@@ -28,7 +28,7 @@ AI images exist to serve the deck's communication goal. Pick whatever combinatio**Hard rule — only what's actually hard**:-- Same `deck_rendering` + same locked deck color roles for every image in the deck+- Same `deck_rendering` + same core deck color anchors/semantic behavior for every image in the deck- HEX codes and color names are rendering guidance — never visible text in the image- Long body copy / data points / bulleted lists / long quotes stay in SVG (improving them later means regenerating the image, which is expensive)- **In-image text is only for words that will not need editing later** — visual keywords, decorative lettering, mood words. Editable text (titles that may be reworded, subtitles, dates, authors, captions, body) belongs in SVG. Changing one in-image word costs an image regeneration; one SVG word costs a keystroke.@@ -40,15 +40,15 @@ Everything else is the AI's judgment per page. No mandated padding, no type-lock## 2. Style and Composition Inputs-Every AI image uses one deck-wide rendering, the deck's already-locked color roles, and a per-image type / composition. Only rendering is a separate image-direction decision.+Every AI image uses one deck-wide rendering, the deck's stable color anchors/semantic behavior, and a per-image type / composition. Only rendering is a separate image-direction decision.| Dimension | Decides | When fixed ||---|---|---|| **Rendering** | Visual style family (vector / sketch-notes / 3d-isometric / corporate-photo / …) | Once per deck — every AI image in the deck shares one rendering |-| **Deck colors** | The exact background / primary / accent / secondary-accent / text roles from `spec_lock.md colors`; these are consumed directly, not reconfirmed | Already locked in Stage 2 |+| **Deck colors** | Core background / primary / accent / secondary-accent / text anchors from `spec_lock.md colors`, interpreted with the Design Spec and per-image context; these are not reconfirmed | Anchored after Stage 2 || **Type** | What the image's internal composition skeleton looks like — geometric layout of a local infographic block (infographic / flowchart / framework / matrix / cycle / funnel / pyramid / comparison / timeline / map / scene). Only applies to `page_role: local`; for `page_role: hero_page`, describe composition with §4.1 primitives instead of picking a type. | Per image |-> Rendering decides *how the image is drawn* (line quality, texture, depth). Color instructions come from the deck roles: background / secondary background usually dominate, primary carries main forms, and accents stay scarce. Adjust those proportions to the page role, but never invent or substitute HEX.+> Rendering decides *how the image is drawn* (line quality, texture, depth). Color instructions begin from the deck roles: background / secondary background usually dominate, primary carries main forms, and accents stay scarce. Adjust proportions and derive coherent lighting/material/tint transitions for the image context; do not replace the deck's identity with an unrelated image-only palette.### 2.1 Where to find each dimension@@ -80,7 +80,7 @@ read_file references/image-type-templates/_index.md### Step 2 — Resolve deck-wide rendering + deck colors-**Primary path — Strategist already locked rendering and ordinary deck colors in `spec_lock.md colors`**:+**Primary path — Strategist already recorded rendering and core deck color anchors in `spec_lock.md colors`**:```image_rendering: vector-illustration@@ -89,7 +89,7 @@ primary: #1E3A5Faccent: #D4AF37```-Use them directly. Do not create another image-color choice and do not change HEX to suit a rendering.+Use them as identity anchors. Do not create another user-facing image-color choice. The rendering and image subject may derive coherent tonal transitions, material colors, lighting, and atmospheric hues when the context requires them, while the core roles keep their established meaning.**Hard rule — `custom` escape hatch**: when `image_rendering` is `custom`, do not read a preset rendering file. Splice `image_rendering_behavior` into the prompt. The deck color-role rows remain authoritative.@@ -100,7 +100,7 @@ This fallback covers a missing key only. An empty or invalid value stops for loc| Signal | Maps to ||---|---|| `design_spec.md d. Style` mode + descriptor | Rendering (consult renderings `_index.md` auto-selection table) |-| Existing `spec_lock.md colors` rows | Deck color-role source; never replace them from `design_spec.md` |+| Existing `spec_lock.md colors` rows | Deck color anchors; interpret them with the completed `design_spec.md`, never replace confirmed identity from a second palette || Existing `spec_lock.md icons.library` | Sanity check: chosen rendering should be compatible with the icon library's visual weight |If rendering inference surfaces multiple candidates, pick the first; do not present another choice after confirmation.@@ -114,7 +114,7 @@ Then read the **single resolved** rendering file. It gives you:- The 80-120 word style paragraph (rendering)- Two ready-to-paste rendering snippets (fewshot)-Derive color behavior directly from the available roles: background / secondary background carry roughly 55–70% of the image field, primary carries main forms, and accent / secondary accent together usually stay below 10%. A rendering may justify a different balance, but all colors still come from the lock and decorative text colors must remain readable.+Derive color behavior from the available roles and image context: background / secondary background usually carry most of the field, primary carries main forms, and accent / secondary accent remain selective. A rendering may justify a different balance and coherent derived tones; decorative text colors must remain readable. Add a new lock role only when that derived color becomes a reusable cross-image semantic token.### Step 3 — Per-image type + assembly@@ -126,7 +126,7 @@ For each `Acquire Via: ai` row in `design_spec.md §VIII`:4. `read_file references/image-type-templates/<type>.md` (only if not already read — types are commonly reused across images in one deck)5. **Assemble the prompt** by combining:- The rendering's style paragraph (from Step 2)- - Color-role instructions derived directly from the locked deck HEX values (from Step 2)+ - Color-role instructions anchored by the deck HEX values and refined for the image context (from Step 2)- The type's structural layout (from Step 3)- The image's specific `Reference` intent (from `design_spec.md §VIII`)- The container sizing guidance from the type file (so the model knows it's painting a local block, not a full canvas)@@ -146,7 +146,7 @@ Every assembled prompt follows this paragraph structure. **Write prose, not tag```[Rendering style paragraph — 80-120 words from the chosen rendering file].-[Deck color behavior — apply the locked color roles directly, e.g. "secondary background #F8F9FA provides 60% breathing space, primary #1E3A5F carries main forms, accent #D4AF37 appears in one or two emphasis points only"].+[Deck color behavior — state the core anchors and any context-justified tonal treatment, e.g. "secondary background #F8F9FA provides the breathing field, primary #1E3A5F carries main forms, accent #D4AF37 marks one emphasis; subtle lighter/darker material transitions remain in the same visual family"].[Type-specific composition — from the chosen type file, e.g. "central hub node with four radiating satellite nodes connected by clean lines"].[Image-specific subject — translated from the row's Reference intent into concrete visual nouns].[Container note — "composed as a {W}x{H}px image for {page_role} use"; add composition cues only when the page actually needs them. SVG-overlay-reservation cues ("leave the lower band calm — SVG title overlays it", "keep the right third calmer for SVG text") are valid **only** when `page_role: hero_page` (SVG sits on top of the image). For `page_role: local`, the image sits inside a region block and the SVG layer never overlays its interior — never reserve overlay space in a local prompt].@@ -447,7 +447,7 @@ Write `project/images/image_prompts.json` with this shape:| Field | Required | Source | Description ||---|---|---|---|| `deck_rendering` | yes | Step 2 lock | Single rendering name shared by all items in this deck |-| `color_scheme` | yes | `spec_lock.md colors` | Exact deck color roles used by every item; no separate image palette |+| `color_scheme` | yes | `spec_lock.md colors` | Core deck color anchors shared by every item; prompts may add contextual tonal behavior, but no separate image palette || `items[].filename` | yes | `§VIII` resource list | Output filename with extension || `items[].type` | conditional | Step 3 per-image (only when `page_role: local`) | One of 11 internal-composition types: `infographic`, `flowchart`, `framework`, `matrix`, `cycle`, `funnel`, `pyramid`, `comparison`, `timeline`, `map`, `scene`. **Omit `type` entirely when `page_role: hero_page`** — the composition comes from §4.1 primitives written directly into the prompt, not from a type file. || `items[].page_role` | yes | Step 3 per-image | `local` (default — region block on SVG page) or `hero_page` (image is page's main voice; SVG overlay minimal or empty) |@@ -486,11 +486,11 @@ C (AI-generated) supports three implementation modes sharing one `image_prompts.**Selection logic — declared-procedure fallback when no path is confirmed**: the confirmed user choice wins. When neither channel confirmed a specific path — the effective choice is `auto` (explicitly confirmed or defaulted) or absent — use the automatic A → B → C chain:-0. **Confirmed override (wins)** — honor the confirmed image source **from whichever channel the confirmation actually happened in**: when the Confirm UI was used, it records the choice to `<project>/confirm_ui/result.json` as `image_ai_path`; a chat confirmation is equally binding and leaves no `result.json` — read the choice from the conversation. From either channel, if the choice is set and not `auto`, honor it directly, **even when it contradicts `IMAGE_BACKEND`**:+0. **Confirmed override (wins)** — honor `AI Image Acquisition Path` from `design_spec.md §I`. Generate Step 4 already consumed the final confirmation into that durable artifact; do not reopen `result.json` here. If the recorded choice is set and not `auto`, honor it directly, **even when it contradicts `IMAGE_BACKEND`**:- `api` → **Path A** (`image_gen.py --manifest`).- `host-native` → **Path B** (host's native image tool) — skip A and do **not** run `image_gen.py --manifest`, *even if `IMAGE_BACKEND` is configured*.- `manual` → **Offline Manual** (write prompts, render the Markdown sidecar, hand off; do **not** run `image_gen.py --manifest`).- ("use Codex's image tool" / "走接口生成" in chat = `host-native` / `api`.) If an explicitly chosen path is unavailable or still fails after its retry, mark the affected row `Needs-Manual`; do not switch to another automated provider. Only when no channel named a specific path (the effective value is `auto` — explicitly confirmed or defaulted — or absent) does the automatic chain decide.+ If an explicitly chosen path is unavailable or still fails after its retry, mark the affected row `Needs-Manual`; do not switch to another automated provider. Only when the Design Spec records `auto` or no specific path applies does the automatic chain decide. A legacy project missing this Design Spec row returns to Step 4 recovery to consume persisted confirmation once and record it; Image_Generator does not inspect the confirmation channel itself.1. **Try Path A** — if `IMAGE_BACKEND` is configured (env or `.env`), run `image_gen.py --manifest`. If it fails twice in a row, fall to Path B.2. **Try Path B** — if `IMAGE_BACKEND` was not configured (A skipped), or A failed, and the host has a native image tool (Codex / Antigravity / Claude Code / similar), the agent invokes the host's image capability directly.3. **Fall to C (Offline Manual)** — if B is also unavailable (no host-native tool) or fails, write prompts to `images/image_prompts.json` and hand off to the user.@@ -638,7 +638,7 @@ Diagnose the failure category, adjust the **one specific dimension** responsible|---|---|---|| Image looks generic, model-average | Tag-soup prompt | Rewrite as one coherent paragraph per §4 || Wrong style family (looks photorealistic when flat was intended) | Rendering mismatch or rendering paragraph diluted | Reaffirm chosen rendering's style paragraph at the top of the prompt |-| Colors don't match deck | Locked role HEX not echoed, or their role / proportion instructions were diluted | Repeat the locked HEX values 2-3 times; restate which deck role owns the field, main forms, and sparse accents |+| Colors don't match deck | Core role anchors or their semantic/proportion instructions were diluted | Restate which deck roles own the field, main forms, and sparse accents; remove unrelated hues while preserving context-justified tonal transitions || Hex code or color name visible as text in image | Missing §5.1 closing sentence | Append the §5.1 hard rule verbatim || Garbled letters in supposedly text-free image | `text_policy: none` rule too weak | Strengthen with explicit list: "no letters, no numbers, no words, no signs, no labels, no captions, no watermarks" || SVG text overlay clashes with busy image area | Page design needs negative space the prompt didn't request | Add a composition cue like "leave the {center / left third / lower band} relatively calm for text overlay" — only when the page actually overlays text on top of the image |@@ -657,9 +657,9 @@ Diagnose the failure category, adjust the **one specific dimension** responsible- Generating prompts for `web` rows — those go through [`image-searcher.md`](./image-searcher.md)- Brand names or HEX codes inside the subject description (degrades output)-- Mixing renderings or inventing image-only colors across images in the same deck+- Mixing renderings or introducing an unrelated image-only palette across images in the same deck- Tag-soup prompts (keyword lists separated by commas without a coherent visual scene)- Globbing `image-renderings/*.md` or any subdirectory — read only the chosen file- Placing an image without updating its `image_prompts.json` `status` and the resource list status-- Switching rendering or deck-color roles for a single image—`hero_page` is not an exception to deck-wide coherence+- Switching rendering or core deck-color semantics for a single image—`hero_page` is not an exception to deck-wide coherence- Embedding body copy, data points, bullet lists, or long quotes inside an image — those route to SVGdiff --git a/skills/ppt-master/references/image-palettes/_index.md b/skills/ppt-master/references/image-palettes/_index.mdindex 5977ae64..71f5b577 100644--- a/skills/ppt-master/references/image-palettes/_index.md+++ b/skills/ppt-master/references/image-palettes/_index.md@@ -8,9 +8,9 @@ Compatibility tombstone for retired `image_palette` fields and historical palett| Input | Current behavior ||---|---|-| `spec_lock.md colors` | Sole source of generated-image color roles and exact HEX values |+| `spec_lock.md colors` | Core recurring deck-color anchors; interpret them with the completed Design Spec and image context, and allow coherent tonal/material/lighting derivatives without creating another palette || `image_rendering` | Controls rendering treatment only; it does not create a second color decision |-| Legacy `image_palette` row | Ignore it; it cannot override the deck color lock |+| Legacy `image_palette` row | Ignore it; it cannot override the confirmed deck identity or current contextual color judgment || No palette row | Expected; do not synthesize a preset or `custom` fallback |**Forbidden — legacy activation**:diff --git a/skills/ppt-master/references/image-renderings/_index.md b/skills/ppt-master/references/image-renderings/_index.mdindex 849ac81b..fdd0c5d5 100644--- a/skills/ppt-master/references/image-renderings/_index.md+++ b/skills/ppt-master/references/image-renderings/_index.md@@ -2,9 +2,9 @@A **rendering** is a visual style family: line quality, texture, depth, material, mood. Lock one rendering per deck — every AI image in the deck shares it.-> **HEX values are not in renderings.** Rendering describes how the image is drawn. The new flow reads exact deck color roles directly from `spec_lock.md colors`; it does not ask for or author a separate image palette. See [`image-generator.md`](../image-generator.md) §2.+> **HEX values are not in renderings.** Rendering describes how the image is drawn. The new flow starts from the deck's core color anchors in `spec_lock.md colors` and interprets them with the Design Spec/image context; it does not ask for or author a separate image palette. See [`image-generator.md`](../image-generator.md) §2.-> **Deck HEX has hard precedence.** Any color name or sample HEX inside an individual rendering file is illustrative legacy prose and MUST be replaced by the current deck-role values when assembling a prompt. A rendering may change texture, lighting, opacity, and role proportions, but it may not tint, warm-grade, cool-grade, replace, or invent HEX. If its material language requires colors the selected deck roles cannot support, do not offer that rendering in Stage 2.+> **Core deck identity has precedence.** Any sample HEX inside an individual rendering file is illustrative legacy prose. Prompt assembly replaces identity roles with the current deck anchors, then may derive coherent tints, light/shadow transitions, material colors, and atmospheric hues from the rendering and image context. Do not replace the deck identity with an unrelated palette. When one derived tone becomes a reusable semantic role across images/pages, promote it to a named lock row.---diff --git a/skills/ppt-master/references/image-renderings/fantasy-animation.md b/skills/ppt-master/references/image-renderings/fantasy-animation.mdindex c8f9c096..cc985e4a 100644--- a/skills/ppt-master/references/image-renderings/fantasy-animation.md+++ b/skills/ppt-master/references/image-renderings/fantasy-animation.md@@ -4,7 +4,7 @@ Ghibli/Disney-inspired hand-drawn animation warmth. Soft painterly forms, gentle## 1. Style paragraph (paste-ready, 110 words)-> Hand-drawn animation style inspired by Ghibli and classic Disney storybook aesthetics. Forms are softly rendered with painterly fills and gentle outlines — never harsh. Exact colors come only from the deck's locked roles; dreamy warmth comes from soft window light, gentle glow, morning haze, brush texture, and atmospheric perspective rather than invented pastel or earth-tone HEX. Characters (when present) are stylized in a friendly cartoon manner — large expressive eyes, simplified anatomy, warm body language. Foreground forms are richer and the background softer. Overall feel is dreamy, magical, comforting, and storybook-like.+> Hand-drawn animation style inspired by Ghibli and classic Disney storybook aesthetics. Forms are softly rendered with painterly fills and gentle outlines — never harsh. Core colors are anchored by the deck roles; dreamy warmth may derive through soft window light, gentle glow, morning haze, brush texture, atmospheric perspective, and coherent pastel/earth-tone transitions. Characters (when present) are stylized in a friendly cartoon manner — large expressive eyes, simplified anatomy, warm body language. Foreground forms are richer and the background softer. Overall feel is dreamy, magical, comforting, and storybook-like.---@@ -20,13 +20,13 @@ Ghibli/Disney-inspired hand-drawn animation warmth. Soft painterly forms, gentle## 3. Using the deck's HEX values-fantasy-animation uses the exact deck roles with a storybook treatment:+fantasy-animation uses the deck roles as identity anchors with a storybook treatment:-- Primary HEX: dominant environment or character color, unchanged-- Secondary HEX: atmospheric field or haze, unchanged-- Accent HEX: a small magical focal point — perhaps a window, flower, or key character element, unchanged+- Primary HEX: anchors the dominant environment or character family+- Secondary HEX: anchors the atmospheric field or haze family+- Accent HEX: anchors a small magical focal point — perhaps a window, flower, or key character element-If those roles cannot support the intended storybook mood without recoloring, choose another rendering in Stage 2.+Derive light, haze, and material tones coherently from those anchors; choose another rendering only when the required mood would replace the deck identity.---@@ -34,4 +34,4 @@ If those roles cannot support the intended storybook mood without recoloring, ch**Snippet A — half-page storybook scene, text_policy: none**-> Hand-drawn storybook animation. A small cottage sits on a hillside with a winding path leading to the foreground. The sky and haze use the deck's locked secondary-background role, the hillside and tree use the locked primary, and one small glowing cottage window uses the locked accent. Do not tint or replace those values. Painterly brush texture, soft light, and atmospheric perspective create the warmth: distant hills are softer, while foreground forms carry more visual weight. A simplified storybook tree stands at foreground left. Composed as a 600×800 half-page block with 10% inner padding. Any figures are gentle cartoon silhouettes with no realistic faces. No text or labels.+> Hand-drawn storybook animation. A small cottage sits on a hillside with a winding path leading to the foreground. The sky and haze derive from the deck's secondary-background family, the hillside and tree from primary, and one small glowing cottage window from accent. Coherent lighter/darker atmospheric transitions are allowed; do not replace these families with an unrelated storybook palette. Painterly brush texture, soft light, and atmospheric perspective create the warmth: distant hills are softer, while foreground forms carry more visual weight. A simplified storybook tree stands at foreground left. Composed as a 600×800 half-page block with 10% inner padding. Any figures are gentle cartoon silhouettes with no realistic faces. No text or labels.diff --git a/skills/ppt-master/references/image-renderings/ink-notes.md b/skills/ppt-master/references/image-renderings/ink-notes.mdindex addcbec2..8fdbe91a 100644--- a/skills/ppt-master/references/image-renderings/ink-notes.md+++ b/skills/ppt-master/references/image-renderings/ink-notes.md@@ -4,7 +4,7 @@ Pure white paper, black ink, sparse semantic color accents — the Mike Rohde sk## 1. Style paragraph (paste-ready, 105 words)-> Professional hand-drawn visual-note style on a clean paper field. All line work uses the deck's body-text color with slight wobble — confident, intentional, with the human-hand quality of a thoughtful whiteboard session. Hand-lettered titles appear bold and slightly oversized (when text policy allows). Color is intentionally sparse: line work dominates ~85% of the visible content, while one or two semantic accents drawn only from the deck's locked accent roles cover less than 10% combined. Backgrounds and shape fills remain mostly empty. Small doodle decorations — stars, dashes, dots — are minimal. Overall feel is professional, considered, manifesto-quality.+> Professional hand-drawn visual-note style on a clean paper field. All line work is anchored by the deck's body-text color with slight wobble — confident, intentional, with the human-hand quality of a thoughtful whiteboard session. Hand-lettered titles appear bold and slightly oversized (when text policy allows). Color is intentionally sparse: line work dominates ~85% of the visible content, while one or two semantic accents derive from the deck's accent families and cover less than 10% combined. Backgrounds and shape fills remain mostly empty. Small doodle decorations — stars, dashes, dots — are minimal. Overall feel is professional, considered, manifesto-quality.---@@ -24,9 +24,9 @@ ink-notes has a near-fixed material language: **dark ink + light background + 1-- Background: use the deck's `background` / `secondary_bg`- Lines and text: use the deck's `body_text`-- Semantic accents: use the deck's `accent` / `secondary_accent` roles and their established meaning; do not add traditional ink-notes colors outside the lock+- Semantic accents: derive from the deck's `accent` / `secondary_accent` roles and preserve their established meaning; contextual ink/paper tonal variants are allowed-This makes ink-notes the rendering most likely to fight a deck's HEX. Offer it only when the locked background / text / accent roles can support the treatment; never invent traditional coral / teal / lavender after confirmation.+This makes ink-notes the rendering most likely to fight a deck's identity. Offer it only when the background / text / accent anchors can support the treatment; do not substitute a stock coral / teal / lavender palette merely because the rendering traditionally uses one.---diff --git a/skills/ppt-master/references/image-renderings/sketch-notes.md b/skills/ppt-master/references/image-renderings/sketch-notes.mdindex f5625268..5e0b0a82 100644--- a/skills/ppt-master/references/image-renderings/sketch-notes.md+++ b/skills/ppt-master/references/image-renderings/sketch-notes.md@@ -4,7 +4,7 @@ Warm cream paper with black hand-drawn lines and soft pastel color blocks. The m## 1. Style paragraph (paste-ready, 110 words)-> Warm hand-drawn sketchnote style on the deck's light background role. All lines use the locked body-text color with deliberate slight wobble, never perfectly straight, giving the human-hand quality of a thoughtful teacher's whiteboard. Soft color blocks derive only from the locked primary, secondary-accent, and accent roles and fill rounded shapes without quite reaching their outlines (a deliberate "hand-painted overshoot" feel). Simple cartoon icons and small doodle decorations (stars, sparkles, dots, underlines) appear sparingly to add warmth. Composition is airy and well organized, with generous whitespace. Overall feel is instructional, friendly, and approachable.+> Warm hand-drawn sketchnote style anchored by the deck's light background and body-text roles. Lines retain the body-text character with deliberate slight wobble, never perfectly straight, giving the human-hand quality of a thoughtful teacher's whiteboard. Soft color blocks derive from the primary, secondary-accent, and accent families, allowing restrained pastel tints and paper/material transitions that stay coherent with those anchors. Simple cartoon icons and small doodle decorations (stars, sparkles, dots, underlines) appear sparingly to add warmth. Composition is airy and well organized, with generous whitespace. Overall feel is instructional, friendly, and approachable.---@@ -20,11 +20,11 @@ Warm cream paper with black hand-drawn lines and soft pastel color blocks. The m## 3. Using the deck's HEX values-sketch-notes has a strong built-in tendency toward warm paper, dark ink, and soft color blocks. Offer it only when the locked deck roles can carry that tendency; otherwise choose another rendering in Stage 2. Once confirmed, use only the locked deck colors.+sketch-notes has a strong built-in tendency toward warm paper, dark ink, and soft color blocks. Use the deck roles as identity anchors, then derive the paper warmth and pastel blocks contextually without creating an unrelated palette.-- Paper background: use the deck's `background` or `secondary_bg`; do not introduce a natural cream outside the lock+- Paper background: begin with `background` or `secondary_bg`; a subtle contextual paper tint is allowed when it preserves the deck's identity and contrast- Ink lines: use the deck's `body_text` role-- Color blocks: use the deck's primary / secondary-accent / accent roles with restrained coverage; do not invent pastel HEX+- Color blocks: derive restrained pastel tints from the primary / secondary-accent / accent families- Single emphasis accent: the deck's accent HEX, used in 1-2 strong sparing places (a key arrow, an emphasized doodle)---@@ -33,4 +33,4 @@ sketch-notes has a strong built-in tendency toward warm paper, dark ink, and sof**Snippet A — half-page educational concept, text_policy: embedded**-> Warm hand-drawn sketchnote on the deck's locked background color. Lines use the locked body-text color with slight wobble and define three rounded rectangle info boxes arranged in a soft triangle. The top box uses the locked primary, the bottom-left uses the locked secondary accent, and the bottom-right uses the locked accent, each with restrained coverage and no invented tint. Color fills do not completely reach their outlines (slight hand-painted overshoot). Hand-drawn wavy arrows connect the boxes, each with a brief inline keyword such as "leads to", "becomes", or "supports" (≤2 words). Each box contains one simple hand-drawn cartoon icon — a lightbulb, a plant, a gear. Small doodle decorations appear sparingly. Composed as a 600×600 half-page block with 14% inner padding and generous whitespace.+> Warm hand-drawn sketchnote anchored by the deck background. Lines use the body-text family with slight wobble and define three rounded rectangle info boxes arranged in a soft triangle. The top box derives from primary, the bottom-left from secondary accent, and the bottom-right from accent; each uses a restrained pastel tint coherent with its anchor. Color fills do not completely reach their outlines (slight hand-painted overshoot). Hand-drawn wavy arrows connect the boxes, each with a brief inline keyword such as "leads to", "becomes", or "supports" (≤2 words). Each box contains one simple hand-drawn cartoon icon — a lightbulb, a plant, a gear. Small doodle decorations appear sparingly. Composed as a 600×600 half-page block with 14% inner padding and generous whitespace.diff --git a/skills/ppt-master/references/image-renderings/warm-scene.md b/skills/ppt-master/references/image-renderings/warm-scene.mdindex 98822eec..6b9291af 100644--- a/skills/ppt-master/references/image-renderings/warm-scene.md+++ b/skills/ppt-master/references/image-renderings/warm-scene.md@@ -4,7 +4,7 @@ Golden-hour cinematic warmth — illustrated scenes with intentional warm lighti## 1. Style paragraph (paste-ready, 100 words)-> Atmospheric scene illustration with golden-hour cinematic lighting. Forms are softly rendered — recognizable but not photorealistic, with soft edges and intentional light direction. The scene has a clear primary light source (low sun, lamplight, window light) casting long soft shadows. Exact colors come only from the deck's locked roles; emotional warmth comes from light placement, bloom, contrast, and atmosphere rather than hue substitution. Composition follows narrative principles — foreground subject, middle-ground context, atmospheric background. Overall feel is cinematic, contemplative, and emotionally warm, well suited to brand story and personal narrative content.+> Atmospheric scene illustration with golden-hour cinematic lighting. Forms are softly rendered — recognizable but not photorealistic, with soft edges and intentional light direction. The scene has a clear primary light source (low sun, lamplight, window light) casting long soft shadows. Core colors are anchored by the deck roles; emotional warmth may derive through light placement, bloom, contrast, atmospheric haze, and coherent warm transitions without replacing the deck identity. Composition follows narrative principles — foreground subject, middle-ground context, atmospheric background. Overall feel is cinematic, contemplative, and emotionally warm, well suited to brand story and personal narrative content.---@@ -20,13 +20,13 @@ Golden-hour cinematic warmth — illustrated scenes with intentional warm lighti## 3. Using the deck's HEX values-warm-scene uses the deck's exact HEX roles and creates warmth through light, not recoloring:+warm-scene uses the deck's HEX roles as identity anchors and creates warmth through light and contextual tonal transitions:-- Primary HEX: dominant tone in shadows and middle ground, unchanged-- Secondary HEX: lit field or atmospheric separation, unchanged-- Accent HEX: a small concentrated zone — sun bloom, lamp glow, or key reflection, unchanged+- Primary HEX: anchors shadows and middle-ground color family+- Secondary HEX: anchors the lit field or atmospheric separation+- Accent HEX: anchors a small concentrated zone — sun bloom, lamp glow, or key reflection-If the locked roles cannot support an emotionally warm scene without hue shifts, do not offer `warm-scene` in Stage 2. Never warm-grade a cool primary after confirmation.+Derive warm light and haze without replacing those core families. Do not apply a generic orange grade that erases a deliberately cool brand identity; choose another rendering when that replacement would be necessary.---@@ -34,4 +34,4 @@ If the locked roles cannot support an emotionally warm scene without hue shifts,**Snippet A — half-page personal story, text_policy: none**-> Atmospheric scene illustration with golden-hour cinematic lighting. A softly rendered figure (simplified silhouette, no detailed face) walks along a path — foreground left, a small distant cabin in the middle ground, soft hills in the atmospheric background. Strong low-angle light comes from the upper right and casts long soft shadows. The sky uses the deck's locked secondary-background role, main forms use the locked primary, and a small sun bloom uses the locked accent; none is hue-shifted. No hard outlines — forms emerge from light and shadow. Add subtle bloom and film grain at 8% opacity. Composed as a 600×800 half-page block with 10% inner padding. Simplified silhouette figures only; no realistic faces, text, or labels.+> Atmospheric scene illustration with golden-hour cinematic lighting. A softly rendered figure (simplified silhouette, no detailed face) walks along a path — foreground left, a small distant cabin in the middle ground, soft hills in the atmospheric background. Strong low-angle light comes from the upper right and casts long soft shadows. The sky derives from the deck's secondary-background family, main forms from primary, and a small sun bloom from accent; coherent light/shadow transitions support the atmosphere without replacing those anchors. No hard outlines — forms emerge from light and shadow. Add subtle bloom and film grain at 8% opacity. Composed as a 600×800 half-page block with 10% inner padding. Simplified silhouette figures only; no realistic faces, text, or labels.diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.mdindex bf128708..62670f13 100644--- a/skills/ppt-master/references/native-shape-authoring.md+++ b/skills/ppt-master/references/native-shape-authoring.md@@ -78,8 +78,9 @@ preserve/mirror round-trip contract.## 3. Fragment Generation-Run one command for one selected object. Generated project pages take colors-from the current page-context projection of `spec_lock.md`; `create-template` takes colors+Run one command for one selected object. Generated project pages choose the+object's solid paint from the current page context, using `spec_lock.md` roles as+reusable anchors rather than an exhaustive palette; `create-template` takes colorsfrom the confirmed brief and template `design_spec.md`. Mirror/preserve inputkeeps the source object's paint instead of regenerating this authored form.@@ -179,7 +180,7 @@ otherwise regenerate the complete compact group.| Connector attachment | Authoring helper v1 creates an unconnected `p:cxnSp` and does not accept endpoint/site metadata. Do not hand-add it. The imported-shape contract may preserve an attachment that already exists in a source PPTX; creating a new attached connector is currently unsupported. || Action button behavior | `actionButton*` presets map visual geometry only. No action, navigation target, or hyperlink is created automatically. || Gradient/pattern paint | Authoring helper v1 accepts solid HEX paint only. Use ordinary SVG when a complex paint treatment is essential. |-| Multi-path darken/lighten | Direct visible layers use the shared normalized paint behavior from the PPTX importer. Their registry-derived HEX values are authorized derivatives of the locked base color, not spec-lock drift. |+| Multi-path darken/lighten | Direct visible layers use the shared normalized paint behavior from the PPTX importer. Their registry-derived HEX values are authorized derivatives of the selected base color and need no separate lock row. || Expanded compatibility | Existing helper-authored carrier/preview fragments remain readable as ordinary Slide-local input and receive a non-blocking migration warning; they do not become structured fixed atoms or object-slot carriers. Imported expanded fragments remain the lossless mirror/preserve form. || External edits | Any registry-path, style, or semantic mismatch fails quality check and export; regenerate the fragment. |diff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.mdindex 4a6603a6..d05ae6ff 100644--- a/skills/ppt-master/references/shared-standards-core.md+++ b/skills/ppt-master/references/shared-standards-core.md@@ -424,12 +424,14 @@ helper cannot write a project, select layout, or generate a page.**Authoring paint boundary**: v1 accepts `none` or six-digit solid HEX fill andstroke, optional fill/stroke opacity, stroke width, line cap, and line join.-Generated pages take colors from `spec_lock.md`; `create-template` authored-templates take them from the confirmed brief and template `design_spec.md`.+Generated pages use `spec_lock.md` for stable semantic color anchors and choose+page-local paint from the retained Design Spec, style, and composition context;+`create-template` authored templates take their values from the confirmed brief+and template `design_spec.md`.Use ordinary SVG for gradients, patterns, filters, or other treatments outside-this narrow contract. Registry-derived multi-path darken/lighten colors are-authorized derivatives of the locked base paint and do not count as color-drift. Mirror preserves source paint under §1.4 instead.+this narrow contract. Registry-derived multi-path darken/lighten colors and+other contextual derivatives need no separate lock row unless they become a+recurring named role. Mirror preserves source paint under §1.4 instead.**Validation**: quality check and export both rerender authored fragments from`preset + frame + adjustments + group paint` and compare every visible path anddiff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 6b1615ad..3b05ac02 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -38,9 +38,9 @@ Do not force communication intent into one catalog label. A deck may report prog>> **One opt-in exception**: present the spec-refinement line alongside the split-mode note ([`generate-pptx.md`](../workflows/generate-pptx.md) Step 4). It is OFF by default — the above discipline holds unchanged. Only when the user *explicitly* asks to refine the spec do you hand off to the [refine-spec](../workflows/stages/refine-spec.md) stage, which produces the full spec first and stops for user review/revision of any part before generation. Never enter it unprompted.-> **Default presentation surface — Confirm UI.** Write `<project>/confirm_ui/recommendations.json` and launch per Generate Step 4. Stage 2 carries ≥3 safe / shifted / bold `design_directions`; each bundles visual style, a six-role HEX palette, CJK + Latin typography, icons, and conditional image rendering. Also print the recommendations + URL in chat as fallback context. Skip launch only for an explicit chat-only request; a chat-question tool is not a substitute. Read the confirmed `result.json`. [`confirm_ui.md`](../scripts/docs/confirm_ui.md) owns schema and lifecycle.+> **Default presentation surface — Confirm UI.** Write `<project>/confirm_ui/recommendations.json` and launch per Generate Step 4. Stage 2 carries ≥3 safe / shifted / bold `design_directions`; each bundles visual style, a six-role HEX palette, CJK + Latin typography, icons, and conditional image rendering. Also print the recommendations + URL in chat as fallback context. Skip launch only for an explicit chat-only request; a chat-question tool is not a substitute. Generate Step 4 reads the final confirmed `result.json` once and retains that object for Design Spec authoring. [`confirm_ui.md`](../scripts/docs/confirm_ui.md) owns schema and lifecycle.-> ⛔ **GATE — final confirmation is the Design Spec input contract.** Immediately before authoring `design_spec.md`, re-read the complete final `result.json` with `stage: final` and `status: confirmed`; on a chat path, use the final visible confirmation summary as the equivalent state. Every explicitly present confirmed field is mandatory. Decide only details that remain unconfirmed. Never omit, delete, replace, narrow, weaken, reinterpret, or re-recommend a confirmed value because later analysis, asset inventory, template evidence, or personal judgment suggests another choice. Consume conditional fields according to their declared semantics, and preserve an explicitly cleared prose field as empty. If a confirmed value cannot be honored, keep the requirement visible and follow [`failure-recovery.md`](../workflows/governance/failure-recovery.md) instead of silently changing it.+> ⛔ **GATE — final confirmation is consumed once into the Design Spec.** Use the complete final object already read by Generate Step 4 (`stage: final`, `status: confirmed`); on a chat path, use the final visible confirmation summary as the equivalent retained state. Do not reopen `result.json` during normal Design Spec or lock authoring. Every explicitly present confirmed field is mandatory. Decide only details that remain unconfirmed. Never omit, delete, replace, narrow, weaken, reinterpret, or re-recommend a confirmed value because later analysis, asset inventory, template evidence, or personal judgment suggests another choice. Consume conditional fields according to their declared semantics, and preserve an explicitly cleared prose field as empty. If a confirmed value cannot be honored, keep the requirement visible and follow [`failure-recovery.md`](../workflows/governance/failure-recovery.md) instead of silently changing it.### a. Canvas Format Confirmation@@ -154,7 +154,7 @@ Proactively provide a color scheme (HEX values) based on content characteristics**Color rules**: 60-30-10 rule (primary 60%, secondary 30%, accent 10%); text contrast ratio >= 4.5:1; no more than 4 colors per page.-**Lock the full neutral set the visual style implies** — not just primary / secondary / accent / border. Predict the extra neutral tiers the locked `visual_style` (§d Layer 2) needs and lock them now; `spec_lock.colors` must be complete before generation, and the Executor draws only from it (never invents a tone mid-deck).+**Lock recurring semantic anchors, not every possible paint.** Add the neutral roles already known to recur across the deck—such as `surface`, `grid`, `scrim`, `overlay`, or `block-shade`—when the visual style and page plan establish a stable meaning for them. Do not try to predict every page-local tint, gradient stop, shadow/glow color, transparency composite, or one-off illustration tone. Those values are chosen from page context during execution; promote one into `spec_lock.colors` only when it becomes a reusable named role.| Style trait | Extra neutral tiers to lock ||---|---|@@ -333,7 +333,7 @@ Read the relevant `_index.md` at confirmation `d` (Layer 1 / Layer 2) for its caDo not start from a universal palette. Precedence is user / brand values → active template inheritance → the industry anchors in `scripts/config.py` → a project-specific proposal that realizes the locked visual style. Keep body-text contrast at least 4.5:1 and normally use no more than four chromatic colors on one page.-Lock the complete role set the style needs, including neutrals such as `surface`, `grid`, `scrim`, `overlay`, or `block-shade`; Executor must not invent a missing tone. For data semantics, use coherent positive / warning / negative ramps rather than unrelated accents.+Lock the stable role set the deck already needs, including recurring neutrals such as `surface`, `grid`, `scrim`, `overlay`, or `block-shade`. Treat these rows as identity and reuse anchors, not an exhaustive color allowlist. Executor may derive or choose contextual paints for gradients, effects, illustrations, and one-off page expression while preserving the confirmed palette's character and contrast. For data semantics, add reusable positive / warning / negative roles when they recur; do not scatter unrelated accents.---@@ -382,12 +382,12 @@ This is what makes the axis meaningful: a `presentation` deck and a `text` deck### 6.2 Planning Artifact Content-Generate Step 4 owns both artifact scaffolds. `design_spec.md` is the Strategist's human-readable design decision; `spec_lock.md` is its machine-readable execution projection. Author them in that order. Never treat the two files as parallel interpretations of `result.json`, and never let lock authoring become a second design pass.+Generate Step 4 owns both artifact scaffolds. `design_spec.md` is the Strategist's complete human-readable design decision; `spec_lock.md` is the context-selected execution subset and routing contract. Author them in that order. `result.json` is read once into the active final-confirmation state and consumed completely while writing the Design Spec. Never reopen it to author the lock, and never treat the two planning files as parallel interpretations of the confirmation.-1. Re-read the complete final confirmation state.-2. Write the full `design_spec.md` from that state plus source analysis. In §IX, each page carries layout, title, one core message, an **Audience move**, final content wording, applicable visualization/image references, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demonstration data.+1. Use the retained complete final-confirmation state already read once by Generate Step 4.+2. Write the full `design_spec.md` from that state plus source analysis and current project context. Record the confirmed production mechanics in §I so later stages never need to reopen `result.json`. In §IX, each page carries layout, title, one core message, an **Audience move**, final content wording, applicable visualization/image references, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demonstration data.3. Compare `design_spec.md` against the final confirmation field by field. Repair every omission or deviation before creating `spec_lock.md`.-4. Derive `spec_lock.md` only from the completed Design Spec. Project the exact values needed by Executor without adding a new recommendation, preference, or interpretation.+4. Author `spec_lock.md` from the completed Design Spec plus the current execution context: retain confirmed identity anchors, select stable cross-page roles and routing values, and omit page-local values that need no reusable name. This is implementation judgment, not a second user-facing recommendation.**Final confirmation → Design Spec consumption map**:@@ -400,13 +400,15 @@ Generate Step 4 owns both artifact scaffolds. `design_spec.md` is the Strategist| Icons | §VI uses the confirmed library or confirmed no-icon/custom path || Every confirmed non-`none` image source, `image_notes`, and AI strategy | §VIII contains at least one matching resource row per source; explicit page roles and intent appear in §VIII and the affected §IX pages || Natural-language template application | §I records it and the relevant layout/prototype choices realize it without silently dropping a requested use or exclusion |-| Formula policy, AI-image acquisition path, generation mode, refine-spec toggle | Their owning Generate stage consumes them; formula policy also shapes §VIII when formula-worthy content exists |+| Formula policy, AI-image acquisition path, generation mode, refine-spec toggle | §I records them as production mechanics; their owning Generate stage consumes the Design Spec, and formula policy also shapes §VIII when formula-worthy content exists |⛔ **GATE 1 — confirmation fidelity.** Do not create or fill `spec_lock.md` until the complete Design Spec has passed the field-by-field comparison above. A missing, changed, substituted, or weakened confirmed value blocks Step 4 even when the Design Spec schema validates. Schema validity proves structure, not fidelity to the user's decision.-⛔ **GATE 2 — lock projection fidelity.** After the Design Spec passes Gate 1, project its machine-relevant decisions into `spec_lock.md`. The lock may normalize syntax for its schema, but it must not change meaning or introduce an independent choice. If a projection exposes a contradiction or missing decision, return to Gate 1, repair the Design Spec from the final confirmation, and regenerate the affected lock rows.+⛔ **GATE 2 — lock context fidelity.** After the Design Spec passes Gate 1, author its machine-relevant execution anchors and routing values into `spec_lock.md`. The lock may normalize syntax and add named recurring implementation roles justified by the Design Spec/page plan, but it must not change confirmed identity or introduce a competing direction. It is intentionally not a field-for-field copy and not a whitelist of every legal SVG value. If authoring exposes a contradiction or missing confirmed decision, return to Gate 1 and repair the Design Spec from the retained final-confirmation state; on a fresh recovery turn only, read the persisted final result once to restore that state.-**Execution lock content**: `spec_lock.md` is the compact machine projection of the completed Design Spec for communication execution, colors, typography, icons, images, page rhythm, chart choices, and route-specific PowerPoint structure. Project every recurring typography size into its named role; do not collapse a confirmed `subtitle` or `annotation` value back into a derived default. Project every §VIII image row with its acquisition source so downstream routing cannot infer a different one. Do not copy planning-only context or decision provenance into the lock. Free-design, brand-only, and `template_reuse_scope: style` routes write `pptx_structure.mode: flat`; the conditional template module owns every structured mapping. Executor rebuilds the lock's current-page projection before every page (see [executor-base.md](executor-base.md) §2.1). Never repair the Design Spec from the lock; repair the Design Spec from the final confirmation, then re-project the lock.+**Execution lock content**: `spec_lock.md` is the compact context-authored contract for communication execution, stable color/type anchors, icons, images, page rhythm, chart choices, and route-specific PowerPoint structure. Project every recurring typography size into its named role; do not collapse a confirmed `subtitle` or `annotation` value back into a derived default. Keep confirmed title/body families and core palette roles stable, while leaving contextual gradient/effect paints and one-off export-safe type choices to page authoring. Project every §VIII image row with its acquisition source so downstream routing cannot infer a different one. Do not copy planning-only context or decision provenance into the lock. Free-design, brand-only, and `template_reuse_scope: style` routes write `pptx_structure.mode: flat`; the conditional template module owns every structured mapping. Executor rebuilds the lock's current-page projection before every page (see [executor-base.md](executor-base.md) §2.1). Never repair the Design Spec from the lock; repair the Design Spec from the retained final-confirmation state, then re-author the affected lock rows.++**Contextual extension during execution**: a page-local color, gradient stop, effect paint, or export-safe display family may remain only in that SVG when its use is genuinely local. If the same value acquires a recurring semantic role across pages, add one named row to `spec_lock.md` before the next affected page and regenerate page-context. This reverse lock update is legitimate consolidation, not a checker workaround; never add one-off values merely to silence an informational comparison.- **Communication trace is mandatory**: Keep the full confirmed communication contract in `design_spec.md §I`, then project only `audience`, `objective`, `core_message`, and canonical `consumption_mode` into `spec_lock.md communication`. Write `objective` as one concise execution sentence that preserves both the confirmed `communication_intent` and the success condition in `audience_outcome`; do not copy `delivery_context`, `artifact_afterlife`, dates, provenance, or conflict-resolution commentary into the lock. Before finalizing §IX, check that every named purpose has at least one outline obligation and **every Slide block**, including cover / divider / closing pages, has an `Audience move` that advances the global outcome. A page that advances no purpose or outcome should be merged, rewritten, or cut. `project_manager.py validate` and `svg_quality_checker.py` enforce the compact lock fields and per-page move presence, not their subjective quality.- **Custom behavior is concise and executable**: For confirmed `custom` mode or visual style, project one resolved `mode_behavior` / `visual_style_behavior` sentence or short paragraph. Preserve the confirmed direction, reference locked role names such as `colors.primary` when needed, and omit selection history, contradictions, precedence explanations, or other Design Spec provenance. Page-context carries these fields directly to Executor.diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.mdindex f1483575..b48c9ed2 100644--- a/skills/ppt-master/references/svg-effects.md+++ b/skills/ppt-master/references/svg-effects.md@@ -16,12 +16,15 @@ Use any compatible technique when it serves the locked visual style and content.| Decision layer | Authority ||---|---|| Technical validity | Required / Forbidden / Conditional contracts in this file |-| Project values | `<project_path>/spec_lock.md` colors, fonts, icons, and images |+| Project values | `<project_path>/spec_lock.md` stable anchors plus the retained Design Spec and current page context || Aesthetic fit | Locked `visual_style` / `visual_style_behavior` || Per-page choice | Content purpose, hierarchy, legibility, semantics, and rhythm |-**Hard rule — illustrative colors**: colors below demonstrate syntax only;-generated pages use matching `spec_lock.md` roles. Fidelity labels are defined+**Reference — illustrative colors**: colors below demonstrate syntax only;+generated pages choose paint from the locked identity anchors, visual style,+content semantics, and current composition. A contextual tint, gradient stop,+shadow/glow paint, or one-off display color need not already be a lock row;+promote it only when it becomes a recurring named role. Fidelity labels are definedin [`shared-standards-core.md`](./shared-standards-core.md). Review an `Approximate` result in native PPTXwhen the effect carries material meaning.@@ -121,6 +124,9 @@ contract. See[`conversion.md`](../scripts/docs/conversion.md#import-compatibility-and-recovery-boundary).The quality checker and exporter preflight both validate definition location,references, gradient structure, and paint context from the same closed contract.+Gradient-stop colors are contextual paint values. Keep them coherent with the+deck anchors and page intent; they are not required to duplicate existing+`spec_lock.colors` literals.**Hard rule — non-degenerate gradient geometry**: an `objectBoundingBox`gradient stroke requires non-zero intrinsic width and height. SVG stroke widthdiff --git a/skills/ppt-master/references/visual-review.md b/skills/ppt-master/references/visual-review.mdindex f3390f3f..685f180d 100644--- a/skills/ppt-master/references/visual-review.md+++ b/skills/ppt-master/references/visual-review.md@@ -14,7 +14,7 @@ If the static checker has not been run or has failed, the subagent must abort wi- font-size ramp drift (`RAMP_MIN_RATIO=0.5` / `MAX=5.0`)- id uniqueness, XML well-formed-- spec_lock drift (colors / fonts / canvas)+- canvas/structural typography validation and informational spec-lock anchor comparison (contextual colors/fonts are allowed)- animation_config compliance## §0.1 Subagent inputsdiff --git a/skills/ppt-master/references/visual-styles/_index.md b/skills/ppt-master/references/visual-styles/_index.mdindex 7519ea80..8b73aaeb 100644--- a/skills/ppt-master/references/visual-styles/_index.md+++ b/skills/ppt-master/references/visual-styles/_index.md@@ -2,7 +2,7 @@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).-> **Styles carry NO HEX and lock no palette.** Color truth and role behavior live in `design_spec.colors` / `spec_lock.colors` (confirmation `e`). A visual style only describes how those existing colors are used in SVG composition—never which colors to substitute. Generated images follow the same single source of truth: their rendering comes from [`image-renderings/`](../image-renderings/), while their exact colors inherit the deck roles directly. [`image-palettes/`](../image-palettes/) is legacy compatibility material only.+> **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.>> 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.diff --git a/skills/ppt-master/scripts/README.md b/skills/ppt-master/scripts/README.mdindex 5e925b99..50c31ca7 100644--- a/skills/ppt-master/scripts/README.md+++ b/skills/ppt-master/scripts/README.md@@ -81,7 +81,7 @@ python3 scripts/project_manager.py page-context-report <project_path>````page-context` prints a read-only compact current-page projection. Its global-lock projection repeats per page as an anti-drift guard; large Design Specs,+lock projection repeats per page as a continuity anchor set, not a color/font allowlist; large Design Specs,prototype, and `templates/charts/` references are emitted only as scopedpath/SHA fingerprints and are read once per execution context. `--bundle` is adeprecated compatibility no-op. `--record-usage` writes one derived snapshotdiff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.mdindex 36e3dd2b..a2b516a0 100644--- a/skills/ppt-master/scripts/docs/confirm_ui.md+++ b/skills/ppt-master/scripts/docs/confirm_ui.md@@ -256,7 +256,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendationsThe shape above is final. Selected custom values use `mode: custom` + `mode_behavior`, `visual_style: custom` + `visual_style_behavior`, or `image_strategy.rendering: custom` + `behavior`. Intermediate writes retain accumulated fields; legacy tier names remain read-compatible.-**Final-result consumption contract.** A final result is the user-confirmed input contract for the Strategist's Design Spec, not another recommendation input. The Strategist re-reads the complete final object, writes and audits `design_spec.md` against every explicitly present field, and may autonomously decide only details that remain unconfirmed. Only after that audit passes does it project `spec_lock.md` from the completed Design Spec; lock authoring is not a second design pass. It must not omit, substitute, narrow, weaken, reinterpret, or re-recommend a confirmed value. If one value cannot be honored, the owning workflow reports or pauses under failure recovery; it never deletes the requirement to keep the pipeline moving.+**Final-result consumption contract.** A final result is the user-confirmed input contract for the Strategist's Design Spec, not another recommendation input. After the final wait, Generate Step 4 reads the complete final object exactly once and retains it while Strategist writes and audits `design_spec.md` against every explicitly present field. Normal lock authoring and downstream execution do not reopen `result.json`; the completed Design Spec is the durable authority. Only after that audit passes does Strategist author `spec_lock.md` from the Design Spec plus current execution context, selecting stable anchors and routing rather than copying every field or enumerating every legal color/font. It must not omit, substitute, narrow, weaken, reinterpret, or re-recommend a confirmed value. If one value cannot be honored, the owning workflow reports or pauses under failure recovery; it never deletes the requirement to keep the pipeline moving.- Bespoke mode / style prose lives only in the required behavior sibling; image custom prose lives in `image_strategy.behavior`. Canvas / icons retain free-text edge cases, color / typography retain `name: "custom"`, and image usage remains a source-id array plus `image_notes`.- `image_ai_path` and `image_strategy` appear only with `image_usage: ai` and remain confirmed downstream. The page is default; explicit/failure chat fallback keeps identical fields. `image_ai_path` selects the Step 5 path, and [`strategist-image.md`](../../references/strategist-image.md) §2 locks the chosen strategy verbatim.diff --git a/skills/ppt-master/scripts/docs/project.md b/skills/ppt-master/scripts/docs/project.mdindex ac178854..368fc40b 100644--- a/skills/ppt-master/scripts/docs/project.md+++ b/skills/ppt-master/scripts/docs/project.md@@ -45,12 +45,10 @@ Notes:fields, illegal enums, malformed page keys, and unmet conditional sections;it does not rewrite either artifact or compare their values for textualequality. It also does not prove final-confirmation → Design Spec fidelity or- Design Spec → lock semantic projection; Generate Step 4 owns those two gates- before this structural validation. One slice is enforced mechanically: when- `confirm_ui/result.json` records a final confirmed stage, every confirmed- non-`none` `image_usage` source must appear in at least one `## images` row- of the lock (`provided` maps to `user`; `ai` is also satisfied by `slice`).- The design schema is structural lint for+ Design Spec/context → lock semantic fidelity; Generate Step 4 owns those two+ gates before this structural validation. Validation reads the planning+ artifacts only and never reopens `confirm_ui/result.json`; the final result is+ consumed once into the Design Spec before validation begins. The design schema is structural lint forthe human-readable brief; the lock schema owns machine execution values. Forstructured template use, strict input prototypes must match their assignedMaster/Layout; adaptive input prototypes retain the assigned Master while a@@ -72,8 +70,8 @@ changes JSON formatting only. Before projection it revalidates the machine lockand selected template-root identities; design-brief values are not treated asa second lock. Slide headings at H3–H6 remain readable by the projector.-The output deliberately repeats the bounded `global` lock projection on every-page as an anti-drift guard. `lock_source` binds that projection to the current+The output deliberately repeats the bounded `global` anchor set on every+page as a cross-page anchor set, not a color/font allowlist. `lock_source` binds that projection to the current`spec_lock.md` SHA. `page_context` contains the current §IX brief, rhythm,resources, and conditional template/chart assignment. `reference_set` containsonly `kind`, scoped path, SHA, and `once-per-execution-context` policy for thediff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex cf20a065..47ee3b5b 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -28,12 +28,12 @@"skills/ppt-master/references/svg-effects.md": 11600,"skills/ppt-master/references/native-data-interface.md": 6200,"skills/ppt-master/references/pptx-structure-interface.md": 4300,- "skills/ppt-master/references/strategist.md": 12250,+ "skills/ppt-master/references/strategist.md": 12400,"skills/ppt-master/references/strategist-image.md": 1800,"skills/ppt-master/references/strategist-template.md": 2100,- "skills/ppt-master/templates/design_spec_reference.md": 800,- "skills/ppt-master/templates/spec_lock_reference.md": 1200,- "skills/ppt-master/workflows/generate-pptx.md": 11600,+ "skills/ppt-master/templates/design_spec_reference.md": 850,+ "skills/ppt-master/templates/spec_lock_reference.md": 1450,+ "skills/ppt-master/workflows/generate-pptx.md": 12000,"skills/ppt-master/workflows/stages/apply-template-workspace.md": 1800},"load_sets": {@@ -143,7 +143,7 @@"registry": "visual-styles"}],- "max_tokens": 47000+ "max_tokens": 47300},"route.generate.planning-image": {"description": "Generate-PPTX planning context after a non-none image source is proposed or confirmed.",@@ -153,7 +153,7 @@"stage.generate.strategist.image-layout"],"files": [],- "max_tokens": 54500+ "max_tokens": 55100},"route.generate.planning-formula": {"description": "Formula-only planning context with no non-formula image resource or layout catalog.",@@ -163,7 +163,7 @@"stage.generate.strategist.image"],"files": [],- "max_tokens": 48500+ "max_tokens": 49100},"route.generate.planning-ai": {"description": "Generate-PPTX planning context when AI image direction is available.",@@ -174,7 +174,7 @@"files": ["skills/ppt-master/references/image-renderings/_index.md"],- "max_tokens": 56500+ "max_tokens": 57100},"stage.generate.apply-template-workspace": {"description": "Conditional Step 3 workspace validation, installation, and fusion framework.",@@ -286,7 +286,7 @@"stage.generate.executor.notes"],"files": [],- "max_tokens": 67650+ "max_tokens": 68700},"route.generate.flat-ai-two-types": {"description": "Generate-PPTX context with AI images, one rendering, and two local types.",@@ -299,7 +299,7 @@"stage.generate.image.ai-two-types"],"files": [],- "max_tokens": 103500+ "max_tokens": 105000},"route.generate.flat-in-hand-image": {"description": "Generate-PPTX context with provided, placeholder, or formula images and no acquisition role.",@@ -311,7 +311,7 @@"stage.generate.executor.notes"],"files": [],- "max_tokens": 80650+ "max_tokens": 82000},"route.generate.flat-web-image": {"description": "Generate-PPTX context with web image acquisition.",@@ -324,7 +324,7 @@"stage.generate.image.web"],"files": [],- "max_tokens": 88000+ "max_tokens": 89300},"route.enhance-native-pptx.audio": {"description": "Enhance Native PPTX with the shared narration-audio stage.",@@ -344,7 +344,7 @@"profile.generate.beautify-pptx"],"files": [],- "max_tokens": 74400+ "max_tokens": 75500},"route.generate.flat-no-image-chart": {"description": "Default flat Generate-PPTX path with chart authoring, native-data replacement, and verification.",@@ -369,7 +369,7 @@"stage.generate.template.brand"],"files": [],- "max_tokens": 75000+ "max_tokens": 75700},"route.generate.deck-structured-no-image": {"description": "Deck-preset structured Generate-PPTX path without image acquisition.",@@ -381,7 +381,7 @@"stage.generate.template.deck"],"files": [],- "max_tokens": 84600+ "max_tokens": 85600},"route.generate.layout-structured-no-image": {"description": "Layout-preset structured Generate-PPTX path without image acquisition.",@@ -393,7 +393,7 @@"stage.generate.template.layout"],"files": [],- "max_tokens": 84900+ "max_tokens": 86000},"route.generate.topic-only-flat-no-image": {"description": "Topic research followed by the default flat no-image Generate-PPTX path.",@@ -403,7 +403,7 @@"route.generate.flat-no-image"],"files": [],- "max_tokens": 69450+ "max_tokens": 70500},"stage.generate.executor.flat": {"description": "Incremental flat Executor core with one locked mode and visual style.",@@ -500,7 +500,7 @@"skills/ppt-master/workflows/stages/resume-execute.md","skills/ppt-master/references/artifact-ownership.md"],- "max_tokens": 43000+ "max_tokens": 43400},"stage.generate.resume-execute-image": {"description": "Fresh-session resume when the locked resource plan contains image rows.",@@ -510,7 +510,7 @@"stage.generate.executor.image"],"files": [],- "max_tokens": 48500+ "max_tokens": 48900},"stage.generate.topic-research": {"description": "Topic-only intake stage.",@@ -526,7 +526,7 @@"files": ["skills/ppt-master/workflows/profiles/beautify-pptx.md"],- "max_tokens": 6800+ "max_tokens": 6900},"stage.generate.refine-spec": {"description": "Explicit post-confirmation spec refinement runbook.",@@ -638,7 +638,7 @@"stage.generate.strategist.template"],"files": [],- "max_tokens": 48800+ "max_tokens": 49400},"route.generate.planning-template-ai": {"description": "Explicit template workspace plus confirmed AI-image planning.",@@ -648,7 +648,7 @@"route.generate.planning-ai"],"files": [],- "max_tokens": 58600+ "max_tokens": 59100},"stage.generate.artifact-schema-guide": {"description": "Compact human guide loaded only to diagnose planning-artifact schema or scaffold failures.",@@ -657,7 +657,7 @@"skills/ppt-master/templates/design_spec_reference.md","skills/ppt-master/templates/spec_lock_reference.md"],- "max_tokens": 2050+ "max_tokens": 2250},"stage.generate.executor.chart": {"description": "Conditional chart/table page execution rules.",diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.mdindex 8e53b3d2..3994e198 100644--- a/skills/ppt-master/templates/design_spec_reference.md+++ b/skills/ppt-master/templates/design_spec_reference.md@@ -2,7 +2,7 @@Project-level `design_spec.md` is a human-readable English-heading Markdown artifact. [`schemas/design_spec.schema.json`](./schemas/design_spec.schema.json) provides structural lint for readable sections and page projection; it is not an execution lock and does not require textual equality with `spec_lock.md`. Authoring starts from [`scaffolds/design_spec.md`](./scaffolds/design_spec.md).-Strategist writes this artifact from the complete final confirmation plus source analysis, audits every confirmed field here first, and only then projects `spec_lock.md` from the completed Design Spec.+Strategist reads the complete final confirmation once, writes this artifact from that retained state plus source analysis, and audits every confirmed field here. Afterward, `spec_lock.md` is authored from the completed Design Spec plus current project/page/template context; normal lock authoring never reopens `result.json`.## 1. Create the artifact@@ -43,7 +43,7 @@ python3 skills/ppt-master/scripts/project_manager.py validate <project_path>Validation reads the Markdown directly. It reports missing or out-of-order I–X sections, unresolved `[fill...]` scaffold placeholders, missing per-slide `Audience move`, and a missing §III `AI Image Strategy` when an §VIII table selects `ai` acquisition.-The schema owns structure only. Strategist role modules own field meaning, recommendation logic, page planning, image policy, and template policy. `spec_lock.md` owns the compact execution projection. On divergence, first repair the Design Spec from the final confirmation when Gate 1 fails; otherwise repair the lock from the audited Design Spec. Never use the lock to overwrite a valid Design Spec decision.+The schema owns structure only. Strategist role modules own field meaning, recommendation logic, page planning, image policy, and template policy. `spec_lock.md` owns stable execution anchors and routing selected in context; it is not an exhaustive value projection. On divergence, repair the Design Spec from the retained final state when Gate 1 fails, then re-author affected lock anchors from the audited Design Spec and current context. Never reopen `result.json` merely to author or validate the lock, and never use the lock to overwrite a valid Design Spec decision.---diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.mdindex 1e9f134a..bc8e1ed7 100644--- a/skills/ppt-master/templates/spec_lock_reference.md+++ b/skills/ppt-master/templates/spec_lock_reference.md@@ -1,10 +1,10 @@# Execution Lock Structure-`spec_lock.md` is the machine projection of an audited `design_spec.md`. After confirmation fidelity passes, start from [`scaffolds/spec_lock.md`](./scaffolds/spec_lock.md); [`schemas/spec_lock.schema.json`](./schemas/spec_lock.schema.json) owns its grammar.+`spec_lock.md` is the compact execution contract authored from an audited `design_spec.md` and the current project context. It keeps stable cross-page anchors and routing values; it is not an exhaustive allowlist of every color, gradient stop, effect paint, or typeface that a page may use. After confirmation fidelity passes, start from [`scaffolds/spec_lock.md`](./scaffolds/spec_lock.md); [`schemas/spec_lock.schema.json`](./schemas/spec_lock.schema.json) owns its grammar.## 1. Create the artifact-After Generate Step 4 Gate 1, run once and project values from the Design Spec:+After Generate Step 4 Gate 1, run once and author the execution anchors from the Design Spec plus current page/resource/template context:```bashpython3 skills/ppt-master/scripts/project_manager.py scaffold-lock <project_path>@@ -24,8 +24,8 @@ The command refuses to overwrite an existing `spec_lock.md`. Re-running it with| `communication` | `audience`, `objective`, `core_message` | Compact execution projection; `objective` combines intent and audience outcome; `consumption_mode` is optional off PPT canvases || `mode` | `mode` | Preset or `custom` || `visual_style` | `visual_style` | Preset or `custom` |-| `colors` | Used color roles | `image_rendering` appears only for AI images |-| `typography` | `font_family`, `body`, `title` | Sizes are unitless numbers |+| `colors` | Stable semantic color roles | Core identity and recurring roles only; contextual SVG paints need no row; `image_rendering` appears only for AI images |+| `typography` | `font_family`, `body`, `title` | Core family/size anchors; sizes are unitless numbers || `icons` | `library`, `inventory` | `stroke_width` is conditional || `page_rhythm` | One `P<NN>` row per page | Values: `anchor`, `dense`, `breathing` || `pptx_structure` | `mode` | Values: `flat`, `structured` |@@ -70,7 +70,7 @@ Structured section value shapes:## 4. Field Grammar Index-- `font_family` grammar: one PPT-safe family name; role-specific families may extend it in the same section.+- `font_family` grammar: one non-empty PPT-safe exported family stack; role-specific families may extend it in the same section.- `objective` grammar: one concise sentence preserving the deck goal and audience success condition.- `image_rendering` grammar: one catalog id, or `custom` with `image_rendering_behavior`.- `stroke_width` grammar: `1.5`, `2`, or `3`; present only for `tabler-outline`.@@ -92,3 +92,10 @@ python3 skills/ppt-master/scripts/project_manager.py validate <project_path>Validation reports unresolved `[fill...]` placeholders, wrong casing, unknown sections or fields, illegal enums, malformed page keys, missing catalog assets, broken structured-layout references, and unmet conditions. It neither rewrites the lock nor checks semantic projection; Generate Step 4 Gate 2 owns that check.Field meaning and selection logic stay in the owning Strategist modules. Executor branch references own consumption behavior. The schema owns only artifact grammar and structural conditions.++## 6. Anchor and extension semantics++- Confirmed core palette roles and structural title/body typography remain stable cross-page anchors.+- Page-local tints, gradient stops, shadow/glow paints, transparency composites, and one-off export-safe display families may be authored from context without adding a lock row.+- When a contextual value becomes a recurring semantic role, add one descriptive `colors` or `*_family` row and regenerate page-context before later pages use that role.+- Do not expand the lock merely to make an informational checker comparison empty. A lock edit should express reuse or identity, not enumerate incidental literals.diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 65cdf299..2f6ea671 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -12,7 +12,7 @@ description: Generate PPTX route authority for source intake, planning, SVG auth- The current main agent hand-writes every SVG page; never delegate page generation or run a Python, Node, or shell generator over `svg_output/`.- Initial SVG cadence: P01 → first-page gate → uninterrupted remaining pages → final gate. Grouped batches and mid-run checker calls are forbidden.-- Before each page, load compact page-context; its lock projection guards drift while unchanged large references stay in context.+- Before each page, load compact page-context; its repeated global values are continuity anchors, while unchanged large references stay in context.- `preset_shape_svg.py` may provide one stdout fragment only after the main agent chooses its semantic role, frame, and paint; it cannot choose layout or write a page.### SVG Page-Design Boundary@@ -190,7 +190,7 @@ The core first chooses the proposed Stage 2 source ids. Load the image module bepython3 ${SKILL_DIR}/scripts/confirm_ui/server.py <project_path> --wait-only```-4. After the final wait returns, re-read the complete `result.json` even when the wait succeeded. Proceed from the file only when it carries `stage: final` and `status: confirmed`. On a non-zero wait, perform this same read before using the documented chat fallback. A stage-skip result returns to the missing stage; it is not a browser failure.+4. After the final wait returns, read the complete `result.json` exactly once and retain that object through Design Spec authoring and its fidelity audit. Proceed only when it carries `stage: final` and `status: confirmed`. Do not reopen the file during normal lock authoring or downstream execution. On a non-zero wait, this same single read determines whether the persisted result succeeded before using the documented chat fallback. A stage-skip result returns to the missing stage; it is not a browser failure.5. After final confirmation or chat fallback, always release the server:@@ -200,7 +200,7 @@ The core first chooses the proposed Stage 2 source ids. Load the image module beIf the user opted out of the page but did not delegate confirmation, skip launch and run the same three stages in chat with explicit user responses. If the user explicitly delegated confirmation, consolidate the same three stages into one AI-authored summary and proceed without `result.json`. Otherwise report the launch URL and keep the staged chat summaries available as fallback.-⛔ **GATE — write the Design Spec from the final state, then project the lock.** Treat every explicitly present final value as a user-owned Design Spec requirement. The Strategist may autonomously elaborate only unconfirmed implementation details; it must not omit, delete, substitute, narrow, weaken, reinterpret, or re-recommend a confirmed value. First author and audit the complete `design_spec.md` through [`strategist.md`](../references/strategist.md) §6.2, including every confirmed image source and explicit `image_notes` role. Only after that audit passes, derive `spec_lock.md` from the completed Design Spec without making another design decision. Apply `strategist-template.md` §3 for an active template, and never write a separate image palette. If one confirmed value cannot be honored, follow [`failure-recovery.md`](governance/failure-recovery.md) instead of silently changing it.+⛔ **GATE — consume the final state once into the Design Spec, then author the lock from context.** Treat every explicitly present final value as a user-owned Design Spec requirement. The Strategist may autonomously elaborate only unconfirmed implementation details; it must not omit, delete, substitute, narrow, weaken, reinterpret, or re-recommend a confirmed value. First author and audit the complete `design_spec.md` through [`strategist.md`](../references/strategist.md) §6.2 from the retained final object, including production mechanics, every confirmed image source, and explicit `image_notes` role. Do not reopen `result.json` afterward. Only after that audit passes, author `spec_lock.md` from the completed Design Spec and current project/page/template context: preserve confirmed identity, choose reusable execution anchors and routing values, and do not enumerate page-local paint or font choices. Apply `strategist-template.md` §3 for an active template, and never write a separate image palette. If one confirmed value cannot be honored, follow [`failure-recovery.md`](governance/failure-recovery.md) instead of silently changing it.**Mandatory — split-mode note** (not a separate confirmation): after listing the Strategist confirmation stage details, you MUST append exactly one short line (rendered in the user's language, prefixed with 💡) about generation mode. Pick the variant by qualitative read of upstream-load signals — recommended page count, source-material bulk, whether `topic-research` ran with substantial web-fetch accumulation:@@ -225,8 +225,8 @@ python3 ${SKILL_DIR}/scripts/analyze_images.py <project_path>/images> ⚠️ **Image handling**: NEVER directly read / open / view image files (`.jpg`, `.png`, etc.). All image info comes from `analyze_images.py` output (`analysis/image_analysis.csv`) or the Design Spec's Image Resource List.**Output**:-- `<project_path>/design_spec.md` — human-readable design narrative-- `<project_path>/spec_lock.md` — machine-readable communication + execution contract; Executor consumes its current-page projection from `page-context`+- `<project_path>/design_spec.md` — complete human-readable design narrative and durable confirmed production state+- `<project_path>/spec_lock.md` — machine-readable communication + stable execution anchors/routing contract; Executor consumes its current-page projection from `page-context`For a new project, scaffold the Design Spec after final confirmation; the command refuses to overwrite an existing artifact:@@ -234,25 +234,25 @@ For a new project, scaffold the Design Spec after final confirmation; the commanpython3 ${SKILL_DIR}/scripts/project_manager.py scaffold-spec <project_path>```-Fill and audit `design_spec.md` against the complete final confirmation. Only after that audit passes, scaffold and fill the machine lock from the completed Design Spec:+Fill and audit `design_spec.md` against the retained complete final confirmation. This is the only normal consumption of the final result. Only after that audit passes, scaffold and author the machine lock from the completed Design Spec plus current execution context:```bashpython3 ${SKILL_DIR}/scripts/project_manager.py scaffold-lock <project_path>```-After filling the lock, compare its machine-relevant values against the completed Design Spec, then run `python3 ${SKILL_DIR}/scripts/project_manager.py validate <project_path>`. A `result.json` → Design Spec mismatch or Design Spec → lock projection mismatch is blocking even when the standalone Markdown schemas pass. `validate` mechanically enforces one slice of this: with a final confirmed `confirm_ui/result.json`, every confirmed non-`none` `image_usage` source must be represented by at least one `## images` row (`ai` is also satisfied by `slice`); the remaining semantic comparison stays with this gate. Repair the Design Spec only from the final confirmation state, then re-project the affected lock rows. A resume path edits existing files in the same order and never re-scaffolds them.+After filling the lock, compare its identity anchors and routing values against the completed Design Spec, then run `python3 ${SKILL_DIR}/scripts/project_manager.py validate <project_path>`. A retained final state → Design Spec mismatch or Design Spec/context → lock mismatch is blocking even when the standalone Markdown schemas pass. `validate` reads the planning artifacts only; it does not reopen `confirm_ui/result.json` or prove semantic fidelity. Repair the Design Spec from the retained final state; only a fresh recovery turn with no retained state reads persisted final evidence once. Then re-author the affected lock rows from the corrected Design Spec and current context. A resume path edits existing files in the same order and never re-scaffolds them.**✅ Checkpoint — Phase deliverables complete, auto-proceed to next step**:```markdown## ✅ Strategist Phase Complete- [x] Read the auto-extracted facts already in `analysis/` (e.g. `source_profile.json`) before the Strategist confirmation stage- [x] Strategist confirmation stage completed (user confirmed via Confirm UI `result.json` or chat fallback)-- [x] Final confirmation re-read before Design Spec authoring+- [x] Final confirmation read once and retained through Design Spec authoring/audit; `result.json` not reopened in the normal path- [x] Split-mode note appended below the confirmation fields (heavy or normal variant)- [x] Spec-refinement opt-in line appended (default OFF; only the user's explicit request enters the refine-spec stage)- [x] Design Specification & Content Outline generated- [x] Gate 1 passed: Design Spec preserves every confirmed value-- [x] Execution lock (`spec_lock.md`) projected from the completed Design Spec with no independent design decision+- [x] Execution lock (`spec_lock.md`) authored from the completed Design Spec + current context as stable anchors/routing, not an exhaustive value whitelist- [x] Communication trace validated: Design Spec retains the contract; the lock has compact `audience` / `objective` / `core_message` fields (plus PPT `consumption_mode`); every §IX Slide has an `Audience move`- [ ] **Next**: Auto-proceed to [Image_Generator / Executor] phase```@@ -263,7 +263,7 @@ After filling the lock, compare its machine-relevant values against the complete🚧 **GATE**: Step 4 complete; `<project_path>/design_spec.md` and `<project_path>/spec_lock.md` both exist. If either required artifact is missing, stop before any acquisition or generation and follow [`failure-recovery.md`](governance/failure-recovery.md) §3. Formula rows already have `Acquire Via: formula` and status `Rendered` or `Needs-Manual`.-> **Trigger**: At least one row in the resource list has `Acquire Via: ai`, `web`, and/or `slice`. If every row is `user`, `formula`, or `placeholder`, skip to Step 6. A final confirmation that selected `ai` or `web` without a matching §VIII resource row is an incomplete Design Spec, not a reason to skip Step 5; return to Step 4 Gate 1, repair the Design Spec from the final confirmation, and re-project the lock.+> **Trigger**: At least one row in the resource list has `Acquire Via: ai`, `web`, and/or `slice`. If every row is `user`, `formula`, or `placeholder`, skip to Step 6. If the completed Design Spec records `ai` or `web` acquisition intent without a matching §VIII resource row, the Design Spec is incomplete; return to Step 4 Gate 1, repair it from the retained final state, and re-author the affected lock anchors from context. Do not reopen `result.json` during this check.**Failure recovery**: stop/continue behavior for AI/web/slice/image-readiness failures is defined in [`workflows/governance/failure-recovery.md`](governance/failure-recovery.md). This Step keeps the acquisition procedure.@@ -290,7 +290,7 @@ A deck with only `ai` rows never loads `image-searcher.md`; a deck with only `we> 💡 **ai path — spot illustrations as one sheet**: when the §VIII image resource plan needs ≥3 same-family spot illustrations as decorative accessories, generate **one grid sheet** (a single `ai` sheet row) instead of one row per element, then slice it (workflow step 2.5 below). Choose sheet geometry from intended placement: `1xN` / `Nx1` are useful for extreme portrait / landscape cells, and a designed `MxN` grid is valid when its cell ratio fits the planned elements. The sheet row is generated but not placed; each cut **element row** (`Acquire Via: slice`) is placed and must appear in `spec_lock.md images`. One generation = one coherent style across all pieces. Resource contract + the geometry rules: [image-generator.md](../references/image-generator.md) §4.3.-> ⚠️ **Honor the confirmed image source before running any generation command**: the `ai` generation path (Path A = `image_gen.py` API / Path B = host-native tool / Offline Manual) is **not** auto-only — a confirmed choice other than `auto` wins, whether it came from chat or, when the page was used, `result.json.image_ai_path`. `host-native` forces Path B even when `IMAGE_BACKEND` is configured; `api` forces Path A; `manual` forces offline. Never run `image_gen.py --manifest` when the confirmed value is `host-native` or `manual`. Full selection rule: [image-generator.md](../references/image-generator.md) §7 Path Selection.+> ⚠️ **Honor the Design Spec's confirmed image source before running any generation command**: the `ai` generation path (Path A = `image_gen.py` API / Path B = host-native tool / Offline Manual) is **not** auto-only — the production value recorded in `design_spec.md §I` wins. `host-native` forces Path B even when `IMAGE_BACKEND` is configured; `api` forces Path A; `manual` forces offline. Never reopen `result.json` here, and never run `image_gen.py --manifest` when the recorded value is `host-native` or `manual`. Full selection rule: [image-generator.md](../references/image-generator.md) §7 Path Selection.Workflow:@@ -311,7 +311,7 @@ Workflow:- [x] analyze_images.py re-run so image_analysis.csv covers the acquired web / AI / sliced images```-**Default — auto-proceed to Step 6.** Only when the user's Step 4 response explicitly opted into split mode (in chat or via Confirm UI `result.json` with `generation_mode: "split"`), output the planning-session handoff below and stop this conversation:+**Default — auto-proceed to Step 6.** Only when `design_spec.md §I` records `generation_mode: split`, output the planning-session handoff below and stop this conversation:```markdown## ✅ Planning Session Complete@@ -377,7 +377,7 @@ python3 ${SKILL_DIR}/scripts/svg_editor/server.py <project_path> --live --daemonpython3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage```-Use `global` as the lock drift guard, `page_context` as the page delta, and `reference_set` under the Executor load policy. The retained Design Spec owns optional `Template Application`. This replaces neither gate artifacts nor source facts. See [`executor-base.md`](../references/executor-base.md) §2.1.+Use `global` as the compact cross-page anchor set, `page_context` as the page delta, and `reference_set` under the Executor load policy. Anchors are defaults and reusable semantic roles, not a color/font allowlist. The retained Design Spec owns optional `Template Application`. This replaces neither gate artifacts nor source facts. See [`executor-base.md`](../references/executor-base.md) §2.1.> ⚠️ **Main-agent only**: SVG generation MUST stay in the current main agent — page design depends on full upstream context. Do NOT delegate to sub-agents.> ⚠️ **Generation rhythm**: P01 → first-page gate → uninterrupted remaining pages → final gate, in one context without batches or mid-run checker calls.@@ -394,16 +394,17 @@ Do not duplicate specialized identity with `data-pptx-role`. Add it only to stru**First-page gate (Mandatory)** — after the **first** SVG page, before drawing page 2:```bash-python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage first-page+python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage first-page --json```-Fix P01 errors and rerun this gate as needed. After it passes, draw P02 through the final page without checker calls.+Run the command unfiltered—do not pipe it through `tail`, `head`, `grep`, or another output truncator. Review the complete P01 issue set from that one run before editing. Select any advisory warnings worth addressing, fix all blocking errors and selected warnings in one consolidated edit pass, then perform one verification rerun. Do not rerun merely to reveal the next issue. If verification still fails, treat its complete output as the next batch and repeat the same review → consolidated edit → single verification cycle; never check between individual fixes. If the terminal output itself is truncated, read only the relevant issue arrays from `validation/svg_quality_first_page_report.json`; do not launch another checker run for discovery. After the gate passes, draw P02 through the final page without checker calls.**Quality Check Gate (Mandatory)** — only after every planned SVG exists, BEFORE annotation handling and speaker notes:```bashpython3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage final --json```- **MUST**: Before this gate, every supported chart/table—including mini charts and sparklines—already has its own draw-time marker plus JSON metadata.-- Any `error` (banned/unsupported SVG features, invalid values, unresolved references, viewBox mismatch, etc.) MUST be fixed before proceeding — return to Visual Construction, regenerate that page, re-run check.+- Run the command unfiltered—do not pipe it through `tail`, `head`, `grep`, or another output truncator. One invocation already scans every page and reports the complete issue set.+- On failure, review all `blocking` errors and all advisory warnings from that run before editing. Choose which warnings merit work, fix every blocking error and the selected warnings in one consolidated edit pass, then perform one verification rerun. If it still fails, its complete output begins the next batch cycle; never run the checker between individual fixes or use repeated invocations to discover one next issue at a time. If terminal output is truncated, extract only `categories.blocking.issues` and, when needed, `categories.introduced.issues` from the report written by that same run.- Every `warning` is advisory and non-blocking: do not return the page for mandatory modification, do not auto-normalize user-authored compatible syntax, and do not require an acknowledgement/disposition line. Recommendation warnings identify the generated-SVG default; fidelity/quality warnings may be reported when material, but the existing input may ship unchanged. If a condition must be corrected before release, the checker must classify it as an `error`, not a `warning`.- The same rule applies to structured-template warnings (empty/framing-only Layout, bare Master, duplicate layout keys): they may guide an optional template cleanup, but warnings alone never fail the quality gate. Flat `style`, free-design, and brand-only routes still rely on their existing hard errors for invalid structure metadata or incomplete required locks.- Run against `svg_output/` (not after `finalize_svg.py` — finalize rewrites SVG and masks violations).@@ -417,6 +418,7 @@ python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage final## ✅ Executor Phase Complete- [x] Live preview started before the first SVG and kept available at the reported URL- [x] P01 gate passed; remaining pages authored without checker calls+- [x] Each failing checker run was reviewed as one complete issue set and followed by one consolidated edit pass; checker output was not filtered- [x] All SVGs generated to svg_output/- [x] Every wrapped prose paragraph uses one `<text>` frame with `<tspan>` line breaks- [x] svg_quality_checker.py passed (0 errors)diff --git a/skills/ppt-master/workflows/governance/failure-recovery.md b/skills/ppt-master/workflows/governance/failure-recovery.mdindex 2e534aff..70f10d57 100644--- a/skills/ppt-master/workflows/governance/failure-recovery.md+++ b/skills/ppt-master/workflows/governance/failure-recovery.md@@ -18,8 +18,8 @@ Global stop/continue rules for all four top-level routes, plus concrete failure| Confirm UI wait timeout | No, if no final result yet | Re-check `result.json` once; keep server cleanup mandatory | Only if user still wants the page | Step 4 same stage or chat fallback || Confirm UI Stage 1 completed then interrupted | Yes until Stage 2 is written/confirmed | Read existing Stage 1 `result.json`, write Stage 2 recommendations, then `--wait-only --wait-stage stage2` | Usually no | Step 4 Stage 2 write/wait || Missing final confirmation | Yes | None | User must confirm or change the values | Step 4 final confirmation |-| Final confirmed value is missing, changed, substituted, or weakened in `design_spec.md` | Yes | Re-read the complete final confirmation state and repair the Design Spec before touching the lock | Only when the confirmed value genuinely cannot be honored | Step 4 Gate 1 — confirmation fidelity |-| `spec_lock.md` changes or omits a machine-relevant Design Spec decision | Yes | Re-project the affected lock rows from the completed Design Spec without making a new design choice | No unless the Design Spec itself is incomplete | Step 4 Gate 2 — lock projection fidelity |+| Final confirmed value is missing, changed, substituted, or weakened in `design_spec.md` | Yes | Repair from the retained final-confirmation object; only a fresh recovery turn with no retained state reads persisted final evidence once | Only when the confirmed value genuinely cannot be honored | Step 4 Gate 1 — confirmation fidelity |+| `spec_lock.md` changes confirmed identity or omits a required execution anchor/routing decision | Yes | Re-author the affected lock rows from the completed Design Spec and current context; do not enumerate page-local literals | No unless the Design Spec itself is incomplete | Step 4 Gate 2 — lock context fidelity || Step 3 rejects a legacy or incomplete template contract | Yes | Stop template consumption; create a new current workspace through Create Template from the original PPTX/reference, then return with its exact workspace root | Only when required source evidence or template choices are unavailable | Create Template → Generate PPTX Step 3 || Formula rendering provider failure | No until the Step 7 readiness gate | Exhaust the provider chain; if unresolved, mark only the affected formula rows `Needs-Manual` and continue | Supply the exact target PNG or change formula policy | Step 4 / Step 7 image readiness gate || AI image generation failure | No | `auto`: follow A → B → Offline Manual. Explicit `api` / `host-native`: retry only that path, then mark the row `Needs-Manual` without switching automated providers | Only when missing files are required before export | Step 5 / Step 7 image readiness gate |@@ -30,7 +30,7 @@ Global stop/continue rules for all four top-level routes, plus concrete failure| Live preview fails to start | No | Continue generation; report that preview is unavailable | Only if user requires browser preview | Step 6 or `live-preview` Step 1 || Live preview closed by user | No | Continue generation | No | Restart through `live-preview` only if requested || Browser annotations submitted during generation | No | Defer application until after Step 7 | User asks to apply annotations | `live-preview` Step 2 |-| `svg_quality_checker.py` error | Yes | Fix the affected SVG, then rerun checker | No unless required asset is missing | Step 6 Visual Construction |+| `svg_quality_checker.py` error | Yes | Review the complete issue set from one unfiltered run; fix all errors and selected warnings in one consolidated edit pass, then perform one verification rerun. If it still fails, use that complete result as the next batch; never check between individual fixes | No unless required asset is missing | Step 6 Visual Construction || `svg_quality_checker.py` warning | No | Continue without mandatory modification or acknowledgement; preserve compatible user syntax, and report material fidelity/quality advice when useful | No | Step 6 advisory warning handling || Missing `notes/total.md` | Yes | Generate speaker notes before Step 7 | No | Step 6 Logic Construction || Step 7 image readiness missing manual files | Yes | None for manual assets; list required filenames and prompts | Yes | Step 7 image readiness gate |@@ -67,10 +67,10 @@ Here, **final confirmation evidence** means either the explicit final confirmati|---|---|| Stage 1 confirmation exists, Stage 2 missing | Write Stage 2 recommendations, then `confirm_ui/server.py <project> --wait-only --wait-stage stage2` || Stage 2 confirmation exists, final confirmation missing | Resume [`generate-pptx`](../generate-pptx.md) Step 4 confirmation orchestration at Stage 3: derive production mechanics from the confirmed solution, then perform the final wait. |-| Final confirmation evidence exists; `design_spec.md` is missing, with or without a surviving `spec_lock.md` | Return to Generate Step 4 and [`strategist.md`](../../references/strategist.md) §6.2; scaffold and write `design_spec.md` from the final confirmation and source analysis, pass Gate 1, then replace the orphan lock's affected rows by projecting from the completed Design Spec. Never reconstruct the Design Spec from an orphan lock. |-| Final confirmation evidence exists; `design_spec.md` exists and `spec_lock.md` missing | Return to Generate Step 4, audit the existing Design Spec against the final confirmation first, then run `project_manager.py scaffold-lock` and fill the lock only from the audited Design Spec. |-| Final confirmation evidence and both planning artifacts exist, but Gate 1 fails | Repair `design_spec.md` from the final confirmation, then re-project every affected lock row. Do not reopen recommendations or infer a replacement from the current lock. |-| Gate 1 passes but Gate 2 fails | Keep the Design Spec unchanged and re-project only the mismatched lock rows from it. |+| Final confirmation evidence exists; `design_spec.md` is missing, with or without a surviving `spec_lock.md` | Return to Generate Step 4 and [`strategist.md`](../../references/strategist.md) §6.2; read final evidence once into the fresh context, scaffold and write `design_spec.md` from it plus source analysis, pass Gate 1, then replace the orphan lock's affected anchors from the completed Design Spec and current context. Never reconstruct the Design Spec from an orphan lock. |+| Final confirmation evidence exists; `design_spec.md` exists and `spec_lock.md` missing | Return to Generate Step 4; in this fresh recovery context read final evidence once to audit the existing Design Spec, then run `project_manager.py scaffold-lock` and author the lock from the audited Design Spec plus current context. |+| Final confirmation evidence and both planning artifacts exist, but Gate 1 fails | In a fresh recovery context read final evidence once, repair `design_spec.md`, then re-author every affected lock row. Do not reopen recommendations or infer a replacement from the current lock. |+| Gate 1 passes but Gate 2 fails | Keep the Design Spec unchanged and re-author only the mismatched lock anchors/routing rows from it plus current context. || No final confirmation evidence is available | Resume Step 4 from the latest stage evidenced by `confirm_ui/result.json`; if no stage is persisted, restart Step 4 at Stage 1. Do not infer confirmed choices from partial planning artifacts. || `design_spec.md` and `spec_lock.md` complete, split mode selected | [`resume-execute`](../stages/resume-execute.md) || Images acquired but SVGs not started | [`generate-pptx`](../generate-pptx.md) Step 6 |diff --git a/skills/ppt-master/workflows/profiles/beautify-pptx.md b/skills/ppt-master/workflows/profiles/beautify-pptx.mdindex 09d7cbf9..8bd9d494 100644--- a/skills/ppt-master/workflows/profiles/beautify-pptx.md+++ b/skills/ppt-master/workflows/profiles/beautify-pptx.md@@ -206,17 +206,17 @@ Write `<project_path>/confirm_ui/recommendations.json` and launch the same confipython3 ${SKILL_DIR}/scripts/confirm_ui/server.py <project_path> --daemon --wait```-Read the confirmed canvas + palette + typography (incl. `body_size`) and any other overrides from `<project_path>/confirm_ui/result.json`. Chat is the canonical fallback when the page cannot open (remote / headless) — present the same fields in chat and honor the reply identically. Always run `--shutdown` on exit (page-confirm or chat-fallback) so port 5050 is free for Step 6 live preview.+After the final wait returns, read `<project_path>/confirm_ui/result.json` exactly once and retain the complete confirmed object through Design Spec authoring. Chat is the canonical fallback when the page cannot open (remote / headless) — present the same fields in chat and retain the reply identically. Always run `--shutdown` on exit (page-confirm or chat-fallback) so port 5050 is free for Step 6 live preview.-On confirmation, enter [`generate-pptx`](../generate-pptx.md) Step 4 as Strategist with the plan pre-resolved. The two beautify invariants always hold: the content-faithful clause ([`strategist.md`](../../references/strategist.md) §d Layer 1) and page count = source slide count (strict 1:1). Everything else comes from the **confirmed** `result.json` — `mode` (recommended `briefing`), canvas, `visual_style`, color (e) + typography (g) incl. `body_size` (the reviewed values; skip both recommendation flows) — honoring whatever the user kept or overrode. §VII = chart/table data → `templates/charts/`, §VIII = source pictures for re-layout.+On confirmation, enter [`generate-pptx`](../generate-pptx.md) Step 4 as Strategist with the plan pre-resolved. The two beautify invariants always hold: the content-faithful clause ([`strategist.md`](../../references/strategist.md) §d Layer 1) and page count = source slide count (strict 1:1). Write the retained confirmed object completely into `design_spec.md` — `mode` (recommended `briefing`), canvas, `visual_style`, color (e) + typography (g) incl. `body_size` (the reviewed values; skip both recommendation flows) — honoring whatever the user kept or overrode. Do not reopen `result.json` afterward. §VII = chart/table data → `templates/charts/`, §VIII = source pictures for re-layout.-**Hard rule — §IX is verbatim and 1:1**: each source slide becomes exactly one page, in source order, its text transcribed word-for-word from `sources/<stem>.md`. Do not merge, split, drop, or rewrite. Write `design_spec.md` + `spec_lock.md` per `strategist.md` §6, then hand off to the Executor.+**Hard rule — §IX is verbatim and 1:1**: each source slide becomes exactly one page, in source order, its text transcribed word-for-word from `sources/<stem>.md`. Do not merge, split, drop, or rewrite. Complete and audit `design_spec.md` first, then author `spec_lock.md` from that Design Spec plus the source/page/template context per `strategist.md` §6 before handing off to the Executor.---## 6. Executor + Export-Run the standard pipeline ([`generate-pptx`](../generate-pptx.md) Steps 6–7). The Executor re-lays-out each page — hierarchy, spacing, alignment, page rhythm — using **only** the inherited palette + fonts from `spec_lock.md`, regenerates charts / tables as native SVG from the extracted data, and re-lays-out the source pictures.+Run the standard pipeline ([`generate-pptx`](../generate-pptx.md) Steps 6–7). The Executor re-lays-out each page — hierarchy, spacing, alignment, page rhythm — using the semantic anchors in `spec_lock.md` plus current page/source/template context; valid page-local colors, gradients, effects, and export-safe display faces need not be added to the lock. It regenerates charts / tables as native SVG from the extracted data and re-lays-out the source pictures.Follow [`generate-pptx`](../generate-pptx.md) Step 7 for the canonical serialpost-processing commands, gates, success criteria, and export artifacts.diff --git a/skills/ppt-master/workflows/stages/refine-spec.md b/skills/ppt-master/workflows/stages/refine-spec.mdindex 92f8a78d..9b509738 100644--- a/skills/ppt-master/workflows/stages/refine-spec.md+++ b/skills/ppt-master/workflows/stages/refine-spec.md@@ -26,7 +26,7 @@ The user **explicitly asks** to refine / review / revise the spec before generat## Step 1: Produce the full spec-Run the default Strategist output exactly as [`generate-pptx`](../generate-pptx.md) Step 4 specifies: write `design_spec.md` (§I–X) from the final confirmation, pass the confirmation-fidelity gate, then project `spec_lock.md` from the completed Design Spec. Read the relevant `sources/` files so the content outline (`§IX`) carries real facts, not skeleton points. Nothing special here — this is the normal spec, just produced under the knowledge that the user is about to review it.+Run the default Strategist output exactly as [`generate-pptx`](../generate-pptx.md) Step 4 specifies: consume the retained final confirmation once into `design_spec.md` (§I–X), pass the confirmation-fidelity gate, then author `spec_lock.md` from the completed Design Spec plus current context as stable anchors/routing rather than an exhaustive value list. Read the relevant `sources/` files so the content outline (`§IX`) carries real facts, not skeleton points. Nothing special here — this is the normal spec, just produced under the knowledge that the user is about to review it.---@@ -47,9 +47,9 @@ The user may revise **any part of the spec**, not just the outline — content oThese overlap with what the confirmed `mode`, visual style, and §6.1 already shape — treat them as discussion angles to surface what is worth talking about, not permission for the Strategist to redo a decision without the user's explicit revision.-**Revise the Design Spec first, then re-project the lock.** An explicit revision the user approves becomes the latest authority for the affected decision and supersedes its earlier confirmation value. Apply it to `design_spec.md` first, then re-project every affected machine value into `spec_lock.md`; lock authoring never decides or overrides the revision. On divergence, repair the lock from the approved Design Spec (see [`strategist.md`](../../references/strategist.md) §6.2). Iterate as many rounds as the user wants. The loop ends only when the user explicitly approves the spec.+**Revise the Design Spec first, then re-author affected lock anchors in context.** An explicit revision the user approves becomes the latest authority for the affected decision and supersedes its earlier confirmation value. Apply it to `design_spec.md` first, then update only the reusable anchors and routing values that the revised Design Spec plus current project/page/template context justify; lock authoring never decides or overrides the revision and never enumerates every legal page-local value. On divergence, repair the lock from the approved Design Spec (see [`strategist.md`](../../references/strategist.md) §6.2). Iterate as many rounds as the user wants. The loop ends only when the user explicitly approves the spec.-**Re-run the route/template preflight after reuse revisions.** If the user changes `template_reuse_scope`, `template_adherence`, `page_layouts`, the Master/Layout definition roster, or any `page_pptx_layouts` assignment, repeat the preflight in [`strategist-template.md`](../../references/strategist-template.md) before approval and hand-back. Switching to `style` rewrites the route to `pptx_structure.mode: flat` and removes all structure mappings/adherence; switching to `mirror` / `layout` restores a complete structured contract. Every newly selected structured prototype must declare root Master/Layout identity, direct atomic Master/Layout visuals, and valid top-level slot groups with positive bounds plus one compatible carrier or explicit composite `object` proxy. A zero-slot Layout is valid. Update the human-facing prototype decisions in the Design Spec first, then re-project `pptx_masters`, unique `pptx_layouts` definitions, and complete `page_pptx_layouts` assignments into the lock. A legacy prototype is not selectable; create a current workspace through [`create-template`](../create-template.md) before refinement.+**Re-run the route/template preflight after reuse revisions.** If the user changes `template_reuse_scope`, `template_adherence`, `page_layouts`, the Master/Layout definition roster, or any `page_pptx_layouts` assignment, repeat the preflight in [`strategist-template.md`](../../references/strategist-template.md) before approval and hand-back. Switching to `style` rewrites the route to `pptx_structure.mode: flat` and removes all structure mappings/adherence; switching to `mirror` / `layout` restores a complete structured contract. Every newly selected structured prototype must declare root Master/Layout identity, direct atomic Master/Layout visuals, and valid top-level slot groups with positive bounds plus one compatible carrier or explicit composite `object` proxy. A zero-slot Layout is valid. Update the human-facing prototype decisions in the Design Spec first, then author the required `pptx_masters`, unique `pptx_layouts` definitions, and complete `page_pptx_layouts` assignments in the lock from the revised template context. A legacy prototype is not selectable; create a current workspace through [`create-template`](../create-template.md) before refinement.---diff --git a/skills/ppt-master/workflows/stages/resume-execute.md b/skills/ppt-master/workflows/stages/resume-execute.mdindex 38293d49..34ba98fe 100644--- a/skills/ppt-master/workflows/stages/resume-execute.md+++ b/skills/ppt-master/workflows/stages/resume-execute.md@@ -53,7 +53,7 @@ Then jump to `### Step 6: Executor Phase` and run the documented pipeline:- Read the Step 6 flat core (`executor-base`, `shared-standards-core`, and the locked mode / visual-style files), then only the branches selected by its condition table- Design Parameter Confirmation- Read the project Design Spec and, when structured, the template Design Spec once; retain both in the fresh execution context-- Per-page `python3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage` load + sequential page generation; the lock projection repeats intentionally, while each prototype/chart SVG is loaded only before its first use or after its SHA changes+- Per-page `python3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage` load + sequential page generation; the stable anchor projection repeats intentionally without becoming a color/font allowlist, while each prototype/chart SVG is loaded only before its first use or after its SHA changes- Quality Check Gate- Speaker notes generation- Step 7: Post-processing & Export (`total_md_split` → `finalize_svg` → `svg_to_pptx`)