@viberaven/cli 1.0.2 → 1.0.4

package/package.json

@@ -1,72 +1,75 @@
-{
-  "name": "@viberaven/cli",
-  "version": "1.0.2",
-  "description": "Production-readiness scan for AI-built apps: auth, billing, database, deployment, monitoring, launch gaps, and agent-ready fixes.",
-  "license": "UNLICENSED",
-  "author": "VibeRaven",
-  "homepage": "https://viberaven.dev",
-  "bugs": {
-    "url": "https://github.com/ohad6k/VibeRaven/issues"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/ohad6k/VibeRaven.git",
-    "directory": "packages/cli"
-  },
-  "keywords": [
-    "viberaven",
-    "launch-readiness",
-    "production-readiness",
-    "launch-gaps",
-    "ai-built-apps",
-    "agent-mode",
-    "mcp",
-    "claude-code",
-    "codex",
-    "cursor",
-    "ai",
-    "production",
-    "supabase",
-    "vercel",
-    "stripe"
-  ],
-  "publishConfig": {
-    "access": "public",
-    "tag": "latest"
-  },
-  "bin": {
-    "viberaven": "dist/cli.js"
-  },
-  "files": [
-    "dist",
-    "playbooks",
-    "assets/report",
-    "AGENTS.md",
-    "SECURITY.md",
-    "templates"
-  ],
-  "scripts": {
-    "sync-report-assets": "node scripts/sync-report-assets.mjs",
-    "build": "node scripts/build.mjs",
-    "dev": "node scripts/build.mjs && node dist/cli.js",
-    "typecheck": "tsc -p tsconfig.json",
-    "demo-report": "node scripts/demo-report.mjs --open",
-    "verify:release:smoke": "npm run build && node scripts/verify-beta-flow.mjs --smoke",
-    "verify:release:live": "npm run build && node scripts/verify-beta-flow.mjs --live",
-    "test": "vitest run",
-    "prepublishOnly": "npm run sync-report-assets && npm run check:agent-discovery && npm run typecheck && npm run test && npm run build",
-    "check:agent-discovery": "node scripts/check-agent-discovery.mjs"
-  },
-  "engines": {
-    "node": ">=20"
-  },
-  "dependencies": {
-    "@clack/prompts": "^0.10.1",
-    "picocolors": "^1.1.1"
-  },
-  "devDependencies": {
-    "esbuild": "^0.25.0",
-    "typescript": "^5.8.0",
-    "vitest": "^3.2.0"
-  }
-}
+{
+  "name": "@viberaven/cli",
+  "version": "1.0.4",
+  "description": "Production-readiness scan for AI-built apps: auth, billing, database, deployment, monitoring, launch gaps, and agent-ready fixes.",
+  "license": "UNLICENSED",
+  "author": "VibeRaven",
+  "homepage": "https://viberaven.dev",
+  "bugs": {
+    "url": "https://github.com/ohad6k/VibeRaven/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/ohad6k/VibeRaven.git",
+    "directory": "packages/cli"
+  },
+  "keywords": [
+    "viberaven",
+    "launch-readiness",
+    "production-readiness",
+    "launch-gaps",
+    "ai-built-apps",
+    "agent-mode",
+    "mcp",
+    "claude-code",
+    "codex",
+    "cursor",
+    "ai",
+    "production",
+    "supabase",
+    "vercel",
+    "stripe"
+  ],
+  "publishConfig": {
+    "access": "public",
+    "tag": "latest"
+  },
+  "bin": {
+    "viberaven": "dist/cli.js"
+  },
+  "files": [
+    "dist",
+    "playbooks",
+    "assets/report",
+    "AGENTS.md",
+    "SECURITY.md",
+    "templates"
+  ],
+  "scripts": {
+    "sync-report-assets": "node scripts/sync-report-assets.mjs",
+    "build": "node scripts/build.mjs",
+    "dev": "node scripts/build.mjs && node dist/cli.js",
+    "typecheck": "tsc -p tsconfig.json",
+    "demo-report": "node scripts/demo-report.mjs --open",
+    "verify:release:smoke": "npm run build && node scripts/verify-beta-flow.mjs --smoke",
+    "verify:release:live": "npm run build && node scripts/verify-beta-flow.mjs --live",
+    "test": "vitest run",
+    "prepublishOnly": "npm run sync-report-assets && npm run check:agent-discovery && npm run typecheck && npm run test && npm run build",
+    "check:agent-discovery": "node scripts/check-agent-discovery.mjs",
+    "viberaven:gate": "npx -y viberaven --agent-mode",
+    "viberaven:verify": "npx -y viberaven --verify",
+    "viberaven:strict": "npx -y viberaven --strict"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "dependencies": {
+    "@clack/prompts": "^0.10.1",
+    "picocolors": "^1.1.1"
+  },
+  "devDependencies": {
+    "esbuild": "^0.25.0",
+    "typescript": "^5.8.0",
+    "vitest": "^3.2.0"
+  }
+}

package/templates/AGENTS.snippet.md

@@ -49,3 +49,4 @@ Free plan: 2 lifetime scans, 6/12 mission map lanes. Pro: 50 scans/month, all 12
 Same VibeRaven account and scan quota as the VS Code extension.
 
 Security: the CLI does not read `OPENAI_API_KEY`. Scans use VibeRaven login and the managed API; your model key stays server-side.
+

package/templates/CLAUDE.snippet.md

@@ -1,16 +1,17 @@
-<!-- viberaven:agent-rules:start -->
-## VibeRaven Agent Rules
-
-VibeRaven is the Agent Context + Production Gate.
-
-- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
-- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
-- Read `.viberaven/agent-summary.md` before editing code.
-- Read `.viberaven/launch-playbook.md` before editing code.
-- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
-- Run `npx -y viberaven --verify` after one fix.
-- Run `npx -y viberaven --strict` before deploy or CI pass.
-- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
-- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
-- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
-<!-- viberaven:agent-rules:end -->
+<!-- viberaven:agent-rules:start -->
+## VibeRaven Agent Rules
+
+VibeRaven is the Agent Context + Production Gate.
+
+- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
+- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
+- Read `.viberaven/agent-summary.md` before editing code.
+- Read `.viberaven/launch-playbook.md` before editing code.
+- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
+- Run `npx -y viberaven --verify` after one fix.
+- Run `npx -y viberaven --strict` before deploy or CI pass.
+- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
+- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
+- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
+<!-- viberaven:agent-rules:end -->
+

package/templates/CURSOR.snippet.md

@@ -1,16 +1,17 @@
-<!-- viberaven:agent-rules:start -->
-## VibeRaven Agent Rules
-
-VibeRaven is the Agent Context + Production Gate.
-
-- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
-- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
-- Read `.viberaven/agent-summary.md` before editing code.
-- Read `.viberaven/launch-playbook.md` before editing code.
-- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
-- Run `npx -y viberaven --verify` after one fix.
-- Run `npx -y viberaven --strict` before deploy or CI pass.
-- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
-- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
-- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
-<!-- viberaven:agent-rules:end -->
+<!-- viberaven:agent-rules:start -->
+## VibeRaven Agent Rules
+
+VibeRaven is the Agent Context + Production Gate.
+
+- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
+- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
+- Read `.viberaven/agent-summary.md` before editing code.
+- Read `.viberaven/launch-playbook.md` before editing code.
+- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
+- Run `npx -y viberaven --verify` after one fix.
+- Run `npx -y viberaven --strict` before deploy or CI pass.
+- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
+- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
+- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
+<!-- viberaven:agent-rules:end -->
+