Progress: Repository-scoped change workflow

Product change

Item	State	Evidence
Linear parent ANU-19	In Progress	Linear issue; started 2026-07-28
Planning branch	Merged and deleted	codex/anu-19-introduce-repository-scoped-change-workflow-and-planning
Product plan	Approved	Change brief and repository impact; approved by Girish 2026-07-28 08:01 UTC
Plan preview	Verified	Strict Product Main preview verified before and after approval
Planning PR	Merged	PR #19; merged 2026-07-28
Product Main foundation child	Done	ANU-20; PR #20 merged as 90837ac
Bento adoption child	Done	ANU-21; PR #7 merged as 56aebc6
CMS adoption child	Done	ANU-22; PR #41 merged as 536bd74
Python adoption child	Done	ANU-23; PR #19 merged as 9415cad
Unity adoption child	Done	ANU-24; PR #8 merged as df947bb
Product completion review	Approved	Completion Review reconciles every child, product criterion, repository, release effect, and known limitation; approved by Girish on 2026-07-28 at 19:55 UTC

Current decisions

• Run a read-only Product Main impact and eligibility preflight before creating any standalone issue, branch, change artifact, or PR.
• On Escalate, return the reasons and exact proposed Product Main intake and perform no repository-change mutation.
• Replace issue-free maintenance with a marked, standalone, repository-labeled Linear issue created directly in In Progress only after a Not required or Required preflight.
• Allow implicit skill selection while retaining explicit approval for every mutation and generated plan.
• Reuse the existing implementation and review procedures through typed issue-kind normalization.
• Permit at most one bounded Product Main documentation companion PR under the same standalone issue.
• Merge implementation before companion documentation and complete Linear only after all required delivery and cleanup verifies.
• Delete both issue-free maintenance skills and the complete anuva maintenance CLI surface with no compatibility alias; the pre-removal audit found no open maintenance PR or surviving local/remote maintenance branch.
• Deliver Product Main CLI/canonical workflow before synchronizing the four implementation repositories.

Current gate

All five child issues are Done, their PRs are merged, their managed branches are deleted locally and remotely, and every local main equals origin/main. Cross-repository acceptance passed with no blocking finding, and the current Completion Review is approved. The next gate is guarded delivery of its completion-phase PR followed by the parent Done transition.

Next proposed sequence

1. Stage and commit the approved completion evidence through guarded Product Main checkpoints.
2. Create, ready, and merge the ANU-19 completion-phase PR while the parent remains In Progress.
3. Run the guarded Linear completion operation and verify ANU-19 is Done.