[firejune]

The guide now gives a fourth destination: play its generated wave inside an existing PixiJS, Phaser or Three.js app. The Pixi snippet is executed literally against published packages; the other hosts link to their measured minimal examples. The companion profile row already landed in rig-c/.github#1 (21163fec6f265e2cff39a35ee423dbff3d266851).

Running the current public tutorial exposed two existing failures, repaired here:

• Step 7 discarded limbs: step 8 reported CONFIG_PART_ATTACHED: part "handwear_l" (also handwear_r/legwear) and CONFIG_NAME_RESOLVES: config.regions.upperarm_r (eight generated regions total). Copying limbs makes the same build green; reverting only that copy reproduces all 11 refusals.
• Step 9 passed raw motion: POSE_NOT_CLEANED: wave.pose.json has no "cleaned" record. Add the required rig-pose clean stage and retarget its output. The corrected command passes; returning to the original raw-sequence input reproduces that named refusal.

Both controls use the same installed versions: parts 1.25.0, core 2.58.1, pose 0.20.4 and play 1.10.1. No old-version pin or validation bypass substitutes for current public instructions.

The new CI runs the tutorial through step 10 on current published packages, using its documented no-Python keypoint route. It uses the checked-out guide scripts rather than cloning main over the candidate, owns its tutorial server on an allocated port, installs the three literal adapter commands in fresh roots, checks both documents' links, bundles the literal Pixi snippet and observes native WebGL pixels and ticker-driven pose changes. Hidden/stopped native scenes, a missing import and a dead link are real negative controls. Disposable CI installs browser OS dependencies explicitly; ordinary runs download Chromium without changing system packages.

Validation on the exact committed file hashes:

• Strict TypeScript check passed; independent source review found no remaining actionable defect.
• Guarded fresh-consumer run 20261015T084439Z-6f0473e8a0ff41219bf4a367bf1cd7a9: exit 0, 75.849 s, peak process-tree RSS 3,580,002,304 B under 4 GiB; four CPU affinity, no guard rejection.
• Native canvas: 51,154 → 51,741 painted pixels; 30,588 changed channels; pose advanced. Hidden scene: 0/0 pixels. Stopped ticker: 0 changed channels and unchanged pose.
• All 74 links and three fresh installs passed; no Spine runtime in their dependency trees. Both guide regression controls passed.

Final GitHub CI must read the merged remote profile and pass on this PR head before landing.

Closes #2.

[firejune]

Independent source review completed on script SHA-256 379a3dfc8335418e72766aa9edba533bbf0733a7362f81de5a8e9c4dd4630089 and the matching workflow/README snapshots, by a separate Sol reviewer. No remaining actionable source defect was found. Earlier findings were repaired: the tutorial link now targets an owned server; empty/frozen controls change the real native scene; root repository anchors use the actual default branch; thrown bundler errors remain named failures with their cause.

The integrating agent separately read the final source deltas and raw successful execution, then matched all three committed file hashes to that tested snapshot. The actual guide regression controls, native nonempty/moving scene, hidden/stopped scenes and 74 link results passed. Final PR-head GitHub CI remains the landing gate.