@viberaven/cli 1.0.0 → 1.0.1

package/AGENTS.md

@@ -40,6 +40,39 @@ For Vercel + Supabase checks:
 npx -y @viberaven/cli audit --vercel-supabase
 ```
 
+## Production Copilot Loop
+
+After every scan, read `.viberaven/agent-tasklist.md` for the prioritized task list.
+
+The loop is:
+
+1. Read `VIBERAVEN_NEXT_ACTION` from scan output for `batchSize`, `batchApplied`, `scanNow`, and `stalled`.
+2. If `stalled: true`, stop calling verify — address provider-action gaps or report to the user.
+3. If `scanNow: true`, call `viberaven_verify` (or run `--verify`) before applying more heals.
+4. For each repo-code task where `requiresUserAction: false` (up to `batchSize` per batch):
+   - Call MCP: `viberaven_heal_apply { gap: "<gapId>", yes: true }`
+   - Or run `--heal --apply --gap <id> --yes`
+5. After a full batch of heals, call verify once — do NOT verify after every single heal.
+6. Repeat until `gate.status === 'clear'` in `.viberaven/gate-result.json`.
+7. If `requiresUserAction: true`:
+   - Read `VIBERAVEN_PROVIDER_ACTION` from terminal output.
+   - Present `dashboardUrl` and `exactStep` to the user.
+   - Wait for user confirmation, then verify.
+8. If `fixType === 'upgrade-required'`, provide `upgradeUrl` and move on.
+
+Do not stop at "scan complete." The loop is not done until `gate.status === 'clear'`.
+
+### Batch discipline
+
+```
+for each repo-code task (up to batchSize):
+  viberaven_heal_apply { gap: "<gapId>", yes: true }
+
+viberaven_verify  ← once per batch, not per fix
+```
+
+On Pro plans, `viberaven_provider_verify` is available as an MCP tool for read-only provider gap verification via Supabase/Vercel MCP evidence.
+
 ## Rules
 
 - Do not skip VibeRaven before deploy/build/cleanup when production readiness is in scope.

package/README.md

@@ -43,6 +43,16 @@ npx -y @viberaven/cli audit --vercel-supabase
 
 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.
 
+## Production Copilot Loop
+
+VibeRaven runs a batch-disciplined loop until the production gate clears. Do not stop at "scan complete."
+
+1. **Scan** — Run `--agent-mode`. Read `.viberaven/agent-tasklist.md` and parse `VIBERAVEN_NEXT_ACTION` from stdout for `batchSize`, `batchApplied`, `scanNow`, and `stalled`.
+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.
+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.
+
+If `stalled: true`, stop calling verify and address provider-action gaps or report to the user. Run `--strict` before deploy or CI pass.
+
 ## Machine Output
 
 ```bash

package/assets/report/station.js

@@ -7274,9 +7274,9 @@ function buildAgentPromptText(payload, nextMove, missing, files) {
 
 function buildChecklistText(payload, nextMove, missing, files) {
   const lines = [
-    '# Station production checklist',
+    '# VibeRaven production checklist',
     '',
-    'Generated from the latest VibeRaven Station run.',
+    'Generated from the latest VibeRaven run.',
     '',
     '## Next move',
     '',