@viberaven/cli 0.1.0-beta.1 → 0.1.0-beta.2

package/AGENTS.md

@@ -1,46 +1,114 @@
-# VibeRaven CLI — agent instructions
-
-Use this when the user asks whether their app is **production-ready**, **launch-ready**, what they are **missing before ship**, or how to improve **auth / database / payments / deployment** on an AI-built project.
-
-## Humans (interactive menu)
-
-```bash
-npx -y @viberaven/cli@beta
-# or: viberaven tui
-```
-
-No subcommand needed — opens an interactive menu for scan, gaps, prompts, and sign-in.
-
-## Run (agents — you run this, not the user)
-
-```bash
-npx -y @viberaven/cli@beta scan
-```
-
-If not signed in:
-
-```bash
-npx -y @viberaven/cli@beta login
-```
-
-Then scan again. Agents should use `scan` without `--open`; open the report only when the user wants the browser map.
-
-## Read
-
-1. `.viberaven/agent-summary.md` — short briefing and top gaps
-2. `.viberaven/last-scan.json` — full mission map, providers, checks
-3. `.viberaven/report.html` — visual map for the user (human menu or `--open`)
-
-## Fix loop
-
-1. `npx -y @viberaven/cli@beta prompt` — stdout = copy-ready prompt for the top gap  
-   Or: `viberaven prompt --gap <id>` / `--area database` / `--provider supabase`
-2. Implement the change in the repo.
-3. `npx -y @viberaven/cli@beta scan` — verify production core % and gap count improved.
-4. Tell the user to review `.viberaven/report.html` for the provider map.
-
-## Rules
-
-- Do not skip the scan — VibeRaven uses repo evidence plus managed analysis, not generic checklists.
-- Prefer fixing **critical** gaps first unless the user names an area.
-- Do not claim external dashboard setup is done unless checks pass or the user confirmed manually.
+# VibeRaven CLI — agent instructions
+
+
+
+Use this when the user asks whether their app is **production-ready**, **launch-ready**, what they are **missing before ship**, or how to improve **auth / database / payments / deployment** on an AI-built project.
+
+
+
+## Humans (interactive menu)
+
+
+
+```bash
+
+npx -y @viberaven/cli@beta
+
+# or: viberaven tui
+
+```
+
+
+
+No subcommand needed — opens an interactive menu for scan, gaps, prompts, and sign-in.
+
+
+
+## Run (agents — you run this, not the user)
+
+
+
+```bash
+
+npx -y @viberaven/cli@beta scan
+
+```
+
+
+
+If not signed in:
+
+
+
+```bash
+
+npx -y @viberaven/cli@beta login
+
+```
+
+
+
+Then scan again. Agents should use `scan` without `--open`; open the report only when the user wants the browser map.
+
+If scan output says `LOGIN_REQUIRED`, stop and ask the user to complete:
+
+```bash
+npx -y @viberaven/cli@beta login
+```
+
+Then rerun:
+
+```bash
+npx -y @viberaven/cli@beta scan
+```
+
+Stable agent-readable labels:
+
+- `READY` — scan finished; read `.viberaven/agent-summary.md` before changing code.
+- `LOGIN_REQUIRED` — stop and ask the user to complete login.
+- `UPGRADE_REQUIRED` — stop; the user must upgrade or wait for quota reset.
+- `MANUAL_ACTION_REQUIRED` — provider dashboard, billing, DNS, webhook, MCP, or live verification needs user/provider action.
+- `ERROR` — report the error and retry only when the cause is clear.
+
+
+
+## Read
+
+
+
+1. `.viberaven/agent-summary.md` — short briefing and top gaps
+
+2. `.viberaven/last-scan.json` — full mission map, providers, checks
+
+3. `.viberaven/report.html` — visual map for the user (human menu or `--open`)
+
+
+
+## Fix loop
+
+
+
+1. `npx -y @viberaven/cli@beta prompt` — stdout = copy-ready prompt for the top gap  
+
+   Or: `viberaven prompt --gap <id>` / `--area database` / `--provider supabase`
+
+2. Implement the change in the repo.
+
+3. `npx -y @viberaven/cli@beta scan` — verify production core % and gap count improved.
+
+4. Tell the user to review `.viberaven/report.html` for the provider map.
+
+
+
+## Rules
+
+
+
+- Do not skip the scan — VibeRaven uses repo evidence plus managed analysis, not generic checklists.
+
+- Prefer fixing **critical** gaps first unless the user names an area.
+
+- Do not claim external dashboard setup is done unless checks pass or the user confirmed manually.
+
+- Do not claim human-provider actions as repo-code fixes. Human-provider actions include dashboard setup, billing/product configuration, DNS, webhooks, provider credentials, quota upgrades, and read-only MCP/provider-live verification.
+

package/README.md

@@ -15,16 +15,24 @@ Uses the **same VibeRaven account and scan quota** as the VS Code extension. **D
 
 ## For coding agents
 
-See [AGENTS.md](./AGENTS.md). Paste [templates/AGENTS.snippet.md](./templates/AGENTS.snippet.md) into your repo's `AGENTS.md`. Typical loop:
+Use VibeRaven when the user asks whether an AI-built app is launch-ready, production-ready, or missing auth/database/payments/deployment/security work.
 
 ```bash
-npx -y @viberaven/cli@beta login   # once
-npx -y @viberaven/cli@beta scan    # no --open needed for agents
-# read .viberaven/agent-summary.md
-npx -y @viberaven/cli@beta prompt
-# implement, then scan again
+npx -y @viberaven/cli@beta scan
 ```
 
+If output includes `LOGIN_REQUIRED`, ask the user to run:
+
+```bash
+npx -y @viberaven/cli@beta login
+```
+
+After the browser/device login completes, run scan again. Then read `.viberaven/agent-summary.md`, run `viberaven prompt` or `viberaven prompt --gap <id>`, implement the repo-code fix, and run `npx -y @viberaven/cli@beta scan` again.
+
+Do not claim dashboard, billing, DNS, webhook, MCP, or provider-live actions as repo-code fixes. Tell the user when `.viberaven/report.html` has manual provider actions to review.
+
+See [AGENTS.md](./AGENTS.md). Paste [templates/AGENTS.snippet.md](./templates/AGENTS.snippet.md) into your repo's `AGENTS.md`.
+
 ## Artifacts
 
 | File | Purpose |
@@ -33,9 +41,11 @@ npx -y @viberaven/cli@beta prompt
 | `.viberaven/agent-summary.md` | Short briefing for agents |
 | `.viberaven/report.html` | Visual mission map + `report/station.css` (extension editorial UI) |
 
-## Switch providers (matches the extension map)
-
-The report shows a provider switch per production area (database, auth, payments, deployment, monitoring, security). Picking one copies a command:
+## Switch providers (matches the extension map)
+
+The report shows provider paths per production area. Clicking a provider in `.viberaven/report.html` updates the static map view for review; it does not silently persist or claim that provider is connected.
+
+To persist a provider choice for the next scan, use:
 
 ```bash
 viberaven stack set database neon && viberaven scan --open
@@ -49,7 +59,9 @@ viberaven stack list
 viberaven stack clear            # remove all overrides
 ```
 
-The next `scan` re-maps that area using your chosen provider.
+The next `scan` re-maps that area using your chosen provider.
+
+Agent-readable scan labels are stable: `READY`, `LOGIN_REQUIRED`, `UPGRADE_REQUIRED`, `MANUAL_ACTION_REQUIRED`, and `ERROR`.
 
 ## Development