automate-axlisted

# Automate.ax Own the workflow end to end. Treat the CLI as an implementation detail: run it, answer its non-secret prompts, write the automation code, validate it, and continue through any requested deployment or maintenance work. Do not hand the user a list of commands when you can perform the work. ## Operate the CLI - Work in the user's intended project directory. Inspect existing files before changing anything. - Use Bun. If `bun` is unavailable, install it with `curl -fsSL https://bun.com/install | bash` on macOS/Linux or `powershell -c "irm bun.sh/install.ps1|iex"` on Windows, reload the shell environment, and verify `bun --version`. - For bootstrap and diagnosis without a local installation, run `bunx automate.ax@latest <command>`. Once initialized, prefer the project's installed CLI with `bunx automate.ax <command>` so CLI and SDK stay aligned. - Run `bunx automate.ax@latest --help` or the relevant subcommand help when flags or capabilities are uncertain. Use JSON output only for non-interactive inspection; it disables interactive authorization flows. - Run interactive commands in a persistent terminal/PTY. Respond to choices from known context instead of asking the user to operate the CLI. - Let commands open the user's browser. If a browser cannot open, surface the exact printed URL as a clickable link, keep the command running while it polls, and resume as soon as the user completes the browser step. - Never ask the user to paste passwords, API keys, or provide