immune-brain 4.0.0 → 4.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "immune-brain",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "Immune-Brain agent skill system",
   "publishConfig": {
     "access": "public",

package/plugins/immune-brain/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "immune-brain",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "Immune-Brain Claude Code Host: native Enrollment, QA, Review, and Kernel settlement.",
   "author": {
     "name": "Immune-Brain Team"

package/plugins/immune-brain/dist/claude/mcp-server.mjs

@@ -39,7 +39,7 @@ function probeHost(env = process.env, platform = process.platform, hostVersion)
 }
 
 // plugins/immune-brain/runtime/plugin_version.ts
-var PLUGIN_VERSION = "4.0.0";
+var PLUGIN_VERSION = "4.0.1";
 
 // plugins/immune-brain/runtime/claude/interaction.ts
 import { createHash, randomUUID } from "node:crypto";

package/plugins/immune-brain/dist/imm-loop.md

@@ -71,7 +71,13 @@ Continue while the current projection has a valid action:
    Normal completion does not require a second user confirmation.
 5. For rework, follow the projected artifact state before editing. Resolve
    findings only after fixing and verifying their cause. Changed snapshots
-   invalidate old evidence; run the newly required obligations.
+   invalidate old evidence; run the newly required obligations. On the second
+   rework of one acceptance id or anchor, the fix response must either state why
+   it covers every known trigger class of the violated invariant — the shared
+   guard, not only the reported path — or declare the trigger outside the
+   accepted contract and answer with `refute_finding` bound to fresh QA evidence
+   for that acceptance. Escalating a local heuristic a third time instead of
+   choosing one of those two responses is the loop this step exists to break.
 6. An unresolved decision pauses only dependent execution. On `awaiting_user`,
    invoke `request_authorization` directly before ending the turn; use the
    Decisions and Recovery route for its native-gate handling. End the turn if

package/plugins/immune-brain/dist/imm-planner.md

@@ -133,6 +133,13 @@ file creation; then it validates the created artifact with
 continue through Kernel `revise_intent` authority and are not a Planner
 overwrite path.
 
+Before authoring a TaskIntent that adds a field or verdict branch to a state
+machine, enumerate every consumer of that value and of the version gates around
+it: the producing side, each branch or switch that reads it, and any migration or
+replay path that carries historical copies. Name all of them in `scope_hint`. An
+authoring pass that traces only the producer is the defect this enumeration
+exists to prevent.
+
 ### Initiative Carrier Preference
 
 For a large proposal split across multiple TaskIntents, exactly one planning

package/plugins/immune-brain/dist/role-prompts/code-review.md

@@ -26,6 +26,14 @@ material task-local maintenance risks. Pure naming, length, complexity
 thresholds, formatting, and design preference are not findings and must not
 cause style-only rework.
 
+When a finding repeats an acceptance id or anchor that already produced rework in
+this task, do not file it as a fresh single-trigger defect. Name the invariant
+class it belongs to and state in `evidence.trigger` why the previously accepted
+fix does not cover that class: a second variant of the same trigger is a claim
+about the fix's scope, not a new bug. A trigger the accepted contract explicitly
+excludes is reported as an advisory note against that boundary, never as blocking
+rework.
+
 Return exactly one JSON object with the fields required by the Loop review
 contract: `contract`, `role`, `task_id`, `snapshot_digest`, `decision` (`pass`
 or `rework`), and for `pass` include `approval` (`kind`, `authority_role`,

package/plugins/immune-brain/runtime/plugin_version.ts

@@ -1,2 +1,2 @@
 // Generated by scripts/plugin_versioning.ts from the root package.json.
-export const PLUGIN_VERSION = "4.0.0" as const;
+export const PLUGIN_VERSION = "4.0.1" as const;

package/plugins/immune-brain/runtime/prompts/code-review.md

@@ -26,6 +26,14 @@ material task-local maintenance risks. Pure naming, length, complexity
 thresholds, formatting, and design preference are not findings and must not
 cause style-only rework.
 
+When a finding repeats an acceptance id or anchor that already produced rework in
+this task, do not file it as a fresh single-trigger defect. Name the invariant
+class it belongs to and state in `evidence.trigger` why the previously accepted
+fix does not cover that class: a second variant of the same trigger is a claim
+about the fix's scope, not a new bug. A trigger the accepted contract explicitly
+excludes is reported as an advisory note against that boundary, never as blocking
+rework.
+
 Return exactly one JSON object with the fields required by the Loop review
 contract: `contract`, `role`, `task_id`, `snapshot_digest`, `decision` (`pass`
 or `rework`), and for `pass` include `approval` (`kind`, `authority_role`,