intentdna 1.6.0 → 1.6.1

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "intentdna",
       "description": "Declarative policy layer for AI agent behavior with plugin-managed hook runtime for Claude Code.",
-      "version": "1.6.0",
+      "version": "1.6.1",
       "author": {
         "name": "Samuel"
       },
@@ -25,5 +25,5 @@
       ]
     }
   ],
-  "version": "1.6.0"
+  "version": "1.6.1"
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "intentdna",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "Declarative policy layer for AI agent behavior",
   "author": {
     "name": "Samuel"

package/dist/templates/flutter-rewrite.dna.yaml

@@ -134,6 +134,7 @@ context_files:
       - ".dna/specs/diagnosis-{{ARGUMENTS}}.md"
     surgeon:
       - ".dna/specs/diagnosis-{{ARGUMENTS}}.md"
+      - ".dna/specs/diagnosis-{{ARGUMENTS}}.review.json"
     fix_reviewer:
       - "docs/behavior/{{ARGUMENTS}}.md"
       - ".dna/specs/diagnosis-{{ARGUMENTS}}.md"
@@ -465,13 +466,20 @@ workflows:
         prompt: |
           This invocation is one fix round.
 
-          Before editing, check whether .dna/fix-progress/$ARGUMENTS.md exists.
-          - If it exists, read it before the diagnosis spec and continue from its Next Round Focus.
-          - If it records REQUEST_CHANGES or BLOCKED_BY_REVIEW, address those review issues before starting unrelated diagnosis items.
-          - Use Failed approaches / Do not repeat to avoid repeating unsuccessful fixes.
-          - If it does not exist, treat this as round 1.
+          Before editing, read .dna/specs/diagnosis-$ARGUMENTS.review.json.
+          - If it is missing, invalid, or verdict is not APPROVE, stop immediately; do not edit.
+          - Manual fix invocations must obey this same gate.
+          - If verdict is REQUEST_REANALYSIS, run diagnosis reanalysis first instead of fixing.
 
-          Read context + diagnosis spec first.
+          Read context + diagnosis spec only after the diagnosis review gate passes.
+
+          Progress artifacts:
+          - .dna/fix-progress/$ARGUMENTS.json is the machine-readable source of truth for controller scheduling.
+          - If JSON exists and provenance matches this module, use its next_round_focus/verdict for the current round.
+          - .dna/fix-progress/$ARGUMENTS.md is human-readable legacy/manual context only; read it for Failed approaches / Do not repeat and evidence, but never use it as the controller verdict or source of truth.
+          - If .md exists without .json, treat it as legacy context only; do not infer PASS/CONTINUE/BLOCKED from it.
+          - If progress records REQUEST_CHANGES or BLOCKED_BY_REVIEW, address those review issues before starting unrelated diagnosis items.
+          - If neither progress artifact exists, treat this as round 1.
 
           Count diagnosis classifications before editing. If UNIMPLEMENTED count is greater than 100, this round is implementation-first: fix UNIMPLEMENTED items by priority only, and leave TEST_BUG / BUG / INFRA / REMOVED for later rounds unless they block implementation.
 
@@ -493,6 +501,9 @@ workflows:
             - type: file
               path: ".dna/specs/diagnosis-$ARGUMENTS.md"
               description: "Diagnosis spec"
+            - type: file
+              path: ".dna/specs/diagnosis-$ARGUMENTS.review.json"
+              description: "Approved diagnosis review gate"
           produces:
             - type: git_commit
               description: "Fix commit"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "intentdna",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "Intent DNA — Declarative policy layer for AI agent behavior",
   "type": "module",
   "main": "dist/index.js",