Release standalone PPT template workflow 0.5.0

USAGE.md

@@ -0,0 +1,19 @@
+# Use the standalone Skill
+
+Read [SKILL.md](SKILL.md), then explicitly select the supplied external template manifest and theme. Use the absolute Skill location; no installed companion Skill or original machine path is required.
+
+```sh
+python3 /path/to/skill/scripts/template_ref.py export-style \
+  --manifest /path/to/template/manifest.json --theme THEME --layout LAYOUT
+python3 /path/to/skill/scripts/template_ref.py resolve \
+  --manifest /path/to/template/manifest.json --theme THEME --layout LAYOUT \
+  --route native --workflow interactive-page
+python3 /path/to/skill/scripts/native_export.py \
+  --manifest /path/to/template/manifest.json --theme THEME \
+  --source /path/to/project/pages/page.svg --source-root /path/to/project \
+  --output /path/to/project/exports/review.pptx
+```
+
+The native exporter accepts released v2 templates, preserves the complete layout roster, and protects existing output. Prepare reviewed page SVGs using the template's slots, typography, grid and paint rules. Inspect actual rendering separately from native structure. See [native authoring](references/native-authoring.md), [PowerPoint checks](references/powerpoint-checks.md), and [project workspace](references/project-workspace.md).
+
+For a portable project, initialize an honest empty skeleton with `ppt_project.py init`. `prepare_native_project.py --project /path/to/project` explicitly copies a local builder/runtime into a clean skeleton. It neither installs dependencies nor updates the author lock automatically. The supplied builder consumes finalized SVGs and notes; data-driven page generation requires the author's explicit binding and build step. Provision the declared dependencies/fonts and verify a relocated rebuild before claiming portability.