Skip to content

Anuva Development Policy Phase 5 Implementation Plan

Status

Status: Phase 5 and Gate 2 are complete. The five exact reviewed process-only PR heads were readied and squash-merged in the approved order on 2026-07-30, post-merge verification passed, and the five managed branches were deleted.

Phases 1 through 5 are complete. Product Main is at 7270381f562b48dbedc65e2c61392867ed9da486, installed anuva-development plugin version 0.2.0 is enabled from the Product Main marketplace, and packaged CLI build 0.2.1-g2fecf51439fc is active with 0.2.1-g3dd30bca40f1 as its verified rollback target.

This plan remains the durable approval and completion record for Phase 5. It does not authorize Phase 6 rules or machine replication, Phase 7 work, a plugin upgrade, a marketplace/cache mutation, Linear work, or implementation-product changes.

Gate 1 source evidence

The process-only migration was delivered through these exact reviewed heads:

Repository PR Exact reviewed head Squash merge Merged at (UTC) Readiness receipt
Bento #8 5131ba6c751a61688b8649497d8a3e93278e8992 1ea2155dc706c222776624c1a6f05ace2ab25a8f 2026-07-30T05:26:09Z 20260730T052428Z-pr-ready-6789
Web #42 89443ecfe28497c920e059659ee8871da5f4541b 109ccd90de7d0f9bed488dfae02d2963600a40f6 2026-07-30T05:28:10Z 20260730T052628Z-pr-ready-cec9
Python #20 8f814209b0cbb14789a1aa3d0b15f1caa7dfbcaf 596190b65e64cfe7df124083df1d9ded904af026 2026-07-30T05:30:21Z 20260730T052830Z-pr-ready-a97d
Unity #9 c99958229a0f18e8b8060f18d3d27f9adb72a1f2 326f457817e03532d29fb1edb5ea997a912ee660 2026-07-30T05:32:05Z 20260730T053048Z-pr-ready-3919
Product Main #29 bdf5be320c5de76327d6119fc7aae1a53a7572fb 7270381f562b48dbedc65e2c61392867ed9da486 2026-07-30T05:34:43Z 20260730T053230Z-pr-ready-ff65

Gate 1 verification passed:

  • all four implementation repositories changed only their exact instruction, active-doc, and twelve shared-skill deletion paths;
  • Product Main changed only its exact instruction/docs, four validator/test, and sixteen shared-skill deletion paths;
  • all 64 approved duplicated files are absent from the five branches;
  • strict served-page verification passed for all changed documentation;
  • fresh post-removal Codex processes found plugin cache 0.2.0, selected the expected lanes, and found no unqualified checked-in shared workflow skill;
  • Web still discovered its Mastra and text-to-speech skills, whose recorded Git trees are unchanged;
  • Product Main focused tests passed with 8 tests and 82 assertions;
  • Product Main typechecking and the full suite passed with 118 tests and 460 assertions; and
  • no Linear, plugin source, marketplace, cache, rules, machine, Cloudflare, or implementation-product mutation occurred.

At the original Gate 1 delivery, Product Main source validation reported the 0.2.0 plugin source and installed cache valid with all twelve skills, while installed packaged CLI build 0.2.1-g3dd30bca40f1 still contained the pre-Phase-5 compatibility requirement. The separately approved focused amendment below resolved that packaged-runtime boundary before Gate 2 without changing the plugin or expanding migration scope.

Focused packaged CLI acceptance amendment

Status: exact live update, rollback, and inverse rollback completed under the separate approval recorded on 2026-07-30. The approved build is active, the prior build is the rollback target, and the plugin, PATH, product code, sibling PR heads, PR readiness, and merge state remain unchanged.

This amendment exists only to distribute the already reviewed Product Main validator change in PR #29. It does not authorize a new CLI command, option, side effect, schema, dependency, plugin change, Linear mutation, product-code change, PR readiness, or merge.

Prepared artifact

Field Exact value
Version 0.2.1
Build ID 0.2.1-g2fecf51439fc
Source commit 2fecf51439fcfa76d4151c50b79012554b615dc2
Source state clean
Platform win32
Architecture x64
Executable anuva.exe
Bytes 102319104
SHA-256 e2f5bf820b0c1dd35eef6103a5335265387c9919cbd19f8bf4ab14f29186a90b
Build directory C:\Anuva\dev\anuva-main-video-creator\dist\anuva-cli\0.2.1-g2fecf51439fc
Proposed live directory C:\Users\Girish\AppData\Local\Anuva\cli\versions\0.2.1-g2fecf51439fc

bun run check:packaged rebuilt the clean artifact and passed seven packaged, isolated installer, launcher, toolchain, rollback, and inverse-rollback tests with 117 assertions. Direct manifest inspection, SHA-256 recomputation, and anuva.exe --version agree with the table.

The ignored dist/ artifact remains unstaged and unpublished. The separately approved live transaction copied those exact bytes to the versioned local installation without changing the repository artifact.

Pre-install live state

The pre-install live state was healthy:

Field Current value
Runtime packaged
Current 0.2.1-g3dd30bca40f1
Previous 0.2.0-gc8776c067168
Launcher C:\Users\Girish\AppData\Local\Anuva\bin\anuva.cmd
Install root C:\Users\Girish\AppData\Local\Anuva
Running build active and equal to current

The current Codex process resolves the stable launcher through its inherited PATH. The persistent user PATH does not contain the Anuva bin directory. The approved installer command therefore includes -SkipPathUpdate; this amendment does not add, remove, or normalize PATH and does not require a new terminal or elevation.

Exact approved installation

Before mutation, recheck:

  1. Product Main HEAD is 2fecf51439fcfa76d4151c50b79012554b615dc2;
  2. the only working-tree changes are this previewed amendment, docs/development/AnuvaDevelopmentPolicyImplementationPlan.md, and the ignored exact artifact; no CLI source, plugin, marketplace, test, or other repository path differs from HEAD;
  3. artifact.json, executable bytes, version output, size, and SHA-256 match the prepared artifact table;
  4. anuva cli status --json still reports current=0.2.1-g3dd30bca40f1 and previous=0.2.0-gc8776c067168; and
  5. plugin source and cache remain version 0.2.0 and valid.

The separate approval of this exact amendment authorized:

& 'C:\Anuva\dev\anuva-main-video-creator\scripts\install-anuva-cli.ps1' `
  -ArtifactDirectory 'C:\Anuva\dev\anuva-main-video-creator\dist\anuva-cli\0.2.1-g2fecf51439fc' `
  -SkipPathUpdate

Expected live effects:

  • validate and copy the exact artifact to the proposed live version directory;
  • change current from 0.2.1-g3dd30bca40f1 to 0.2.1-g2fecf51439fc;
  • change previous from 0.2.0-gc8776c067168 to 0.2.1-g3dd30bca40f1;
  • atomically rewrite the stable launcher with the same closed packaged-launcher contract;
  • append one redacted cli.install receipt; and
  • leave user PATH, the preserved legacy source, the older version directories, plugin state, repositories, Cloudflare, and running docs processes unchanged.

No installer dry-run exists. The closed artifact schema, trusted direct-child build directory, clean-build requirement, checksum validation, isolated installer tests, exact effect table, and separate approval form its mutation boundary.

Post-install acceptance

Immediately after installation:

  1. require anuva --version to return 0.2.1 (2fecf51439fcfa76d4151c50b79012554b615dc2 clean);
  2. require anuva cli status --json to report a healthy active packaged build with the exact proposed current and previous pointers;
  3. require anuva skills validate --json to report valid plugin source and cache version 0.2.0, twelve skills, no compatibility field, and no errors;
  4. run that validator from Product Main, Bento, Web, Python, and Unity without changing their files;
  5. run anuva doctor --json and anuva context show --json from Product Main;
  6. confirm the plugin, marketplace, cache, five Git branches, draft/merge states, docs listeners, Cloudflare, and Linear are unchanged; and
  7. stop before rollback on any identity, pointer, validation, or scope mismatch.

Exact rollback test

After post-install acceptance, preview the pointer swap:

anuva cli rollback --dry-run

Require the dry run to show:

  • current: 0.2.1-g2fecf51439fc -> 0.2.1-g3dd30bca40f1; and
  • previous: 0.2.1-g3dd30bca40f1 -> 0.2.1-g2fecf51439fc.

Only within the separately approved live amendment, run:

anuva cli rollback --confirm

Then require the old build's version and CLI status to be healthy. Its anuva skills validate --json is expected to report the removed Product Main compatibility copies as missing; that is the known reason for this amendment, not evidence of plugin loss. The source validator must still report the plugin source/cache valid:

bun run src/cli.ts skills validate --json

A fully functional long-term rollback combines the old CLI pointer with restoration of the Product Main checked-in copies. Before merge, that source rollback is abandonment of PR #29 and return to baseline fc5439bf626ab64d66b6f553d7b6761c46611b58. After merge, it is the Product Main PR revert before or together with the CLI pointer rollback. Sibling PRs do not need to change merely to test the CLI pointer.

Exact inverse rollback

Preview the inverse swap:

anuva cli rollback --dry-run

Require:

  • current: 0.2.1-g3dd30bca40f1 -> 0.2.1-g2fecf51439fc; and
  • previous: 0.2.1-g2fecf51439fc -> 0.2.1-g3dd30bca40f1.

Then run, only under the same live-amendment approval:

anuva cli rollback --confirm

Repeat the complete post-install acceptance matrix and finish with current=0.2.1-g2fecf51439fc, previous=0.2.1-g3dd30bca40f1, plugin version 0.2.0, and all five PRs still draft.

Live acceptance evidence

The approved transaction completed on 2026-07-30 with no stop condition:

Stage Receipt Result
Exact install 20260730T050047Z-cli-install-0e3b current=0.2.1-g2fecf51439fc, previous=0.2.1-g3dd30bca40f1, pathUpdated=false, restartRequired=false
Rollback 20260730T050148Z-cli-rollback-1f64 current=0.2.1-g3dd30bca40f1, previous=0.2.1-g2fecf51439fc
Inverse rollback 20260730T050233Z-cli-rollback-80c9 current=0.2.1-g2fecf51439fc, previous=0.2.1-g3dd30bca40f1

The installer recomputed e2f5bf820b0c1dd35eef6103a5335265387c9919cbd19f8bf4ab14f29186a90b, copied build 0.2.1-g2fecf51439fc, preserved the closed packaged launcher, and did not update persistent user PATH. The final version is 0.2.1 (2fecf51439fcfa76d4151c50b79012554b615dc2 clean), and anuva cli status --json reports a healthy packaged runtime whose running executable equals the active versioned target.

Both rollback dry runs proposed exactly the reviewed swaps. The old build was healthy after rollback. Its validator reproduced only the eight expected missing-compatibility-copy errors; marketplace, plugin source, installed cache, version 0.2.0, and all twelve skills remained valid. The Product Main source validator returned valid with no errors. The inverse rollback restored the approved build and the final rollback target exactly.

The complete post-inverse acceptance matrix passed from Product Main, Bento, Web, Python, and Unity:

Check Result
Plugin source valid version 0.2.0, twelve skills
Installed cache valid version 0.2.0, twelve skills
Packaged-validator compatibility field absent in all five repositories
Packaged-validator errors none in all five repositories
Product Main context expected repository and codex/development-policy-phase-5-product-main branch
Keyring-capable anuva doctor --json healthy; every check passed
Persistent user PATH unchanged; Anuva bin remains absent

Only this local CLI installation, its version pointers, stable launcher, and redacted receipts changed. No plugin install or upgrade command ran. No Linear, product-code, sibling-repository, Cloudflare, PR readiness, or merge mutation ran. PR #29 receives only this evidence update and remains draft.

Evidence and approval boundary

The artifact, receipt, pointer, validation, and five-repository evidence is recorded above. Strictly verify the changed plan pages, commit and push only that evidence update, and review the new exact PR #29 head. Do not ready or merge any PR.

Stop and request a revised amendment if:

  • the exact artifact, source commit, size, SHA-256, or clean state changes;
  • current or previous pointers differ before installation;
  • installation would change PATH, require elevation, or touch an unlisted target;
  • source, packaged, plugin, cache, or five-repository validation fails;
  • rollback or inverse rollback proposes a different pointer swap;
  • any repository, PR readiness/merge state, plugin, Linear, Cloudflare, or product path would change; or
  • the old validator's known compatibility result expands into another runtime failure.

Live-amendment approval prompt:

Approve installation of exact clean CLI artifact 0.2.1-g2fecf51439fc with SHA-256 e2f5bf820b0c1dd35eef6103a5335265387c9919cbd19f8bf4ab14f29186a90b using the exact -SkipPathUpdate command, followed by the specified post-install acceptance, rollback to 0.2.1-g3dd30bca40f1, inverse rollback to 0.2.1-g2fecf51439fc, evidence-only PR #29 update, and a stop before PR readiness or merge. Do not modify the plugin, Linear, product code, sibling PR heads, PATH, Cloudflare, or merge state.

Outcome

Phase 5 made the installed skills-only plugin the only active shared Anuva workflow-skill source in Product Main, Bento, Web, Python, and Unity. It:

  • replaced active checked-in-skill references with $anuva-development:<skill>;
  • retained repository-specific ownership and verification rules in each repository's AGENTS.md and active process documentation;
  • removed the duplicated shared skill directories only after fresh-process plugin discovery is reconfirmed for that repository;
  • preserved Web's local Mastra and text-to-speech skills;
  • preserved historical change records unchanged;
  • changed Product Main packaged-skill validation so removed compatibility copies are no longer required; and
  • delivered one process-only PR per repository, coordinated without Linear.

The exit criterion was met: all five repositories discover and use plugin version 0.2.0, no active document invokes an unqualified duplicated shared skill, no checked-in shared Anuva skill directory remains, and no product implementation file changed.

Authority and boundaries

This is a material development-process change under the explicit-only $anuva-development:anuva-development-process-change lane. The approved development policy makes that lane Linear-free.

Phase 5 may change only:

  • repository instructions and active development-process, bootstrap, prompt, and engineering documentation listed below;
  • checked-in shared Anuva skill copies listed below;
  • Product Main's packaged-skill validator description, implementation, and focused tests needed to stop requiring those copies; and
  • this plan, the parent implementation plan, the policy rollout status, and the Development index.

Phase 5 must not:

  • create or mutate a Linear issue;
  • change Bento, Web, Python, or Unity product source, tests, configuration, schemas, assets, packages, or runtime behavior;
  • change Product Main plugin source, manifest, marketplace entry, installed cache, enablement, or plugin version;
  • change CLI commands or side-effect behavior beyond removing the obsolete checked-in-compatibility requirement from anuva skills validate;
  • edit historical docs/changes/** records;
  • remove Web's repository-local Mastra or text-to-speech skills;
  • change Codex rules, machine bootstrap, Cloudflare, MkDocs behavior, or the repository registry; or
  • start Phase 6 or Phase 7.

Any required path or effect outside this boundary stops the phase for a revised plan and separate approval.

Exact baseline

Gate 1 must begin from these repository commits and preserve the recorded pre-existing state:

Repository Baseline main Shared-skill Git tree
Product Main fc5439bf626ab64d66b6f553d7b6761c46611b58 173cfe347a6df4cf4142f4080227611f5c71d9fa
Bento 56aebc61a3f95cad8741f73ae785e2b55ba7b218 7353c72b8db7b239498b4c9486cf7772d4df5fa9
Web 536bd745f9db35647041d059c9aca6e09b0eb163 e546c5330a5ecb6903606c5d9a7ecaaa9ddd5fb8
Python 9415cad6022e8bda245e04bdd4e4aade0aa90680 4926a072bd937eb67dda8e499dc8cb2dcbb2553f
Unity df947bbe50c003431cbf96862ff6ddf24d1095bc 7a97e5ecfdae127a582eaa91de87f1d6eb37d227

Bento also has a user-owned untracked __pycache__/ directory. It must remain untouched and uncommitted.

The durable plugin source is Product Main Git tree 13af45f55514554ba262038dccd5c81986b13da9. The active source and installed cache are version 0.2.0 and had matching checkout tree SHA-256 a2b6ab32b7392db0a04b693132cdc545ae357251cedabc7e054365373c72e740 after Phase 4. Gate 1 must recheck the version, source validation, installed cache validation, and fresh-process discovery before the first deletion. A different plugin identity is a stop condition, not an implied upgrade.

Web's domain-skill baselines are:

  • Mastra tree 27d3ddd43e21dcec1e25e5144035117581b35149; and
  • text-to-speech tree dd84f377254e264d24bb9191d502708fb574ef58.

Canonical skill identities

Every active shared-skill reference changed by this phase must use the plugin-qualified identity:

Existing identity Phase 5 identity
$linear-list-ready-issues $anuva-development:linear-list-ready-issues
$linear-implement-issue $anuva-development:linear-implement-issue
$anuva-implement-issue $anuva-development:anuva-implement-issue
$anuva-repository-change $anuva-development:anuva-repository-change
$anuva-preview-docs $anuva-development:anuva-preview-docs
$anuva-review-and-complete-pr $anuva-development:anuva-review-and-complete-pr
$linear-plan-change $anuva-development:linear-plan-change
$anuva-plan-product-change $anuva-development:anuva-plan-product-change
$anuva-review-product-change $anuva-development:anuva-review-product-change
$anuva-development-process-change $anuva-development:anuva-development-process-change
$anuva-manage-development-environment $anuva-development:anuva-manage-development-environment
$anuva-manage-toolchain $anuva-development:anuva-manage-toolchain

Prose may describe a skill without an invocation token. Any invocation token in an active file must use the qualified form.

Shared copies removed

Bento, Web, Python, and Unity each remove exactly these six directories under .agents/skills/anuva/, comprising one SKILL.md and one agents/openai.yaml per directory:

  • linear-list-ready-issues;
  • linear-implement-issue;
  • anuva-implement-issue;
  • anuva-repository-change;
  • anuva-preview-docs; and
  • anuva-review-and-complete-pr.

Product Main removes exactly these eight directories under .agents/skills/anuva/, also comprising one SKILL.md and one agents/openai.yaml per directory:

  • linear-plan-change;
  • anuva-plan-product-change;
  • anuva-review-product-change;
  • linear-implement-issue;
  • anuva-implement-issue;
  • anuva-review-and-complete-pr;
  • anuva-repository-change; and
  • anuva-preview-docs.

That is 64 duplicated files across five repositories. Empty .agents/skills/anuva/ directories are removed. Other .agents content is out of scope.

Exact repository scopes

Bento

Managed branch: codex/development-policy-phase-5-bento

Allowed modified files:

  • AGENTS.md;
  • docs/bootstrap/AnuvaCli.md;
  • docs/process/ChangeWorkflow.md;
  • docs/prompts/ImplementLinearIssue.md; and
  • the twelve shared-skill files under the six deletion directories.

Repository-specific ownership and verification remain in AGENTS.md and the active process pages. docs/changes/** and __pycache__/ are excluded.

Web

Managed branch: codex/development-policy-phase-5-web

Allowed modified files:

  • AGENTS.md;
  • docs/bootstrap/AnuvaCli.md;
  • docs/process/ChangeWorkflow.md;
  • docs/prompts/ImplementLinearIssue.md; and
  • the twelve shared-skill files under the six deletion directories.

.agents/skills/mastra/**, .agents/skills/text-to-speech/**, docs/changes/**, and all product paths are excluded.

Python

Managed branch: codex/development-policy-phase-5-python

Allowed modified files:

  • AGENTS.md;
  • docs/bootstrap/AnuvaCli.md;
  • docs/bootstrap/BootstrapContext.md;
  • docs/process/ChangeWorkflow.md;
  • docs/prompts/ImplementLinearIssue.md; and
  • the twelve shared-skill files under the six deletion directories.

All service, worker, orchestration, upload, monitoring, protocol, configuration, and test paths are excluded.

Unity

Managed branch: codex/development-policy-phase-5-unity

Allowed modified files:

  • AGENTS.md;
  • docs/bootstrap/AnuvaCli.md;
  • docs/process/ChangeWorkflow.md;
  • docs/prompts/ImplementLinearIssue.md; and
  • the twelve shared-skill files under the six deletion directories.

All Unity project, asset, package, settings, scene, rendering, and test paths are excluded.

Product Main

Managed branch: codex/development-policy-phase-5-product-main

Allowed active-reference and policy files:

  • AGENTS.md;
  • docs/development/DocumentationLifecycle.md;
  • docs/development/ImplementationRepositoryChanges.md;
  • docs/development/ImplementationWorkflow.md;
  • docs/development/ProductChangeWorkflow.md;
  • docs/development/ReviewAndCompletionWorkflow.md;
  • docs/development/DevelopmentEnvironment.md;
  • docs/engineering/AgentInstructions.md;
  • docs/engineering/CodexDevelopmentProcess.md;
  • docs/engineering/PromptSkillCliModel.md;
  • docs/engineering/Skills.md;
  • docs/prompts/ImplementCmsIssue.md;
  • docs/playbooks/RenderProgressWorkflowExample.md;
  • docs/development/AnuvaDevelopmentPolicyPhase5ImplementationPlan.md;
  • docs/development/AnuvaDevelopmentPolicyImplementationPlan.md;
  • docs/development/DevelopmentProcessPolicy.md; and
  • docs/development/index.md.

Allowed validator files:

  • src/cli.ts;
  • src/commands/skills/index.ts;
  • tests/unit/plugin-distribution.test.ts; and
  • tests/unit/skills-validation.test.ts.

Allowed deletions are the sixteen shared-skill files under the eight Product Main deletion directories. Plugin source, marketplace source, CLI operations outside the validator contract, older phase plans, docs/changes/**, and docs/cli-implementation/** are excluded.

The validator change is exact:

  1. rename the command description so it validates plugin source and installed caches rather than compatibility copies;
  2. remove the hard-coded checked-in compatibility inventory and its missing-file errors from validateDevelopmentSkills;
  3. remove the obsolete compatibility result field;
  4. make fixture and distribution tests prove validation succeeds without .agents/skills/anuva; and
  5. retain all marketplace, manifest, metadata, source-skill, and installed-cache validation.

This does not add a command, option, mutation, network call, or arbitrary execution path.

Implementation sequence

Gate 1: process-only source migration and draft PRs

After separate approval of this exact plan:

  1. Reconfirm all five baseline commits and working-tree states. Stop on an unexpected tracked change; preserve known user-owned untracked files.
  2. Run anuva skills validate --json and fresh-process read-only discovery from each repository. Confirm the installed plugin is version 0.2.0.
  3. Rename the current codex/development-policy-phase-5-plan branch to the named Product Main migration branch, preserving this reviewed plan, and create the other four named managed branches from their exact baselines.
  4. For each implementation repository, start its owned docs preview before editing, update only its allowed instruction and active-doc paths, then remove its six checked-in shared-skill directories.
  5. After each repository removal, run the repository's strict documentation verification, git diff --check, the path allowlist proof, and fresh-process discovery/routing checks before proceeding.
  6. Verify Web's two domain-skill trees remain unchanged and discoverable.
  7. Implement Product Main last: update the allowed active references, remove the eight checked-in copies, and apply the exact validator/test change.
  8. Run focused validator/plugin tests, the complete Product Main check, anuva skills validate --json, strict Product Main docs verification, git diff --check, path allowlist proof, and fresh-process routing checks.
  9. Commit and push one complete process-only branch per repository and create five focused draft PRs. Do not ready or merge them.
  10. Review all five exact PR heads, diffs, checks, reviews, comments, review threads, discovery evidence, and rollback order. Present one exact merge-set preview and stop for Gate 2 approval.

Gate 1 approval does not authorize a plugin install/reinstall, cache refresh, marketplace mutation, PR readiness, merge, branch deletion, or Phase 6 work.

Gate 2: reviewed merge set

Gate 2 is a separate user approval guarded to the five exact reviewed PR heads. Before requesting it, the preview must include:

  • repository, branch, PR URL, and exact head commit;
  • complete allowed-path comparison for every PR;
  • docs-verification result and exact HTTPS preview URLs;
  • relevant test/check results;
  • fresh-process plugin discovery and routing evidence;
  • plugin source/cache version and validation result;
  • Web domain-skill tree identities;
  • confirmation that product paths and historical records are unchanged;
  • unresolved review/comment/thread state; and
  • the exact forward and rollback merge order.

On Gate 2 approval, ready and merge only those exact heads in this order:

  1. Bento;
  2. Web;
  3. Python;
  4. Unity; and
  5. Product Main.

If any exact head changes, a required check fails, a blocking review appears, or a required path expands, stop and present a revised merge-set preview.

After all five merges, synchronize each local main, confirm each squash merge commit's tree exactly matches its reviewed head tree, rerun the cross-repository acceptance matrix, and delete only the five managed local and remote branches. Record completion evidence in this plan and the policy status through a focused Product Main completion PR if the reviewed Product Main head cannot truthfully contain post-merge evidence. That completion PR requires its own exact review and approval; it is not implicitly authorized by Gate 2.

Gate 2 completion evidence

Gate 2 completed in the approved Bento, Web, Python, Unity, Product Main order. GitHub reports all five PRs merged at the exact reviewed heads shown above. Because the repository merge method was squash, completion was proven by exact Git tree equality between each reviewed head and its recorded squash merge commit, rather than by an invalid ancestor test. Each local main and origin/main was then synchronized to its exact merge commit.

Post-merge acceptance passed:

  • plugin source and installed cache version 0.2.0 validate with all twelve skills, and fresh-process discovery and routing passed in all five repositories;
  • all 64 approved duplicated shared-skill files remain absent, active invocations are plugin-qualified, and historical change records are unchanged;
  • Web's Mastra tree remains 27d3ddd43e21dcec1e25e5144035117581b35149 and its text-to-speech tree remains dd84f377254e264d24bb9191d502708fb574ef58;
  • strict verification passed for every changed documentation page in all five repositories;
  • Product Main's focused validator/plugin suite passed with 8 tests and 82 assertions, and its full typecheck and suite passed with 118 tests and 460 assertions;
  • packaged CLI build 0.2.1-g2fecf51439fc with approved SHA-256 e2f5bf820b0c1dd35eef6103a5335265387c9919cbd19f8bf4ab14f29186a90b is active, and build 0.2.1-g3dd30bca40f1 is the verified rollback target;
  • the install, rollback, and inverse-rollback receipts are respectively 20260730T050047Z-cli-install-0e3b, 20260730T050148Z-cli-rollback-1f64, and 20260730T050233Z-cli-rollback-80c9;
  • anuva doctor reports the installed runtime healthy;
  • the five managed local and remote migration branches were deleted after synchronization, while Bento's user-owned untracked __pycache__/ remained untouched; and
  • no Linear, plugin source, marketplace, cache, PATH, Cloudflare, implementation-product, or Phase 6 mutation occurred.

Verification matrix

Every repository

  • installed plugin reports version 0.2.0;
  • repository source and installed cache validate;
  • a fresh Codex process lists the relevant anuva-development:<skill> identities;
  • a natural-language repository scenario identifies the correct plugin skill;
  • an explicit plugin-qualified preview or process skill loads from the installed cache;
  • .agents/skills/anuva is absent;
  • active files contain no unqualified invocation of a removed shared skill;
  • historical docs/changes/** files are byte-identical;
  • strict MkDocs verification succeeds for every changed docs page;
  • git diff --check succeeds; and
  • the baseline-to-head file list is a subset of the exact repository allowlist.

Repository-specific

Repository Required evidence
Product Main Focused validator/plugin tests, full check and typecheck, product/development-process routing, valid source/cache, no compatibility requirement
Bento Repository-local change routes to the plugin and retains Bento ownership/test guidance; __pycache__/ untouched
Web Repository-local change routes to the plugin; Mastra and text-to-speech trees unchanged and both local skills discoverable
Python Repository-local change routes to the plugin and retains service, worker, ZeroMQ, upload, and monitoring verification guidance
Unity Repository-local change routes to the plugin and retains Unity project, rendering, and test verification guidance

The machine-one documentation preview bases remain:

Repository Preview
Product Main https://main1.girishd.com/
Bento https://bento1.girishd.com/
Web https://web1.girishd.com/
Python https://python1.girishd.com/
Unity https://unity1.girishd.com/

No implementation-repository product test suite is required for a proven instruction/docs/deletion-only diff. If a product path changes or a repository requires product execution to establish safety, stop because the plan boundary has expanded.

Rollback

Before Gate 2, rollback is branch abandonment or PR closure: each repository's main still contains its checked-in copies, and plugin version 0.2.0 remains installed.

After any partial Gate 2 merge, revert merged PRs in reverse merge order. If Product Main has merged, revert Product Main first so the validator and shared fallback copies are restored before reverting implementation repositories. Then revert Unity, Python, Web, and Bento as applicable. Do not uninstall or downgrade the plugin during repository rollback.

After a complete merge, the primary rollback target is the five PR reverts in this order:

  1. Product Main;
  2. Unity;
  3. Python;
  4. Web; and
  5. Bento.

Each revert must restore the exact recorded shared-skill Git tree and active references, pass strict docs verification, and preserve unrelated work. The Phase 4 merged 0.1.0 source remains the installed-plugin recovery target already proven by Phase 4, but it is used only if the plugin itself fails; a repository migration problem alone uses PR reverts.

Stop conditions

Stop and request a revised plan or new approval if:

  • any baseline commit or tracked working tree differs unexpectedly;
  • plugin version, source tree, cache validation, or fresh-process discovery differs from the recorded baseline;
  • any implementation product path, historical record, domain skill, plugin source, marketplace/cache state, rule, machine configuration, or Cloudflare state would change;
  • a required active reference exists outside the exact allowlist;
  • repository-specific verification cannot remain in allowed instructions/docs;
  • removal causes a plugin discovery or routing failure;
  • the Product Main validator change requires behavior beyond the exact compatibility-requirement removal;
  • strict docs verification, focused tests, full Product Main checks, or PR review is not clean;
  • an exact PR head changes after review; or
  • rollback cannot restore the recorded tree identities without overwriting unrelated work.

Approval prompts

Gate 1 request:

Approve the exact Phase 5 Gate 1 process-only migration plan: create the five named branches, update only the listed active instructions/docs and bounded Product Main validator files, remove exactly the listed duplicated shared skills after discovery checks, verify each repository, and deliver five focused draft PRs. Do not install or upgrade the plugin, mutate Linear, touch product code, or merge.

Gate 2 request:

Approve readiness and merge of the five reviewed Phase 5 PR heads in the presented order, followed by exact post-merge verification and managed branch cleanup. Stop if any head, check, review state, path scope, plugin identity, or rollback evidence differs.