@viberaven/cli 1.6.12 → 1.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (36) hide show
  1. package/AGENTS.md +64 -64
  2. package/LICENSE +21 -21
  3. package/README.md +67 -67
  4. package/SECURITY.md +59 -59
  5. package/dist/cli.js +5025 -1958
  6. package/dist/console/app.js +251 -251
  7. package/dist/console/index.html +46 -46
  8. package/dist/console/styles.css +267 -267
  9. package/dist/github-ci.js +1645 -0
  10. package/dist/playbooks/_stack-default.json +11 -11
  11. package/dist/playbooks/auth-supabase.json +31 -31
  12. package/dist/playbooks/stripe.json +66 -66
  13. package/dist/playbooks/supabase.json +51 -51
  14. package/dist/playbooks/vercel.json +42 -42
  15. package/dist/report/assets/provider-authjs.svg +5 -5
  16. package/dist/report/assets/provider-aws.svg +5 -5
  17. package/dist/report/assets/provider-logrocket.svg +4 -4
  18. package/dist/report/report-cli.css +1466 -1466
  19. package/dist/report/station.css +11854 -11854
  20. package/dist/report/station.js +8319 -8319
  21. package/dist/stack/app.js +14 -14
  22. package/dist/stack/scene.css +522 -484
  23. package/dist/stack/stack.css +1691 -1691
  24. package/dist/vendor/anime.umd.min.js +7 -7
  25. package/package.json +96 -95
  26. package/playbooks/_stack-default.json +11 -11
  27. package/playbooks/auth-supabase.json +31 -31
  28. package/playbooks/stripe.json +66 -66
  29. package/playbooks/supabase.json +51 -51
  30. package/playbooks/vercel.json +42 -42
  31. package/schemas/permissions-matrix.schema.json +90 -90
  32. package/schemas/verification-plan.schema.json +350 -0
  33. package/schemas/verification-report.schema.json +550 -0
  34. package/templates/AGENTS.snippet.md +56 -56
  35. package/templates/CLAUDE.snippet.md +14 -14
  36. package/templates/CURSOR.snippet.md +14 -14
package/templates/CURSOR.snippet.md CHANGED
@@ -1,14 +1,14 @@
1
- <!-- viberaven:agent-rules:start -->
2
- ## VibeRaven Agent Rules
3
-
4
- VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase. This is advice, not a gate: the user decides when to ship. It is a repository check, not a live database test, and a clear result is not a security audit.
5
-
6
- - Suggest one pass with `npx -y viberaven --agent-mode` from the project root before a Vercel + Supabase app launches or is handed off, after a Supabase migration or policy change, or when the user reports a production error about RLS, env vars, the database connection, the service role key or a Stripe webhook. It is not needed for apps that do not use Vercel and Supabase, for general SQL or deployment questions, or for one local error.
7
- - Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the verdict, and `.viberaven/context-map.json` for compact agent context.
8
- - Read `.viberaven/agent-summary.md` and `.viberaven/launch-playbook.md` before editing code for a listed gap.
9
- - Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
10
- - Run `npx -y viberaven --verify` once per batch of fixes, not after every edit.
11
- - For the Vercel + Supabase repo evidence, run `npx -y viberaven audit --vercel-supabase`.
12
- - `npx -y viberaven --strict` returns the verdict as an exit code for CI when the user wants one.
13
- - 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 happen in the provider dashboard.
14
- <!-- viberaven:agent-rules:end -->
1
+ <!-- viberaven:agent-rules:start -->
2
+ ## VibeRaven Agent Rules
3
+
4
+ VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase. This is advice, not a gate: the user decides when to ship. It is a repository check, not a live database test, and a clear result is not a security audit.
5
+
6
+ - Suggest one pass with `npx -y viberaven check` from the project root before a Vercel + Supabase app launches or is handed off, after a Supabase migration or policy change, or when the user reports a production error about RLS, env vars, the database connection, the service role key or a Stripe webhook. It is not needed for apps that do not use Vercel and Supabase, for general SQL or deployment questions, or for one local error.
7
+ - Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the verdict, and `.viberaven/context-map.json` for compact agent context.
8
+ - Read `.viberaven/agent-summary.md` and `.viberaven/launch-playbook.md` before editing code for a listed gap.
9
+ - Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
10
+ - Run `npx -y viberaven --verify` once per batch of fixes, not after every edit.
11
+ - For the Vercel + Supabase repo evidence, run `npx -y viberaven audit --vercel-supabase`.
12
+ - `npx -y viberaven --strict` returns the verdict as an exit code for CI when the user wants one.
13
+ - 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 happen in the provider dashboard.
14
+ <!-- viberaven:agent-rules:end -->