AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He
refactor(planning): compact the execution lock contract
hugohe3b17ce8d92301
diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 4fd8cf72..815a802f 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -348,7 +348,7 @@ 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—and project validation requires the six contract key lines under `spec_lock.md ## communication` (any prose value may be blank) 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 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.**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.@@ -373,13 +373,13 @@ The Role Switching Protocol (mandated read of `references/<role>.md` before modeThe 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 communication trace 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 projection plus the exact values Executor must literally use (HEX colors, font stacks, 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.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. `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.+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 --bundle` is route-sensitive: flat pages add no template payload, structured layout pages add the complete selected prototype, and mirror pages add that prototype plus `ppt-master.template-text-slots.v2-min`. Each v2-min slot contains only selector, role, current/segmented text, and tspan count. A top-level tool hash covers selectors plus immutable text/tspan topology and attributes; page-context recomputes it and every projected field from the complete prototype, then strips the hash before model output. Legacy v1 sidecars receive the same compatibility validation and are projected to this shape in memory. The model supplies semantic decisions and replacement text. Checker and structured export validate output attributes, text topology, and resource hashes against the complete prototype internally.diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 070cde44..ffdf4785 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -344,7 +344,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` 中的可见状态是权威输入,不存在确认后的隐藏修正;项目校验还会要求 `spec_lock.md ## communication` 下存在六个沟通契约键(任一文本值都允许留空),并要求 §IX 每个 Slide block 都有 `Audience move`。+**策略师确认阶段是唯一的阻塞 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`。**图片分析走重算元数据,不读像素。** 当项目里存在图片时,Strategist 和 Executor 使用 `analyze_images.py` 的输出(`analysis/image_analysis.csv`),而不是直接打开图片文件。这个 CSV 是基于当前 `images/` 目录重算出来的视图,不是持久缓存。每次做图片敏感决策前重跑分析,就是它的防陈旧策略:用户图、抽取图、网络图、AI 图、公式图和切片图最终都会汇入同一张可度量事实表。@@ -369,13 +369,13 @@ Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workflStrategist 阶段产出两份看起来冗余但服务不同对象的产物:- `design_spec.md` —— 人类可读叙述;deck 的「为什么」(沟通意图、受众变化、叙事 / 模板 / 视觉理由、页面大纲)-- `spec_lock.md` —— 机器可读执行契约;包含紧凑沟通追踪,以及 Executor 必须**字面照搬**的精确值(HEX 颜色、字体栈、图标库、图片资源与结构映射)+- `spec_lock.md` —— 机器可读执行契约;包含紧凑的 `audience` / `objective` / `core_message` 沟通投影,以及 Executor 必须**字面照搬**的精确值(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,只输出创作该页所需的全局执行值和逐页路由事实。该视图省略 Executor core 已经恒定加载的通用 SVG/图标禁令,只保留项目专属 forbidden 行。图片从当前页 brief、图片资源表中的显式页分配和 mirror 原型引用中选择;已分配给其他页面的图片会被排除,仍无法归属的 legacy 图片保留在兼容子集中,只有所有锁定图片都能确定归属到其他页面时才记录 `confirmed-none`。-这份 lock 同时也是逐页路由表。除了全局配色和字体,它还承载 `page_rhythm`(`anchor` / `dense` / `breathing`)、`page_charts`(某页应适配哪个图表模板)、带放置/裁剪契约的图片行,以及决定加载哪些执行规则文件的 `mode` / `visual_style`。`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`,那些段整段省略,而不是写成空值。其余字段的空值本身仍是信号:没有图表、没有图片,很多时候是设计选择,而不是漏填。+这份 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 --bundle` 按路线收敛输入:flat 页面不增加模板 payload;structured layout 页面增加当前完整原型;mirror 页面再增加 `ppt-master.template-text-slots.v2-min`。v2-min 的每个 slot 只包含 selector、role、当前/分段文本和 tspan 数量;顶层 tool hash 覆盖 selector 及不可变文字/tspan 拓扑和属性。page-context 会根据完整原型重算该 hash 与所有投影字段,再从模型输出中剥离 hash;旧 v1 sidecar 也会经过同等兼容校验并在内存中投影成同一形状。模型只负责语义决策和 replacement 文本;Checker 与 structured export 在内部根据完整原型校验输出属性、文字拓扑和资源 hash。diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex d2609fdf..c0dd28aa 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -27,7 +27,7 @@ Always-loaded Executor authority for flat SVG page authoring and behavior shared## 2. Design Parameter Confirmation (Mandatory Step)-Before the first SVG page, output a confirmation listing: the compact communication intent + desired audience outcome, canvas dimensions, body font size, color scheme (primary/secondary/accent HEX), font plan, and the live-preview URL reported by the launcher. If the preview launch failed, state that failure before generating SVGs instead of silently proceeding. Prevents purpose/spec/execution drift.+Before the first SVG page, output a confirmation listing: the compact communication objective, canvas dimensions, body font size, color scheme (primary/secondary/accent HEX), font plan, and the live-preview URL reported by the launcher. If the preview launch failed, state that failure before generating SVGs instead of silently proceeding. Prevents purpose/spec/execution drift.### 2.1 Per-page execution context (Mandatory)@@ -37,11 +37,11 @@ Before the first SVG page, output a confirmation listing: the compact communicatpython3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --bundle --record-usage```-Use the bundle's communication, canvas, mode/style, colors, typography, icons, current §IX brief/locks, and optional `global.template_application`. The latter governs which template content stays, changes, or moves; reuse/adherence select exporter mechanics only. This projection overrides neither facts, locks, nor technical constraints. After an approved lock change, rerun it before drawing the affected page.+Use the bundle's communication, canvas, mode/style, conditional `mode_behavior` / `visual_style_behavior`, colors, typography, icons, current §IX brief/locks, and optional `global.template_application`. The latter governs which template content stays, changes, or moves; reuse/adherence select exporter mechanics only. This projection overrides neither facts, locks, nor technical constraints. After an approved lock change, rerun it before drawing the affected page.**Source facts**: The bundle carries page intent and locked execution values, 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.-**Per-page communication trace**: Read the current §IX `Core message` and `Audience move` before choosing composition. The page must advance at least one purpose named in `communication.communication_intent` and move the audience toward `communication.audience_outcome`; `communication.core_message` remains the deck-wide north star. A page that cannot state this movement is an upstream outline defect — surface `warning: P<NN> has no communication move` instead of compensating with decorative layout. Do not invent a new purpose, ask, or outcome at execution time. Structural pages may advance the contract by establishing relevance / tension / decision frame or by completing the final commitment; they are not exempt from having a reason to exist.+**Per-page communication trace**: Read `communication.objective`, `communication.core_message`, and the current §IX `Core message` + `Audience move` before choosing composition. The page must advance the compact objective and move the audience as authored in §IX; the global core message remains the deck-wide north star. A page that cannot state this movement is an upstream outline defect — surface `warning: P<NN> has no communication move` instead of compensating with decorative layout. Do not invent a new purpose, ask, or outcome at execution time. Structural pages may advance the contract by establishing relevance / tension / decision frame or by completing the final commitment; they are not exempt from having a reason to exist.**Per-page reading-mode check**: Read `communication.consumption_mode` before choosing the page's composition. Apply it together with the authored §IX block texture and `page_rhythm`:diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex e4dad258..6b1615ad 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -406,9 +406,10 @@ Generate Step 4 owns both artifact scaffolds. `design_spec.md` is the Strategist⛔ **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.-**Execution lock content**: `spec_lock.md` is the compact machine projection of the completed Design Spec for 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 `content_divergence` into the lock; its effect is already authored into §IX. 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 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.- - **Communication trace is mandatory**: Project `audience`, `communication_intent`, `audience_outcome`, `core_message`, `delivery_context`, `artifact_afterlife`, and canonical `consumption_mode` from the audited Design Spec into `spec_lock.md communication`. 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 section / field presence, not the subjective quality of the move.+ - **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.- **page_rhythm is mandatory**: Based on the page list in §IX Content Outline, assign each page one of `anchor` / `dense` / `breathing`. This is what breaks the uniform "every page is a card grid" feel. New locks may not omit the section; consumer omission behavior is owned by [`executor-base.md`](executor-base.md) §2.1.- **Fact IDs and scenario labels are mandatory when applicable**: Read any `sources/*.facts.json`. For each §IX page, list the stable IDs actually used; never cite an ID whose claim is absent from the page. Mark invented KPIs/targets/internal ratios as `Data class: scenario` and state which values are scenario data. Executor carries external sources into notes/footnotes and renders a visible scenario label for scenario figures.- **Rhythm follows narrative, not quota**: `breathing` pages mark natural pauses — chapter transitions, standalone emphasis (hero quote / big number), SCQA bridges. Dense decks may legitimately be all `dense`. **Do NOT invent filler pages** ("Thank you", empty dividers) to pad rhythm — every `breathing` page must say something independent. Consumption mode biases the overall lean (`presentation` toward more `anchor` / `breathing`, `text` toward `dense`; see §6.1) — a bias, never a quota.diff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.mdindex 0bc6f26f..36e3dd2b 100644--- a/skills/ppt-master/scripts/docs/confirm_ui.md+++ b/skills/ppt-master/scripts/docs/confirm_ui.md@@ -203,7 +203,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations- `recommend.*` names each recommended id. New mode / style values use a catalog id or literal `custom`; arbitrary prose values are legacy-only. Use `recommend.image_strategy: "custom"` only when an explicit user-supplied image direction should start selected. Missing recommendations fall back to the normal preset. Legacy aliases remain accepted; new files write canonical ids.- `custom_candidates` is recommendation-only. Mode / style carry localized `name` + `behavior`; conditional image strategy also carries `rendering: "custom"`, `visual`, and `mood`. The server rejects missing required candidates; the UI shows full copy, edits it only after selection, rejects a selected blank, and omits unselected candidates from `result.json`. Template-backed proposals obey inherited identity, prototype capacity, and `template_application`.-- `audience`, `communication_intent`, and `audience_outcome` are load-bearing Stage-1 reasoning inputs, so seed concrete recommendations when the evidence supports them; they are not required user inputs. Every Stage-1 prose field may be blank after confirmation, while the six communication keys remain present as key lines in `spec_lock.md communication`. `communication_intent` may preserve several purposes plus priority / sequence; never add a `primary_job` enum.+- `audience`, `communication_intent`, and `audience_outcome` are load-bearing Stage-1 reasoning inputs, so seed concrete recommendations when the evidence supports them; they are not required user inputs. Every Stage-1 prose field may be blank after confirmation. The complete six-field contract stays in `result.json` and `design_spec.md`; `spec_lock.md communication` receives only the compact `audience` / `objective` / `core_message` execution projection plus the applicable reading mode. `communication_intent` may preserve several purposes plus priority / sequence; never add a `primary_job` enum.- Do not write `recommend.template_reuse_scope` or `recommend.template_adherence`. Strategist records those internal exporter values later in `spec_lock.md` after inspecting the actual template and current content.- For an active template workspace, write one editable prose field as top-level `template_application.value`. It summarizes actual page/prototype use and preservation/reorganization decisions. Omit it for free design. The UI returns the current string through Stage 2, Stage 3, and final confirmation; Strategist then persists the final effective plan as `- **Template Application**: ...` in `design_spec.md §I`, and `page-context` projects it to Executor. Never replace it with internal reuse/adherence ids or a fixed option menu.- `recommend.image_usage` should be an array of source ids when more than one source applies, e.g. `["ai", "provided"]`. A single string is still accepted for backward compatibility. Do not write bare `"custom"` and do not encode a mixed-source plan as prose here; write the prose to top-level `image_notes.value`.diff --git a/skills/ppt-master/scripts/project_utils.py b/skills/ppt-master/scripts/project_utils.pyindex 8b1133c7..4f277f92 100644--- a/skills/ppt-master/scripts/project_utils.py+++ b/skills/ppt-master/scripts/project_utils.py@@ -93,11 +93,8 @@ _DESIGN_SPEC_NAMES = ()_COMMUNICATION_TRACE_KEYS = ('audience',- 'communication_intent',- 'audience_outcome',+ 'objective','core_message',- 'delivery_context',- 'artifact_afterlife',)@@ -242,7 +239,7 @@ def validate_communication_trace(check_lock: bool = True,check_design: bool = True,) -> List[str]:- """Validate either or both legacy communication-trace surfaces."""+ """Validate either or both communication-trace surfaces."""root = Path(project_path)design_spec = next((root / name for name in _DESIGN_SPEC_NAMES if (root / name).is_file()),@@ -378,7 +375,7 @@ def validate_project_structure(Args:project_path: Project directory pathverbose: Whether to show detailed fix suggestions- validate_communication: Whether to run the markerless legacy trace check+ validate_communication: Whether to run the communication trace checkReturns:(is_valid, error_list, warning_list)diff --git a/skills/ppt-master/templates/scaffolds/spec_lock.md b/skills/ppt-master/templates/scaffolds/spec_lock.mdindex 82b523bd..d765b434 100644--- a/skills/ppt-master/templates/scaffolds/spec_lock.md+++ b/skills/ppt-master/templates/scaffolds/spec_lock.md@@ -7,11 +7,8 @@## communication- audience:-- communication_intent:-- audience_outcome:+- objective:- core_message:-- delivery_context:-- artifact_afterlife:- consumption_mode: [fill]## modediff --git a/skills/ppt-master/templates/schemas/spec_lock.schema.json b/skills/ppt-master/templates/schemas/spec_lock.schema.jsonindex ca0ec973..1b90da7a 100644--- a/skills/ppt-master/templates/schemas/spec_lock.schema.json+++ b/skills/ppt-master/templates/schemas/spec_lock.schema.json@@ -74,27 +74,18 @@"required": true,"required_fields": ["audience",- "communication_intent",- "audience_outcome",- "core_message",- "delivery_context",- "artifact_afterlife"+ "objective",+ "core_message"],"allow_empty_fields": ["audience",- "communication_intent",- "audience_outcome",- "core_message",- "delivery_context",- "artifact_afterlife"+ "objective",+ "core_message"],"allowed_fields": ["audience",- "communication_intent",- "audience_outcome",+ "objective","core_message",- "delivery_context",- "artifact_afterlife","consumption_mode"],"field_enums": {diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.mdindex 1724f731..1e9f134a 100644--- a/skills/ppt-master/templates/spec_lock_reference.md+++ b/skills/ppt-master/templates/spec_lock_reference.md@@ -21,7 +21,7 @@ The command refuses to overwrite an existing `spec_lock.md`. Re-running it with| Section | Required keys | Notes || --- | --- | --- || `canvas` | `viewBox`, `format` | `format` is the canonical display name (for example `PPT 16:9`); `viewBox` is the matching exact geometry |-| `communication` | `audience`, `communication_intent`, `audience_outcome`, `core_message`, `delivery_context`, `artifact_afterlife` | Values may be empty after explicit confirmation; `consumption_mode` is optional off PPT canvases |+| `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 |@@ -71,6 +71,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.+- `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`.- `page_rhythm` grammar: `P` + at least two digits (`P01`, `P100`) followed by `anchor|dense|breathing`.diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 15aa8139..bb509257 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -253,7 +253,7 @@ After filling the lock, compare its machine-relevant values against the complete- [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] Communication trace validated: `spec_lock.md ## communication` contains all six contract key lines (optional values may be blank), and every `design_spec.md §IX` Slide block has an `Audience move`+- [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```