Implementation Log: ANU-21 - Adopt Repository-change Workflow in Anuva Bento
Timeline
| Time (UTC) | Change or decision | Evidence |
|---|---|---|
| 2026-07-28 14:26 | Started the approved implementation child. | anuva work start ANU-21 --confirm; receipt 20260728T142616Z-work-start-f3e0; branch codex/anu-21-adopt-repository-change-workflow-in-anuva-bento |
| 2026-07-28 14:27 | Recorded the planning pre-edit timestamp and ensured the branch-specific Bento docs preview. | Pre-edit 2026-07-28T14:27:03.7745779Z; preview https://bento1.girishd.com |
| 2026-07-28 14:32 | Completed and strictly previewed the planning-only change folder, ImplementationPlan, and navigation. | All three requested pages returned HTTP 200 and matched a fresh strict build. |
| 2026-07-28 14:37 | Received separate explicit approval of the exact current ImplementationPlan. | User message: Approve the ANU-21 ImplementationPlan |
| 2026-07-28 14:37 | Revalidated ANU-21 and the merged Product Main foundation before implementation. | ANU-21 In Progress, kind implementation-child, repository anuva-bento, parent ANU-19, blocker ANU-20 Done; Product Main main at 90837acdcff768558554c8b029b6dea67b461ce9 |
| 2026-07-28 14:43 | Replaced Direct Maintenance and aligned shared lifecycle skills. | Removed the old skill and metadata; added the canonical repository-change skill and metadata; updated validation, implementation, review, and discovery metadata. |
| 2026-07-28 14:46 | Aligned active Bento policy and workflow documentation. | AGENTS.md, docs/process/ChangeWorkflow.md, and docs/bootstrap/AnuvaCli.md |
| 2026-07-28 14:49 | Validated all checked-in Anuva skills. | Skill-creator quick_validate.py: six of six valid |
| 2026-07-28 14:50 | Removed the temporary validator dependency. | Workspace-only .validator-deps/ deleted after validation |
| 2026-07-28 14:54 | Verified the Product Main canonical/local boundary. | Repository-change skill, normalized Linear validator, and all discovery metadata match canonical content; implementation and review differ only by documented Bento verification and managed-auth guidance. |
| 2026-07-28 14:57 | Forward-tested a natural upstream/shared-contract/multi-repository request. | Fresh agent returned Escalate with an exact Product Main Backlog intake and performed no mutation. |
| 2026-07-28 14:59 | Compared no-side-effect snapshots. | HEAD, current branch, worktree delta, change-folder inventory, local maintenance refs, and open PR inventory were unchanged; open PRs remained []. |
| 2026-07-28 15:02 | Verified removed and replacement CLI help surfaces. | repository-change present and maintenance absent from anuva --help |
| 2026-07-28 15:04 | Verified active reference and recovery state. | No active deprecated-workflow reference outside change history; no local or remote codex/maintenance-* branch; no open Bento PR required recovery. |
| 2026-07-28 15:28 | Completed repository and documentation verification. | git diff --check, active-reference search, executable-file scope check, recursive indexes, and seven-page fresh strict MkDocs/live comparison passed. |
| 2026-07-28 15:31 | Committed the verified ANU-21 implementation through the guarded checkpoint. | Commit 0604e00b8dcc1318aca516910f1e80a554fd677b; receipt 20260728T153134Z-work-commit-cd1c |
| 2026-07-28 15:32 | Created and linked the draft implementation PR. | Bento PR #7; Linear moved from In Progress to In Review; receipt 20260728T153209Z-pr-create-c927 |
| 2026-07-28 15:43 | Completed the independent acceptance review. | Reviewed PR head 33f17747d51a57e6301ecdf59ef6883f2446a5f4; complete diff is scoped, PR is mergeable, no review requested changes, no configured check runs, and repository/docs verification reconfirmed. |
Implementation details
Skill lifecycle
- Added the canonical implicit-or-explicit
.agents/skills/anuva/anuva-repository-change/entry point and its UI metadata. - Deleted
.agents/skills/anuva/anuva-direct-maintenance/completely. - Updated
$linear-implement-issueto distinguish and validate: - Product Main-created implementation children; and
- marked standalone repository-change issues.
- Updated
$anuva-implement-issueand$anuva-review-and-complete-prto share the canonical lifecycle while retaining only these Bento-specific additions: - upstream install/build/convergence and focused downstream verification when executable Bento files change;
- an evidence-backed skip when the diff is process-only;
- upstream ancestry/synchronization, provenance, license/notices, artifact, and hard-offline checks when affected;
- recursive indexes and strict Bento previews; and
- managed-sandbox GitHub authentication retry guidance.
Policy and documentation
- Replaced the explicit-only Direct Maintenance authorization in
AGENTS.mdwith implicit repository-change selection, pre-mutation preflight, no-side-effect escalation, and the three independent approval boundaries. - Expanded
docs/process/ChangeWorkflow.mdwith the child and standalone entry paths,Not required/Required/Escalatedispositions, bounded Product Main documentation delivery, implementation-first merge ordering, cleanup, and Linear completion. - Replaced the removed CLI help surface in
docs/bootstrap/AnuvaCli.mdwith the guarded repository-change namespace and its dry-run/confirm contract.
Escalate forward-test evidence
The independent test request was:
Sync Bento to the next upstream release and revise the shared player contract across CMS and Unity.
The checked-in skill classified it as Escalate because it combined an upstream
release, a shared contract, and multiple implementation repositories. It
returned an exact Product Main proposal with:
- title
Coordinate the next Bento upstream release and shared player contract revision; - Backlog state, Normal priority, and
anuva-main-video-creatorlabel; - outcome, constraints, non-goals, source request, affected repositories, and acceptance evidence; and
- explicit confirmation that no Linear issue, branch, change artifact, intake dry-run, or PR was created.
Before/after evidence remained identical:
- HEAD
8dd5c4ff8a8a9760f845b2fc43c34ae6a940e07e; - branch
codex/anu-21-adopt-repository-change-workflow-in-anuva-bento; - the scoped ANU-21 worktree delta and one pre-existing untracked
__pycache__/; - the ANU-21 change-folder inventory;
- no local
codex/maintenance-*ref; and - no open Bento PR.
Commands and results
| Command or check | Result |
|---|---|
anuva linear issue get ANU-21 --json |
Passed; correct child, repository, state, parent, links, and blocker |
anuva repository-change --help |
Passed; start, docs, and complete available |
Root anuva --help assertion |
Passed; repository-change present and removed namespace absent |
Skill-creator quick_validate.py over .agents/skills/anuva/* |
Passed; all six skills valid |
| Normalized canonical content comparison | Passed for repository-change, Linear validator, and all discovery metadata |
| Canonical/local implementation and review diff inspection | Passed; only documented Bento verification/auth additions |
| Escalate forward test and before/after snapshot | Passed; exact Product Main intake, no side effects |
Active-reference search outside docs/changes/** and .git/** |
Passed; no match |
Local and remote codex/maintenance-* branch search |
Passed; none |
| Open Bento PR inventory before and after forward test | Passed; [] |
gh auth status |
Passed for girish-d through the keyring |
git diff --check |
Passed |
| Executable Bento changed-file check | Passed; none |
anuva docs validate-indexes --repository current |
Passed; no missing or empty index |
Seven-page anuva docs wait strict/live comparison |
Passed; every page HTTP 200 and verifiedAgainstStrictBuild: true |
Acceptance review
- Re-read the normalized ANU-21 child, approved ImplementationPlan, ImplementationLog, CompletionReport, Product Main ANU-19 Bento contract, and complete PR diff.
- Confirmed PR #7 targets
mainfrom the exact managed branch, is open, draft, and mergeable. - Confirmed there are no requested changes, review comments, or configured GitHub check runs.
- Re-ran
git diff --check main...HEAD, current-main ancestry, active-reference search, changed-file scope, recursive index validation, and strict preview verification. - Revalidated Product Main documentation disposition
Not required; the diff contains no new product decision, shared contract, upstream release, multi-repository implementation, or Product Main companion requirement.
Network and environment behavior
- Read-only Anuva CLI commands that load the Product Main TypeScript source
initially encountered managed-sandbox
EPERM; required checks were retried successfully in the scoped approved context. - GitHub and remote Git reads initially encountered sandbox network denial; read-only retries succeeded with scoped approval.
- The bundled Python runtime lacked PyYAML. PyYAML
6.0.3was downloaded into workspace-only.validator-deps/, used only forquick_validate.py, and the temporary directory was removed immediately afterward. - No dependency, runtime, package, generated artifact, or upstream source file was changed.
- The pre-existing untracked
__pycache__/remained untouched.
Product-build decision
The changed-file inventory contains only:
- checked-in skill Markdown and
agents/openai.yaml; AGENTS.md;- repository Markdown documentation; and
mkdocs.yml.
Therefore npm ci, the upstream build, Windows single-file build, convergence
tests, downstream typechecks, editor/player tests, template tests, and packaging
checks were intentionally not run, exactly as ANU-21 requires for process-only
edits.