Skip to content

Implementation Issues: Anuva Bento Integration

Status

These repository-scoped Linear children for ANU-8 were approved by Girish on 2026-07-24 at 06:06 UTC and created through the reviewed implementation manifest. ANU-9 completed the repository bootstrap, and ANU-10 completed the revised Web-feasibility spike.

On 2026-07-25, Product Main recorded proceed based on ANU-10 evidence. Unity/Vuplex verification and performance testing were explicitly deferred from ANU-10 to ANU-15. The deferral does not waive final product acceptance. ANU-11 through ANU-16 remain Ready and may start only through their normal dependency and implementation-plan approval boundaries.

Proposed issues

Client key Linear issue Repository Priority Depends on Status / start gate
main-bento-bootstrap ANU-9 anuva-main-video-creator High None Done
bento-feasibility-spike ANU-10 anuva-bento High ANU-9 Done; proceed decision recorded
bento-runtime-contract ANU-11 anuva-bento High ANU-10 Ready; Product Main proceed gate satisfied
bento-editor-templates ANU-12 anuva-bento High ANU-11 Ready; blocked on dependency
cms-bento-v2 ANU-13 anuvax-cms High ANU-11 Ready; blocked on dependency
cms-bento-editor-ai ANU-14 anuvax-cms High ANU-12 and ANU-13 Ready; blocked on dependencies
unity-bento-three-player ANU-15 anuva-unity-video-creator High ANU-11 and ANU-13 Ready; owns deferred Vuplex/performance evidence
python-bento-package ANU-16 anuva-python-server High ANU-13 and ANU-15 Ready; blocked on dependencies

Issue drafts

main-bento-bootstrap: Register and bootstrap the Anuva Bento repository

  • Linear issue: ANU-9
  • Repository: anuva-main-video-creator
  • Priority: High
  • Dependencies: None
  • Status: Done
  • Implementation plan: ImplementationPlan.md

Scope

Create the approved private Shoonya-Game-Technologies/anuva-bento downstream from a recorded upstream Bento release tag and commit while preserving ancestry. Set origin to the private repository and upstream to https://github.com/nyblnet/bento.git. Configure protected main, ownership, license/notices, and a reviewed upstream-sync policy.

Add anuva-bento to Product Main's repository registry, architecture, capability map, Linear repository label guidance, CLI repository allowlist, development configuration, docs preview/publisher mappings, and tests. Install the standard Anuva repository instructions, issue/PR skills, prompts, templates, change-doc structure, and docs-preview workflow in the new repository. Expand ImplementationIssues.manifest.json with the already approved downstream issue drafts only after the new key and label validate.

This issue owns repository and workflow bootstrap, not Bento product changes.

Acceptance

  • The private repository exists under the approved organization and is not a public GitHub fork.
  • The recorded upstream tag and SHA are present with ancestry, branches, tags, MIT license, copyright, and third-party notices intact.
  • origin, read-only-normal-operation upstream, protected main, ownership, and sync-branch policy are documented and verified.
  • The unmodified selected upstream baseline installs, builds, and passes its applicable tests before any Anuva product modification.
  • Linear has exactly one anuva-bento repository label and the Anuva CLI can read, start, submit, and complete a validated Bento issue.
  • The CLI/config/docs/publisher allowlists and repository-context tests include anuva-bento without becoming arbitrary-string executors.
  • The new repository has AGENTS instructions, standard skills/templates, implementation workflow docs, a strict MkDocs preview, and launcher verification.
  • Rehearsing an upstream sync branch does not overwrite downstream refs.
  • The expanded manifest validates and a dry run shows the approved dependency graph without creating issues.

Docs

Update Product Architecture, Repository Registry, Capability Map, Linear workflow/configuration, Anuva CLI/configuration, docs environment, aggregate publisher mapping, and this change's Progress/ImplementationIssues records.

In anuva-bento, create the repository overview, provenance, architecture, development workflow, Anuva CLI bootstrap, upstream-sync/release procedure, security/license notes, templates, and the issue ImplementationPlan, ImplementationLog, and CompletionReport. Return exact preview URLs for both repositories after each logical documentation update.

Verification

Run Product Main typecheck, unit/integration tests, manifest validation, CLI help/dry-run/context tests, strict MkDocs build, recursive docs-index validation, launcher/install checks, and configuration parsing on safe examples.

Run the selected upstream Bento install/build and applicable test suite, verify the tag/SHA/remotes/branch protection/license/notices, verify no secrets or mirror credentials entered Git, run the downstream strict docs/index checks, and exercise one no-product-change issue/PR dry run in repository context.

bento-feasibility-spike: Prove Anuva Bento editor/player and Vuplex feasibility

Accepted scope revision

The approved ANU-10 implementation plan replaced Unity execution with a Web host that simulated the later Unity-owned authoritative clock. It also deferred performance and three-player profiling. Product Main accepted the resulting evidence on 2026-07-25 and recorded proceed without claiming the two deferred areas as passed.

Unity/Vuplex compatibility, capture behavior, and three-WebView profiling remain mandatory ANU-15 acceptance work and final ANU-8 completion evidence.

Scope

Create the smallest maintainable Anuva adapter layer needed to prove a structured document in the Bento editor, a read-only player entry, a Web host, and Unity Vuplex. Prototype the composite three-surface envelope and a versioned external control API. Disable update/collaboration network behavior. Exercise one Main, one Companion, and one transparent Emphasis document with representative fonts, images, SVG, charts, transitions, fragments/states, and supported media.

Measure three concurrent players and arbitrary deterministic seek. Rehearse one upstream merge to measure the downstream conflict surface. Treat all spike APIs as provisional and publish no production package.

Acceptance

  • The selected Bento baseline builds reproducibly from the private downstream.
  • Anuva changes remain concentrated behind documented adapters/build entries rather than pervasive upstream edits.
  • One representative document renders consistently in editor, Web player, and Unity Vuplex while offline.
  • Three concurrent players meet proposed memory, CPU/GPU, startup, and frame-time thresholds or provide evidence for a reviewed fallback.
  • External reset/seek/tick restores deterministic state after arbitrary scene navigation; transparent Emphasis output works.
  • Required fonts/assets become ready before capture and no production-mode request reaches Bento update or collaboration services.
  • Template reapplication preserves semantic content in the representative case and reports unsafe mappings.
  • The upstream merge rehearsal preserves Anuva adapters and documents recurring conflict risk.
  • A go/no-go report maps every criterion to evidence and recommends proceed, revise, or stop.

Docs

Maintain ImplementationPlan, ImplementationLog, and CompletionReport. Document the provisional envelope/API, source-change map, Web/Vuplex setup, asset matrix, network observations, performance measurements, upstream rehearsal, and go/no-go evidence. Synchronize the report to Product Main.

Verification

Run upstream/downstream builds and tests, contract fixtures, editor/player host tests, offline network capture, Web browser checks, Unity compile/import and Vuplex manual/automated checks, deterministic seek/replay comparisons, transparency/asset tests, three-player profiling, and strict docs/index builds.

Do not begin any production child until Product Main records explicit “go.”

bento-runtime-contract: Build the Anuva Bento contract and deterministic player

  • Repository: anuva-bento
  • Priority: High
  • Dependencies: bento-feasibility-spike

Scope

After the Product Main go decision, implement the production versioned contract package and read-only player. Define composite presentation, surfaces, timeline, template metadata, stable identities, runtime compatibility, schemas, validation, pure-data transformations, structured errors, player commands/events, external clock behavior, transparency, readiness, and asset loading.

Package exact-version static player artifacts and a server-safe private contract package. Disable editor-only, update, and collaboration behavior in the player.

Acceptance

  • Runtime schemas accept valid fixtures and reject incompatible or unsafe data with stable errors.
  • The contract package has no editor DOM dependency and works in CMS server tests.
  • The player exposes the approved load/reset/seek/tick/show/hide/clear/fragment API and readiness/error events.
  • Deterministic replay and arbitrary seek pass across approved animations and representative assets.
  • Player artifacts are versioned, checksummed, offline, transparency-capable, and retain required notices.
  • Compatibility metadata lets CMS, Python, and Unity reject unsupported combinations before use.

Docs

Maintain implementation plan/log/report plus normative schema, compatibility, player API, error, asset, packaging, security, license, and release documentation. Provide fixtures and exact downstream preview/package references to consumers.

Verification

Run typecheck/lint/unit/integration/build, schema property/fixture tests, deterministic clock/seek tests, readiness/asset/error tests, network-denial checks, artifact checksum/version/license inspection, consumer smoke tests, and strict docs/index validation.

bento-editor-templates: Build the Anuva Bento editor and template families

  • Repository: anuva-bento
  • Priority: High
  • Dependencies: bento-runtime-contract

Scope

Implement the Anuva editor build, host bridge, three-surface navigation, semantic content bindings, template-family schema, coordinated Main/Companion/Emphasis layout packs, family/layout application, media adapters, undoable commands, and validated AI-operation primitives. Provide load/save/revision messages without owning CMS persistence.

Acceptance

  • One editor instance can focus and edit all three independent surfaces while preserving presentation context.
  • A versioned template family styles all surfaces coherently and respects surface dimensions, transparency, and safe areas.
  • Theme/layout/family changes preserve compatible semantic content and user extras, warn on unsafe mappings, and undo atomically.
  • Host messages validate origin, schema, revision, and runtime compatibility.
  • AI primitives are typed, validated, auditable, surface-aware, and contain no unrestricted script execution.
  • Editor production mode disables public update/collaboration behavior and uses the same renderer version as the player.

Docs

Maintain implementation plan/log/report plus editor-host protocol, template authoring/versioning, semantic bindings, AI operation catalog, media adapters, undo/failure behavior, security, and example-family documentation.

Verification

Run typecheck/lint/unit/integration/build, editor bridge/origin/revision tests, template preservation/undo tests, semantic and AI-operation validation, three-surface editing scenarios, accessibility/keyboard checks, network-denial checks, fixtures, and strict docs/index validation.

cms-bento-v2: Implement PresentationConfig v2 and multi-surface compilation

  • Repository: anuvax-cms
  • Priority: High
  • Dependencies: bento-runtime-contract

Scope

Replace active Reveal-oriented presentation contracts with PresentationConfig v2 and the Anuva Bento aggregate. Implement persistence and revisions, multi-surface narrative planning, complementary surface-item compilation, authoritative timeline resolution, contract validation, assets, immutable render-package assembly, fixtures, and clean development-data recreation.

Acceptance

  • Representative narratives compile valid, complementary Main, Companion, and Emphasis documents with stable identities and one authoritative timeline.
  • Scene mapping supports zero or more items per surface, persistence, replacement, clear, fragments/states, and transient emphasis.
  • Aggregate revisions and conflict primitives are durable and validated.
  • Packages pin compatible contract/player versions and immutable asset identities or checksums without credentials or expiring render dependencies.
  • Active generation no longer produces direct Reveal markup after cutover.
  • Fresh development data and fixtures use v2 exclusively.

Docs

Maintain implementation plan/log/report and update PresentationConfig, generation/agents/tools, persistence/revisions, timing, assets, validation, render-package, migration/cutover, failure/recovery, and testing documentation.

Verification

Run CMS lint/typecheck/unit/integration and relevant Playwright checks, schema and fixture tests, multi-surface generation/timing/property tests, package checksum and offline-asset checks, persistence/conflict tests, clean database recreation, Reveal-path search, consumer compatibility tests, and strict docs/index builds.

cms-bento-editor-ai: Embed the Bento editor, AI Assistant, and shared preview

  • Repository: anuvax-cms
  • Priority: High
  • Dependencies: bento-editor-templates, cms-bento-v2

Scope

Launch the Anuva Bento editor from the Scene Editor with full-presentation context and scene/surface focus. Implement authenticated load/save/autosave, aggregate revision conflicts, media integration, template selection/application, validated AI Assistant operations, undo/recovery, and Web preview through the exact shared player version.

Acceptance

  • Users can open, edit, autosave, and preview all three surfaces for any scene.
  • Conflicting revisions preserve both persisted and unsaved work and present a tested resolution path.
  • Template and AI changes target the intended presentation/surface scope, validate before persistence, remain undoable, and record attribution.
  • Web preview uses the saved document and same exact player version packaged for Unity.
  • Iframe messaging validates origin/schema; documents and assets carry no access tokens or executable AI output.
  • Failure, reconnect, stale-runtime, and unsupported-document states are clear and recoverable.

Docs

Maintain implementation plan/log/report and update user workflow, Scene Editor, editor host/auth protocol, persistence/conflicts, AI tools, templates/media, preview/versioning, security, accessibility, failure/recovery, and tests.

Verification

Run lint/typecheck/unit/integration and relevant Playwright projects; exercise load/save/autosave/conflict/undo, origin/schema/security failures, surface focus, template/AI operations, asset behavior, preview/runtime parity, accessibility, network-denial, and strict docs/index validation.

unity-bento-three-player: Integrate three deterministic Bento Vuplex players

  • Repository: anuva-unity-video-creator
  • Priority: High
  • Dependencies: bento-runtime-contract, cms-bento-v2

Scope

Replace the active generated Reveal/regex HTML path with three long-lived Anuva Bento players hosted in Vuplex. Load the staged surface documents, map them to Main/Companion/Emphasis outputs, execute the authoritative timeline from Unity time, support reset/seek/tick/readiness/errors, and enforce asset readiness before capture. Remove duplicate Unity-local production contracts after acceptance.

Acceptance

  • Three surfaces render simultaneously from one package and report the exact expected player/runtime version.
  • Arbitrary scene seek/reset restores identical state on all surfaces.
  • Main/Companion persistence and Emphasis show/hide/transparency behave as specified.
  • Fonts, images, SVG, charts, approved media, fragments/states, and animations are ready and deterministic before capture.
  • Player/package/version/readiness failures stop rendering with structured errors.
  • Three-WebView profiling meets approved thresholds or a Product Main-reviewed alternative is implemented.
  • Direct Reveal bridge assumptions and duplicate production contract classes are removed after cutover.

Docs

Maintain implementation plan/log/report and update virtual screens, player bridge, package loading, authoritative timing, seek/reset, assets/readiness, errors, performance, capture, cutover, and verification documentation.

Verification

Run Unity compile/import health, applicable Edit/Play Mode tests, bridge/schema tests, three-surface fixtures, arbitrary seek/replay, transparency/assets/media, version/readiness/error paths, three-WebView profiling at approved resolutions, representative capture comparison, Reveal-path search, and strict docs/index validation.

python-bento-package: Validate and stage Bento v2 render packages

  • Repository: anuva-python-server
  • Priority: High
  • Dependencies: cms-bento-v2, unity-bento-three-player

Scope

Accept the finalized PresentationConfig v2 render package, validate contract and runtime versions plus checksums, stage player assets/documents/timeline/media in an immutable job-local layout, invoke Unity with that package, preserve artifact identity across retries, and propagate structured Bento/Unity failures without transforming presentation content.

Acceptance

  • A complete package reaches Unity unchanged after version/checksum validation.
  • Unsupported versions, missing files, checksum mismatches, or unsafe paths fail before Unity startup with stable structured errors.
  • Retry reuses or recreates the same immutable artifact identities according to the approved lifecycle contract.
  • Staging contains no credentials and does not depend on expiring URLs or public Bento services.
  • Existing render progress, cancellation, upload, and cleanup behavior remains correct for v2 jobs.

Docs

Maintain implementation plan/log/report and update render package, validation, staging, job lifecycle, retries, cancellation, cleanup, structured errors, security, monitoring, and testing documentation.

Verification

Run formatting/static/unit/integration checks; valid/invalid package fixtures; version/checksum/path-traversal/missing-asset tests; retry/cancel/cleanup tests; Unity handoff and representative render smoke; structured-error propagation; credential/network inspection; and strict docs/index validation.

Dependency and approval contract

  • main-bento-bootstrap is the only issue in the initial manifest.
  • The bootstrap CompletionReport must prove the repository, label, allowlist, and normal delivery workflow before the expanded manifest is used.
  • bento-feasibility-spike must complete before its dependent issues unblock.
  • A completed spike is evidence, not authorization. Product Main must record an explicit go/no-go decision in Progress.md.
  • If the decision is “revise” or “stop,” production issues remain unstarted and ANU-8 returns to planning or cancellation review.
  • Product Main completion begins only after all required children are terminal and every merged PR and CompletionReport is available.