intentdna 1.6.3 → 1.6.5

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

@@ -289,7 +289,7 @@ controllers:
   fix-loop:
     name: Fix Loop
     description: "Run diagnosis once if needed, then loop fix/review/verify until PASS or stop condition"
-    kind: flutter_rewrite_fix_loop
+    kind: fix_loop
     max_rounds: 10
     progress_artifact_path: ".dna/fix-progress/$ARGUMENTS.json"
     diagnosis_workflow: diagnosis
@@ -303,7 +303,47 @@ controllers:
       surgeon: surgeon
       fix_reviewer: fix_reviewer
       test_runner: test_runner
-    stop_format: zh_three_part
+    stop_format: configured_stop_report
+    policy:
+      diagnosis_reuse_criteria:
+        - "$diagnosis_artifact_path exists"
+        - "$diagnosis_review_artifact_path exists and verdict is APPROVE"
+        - "behavior doc is not newer than diagnosis spec"
+        - "baseline artifact is not newer than diagnosis spec"
+        - "user did not explicitly pass reanalyze or scope changed"
+        - "progress JSON does not say diagnosis_invalid"
+      progress_provenance_checks:
+        - "module equals the safe module argument"
+        - "round equals the provided current_round"
+        - "run_id equals the provided controller_run_id"
+        - "diagnosis_artifact equals $diagnosis_artifact_path"
+        - "review_artifact equals $review_artifact_path"
+        - "git_head or last_fix_commit references the current round's fix commit when available"
+        - "updated_at is not earlier than the current round start time"
+      progress_provenance_failure: "if provenance is missing, stale, or mismatched, stop with Verdict BLOCKED and failure_reason PROGRESS_PROVENANCE_MISMATCH"
+      verdict_branches:
+        - "PASS -> success stop"
+        - "CONTINUE -> next fresh context fix round"
+        - "REQUEST_CHANGES -> stop with the configured stop report"
+        - "BLOCKED -> stop with the configured stop report"
+      verdict_mapping:
+        - "PASS / CONTINUE / REQUEST_CHANGES / BLOCKED mapping:"
+        - "- PASS: success stop"
+        - "- CONTINUE: start the next fresh context round"
+        - "- REQUEST_CHANGES: stop, report reviewer/verifier requested changes"
+        - "- BLOCKED: stop, report blocker"
+        - "- MAX_ROUNDS: stop, report max rounds reached and next focus"
+      stop_report:
+        - "On REQUEST_CHANGES, BLOCKED, or MAX_ROUNDS, output exactly these Chinese sections:"
+        - "结论：state the direct stop trigger, current round, and current commit if one exists."
+        - "为什么停止：explain the workflow principle in plain language; if this is a current-round new red, explain that continuing would build on a bad baseline."
+        - "是否回滚：say whether rollback/revert is recommended. If the commit direction looks wrong or the blast radius is unclear, recommend revert; if the failure is narrow and fixable, recommend fix-forward."
+        - "下一步：give one concrete next action. If recommending fix-forward, include a copy-paste single-fix prompt with current commit, exact failure, allowed scope, forbidden actions, verification command, commit expectation, and stop conditions."
+      constraints:
+        - "Do not infer module completion from raw test output."
+        - "The controller must schedule only from $progress_artifact_path."
+        - "Manual /dna-frw-diagnosis and /dna-frw-fix flows remain separate and available."
+        - "Do not use the generic workflow policy block; branch only from the progress JSON verdict."
 
 workflows:
   behavior-lock:
@@ -494,7 +534,11 @@ workflows:
 
           Continue within the round while changes are coherent and reviewable. If the remaining work is large, stop at a natural boundary and leave the rest for the next fix round.
 
-          After each fix: run tests ONCE for that specific file.
+          Shared boundary rule:
+          - If this round changes an interface, abstract class, provider, initializer, repository contract, constructor, public model/DTO, fake/mock, or test helper, search for affected fake/mock/helper implementations and update them in the same round.
+          - In that case, run the targeted test plus the affected module behavior suite once when practical; do not wait for final verification to discover compile/load failures caused by stale test fakes.
+
+          After each fix: run tests ONCE for that specific file unless the shared boundary rule requires the affected module behavior suite.
           Commit only the round's coherent changes, with message including what changed, why, and which tests were targeted.
         handoff:
           consumes:
@@ -520,7 +564,8 @@ workflows:
           2. Is REMOVED handling absent unless explicitly approved by user?
           3. Does implementation preserve v1 behavior and follow v2 architecture?
           4. Are test infra changes honest, not fake mocks?
-          5. Is there unrelated refactor or scope creep?
+          5. If shared interfaces/providers/initializers/contracts/constructors/models or test helpers changed, were affected fake/mock/helper implementations searched and synchronized?
+          6. Is there unrelated refactor or scope creep?
 
           Output exactly one structured verdict block:
           ```json
@@ -614,6 +659,8 @@ workflows:
           - Remaining UNIMPLEMENTED skipped: U diagnosis-backed skipped tests still remaining
           - Failure reason: why progress stopped, if any
           - Next round focus: the priority/classification/test file to continue with, if verdict is CONTINUE or REQUEST_CHANGES
+          - Rollback decision: say whether the current round commit should be reverted or fixed forward, with one plain-language reason
+          - Single-fix prompt: required when rollback decision recommends fix-forward; include current commit, exact failure, allowed scope, forbidden actions, verification command, commit expectation, and stop conditions
 
           Always write or update .dna/fix-progress/$ARGUMENTS.md before finishing, even when review blocks verification. Include these sections:
           - Current verdict: Verdict, Review, Module complete, Last fix commit, Updated at
@@ -622,6 +669,8 @@ workflows:
           - Review Issues To Address First: reviewer issues when Review is REQUEST_CHANGES
           - Failed approaches / Do not repeat: approaches that failed or caused regressions
           - Evidence: commands run and relevant paths
+          - Rollback Decision: required when Verdict is REQUEST_CHANGES or BLOCKED after a current-round commit exists; say revert or fix-forward with one reason
+          - Single-Fix Prompt: required when Rollback Decision recommends fix-forward; make it copy-pasteable and narrow
 
           Always write or update .dna/fix-progress/$ARGUMENTS.json before finishing, even when review blocks verification. The JSON must match this contract exactly:
           ```json

package/dist/templates/metadata.d.ts

@@ -0,0 +1,6 @@
+export interface TemplateMatchMetadata {
+    name: string;
+    keywords: readonly string[];
+}
+export declare const TEMPLATE_MATCH_METADATA: readonly TemplateMatchMetadata[];
+export declare function getTemplateMatchMetadata(name: string): TemplateMatchMetadata | undefined;

package/dist/templates/metadata.js

@@ -0,0 +1,32 @@
+export const TEMPLATE_MATCH_METADATA = [
+    { name: "code-review-pipeline", keywords: ["review", "code review", "pr review", "pull request", "审查"] },
+    { name: "safe-refactoring", keywords: ["refactor", "refactoring", "restructure", "rewrite safely", "重构"] },
+    { name: "tdd-strict", keywords: ["tdd", "test driven", "test first", "red green", "测试驱动"] },
+    { name: "full-pipeline", keywords: ["pipeline", "plan implement test", "full workflow", "完整流水线"] },
+    { name: "systematic-debugging", keywords: ["debug", "debugging", "bug fix", "troubleshoot", "调试"] },
+    { name: "verification-loop", keywords: ["verify", "verification", "validate", "check", "验证"] },
+    { name: "secure-dev", keywords: ["security", "secure", "owasp", "vulnerability", "安全"] },
+    { name: "enterprise-baseline", keywords: ["enterprise", "organization", "company", "corporate", "企业"] },
+    { name: "frontend-quality", keywords: ["frontend", "react", "vue", "css", "ui", "前端"] },
+    { name: "api-backend", keywords: ["api", "backend", "rest", "graphql", "server", "后端"] },
+    { name: "mobile-dev", keywords: ["mobile", "ios", "android", "react native", "移动"] },
+    { name: "documentation-writer", keywords: ["doc", "documentation", "readme", "wiki", "文档"] },
+    { name: "devops-cicd", keywords: ["devops", "ci", "cd", "deploy", "pipeline", "运维"] },
+    { name: "monorepo-governance", keywords: ["monorepo", "workspace", "packages", "governance"] },
+    { name: "flutter-behavior-lock", keywords: ["flutter", "behavior lock", "behavior spec", "行为锁定"] },
+    { name: "flutter-rewrite", keywords: ["flutter", "rewrite", "migration", "flutter rewrite"] },
+    { name: "flutter-refactoring-rescue", keywords: ["flutter", "rescue", "refactoring rescue"] },
+    { name: "multi-perspective-review", keywords: ["multi perspective", "multiple reviewer", "多角度"] },
+    { name: "subagent-parallel", keywords: ["parallel", "subagent", "concurrent", "并行"] },
+    { name: "yolo-with-guardrails", keywords: ["yolo", "fast", "guardrails", "move fast"] },
+    { name: "brainstorming-first", keywords: ["brainstorm", "explore", "ideation", "探索"] },
+    { name: "branch-finishing", keywords: ["branch", "finish", "cleanup", "pr prep"] },
+    { name: "pr-submitter", keywords: ["pr", "pull request", "submit"] },
+    { name: "migration-safety", keywords: ["migration", "migrate", "upgrade", "database migration", "dependency upgrade", "迁移"] },
+    { name: "incident-response", keywords: ["incident", "production issue", "hotfix", "outage", "postmortem", "事故"] },
+    { name: "performance-audit", keywords: ["performance", "profiling", "benchmark", "optimize", "latency", "性能"] },
+];
+const TEMPLATE_MATCH_METADATA_BY_NAME = new Map(TEMPLATE_MATCH_METADATA.map((entry) => [entry.name, entry]));
+export function getTemplateMatchMetadata(name) {
+    return TEMPLATE_MATCH_METADATA_BY_NAME.get(name);
+}

package/package.json

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