Harden TUI input and smoke coverage

Author: Evan1108-Coder

.env.example

@@ -1,16 +1,16 @@
-# This file is for the project being set up, not P-Setup's own AI keys.
-# Store P-Setup provider API keys globally with:
+# This file is for the project being set up, not Setupr's own AI keys.
+# Store Setupr provider API keys globally with:
 #
-#   setup auth set-key github
-#   setup auth set-key minimax
-#   setup auth set-key moonshot
+#   setupr auth set-key github
+#   setupr auth set-key minimax
+#   setupr auth set-key moonshot
 #
 # Project app variables belong here, for example:
 # DATABASE_URL=postgres://localhost/app
 # NEXT_PUBLIC_API_URL=http://localhost:3000
 
 # Optional local override for this project only.
-# Prefer `setup auth use <model>` for your global default.
+# Prefer `setupr auth use <model>` for your global default.
 # P_SETUP_AI_MODEL=openai/gpt-4.1-mini
 
 # Optional logging verbosity: debug, info, warn, error.

ENVREADME.md

@@ -2,14 +2,14 @@
 
 ## Setupr AI Provider Keys
 
-Setupr provider API keys should be stored globally with `setup auth`, not in a project `.env` file:
+Setupr provider API keys should be stored globally with `setupr auth`, not in a project `.env` file:
 
 ```bash
-setup auth login
-setup auth set-key github
-setup auth list
-setup auth test
-setup auth use openai/gpt-4.1-mini
+setupr auth login
+setupr auth set-key github
+setupr auth list
+setupr auth test
+setupr auth use openai/gpt-4.1-mini
 ```
 
 Keys are stored at `~/.setupr/secrets.json` with file permissions `0600`, and Setupr only displays masked values.
@@ -33,15 +33,15 @@ For GitHub Models, use a token that can read GitHub Models. Fine-grained PATs or
 Setupr resolves provider keys in this order:
 
 1. Shell environment variables
-2. Global auth storage from `setup auth set-key`
+2. Global auth storage from `setupr auth set-key`
 3. Local `.env.local`
 4. Local `.env`
-5. Saved model preference from `setup auth use` (for model selection only)
+5. Saved model preference from `setupr auth use` (for model selection only)
 
 To migrate old provider keys out of a project `.env`:
 
 ```bash
-setup auth migrate
+setupr auth migrate
 ```
 
 Project `.env`, `.env.local`, and `.env.example` should primarily describe the app being set up, such as `DATABASE_URL`, `PORT`, or `NEXT_PUBLIC_API_URL`.
@@ -55,7 +55,7 @@ Project `.env`, `.env.local`, and `.env.example` should primarily describe the a
 
 If several provider keys are set, the selected model is deterministic:
 
-1. `P_SETUP_AI_MODEL` or `setup auth use ...` wins.
+1. `P_SETUP_AI_MODEL` or `setupr auth use ...` wins.
 2. Otherwise Setupr picks the cheapest configured model from its known local pricing table.
 3. GitHub Models catalog pricing is treated as unknown, so GitHub is picked automatically only if explicitly selected or if it is the only configured provider.
 4. The setup pre-warning and TUI timeline show which model the AI director is using.
@@ -74,31 +74,31 @@ Setupr detects required environment variables by:
 
 ```bash
 # Open the interactive .env editor TUI
-setup env
+setupr env
 
 # Create .env from .env.example
-setup env init
+setupr env init
 
 # Recreate .env from .env.example even if .env already exists.
 # If no .env.example exists, --force creates an empty .env with a warning.
-setup env init --force
+setupr env init --force
 
 # Check for missing variables
-setup env check
+setupr env check
 
 # Sync .env structure with .env.example (preserves values)
-setup env sync
+setupr env sync
 
 # Smart analysis: detect issues + interactive fix
-setup env smart
+setupr env smart
 ```
 
 ### `env` Editor Behavior
 
-- `setup env` opens a TUI editor for the local `.env`
+- `setupr env` opens a TUI editor for the local `.env`
 - if `.env` is missing but `.env.example` exists, Setupr asks before creating `.env` from the template
 - if both `.env` and `.env.example` are missing, Setupr returns `ENV_TEMPLATE_MISSING`
-- `setup env --force` creates an empty `.env` when no template exists and explains that no variables were inferred
+- `setupr env --force` creates an empty `.env` when no template exists and explains that no variables were inferred
 - the editor accepts normal value edits and pasted `KEY=value` lines
 - sensitive keys such as API keys, tokens, secrets, and passwords are masked in the editor input
 
@@ -113,11 +113,11 @@ setup env smart
 
 ### Safety Defaults
 
-- `setup env init` never overwrites an existing `.env` unless you pass `--force`
-- `setup env init` does not create `.env` when `.env.example` is missing unless you pass `--force`; without force it returns `ENV_TEMPLATE_MISSING`
+- `setupr env init` never overwrites an existing `.env` unless you pass `--force`
+- `setupr env init` does not create `.env` when `.env.example` is missing unless you pass `--force`; without force it returns `ENV_TEMPLATE_MISSING`
 - with `--force`, a missing `.env.example` creates an empty `.env` and reports that no variables were inferred
-- `setup` creates a missing `.env` from `.env.example` during the environment step
-- `setup env check` exits non-zero when required variables are missing
+- `setupr setup` creates a missing `.env` from `.env.example` during the environment step
+- `setupr env check` exits non-zero when required variables are missing
 - Plain-mode setup stops and exits non-zero if install, env setup, build, or verification fails
 
 ### Validation Rules

README.md

@@ -143,41 +143,41 @@ GitHub Models tokens need GitHub Models access; fine-grained PATs or app tokens
 
 ```bash
 # Guided setup for provider API keys
-setup auth login
+setupr auth login
 
 # Save one provider API key globally
-setup auth set-key github
+setupr auth set-key github
 
 # View configured providers without printing raw keys
-setup auth list
+setupr auth list
 
 # Test configured providers with tiny requests
-setup auth test
+setupr auth test
 
 # View available models
-setup auth models
+setupr auth models
 
 # Set preferred model
-setup auth use openai/gpt-4.1-mini
+setupr auth use openai/gpt-4.1-mini
 ```
 
-Setupr stores provider API keys globally in `~/.setupr/secrets.json` with file permissions `0600`. Raw keys are never printed; `setup auth list` and `setup auth status` show only masked keys.
+Setupr stores provider API keys globally in `~/.setupr/secrets.json` with file permissions `0600`. Raw keys are never printed; `setupr auth list` and `setupr auth status` show only masked keys.
 
-`setup auth test` runs configured providers concurrently with short per-provider timeouts. A slow or unavailable provider reports a classified timeout/error without blocking checks for the other configured providers.
+`setupr auth test` runs configured providers concurrently with short per-provider timeouts. A slow or unavailable provider reports a classified timeout/error without blocking checks for the other configured providers.
 
 Setupr resolves provider keys in this order:
 
 1. Shell environment variables, useful for CI or temporary overrides
-2. Global Setupr auth storage from `setup auth set-key`
+2. Global Setupr auth storage from `setupr auth set-key`
 3. Project `.env.local` / `.env` for backward compatibility only
 
 The project `.env` file is for the app being set up, not for Setupr's own API keys. To migrate old project-local provider keys into global auth:
 
 ```bash
-setup auth migrate
+setupr auth migrate
 ```
 
-When multiple provider keys are present, `P_SETUP_AI_MODEL` or `setup auth use <model>` wins. If no model is pinned, Setupr chooses the cheapest configured model from its known local pricing table and shows that choice in the pre-execution warning. GitHub Models catalog/custom pricing is treated as unknown, so GitHub is used automatically only when it is explicitly selected or it is the only configured provider.
+When multiple provider keys are present, `P_SETUP_AI_MODEL` or `setupr auth use <model>` wins. If no model is pinned, Setupr chooses the cheapest configured model from its known local pricing table and shows that choice in the pre-execution warning. GitHub Models catalog/custom pricing is treated as unknown, so GitHub is used automatically only when it is explicitly selected or it is the only configured provider.
 
 Setupr still accepts `export KEY=value` syntax in project env files for project variables and backward-compatible provider overrides.
 
@@ -241,8 +241,8 @@ Every command uses the same error format in plain mode and TUI mode:
 
 Examples:
 
-- `setup env init` stops if `.env.example` is missing, because Setupr cannot infer required variables. `setup env init --force` creates an empty `.env` and explains that no variables were inferred.
-- `setup auth list` stops on a corrupt `~/.setupr/secrets.json` instead of pretending keys are missing, so existing secrets are not accidentally overwritten.
+- `setupr env init` stops if `.env.example` is missing, because Setupr cannot infer required variables. `setupr env init --force` creates an empty `.env` and explains that no variables were inferred.
+- `setupr auth list` stops on a corrupt `~/.setupr/secrets.json` instead of pretending keys are missing, so existing secrets are not accidentally overwritten.
 - command failures are classified as install, build, test, network, permission, timeout, or missing-tool errors when possible.
 - `--force` skips ordinary prompts, but it does not ignore failed commands, invalid auth storage, missing secrets, or destructive blockers.
 
@@ -313,26 +313,26 @@ All command-like actions from setup, doctor, start, plugins, and AI steering pas
 
 ```bash
 # Open the interactive .env editor TUI
-setup env
+setupr env
 
 # Create .env from .env.example
-setup env init
+setupr env init
 
 # Overwrite an existing .env from .env.example, or create an empty .env
 # when no .env.example exists
-setup env init --force
+setupr env init --force
 
 # Check for missing variables
-setup env check
+setupr env check
 
 # Sync structure with .env.example
-setup env sync
+setupr env sync
 
 # Smart reorganize + auto-fill
-setup env smart
+setupr env smart
 ```
 
-Bare `setup env` opens the env editor. If `.env` exists, it opens directly. If only `.env.example` exists, Setupr asks before creating `.env` from the template. If neither file exists, it stops with `ENV_TEMPLATE_MISSING`; `setup env --force` creates an empty `.env` and explains that no variables were inferred.
+Bare `setupr env` opens the env editor. If `.env` exists, it opens directly. If only `.env.example` exists, Setupr asks before creating `.env` from the template. If neither file exists, it stops with `ENV_TEMPLATE_MISSING`; `setupr env --force` creates an empty `.env` and explains that no variables were inferred.
 
 ### Checkpoint & Resume
 
@@ -346,11 +346,11 @@ Bare `setup env` opens the env editor. If `.env` exists, it opens directly. If o
 ### Project Memory
 
 ```bash
-setup notes add "Use pnpm for installs"
-setup notes list
-setup history 10
-setup context export team-context.json
-setup context import team-context.json
+setupr notes add "Use pnpm for installs"
+setupr notes list
+setupr history 10
+setupr context export team-context.json
+setupr context import team-context.json
 ```
 
 Notes are saved in `.setupr/notes.json`. History uses `.setupr/history.jsonl`, and context export/import moves a deterministic bundle of notes plus history for team handoff.
@@ -428,15 +428,15 @@ Global config stored at `~/.setupr/config.json`:
 }
 ```
 
-Provider API keys are stored separately at `~/.setupr/secrets.json` and should be managed with `setup auth`.
+Provider API keys are stored separately at `~/.setupr/secrets.json` and should be managed with `setupr auth`.
 
 ### Help
 
 ```bash
-setup help
-setup help auth
-setup auth --help
-setup help auth set-key
+setupr help
+setupr help auth
+setupr auth --help
+setupr help auth set-key
 ```
 
 Global help lists every command. Command help shows subcommands, variations, options, and examples for that command.

SETUP.md

@@ -26,20 +26,20 @@ After installation, the `setup` command is available globally:
 
 ```bash
 setup
-setup doctor
-setup info
+setupr doctor
+setupr info
 ```
 
 ### Command Discovery
 
 Use the built-in help tree when you are not sure which workflow to run:
 
 ```bash
-setup help
-setup help chat
-setup help git
-setup help docker
-setup workspace --help
+setupr help
+setupr help chat
+setupr help git
+setupr help docker
+setupr workspace --help
 ```
 
 The rich help output lists the primary project-control surface, including setup, chat, auth, env, git, CI, Docker, secrets, templates, workspace, health, test, security, fix, release, perf, GitHub, registry, share, plugin, lint, and format commands. Advanced inspection/file-generation commands remain directly runnable for compatibility, but they are not advertised in the primary command index.
@@ -76,21 +76,21 @@ You can steer the agent from the persistent input at the bottom of the TUI. For
 To enable AI-powered features, save at least one provider key in global Setupr auth storage:
 
 ```bash
-setup auth login
-# Or: setup auth set-key github
+setupr auth login
+# Or: setupr auth set-key github
 ```
 
 Project `.env` files are for the app being set up, not Setupr's own API keys. For model preference:
 
 ```bash
-setup auth use kimi-k2-turbo-preview
+setupr auth use kimi-k2-turbo-preview
 # Or temporarily: P_SETUP_AI_MODEL=openai/gpt-4.1 setup
 ```
 
 Supported model IDs are listed with:
 
 ```bash
-setup auth models
+setupr auth models
 ```
 
 Without an API key, Setupr works fully — it just uses pattern matching and heuristics instead of AI for step planning and chat responses.
@@ -162,7 +162,7 @@ setupr perf scan --json
 For non-interactive environments:
 
 ```bash
-setup --force --plain
+setupr --force --plain
 ```
 
 This skips safe prompts and outputs plain text (no TUI). Setupr still avoids inventing secrets and should stop for destructive or blocked actions.
@@ -173,15 +173,15 @@ If any setup step fails in plain mode, Setupr stops immediately and returns a no
 
 ```bash
 # Remove dependency/cache artifacts
-setup clean --deps
+setupr clean --deps
 
 # Remove local-only files before sharing a project
-setup clean --share
+setupr clean --share
 
 # Remove dependencies, build output, caches, and local env files
-setup clean --all
+setupr clean --all
 ```
 
-The positional forms also work: `setup clean deps`, `setup clean share`, and `setup clean all`.
+The positional forms also work: `setupr clean deps`, `setupr clean share`, and `setupr clean all`.
 
-In TUI mode, `setup clean` opens a safety review before deleting anything. Review the target list, protected-file notes, and risk summary, then type `CLEAN` to confirm. `--force` skips the review prompt and starts cleaning after the target scan, while still reporting exactly what was removed or failed.
+In TUI mode, `setupr clean` opens a safety review before deleting anything. Review the target list, protected-file notes, and risk summary, then type `CLEAN` to confirm. `--force` skips the review prompt and starts cleaning after the target scan, while still reporting exactly what was removed or failed.