Skip to content

Implementation Log: ANU-23

Status

  • Linear: ANU-23, In Review
  • Branch: codex/anu-23-adopt-repository-change-workflow-in-anuva-python
  • Planning base: 3bf4be2088004581a98c950500e617fa6be2bd40
  • Product Main foundation: 90837acdcff768558554c8b029b6dea67b461ce9
  • Product Main documentation disposition: Not required
  • Plan approval recorded: 2026-07-28 18:29 UTC
  • Acceptance evidence updated: 2026-07-28 18:54 UTC

Product Main disposition

ANU-19 already defines the product-wide repository-change process, canonical skills, issue kinds, CLI operations, rollout sequencing, and cross-repository acceptance. ANU-23 changes only Python Server-owned skill copies, repository policy, local workflow/bootstrap documentation, and this implementation record. No Product Main companion documentation PR is required.

The disposition was revalidated before implementation. No new product decision, shared-contract revision, multi-implementation-repository requirement, migration, authentication/authorization change, privacy/security issue, deployment architecture change, release coordination, or ownership uncertainty was introduced by the implementation.

Implementation record

2026-07-28 18:19 UTC - Work started

  • Validated ANU-23 as a Ready implementation-child for anuva-python-server.
  • Confirmed its ANU-20 blocker was Done and Product Main source/preview inputs were complete.
  • Ran the separately approved anuva work start ANU-23 --confirm.
  • Linear moved from Ready to In Progress and the managed branch was created.

2026-07-28 18:21 UTC - Plan previewed

  • Created the change overview and ImplementationPlan only.
  • Added the minimum changes-index and MkDocs navigation entries needed for the preview.
  • Validated recursive indexes, git diff --check, and strict MkDocs.
  • Verified the live overview, ImplementationPlan, and changes index against a fresh strict build.
  • Ended the turn at the mandatory exact-plan approval gate.

2026-07-28 18:29 UTC - Exact plan approved

  • Recorded Girish's separate approval of the current ImplementationPlan.
  • Revalidated ANU-23, its blocker, Product Main inputs, branch, base commit, and unchanged plan.
  • Recorded pre-edit timestamp 2026-07-28T18:29:21.5502527Z and confirmed the branch-specific docs listener before implementation edits.

2026-07-28 18:30-18:42 UTC - Workflow adoption

  • Deleted the checked-in Direct Maintenance skill and discovery metadata.
  • Added the canonical $anuva-repository-change skill and metadata.
  • Updated $linear-implement-issue to validate both Product Main-created children and marked standalone repository-change issues.
  • Updated $anuva-implement-issue and $anuva-review-and-complete-pr to the canonical normalized lifecycle, with only the planned Python-specific verification and managed-auth clauses.
  • Preserved separate mutation, plan, and completion approval gates; bounded Product Main documentation delivery; implementation-first completion; and retryable reconciliation.
  • Updated AGENTS.md, the local workflow, CLI bootstrap, bootstrap context and index, changes index, and change navigation.
  • Preserved all worker, protocol, Web App/Unity adapter, localhost, simulator, path-safety, output-validation, diagnostics, redaction, and external-tool verification rules.
  • The managed workspace prevented the normal patch helper from writing the protected .agents tree. The desired files were generated through patch edits in a temporary repository-local staging folder, copied to only the approved skill targets with scoped filesystem approval, byte-verified, and the temporary files removed.

Escalate no-side-effect scenario

Synthetic natural request:

Expose the Python worker dashboard on the LAN, add bearer-token authentication, and change the Python-to-Unity ZeroMQ contract so remote operators can cancel renders.

Disposition: Escalate.

Reasons:

  • exposing a localhost service changes deployment architecture;
  • bearer-token handling changes authentication and security;
  • the ZeroMQ contract is shared with Unity; and
  • implementation would span the Python Server and Unity repositories.

Exact proposed Product Main intake:

  • Title: Define authenticated remote worker control across Python and Unity
  • State: Backlog
  • Priority: Normal
  • Label: anuva-main-video-creator
  • Outcome: define the approved operator, authentication, network exposure, cancellation, and Python-to-Unity protocol contract before repository implementation.
  • Constraints: preserve localhost defaults and current protocol until approved; keep credentials and signed values out of logs/diagnostics; preserve one-active-job V1 behavior; use normal Product Main planning and repository children.
  • Non-goals: no standalone repository issue, branch, change artifact, PR, implementation, deployment, or compatibility shortcut during preflight.
  • Source request: the synthetic request above.
  • Affected repositories: anuva-python-server and anuva-unity-video-creator.
  • Acceptance evidence: an approved Product Main contract covering threat model, authentication/authorization, network binding, protocol messages, failure and recovery behavior, repository impacts, verification, and rollout.

Before and after the scenario:

  • ANU-23 remained the same In Progress issue with unchanged updatedAt;
  • branch remained codex/anu-23-adopt-repository-change-workflow-in-anuva-python;
  • HEAD remained 3bf4be2088004581a98c950500e617fa6be2bd40;
  • worktree inventory and the sole ANU-23 change folder were unchanged; and
  • open GitHub PR inventory remained [].

No anuva repository-change start, Linear mutation, branch operation, file edit, or PR mutation was invoked for the scenario.

Verification record

  • All six checked-in Anuva skill folders passed the skill-creator quick_validate.py validator.
  • The canonical repository-change and issue-validation skills match Product Main, ignoring line-ending normalization.
  • Implementation/review diffs from Product Main contain only the planned Python-specific verification and managed-auth clauses.
  • Active repository content outside this ANU-23 removal record contains no old maintenance skill, command, branch-prefix, authorization, or compatibility reference.
  • anuva --help exposes repository-change and no removed maintenance command group.
  • anuva repository-change --help exposes guarded start, bounded Product Main docs, and complete operations.
  • No executable Python, worker configuration, protocol, simulator, dependency, script, or test file changed; pytest is intentionally not run.
  • Final Git, index, strict MkDocs, live preview, and PR evidence are recorded in CompletionReport.md.

2026-07-28 18:45 UTC - Local acceptance verified

  • git diff --check passed.
  • Recursive documentation indexes validated with no missing or empty indexes.
  • Strict MkDocs completed successfully. Its only output beyond build success was the existing Material-for-MkDocs upstream warning and the existing notice that bootstrap/index.md and process/index.md are outside explicit navigation.
  • Every changed Markdown page returned HTTP 200 and matched the fresh strict build for the current branch/source generation.
  • The exact preview URLs were recorded in CompletionReport.md.

2026-07-28 18:47 UTC - Draft delivery created

  • Used the guarded stage and commit checkpoints to create commit 5b6bc3248e3c16e5a2a7b06356c438f2120b07d2.
  • Ran anuva pr create ANU-23 --draft --dry-run and reviewed the exact push, draft PR, link, and Linear transition effects.
  • Ran the confirmed operation, creating Shoonya-Game-Technologies/anuva-python-server#19.
  • The CLI linked the PR and moved ANU-23 from In Progress to In Review.
  • The PR remains draft. No ready, merge, cleanup, base synchronization, or Linear Done mutation was performed.

2026-07-28 18:54 UTC - Acceptance review passed

  • Re-read the normalized ANU-23 contract, approved ImplementationPlan, ImplementationLog, CompletionReport, Product Main ANU-19 repository impact and progress, and the complete PR patch.
  • Confirmed PR #19 is open, draft, targets main, uses the exact managed head, and is mergeable.
  • Confirmed the PR has no requested changes. GitHub reports no configured check runs for this process-only repository; there are no failed or pending check contexts.
  • Re-ran all six skill validations, the complete active-reference search, canonical lifecycle comparisons, git diff --check, recursive docs-index validation, and strict MkDocs.
  • Confirmed the only open repository PR is ANU-23 #19 and no local, remote, or open-PR maintenance recovery work exists.
  • Revalidated the Product Main documentation disposition as Not required and confirmed the PR contains no executable Python, configuration, protocol, simulator, dependency, script, or test change. Pytest remains intentionally skipped.
  • Found and corrected the stale top-level Linear status in this log from In Progress to In Review. No implementation finding, requested change, conflict, acceptance gap, or new escalation condition remains.
  • Completion remains paused pending explicit approval of the exact ready and guarded merge mutations.