kenaz 0.3.9 → 0.3.11

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

@@ -12,11 +12,6 @@ const {
   checkAndUpdatePostCompleteGuard,
   writeInboxEntryIdempotent,
 } = require('./post-complete');
-const {
-  saveTaskHealthSnapshot,
-  readPreTaskHealthSnapshot,
-  resolveMcpProjectPath,
-} = require('./post-complete/health');
 const {
   isAutoWritePath,
   filterOutcomeFilesForPrediction,
@@ -770,136 +765,6 @@ test('checkAndUpdatePostCompleteGuard: worktree→null still fires (TASK_1430)',
   }
 });
 
-// ── Health snapshot enrichment tests (TASK_1431) ─────────────────────────────
-
-test('saveTaskHealthSnapshot: delta_from_previous computed against most recent prior _after snapshot', () => {
-  const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), 'pc-health-delta-'));
-  try {
-    const snapshotsDir = path.join(tmpRoot, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(snapshotsDir, { recursive: true });
-
-    // Write a prior _after snapshot with a slightly older timestamp
-    fs.writeFileSync(
-      path.join(snapshotsDir, 'TASK_100_after.json'),
-      JSON.stringify({
-        score: 45.0, grade: 'F (Critical)', score_version: 'memory-v1',
-        timestamp: new Date(Date.now() - 10000).toISOString(), sub_metrics: {},
-      }, null, 2)
-    );
-
-    saveTaskHealthSnapshot('TASK_200', 'after', { score: 47.0, grade: 'F (Critical)', sub_metrics: { degree_entropy: { score: 60 } } }, tmpRoot);
-
-    const saved = JSON.parse(fs.readFileSync(path.join(snapshotsDir, 'TASK_200_after.json'), 'utf8'));
-    assert.equal(saved.score, 47.0);
-    assert.equal(saved.delta_from_previous, 2.0, 'delta should be 47 - 45 = 2.0');
-    assert.equal(saved.trend_5tasks, null, 'trend_5tasks is null when <5 priors');
-    assert.ok(saved.sub_metrics && typeof saved.sub_metrics === 'object', 'sub_metrics should be present');
-    assert.ok(saved.timestamp, 'timestamp must be present');
-  } finally {
-    fs.rmSync(tmpRoot, { recursive: true, force: true });
-  }
-});
-
-test('saveTaskHealthSnapshot: trend_5tasks=null when fewer than 5 prior _after snapshots', () => {
-  const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), 'pc-health-trend4-'));
-  try {
-    const snapshotsDir = path.join(tmpRoot, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(snapshotsDir, { recursive: true });
-
-    // Write exactly 4 prior _after snapshots (one short of 5)
-    for (let i = 0; i < 4; i++) {
-      fs.writeFileSync(
-        path.join(snapshotsDir, `TASK_${100 + i}_after.json`),
-        JSON.stringify({
-          score: 45.0 + i, grade: 'F (Critical)', score_version: 'memory-v1',
-          timestamp: new Date(Date.now() - (4 - i) * 10000).toISOString(), sub_metrics: {},
-        }, null, 2)
-      );
-    }
-
-    saveTaskHealthSnapshot('TASK_200', 'after', { score: 50.0, grade: 'D (Poor)', sub_metrics: {} }, tmpRoot);
-
-    const saved = JSON.parse(fs.readFileSync(path.join(snapshotsDir, 'TASK_200_after.json'), 'utf8'));
-    assert.equal(saved.trend_5tasks, null, 'trend_5tasks must be null when only 4 priors exist');
-    assert.ok(typeof saved.delta_from_previous === 'number', 'delta_from_previous should be a number when 1+ prior exists');
-  } finally {
-    fs.rmSync(tmpRoot, { recursive: true, force: true });
-  }
-});
-
-test('saveTaskHealthSnapshot: trend_5tasks computed when exactly 5 prior snapshots exist', () => {
-  const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), 'pc-health-trend5-'));
-  try {
-    const snapshotsDir = path.join(tmpRoot, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(snapshotsDir, { recursive: true });
-
-    // 5 prior snapshots: scores 40,41,42,43,44 (newest=44 at i=4, oldest=40 at i=0)
-    for (let i = 0; i < 5; i++) {
-      fs.writeFileSync(
-        path.join(snapshotsDir, `TASK_${100 + i}_after.json`),
-        JSON.stringify({
-          score: 40.0 + i, grade: 'F (Critical)', score_version: 'memory-v1',
-          timestamp: new Date(Date.now() - (5 - i) * 10000).toISOString(), sub_metrics: {},
-        }, null, 2)
-      );
-    }
-
-    // current score=50; priors newest-first=[44,43,42,41,40]; 5th prior = 40
-    // trend_5tasks = 50 - 40 = 10
-    saveTaskHealthSnapshot('TASK_200', 'after', { score: 50.0, grade: 'D (Poor)', sub_metrics: {} }, tmpRoot);
-
-    const saved = JSON.parse(fs.readFileSync(path.join(snapshotsDir, 'TASK_200_after.json'), 'utf8'));
-    assert.equal(saved.trend_5tasks, 10.0, 'trend_5tasks = currentScore - score5TasksAgo = 50 - 40');
-    assert.equal(saved.delta_from_previous, 6.0, 'delta_from_previous = 50 - 44 (most recent prior)');
-  } finally {
-    fs.rmSync(tmpRoot, { recursive: true, force: true });
-  }
-});
-
-test('saveTaskHealthSnapshot: sub_metrics object passes through from health response', () => {
-  const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), 'pc-health-subm-'));
-  try {
-    const snapshotsDir = path.join(tmpRoot, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(snapshotsDir, { recursive: true });
-
-    const subMetrics = {
-      degree_entropy: { score: 60.5, weight: 0.25, excluded_count: 3 },
-      community_balance: { score: 45.0, weight: 0.20 },
-    };
-    saveTaskHealthSnapshot('TASK_300', 'after', { score: 52.0, grade: 'D (Poor)', sub_metrics: subMetrics }, tmpRoot);
-
-    const saved = JSON.parse(fs.readFileSync(path.join(snapshotsDir, 'TASK_300_after.json'), 'utf8'));
-    assert.deepEqual(saved.sub_metrics, subMetrics, 'sub_metrics should be stored unchanged');
-  } finally {
-    fs.rmSync(tmpRoot, { recursive: true, force: true });
-  }
-});
-
-test('readPreTaskHealthSnapshot: old snapshot without enrichment fields loads without error', () => {
-  const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), 'pc-health-compat-'));
-  try {
-    const snapshotsDir = path.join(tmpRoot, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(snapshotsDir, { recursive: true });
-
-    // Old-format snapshot: only score, grade, timestamp (no sub_metrics/delta/trend)
-    fs.writeFileSync(
-      path.join(snapshotsDir, 'TASK_OLD_before.json'),
-      JSON.stringify({ score: 48.0, grade: 'F (Critical)', timestamp: new Date().toISOString() }, null, 2)
-    );
-
-    const sn = readPreTaskHealthSnapshot('TASK_OLD', tmpRoot);
-    assert.ok(sn, 'old snapshot should load without error');
-    assert.equal(sn.score, 48.0, 'score should be readable');
-    // New fields are absent in old snapshots — undefined is fine, not an error
-    assert.equal(sn.delta_from_previous, undefined, 'missing delta_from_previous is undefined not error');
-    assert.equal(sn.sub_metrics, undefined, 'missing sub_metrics is undefined not error');
-  } finally {
-    fs.rmSync(tmpRoot, { recursive: true, force: true });
-  }
-});
-
-// ---- TASK_1674: untracked-path collision tests --------------------------------
-
 test('_neutralizeUntrackedCollisions: TASK_1674 -- untracked file collides with task-branch-added path, merge proceeds and WIP preserved', () => {
   const tmpRoot = fs.mkdtempSync(path.join(os.tmpdir(), "pc-t1674-"));
   try {

package/core/.formation/tools/prompt.js

@@ -167,6 +167,10 @@ function buildSubagentPrompt(skillDef, taskInput, taskData, options = {}) {
   lines.push('');
   appendRustCheckReminder(lines, taskData, options, isIsolated);
 
+  // TASK_2409: lessons the user's Ansuz learned for this project (bounded; nothing is added when there are none).
+  const learned = projectLessons(taskData, options);
+  if (learned.facts.length) lines.push('## Project lessons', ...learned.facts, '');
+
   lines.push('## Verify and report');
   // Ponytail A/B 2026-10-10: the arm without this line broke an existing fixture test it never ran.
   lines.push('Before editing, grep the callers, tests and fixtures your change reaches; fix what it breaks. Least code that completes the card: reuse existing helpers, no unrequested abstraction, option or duplicate implementation.');
@@ -179,12 +183,22 @@ function buildSubagentPrompt(skillDef, taskInput, taskData, options = {}) {
   if (onBlocked && onBlocked.run) {
     lines.push(`Blocked: \`${buildTaskApiRewriter(options)(onBlocked.run).replace(/\{task_id\}/g, taskId)}\` and explain.`);
   }
+  for (const c of learned.checks) lines.push(`Project check: ${c.slice(2)}`);
   lines.push('Final report <= 20 lines: files touched, tests run, commit sha, unverified items.');
   lines.push('');
   appendDispatchOverrides(lines, taskData);
   return lines.join('\n');
 }
 
+function projectLessons(taskData, options) {
+  const none = { facts: [], checks: [] };
+  if (!options.projectPath) return none;
+  try {
+    const parsed = typeof taskData === 'string' ? JSON.parse(taskData) : taskData;
+    return require('../../.specialist/tools/lessons').dispatchLessons(options.projectPath, (parsed && parsed.scope_paths) || []);
+  } catch { return none; }
+}
+
 function extractTaskId(taskData) {
   try {
     const parsed = typeof taskData === 'string' ? JSON.parse(taskData) : taskData;

package/core/.formation/tools/route-audit.test.js

@@ -1,21 +1,15 @@
 'use strict';
-// TASK_2341: every /api/synapse/* and /api/cortex/* path called from node code (.formation, .claude/hooks,
-// .specialist, .collaboration) must exist in the Rust router on this branch. Source of truth: synapse.rs router().
+// TASK_2411: the memory system (synapse/hippocampus/cortex recall) and its /api/synapse router are gone, so no node
+// code (.formation, .claude/hooks, .specialist, .collaboration) may call /api/synapse/* or /api/cortex/*.
 const { test } = require('node:test');
 const assert = require('node:assert/strict');
 const fs = require('fs');
 const path = require('path');
 
 const ROOT = path.resolve(__dirname, '..', '..');
-const SYNAPSE_RS = path.join(ROOT, 'dashboard', 'src-tauri', 'src', 'infrastructure', 'http_server', 'routes', 'synapse.rs');
 const SCAN_DIRS = ['.formation', '.claude/hooks', '.specialist', '.collaboration'];
 const SKIP = /node_modules|[\/](logs|sessions|reports|designs|research|investigations|decisions)[\/]|\.test\.js$/;
 
-function routerPaths() {
-  const src = fs.readFileSync(SYNAPSE_RS, 'utf8');
-  const body = src.slice(src.indexOf('pub fn router()'), src.indexOf('#[cfg(test)]'));
-  return new Set([...body.matchAll(/\.route\(\s*"([^"]+)"/g)].map(m => '/api/synapse' + m[1]));
-}
 function walk(dir, out) {
   if (!fs.existsSync(dir)) return out;
   for (const e of fs.readdirSync(dir, { withFileTypes: true })) {
@@ -38,18 +32,12 @@ function calledPaths() {
   return found;
 }
 
-test('router paths are discovered', () => {
-  const r = routerPaths();
-  for (const p of ['/api/synapse/recall', '/api/synapse/runes/mark-acted-on-by-task']) assert.ok(r.has(p), p);
-  assert.ok(!r.has('/api/synapse/link-cognitive') && !r.has('/api/synapse/health'));
-  // TASK_2348: the spike bus and the reflex routes are gone
-  for (const p of ['/api/synapse/spike-bus/send', '/api/synapse/spike-bus/poll', '/api/synapse/reflex/feedback', '/api/synapse/reflex/dispatch/query', '/api/synapse/reflex/dopamine', '/api/synapse/reflex/consequence_feedback']) assert.ok(!r.has(p), p);
+test('no node code calls the removed /api/synapse or /api/cortex routes', () => {
+  const calls = calledPaths();
+  assert.deepEqual(calls, [], 'callers of removed routes: ' + JSON.stringify(calls));
 });
 
-test('every /api/synapse|cortex path called from node code exists on this branch', () => {
-  const r = routerPaths();
-  const calls = calledPaths();
-  assert.ok(calls.length >= 1, 'expected to find callers'); // turn-context.js stopped calling /turn-context (Kuzu removal)
-  const missing = calls.filter(c => !r.has(c.p));
-  assert.deepEqual(missing, [], 'callers of removed routes: ' + JSON.stringify(missing));
+test('control: the scanner does find a /api/synapse path in a line of code', () => {
+  const line = "fetch('http://127.0.0.1:18080/api/synapse/recall')";
+  assert.ok([...line.matchAll(/\/api\/(synapse|cortex)\/[A-Za-z0-9_\-/]+/g)].length === 1);
 });

package/core/.rule/INDEX.yaml

@@ -27,10 +27,10 @@ load_order:
   - 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_recall/inscribe/forge 條款自 2026-10-10 暫停（記憶系統凍結）"
-  # 2026-10-10: synapse-cognitive-fusion.yaml (SYN-008~012) and cortex-tools.yaml (COR-001~004) removed from the index - memory system frozen (recall ~4.7% acted on, mostly mandated). Files kept on disk.
+    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.
   - path: "general/ddx-synapse-stack.yaml"
-    description: "COG-DDX-001~003: DDx 反射 — 非 trivial 問題強制先列 3+ 假說，對抗 tunneling（synapse_recall 條款自 2026-10-10 暫停，改用 Grep/讀碼/記憶檔）"
+    description: "COG-DDX-001~003: DDx 反射 — 非 trivial 問題強制先列 3+ 假說，對抗 tunneling（recall 步驟改用 Grep/讀碼/記憶檔；synapse_* 已於 2026-10-11 移除）"
   - path: "general/specialist-identity-contract.yaml"
     description: "IDENT-001~007: Specialist 身份延續合約 — 不可變核心、可進化規則、可觀測標記、漂移指標、verify-identity.js 驗證流程"
   - path: "general/worktree-isolation.yaml"

package/core/.rule/general/ddx-synapse-stack.yaml

@@ -1,5 +1,6 @@
 # .rule/general/ddx-synapse-stack.yaml
-# COG-DDX-001: DDx + Synapse reflex stack for any non-trivial problem
+# COG-DDX-001: DDx reflex stack
+# NOTE 2026-10-11 (TASK_2411): synapse_* tools were removed; recall steps use Grep + native memory. for any non-trivial problem
 # Priority: overrides CLAUDE.md and .claude/skills/
 # Origin: 2026-04-05 Ansuz session — user identified that DDx + Synapse + Thalamus
 #   is the strongest operating mode but is never activated without user prompt.
@@ -13,11 +14,10 @@ _meta:
   last_updated: "2026-04-05"
   related:
     - "synapse-code-intelligence.yaml"
-    - "synapse-cognitive-fusion.yaml"
 
 rules:
   - id: "COG-DDX-001"
-    title: "DDx + Synapse reflex stack — mandatory on first contact with any non-trivial problem"
+    title: "DDx reflex stack — mandatory on first contact with any non-trivial problem"
     severity: "must"
     applies_to: ["ai_agent"]
 
@@ -35,16 +35,16 @@ rules:
       BEFORE the first domain tool call that touches the subject, the agent must:
         1. List 3+ competing hypotheses with one-line evidence each
            (differential diagnosis, not first-instinct single path)
-        2. Call synapse_recall on domain keywords (and Grep for exact strings)
-           (historical runes/sigils may already contain the answer)
-        3. When modifying any code symbol: synapse_recall it, then check kenaz_lsp_references / kenaz_lsp_callers for the blast radius
+        2. Grep/Glob domain keywords and check native memory files / `kenaz learn list`
+           (prior lessons may already contain the answer)
+        3. When modifying any code symbol: check kenaz_lsp_references / kenaz_lsp_callers for the blast radius
 
       These three steps are a STACK — skipping any one of them is a violation.
 
     why: |
       Observed failure mode (2026-04-05 TR87 session): agent tunneled 15
       iterations on a dead hypothesis, attempted brute-force BFS search,
-      called synapse_recall only reactively. User forced explicit DDx; puzzle
+      searched prior knowledge only reactively. User forced explicit DDx; puzzle
       then cracked in 3 steps.
       Lesson: principles-as-text do not trigger reflexively. The stack must be
       a structural precommitment, not an optional heuristic.
@@ -55,12 +55,12 @@ rules:
         - You are "trying variants" of a single idea after disconfirmation
         - You are reaching for brute-force enumeration or search
         - You cannot name 2 hypotheses besides the one you are pursuing
-        - You have not called synapse_recall this session on the current topic
+        - You have not searched code/native memory this session on the current topic
 
     enforcement: |
       - Phase 1 (needs analysis) exit requires hypotheses[] with length >= 3
         OR an explicit note that problem is trivial (scope exception)
-      - Phase 2 (background research) exit requires synapse_recall_performed=true
+      - Phase 2 (background research) exit requires evidence of Grep/read-code research
       - Kernel guardrails enforce at dispatch time
 
     examples:
@@ -69,14 +69,14 @@ rules:
           H1: auth token expired/invalid (check expiry logic)
           H2: session store disconnected (check Redis/DB)
           H3: CORS/cookie path changed (check recent config diffs)
-        synapse_recall(query="login auth token session"), kenaz_lsp_callers on
+        Grep "login auth token session", kenaz_lsp_callers on
         the entrypoint — THEN read code.
       design_decision: |
         User asks "should we use Redis or Postgres pub/sub?" BEFORE recommending:
           H1: Redis if latency < 10ms matters and durability is optional
           H2: Postgres if ACID + existing infra reuse wins
           H3: Neither — use in-process channels if single-node
-        synapse_recall(query="pub sub messaging event bus") to find prior decisions.
+        Grep/native memory for "pub sub messaging event bus" to find prior decisions.
 
   - id: "COG-DDX-002"
     title: "Hypothesis death triggers immediate DDx re-enumeration"

package/core/.rule/general/specialist-identity-contract.yaml

@@ -35,8 +35,8 @@ rules:
       The identity_contract.yaml is referenced (not duplicated) — the
       self_model_seed.json NARRATIVE section encodes the contract's intent.
     enforcement: |
-      Phase 0 actions item "[Tier 3b — 身份認識]" triggers cortex_recall for
-      Ansuz identity awareness. A session that skips Phase 0 has no identity.
+      Phase 0 actions item "[Tier 3b — 身份認識]" loads the self-model
+      files for Ansuz identity awareness (cortex_recall removed 2026-10-11). A session that skips Phase 0 has no identity.
     violation: "DI-001 — no phase structure visible"
     source: "dev/archive/ansuz/legacy/phases/phase_0.yaml → actions[Tier 3b]"
 
@@ -44,12 +44,12 @@ rules:
     title: "Observable markers are evaluated at Phase 9 cognitive checkpoint"
     rule: |
       During Phase 9 cognitive checkpoint, the session MUST evaluate:
-        1. cognitive_checkpoint_compliance (OM-001) — inscribe or explicit skip
+        1. cognitive_checkpoint_compliance (OM-001) — lesson recorded (`kenaz learn add` / native memory) or explicit skip
         2. acceptance_criteria_evaluation (OM-002) — all criteria have status
       These two markers carry 0.45 of the total identity score. Skipping both
       guarantees DRIFT_WARNING even if all other markers pass.
     enforcement: |
-      Phase 9 checklist item: "cognitive_checkpoint 已判斷（inscribe 或明確跳過）"
+      Phase 9 checklist item: "cognitive_checkpoint 已判斷（記錄教訓或明確跳過）"
       and acceptance criteria evaluation in progress note.
     violation: "DI-005 — Phase 9 cognitive checkpoint absent"
     source: "dev/archive/ansuz/legacy/phases/phase_9.yaml → cognitive_checkpoint"
@@ -88,7 +88,7 @@ rules:
       When evaluating identity across model substrates (e.g., Opus 4.6 vs Sonnet 4.6),
       the following differences are acceptable and MUST NOT be flagged as drift:
         - Response verbosity differences
-        - Different Synapse tool choices for equivalent recall
+        - Different tool choices for equivalent lookup
         - Analysis depth differences
         - Phrasing variation in principles
       Identity is evaluated on STRUCTURE (phase discipline, task system, memory usage,

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

@@ -1,10 +1,10 @@
 # .rule/general/synapse-code-intelligence.yaml
-# 代碼導航與記憶規則 — Agent 何時、如何使用 kenaz_lsp_* / Grep / Glob / Synapse 記憶工具
+# 代碼導航規則 — Agent 何時、如何使用 kenaz_lsp_* / Grep / Glob
 # 優先級：此規則凌駕於 CLAUDE.md 和 .claude/skills/ 中的定義
 #
 # TASK_2335（Kuzu replacement W5a）：Synapse 的代碼圖譜（search / context / impact / pulse / map /
 # cypher / trace_route / detect_changes 等）已移除。代碼導航改由 kenaz_lsp_* 工具提供；
-# 文字與概念搜尋用 Grep / Glob；Synapse 只保留記憶層（recall / inscribe / forge / sigils）。
+# 文字與概念搜尋用 Grep / Glob。記憶層（synapse_*）已於 2026-10-11 移除（TASK_2411）。
 # 規則編號 SYN-001~007 保持不變（其他規則與失敗記錄以編號引用）。
 
 _meta:
@@ -23,21 +23,20 @@ rules:
     title: "工具可用性偵測"
     description: |
       每個 session 開始時，偵測 Kenaz MCP 工具是否可用。
-      kenaz_lsp_* 與 synapse_* 都依賴 Dashboard（Rust HTTP server on port 18080），
+      kenaz_lsp_* 依賴 Dashboard（Rust HTTP server on port 18080）；
       Dashboard 沒啟動時，MCP 工具不會出現在工具列表中。
     severity: "must"
 
     detection_method: |
-      使用 ToolSearch 搜尋 "synapse"（記憶工具）與 "kenaz_lsp"（代碼導航工具）：
-        - 找到 synapse_status / synapse_recall → 記憶層可用
+      使用 ToolSearch 搜尋 "kenaz_lsp"（代碼導航工具）：
         - 找到 kenaz_lsp_callers / kenaz_lsp_references → LSP 導航可用
-        - 沒找到 → 對應能力不可用，降級為 Grep/Glob
+        - 沒找到 → 不可用，降級為 Grep/Glob
 
     on_unavailable: |
       該 session 全程使用 Grep/Glob，不再嘗試已確認不可用的工具。
 
     project_path_mandatory: |
-      ⚠️ 所有 kenaz_lsp_* 與 synapse_* MCP 工具呼叫必須明確帶 projectPath 參數。
+      ⚠️ 所有 kenaz_lsp_* MCP 工具呼叫必須明確帶 projectPath 參數。
       Dashboard 的 active project 可能指向其他專案，default project 不可靠。
       - Core 模式：projectPath = 當前工作目錄的絕對路徑
       - 子專案模式：projectPath = 子專案的絕對路徑（從 .kenaz/project.yaml 讀取）
@@ -50,7 +49,7 @@ rules:
     title: "搜尋工具選擇決策樹"
     description: |
       Agent 遇到搜尋 / 導航需求時，按此決策樹選擇工具。
-      原則：文字用 Grep/Glob，符號關係用 LSP，歷史經驗用 synapse_recall。
+      原則：文字用 Grep/Glob，符號關係用 LSP。
     severity: "should"
 
     decision_tree: |
@@ -68,10 +67,6 @@ rules:
       ├── 「這個函數/類在哪裡定義？」 → kenaz_lsp_definition(projectPath, file, line | symbol)
       ├── 「這個檔案有哪些 symbol？」 → kenaz_lsp_symbols(projectPath, file)
       │
-      ├── [歷史經驗 — 需要 Synapse 記憶層可用]
-      │
-      ├── 「這個 symbol / 模組有已知風險或決策嗎？」 → synapse_recall
-      │
       ├── [Bug 調查兩階段]
       │
       ├── Step 1: 定位入口（error log 有精確路徑/URL）→ Grep 找到檔案
@@ -127,27 +122,13 @@ rules:
         use_instead: "Grep (count mode)"
 
   # =============================================================================
-  # SYN-003.5: 記憶查詢語言規則
+  # SYN-003.5: 記憶查詢語言規則（已移除）
+  # synapse_recall/inscribe 已於 2026-10-11 移除（TASK_2411），英文限制不再適用。
   # =============================================================================
   - id: "SYN-003.5"
-    title: "記憶查詢語言規則"
-    description: |
-      Synapse 記憶層的 FTS5 和 embedding 都基於英文。
-      非英文查詢（中文、日文等）必須先翻譯成英文再召回。
-    severity: "must"
-
-    rule: |
-      召回和寫入都必須使用英文：
-
-      召回（synapse_recall）：
-      - 用戶用非英文描述需求時，翻譯成英文再查詢
-      - 例：「怎麼處理終端機的大小調整？」→ query="terminal resize fit columns rows"
-
-      寫入（synapse_inscribe / synapse_forge）：
-      - Rune content 必須用英文撰寫
-      - Sigil name 和 abstract 必須用英文
-      - 原因：recall 用英文搜尋，中文 content 永遠搜不到
-      - 例：「加入 WAL 修復鎖定問題」→ content="Added WAL + busy_timeout to fix exclusive lock blocking reads"
+    title: "記憶查詢語言規則（已移除）"
+    description: "Synapse 記憶工具已移除；此條不再適用。"
+    severity: "may"
 
   # =============================================================================
   # SYN-004: kenaz_lsp_* 參數指南
@@ -222,24 +203,20 @@ rules:
 
       refactoring: |
         重構前評估：
-        kenaz_lsp_references → kenaz_lsp_callers → synapse_recall
+        kenaz_lsp_references → kenaz_lsp_callers
         1. kenaz_lsp_references 看改動的 blast radius
         2. kenaz_lsp_callers 看跨模組呼叫者
-        3. synapse_recall 查已知風險
 
       pre_task: |
         開發任務前的標準動作：
-        synapse_status → synapse_recall → Grep/Glob → kenaz_lsp_*
-        1. synapse_status 檢查記憶層狀態
-        2. synapse_recall 查詢歷史 rune 知識（有沒有已知的 risk/decision 需要注意）
-        3. Grep/Glob 找相關實現和型別定義
-        4. 修改既有 symbol 前用 kenaz_lsp_references / kenaz_lsp_callers 看影響範圍
+        Grep/Glob → kenaz_lsp_*
+        1. Grep/Glob 找相關實現和型別定義
+        2. 修改既有 symbol 前用 kenaz_lsp_references / kenaz_lsp_callers 看影響範圍
 
       pre_code_analysis: |
         寫代碼前的分析（修改既有 symbol 時）：
-        1. synapse_recall(symbol 或模組關鍵字) → 已知 risk / decision / fix
-        2. kenaz_lsp_references(symbol) → 爆炸半徑
-        3. kenaz_lsp_callers(symbol, depth=2) → 跨模組呼叫者
+        1. kenaz_lsp_references(symbol) → 爆炸半徑
+        2. kenaz_lsp_callers(symbol, depth=2) → 跨模組呼叫者
         禁止盲寫 — 修改非 trivial symbol 前不看影響範圍是被禁止的行為（FAIL-009）。
 
       red_flags: |
@@ -261,88 +238,29 @@ rules:
           reality: "爆炸半徑由引用關係決定，不由你的直覺決定。一行改動可以跨三個模組邊界。"
 
       post_code: |
-        寫代碼後的驗證和認知更新：
+        寫代碼後的驗證：
         1. git diff 確認實際改了哪些 symbol
         2. 對每個改動的公開 symbol → kenaz_lsp_references 檢查是否有漏改的呼叫端
-        3. 如有 non-obvious 發現 → synapse_inscribe 留給下一個 agent
+        3. 如有 non-obvious 發現 → `kenaz learn add` 或原生記憶檔留給下一個 agent
 
-      post_task: |
-        任務完成後的認知層更新（選擇性）：
-        synapse_inscribe / synapse_forge
-        判斷標準：「這個發現，未來 agent 在同 symbol 附近工作時需要知道嗎？」
-        YES → synapse_inscribe（單 symbol 標註）或 synapse_forge（跨 symbol 概念）
-        NO  → 跳過，不要為了寫而寫
 
     tool_summary:
       kenaz_lsp_callers: "誰呼叫這個 symbol（支援 depth 遞迴）"
       kenaz_lsp_references: "所有引用位置 — 修改影響範圍"
       kenaz_lsp_definition: "定義位置"
       kenaz_lsp_symbols: "檔案內 symbol 列表"
-      synapse_status: "檢查記憶層狀態"
-      synapse_recall: "FTS5 召回 runes + sigils，按 confidence × recency 排序（認知層歷史知識）"
-      synapse_inscribe: "對 symbol 寫入 Rune 知識標註（insight/decision/fix/pattern/risk/summary）。supersedes 參數可取代舊 rune"
-      synapse_forge: "建立/更新 Sigil 跨 symbol 概念節點（永久，同名 upsert）"
-      synapse_sigils: "瀏覽所有 Sigil 概念圖，expand=true 附 symbol 摘要"
 
   # =============================================================================
-  # SYN-007: 認知層工具使用規則
+  # SYN-007: 認知層工具（已移除）
   # =============================================================================
   - id: "SYN-007"
-    title: "認知層工具使用規則"
+    title: "認知層工具已移除"
     description: |
-      記憶層工具（synapse_recall / synapse_inscribe / synapse_forge / synapse_sigils）
-      的使用時機和紀律。這些工具操作 memory.db（獨立 SQLite）。
+      synapse_recall / inscribe / forge / sigils 等記憶層 MCP 工具已於 2026-10-11 移除（TASK_2411），
+      呼叫會得到 Unknown tool。教訓寫入 `kenaz learn add` 或 Claude 原生記憶檔（含 triggers: frontmatter）；
+      歷史知識用 Grep / 讀碼 / `kenaz learn list` 查。
     severity: "should"
 
-    recall_triggers:
-      description: "以下情況應呼叫 synapse_recall 查詢歷史知識"
-      must_recall:
-        - trigger: "任務開始，scope_paths 涉及已有 symbol"
-          query_hint: "用 scope_paths 中的關鍵詞搜尋"
-          purpose: "確認有無已知 risk、design decision、已修復的 bug pattern"
-        - trigger: "遇到陌生或複雜的函數/模組"
-          query_hint: "用 symbol 名稱或功能描述搜尋"
-          purpose: "Agent 之前可能已留下 insight"
-        - trigger: "debug 過程中懷疑有類似歷史問題"
-          query_hint: "用錯誤特徵或受影響模組搜尋"
-          purpose: "避免重複排查已知問題"
-      skip_recall_when:
-        - "memory.db 尚無任何資料（全新系統，尚未有 agent inscribe）"
-        - "任務是全新功能，與現有 symbol 無交集"
-        - "明確知道沒有相關 rune（之前剛查過）"
-
-    inscribe_triggers:
-      description: "任務完成後，判斷是否值得留下 Rune"
-      write_rune_when:
-        - "發現 non-obvious 的 bug pattern 或 side-effect"
-        - "做出影響後續開發的架構決策"
-        - "修復了容易再次出現的問題（type=fix）"
-        - "發現模組有使用限制或已知風險（type=risk）"
-      do_not_write_when:
-        - "只是執行了標準流程，沒有新發現"
-        - "重複 docstring 或 code 中已說明的事"
-        - "confidence < 0.6（系統會拒絕）"
-        - "一般任務執行步驟（用 task log 記錄）"
-      symbol_id_format: "file_path:name:kind（例：src/synapse/memory.rs:inscribe_rune:function）"
-      related_rune_ids: |
-        SYN-012（強制）：inscribe 時回溯本 session 先前 recall 過的 rune，將相關 rune_id 傳入
-        related_rune_ids 參數，閉合 recall → acted_on → confidence_boost 學習迴路。
-
-    forge_triggers:
-      description: "識別出跨 symbol 的語義抽象時呼叫 synapse_forge"
-      write_sigil_when:
-        - "多個 symbol 共同構成一個有名字的概念（如 payment_flow、auth_pipeline）"
-        - "發現一個重要的 anti_pattern 跨越多個模組"
-      note: "Sigil 是稀缺的，比 Rune 更需要謹慎。一個 Sigil 代表整個系統的一個認知單元"
-
-    conflict_resolution:
-      description: "當新發現與已有 Rune 衝突時的處理流程"
-      supersede_flow:
-        - "recall 撈出舊 rune → 發現內容過時或錯誤"
-        - "synapse_inscribe({ ..., supersedes: '<舊rune_id>' }) → 舊 rune 被標記 superseded_by，recall 自動排除"
-        - "新 rune 取代舊 rune 成為 active 知識"
-      rule: "不要留下矛盾的 rune 並存 — 用 supersedes 取代；檢查矛盾用 synapse_rune_conflicts，過時檢查用 synapse_scan_stale_runes"
-
 # =============================================================================
 # 快速參考
 # =============================================================================
@@ -361,10 +279,6 @@ quick_reference:
   kenaz_lsp_symbols:
     best_for: "不讀完整檔案就了解其結構"
 
-  synapse_recall:
-    strength: "歷史 rune / sigil 召回，按 confidence × recency 排序"
-    best_for: "修改前確認有無已知 risk / decision / fix"
-
   grep:
     strength: "精確匹配、正則、速度快、無依賴"
     weakness: "不理解語意、結果無排序"

package/core/.rule/general/worktree-isolation.yaml

@@ -43,8 +43,8 @@ rules:
         description: |
           ALL Edit/Read/Write operations MUST use the worktree path as prefix.
           Example: if pwd returns /c/.../KenazAI/.claude/worktrees/agent-abc/,
-          then reading dashboard/src/app/page.tsx uses:
-          /c/.../KenazAI/.claude/worktrees/agent-abc/dashboard/src/app/page.tsx
+          then reading packages/kenaz/lib/cli.js uses:
+          /c/.../KenazAI/.claude/worktrees/agent-abc/packages/kenaz/lib/cli.js
         severity: "must"
 
       - id: "WT-001-C"

package/core/.rule/pipeline/task-execution.yaml

@@ -248,15 +248,12 @@ rules:
 
       === Agent 傳遞測試指令 ===
       post-complete.js --task=TASK_XXX \
-        --test-cmd "cd dashboard && npm test -- --passWithNoTests" \
-        --test-cmd "cd dashboard/pty-server && cargo test"
+        --test-cmd "node dev/scripts/rust-verify-worktree.js run <branch> <filter>"
 
       如果 Agent 未傳 --test-cmd，腳本 fallback 到自動偵測所有可用測試套件。
 
       === Agent 測試判斷指引 ===
-      - 修改 dashboard/src/ (React/TS) → --test-cmd "cd dashboard && npm test -- --passWithNoTests"
-      - 修改 dashboard/src-tauri/ (Rust) → --test-cmd "cd dashboard/src-tauri && cargo test"
-      - 修改 dashboard/pty-server/ (Rust) → --test-cmd "cd dashboard/pty-server && cargo test"
+      - 修改 dashboard/src-tauri/ (Rust, kenaz-server) → --test-cmd "node dev/scripts/rust-verify-worktree.js run <branch> <filter>"（Dashboard 前端與 pty-server 已於 2026-10-11 移除）
       - 修改 kenaz-cortex/ (Python) → --test-cmd "cd kenaz-cortex && pytest"
       - 只修改 .yaml/.md/設定檔 → --skip-tests（無需測試）
       - 修改多個子系統 → 多個 --test-cmd，分別指定
@@ -278,12 +275,12 @@ rules:
       Agent 忘記傳參時，auto-detect fallback 保底。
       防止 Agent 完成 TASK_B 時意外破壞 TASK_A 的功能。
     examples:
-      - scenario: "修改了 React 組件和 Rust PTY server"
+      - scenario: "修改了 kenaz-server 的 Rust 與 plugin 的 JS"
         action: |
-          Agent 判斷：改了 dashboard/src/ 和 dashboard/pty-server/
+          Agent 判斷：改了 dashboard/src-tauri/ 和 plugins/kenaz/scripts/
           → post-complete.js --task=TASK_XXX \
-              --test-cmd "cd dashboard && npm test -- --passWithNoTests" \
-              --test-cmd "cd dashboard/pty-server && cargo test"
+              --test-cmd "node dev/scripts/rust-verify-worktree.js run <branch> peer" \
+              --test-cmd "node --test plugins/kenaz/scripts/kenaz.test.js"
           → 腳本依序跑 2 組測試
           → 全過 → 繼續 PPL-109 commit
       - scenario: "只修改了 Python 後端 API"