create-aura3d 1.0.10 → 1.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-aura3d",
-  "version": "1.0.10",
+  "version": "1.1.0",
   "type": "module",
   "bin": {
     "create-aura3d": "dist/cli.js"

package/templates/cartoon-channel/README.md

@@ -13,6 +13,16 @@ It uses:
 - Child-safe, reduced-motion, and high-contrast accessibility proof defaults.
 - Primitive-mouth and typed-GLB viseme examples.
 - Phoneme/viseme/dub source proof metadata for stable shot, storyboard, caption, line, and word timing ids.
+- A deterministic sample episode visual layer at `/?sampleTime=24` so reviewers
+  can see a clean cartoon frame sourced from the same shot/caption contract.
+- An Aura3D-rendered cartoon scene graph for visual review: moon garden,
+  stylized robot characters, props, lights, camera, captions, and typed GLB
+  character asset evidence through `src/aura-assets.ts`.
+- A release-facing route that deliberately ignores the rejected
+  `concept-2-5d`, `puppet-2d`, and `image-puppet` query views. Those earlier
+  experiments remain only as negative evidence: still-image parallax, flat
+  cutout motion, and `notTrue3D` proof are not accepted as Aura3D 1.1 cartoon
+  animation readiness.
 
 Replace primitive characters with typed GLB assets by running:
 
@@ -35,6 +45,34 @@ model(assets.miko);
 
 Do not replace this with a string asset id or a raw loader.
 
+Run the sample episode visual test:
+
+```bash
+npm test
+```
+
+The visual test captures a review frame at:
+
+```text
+tests/reports/prompt-animation/cartoon-sample-episode.png
+```
+
+Run the failed-puppet negative gate:
+
+```bash
+npm run test:negative-failed-puppets
+```
+
+That gate proves the old `?view=concept-2-5d`, `?view=puppet-2d`, and
+`?view=image-puppet` query strings fall back to the supported sample episode
+route and do not expose release-facing puppet/parallax proof objects.
+
+Do not use `tests/reports/prompt-animation/cartoon-image-puppet-animation.webm`
+or the old 2.5D/cutout routes as product evidence. Aura3D's accepted cartoon
+animation proof must come from typed assets or explicitly segmented rigs with
+independent body-region motion, caption timing, visible mouth movement, and
+render/package evidence.
+
 This scaffold intentionally does not claim publish readiness from source alone.
 Before closing build, route, asset, screenshot, render, or visual-quality gates,
 archive the matching `npm run build`, `assets validate-cartoon`, browser