intentdna 1.0.0 → 1.2.0

package/dist/templates/flutter-behavior-lock.dna.yaml

@@ -0,0 +1,122 @@
+# flutter-behavior-lock: 锁定 v1 行为 → 生成测试
+# 场景: 框架迁移前/中，需要把 v1 的所有行为锁定为可执行的测试
+# 产出: 行为文档 + 单元测试 + 端到端测试用例
+# 执行方式: 逐模块，每个模块独立 agent 会话
+
+version: "0.1.0"
+id: template_flutter_behavior_lock
+name: Flutter Behavior Lock
+type: project
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+genes:
+  scan_not_change:
+    description: This workflow only reads v1 and writes docs/tests — never modifies app code
+    codons:
+      - type: threshold
+        condition: "modify_app_source == false"
+        action: block
+      - type: attract
+        target: read_source_generate_docs
+      - type: repel
+        target: refactor_during_scan
+
+  function_call_granularity:
+    description: Behavior docs at function-call level — not too coarse, not too fine
+    codons:
+      - type: attract
+        target: user_action_to_function_call
+      - type: repel
+        target: widget_tree_details
+      - type: repel
+        target: vague_feature_description
+      - type: weight
+        a: precision
+        b: brevity
+        ratio: 0.7
+
+  one_module_per_session:
+    description: Each agent session handles exactly one module to avoid context overflow
+    codons:
+      - type: attract
+        target: single_module_focus
+      - type: repel
+        target: cross_module_scanning
+      - type: threshold
+        condition: "modules_per_session <= 1"
+        action: escalate
+
+contexts: {}
+
+roles:
+  scanner:
+    description: Reads v1 source code, outputs behavior document for one module
+    tool_permissions:
+      allow: [Read, Grep, Glob, Bash]
+      deny: [Edit, Write, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: []
+    instructions:
+      - Scan ONE module only (specified in prompt)
+      - For each page/screen in the module, list all user-visible actions
+      - For each action, trace the call chain to the first service/repository call
+      - "Format: 动作 → 函数调用 → 期望返回值/副作用"
+      - Output as structured markdown with checkboxes
+      - Mark uncertain items as [待确认]
+      - Do NOT read v2 code — only v1
+
+  test_writer:
+    description: Reads behavior document, writes unit tests for v2, runs baseline
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["test/**", "docs/behavior/**"]
+    instructions:
+      - Read the behavior document for the specified module
+      - Write one test file per page/screen
+      - Each user action = one test case
+      - "Test the function call level: does the service method return expected result?"
+      - Use existing v2 framework patterns (check test/ for examples)
+      - Run tests after writing — record pass/fail counts as baseline
+      - Append baseline to docs/behavior/{module}.md under a '# Baseline' section
+      - Red tests are expected (v2 not yet fixed)
+      - Do NOT modify app source code — only write tests
+
+  qa_verifier:
+    description: Runs end-to-end verification on device/emulator via adb
+    tool_permissions:
+      allow: [Read, Bash, Grep, Glob]
+      deny: [Edit, Write, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: []
+    instructions:
+      - Use adb to screencap the target module's page on device
+      - Use adb logcat to capture runtime errors
+      - If device not connected, skip and report
+      - Append screenshots and error logs to docs/behavior/{module}.md
+      - Never modify code — only observe and report
+
+workflows:
+  behavior-lock:
+    name: Behavior Lock
+    steps:
+      - id: scan
+        role: scanner
+        description: Scan one v1 module, output behavior document
+        prompt: "Scan module '{{module}}' in {{v1_path}}. Output behavior document to {{output_path}}/{{module}}.md. Then immediately proceed to write_tests step — do not stop."
+      - id: write_tests
+        role: test_writer
+        depends_on: [scan]
+        description: Write unit tests, run baseline, append results to behavior doc
+        prompt: "Read {{output_path}}/{{module}}.md. Write tests in {{test_path}}/{{module}}/ for v2 code at {{v2_path}}. Run tests and record pass/fail as baseline in the behavior doc. Then immediately proceed to qa_verify step."
+      - id: qa_verify
+        role: qa_verifier
+        depends_on: [write_tests]
+        description: End-to-end verification on device via adb (optional)
+        prompt: "Verify '{{module}}' module on device. Use adb screencap + logcat. Append results to {{output_path}}/{{module}}.md. Skip if no device connected but note in summary."

package/dist/templates/flutter-refactoring-rescue.dna.yaml

@@ -0,0 +1,140 @@
+# flutter-refactoring-rescue: 修复已迁移但不能用的 Flutter 项目
+# 场景: 框架迁移已完成，但功能链路断裂，需要逐条修复
+# 核心纪律: 一次一条链路，改一个验一个，v1 是 oracle
+# 参考: safe-refactoring + verification-loop + Superpowers systematic-debugging
+
+version: "0.1.0"
+id: template_flutter_refactoring_rescue
+name: Flutter Refactoring Rescue
+type: project
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+genes:
+  one_chain_at_a_time:
+    description: Each session fixes exactly one functional chain (e.g. "send message → receive reply")
+    codons:
+      - type: attract
+        target: single_feature_chain_per_session
+      - type: repel
+        target: parallel_feature_changes
+      - type: repel
+        target: cross_module_changes
+      - type: threshold
+        condition: "files_changed_per_commit <= 5"
+        action: escalate
+
+  v1_is_oracle:
+    description: Copy logic from v1, never guess API signatures or behavior
+    codons:
+      - type: attract
+        target: read_v1_source_before_changing_v2
+      - type: attract
+        target: copy_logic_from_v1
+      - type: repel
+        target: guess_api_signature
+      - type: repel
+        target: invent_new_logic
+      - type: threshold
+        condition: "fabricate_code_without_v1_reference == false"
+        action: block
+
+  runtime_verification:
+    description: Every change must be verified on device before commit
+    codons:
+      - type: attract
+        target: adb_screenshot_after_change
+      - type: attract
+        target: logcat_error_check
+      - type: repel
+        target: assumed_fix
+      - type: threshold
+        condition: "commit_without_device_verification == false"
+        action: block
+      - type: sense
+        signal: incomplete_result
+        response: retry_with_more_depth
+
+  small_steps:
+    description: Change one file, verify, then move to next
+    codons:
+      - type: attract
+        target: single_file_change
+      - type: attract
+        target: hot_reload_after_each_change
+      - type: repel
+        target: batch_file_changes
+      - type: weight
+        a: safety
+        b: speed
+        ratio: 0.9
+
+  preserve_behavior:
+    description: Preserve existing behavior including bugs — only change framework
+    codons:
+      - type: attract
+        target: same_inputs_same_outputs
+      - type: attract
+        target: preserve_bug_behavior
+      - type: repel
+        target: sneaky_behavior_changes
+      - type: repel
+        target: improvement_during_refactor
+      - type: sense
+        signal: uncertain_information
+        response: escalate_to_human
+
+contexts: {}
+
+roles:
+  investigator:
+    description: Reads v1 code and traces the broken chain — never writes code
+    tool_permissions:
+      allow: [Read, Grep, Glob, Bash]
+      deny: [Edit, Write, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: []
+    instructions:
+      - Trace the full call chain in v1 for the target feature
+      - Find the corresponding v2 code for each step in the chain
+      - Identify the first breakpoint where v2 diverges from v1
+      - Report with exact file paths and line numbers
+      - Use adb logcat to capture runtime errors
+      - Never suggest code changes — only report findings
+
+  surgeon:
+    description: Fixes one breakpoint at a time by copying logic from v1
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["lib/**"]
+    instructions:
+      - Fix only the breakpoint identified by investigator
+      - Copy logic from v1, adapt to v2 framework — do not invent
+      - Change at most one file per round
+      - After each change, verify with hot reload + adb screenshot
+      - If the fix doesn't work, revert and re-analyze
+      - Never "improve" code during refactoring — preserve exact behavior
+
+workflows:
+  rescue-chain:
+    name: Chain Rescue
+    steps:
+      - id: trace
+        role: investigator
+        description: Trace the broken chain in v1 and v2, identify first breakpoint
+        prompt: "Trace the call chain for '{{feature}}' in v1 ({{v1_path}}) and v2 ({{v2_path}}). Find where v2 breaks."
+      - id: fix
+        role: surgeon
+        depends_on: [trace]
+        description: Fix the identified breakpoint
+        prompt: "Fix the breakpoint identified by investigator. Copy logic from v1, change one file only."
+      - id: verify
+        role: investigator
+        depends_on: [fix]
+        description: Verify the fix with adb
+        prompt: "Run the feature on device. adb screencap + logcat. Compare with v1 behavior."

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

@@ -0,0 +1,216 @@
+# flutter-rewrite: 完整重构工作流（统一 DNA，不需要切换）
+# 包含所有阶段的角色和约束，通过 .dna-mode 状态文件切换行为
+# 参考: OMC hooks.json — 一套 hooks 固定注册，状态驱动行为
+
+version: "0.1.0"
+id: template_flutter_rewrite
+name: Flutter Rewrite (Unified)
+type: project
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+# 项目级变量 — dna sync 时交互式提问
+variables:
+  v1_path:
+    description: "v1 源码路径 (v1 的 lib 目录)"
+    default: "common/lib"
+  v2_path:
+    description: "v2 源码路径 (v2 的 packages 目录)"
+    default: "v2/packages"
+  behavior_docs:
+    description: "行为文档输出目录"
+    default: "docs/behavior"
+  test_path:
+    description: "测试输出目录"
+    default: "test/behavior"
+
+genes:
+  # ── 全局约束（所有模式都生效）──
+  no_add_no_remove:
+    description: Do not add features v1 doesn't have, do not remove features v1 has
+    codons:
+      - type: threshold
+        condition: "add_new_feature == false"
+        action: block
+      - type: threshold
+        condition: "remove_existing_feature == false"
+        action: block
+      - type: repel
+        target: improvement_during_refactor
+
+  one_module_per_session:
+    description: Each session handles exactly one module
+    codons:
+      - type: attract
+        target: single_module_focus
+      - type: repel
+        target: cross_module_changes
+      - type: threshold
+        condition: "modules_per_session <= 1"
+        action: escalate
+
+  v1_is_truth:
+    description: v1 source code is the only source of truth, not old docs
+    codons:
+      - type: attract
+        target: read_v1_source_before_changing
+      - type: repel
+        target: guess_api_signature
+      - type: threshold
+        condition: "fabricate_code_without_v1_reference == false"
+        action: block
+
+  # ── scan 模式约束 ──
+  scan_read_only:
+    description: In scan mode, never modify app source code
+    codons:
+      - type: attract
+        target: read_source_generate_docs
+      - type: repel
+        target: refactor_during_scan
+
+  # ── rescue 模式约束 ──
+  rescue_small_steps:
+    description: In rescue mode, change one file at a time and verify
+    codons:
+      - type: attract
+        target: single_file_change
+      - type: attract
+        target: test_after_each_change
+      - type: repel
+        target: batch_file_changes
+      - type: weight
+        a: safety
+        b: speed
+        ratio: 0.9
+
+  preserve_behavior:
+    description: Preserve existing behavior including bugs
+    codons:
+      - type: attract
+        target: same_inputs_same_outputs
+      - type: repel
+        target: sneaky_behavior_changes
+      - type: sense
+        signal: uncertain_information
+        response: escalate_to_human
+
+contexts: {}
+
+roles:
+  # ── Phase 0/3: behavior-lock 角色 ──
+  scanner:
+    description: Scans v1 source code, outputs behavior document. Read-only.
+    tool_permissions:
+      allow: [Read, Grep, Glob, Bash]
+      deny: [Edit, Write, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: []
+    instructions:
+      - Scan ONE module only
+      - "For each page, list user-visible actions: 动作 → 函数调用 → 返回值"
+      - Output as markdown with checkboxes
+      - Do NOT read v2 code — only v1
+
+  test_writer:
+    description: Reads behavior document, writes unit tests for v2.
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["test/**", "docs/behavior/**"]
+    instructions:
+      - Read the behavior document for the module
+      - Write one test file per page/screen
+      - Each user action = one test case
+      - Test service/repository layer, not UI
+      - Run tests after writing — record baseline
+      - Red tests are expected
+
+  # ── Phase 4: rescue 角色 ──
+  investigator:
+    description: Traces broken chain in v1 and v2, identifies breakpoint. Read-only.
+    tool_permissions:
+      allow: [Read, Grep, Glob, Bash]
+      deny: [Edit, Write, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: []
+    instructions:
+      - Trace the call chain in v1 for the target feature
+      - Find where v2 diverges
+      - Report with exact file paths and line numbers
+      - Never suggest code changes
+
+  surgeon:
+    description: Fixes one breakpoint at a time by understanding v1 intent and rewriting in v2 style.
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["lib/**", "v2/**"]
+    instructions:
+      - Fix only the identified breakpoint
+      - Read v1 to understand intent, rewrite in v2 framework style
+      - Do not copy v1 code verbatim — adapt to v2 architecture
+      - Change at most one call chain (2-3 files) per round
+      - After each change, run tests
+      - If fix doesn't work, revert and re-analyze
+      - Never "improve" code — preserve exact behavior
+      - "UI files: copy from v1, only change state binding syntax (Obx→Consumer, Get.to→context.go)"
+
+  # ── Core align 角色 ──
+  core_aligner:
+    description: Aligns v2 core with v1 infrastructure. Can modify core only.
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["v2/packages/core/**"]
+    instructions:
+      - Compare v1 and v2 core module by module
+      - MethodChannel names and method signatures must match v1 exactly
+      - Only change DI pattern (GetX → Riverpod), not logic
+      - Do not add methods v1 doesn't have
+      - Do not remove methods v1 has
+
+workflows:
+  behavior-lock:
+    name: Behavior Lock
+    description: "Scan v1 module $ARGUMENTS, generate behavior doc and tests for v2"
+    steps:
+      - id: scan
+        role: scanner
+        description: "Scan v1 module in {{v1_path}}/. Output behavior doc to {{behavior_docs}}/$ARGUMENTS.md. List all user actions with call chains."
+        prompt: "Scan module '$ARGUMENTS' in {{v1_path}}/. For each page, list: action → function() → return value. Output to {{behavior_docs}}/$ARGUMENTS.md. Then immediately proceed to write_tests."
+      - id: write_tests
+        role: test_writer
+        depends_on: [scan]
+        description: "Read {{behavior_docs}}/$ARGUMENTS.md, write tests in {{test_path}}/$ARGUMENTS/, run baseline."
+        prompt: "Read {{behavior_docs}}/$ARGUMENTS.md. Write tests in {{test_path}}/$ARGUMENTS/. Run tests, record red/green baseline. Append baseline to behavior doc."
+
+  rescue:
+    name: Rescue
+    description: "Fix v2 module $ARGUMENTS by making failing tests pass"
+    steps:
+      - id: investigate
+        role: investigator
+        description: "Run tests, find first red test, trace the broken call chain in v1 and v2."
+        prompt: "Run tests in {{test_path}}/$ARGUMENTS/. For the first red test, trace: what does v1 do vs what does v2 do? Find the breakpoint. Report and wait for user confirmation."
+      - id: fix
+        role: surgeon
+        depends_on: [investigate]
+        description: "Fix the breakpoint. Read v1 intent, rewrite in v2 style. Run tests after."
+        prompt: "Fix the identified breakpoint. Read v1 in {{v1_path}}/. Rewrite in v2 style in {{v2_path}}/. Run tests. Red→green = done. Still red = revert and re-analyze."
+
+  core-align:
+    name: Core Align
+    description: "Align v2 core infrastructure with v1"
+    steps:
+      - id: align
+        role: core_aligner
+        description: "Compare {{v1_path}}/ and {{v2_path}}/core/ module by module. Fix mismatches."
+        prompt: "Compare v1 ({{v1_path}}/) and v2 core ({{v2_path}}/core/lib/). List mismatches. Fix by copying v1 logic, only changing DI (GetX→Riverpod). Run flutter analyze after each fix."

package/package.json

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