@viberaven/cli 1.3.1 → 1.3.5

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 (4) hide show
  1. package/README.md +109 -128
  2. package/dist/cli.js +3057 -336
  3. package/dist/cli.js.map +2 -2
  4. package/package.json +2 -2
package/README.md CHANGED
@@ -1,128 +1,109 @@
1
- # @viberaven/cli
2
-
3
- [![npm version](https://img.shields.io/npm/v/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
4
- [![npm downloads](https://img.shields.io/npm/dw/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
5
- [![license](https://img.shields.io/npm/l/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
6
-
7
- VibeRaven is the Agent Context + Production Gate for AI-built apps. It gives Claude Code, Codex, Cursor, and other coding agents a production-readiness loop before Vercel/Supabase deployment.
8
-
9
- ## Humans
10
-
11
- ```bash
12
- npx -y viberaven
13
- ```
14
-
15
- No subcommand is needed in a real terminal. It opens the interactive menu for sign-in, scan, report, provider guides, dashboards, prompts, and sign-out.
16
-
17
- ## Coding Agents
18
-
19
- Agents should run:
20
-
21
- ```bash
22
- npx -y viberaven --agent-mode
23
- ```
24
-
25
- If running from the `viberaven` monorepo root, run:
26
-
27
- ```bash
28
- node packages/cli/dist/cli.js --agent-mode
29
- ```
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
-
39
- Fix one repo-code gap, then run:
40
-
41
- ```bash
42
- npx -y viberaven --verify
43
- npx -y viberaven --strict
44
- ```
45
-
46
- For focused work:
47
-
48
- ```bash
49
- npx -y viberaven next --json
50
- npx -y viberaven prompt --gap <id>
51
- npx -y viberaven audit --vercel-supabase
52
- ```
53
-
54
- ## Chat-native production actions
55
-
56
- Agent mode writes a compact action surface for Codex, Claude Code, Cursor, and other agents:
57
-
58
- ```bash
59
- npx -y viberaven --agent-mode
60
- npx -y viberaven actions
61
- npx -y viberaven verify --action VR-A1
62
- ```
63
-
64
- VibeRaven writes `.viberaven/actions.json` as the V1 source of truth and renderer contract for the current action surface. The manifest is generated by `--agent-mode`; `.viberaven/action-registry.json` preserves stable action handles across runs.
65
-
66
- Chat output is intentionally limited to focused actions, provider targets, copy payloads, verification commands, repo-relative file targets, and resume prompts. It does not print secrets, raw env values, or generic dashboard link dumps.
67
-
68
- 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.
69
-
70
- Preview the action surface without login, scan, or API spend:
71
-
72
- ```bash
73
- npx -y viberaven preview --agent-mode
74
- ```
75
-
76
- The preview uses sample renderer data to show the intended chat-native shape. It is not a production verdict for the current repository.
77
-
78
- ## Agent infrastructure direction
79
-
80
- VibeRaven's action model is designed for normal Codex, Claude Code, Cursor, and MCP workflows today, and for richer agent hosts later.
81
-
82
- Managed-agent systems need durable sessions, observable event history, credential boundaries, bounded execution, and resumable action state. VibeRaven keeps those concerns in the manifest contract:
83
-
84
- - `.viberaven/actions.json` is the current action surface.
85
- - `.viberaven/action-registry.json` preserves stable IDs and lifecycle history.
86
- - Future session events can add an append-only timeline without changing the current action model.
87
- - Provider credentials and raw env values must stay out of chat output, manifests, MCP resources, and UI renderers.
88
- - Future local/hosted consoles should execute only narrow VibeRaven commands, not arbitrary shell text.
89
-
90
- ## Production Copilot Loop
91
-
92
- VibeRaven runs a batch-disciplined loop until the production gate clears. Do not stop at "scan complete."
93
-
94
- 1. **Scan** — Run `--agent-mode`. Read `.viberaven/agent-tasklist.md` and parse `VIBERAVEN_NEXT_ACTION` from stdout for `batchSize`, `batchApplied`, `scanNow`, and `stalled`.
95
- 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.
96
- 3. **Verify and clear** — Run `--verify` once per batch (not after every heal). Repeat until `gate.status === 'clear'` in `.viberaven/gate-result.json`. For provider gaps, read `VIBERAVEN_PROVIDER_ACTION`, complete the dashboard step, then verify.
97
-
98
- If `stalled: true`, stop calling verify and address provider-action gaps or report to the user. Run `--strict` before deploy or CI pass.
99
-
100
- ## Machine Output
101
-
102
- ```bash
103
- npx -y viberaven --agent-mode --json
104
- npx -y viberaven --agent-mode --jsonl
105
- npx -y viberaven --strict --json
106
- ```
107
-
108
- Machine artifact contract:
109
-
110
- ```text
111
- docs/contracts/artifacts.md
112
- https://viberaven.dev/schemas/gate-result.schema.json
113
- https://viberaven.dev/schemas/context-map.schema.json
114
- https://viberaven.dev/schemas/gap.schema.json
115
- https://viberaven.dev/schemas/heal-result.schema.json
116
- ```
117
-
118
- ## Development
119
-
120
- ```bash
121
- npm run cli:build
122
- npm run cli:test
123
- node packages/cli/dist/cli.js scan
124
- ```
125
-
126
- ## License
127
-
128
- The public npm CLI package is MIT licensed. Private monorepo code and extension packaging may have separate product terms.
1
+ # @viberaven/cli
2
+
3
+ [![npm version](https://img.shields.io/npm/v/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
4
+ [![npm downloads](https://img.shields.io/npm/dw/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
5
+ [![license](https://img.shields.io/npm/l/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
6
+
7
+ VibeRaven is the local Studio cockpit for AI-built apps. It gives Codex, Claude Code, Gemini CLI, Cursor, and other coding agents a clean production workspace for chat, provider context, MCP-assisted setup, release/version review, diffs, and approval-controlled repo work.
8
+
9
+ ## Start the Studio
10
+
11
+ ```bash
12
+ npx -y viberaven
13
+ ```
14
+
15
+ That command opens the local Studio UI for:
16
+
17
+ - agentic chat with connected CLIs;
18
+ - draggable provider and release context;
19
+ - provider MCP visibility;
20
+ - architecture map, terminal, and diff views;
21
+ - approval modes for ask, approve, and full-access work.
22
+
23
+ The unscoped `viberaven` package is a small shim that launches this CLI package.
24
+
25
+ ## Agent Connections
26
+
27
+ Inside the Studio, connect an installed CLI and test it before chat control:
28
+
29
+ - Codex CLI
30
+ - Claude Code
31
+ - Gemini CLI
32
+
33
+ Installed is not the same as connected. VibeRaven asks the selected CLI to prove it can run in the current repo before using it for real chat work.
34
+
35
+ ## Provider And Release Context
36
+
37
+ Use the Studio side tabs and context chips to attach provider or version context to a chat mission:
38
+
39
+ - Providers: Supabase, Vercel, GitHub, Stripe, Sentry, PostHog, Clerk, Auth.js, Resend, Upstash.
40
+ - Releases: current and recent git tags, changelog snippets, rollback context, and release comparisons.
41
+ - Architecture: repo and provider boundaries for inspection and planning.
42
+
43
+ Provider dashboard checks are not cleared by repo-code edits. Billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must still be completed or verified in the provider dashboard or through read-only provider evidence.
44
+
45
+ ## Machine And CI Commands
46
+
47
+ The Studio is the default product surface. These commands remain available for automation and CI:
48
+
49
+ ```bash
50
+ npx -y viberaven check --json
51
+ npx -y viberaven --strict --json
52
+ npx -y viberaven actions
53
+ npx -y viberaven verify --action VR-A1
54
+ ```
55
+
56
+ For focused work:
57
+
58
+ ```bash
59
+ npx -y viberaven next --json
60
+ npx -y viberaven prompt --gap <id>
61
+ npx -y viberaven audit --vercel-supabase
62
+ ```
63
+
64
+ ## Legacy Agent Mode
65
+
66
+ `--agent-mode` is kept for older artifact-first agent workflows:
67
+
68
+ ```bash
69
+ npx -y viberaven --agent-mode
70
+ ```
71
+
72
+ It writes artifacts such as:
73
+
74
+ - `.viberaven/agent-tasklist.md`
75
+ - `.viberaven/gate-result.json`
76
+ - `.viberaven/context-map.json`
77
+ - `.viberaven/agent-summary.md`
78
+ - `.viberaven/launch-playbook.md`
79
+
80
+ New product work should prefer the Studio and MCP/chat context flow instead of the old tasklist-first loop.
81
+
82
+ ## MCP
83
+
84
+ Use the MCP package when an agent host supports MCP tools:
85
+
86
+ ```bash
87
+ npx -y @viberaven/mcp
88
+ ```
89
+
90
+ The MCP server wraps the public CLI and exposes readiness, verification, action, audit, and healing tools without exposing secrets.
91
+
92
+ ## Development
93
+
94
+ ```bash
95
+ npm --prefix packages/cli run typecheck
96
+ npm --prefix packages/cli test -- local-ui/server.test.ts
97
+ npm --prefix packages/cli run build
98
+ ```
99
+
100
+ For a local package publish check, run from this package directory:
101
+
102
+ ```bash
103
+ cd packages/cli
104
+ npm pack --dry-run
105
+ ```
106
+
107
+ ## License
108
+
109
+ MIT