Release PPT workflow 0.7.1 with portable installation and production components

SKILL.md

@@ -2,13 +2,17 @@
 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.5.0"
+  version: "0.7.1"
 ---
 
 # PPT Template Workflow
 
+For installation, upgrades and environment checks, read [INSTALL.md](INSTALL.md); for first use and example requests, read [USAGE.md](USAGE.md). Install this root only. Keep the preserved nested compiler attribution entry disabled in agents that recursively discover skills.
+
 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.
+
 ## Select and review
 
 Read the supplied catalog or manifest with `scripts/template_ref.py`. For a foundation project, start with its README consumer links. If the task needs a template and no source is specified, ask once for the source instead of guessing a global library.
@@ -30,12 +34,16 @@ Use the resolved workspace or native template path. v2 can provide a complete na
 
 Keep the user's working style above downstream defaults. For `interactive-page`, finish and review the current page before advancing; page count is not batch permission. Reuse settled route, theme and backend decisions. Explain an actual conflict with its source before continuing.
 
+If the manifest declares `page_library`, read [page examples](references/page-library.md). Use `scripts/page_library.py list` to find compositions, then `inspect --entry <id> --theme <id> --for-use` to verify a compatible reference and its source/preview hashes. Read its rationale, method and actual preview before adapting the source. Examples do not change the active template, palette, layout roster or review sequence. Templates without a library remain supported.
+
 - **Native:** read [native authoring](references/native-authoring.md). Author the current SVG page against its declared layout and compile it with `scripts/native_export.py`, retaining Master, Layout and placeholder identities. Avoid slide-local copies that cover inherited objects.
 - **Page mockups and materials:** read [visual design and materials](references/visual-design.md). Use the host image-generation tool for requested raster mockups, illustrations and image edits; keep exact supplied evidence and identity assets separate from style references. Use existing vectors and the bundled `scripts/paint_asset.py` for declared SVG paint changes.
 - **Image-rebuild:** read [object reconstruction](references/object-reconstruction.md). Inventory the current page, separate background and foreground sources, then author native text and structural objects in the selected SVG layout. Use source material or host image editing where needed; an image assembly is not editable completion.
 
 Read [authoring handoff](references/authoring-handoff.md) for shared page inputs, icon roles and theme changes. Use [PowerPoint checks](references/powerpoint-checks.md) when application opening, rendering or actual editing evidence is needed. If a required host capability is unavailable, finish independent work and name that specific evidence gap; do not substitute an old export or change the selected backend silently.
 
+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.
+
 ## 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.
@@ -46,6 +54,12 @@ When the user needs version control, collaboration or rebuilding after moving de
 
 Preserve the user's page-by-page workflow. Projectization does not authorize batch creation, Git initialization, commits, publishing or global tool installation.
 
+## Collaborate by page
+
+When multiple people or Agents are authorized to share the deck, read [page collaboration](references/page-collaboration.md). The coordinator fixes the narrative, stable page IDs, style snapshot and shared inputs before assigning disjoint page directories. Workers deliver source/content/notes, private assets, previews and a page packet; one coordinator integrates order, shared resources, locks and final compilation. Adapt the bundled [plan](assets/collaboration/plan.example.json) and [packet](assets/collaboration/page-packet.example.json) examples. Parallel work does not itself authorize messaging, batch creation or shared writes.
+
+Prepare useful page-library contributions as sanitized candidates with rationale, implementation, source/assets and preview evidence. The template maintainer reviews and versions them. Do not modify a locked vendor snapshot to publish a candidate.
+
 ## Verify and report
 
 Check the rendered current page and actual editable objects. Distinguish editable text/shapes/tables/charts/formulas, picture exceptions and inherited placeholders. Confirm native structure separately from appearance. Read [runtime and provenance](references/runtime-and-provenance.md) for dependencies, bundled compiler integrity, supported source boundaries and destination font checks.