@pablozrrrr/jevguard 0.2.0 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pablozrrrr/jevguard",
-  "version": "0.2.0",
+  "version": "0.2.3",
   "description": "OpenCode plugin that reviews a completed agent turn against a repository semantic rule using Jev.",
   "license": "MIT",
   "type": "module",

package/skills/jev-init/SKILL.md

@@ -101,8 +101,14 @@ A single README sentence, an isolated code sample, personal preference, or an
 aspiration the repository does not already follow is **not** strong evidence. Exclude
 speculative rules and say which candidates you dropped and why.
 
-Each rule block keeps the document grammar; `severity` and `scope` remain the only
-accepted metadata. Provenance is **never** written inside a rule block.
+Each rule block keeps the document grammar. The accepted metadata is `severity`,
+repeatable `scope` (a leading `!` excludes), and optional `evidence` (`code`, the
+default, `docs`, or `any`). Provenance is **never** written inside a rule block.
+
+Prefer a bounded `scope:` over a repository-wide rule: a convention that only holds under
+particular paths must say so, or it will fire where it does not apply. Add
+`evidence: docs` or `evidence: any` only when the rule genuinely inspects documentation,
+because the default `code` class excludes prose.
 
 ### 5. Write the provenance preamble before the rules
 
@@ -165,11 +171,12 @@ remediation:
   auto_propose: true
   propose_on:
     - FAIL
-  model: opencode/gpt-5.6-luna
 ```
 
-Do not invent thresholds, add keys, or change the model. The default configuration is
-valid and uses the documented defaults.
+Do not invent thresholds or add keys. The default configuration is valid and uses the
+documented defaults. Never pin `remediation.model`: when it is absent the proposer
+inherits the host model, which is the only portable choice. A hard-coded provider
+model can be absent on the user's machine and would make every proposal fail.
 
 ### 7. Preview both files and require explicit confirmation