@su-record/vibe 4.1.18 → 4.1.20

package/hooks/notify.js

@@ -1,9 +1,10 @@
 #!/usr/bin/env node
 /**
- * Notification hook — it never judges. Always exits 0.
+ * Notification hook — it never judges the work; it gates one thing: an irreversible command without a token.
  *
  *   post  PostToolUse(Edit|Write): runs `vibe state --json` and tells the model about a voided DONE or open inbox items.
- *   pre   PreToolUse(Bash): warns on stderr when an irreversible command has no recent authorize record.
+ *   pre   PreToolUse(Bash): an irreversible command with no recent authorize record is blocked (exit 2) under the
+ *         strict and irreversible token policies, and only warned about under off.
  *         PreToolUse(Read): when the file is over READ_ADVISE_LINES, tells the model that `vibe read <file> --ask`
  *         lets a low-reasoning model read it — advice only, the read goes ahead.
  *
@@ -72,13 +73,16 @@ function recentAuthorize(action) {
 
 if (!fs.existsSync(path.join(root, '.vibe'))) process.exit(0);
 
-function tokensOff() {
+function tokenPolicy() {
   try {
-    return JSON.parse(fs.readFileSync(path.join(root, '.vibe', 'config.json'), 'utf-8')).tokens === 'off';
+    return JSON.parse(fs.readFileSync(path.join(root, '.vibe', 'config.json'), 'utf-8')).tokens || 'irreversible';
   } catch {
-    return false;
+    return 'irreversible';
   }
 }
+function tokensOff() {
+  return tokenPolicy() === 'off';
+}
 
 const READ_ADVISE_LINES = Number(process.env.VIBE_READ_ADVISE_LINES || 400);
 
@@ -96,7 +100,7 @@ function adviseRead(payload) {
   if (!file) return;
   const lines = countLines(path.resolve(root, file));
   if (lines <= READ_ADVISE_LINES) return;
-  const shown = path.isAbsolute(file) ? path.relative(root, file) || file : file;
+  const shown = (path.isAbsolute(file) ? path.relative(root, file) || file : file).split(path.sep).join('/');
   emitContext(`[vibe] ${shown} is ${lines} lines — when it only has to be understood, not edited or debugged, \`vibe read ${shown} --ask "<question>"\` lets a low-reasoning model read it and returns the answer with line numbers`);
 }
 
@@ -106,12 +110,13 @@ if (mode === 'pre') {
     adviseRead(payload);
     process.exit(0);
   }
-  if (tokensOff()) process.exit(0);
   const command = String((payload.tool_input && payload.tool_input.command) || '');
+  // Under strict and irreversible the gate blocks (exit 2 stops the tool call in Claude Code); under off it only warns.
   for (const [action, re] of IRREVERSIBLE) {
     if (re.test(command) && !recentAuthorize(action)) {
-      process.stderr.write(`[vibe] "${action}" is irreversible and no authorize record exists in the last 10 minutes — get a human token with \`vibe ask --needs authorize:${action}\` and run \`vibe authorize\` first\n`);
-      break;
+      const blocking = tokenPolicy() !== 'off';
+      process.stderr.write(`[vibe] "${action}" is irreversible and no authorize record exists in the last 10 minutes — ${blocking ? 'blocked: ' : ''}get a human token with \`vibe ask --needs authorize:${action}\` and run \`vibe authorize\` first\n`);
+      process.exit(blocking ? 2 : 0);
     }
   }
   process.exit(0);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@su-record/vibe",
-  "version": "4.1.18",
+  "version": "4.1.20",
   "description": "An AX/FDE harness for Claude Code, Codex CLI and ChatGPT desktop. Say what you need, approve the scenarios once; the harness proves the work by running the checks itself. Memory in plain files, human tokens for irreversible actions, a ledger instead of claims.",
   "type": "module",
   "bin": {

package/skills/vibe-build/SKILL.md

@@ -9,8 +9,8 @@ user-invocable: false
 ## Procedure
 
 1. Take scenarios in the order of `remaining` from `vibe state --json` — parents before their `needs` dependents (`vibe state --graph` shows the edges). Put scenarios marked `irreversible` last.
-   - Scenarios with no edge between them may be built by parallel agents, each in its own worktree, merged before `vibe check --all`. Never two agents in one working tree.
-2. Build only what that scenario needs — code, a script, a document, configuration, whatever. Make sure the check itself (`check.cmd`, `check.path`) can actually run.
+   - Scenarios with no edge between them may be built by parallel agents, each in its own worktree, merged before `vibe check --all`. Never two agents in one working tree. Batch scenarios of one shape into one dispatch; never a nested subagent (a reviewer's reviewer counts for nothing). Hand artifacts to an agent as files, never pasted. When the context is nearly full, start a new session from `.vibe/` instead of compacting.
+2. Read `vibe context {id}` first — the files and symbols the check touches, the decisions and regressions that touched them, the conventions — then build only what that scenario needs. Make sure the check itself (`check.cmd`, `check.path`) can actually run.
    - Orientation reads ("what does this module do", "where is X handled") go through `vibe read <files> --ask "<question>"` — a low-reasoning model reads and answers with line numbers; read the file yourself only to edit or debug it.
 3. Run `vibe check {id} --json`.
    - Pass (`code 0`): next scenario.

package/skills/vibe-discover/SKILL.md

@@ -8,6 +8,8 @@ user-invocable: false
 
 ## Procedure
 
+Order the questions by impact: scope first, then security and privacy, then the reader's or user's experience, then technical detail. A question further down the list is asked only when the earlier ones are settled.
+
 1. Read what the user attached through the harness, so every client sees the same thing:
    - table (csv · tsv · jsonl · json · xlsx) → `vibe profile {file} --json` [`--sheet`]: columns, types, missing counts, duplicates, up to three anomalies with numbers
    - document (xlsx · docx · pptx · pdf · hwp · hwpx · html) → `vibe read {file} --json` [`--sheet` · `--pages`]; it says which reader it used (pdf: `pdftotext` when installed, else built-in)

package/skills/vibe-prove/SKILL.md

@@ -17,3 +17,5 @@ user-invocable: false
 ## What DONE means
 
 DONE means every gate scenario passed on this exact tree. Changing any file sends the state back to RUNNING; run `vibe check --all` again.
+
+On STUCK, read `vibe context {id}` before touching anything — the decisions and regressions around that scenario are usually the reason.

package/skills/vibe-scope/SKILL.md

@@ -21,7 +21,7 @@ user-invocable: false
 3. Save with `vibe intent draft --stdin --json`, sending `{"intent": "...", "scenarios": "..."}` (both in English).
    - On rejection (`code 1`) fix the reasons and save again. Do not pass by deleting a rejected scenario — bind a check to it.
    - On success the response contains `token` when the project's token policy is `strict`; otherwise `token` is null and a plain yes in chat is enough.
-4. Research and proposals, once, before the approval message: `vibe research --from-intent --json` (up to five candidates with an action each, what moved in the last 30 days first — `--days N` for another window; skip silently on exit 2 and say "no network") and `vibe skill suggest --json` (up to three). Show both in the approval message. Do not install anything — the user says "add 1" and you run the printed `vibe skill add …` (preview first, `--yes` after they have seen the commands).
+4. Run `vibe intent analyze` and resolve every `uncovered` bullet (add a scenario or cut the bullet) before asking; an `unrequested` scenario is cut or the bullet is written. Then research and proposals, once, before the approval message: `vibe research --from-intent --json` (up to five candidates with an action each, what moved in the last 30 days first — `--days N` for another window; skip silently on exit 2 and say "no network") and `vibe skill suggest --json` (up to three). Show both in the approval message. Do not install anything — the user says "add 1" and you run the printed `vibe skill add …` (preview first, `--yes` after they have seen the commands). `vibe status` lists the tools vibe would use if present; when the project would use one (a large repository → a symbol graph; a design review → a screenshot tool) put its one-line install in the approval message. A project-local skill is kept only if removing a line of it would make the model err.
 5. Send **one** approval message:
 
 ```