Link report structure and production guidance (0.8.0)

SKILL.md

@@ -2,7 +2,7 @@
 name: ppt-template-workflow
 description: Create and revise template-based editable PPTX decks, design page mockups and materials, reconstruct visual pages into native objects, and maintain portable source projects. Select one external template and theme at a time; includes its own native compiler and workflows without requiring another installed Skill.
 metadata:
-  version: "0.7.4"
+  version: "0.8.0"
 ---
 
 # PPT Template Workflow
@@ -11,7 +11,9 @@ For installation, upgrades and environment checks, read [INSTALL.md](INSTALL.md)
 
 Use **template → theme → layout** as versioned inputs. A catalog can contain multiple independent templates; activate one template and one theme at a time. This skill contains no organization, default palette, template identity or local library path. Templates and themes remain separate packages. Its native compiler, project tools and authoring guidance are bundled; no other installed Skill is required. The installer provides Python libraries and fonts. Image generation and application UI checks use host capabilities when the task needs them.
 
-Read [production rules](references/production-rules.md) for the whole workflow. Preserve source meaning, provenance, real data, implementation claims and rebuildable inputs as requirements; use its planning and design methods as recommendations. Reuse settled choices and review at the authorized granularity. Record justified design exceptions without adding approval gates.
+Read [production rules](references/production-rules.md) for production and content fidelity. Preserve source meaning, provenance, real data, implementation claims and rebuildable inputs as requirements; use its design methods as recommendations. Reuse settled choices and review at the authorized granularity. Record justified design exceptions without adding approval gates.
+
+Report logic, chapter relationships and page content allocation are maintained separately by the optional `report-structure` Skill, including its user examples and derived rules. Consume an existing content plan through [content handoff](references/content-handoff.md): identify what the audience should understand, necessary premises, progression within the page, key reasoning steps and the visual association between conclusions and evidence. This Skill remains independently usable: establish a minimal current-page brief when none is provided, and return consequential content changes for review at the user's agreed granularity. It does not maintain a second narrative rule or example library.
 
 For every authored or reconstructed page, apply the required [text and container rules](references/text-and-containers.md): prefer one native text frame per paragraph; any necessary fragments must remain one logical text block with unified content and layout. Keep substantive explanations out of small muted notes, distinguish different text roles by size/weight/color, and use one shared internal layout implementation per container type/variant. Authors supply content and whole-container bounds, never instance-specific child positions.
 
@@ -50,6 +52,8 @@ Read [authoring handoff](references/authoring-handoff.md) for shared page inputs
 
 For data graphics read [charts](references/charts.md); for native tables, metrics, timelines and explicit linear flows read [components](references/components.md). Their generators return data-bound component groups to compose inside an existing template slot, retaining its UI/Master/Layout. Keep sources and synchronize native payloads and visible fallback. New icons follow [icon production](references/icon-production.md) regardless of whether drawn, generated or externally sourced.
 
+Apply the [visual design boundary](references/visual-design.md#page-composition-and-html-boundary) to every route: do not lay out report pages with HTML/DOM/CSS or convert such layouts through screenshots, printing or other formats. HTML may host a JavaScript visualization itself and its necessary runtime container; surrounding page text and layout use the permitted native/SVG route.
+
 ## Keep a portable source project
 
 When the user needs version control, collaboration or rebuilding after moving devices, read [project workspace](references/project-workspace.md) and use `scripts/ppt_project.py`. Keep stable page IDs, page sources/content/notes, data, assets, the selected template snapshot and an explicit local builder together. Declare the builder's actual dependencies and fonts in the environment metadata; this skill does not install them.