Skip to content

Required Changes in Implementation Repositories

Apply the following changes independently in anuva-bento, anuvax-cms, anuva-python-server, and anuva-unity-video-creator after the Product Main process is approved.

Shared changes

  1. Update root AGENTS.md to declare the installed anuva-development plugin as the shared workflow source, GitHub PRs as the code-delivery plane, Linear as explicit tracking, and repository Markdown as the technical record.
  2. Remove GitHub Project, GitHub issue handoff, BrainDump.md, tasks.yml, YAML workflow executor, Codex Goals, Symphony, automated publisher, and browser-agent instructions that conflict with this process.
  3. Discover shared skills through the installed plugin-qualified $anuva-development:<skill> identities. Do not add repository copies of shared Anuva workflow skills. Preserve repository-local domain skills.
  4. Add the workflow prompt references needed by the repository. CMS receives the implement-cms-issue prompt; Python and Unity receive repository-specific variants with the same inputs and outputs.
  5. Add templates for ImplementationPlan.md, ImplementationLog.md, and CompletionReport.md under the existing docs hierarchy.
  6. Add a docs page describing the local mkdocs serve --dirty port and exact machine hostnames: CMS uses web1.girishd.com/web2.girishd.com on port 4002, Python uses python1.girishd.com/python2.girishd.com on port 4013, Unity uses unity1.girishd.com/unity2.girishd.com on port 4004, and Bento uses bento1.girishd.com/bento2.girishd.com on port 4005.
  7. Add an Anuva CLI bootstrap page covering installation, machine configuration, credentials, anuva doctor, read-only discovery, and approval-gated commands.
  8. Update mkdocs.yml navigation so the new process, skills, templates, and active change folders are reviewable.
  9. Keep user-facing sections reachable through meaningful indexes or explicit navigation, and validate documentation with anuva docs verify.
  10. Route repository-local requests through the Routine, Material, or Product Main required preflight. Routine and material work are issue-free by default; create a standalone Linear issue only when explicitly requested.

Repository-specific verification

Repository Required emphasis
anuva-bento Upstream provenance and license integrity, deterministic editor/player builds, sync safety, runtime-contract tests, and strict local docs.
anuvax-cms Lint, typecheck, unit/integration checks, and relevant Playwright projects; document Web-visible acceptance evidence.
anuva-python-server Python formatting/static checks, unit/integration tests, ZeroMQ/job-lifecycle compatibility, and service health evidence.
anuva-unity-video-creator Unity edit/play mode tests where available, compile/import health, deterministic render evidence, and clearly documented manual verification.

Rollout order

  1. Implement and test the Anuva CLI and canonical skills in Product Main.
  2. Adopt the repository-change workflow in Bento.
  3. Adopt the same canonical contract in CMS.
  4. Apply it to Python.
  5. Apply it to Unity without forcing Unity work into automation that is less useful than an interactive Codex task.
  6. Port the manual canonical docs publisher and retire the PowerShell entry point only after parity tests pass.