Skip to content

Completion Report: ANU-21 - Adopt Repository-change Workflow in Anuva Bento

Implementation summary

ANU-21 replaces the Bento repository's issue-free Direct Maintenance entry point with the canonical Product Main-owned repository-change workflow. Natural repository-local requests now select a read-only ownership and Product Main documentation preflight before any standalone mutation. Product Main-created children and marked standalone issues then share explicit plan-first, draft-PR, and independently approved completion lifecycles.

The implementation is process-only. It changes checked-in skills, discovery metadata, repository policy, workflow/bootstrap documentation, and ANU-21 evidence. It does not change Bento runtime source, contracts, schemas, dependencies, templates, builds, packages, artifacts, provenance, license, or notices.

Acceptance evidence

Acceptance item Evidence Result
Natural repository-local Bento changes route to the new skill. Canonical implicit trigger in .agents/skills/anuva/anuva-repository-change/SKILL.md; aligned AGENTS.md and workflow docs Passed
Preflight occurs before any standalone issue, branch, artifact, or PR. Repository-change steps 1-3; process flow; forward test Passed
Escalate returns an exact Product Main intake with no side effect. Independent upstream/shared-contract/multi-repository forward test plus identical before/after HEAD, branch, worktree, folder, ref, and PR snapshots Passed
Every mutation and generated plan remains approval-gated. Repository-change intake approval; implementation-child start approval; mandatory subsequent plan approval; independent completion approval in updated skills and docs Passed
Product, shared-contract, upstream-release, and multi-repository requests escalate. Skill trigger/body, AGENTS.md, process docs, and representative forward test Passed
Direct Maintenance files and active references are absent with no alias. Deleted skill and metadata; zero active-reference matches; root CLI help contains repository-change and no removed namespace Passed
Shared skills match the canonical lifecycle with only documented Bento differences. Exact normalized comparisons plus focused implementation/review diffs Passed
Bento upstream, provenance, license, artifact, and verification rules remain intact. Existing repository docs unchanged; localized skill/AGENTS guardrails; no executable or distribution file in diff Passed
Required implementation records and local docs are complete. ANU-21 index, plan, log, report; updated process/bootstrap docs and navigation Passed

Verification commands and results

Check Result
ANU-21 Linear normalization Passed: implementation-child, anuva-bento, In Review, ANU-19 parent, ANU-20 Done, linked PR #7
Product Main foundation Passed: merged main commit 90837acdcff768558554c8b029b6dea67b461ce9
Six skill validations Passed
Canonical/local skill and metadata comparison Passed
Escalate forward test Passed with exact Product Main proposal and no side effect
Replacement/removal CLI help assertion Passed
Complete active-reference search Passed; no active match outside change records
Local/remote maintenance branch and open PR audit Passed; none
git diff --check Passed
Recursive documentation index validation Passed; no missing or empty index
Fresh strict MkDocs build/live comparison Passed; all seven requested pages returned HTTP 200 and matched the strict build

Acceptance review

  • Reviewed PR head: 33f17747d51a57e6301ecdf59ef6883f2446a5f4.
  • PR #7 is open, draft, targets main from the exact managed branch, and is mergeable.
  • GitHub reports no requested changes, review comments, or configured check runs.
  • The complete 18-file diff is process-only and matches the approved plan and Product Main ANU-19 Bento contract.
  • Current main is an ancestor of the PR head; local and remote managed branch heads match.
  • Active deprecated-workflow references remain absent outside immutable change history, and no executable Bento file entered the diff.
  • Recursive indexes and the exact strict branch previews remain valid.
  • Product Main documentation disposition remains Not required.

Documentation and preview URLs

These URLs are branch previews, not canonical publication.

Product Main synchronization

Disposition: Not required.

ANU-19 already defines the product-wide repository-change contract, repository ownership matrix, rollout sequencing, and cross-repository acceptance. ANU-20 merged the CLI foundation and canonical skill lifecycle. ANU-21 changes only Bento-owned skill copies, policy, and local workflow/bootstrap docs. Product Main progress and completion evidence remain owned by ANU-19; this child must not create a Product Main documentation companion PR.

The disposition was revalidated after implementation. No new product decision, shared-contract change, multi-repository implementation, migration, authentication/authorization, privacy/security, billing, deployment, upstream-release, release-coordination, or ownership uncertainty entered the ANU-21 diff.

Product-build skip

No executable Bento file changed. The diff is limited to skills, metadata, policy, Markdown, and MkDocs navigation. Product install/build/convergence, single-file, typecheck, editor/player, template, packaging, compatibility, and network tests were therefore intentionally skipped under the approved ANU-21 verification contract.

Delivery

  • Branch: codex/anu-21-adopt-repository-change-workflow-in-anuva-bento
  • Planning base: 8dd5c4ff8a8a9760f845b2fc43c34ae6a940e07e
  • Verified implementation commit: 0604e00b8dcc1318aca516910f1e80a554fd677b
  • Reviewed delivery-evidence commit: 33f17747d51a57e6301ecdf59ef6883f2446a5f4
  • Draft PR: Shoonya-Game-Technologies/anuva-bento#7
  • Linear state: In Review
  • Product Main documentation companion: not applicable

Remaining risks and skipped checks

  • Product builds were not run because there is no executable or distribution file in scope.
  • The forward test validates one representative mandatory-escalation path; the canonical Product Main CLI tests remain the authority for typed intake, idempotency, companion delivery, ordered completion, and partial recovery.
  • The pre-existing untracked __pycache__/ is unrelated and was not changed, staged, or included in verification scope.