Skip to content

Completion Report: ANU-23

Outcome

The Anuva Python Server now uses the canonical implicit-or-explicit $anuva-repository-change workflow for repository-local changes. The prior maintenance entry point and active authorization are removed without an alias. The Product Main-created child lifecycle remains supported, and every intake or start, generated plan, and completion mutation remains independently approval-gated.

ANU-23 is implementation-complete on its managed branch and is delivered through draft PR Shoonya-Game-Technologies/anuva-python-server#19. Linear is In Review. The PR is not ready or merged, and the issue is not Done.

Scope and repository boundary

Changed scope is limited to:

  • checked-in Anuva skill instructions and discovery metadata;
  • AGENTS.md delivery policy;
  • local process and bootstrap documentation;
  • ANU-23 plan, implementation log, completion report, indexes, and MkDocs navigation.

No Python runtime, configuration, Web App or Unity contract, ZeroMQ protocol, simulator, dashboard/content server, dependency, operational script, migration, or test file changed.

Product Main documentation disposition

Not required, revalidated before implementation and completion.

ANU-19 and the merged ANU-20 foundation already define the product-wide repository-change workflow, canonical skills, CLI and issue-kind contracts, rollout, and acceptance. This child only adopts those contracts in Python-owned files. No Product Main companion branch or PR is required.

Acceptance evidence

Acceptance item Evidence
Natural repository-local Python changes route to the new skill. .agents/skills/anuva/anuva-repository-change/SKILL.md has an implicit-or-explicit trigger covering code, configuration, tests, docs, prompts, templates, and skills; matching UI metadata is present.
Read-only preflight runs before standalone effects. Repository-change steps 1-3 require ownership/contract inspection and exactly one Product Main documentation disposition before any issue, branch, artifact, or PR.
Escalate returns exact Product Main intake with no side effects. ImplementationLog.md records the deployment/auth/shared-protocol/multi-repository scenario, exact intake, and matching before/after Linear, Git, change-folder, and PR snapshots.
Every allowed mutation and generated plan remains approval-gated. Repository-change, implementation, review, AGENTS.md, and workflow docs preserve separate intake/start, exact-plan, and completion approvals.
Protocol, product, security/privacy, deployment, and multi-repository work escalates. Skill trigger and step 2 enumerate these boundaries; the synthetic scenario exercises protocol, auth/security, deployment, and two repositories.
Direct Maintenance files and active references are absent without an alias. Old skill and metadata are deleted; active-reference search outside this removal record returns no matches; root CLI help has no removed command group.
Shared skill copies match the canonical lifecycle with only Python-specific differences. Repository-change and Linear validation copies match Product Main; implementation/review diffs contain only Python verification and managed-auth additions documented in the approved plan.
Python service, protocol, security, simulator, operational, and verification rules remain intact. AGENTS.md repository purpose, ownership, working rules, docs routing, verification, and escalation sections remain; normalized lifecycle skills explicitly preserve the affected boundaries.

Verification

Check Result
Skill validation for every checked-in Anuva skill Passed
Canonical lifecycle comparison Passed; only documented Python/auth additions
Escalate no-side-effect scenario Passed
Complete active-reference search Passed; no active matches
Replacement/root CLI help Passed
Local/remote maintenance branch inventory Passed; none found
git diff --check Passed
Recursive docs-index validation Passed; no missing or empty indexes
Strict MkDocs build Passed
Fresh live page verification Passed; every changed page returned HTTP 200 and matched the fresh strict build
Focused pytest Not run: no executable Python file changed
Complete PR patch review Passed; all 20 files are within the approved process-only scope
PR reviews No requested changes
PR checks No configured check runs reported; no failed or pending contexts
PR mergeability Open, draft, and mergeable on the exact managed head targeting main

Documentation previews

All pages below were verified against the fresh strict build for the current ANU-23 branch generation:

These previews are review artifacts and are not canonical until merged.

Remaining lifecycle

Acceptance review is complete with no unresolved findings. Completion remains paused for independent approval of the exact mutations:

  1. ready draft PR #19;
  2. run the guarded implementation-child merge with this absolute CompletionReport path;
  3. verify the merge commit;
  4. fast-forward local main;
  5. delete and verify the managed branch locally and remotely;
  6. record completion evidence; and
  7. move ANU-23 from In Review to Done.

No Product Main documentation companion exists or is required for this child.