Anuva CLI Bootstrap

The allowlisted workflow CLI is owned by anuva-main-video-creator and installed as a user-scoped command:

cd C:\Anuva\dev\anuva-main-video-creator
.\scripts\install-anuva-cli.ps1

Machine configuration is %APPDATA%\Anuva\development.yaml. The Bento entry is:

anuva-bento:
  path: C:\Anuva\dev\anuva-bento
  github: Shoonya-Game-Technologies/anuva-bento
  linearRepositoryLabel: anuva-bento
  docsPort: 4005
  docsUrl: https://bento1.girishd.com
  baseBranch: main

Verify from this repository:

anuva context show --json
anuva doctor
anuva linear issue list-ready --repository current --json
anuva repository-change --help

Shared workflow skills are installed through Product Main's anuva-development plugin. Natural repository-local change requests select $anuva-development:anuva-repository-change. The skill performs the ownership and Product Main preflight and returns Routine, Material, or Product Main required.

Routine and material repository changes are issue-free by default. Use the standalone repository-change CLI only when the user explicitly requests Linear tracking. In that case, preview the exact typed intake with:

anuva repository-change start <intake-json> --dry-run

Only after explicit tracking approval does the workflow repeat the identical intake with --confirm. Product Main-created implementation children continue to start through anuva work start. Use $anuva-development:linear-implement-issue and $anuva-development:anuva-review-and-complete-pr for tracked work.

Only the guarded repository-change and Product Main implementation-child lifecycles are supported.

Use LINEAR_API_KEY and GitHub CLI authentication; do not place credentials in the YAML file or repository.