Anuva CLI Bootstrap
The workflow CLI is owned by anuva-main-video-creator and is exposed as the
user-scoped anuva command on every development machine.
Open a new terminal or Codex process after the installer changes user PATH. The
launcher lives at %LOCALAPPDATA%\Anuva\bin\anuva.cmd, delegates to the current
Product Main checkout, and preserves the implementation repository as the
working directory. Rerun the installer after moving that checkout.
Verify configuration and context from this repository:
anuva doctor --json
anuva context show --json
anuva linear issue list-ready --repository current --json
anuva repository-change --help
The machine config is %APPDATA%\Anuva\development.yaml. Keep secrets out of
the file; use LINEAR_API_KEY and gh auth login. Every mutation requires a
reviewed dry run or explicit --confirm at the user-approved workflow boundary.
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 returns Routine,
Material, or Product Main required after its ownership and risk preflight.
Routine and material 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 typed intake:
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. Do not create generic Linear issues, change Linear manually, or merge implementation PRs directly through GitHub.
In anuvax-cms, pnpm anuva:cli remains the application-specific presentation
tool. It is unrelated to the global delivery command anuva.