@viberaven/cli 1.5.0 → 1.5.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.
- package/AGENTS.md +157 -157
- package/LICENSE +21 -21
- package/README.md +113 -113
- package/SECURITY.md +59 -59
- package/dist/cli.js +2475 -476
- package/dist/console/app.js +251 -251
- package/dist/console/index.html +46 -46
- package/dist/console/styles.css +267 -267
- package/dist/playbooks/_stack-default.json +11 -11
- package/dist/playbooks/auth-supabase.json +31 -31
- package/dist/playbooks/stripe.json +66 -66
- package/dist/playbooks/supabase.json +51 -51
- package/dist/playbooks/vercel.json +42 -42
- package/dist/report/assets/provider-authjs.svg +5 -5
- package/dist/report/assets/provider-aws.svg +5 -5
- package/dist/report/assets/provider-logrocket.svg +4 -4
- package/dist/report/report-cli.css +1466 -1466
- package/dist/report/station.css +11854 -11854
- package/dist/report/station.js +8319 -8319
- package/dist/stack/app.js +16 -11
- package/dist/stack/stack.css +854 -442
- package/dist/vendor/anime.umd.min.js +7 -7
- package/package.json +12 -2
- package/playbooks/_stack-default.json +11 -11
- package/playbooks/auth-supabase.json +31 -31
- package/playbooks/stripe.json +66 -66
- package/playbooks/supabase.json +51 -51
- package/playbooks/vercel.json +42 -42
- package/schemas/permissions-matrix.schema.json +90 -0
- package/templates/AGENTS.snippet.md +52 -52
- package/templates/CLAUDE.snippet.md +17 -17
- package/templates/CURSOR.snippet.md +17 -17
|
@@ -1,17 +1,17 @@
|
|
|
1
|
-
<!-- viberaven:agent-rules:start -->
|
|
2
|
-
## VibeRaven Agent Rules
|
|
3
|
-
|
|
4
|
-
VibeRaven is the Agent Context + Production Gate.
|
|
5
|
-
|
|
6
|
-
- 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.
|
|
7
|
-
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
|
-
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
|
-
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
-
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
-
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
-
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
-
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
|
-
- 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.
|
|
15
|
-
- 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.
|
|
16
|
-
<!-- viberaven:agent-rules:end -->
|
|
17
|
-
|
|
1
|
+
<!-- viberaven:agent-rules:start -->
|
|
2
|
+
## VibeRaven Agent Rules
|
|
3
|
+
|
|
4
|
+
VibeRaven is the Agent Context + Production Gate.
|
|
5
|
+
|
|
6
|
+
- 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.
|
|
7
|
+
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
|
+
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
|
+
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
+
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
+
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
+
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
+
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
|
+
- 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.
|
|
15
|
+
- 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.
|
|
16
|
+
<!-- viberaven:agent-rules:end -->
|
|
17
|
+
|
|
@@ -1,17 +1,17 @@
|
|
|
1
|
-
<!-- viberaven:agent-rules:start -->
|
|
2
|
-
## VibeRaven Agent Rules
|
|
3
|
-
|
|
4
|
-
VibeRaven is the Agent Context + Production Gate.
|
|
5
|
-
|
|
6
|
-
- 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.
|
|
7
|
-
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
|
-
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
|
-
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
-
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
-
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
-
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
-
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
|
-
- 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.
|
|
15
|
-
- 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.
|
|
16
|
-
<!-- viberaven:agent-rules:end -->
|
|
17
|
-
|
|
1
|
+
<!-- viberaven:agent-rules:start -->
|
|
2
|
+
## VibeRaven Agent Rules
|
|
3
|
+
|
|
4
|
+
VibeRaven is the Agent Context + Production Gate.
|
|
5
|
+
|
|
6
|
+
- 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.
|
|
7
|
+
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
|
+
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
|
+
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
+
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
+
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
+
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
+
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
|
+
- 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.
|
|
15
|
+
- 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.
|
|
16
|
+
<!-- viberaven:agent-rules:end -->
|
|
17
|
+
|