Skip to content

Implementation Issues: Repository-scoped change workflow

Status

All five repository-scoped implementation issues are Done. Their linked PRs are merged, Completion Reports are recorded in Linear, local bases are synchronized, and managed child branches are deleted locally and remotely.

Proposed issues

Client key Linear issue Repository Priority Depends on Status / start gate
product-main-repository-change-foundation ANU-20 anuva-main-video-creator Normal None Done; PR #20 merged as 90837ac
bento-repository-change-adoption ANU-21 anuva-bento Normal ANU-20 Done; PR #7 merged as 56aebc6
cms-repository-change-adoption ANU-22 anuvax-cms Normal ANU-20 Done; PR #41 merged as 536bd74
python-repository-change-adoption ANU-23 anuva-python-server Normal ANU-20 Done; PR #19 merged as 9415cad
unity-repository-change-adoption ANU-24 anuva-unity-video-creator Normal ANU-20 Done; PR #8 merged as df947bb

Issue contracts

The complete scope, acceptance, docs, verification, and Product Main sync requirements for all five issues are defined in Repository Impact. The executable handoff is ImplementationIssues.manifest.json.

All issues require:

  • a read-only pre-mutation eligibility and Product Main documentation preflight;
  • no standalone issue, branch, artifact, or PR when that preflight returns Escalate;
  • the repository's normal linear-implement-issue validation;
  • a guarded anuva work start mutation;
  • a previewed ImplementationPlan and subsequent explicit approval;
  • an ImplementationLog and CompletionReport;
  • repository-specific checks and strict docs preview;
  • a linked draft PR followed by independent completion review; and
  • guarded merge, cleanup, base synchronization, and Linear completion.

Dependency and approval contract

  • The Product Main foundation issue owns the CLI capabilities and canonical shared workflow.
  • The four adoption issues must remain blocked until the foundation issue is Done.
  • No implementation repository may copy the new skill before the CLI contract it invokes is merged and locally available.
  • A material change to issue kinds, implicit-selection authority, Product Main companion scope, merge ordering, or completion semantics returns to ANU-19 planning or a decision phase.
  • Product Main completion begins only after all five issues are terminal with complete PR and report evidence.

Manifest

ImplementationIssues.manifest.json is the typed source used for guarded issue creation. The planning PR merged before the live command created ANU-20 through ANU-24 and their dependency relations.