@su-record/vibe 4.1.7 → 4.1.9

package/skills/{vibe.prove → vibe-prove}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: vibe.prove
+name: vibe-prove
 description: Prove — run every scenario and regression at once with `vibe check --all` to reach DONE. On STUCK, stop and ask.
 user-invocable: false
 ---
@@ -10,9 +10,9 @@ user-invocable: false
 
 1. Run `vibe check --all --json`. Every scenario plus every registered regression runs — independent ones in parallel, dependents after their parents pass.
 2. Show the user a table: scenario · check type · pass/fail/blocked/pending · time. `human` items read "confirmation requested" with the inbox id; `blocked` items name the parent.
-3. On failures go back to `vibe.build`. On STUCK (`stuck: true`) do not fix — show the inbox question to the user and wait.
+3. On failures go back to `vibe-build`. On STUCK (`stuck: true`) do not fix — show the inbox question to the user and wait.
 4. Surface first (at most 3, each with a reason): scenarios that never ran, checks that flip between pass and fail (evidence history), runs that hit a limit (`tail` contains "killed").
-5. When `done: true`, move to `vibe.handoff`.
+5. When `done: true`, move to `vibe-handoff`.
 
 ## What DONE means
 

package/skills/{vibe.scope → vibe-scope}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: vibe.scope
+name: vibe-scope
 description: Scope — write the intent and scenarios (each bound to a check), get one human token in one approval message. Make sure the tools needed for building are in place before building.
 user-invocable: false
 ---
@@ -9,7 +9,8 @@ user-invocable: false
 ## Procedure
 
 1. Turn the discovery result into scenarios. A scenario is stored only if it carries exactly one check type:
-   - `run` command exit code · `file` exists/regex/contains/schema/sum (a column total equals a reference) · `http` status/schema/maxMs · `eval` count of matching labelled cases (jsonl `{input, expected}` through a runner's stdin/stdout, `expect.pass` is a count) · `human` no verdict (goes to the inbox)
+   - `run` command exit code · `file` exists/regex/contains/schema/sum (a column total equals a reference) · `http` status/schema/maxMs · `eval` count of matching labelled cases (jsonl `{input, expected}` through a runner's stdin/stdout, `expect.pass` is a count) · `review` a language pack's copy editor then chief editor, run by the harness, exact `PASS` only · `human` no verdict (goes to the inbox)
+   - When a success condition is human-read text (blog, column, article, report, script, speech), propose `check: { type: review, path: <file>, contract: <file>, evidence: <file> }` and mark it `⚠ model-judged` in the approval message.
    - A condition you cannot check gets `human` explicitly. An irreversible action (push, deploy, send, delete, spend) gets `irreversible: <action>`.
    - A scenario that only makes sense after another one has passed gets `needs: [ids]`. The harness orders and parallelises checks from these edges; keep a connected graph under six scenarios.
 2. Check for missing scenario kinds yourself: the failure path, rollback, permission boundaries. Add them or say in one line why they are not needed. When the intent writes code, propose a size gate: `check: { type: run, cmd: "vibe size src --max-file 400 --max-function 50" }`.
@@ -31,7 +32,7 @@ To proceed, {paste {token} | say yes}.
 ```
 
 6. When the user pastes the number (or says yes when no token was issued), run `vibe approve "{number}" --json` (or `vibe approve --json`). On `code 3` show the reason and ask again. On a change request go back to step 3.
-7. When the state is APPROVED and any accepted skill is installed, move to `vibe.build`.
+7. When the state is APPROVED and any accepted skill is installed, move to `vibe-build`.
 
 ## Never