ANU-8: Anuva Bento Integration

This change replaces Anuva's direct Reveal-oriented slide authoring and playback contract with a structured, versioned Anuva Bento platform shared by Web preview and Unity rendering.

The delivery is intentionally gated. Anuva first established a private Bento downstream and proved the Web feasibility boundary before Product Main authorized the full editor, template, CMS, Unity, and render-package implementation. Unity, Vuplex, and performance evidence remains deferred to the production Unity child.

Change artifacts

• Change brief
• Repository impact
• Implementation issues
• Product decision
• ANU-9 implementation plan
• ANU-9 implementation log
• ANU-9 completion report
• Progress
• ADR 0001: Adopt a private Anuva Bento downstream
• Ideation source

Delivery gates

1. Repository bootstrap: create the private downstream, register it in Product Main and Linear, and install the normal Anuva delivery harness.
2. Feasibility spike: prove maintainable upstream boundaries, offline deterministic Web playback, transparency, assets, and contract feasibility.
3. Go/no-go approval: Product Main accepted the revised spike evidence and recorded proceed on 2026-07-25, with Unity/Vuplex and performance testing deferred to ANU-15.
4. Production delivery: implement the downstream runtime, CMS authoring and compilation, Unity playback, and Python package transport.
5. Clean cutover: remove the active Anuva Reveal contract only after cross-repository acceptance passes.

Current state

• Linear parent: ANU-8
• Priority: High
• Status: In Progress; ANU-9 and ANU-10 are Done
• Product decision: Proceed, recorded 2026-07-25 with Unity/Vuplex and performance testing deferred to ANU-15
• Decision branch: codex/anu-8-anuva-bento-integration-planning
• Production implementation issues: ANU-11 through ANU-16 are Ready and remain governed by their dependency and per-issue approval boundaries
• Canonical publication: not published