@viberaven/cli 0.1.0-beta.4 → 0.1.0-beta.7

package/AGENTS.md

@@ -36,43 +36,21 @@ 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
-```
+If not signed in, `scan` starts VibeRaven sign-in, opens the browser approval page when possible, waits for the user to approve the editor/agent connection, then continues the 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.
+If the local agent environment cannot open a browser, show the printed `Open:` URL to the user. After approval, rerun `npx -y @viberaven/cli@beta scan`.
 
+Manual fallback if the scan flow cannot start login:
 
+```bash
+npx -y @viberaven/cli@beta login
+```
 
-## Read
+Agents should use `scan` without `--open`; open the report only when the user wants the browser map.
+
+
+
+## Read
 
 
 

package/README.md

@@ -4,41 +4,43 @@ Launch readiness for Claude Code, Codex, and other coding agents — same missio
 
 ## For humans
 
+```bash
+npx -y @viberaven/cli@beta login
+npx -y @viberaven/cli@beta scan --open
+```
+
+Sign in once, then scan with `--open` to view `.viberaven/report.html` in the browser (same editorial Mission Map skin as the extension). Or run **`viberaven`** with no args for the interactive terminal menu.
+
+Uses the **same VibeRaven account and scan quota** as the VS Code extension. **Does not use your `OPENAI_API_KEY`** — scans go through the managed API after login. See [SECURITY.md](./SECURITY.md).
+
+## For coding agents
+
+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 scan
+```
+
+If login is missing, `scan` starts VibeRaven sign-in, opens the browser approval page when possible, waits for the user to approve the connection, then continues the scan.
+
+If the local agent environment cannot open a browser, show the printed `Open:` URL to the user. After they approve it, rerun:
+
 ```bash
-npx -y @viberaven/cli@beta
+npx -y @viberaven/cli@beta scan
 ```
 
-Use the menu to sign in, sign out, scan, open `.viberaven/report.html`, copy the top prompt, and rescan. Direct commands also work:
+Manual fallback:
 
 ```bash
 npx -y @viberaven/cli@beta login
-npx -y @viberaven/cli@beta logout
-npx -y @viberaven/cli@beta status
-npx -y @viberaven/cli@beta scan --open
 ```
-
-Uses the **same VibeRaven account and scan quota** as the VS Code extension. **Does not use your `OPENAI_API_KEY`** — scans go through the managed API after login. See [SECURITY.md](./SECURITY.md).
-
-Quota:
-
-- Free: 2 lifetime scans
-- Pro: 50 scans per month
 
-## For coding agents
-
-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 scan
-```
-
-If output includes `LOGIN_REQUIRED`, ask the user to run:
+Read `.viberaven/agent-summary.md` and `.viberaven/launch-playbook.md`. Loop:
 
-```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.
+1. `viberaven next --json`
+2. Repo fix → `viberaven prompt --gap <id>` → implement → `viberaven report` (free) or `scan`
+3. Provider → `viberaven guide <provider>` and `viberaven open <provider>`
+4. Repeat until done; check `viberaven status --json` before each new scan
 
 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.
 
@@ -49,14 +51,13 @@ See [AGENTS.md](./AGENTS.md). Paste [templates/AGENTS.snippet.md](./templates/AG
 | File | Purpose |
 |------|---------|
 | `.viberaven/last-scan.json` | Full scan payload |
-| `.viberaven/agent-summary.md` | Short briefing for agents |
+| `.viberaven/agent-summary.md` | Short briefing + next action for agents |
+| `.viberaven/launch-playbook.md` | Ordered launch checklist |
 | `.viberaven/report.html` | Visual mission map + `report/station.css` (extension editorial UI) |
 
-## 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:
+## 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:
 
 ```bash
 viberaven stack set database neon && viberaven scan --open
@@ -70,9 +71,7 @@ viberaven stack list
 viberaven stack clear            # remove all overrides
 ```
 
-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`.
+The next `scan` re-maps that area using your chosen provider.
 
 ## Development