@viberaven/cli 1.0.6 → 1.1.0
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/README.md +18 -28
- package/dist/cli.js +312 -515
- package/dist/cli.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -28,16 +28,13 @@ If running from the `viberaven` monorepo root, run:
|
|
|
28
28
|
node packages/cli/dist/cli.js --agent-mode
|
|
29
29
|
```
|
|
30
30
|
|
|
31
|
-
Then read artifacts in this order:
|
|
32
|
-
|
|
33
|
-
1. `.viberaven/agent-tasklist.md`
|
|
34
|
-
2. `.viberaven/gate-result.json`
|
|
35
|
-
3. `.viberaven/context-map.json`
|
|
36
|
-
4. `.viberaven/agent-summary.md`
|
|
37
|
-
5. `.viberaven/launch-playbook.md`
|
|
38
|
-
6. `.viberaven/launch-plan.json`
|
|
39
|
-
7. `.viberaven/launch-tasklist.md`
|
|
40
|
-
8. `.viberaven/provider-actions.json`
|
|
31
|
+
Then read artifacts in this order:
|
|
32
|
+
|
|
33
|
+
1. `.viberaven/agent-tasklist.md`
|
|
34
|
+
2. `.viberaven/gate-result.json`
|
|
35
|
+
3. `.viberaven/context-map.json`
|
|
36
|
+
4. `.viberaven/agent-summary.md`
|
|
37
|
+
5. `.viberaven/launch-playbook.md`
|
|
41
38
|
|
|
42
39
|
Fix one repo-code gap, then run:
|
|
43
40
|
|
|
@@ -56,34 +53,27 @@ npx -y viberaven audit --vercel-supabase
|
|
|
56
53
|
|
|
57
54
|
Provider dashboard checks are not cleared by repo-code edits. Billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard or through read-only provider evidence.
|
|
58
55
|
|
|
59
|
-
##
|
|
56
|
+
## VibeRaven Production Protocol
|
|
57
|
+
|
|
58
|
+
VibeRaven 1.1.0 introduces the Production Protocol for AI-built apps.
|
|
60
59
|
|
|
61
|
-
|
|
60
|
+
Run the canonical agent command:
|
|
62
61
|
|
|
63
62
|
```bash
|
|
64
63
|
npx -y viberaven --agent-mode
|
|
65
64
|
```
|
|
66
65
|
|
|
67
|
-
|
|
66
|
+
Then have the AI coding agent read:
|
|
68
67
|
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
4. Guide Vercel preview deploy before production promotion.
|
|
73
|
-
5. Guide Supabase, Stripe, analytics, and monitoring setup through MCP/plugin/CLI/dashboard/manual fallback actions.
|
|
74
|
-
6. Require approval before provider writes, database migrations, secret writes, preview deploys, and production deploys.
|
|
68
|
+
- `.viberaven/prp.json`
|
|
69
|
+
- `.viberaven/mission-map.md`
|
|
70
|
+
- `.viberaven/context-map.json`
|
|
75
71
|
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
```bash
|
|
79
|
-
npx -y viberaven --agent-mode --launch-mode ask
|
|
80
|
-
```
|
|
81
|
-
|
|
82
|
-
Modes: `manual`, `ask`, `safe`, `full`. The default is `ask`.
|
|
72
|
+
The agent should fix `nextActions` in order and must not claim production-ready while `decision.status` is `blocked`.
|
|
83
73
|
|
|
84
74
|
## Production Copilot Loop
|
|
85
|
-
|
|
86
|
-
VibeRaven runs a batch-disciplined loop until the production gate clears. Do not stop at "scan complete."
|
|
75
|
+
|
|
76
|
+
VibeRaven runs a batch-disciplined loop until the production gate clears. Do not stop at "scan complete."
|
|
87
77
|
|
|
88
78
|
1. **Scan** — Run `--agent-mode`. Read `.viberaven/agent-tasklist.md` and parse `VIBERAVEN_NEXT_ACTION` from stdout for `batchSize`, `batchApplied`, `scanNow`, and `stalled`.
|
|
89
79
|
2. **Batch heals** — For each repo-code task where `requiresUserAction: false`, apply up to `batchSize` heals per batch (free=3, pro=10) via `viberaven_heal_apply { gap: "<gapId>", yes: true }` or `--heal --apply --gap <id> --yes`. When `scanNow: true`, verify before applying more heals.
|