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.
Approved Product Main implementation children start through the guarded work command:
Natural or explicit repository-local requests route through
$anuva-development:anuva-repository-change. Its read-only preflight returns
Routine, Material, or Product Main required. Routine and material work is
issue-free by default; material work requires a separately approved exact plan.
Use the standalone repository-change CLI only when the user explicitly requests Linear tracking. Preview that typed intake before requesting approval:
anuva repository-change start <intake-json> --dry-run
anuva repository-change start <intake-json> --confirm
Workflow selection does not approve a material plan, PR readiness, merge,
branch cleanup, base synchronization, evidence updates, or Linear completion.
Use docs/process/ChangeWorkflow.md and the installed plugin for the complete
approval-gated lifecycle.