kenaz 0.3.18 → 0.3.19

package/core/.formation/tools/loader.js

@@ -1,11 +1,7 @@
 /**
  * Formation Loader
- * YAML 技能定義 + 任務載入（支援新舊兩套任務系統）
- *
- * 任務系統：
- *   新系統 (.collaboration/tasks/)  — TASK_151+ 目錄即狀態，YAML 格式
- *   舊系統 (dev/pipeline/)          — TASK_134~187 JSON 索引 + YAML 檔
- *   查詢順序：新系統 → 舊系統 YAML → 舊系統 TASK_QUEUE.json
+ * YAML skill definitions + task loading (via task-api.js, which resolves
+ * .kenaz/tasks/ first and .collaboration/tasks/ as the legacy fallback).
  */
 
 const { execSync } = require('child_process');
@@ -14,14 +10,10 @@ const fs = require('fs');
 const yaml = (() => { try { return require('js-yaml'); } catch { return require('../../.vendor/js-yaml.cjs'); } })();
 const { FORMATION_DIR, COLLABORATION_API, ROOT } = require('./utils');
 
-// 舊系統路徑
-const LEGACY_PIPELINE_DIR = path.join(ROOT, 'dev', 'pipeline');
-const LEGACY_TASK_QUEUE = path.join(LEGACY_PIPELINE_DIR, 'TASK_QUEUE.json');
-
 /**
- * 載入 skill YAML 定義
- * @param {string} formation - 陣型名稱 (unit/solo/squad/legion)
- * @param {string} skill - 技能名稱
+ * Load a skill YAML definition (.formation/<formation>/<skill>.yaml).
+ * @param {string} formation - formation name (unit)
+ * @param {string} skill - skill name
  * @returns {object} parsed YAML
  */
 function loadSkill(formation, skill) {
@@ -34,48 +26,33 @@ function loadSkill(formation, skill) {
 }
 
 /**
- * 載入任務資料（新系統優先，fallback 舊系統）
- *
- * 查詢順序：
- *   1. .collaboration/tasks/ 或 .kenaz/tasks/ (新系統 — task-api.js get)
- *   2. dev/pipeline/completed/ + tasks/ (舊系統 YAML 檔)
- *   3. dev/pipeline/TASK_QUEUE.json (舊系統 JSON 索引)
+ * Load task data through task-api.js.
  *
- * @param {string} taskId - TASK_XXX 格式的任務 ID
- * @param {object} [options] - 可選參數
- * @param {string} [options.projectPath] - 子專案路徑（優先在此查找任務）
- * @returns {string|null} 任務 YAML/JSON 文本，或 null
+ * @param {string} taskId - TASK_XXX
+ * @param {object} [options]
+ * @param {string} [options.projectPath] - sub-project path (looked up first)
+ * @returns {string|null} task YAML text, or null
  */
 function loadTask(taskId, options) {
   if (!taskId || !taskId.startsWith('TASK_')) return null;
 
   const projectRoot = options?.projectPath || ROOT;
 
-  // 1. 新系統 (.collaboration / .kenaz)
-  const fromCollab = loadTaskFromCollaboration(taskId, projectRoot);
-  if (fromCollab) return fromCollab;
-
-  // 2. 舊系統 YAML 檔 (dev/pipeline/completed/ + tasks/)
-  const fromYaml = loadTaskFromLegacyYaml(taskId, projectRoot);
-  if (fromYaml) return fromYaml;
-
-  // 3. 舊系統 JSON 索引 (TASK_QUEUE.json)
-  const fromQueue = loadTaskFromLegacyQueue(taskId, projectRoot);
-  if (fromQueue) return fromQueue;
+  const fromApi = loadTaskFromApi(taskId, projectRoot);
+  if (fromApi) return fromApi;
 
-  console.warn(`⚠️  Task ${taskId} not found in any system (root: ${projectRoot})`);
+  console.warn(`⚠️  Task ${taskId} not found (root: ${projectRoot})`);
   return null;
 }
 
 /**
- * 從新系統 .collaboration 載入
  * @param {string} taskId
- * @param {string} projectRoot - 專案根目錄
+ * @param {string} projectRoot
  */
-function loadTaskFromCollaboration(taskId, projectRoot) {
+function loadTaskFromApi(taskId, projectRoot) {
   if (!fs.existsSync(COLLABORATION_API)) return null;
   try {
-    // 當 projectRoot 與 core ROOT 不同時，使用 --project-path
+    // When projectRoot differs from the core ROOT, pass --project-path
     const projectArg = projectRoot !== ROOT ? ` --project-path "${projectRoot}"` : '';
     const result = execSync(
       `node "${COLLABORATION_API}"${projectArg} get ${taskId}`,
@@ -87,104 +64,4 @@ function loadTaskFromCollaboration(taskId, projectRoot) {
   return null;
 }
 
-/**
- * 從舊系統 YAML 檔載入 (dev/pipeline/completed/ + tasks/)
- * @param {string} taskId
- * @param {string} projectRoot - 專案根目錄
- */
-function loadTaskFromLegacyYaml(taskId, projectRoot) {
-  const pipelineDir = path.join(projectRoot, 'dev', 'pipeline');
-  const dirs = ['completed', 'tasks'];
-  for (const dir of dirs) {
-    const dirPath = path.join(pipelineDir, dir);
-    if (!fs.existsSync(dirPath)) continue;
-    try {
-      const files = fs.readdirSync(dirPath);
-      const match = files.find(f => f.startsWith(taskId) && f.endsWith('.yaml'));
-      if (match) {
-        return fs.readFileSync(path.join(dirPath, match), 'utf8').trim();
-      }
-    } catch (e) {}
-  }
-  return null;
-}
-
-/**
- * 從舊系統 TASK_QUEUE.json 載入
- * @param {string} taskId
- * @param {string} projectRoot - 專案根目錄
- */
-function loadTaskFromLegacyQueue(taskId, projectRoot) {
-  const queuePath = path.join(projectRoot, 'dev', 'pipeline', 'TASK_QUEUE.json');
-  if (!fs.existsSync(queuePath)) return null;
-  try {
-    const queue = JSON.parse(fs.readFileSync(queuePath, 'utf8'));
-    const task = (queue.tasks || []).find(t => t.id === taskId);
-    if (task) {
-      return yaml.dump(task, { lineWidth: -1 });
-    }
-  } catch (e) {}
-  return null;
-}
-
-/**
- * 列出某個 formation 下所有可用的 skill
- * @param {string} formation - 陣型名稱
- * @returns {string[]} skill 名稱列表
- */
-function listSkills(formation) {
-  const dir = path.join(FORMATION_DIR, formation);
-  if (!fs.existsSync(dir)) return [];
-  return fs.readdirSync(dir)
-    .filter(f => f.endsWith('.yaml'))
-    .map(f => f.replace('.yaml', ''));
-}
-
-/**
- * 載入 specialist 定義（5 個 YAML 檔案）
- * @param {string} name - specialist 名稱 (e.g., "Ansuz", "Amelia")
- * @returns {object} { principles, workflow, knowledge, rule, capability }
- */
-function loadSpecialist(name) {
-  const specialistDir = path.join(ROOT, '.specialist', name);
-  if (!fs.existsSync(specialistDir)) {
-    console.error(`❌ Specialist not found: ${specialistDir}`);
-    process.exit(1);
-  }
-
-  const files = ['principles', 'workflow', 'knowledge', 'rule', 'capability'];
-  const specialist = { name };
-
-  for (const file of files) {
-    const filePath = path.join(specialistDir, `${file}.yaml`);
-    if (!fs.existsSync(filePath)) {
-      console.warn(`⚠️  Missing ${file}.yaml for specialist ${name}`);
-      specialist[file] = null;
-      continue;
-    }
-    try {
-      specialist[file] = yaml.load(fs.readFileSync(filePath, 'utf8'));
-    } catch (e) {
-      console.error(`❌ Failed to parse ${filePath}: ${e.message}`);
-      process.exit(1);
-    }
-  }
-
-  return specialist;
-}
-
-/**
- * 列出所有可用的 specialist
- * @returns {string[]} specialist 名稱列表
- */
-function listSpecialists() {
-  const specialistDir = path.join(ROOT, '.specialist');
-  if (!fs.existsSync(specialistDir)) return [];
-  return fs.readdirSync(specialistDir)
-    .filter(f => {
-      const stat = fs.statSync(path.join(specialistDir, f));
-      return stat.isDirectory();
-    });
-}
-
-module.exports = { loadSkill, loadTask, listSkills, loadSpecialist, listSpecialists };
+module.exports = { loadSkill, loadTask };

package/core/.formation/tools/post-complete.js

@@ -54,7 +54,6 @@
  * | 2.5d  | Safety net: force-move to done           | merge succeeded but complete() failed     | spawnSync                  | task stays in active                |
  * | 2.6b  | Ansuz inbox signal                       | result.taskCompleted && !dryRun           | catch (silent)             | Ansuz not notified                  |
  * | 2.6c  | Relay task_completed event (TASK_1409)   | result.taskCompleted && !dryRun && relay  | catch (silent)             | PM inbox not notified cross-node    |
- * | 3     | Memory agent onTaskCompleted/onError     | memoryAgent && taskId                     | catch (log warning)        | memory event not queued             |
  *
  * A.2  gitBranchAndMerge() — serial mode (L2344)
  *
@@ -301,12 +300,6 @@ const { verify: verifyAcceptance } = require('./verify-acceptance');
 // LLM-based acceptance verification (./verify-acceptance.js) remains and is the
 // one whose result (result.git.acceptance) is actually read.
 
-// Memory Agent（記憶系統整合）
-let memoryAgent = null;
-try {
-  memoryAgent = require('../../.memory/tools/memory-agent');
-} catch { /* memory-agent not available — graceful degradation */ }
-
 // Design Reasoning Attribution (TASK_1074)
 let designReasoning = null;
 try {
@@ -587,7 +580,6 @@ function listDaemonManagedPaths(projectRoot) {
 
   scanDir('.synapse');
   scanDir('.prefrontal');
-  scanDir('.memory');
   if (fs.existsSync(path.join(projectRoot, '.tmp'))) discovered.add('.tmp/');
 
   return Array.from(discovered);
@@ -3003,29 +2995,6 @@ function postComplete(opts = {}) {
     } catch { /* fire-and-forget — never blocks post-complete */ }
   }
 
-  // Step 3: Memory Agent（記憶系統整合）
-  if (memoryAgent && taskId) {
-    try {
-      const testsFailed = result.git?.regression && !result.git.regression.passed && !result.git.regression.skipped;
-      if (testsFailed) {
-        // 回歸測試失敗 → onError（fire-and-forget）
-        memoryAgent.onError({
-          event: 'regression_test_failure',
-          taskId,
-          error: `Regression tests failed after ${taskId} completion`,
-          summary: result.git.regression.output?.slice(-500),
-        }).catch(() => {});
-        console.log('   🧠 Memory: error event queued (regression failure)');
-      } else {
-        // 任務成功完成 → onTaskCompleted（fire-and-forget）
-        memoryAgent.onTaskCompleted(taskId).catch(() => {});
-        console.log('   🧠 Memory: task completion event queued');
-      }
-    } catch (e) {
-      console.log(`   ⚠️  Memory agent skipped: ${e.message}`);
-    }
-  }
-
   // Step 4.6: Guard Failure Detector (TASK_1653)
   // Runs shadow-mode failure detectors for active lesson guards that carry failure_signature.
   // Reads guard snapshots directly from lesson_guards.yaml (not the task chart) because

package/core/.rule/INDEX.yaml

@@ -24,8 +24,6 @@ load_order:
     description: "GEN-009: 跨平台相容原則 - Windows/macOS/Linux 三平台相容性要求"
   - path: "general/agent-workflow.yaml"
     description: "Agent 工作流程 - 記憶點優先 + 邊界意識 + Context Integrity Canary（AGT-001 至 AGT-009）"
-  - path: "general/sunny-access-control.yaml"
-    description: "SEC-010: Sunny 系統存取控制 - 禁止其他 Agent 存取 .system/sunny/"
   - path: "general/synapse-code-intelligence.yaml"
     description: "SYN-001~007: 代碼導航 — kenaz_lsp_* 代碼導航、Grep/Glob 文字與概念搜尋。記憶層 synapse_* 工具已於 2026-10-11 移除（TASK_2411）"
   # 2026-10-11 (TASK_2411): synapse-cognitive-fusion.yaml, cortex-tools.yaml, memory-source-priority.yaml, memory-language.yaml deleted - memory system removed.
@@ -41,14 +39,6 @@ load_order:
     description: "VERIFY-TGT-001~002: Rust 驗證正典 CARGO_TARGET_DIR — 單一共用目錄（dev/scripts/verify-target-dir.js），禁止自創目錄；並行驗證被 cargo 檔案鎖串行化屬正常等待"
   - path: "general/task-pool-routing.yaml"
     description: "POOL-001~003: 本地任務 vs 任務池 路由規則 — 詞彙驅動路由、術語一致性、Pool 操作安全（publish/claim 破壞性語義）"
-  - path: "general/pipeline.yaml"
-    description: "Pipeline 系統規則 - 任務管理規範"
-  - path: "pipeline/PPL-002-completed-task-archival.yaml"
-    description: "已完成任務封存規則 - 防止佇列污染"
-  - path: "pipeline/auto-update.yaml"
-    description: "PPL-003 - 任務完成後必須更新 Pipeline 系統（Critical）"
-  - path: "pipeline/task-execution.yaml"
-    description: "PPL-101 至 PPL-113 - Pipeline 任務執行規範（拆分、依賴、並行、回歸保護等）"
 
   # Code 規則組 - 從核心原則到具體實踐
   - path: "code/principles.yaml"
@@ -70,14 +60,6 @@ load_order:
 
   - path: "design/ui.yaml"
     description: "UI 設計規範"
-  - path: "design/ux.yaml"
-    description: "UX 設計原則"
-  - path: "design/colors.yaml"
-    description: "色彩系統"
-  - path: "architecture/decisions.yaml"
-    description: "架構決策記錄"
-  - path: "business/constraints.yaml"
-    description: "業務邏輯約束"
 
 # 嚴重程度定義
 severity_levels:

package/core/.rule/general/agent-workflow.yaml

@@ -11,118 +11,7 @@ _meta:
   version: "1.0.0"
 
 rules:
-  # =============================================================================
-  # AGT-001: 記憶點優先載入（核心規則）
-  # =============================================================================
-  - id: "AGT-001"
-    title: "記憶點優先載入"
-    description: |
-      所有 Agent 開始工作前，必須先讀取 .memory/CONTEXT.md。
-      此文件包含專案當前狀態、已完成功能、技術棧、關鍵路徑。
-      只有在需要詳細任務資訊時，才讀取任務文件。
-    severity: "must"
-    rationale: "減少 context 消耗，快速掌握專案狀態"
-    workflow:
-      - step: 1
-        action: "讀取 .memory/CONTEXT.md"
-        purpose: "快速掌握專案全局狀態"
-        required: true
-      - step: 2
-        action: "評估是否需要詳細任務資訊"
-        purpose: "判斷是否需要讀取更多文件"
-        criteria:
-          - "如果任務涉及特定功能，需要確認技術細節"
-          - "如果需要了解依賴關係"
-          - "如果 CONTEXT.md 資訊不足以開始工作"
-      - step: 3
-        action: "視需要讀取 dev/pipeline/PROGRESS.md 或具體任務文件"
-        purpose: "獲取具體任務細節和當前進度"
-        note: "優先讀取 PROGRESS.md 而非 TASK_QUEUE.json（後者較大）"
-
-  # =============================================================================
-  # AGT-002: 記憶點更新責任
-  # =============================================================================
-  - id: "AGT-002"
-    title: "記憶點更新責任"
-    description: |
-      完成重要里程碑或重大變更後，Agent 應更新 .memory/CONTEXT.md。
-      更新時機：
-      - 完成重要功能
-      - 技術架構變更
-      - 新增/移除主要模組
-    severity: "should"
-    rationale: "保持記憶點準確，供下次 session 使用"
-    update_triggers:
-      - "新功能完成"
-      - "重大 Bug 修復"
-      - "架構變更"
-      - "新模組加入"
-      - "技術棧更新"
-
-  # =============================================================================
-  # AGT-003: 避免重複讀取任務文件
-  # =============================================================================
-  - id: "AGT-003"
-    title: "避免重複讀取任務文件"
-    description: |
-      不要每次都讀取所有任務的詳細資訊。
-      .memory/CONTEXT.md 已包含足夠的狀態摘要。
-      只在需要特定任務細節時才讀取對應的任務文件。
-    severity: "should"
-    rationale: "節省 token，提高效率"
-    anti_patterns:
-      - "每次都讀取 TASK_QUEUE.json 全部內容"
-      - "遍歷 dev/pipeline/tasks/ 目錄讀取所有任務"
-      - "重複讀取已知資訊"
-
-  # =============================================================================
-  # AGT-004: 任務執行前置流程（新增）
-  # =============================================================================
-  - id: "AGT-004"
-    title: "任務執行前置流程"
-    description: |
-      定義 Agent 執行任務前的標準流程，確保記憶點系統與任務單系統協同運作。
-      此流程為基本流程：先讀 CONTEXT.md → 再讀任務單 → 執行任務。
-    severity: "must"
-    rationale: "確保 Agent 在充分了解專案狀態後才開始執行任務"
-    workflow:
-      - phase: "Context 獲取"
-        steps:
-          - step: 1
-            action: "讀取 .memory/CONTEXT.md"
-            required: true
-            purpose: "了解專案全局狀態、技術棧、關鍵路徑"
-          - step: 2
-            action: "讀取 dev/pipeline/PROGRESS.md"
-            required: true
-            purpose: "了解當前進度和待處理任務列表"
-      - phase: "任務確認"
-        steps:
-          - step: 3
-            action: "確定本次要執行的任務"
-            required: true
-            purpose: "從待處理佇列中選取最優先的任務"
-          - step: 4
-            action: "讀取具體任務文件（dev/pipeline/tasks/TASK_XXX.yaml）"
-            required: true
-            purpose: "獲取任務的詳細需求、驗收標準、技術備註"
-      - phase: "執行任務"
-        steps:
-          - step: 5
-            action: "按照任務需求執行開發工作"
-            required: true
-            purpose: "完成任務定義的所有驗收標準"
-          - step: 6
-            action: "更新進度文件"
-            required: true
-            purpose: "記錄任務完成狀態，歸檔任務文件"
-    integration:
-      memory_system: ".memory/CONTEXT.md"
-      task_system: "dev/pipeline/"
-      relationship: |
-        記憶點系統提供專案全局 Context，減少重複讀取。
-        任務單系統提供具體執行細節和驗收標準。
-        兩者協同運作：先從記憶點獲取全局視角，再從任務單獲取執行細節。
+  # AGT-001~004（.memory/CONTEXT.md 記憶點載入/更新、PROGRESS.md 任務前置）已於 2026-10 移除：記憶系統與 dev/pipeline 已退役。
 
   # =============================================================================
   # AGT-005: 失敗時必須查閱失敗經驗
@@ -238,10 +127,8 @@ rules:
       - pattern: "專案根目錄及其子目錄"
         description: "當前工作目錄（project root）"
         examples:
-          - ".memory/"
           - ".failure/"
           - ".rule/"
-          - "dev/pipeline/"
           - "src/"
           - "dashboard/"
 
@@ -259,16 +146,16 @@ rules:
     error_messages:
       - trigger: "嘗試訪問 ~/.claude/"
         message: "❌ 違反 AGT-007：禁止訪問用戶私有配置目錄 (~/.claude/)"
-        suggestion: "全局記憶由 Claude Code 自動管理，請在專案內 .memory/ 記錄專案相關資訊"
+        suggestion: "全局記憶由 Claude Code 自動管理；專案教訓用 `kenaz learn add`"
       - trigger: "嘗試訪問 C:\\Users\\*\\.claude\\"
         message: "❌ 違反 AGT-007：禁止訪問用戶私有配置目錄"
-        suggestion: "請使用專案內的 .memory/ 系統"
+        suggestion: "專案教訓請用 `kenaz learn add`，不要寫入用戶目錄"
 
     related_systems:
-      project_memory:
-        path: ".memory/"
-        purpose: "專案特定的記憶、日誌、任務記錄"
-        management: "Agent 手動寫入"
+      project_lessons:
+        path: ".kenaz/knowledge/"
+        purpose: "專案教訓（kenaz learn add）"
+        management: "kenaz learn"
         should_access: true
       global_memory:
         path: "~/.claude/projects/.../memory/MEMORY.md"
@@ -281,11 +168,8 @@ rules:
       good:
         - description: "✅ 在專案內記錄學習經驗"
           code: |
-            # 正確：寫入專案內的 .memory/topics/
-            Write(
-                file_path=".memory/topics/learning-2026-02-11.md",
-                content="學習筆記內容..."
-            )
+            # 正確：用 kenaz learn 記錄到專案內
+            Bash(command='kenaz learn add "..."')
       bad:
         - description: "❌ 嘗試訪問全局記憶目錄"
           code: |
@@ -343,7 +227,7 @@ rules:
       - phase: "檢查階段"
         questions:
           - "任務要求的所有輸出是否已產生？"
-          - "文檔是否已寫入專案內？（.memory/, .failure/, dev/）"
+          - "文檔是否已寫入專案內？（.failure/, dev/）"
           - "代碼變更是否已完成？"
           - "Git commit 是否已建立？"
           - "任務狀態是否已更新？"
@@ -385,7 +269,7 @@ rules:
       - phase: "Output Verification（驗證輸出）"
         steps:
           - "檢查所有要求的輸出是否已產生"
-          - "驗證文檔在專案內（.memory/, .failure/）"
+          - "驗證文檔在專案內（.failure/）"
           - "確認 Git commit 已建立"
       - phase: "Completion Check（完成檢查）"
         question: "所有輸出都完整嗎？"
@@ -429,7 +313,7 @@ rules:
           scenario: "完成並行處理失敗學習文檔"
           steps:
             - "1. 建立 .failure/architecture/FAIL-004_*.md ✅"
-            - "2. 建立 .memory/topics/parallel-processing-*.md ✅"
+            - "2. 建立專案內的 parallel-processing 筆記 ✅"
             - "3. Git commit ✅"
             - "4. 檢查：所有輸出都完整？ → 是 ✅"
             - "5. 停止工作，等待用戶指示 ✅"
@@ -439,7 +323,7 @@ rules:
           scenario: "完成並行處理失敗學習文檔後"
           steps:
             - "1. 建立 .failure/architecture/FAIL-004_*.md ✅"
-            - "2. 建立 .memory/topics/parallel-processing-*.md ✅"
+            - "2. 建立專案內的 parallel-processing 筆記 ✅"
             - "3. Git commit ✅"
             - "4. 想：'應該更新 MEMORY.md 索引' ❌"
             - "5. 嘗試訪問 ~/.claude/.../memory/ ❌（違反 AGT-007）"
@@ -461,7 +345,7 @@ rules:
     checklist:
       - item: "✅ 所有任務要求的輸出都已產生"
         importance: "critical"
-      - item: "✅ 文檔都在專案內（.memory/, .failure/）"
+      - item: "✅ 文檔都在專案內（.failure/）"
         importance: "critical"
       - item: "✅ Git commit 已建立"
         importance: "high"
@@ -536,37 +420,3 @@ rules:
         importance: "critical"
       - item: "✅ 恢復的 scope_paths 與當前任務一致"
         importance: "high"
-
-  # =============================================================================
-  # AGT-010: Formation Dispatch 後必須切回 User Branch
-  # =============================================================================
-  - id: "AGT-010"
-    title: "Dispatch 後切回 User Branch"
-    description: |
-      （已退役）Formation headless dispatch 曾在獨立進程中建立 task branch（task/task_XXX），
-      完成後 post-complete.js 會 merge 回 user branch。但呼叫者（Ansuz/Agent）的
-      working tree 仍停留在 task branch 上。
-
-      如果 dispatch 後繼續在同一 session 做其他改動，會意外 commit 到 task branch，
-      而不是 user branch。用戶在桌面端會看到 branch 不一致。
-    severity: "must"
-    rationale: "headless dispatch 是獨立進程（已退役，僅供歷史參照），不會切換呼叫者的 git working tree"
-    trigger: "legacy Formation dispatch 完成後，Ansuz 或 Agent 要做下一個改動之前"
-    workflow:
-      - step: 1
-        action: "確認 dispatch 完成（task status = completed）"
-      - step: 2
-        action: "git checkout <user-branch>（通常是 xyz951610 或 main）"
-        command: "git checkout $(git config --get init.defaultBranch || echo main)"
-        note: "如果有 uncommitted changes，先 stash 再 checkout"
-      - step: 3
-        action: "確認 task branch 的改動已 merge（git log 可見 merge commit）"
-      - step: 4
-        action: "繼續下一個改動"
-    anti_pattern: |
-      ❌ Dispatch 完成後直接繼續編輯（仍在 task/task_XXX branch）
-      ❌ 多個 task 共用同一個 task branch（每個 task 應有自己的 branch）
-    applies_to:
-      - "Ansuz（PM dispatch 後繼續做其他工作）"
-      - "任何仍經 legacy Formation dispatch 的 Agent"
-      - "用戶手動 dispatch 後"

package/core/.rule/general/project-self-containment.yaml

@@ -45,7 +45,7 @@ rules:
         - path: "dev/"
           purpose: "開發工具和任務管理"
           must_contain:
-            - "pipeline/ - 任務追蹤系統"
+            - "pipeline/ - 凍結的舊任務佇列（僅歷史參照；現行任務在 .kenaz/tasks/）"
             - "scripts/ - 自動化腳本"
             - "PRODUCT_SPEC.md - 產品規格"
 
@@ -95,21 +95,16 @@ rules:
       task_tracking:
         - title: "任務追蹤必須在專案內"
           description: |
-            所有任務追蹤文件必須在 dev/pipeline/ 下。
-            背景 agent 的任務狀態必須更新到 TASK_QUEUE.json。
+            所有任務追蹤文件必須在專案內的 .kenaz/tasks/ 下（YAML 任務卡，目錄即狀態）。
+            背景 agent 的任務狀態必須透過 task-api.js 更新。
 
           required_files:
-            - "dev/pipeline/TASK_QUEUE.json - 任務佇列"
-            - "dev/pipeline/PROGRESS.md - 進度追蹤"
-            - "dev/pipeline/tasks/ - 待處理任務"
-            - "dev/pipeline/completed/ - 已完成任務"
+            - ".kenaz/tasks/{backlog,active,done,blocked,cancel}/ - 任務卡"
 
           update_rule: |
             Agent 完成任務後必須：
-            1. 更新 TASK_QUEUE.json 中的任務狀態
-            2. 移動任務文件到 completed/
-            3. 更新 PROGRESS.md
-            4. 建立 Git commit（包含 Task ID）
+            1. node .collaboration/core/task-api.js complete TASK_XXX
+            2. 建立 commit（包含 Task ID）
 
       background_agents:
         - title: "背景 Agent 必須使用專案配置"
@@ -122,7 +117,7 @@ rules:
             - "Task(run_in_background=True) 創建新 session"
             - "新 session 讀取 .claude/settings.local.json"
             - "背景 agent 使用專案配置的權限執行"
-            - "輸出文件寫入專案的 temp 目錄或 dev/pipeline/"
+            - "輸出文件寫入專案的 temp 目錄"
 
           anti_pattern: |
             ❌ 假設背景 agent 會繼承主 session 的權限
@@ -167,13 +162,7 @@ rules:
         - description: "背景 Agent 更新專案內任務狀態"
           code: |
             # 在 Agent 執行完成後
-            node -e "
-            const fs = require('fs');
-            const queue = JSON.parse(fs.readFileSync('dev/pipeline/TASK_QUEUE.json', 'utf8'));
-            const task = queue.tasks.find(t => t.id === 'TASK_XXX');
-            task.status = 'completed';
-            fs.writeFileSync('dev/pipeline/TASK_QUEUE.json', JSON.stringify(queue, null, 2));
-            "
+            node .collaboration/core/task-api.js complete TASK_XXX
 
       bad:
         - description: "❌ 依賴全局配置"

package/core/.rule/general/rust-verify-target.yaml

@@ -37,14 +37,15 @@ rules:
       shell_usage: "CARGO_TARGET_DIR=$(node dev/scripts/verify-target-dir.js) cargo check --lib -p kenaz-dashboard"
 
     rationale: |
-      - Windows MAX_PATH: vendor/kuzu CMake object paths exceed 260 chars when
-        the target dir sits under the repo or a worktree; a short root fixes it.
+      - Windows MAX_PATH: deep C/C++ dependency object paths (bundled sqlite etc.)
+        can approach 260 chars when the target dir sits under the repo or a
+        worktree; a short root keeps them safe.
       - Bounded growth: one shared dir caps disk usage structurally instead of
         relying on agent cleanup discipline (proven not to happen).
       - Warm cache: repeat verification from the same source root is much faster.
-        Caveat: kuzu is a [patch] path dep — its artifacts are keyed per source
-        root, so a verify from a NEW worktree path recompiles kuzu (but coexists
-        without invalidating other roots' artifacts).
+        Caveat: workspace crates are keyed per source root, so a verify from a
+        NEW worktree path recompiles them (but coexists without invalidating
+        other roots' artifacts).
       - The repo's own dashboard/src-tauri/target must NOT be shared for
         verification: live tauri dev holds onnxruntime.dll there (os error 32).
 

package/core/.rule/general/synapse-code-intelligence.yaml

@@ -217,7 +217,7 @@ rules:
         寫代碼前的分析（修改既有 symbol 時）：
         1. kenaz_lsp_references(symbol) → 爆炸半徑
         2. kenaz_lsp_callers(symbol, depth=2) → 跨模組呼叫者
-        禁止盲寫 — 修改非 trivial symbol 前不看影響範圍是被禁止的行為（FAIL-009）。
+        禁止盲寫 — 修改非 trivial symbol 前不看影響範圍是被禁止的行為。
 
       red_flags: |
         如果你發現自己在想以下任何一句話 — 立刻停下，這是跳過影響分析的前兆：
@@ -226,12 +226,12 @@ rules:
         - 「我已經很熟這段代碼了」
         - 「只是改個文字 / 樣式 / 常數」
         - 「趕時間，先改了再說」
-        來源：FAIL-009（LoadingScreen.tsx 事件）。
+        來源：LoadingScreen.tsx 事件。
         原則：覺得太簡單不需要查的時刻，正是最需要它的時刻。
 
       anti_rationalization:
         - excuse: "這只是 UI 改動，不影響邏輯"
-          reality: "LoadingScreen.tsx 就是這樣出事的（FAIL-009）。UI 組件有 props、state、context 依賴。"
+          reality: "LoadingScreen.tsx 就是這樣出事的。UI 組件有 props、state、context 依賴。"
         - excuse: "我剛才已經查過相關的 symbol 了"
           reality: "每個被修改的 symbol 都需要獨立查影響範圍。相關不等於相同。"
         - excuse: "這次改動範圍很小，不會有爆炸半徑"