@viberaven/cli 0.1.0-beta.0

package/AGENTS.md

@@ -0,0 +1,37 @@
+# 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.
+
+## Run (user does not need to type this — you run it)
+
+```bash
+npx -y @viberaven/cli@beta scan --open
+```
+
+If not signed in:
+
+```bash
+npx -y @viberaven/cli@beta login
+```
+
+Then scan again.
+
+## 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 (opened with `--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.

package/README.md

@@ -0,0 +1,70 @@
+# @viberaven/cli
+
+Launch readiness for Claude Code, Codex, and other coding agents — same mission map and provider intelligence as VibeRaven Station.
+
+## For humans
+
+```bash
+npx -y @viberaven/cli@beta login
+npx -y @viberaven/cli@beta scan --open
+```
+
+Uses the **same VibeRaven account and scan quota** as the VS Code extension.
+
+Opens `.viberaven/report.html` with an interactive provider map and copy-ready agent prompts.
+
+## For coding agents
+
+See [AGENTS.md](./AGENTS.md). Typical loop:
+
+```bash
+npx -y @viberaven/cli@beta scan --open
+# read .viberaven/agent-summary.md
+npx -y @viberaven/cli@beta prompt
+# implement, then scan again
+```
+
+## Artifacts
+
+| File | Purpose |
+|------|---------|
+| `.viberaven/last-scan.json` | Full scan payload |
+| `.viberaven/agent-summary.md` | Short briefing for agents |
+| `.viberaven/report.html` | Visual mission map (Phase A) |
+
+## 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
+```
+
+You can also set it directly:
+
+```bash
+viberaven stack set auth clerk   # persists to .viberaven/stack.json
+viberaven stack list
+viberaven stack clear            # remove all overrides
+```
+
+The next `scan` re-maps that area using your chosen provider.
+
+## Development
+
+From repo root:
+
+```bash
+npm run cli:build
+npm run cli:test
+node packages/cli/dist/cli.js scan
+```
+
+Inside `packages/cli`:
+
+```bash
+npm run typecheck     # tsc against the shared station engine
+npm run demo-report   # render a sample report.html and open it
+```
+
+The report reuses the Station Mission Map visual language (`src/report/reportStyles.ts`) for parity with the extension.