Completion Review: Repository-scoped change workflow
Review state
- Parent change: ANU-19, In Progress
- Implementation children: ANU-20 through ANU-24, all Done
- Linked implementation pull requests: all five merged
- Product acceptance decision: approved by Girish on 2026-07-28 at 19:55 UTC
- Canonical publication: not published
The reviewed delivery satisfies the approved ANU-19 product and engineering process contract. Product Main now owns a guarded standalone repository-change intake and completion lifecycle, while all four implementation repositories expose the same implicit-or-explicit routing and preserve their local verification boundaries.
Reviewed delivery evidence
| Child | Repository delivery | Durable evidence |
|---|---|---|
| ANU-20 | Product Main PR #20, merged as 90837acdcff768558554c8b029b6dea67b461ce9 on 2026-07-28 |
Completion report |
| ANU-21 | Bento PR #7, merged as 56aebc61a3f95cad8741f73ae785e2b55ba7b218 on 2026-07-28 |
Completion report |
| ANU-22 | CMS PR #41, merged as 536bd745f9db35647041d059c9aca6e09b0eb163 on 2026-07-28 |
Completion report |
| ANU-23 | Python PR #19, merged as 9415cad6022e8bda245e04bdd4e4aade0aa90680 on 2026-07-28 |
Completion report |
| ANU-24 | Unity PR #8, merged as df947bbe50c003431cbf96862ff6ddf24d1095bc on 2026-07-28 |
Completion report |
Product Main inspected current Linear normalization, the complete child reports, current GitHub merge metadata and changed-file lists, local and remote Git state, canonical/local skill differences, active repository content, CLI help, and the Product Main executable verification. Acceptance does not rely only on the child reports.
Product acceptance evidence
| Product criterion | Result | Evidence reviewed |
|---|---|---|
Matching repository-local work can select anuva-repository-change implicitly or explicitly |
Passed | The skill and discovery metadata exist in all five repositories; active AGENTS and workflow pages route matching local work through the preflight. |
| Read-only ownership, affected-file, contract, and Product Main documentation inspection precedes standalone effects | Passed | The canonical skill is identical across Product Main, Bento, Python, and Unity and content-identical in CMS; every adoption report records the pre-mutation sequence. |
Escalate returns an exact Product Main intake and creates no issue, branch, artifact, or PR |
Passed | Product Main schema rejects Escalate as a standalone intake; Product Main tests and each implementation repository's recorded forward fixture cover fail-closed behavior and matching before/after state. |
Only Not required and Required may present and execute a complete standalone intake |
Passed | Versioned schema requires complete scope, acceptance, docs, verification, evidence, repository, priority, and bounded paths before the guarded start operation. |
| Confirmed intake creates or reuses one marked In Progress issue and reconciles its branch idempotently | Passed | Linear SDK marker lookup, exact-contract verification, deterministic branch reconciliation, and create/reuse/restore/dirty-refusal tests passed. |
| Product parents, implementation children, and marked standalone issues cannot cross lifecycle boundaries | Passed | Kind matrix and command guards passed; ANU-20 through ANU-24 completed through the unchanged child path. |
| A generated Implementation Plan receives a separate explicit approval before implementation | Passed | Canonical validation and implementation skills preserve the turn boundary; all five child plans and approval records are durable. |
| Child and standalone delivery share compatible planning, implementation, PR, review, and completion procedures | Passed | Canonical routing and Linear-validation skills match across repositories; implementation/review variants add only documented repository-specific verification and managed-auth guidance. |
| Repository PR creation links Linear and moves delivery to In Review | Passed | Every child had one exact linked PR and moved through In Review before its independently approved merge. |
| Product Main documentation disposition is planned and revalidated | Passed | ANU-20 recorded Required because it changed Product Main itself; ANU-21 through ANU-24 each revalidated Not required because adoption remained repository-owned. |
Bounded Product Main companion delivery is available only for Required standalone documentation |
Passed | Allowlisted paths, distinct managed branch/PR identity, strict preview input, implementation-first ordering, and Done suppression on docs failure passed Product Main tests. No rollout child needed a companion PR. |
| Product decisions and cross-repository needs cannot be smuggled through repository-local docs | Passed | All five policies enumerate mandatory escalation categories; repository forward fixtures exercised representative shared-contract, authentication, migration, deployment, or multi-repository inputs. |
| Completion approval covers readiness, ordered merge, base synchronization, branch cleanup, evidence, and Done | Passed | Each child paused for explicit completion approval and the guarded CLI verified these effects before its Done transition. |
| Repeated intake and completion reconcile supported partial success without duplicates | Passed | Marker reuse, duplicate-PR recovery, branch reconciliation, exact completion-order tests, already-cleaned recovery, and Done suppression on partial docs failure passed. |
| Direct Maintenance and cross-repository issue-free maintenance are completely removed | Passed | Removed skill folders and metadata are absent; Product Main has no maintenance source, help entry, implementation, or tests; invoking anuva maintenance returns unknown command. |
| No active repository content authorizes or references the removed workflow | Passed | Cross-repository search returned zero matches outside immutable ANU-19 through ANU-24 change records; no local or remote maintenance branch remains. |
| Product Main, Bento, CMS, Python, and Unity are aligned without weakening local safeguards | Passed | Canonical routing and Linear validation match line-for-line; implementation/review deltas preserve Bento upstream, CMS auth/schema, Python protocol/security, and Unity ownership/serialization verification. |
| Required executable, skill, index, and strict documentation checks pass | Passed | Product Main typecheck and 74 tests passed; every child report records skill validation, active-reference search, recursive indexes, git diff --check, and strict branch previews. |
Cross-repository reconciliation
| Repository | Current main |
Managed child branch | Worktree note |
|---|---|---|---|
| Product Main | 90837acdcff768558554c8b029b6dea67b461ce9, equal to origin/main before this completion branch |
Absent locally and remotely | Clean |
| Bento | 56aebc61a3f95cad8741f73ae785e2b55ba7b218, equal to origin/main |
Absent locally and remotely | Pre-existing untracked __pycache__/ remains outside delivery scope |
| CMS | 536bd745f9db35647041d059c9aca6e09b0eb163, equal to origin/main |
Absent locally and remotely | Clean |
| Python | 9415cad6022e8bda245e04bdd4e4aade0aa90680, equal to origin/main |
Absent locally and remotely | Clean |
| Unity | df947bbe50c003431cbf96862ff6ddf24d1095bc, equal to origin/main |
Absent locally and remotely | Clean |
The Bento __pycache__/ was present before ANU-21, was excluded from its PR,
and is recorded in its report. It is not treated as a clean-worktree claim or
as an ANU-19 delivery artifact.
Verification review
bun run typecheck: passed on Product Main completion review.bun test: 74 passed, 0 failed, 241 assertions across 18 files.- Product Main repository-change coverage includes schema rejection of
Escalate, kind isolation, marker reuse, path bounds, branch reconciliation, exact implementation-before-docs ordering, partial-failure recovery, and removal of the old CLI group. - Cross-repository active-reference search: zero active matches outside the immutable ANU-19 through ANU-24 change records.
- Canonical comparison: repository-change and Linear-validation skills are content-identical; implementation/review differences are restricted to the documented repository-specific checks and keyring-capable authentication wording.
- Every linked PR is merged and none had configured GitHub status checks. This review records absent checks rather than describing them as passing.
- Every repository's local
mainequalsorigin/main, and every managed child branch is absent locally and remotely. - Recursive Product Main documentation indexes are valid.
The child Completion Reports were authored before their guarded ready-and-merge operations, so some describe the PR as open and the issue as In Review. Current GitHub and Linear evidence supersedes those timing notes: all five PRs are merged and ANU-20 through ANU-24 are Done.
Security, privacy, and recovery review
- Linear content remains typed and is never interpolated into arbitrary shell commands.
- Repository, label, issue, path, URL, base, head, and PR identity validation remains fail-closed.
- Product Main companion delivery is restricted to configured Markdown paths, nearest indexes, and navigation; it cannot change code or decisions.
- Escalation categories explicitly cover product decisions, shared contracts, migrations, authentication/authorization, privacy, security, billing, deployment architecture, release coordination, and uncertain ownership.
- No secret, user data, credential, signed URL, runtime endpoint, or public service is introduced by this process-only rollout.
- Intake and completion retries reconcile durable Linear, Git, GitHub, docs, and cleanup state without rewriting immutable history.
Release impact
ANU-19 is an internal development-process rollout across Product Main, Bento, CMS, Python, and Unity. It changes Codex skills, allowlisted CLI behavior, repository policy, workflow documentation, and durable change records. It does not change product runtime behavior, application contracts, schemas, database state, authentication, billing, deployment architecture, packages, generated artifacts, production services, or public APIs.
No production deployment, database migration, package publication, GitHub
release, or canonical aggregate documentation publication is required.
Repository-local change requests may use the new workflow immediately from the
merged repository main branches. The canonical aggregate remains unpublished
until separately requested.
Remaining follow-ups and limitations
- This rollout proves the canonical workflow through Product Main tests and Product Main-created implementation children. The first live marked standalone repository issue will provide operational evidence for the new SDK-backed intake path without changing ANU-19 acceptance.
- No child required a Product Main documentation companion PR; the bounded companion path is verified by Product Main tests rather than a rollout PR.
- GitHub status checks are not configured for these five repositories; reviewed repository-local verification and strict documentation evidence supply the current acceptance basis.
- The pre-existing Bento
__pycache__/remains unrelated local state.
None of these items is an unfinished ANU-19 acceptance criterion.
Completion decision
The repository-scoped intake, plan approval, implementation, Product Main documentation disposition, independent completion, recovery, removal, cross-repository alignment, security, verification, and documentation requirements are satisfied. Deliver the completion-phase Product Main PR while ANU-19 remains In Progress. Only after that PR merges may the guarded Linear completion command mark ANU-19 Done.
Approval record
- Reviewed by: Girish
- Approved at: 2026-07-28 19:55 UTC
- Approval scope: This Completion Review as written, including the absence of
configured GitHub status checks, the process-only release impact, the
test-backed rather than rollout-PR companion path, and the unrelated Bento
__pycache__/state