intentdna 1.6.0 → 1.6.2

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.2",
       "author": {
         "name": "Samuel"
       },
@@ -25,5 +25,5 @@
       ]
     }
   ],
-  "version": "1.6.0"
+  "version": "1.6.2"
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "intentdna",
-  "version": "1.6.0",
+  "version": "1.6.2",
   "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"
@@ -518,6 +529,9 @@ workflows:
             "module": "$ARGUMENTS",
             "round": 1,
             "run_id": "controller run id or manual-run",
+            "actionability": "none | actionable | needs_human | unsafe | unclear",
+            "scope": "none | in_diagnosis | outside_diagnosis | unclear",
+            "risk": "none | low | medium | high",
             "issues": ["specific issue with evidence path; empty when approved"],
             "evidence_paths": ["paths that justify the verdict"],
             "failure_reason": "why changes need another round; empty when approved",
@@ -533,9 +547,11 @@ workflows:
           - module is required and must equal $ARGUMENTS.
           - round is required and must be the provided current_round, or 1 for manual fix invocation.
           - run_id is required and must equal the provided controller_run_id, or "manual-run" for manual fix invocation.
-          - updated_at is a required ISO timestamp string.
-
-          REQUEST_CHANGES → include failure_reason and concrete next_round_focus for the next fix invocation. The next_round_focus must name the priority/classification and specific test file or evidence path to address first.
+          - actionability, scope, risk, and updated_at are required.
+          - APPROVE → actionability/scope/risk should be none, issues empty, failure_reason empty, next_round_focus empty.
+          - REQUEST_CHANGES can continue automatically only when actionability is actionable, scope is in_diagnosis, risk is low or medium, and next_round_focus is concrete.
+          - REQUEST_CHANGES must stop when actionability is needs_human/unsafe/unclear, scope is outside_diagnosis/unclear, risk is high, or next_round_focus is empty.
+          - REQUEST_CHANGES → include failure_reason and concrete next_round_focus for the next fix invocation. The next_round_focus must name the priority/classification and specific test file or evidence path to address first.
         handoff:
           consumes:
             - type: git_commit
@@ -559,7 +575,9 @@ workflows:
         prompt: |
           Read the review verdict and diagnosis spec first.
 
-          If the review verdict is REQUEST_CHANGES, set Verdict: BLOCKED, set Failure reason: BLOCKED_BY_REVIEW plus reviewer details, and do not claim verification.
+          If the review verdict is REQUEST_CHANGES:
+          - If actionability is actionable, scope is in_diagnosis, risk is low or medium, and next_round_focus is concrete, set Verdict: CONTINUE and do not run tests; copy reviewer next_round_focus into Next Round Focus.
+          - Otherwise set Verdict: BLOCKED, set Failure reason: BLOCKED_BY_REVIEW plus reviewer details, and do not run tests.
 
           If the review verdict is APPROVE:
           - Run full module test suite for $ARGUMENTS.
@@ -576,7 +594,8 @@ workflows:
           - Before writing Module complete: yes, read diagnosis classification summary, read current test summary, compare skipped tests against remaining UNIMPLEMENTED diagnosis items, and if any UNIMPLEMENTED skipped remains, Module complete must be no.
 
           Verdict mapping:
-          - review REQUEST_CHANGES -> Verdict: BLOCKED, Failure reason: BLOCKED_BY_REVIEW.
+          - review REQUEST_CHANGES + actionable + in_diagnosis + risk low/medium + concrete next_round_focus -> Verdict: CONTINUE, Module complete: no, Next Round Focus: reviewer next_round_focus.
+          - review REQUEST_CHANGES without safe actionable scope -> Verdict: BLOCKED, Failure reason: BLOCKED_BY_REVIEW.
           - 0 failed + remaining UNIMPLEMENTED skipped > 0 -> Verdict: CONTINUE, Module complete: no, Next Round Focus: next diagnosis-backed UNIMPLEMENTED test/evidence path.
           - progress contradicts diagnosis/test evidence -> Verdict: BLOCKED, Failure reason: PROGRESS_DIAGNOSIS_CONFLICT.
           - new red caused by current round -> Verdict: REQUEST_CHANGES.
@@ -612,6 +631,9 @@ workflows:
             "module": "$ARGUMENTS",
             "round": 1,
             "run_id": "controller run id or manual-run",
+            "actionability": "none | actionable | needs_human | unsafe | unclear",
+            "scope": "none | in_diagnosis | outside_diagnosis | unclear",
+            "risk": "none | low | medium | high",
             "diagnosis_artifact": ".dna/specs/diagnosis-$ARGUMENTS.md",
             "review_artifact": ".dna/reviews/$ARGUMENTS-review.json",
             "git_head": null,
@@ -638,10 +660,11 @@ workflows:
           - git_head is the current git HEAD after verification if available, otherwise null.
           - verdict is required and must be PASS, CONTINUE, REQUEST_CHANGES, or BLOCKED.
           - review is required and must be APPROVE or REQUEST_CHANGES.
+          - actionability, scope, and risk are required and must mirror the review verdict when review is REQUEST_CHANGES; use none/none/none when review is APPROVE.
           - module_complete is a required boolean and must match the Markdown Module complete value.
           - fixed_count, new_red_count, blocked_count, remaining_count, and remaining_unimplemented_skipped_count are required non-negative integers.
           - next_round_focus is required and non-empty when verdict is CONTINUE or REQUEST_CHANGES; empty string is allowed when verdict is PASS.
-          - failure_reason is required and non-empty when verdict is BLOCKED or REQUEST_CHANGES; empty string is allowed when verdict is PASS or CONTINUE.
+          - failure_reason is required and non-empty when verdict is BLOCKED or REQUEST_CHANGES; empty string is allowed when verdict is PASS or CONTINUE. When review REQUEST_CHANGES is normalized to verdict CONTINUE, keep reviewer failure details in Review Issues To Address First instead of failure_reason.
           - last_fix_commit is the commit hash string if available, otherwise null.
           - evidence_paths is a required array of command/test/diagnosis/review evidence paths.
           - updated_at is a required ISO timestamp string.
@@ -650,9 +673,9 @@ workflows:
 
           Verdict meanings:
           - PASS: all actionable BUG / UNIMPLEMENTED items are fixed, with no diagnosis-backed UNIMPLEMENTED skipped tests remaining; only TEST_BUG / INFRA / REMOVED / explicitly user-approved blocked items may remain
-          - CONTINUE: this round made progress and remaining approved items should continue in the next fix invocation
+          - CONTINUE: this round made progress or review found safe, actionable, in-diagnosis issues that should continue in the next fix invocation
           - REQUEST_CHANGES: verification found issues in this round's changes
-          - BLOCKED: review blocks verification, user confirmation is needed, evidence conflicts, or repeated no-progress prevents safe continuation
+          - BLOCKED: review blocks verification, user confirmation is needed, evidence conflicts, unsafe/out-of-scope changes, or repeated no-progress prevents safe continuation
         handoff:
           consumes:
             - type: file

package/package.json

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