Skip to content

Implementation Log: ANU-24

Source and approvals

  • Linear issue: ANU-24, implementation-child, repository anuva-unity-video-creator.
  • Parent: ANU-19.
  • Blocker: ANU-20, Done.
  • Product Main foundation: main commit 90837acdcff768558554c8b029b6dea67b461ce9.
  • Unity planning base: f111578b164df0a78f51f7d77e73584bbeaa9c4b.
  • Managed branch: codex/anu-24-adopt-repository-change-workflow-in-anuva-unity.
  • anuva work start ANU-24 --confirm was explicitly approved and ran at 2026-07-28 19:04 UTC, moving Linear from Ready to In Progress.
  • The generated ImplementationPlan was separately approved at 2026-07-28 19:09 UTC.
  • Implementation documentation pre-edit timestamp: 2026-07-28T19:09:25.6489105Z.

Product Main documentation disposition

Not required, revalidated before implementation.

ANU-19 and merged ANU-20 already define the product-wide workflow, issue-kind and CLI contracts, canonical skills, ownership matrix, rollout, and cross-repository acceptance. ANU-24 changes only Unity-owned checked-in skill copies, policy, and local workflow/bootstrap documentation. No Product Main companion branch or PR is permitted for this implementation child.

Implementation record

Repository-change entry point

  • Deleted the Direct Maintenance SKILL.md and agents/openai.yaml.
  • Added the canonical implicit-or-explicit $anuva-repository-change instructions and discovery metadata.
  • Added no README, compatibility alias, deprecated command, recovery path, or duplicate CLI implementation.

Shared lifecycle skills

  • Updated $linear-implement-issue to validate Product Main-created implementation children and marked standalone repository-change issues with kind-specific state, parent, marker, repository, preflight, and link rules.
  • Updated $anuva-implement-issue to preserve separate start/intake, exact-plan, and implementation delivery gates for both supported issue kinds.
  • Updated $anuva-review-and-complete-pr to review and complete either supported issue kind through an independent completion approval.
  • The repository-change and validation skills match the Product Main canonical copies, ignoring line-ending normalization.
  • Implementation and review differ from Product Main only by the approved Unity verification, ownership, contract, and managed-auth additions.
  • Updated UI metadata to match the new supported issue kinds.

Policy and documentation

  • Replaced the old authorization in AGENTS.md with implicit repository-change routing, read-only preflight, exact escalation boundaries, and independent approval gates.
  • Rewrote docs/process/ChangeWorkflow.md for Product Main children, standalone repository changes, no-side-effect escalation, bounded Product Main documentation delivery, and guarded completion.
  • Updated CLI and bootstrap guidance, local process/bootstrap indexes, the docs home boundary wording, this change index, the recursive changes index, and MkDocs navigation.
  • Preserved Unity first-party and vendor boundaries, .meta requirements, serialization safety, package/project escalation, PresentationConfig and Unity/Python protocol boundaries, render/capture evidence, and verification commands.

Escalate no-side-effect scenario

Synthetic request:

Add a renderCallbackUrl field to PresentationConfig, change the Unity/Python lifecycle message to use it, update CMS generation, and deploy both sides.

Disposition: Escalate.

Reasons:

  • changes the shared PresentationConfig render contract;
  • changes the Unity/Python lifecycle protocol;
  • requires Unity, Python Server, and CMS implementation;
  • includes deployment coordination.

Exact Product Main intake returned by the forward test:

  • Title: Define coordinated render callback contract across CMS, Python, and Unity
  • State: Backlog
  • Priority: Normal
  • Label: anuva-main-video-creator
  • Outcome: define an approved callback field, lifecycle semantics, rollout, and verification contract for CMS generation, Python orchestration, and Unity consumption.
  • Constraints: preserve the current payload and protocol until approved; plan all affected repositories; keep secrets and callback authorization explicit; define compatibility and rollout before implementation.
  • Non-goals: no repository-local intake, branch, artifact, PR, or deployment from the Unity preflight.
  • Source request: the synthetic request above.
  • Affected repositories: anuvax-cms, anuva-python-server, anuva-unity-video-creator, and anuva-main-video-creator.
  • Acceptance evidence: approved field/schema semantics, protocol lifecycle, security and deployment constraints, repository handoffs, compatibility behavior, and cross-repository verification.

Before and after snapshots matched exactly:

  • Linear: ANU-24 retained ID e06771b7-dd61-4a39-84eb-a7beb9729bb9, In Progress, implementation child, Unity repository.
  • Git: branch and HEAD remained codex/anu-24-adopt-repository-change-workflow-in-anuva-unity and f111578b164df0a78f51f7d77e73584bbeaa9c4b; the scoped worktree file set did not change during the scenario.
  • Change folder: only index.md and ImplementationPlan.md existed before and after the scenario.
  • GitHub: the same six historical merged PRs existed; no new or open PR was created.

No anuva repository-change start, Linear mutation, branch operation, artifact creation, or GitHub mutation ran for this scenario.

Verification record

  • All six surviving checked-in Anuva skill folders passed the skill-creator quick_validate.py validator with PyYAML 6.0.3; the temporary validator dependency directory was removed.
  • Active content outside this ANU-24 removal record contains no old skill, command, branch-prefix, authorization, or compatibility reference.
  • anuva --help exposes repository-change and no maintenance command group.
  • anuva repository-change --help exposes guarded start, bounded Product Main docs, and complete operations.
  • No local or remote codex/maintenance-* branch exists. Historical merged PRs #6 and #7 remain as immutable GitHub history; no open maintenance PR exists.
  • No Unity executable, scene, prefab, serialized asset, .meta, package, ProjectSettings, StreamingAssets, vendor, protocol, render, capture, or test file changed. Unity import/compile, EditMode, PlayMode, and manual render/capture checks are intentionally not run.
  • git diff --check passed.
  • Recursive documentation indexes validated with no missing or empty indexes.
  • At 2026-07-28 19:26 UTC, all eleven changed documentation pages returned HTTP 200 and matched the fresh strict MkDocs build for the current branch/source generation.

Draft delivery

  • anuva work stage --dry-run listed exactly 22 approved paths and changes.
  • The confirmed stage checkpoint recorded receipt 20260728T192809Z-work-stage-c602.
  • anuva work commit --dry-run listed the same fully staged scope.
  • The confirmed commit checkpoint created 7620cf712cefd648888290a086521e77e0a4a2c6 with receipt 20260728T192842Z-work-commit-4d87.
  • anuva pr create ANU-24 --draft --dry-run showed the exact push, draft PR, link, and In Review transition effects.
  • The confirmed operation created draft PR Shoonya-Game-Technologies/anuva-unity-video-creator#8, linked it to ANU-24, and moved Linear from In Progress to In Review. Receipt: 20260728T192904Z-pr-create-301a.
  • No PR readiness, merge, branch cleanup, local main synchronization, or Linear Done mutation was performed.

Acceptance review

2026-07-28 19:35 UTC

  • Re-read the normalized ANU-24 contract, approved ImplementationPlan, ImplementationLog, CompletionReport, Product Main ANU-19 ChangeBrief and RepositoryImpact, and the complete 22-file PR patch.
  • Confirmed PR #8 is open, draft, targets main, uses exact managed head fc2fe925dfd8639edf0d20aa7ec4554f34b1b91e, and is mergeable.
  • Confirmed the PR has no requested changes. GitHub reports no configured check runs, so there are no failed or pending check contexts.
  • Confirmed the Product Main documentation disposition remains Not required; ANU-19 and ANU-20 already own the cross-repository workflow contract and this child changes only Unity-owned process files.
  • Reconfirmed the canonical repository-change and issue-validation copies, documented Unity-only implementation/review differences, clean managed worktree, complete active-reference search, absent maintenance branches, replacement/root CLI help, git diff --check, recursive docs indexes, exact changed-file scope, and the process-only Unity test skip.
  • Found no acceptance, scope, ownership, security, contract, serialization, package, protocol, render, capture, documentation, review, check, or mergeability gap.
  • Updated the durable evidence and strict previews before presenting the exact completion mutations. No PR readiness, merge, cleanup, synchronization, report-recording, or Linear Done mutation has run.