kenaz 0.3.9 → 0.3.11

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

@@ -1,246 +0,0 @@
-'use strict';
-/**
- * TASK_2038 — post-complete MCP/HTTP payloads always carry an explicit
- * projectPath, instead of omitting it for a core KenazAI run.
- *
- * Prior bug: every MCP/HTTP payload in the post-complete module family spread
- * `...(projectPath ? { projectPath } : {})`. For a core run, projectPath is
- * undefined (post-complete.js only sets it from --project-path, ~L4016), so
- * the key was OMITTED entirely — the backend then fell back to whatever
- * project the Dashboard currently has selected, not this run's actual
- * project. Local, file-based reads in the same modules already resolved
- * `projectPath || ROOT` correctly; only the MCP/HTTP payloads diverged.
- * Measured live (see TASK_2038 dispatch background / rune_ec9ec6c1): 4 of 5
- * recent KEEP/REVERT verdicts were scored against a different repo.
- *
- * Fix: resolveMcpProjectPath(projectPath) in health.js, reused by
- * outcome.js/cognitive.js/post-complete.js, always resolves to
- * `projectPath || ROOT` and is sent explicitly instead of spread.
- *
- * Negative control: with health.js reverted to its pre-fix (HEAD) content,
- * the "measureHealthScoreSync(undefined) sends an explicit projectPath"
- * assertion below fails — the stub server receives an arguments object with
- * no projectPath key at all. See this task's report for the captured output.
- *
- * Run: node --test .formation/tools/post-complete/task2038.test.js
- */
-
-const test = require('node:test');
-const assert = require('node:assert/strict');
-const fs = require('fs');
-const path = require('path');
-const http = require('node:http');
-const vm = require('node:vm');
-const Module = require('node:module');
-
-const { ROOT } = require('../utils');
-const {
-  resolveMcpProjectPath,
-  resolveMcpDashboardPort,
-  triggerGuardianHealthCheck,
-} = require('./health');
-
-/**
- * measureHealthScoreSync spawns a FRESH node process (spawnSync) to make its
- * HTTP call, which cannot reach a stub server created in this same test
- * process on this sandboxed host (verified: the child process's connection
- * attempt to 127.0.0.1 hangs and times out even with sandboxing disabled —
- * an environment limitation, not a defect in the fix). So instead of a real
- * network round-trip, this loads health.js in an isolated vm context with
- * child_process.spawnSync stubbed, and inspects the EXACT inline script text
- * measureHealthScoreSync builds — the same level of proof (does the outgoing
- * MCP arguments object carry an explicit, correctly-resolved projectPath?)
- * without depending on loopback networking working inside a spawned process.
- */
-function loadHealthWithSpawnSyncStub(spawnSyncStub) {
-  const sourcePath = require.resolve('./health');
-  const src = fs.readFileSync(sourcePath, 'utf8');
-  const localRequire = Module.createRequire(sourcePath);
-  const mod = { exports: {} };
-  const ctx = {
-    module: mod,
-    exports: mod.exports,
-    require: (name) => (name === 'child_process' ? { spawnSync: spawnSyncStub } : localRequire(name)),
-    console,
-    process,
-    Buffer,
-    __dirname: path.dirname(sourcePath),
-    __filename: sourcePath,
-  };
-  vm.createContext(ctx);
-  vm.runInContext(src, ctx, { filename: sourcePath });
-  return mod.exports;
-}
-
-async function stubServer(t, handler) {
-  const s = http.createServer(handler);
-  await new Promise((resolve) => s.listen(0, '127.0.0.1', resolve));
-  t.after(() => new Promise((resolve) => { s.closeAllConnections(); s.close(resolve); }));
-  return s.address().port;
-}
-
-async function withEnv(key, value, fn) {
-  const had = Object.prototype.hasOwnProperty.call(process.env, key);
-  const prev = process.env[key];
-  process.env[key] = value;
-  try {
-    return await fn();
-  } finally {
-    if (had) process.env[key] = prev; else delete process.env[key];
-  }
-}
-
-function writeSynapseHealthResponse(res) {
-  const body = JSON.stringify({
-    jsonrpc: '2.0',
-    id: 'hc-sync',
-    result: { content: [{ type: 'text', text: JSON.stringify({ overall_score: 90, grade: 'A', metrics: {} }) }] },
-  });
-  res.writeHead(200, { 'Content-Type': 'application/json' });
-  res.end(body);
-}
-
-function readJsonBody(req) {
-  return new Promise((resolve, reject) => {
-    let raw = '';
-    req.on('data', (c) => { raw += c; });
-    req.on('end', () => {
-      try { resolve(JSON.parse(raw)); } catch (e) { reject(e); }
-    });
-    req.on('error', reject);
-  });
-}
-
-// ── resolveMcpProjectPath ───────────────────────────────────────────────
-
-test('resolveMcpProjectPath falls back to ROOT for every falsy input, passes through an explicit path', () => {
-  assert.equal(resolveMcpProjectPath(undefined), ROOT);
-  assert.equal(resolveMcpProjectPath(null), ROOT);
-  assert.equal(resolveMcpProjectPath(''), ROOT);
-  assert.equal(resolveMcpProjectPath('/fixture/project'), '/fixture/project');
-});
-
-test('resolveMcpDashboardPort defaults to 18080, honors KENAZ_DASHBOARD_PORT override', async () => {
-  assert.equal(resolveMcpDashboardPort(), 18080);
-  await withEnv('KENAZ_DASHBOARD_PORT', '54321', () => {
-    assert.equal(resolveMcpDashboardPort(), 54321);
-  });
-  await withEnv('KENAZ_DASHBOARD_PORT', 'not-a-number', () => {
-    assert.equal(resolveMcpDashboardPort(), 18080);
-  });
-});
-
-// ── measureHealthScoreSync (TASK_1861 KENAZ_DASHBOARD_PORT seam) ────────
-
-function extractSpawnedScript(capturedArgs) {
-  assert.ok(capturedArgs, 'spawnSync must have been called');
-  assert.equal(capturedArgs[1][0], '-e');
-  return capturedArgs[1][1];
-}
-
-test('measureHealthScoreSync(undefined) builds an MCP script that sends an explicit projectPath === ROOT (negative control: fails on pre-fix code — see report)', () => {
-  let capturedArgs = null;
-  const health = loadHealthWithSpawnSyncStub((...args) => {
-    capturedArgs = args;
-    return { stdout: JSON.stringify({ score: 90, grade: 'A' }), stderr: '' };
-  });
-
-  const result = health.measureHealthScoreSync(undefined);
-  // Cross-realm result (JSON.parse ran inside the vm context) -- compare
-  // fields directly rather than deepEqual, which fails on prototype identity
-  // across realms even when the data matches.
-  assert.equal(result.score, 90);
-  assert.equal(result.grade, 'A');
-
-  const script = extractSpawnedScript(capturedArgs);
-  const ppMatch = script.match(/const pp = (.+);/);
-  assert.ok(ppMatch, 'script must define `pp`');
-  const ppValue = JSON.parse(ppMatch[1]);
-  assert.equal(ppValue, ROOT,
-    'measureHealthScoreSync(undefined) must resolve pp to ROOT, not omit it (pre-fix code sets pp = null here)');
-  assert.match(script, /arguments: \{ mode: 'score', save_snapshot: true, projectPath: pp \}/,
-    'the MCP arguments object must send projectPath unconditionally, not spread it behind a truthiness check');
-});
-
-test('measureHealthScoreSync(explicitPath) forwards that path unchanged into the MCP script', () => {
-  let capturedArgs = null;
-  const health = loadHealthWithSpawnSyncStub((...args) => {
-    capturedArgs = args;
-    return { stdout: JSON.stringify({ score: 1, grade: 'F' }), stderr: '' };
-  });
-
-  health.measureHealthScoreSync('/fixture/sub-project');
-
-  const script = extractSpawnedScript(capturedArgs);
-  const ppMatch = script.match(/const pp = (.+);/);
-  assert.equal(JSON.parse(ppMatch[1]), '/fixture/sub-project');
-});
-
-test('measureHealthScoreSync honors KENAZ_DASHBOARD_PORT in the spawned script (TASK_1861 seam, unaffected by this fix)', async () => {
-  let capturedArgs = null;
-  const health = loadHealthWithSpawnSyncStub((...args) => {
-    capturedArgs = args;
-    return { stdout: '', stderr: '' };
-  });
-
-  await withEnv('KENAZ_DASHBOARD_PORT', '54329', () => {
-    health.measureHealthScoreSync(undefined);
-  });
-
-  const script = extractSpawnedScript(capturedArgs);
-  assert.match(script, /port: 54329,/);
-});
-
-// ── triggerGuardianHealthCheck (TASK_2038: must honor the same port seam) ──
-
-test('triggerGuardianHealthCheck(undefined) sends explicit projectPath === ROOT and honors KENAZ_DASHBOARD_PORT', async (t) => {
-  let resolveReceived;
-  const receivedPromise = new Promise((resolve) => { resolveReceived = resolve; });
-  const port = await stubServer(t, async (req, res) => {
-    const parsed = await readJsonBody(req);
-    resolveReceived(parsed.params.arguments);
-    writeSynapseHealthResponse(res);
-  });
-
-  await withEnv('KENAZ_DASHBOARD_PORT', String(port), async () => {
-    triggerGuardianHealthCheck(undefined);
-    const args = await Promise.race([
-      receivedPromise,
-      new Promise((_, reject) => setTimeout(
-        () => reject(new Error('stub server on KENAZ_DASHBOARD_PORT never received a request — triggerGuardianHealthCheck may still hardcode port 18080')),
-        5000,
-      )),
-    ]);
-    assert.ok(Object.prototype.hasOwnProperty.call(args, 'projectPath'),
-      'synapse_health arguments must carry a projectPath key, not omit it');
-    assert.equal(args.projectPath, ROOT);
-  });
-});
-
-// ── source assertion: the omitting spread pattern is gone everywhere ────
-
-test('the projectPath-omitting spread pattern no longer appears in post-complete/*.js or post-complete.js', () => {
-  const files = [
-    path.join(__dirname, 'health.js'),
-    path.join(__dirname, 'outcome.js'),
-    path.join(__dirname, 'cognitive.js'),
-    path.join(__dirname, '..', 'post-complete.js'),
-  ];
-  // Matches the exact prior bug shape: `...(projectPath ? { projectPath } : {})`
-  // (with or without spaces inside the braces).
-  const pattern = /\.\.\.\(\s*projectPath\s*\?\s*\{\s*projectPath\s*\}\s*:\s*\{\s*\}\s*\)/;
-
-  for (const file of files) {
-    assert.ok(fs.existsSync(file), `expected file to exist: ${file}`);
-    const src = fs.readFileSync(file, 'utf8');
-    // Drop lines that are JSDoc/comment prose (this test file's own fix
-    // description quotes the old pattern verbatim inside a `/** ... */`
-    // block in health.js) so only executable code is checked.
-    const codeOnly = src
-      .split('\n')
-      .filter((line) => !/^\s*(\*|\/\/|\/\*)/.test(line))
-      .join('\n');
-    assert.doesNotMatch(codeOnly, pattern,
-      `${file} must not conditionally omit projectPath from an MCP/HTTP payload`);
-  }
-});

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

@@ -1,74 +0,0 @@
-'use strict';
-// TASK_2341: the memory-only health score must never revert/block a task, and graph-era snapshots must
-// never be compared with memory-era ones.
-const { test } = require('node:test');
-const assert = require('node:assert/strict');
-const fs = require('fs');
-const os = require('os');
-const path = require('path');
-const health = require('./health');
-
-const GRAPH_ERA_BASELINE = { score: 85, grade: 'B', timestamp: '2026-01-01T00:00:00.000Z', sub_metrics: { degree_entropy: 90, orphan_ratio: 80 } };
-const MEMORY_POST = { score: 40, grade: 'F', score_version: 'memory-v1', sub_metrics: { rune_vitality: 40 }, timestamp: '2026-10-07T00:00:00.000Z' };
-
-test('AC: graph-era baseline 85, new memory score 40 -> verdict is not REVERT, no delta is attributed', () => {
-  const v = health.computeHealthVerdict(GRAPH_ERA_BASELINE, MEMORY_POST, -2, { projectPath: os.tmpdir() });
-  assert.notEqual(v.verdict, 'REVERT');
-  assert.equal(v.verdict, 'RECORDED');
-  assert.equal(v.delta, null, 'graph-era baseline is incomparable with memory-v1');
-  assert.deepEqual(v.subMetricRegressions, []);
-});
-
-test('even a same-version drop (85 -> 40) is only recorded, never REVERT / SUBMETRIC_REGRESSION', () => {
-  const pre = { score: 85, score_version: 'memory-v1', timestamp: '2026-10-06T00:00:00.000Z', sub_metrics: { degree_entropy: 90 } };
-  const v = health.computeHealthVerdict(pre, MEMORY_POST, -2);
-  assert.equal(v.verdict, 'RECORDED');
-  assert.equal(v.delta, -45);
-  assert.deepEqual(v.subMetricRegressions, []);
-});
-
-test('numeric baseline (legacy call shape) is treated as graph-era: no revert, no delta', () => {
-  const v = health.computeHealthVerdict(85, MEMORY_POST, -2);
-  assert.equal(v.verdict, 'RECORDED');
-  assert.equal(v.delta, null);
-});
-
-test('no automatic revert / merge-block path remains for health', () => {
-  const root = path.resolve(__dirname, '..', '..', '..');
-  // comment lines (history notes) are not code paths
-  const isComment = l => /^\s*(\/\/|\*|\/\*)/.test(l);
-  const read = rel => fs.readFileSync(path.join(root, rel), 'utf8').split('\n').filter(l => !isComment(l)).join('\n');
-  const pc = read('.formation/tools/post-complete.js');
-  assert.doesNotMatch(pc, /HEIMDALL_POSTMERGE_REVERT|revert -m|verdict === 'REVERT'/);
-  const gm = read('.formation/tools/post-complete/git-merge.js');
-  assert.doesNotMatch(gm, /healthGateBlock|blockedReason = 'health_gate'|measureHealthScoreSync/);
-  const h = read('.formation/tools/post-complete/health.js');
-  assert.doesNotMatch(h, /verdict = 'REVERT'|SUBMETRIC_REGRESSION'|verdict: 'REVERT'/);
-});
-
-test('snapshots are tagged memory-v1 and graph-era snapshots are excluded from the trend', () => {
-  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'task2341-'));
-  try {
-    const dir = path.join(tmp, '.kenaz', 'health_snapshots');
-    fs.mkdirSync(dir, { recursive: true });
-    fs.writeFileSync(path.join(dir, 'TASK_1_after.json'), JSON.stringify({ score: 90, timestamp: new Date(Date.now() - 5000).toISOString(), sub_metrics: {} }));
-    const payload = health.saveTaskHealthSnapshot('TASK_2', 'after', { score: 40, grade: 'F', sub_metrics: {} }, tmp);
-    assert.equal(payload.score_version, 'memory-v1');
-    assert.equal(payload.delta_from_previous, null, 'graph-era prior (score 90) must not produce a delta');
-    const payload2 = health.saveTaskHealthSnapshot('TASK_3', 'after', { score: 43, grade: 'F', sub_metrics: {} }, tmp);
-    assert.equal(payload2.delta_from_previous, 3);
-    assert.deepEqual(health.loadRecentAfterSnapshots(tmp).map(s => s.taskId).sort(), ['TASK_2', 'TASK_3']);
-  } finally { fs.rmSync(tmp, { recursive: true, force: true }); }
-});
-
-test('writeVerdictToTask note carries delta n/a for an incomparable baseline (source check)', () => {
-  const src = fs.readFileSync(path.join(__dirname, 'health.js'), 'utf8');
-  assert.match(src, /deltaText = typeof delta === 'number' \? delta\.toFixed\(2\) : 'n\/a'/);
-});
-
-test('cognitive.js no longer exports callers of the removed link-cognitive route and still loads', () => {
-  const cog = require('./cognitive');
-  assert.equal(cog.linkCognitiveEdgeHttp, undefined);
-  assert.equal(cog.performCognitiveAttribution, undefined);
-  for (const k of ['callHippocampusMcpSync', 'triggerPassiveRuneExtraction', 'collectThinkingTags']) assert.equal(typeof cog[k], 'function', k);
-});

package/core/.rule/general/cortex-tools.yaml

@@ -1,181 +0,0 @@
-# .rule/general/cortex-tools.yaml
-# Cortex 跨專案智能規則 — Agent 何時、如何使用 Cortex MCP 工具
-# 優先級：此規則凌駕於 CLAUDE.md 和 .claude/skills/ 中的定義
-# 與 synapse-code-intelligence.yaml 互補：Synapse = 當前專案，Cortex = 跨專案
-
-_meta:
-  category: "general"
-  priority: 1
-  applies_to:
-    - "ai_agent"
-  last_updated: "2026-03-15"
-
-rules:
-  # =============================================================================
-  # COR-001: Cortex 可用性偵測
-  # =============================================================================
-  - id: "COR-001"
-    title: "Cortex 可用性偵測"
-    description: |
-      Cortex 與 Synapse 共用 Dashboard MCP server。
-      SYN-001 偵測到 Synapse 可用時，Cortex 同時可用。
-    severity: "should"
-
-    detection_method: |
-      ToolSearch 搜尋 "cortex"：
-        - 找到 cortex_status / cortex_search / cortex_recall → Cortex 可用
-        - 沒找到 → Cortex 不可用，跨專案查詢降級為手動（僅限當前專案 Synapse）
-
-    on_available: "Synapse + Cortex: ON"
-    on_unavailable: "Cortex: OFF — 跨專案功能不可用"
-
-  # =============================================================================
-  # COR-002: Cortex 工具選擇決策樹
-  # =============================================================================
-  - id: "COR-002"
-    title: "Cortex vs Synapse 選擇決策樹"
-    description: |
-      Synapse 搜尋當前專案，Cortex 搜尋所有已註冊專案。
-      預設用 Synapse，只有明確跨專案需求時才用 Cortex。
-    severity: "should"
-
-    decision_tree: |
-      搜尋需求
-      │
-      ├── 當前專案內的代碼/symbol？ → kenaz_lsp_*（符號關係）/ Grep（文字）
-      │
-      ├── [以下用 Cortex]
-      │
-      ├── 「其他專案怎麼處理這個問題？」→ cortex_search(query=..., exclude_current=true)
-      ├── 「有沒有跨專案的共通模式？」→ cortex_search(query=...)
-      ├── 「這個概念在哪些專案出現？」→ cortex_relate(concept_name=...)
-      ├── 「跨專案的歷史知識（Rune/Sigil）？」→ cortex_recall(query=...)
-      ├── 「全局概念圖概覽？」→ cortex_overview
-      ├── 「跨專案的模組/概念關係？」→ cortex_cypher(query=...)
-      │
-      └── 不確定 → 先用 Synapse，結果不足再用 Cortex 補充
-
-  # =============================================================================
-  # COR-003: Cortex 使用場景
-  # =============================================================================
-  - id: "COR-003"
-    title: "Cortex 使用場景"
-    description: |
-      定義何時使用 Cortex 跨專案工具。
-    severity: "should"
-
-    use_cortex:
-      - trigger: "跨專案語義搜尋"
-        tool: "cortex_search"
-        description: "在所有已註冊專案中搜尋相似代碼、模式或實現"
-        example: "cortex_search(query='authentication middleware', exclude_current=true)"
-        best_for: "找其他專案的參考實現、避免重複造輪子"
-
-      - trigger: "跨專案認知回憶"
-        tool: "cortex_recall"
-        description: "搜尋所有專案的 Rune 和 Sigil 歷史知識"
-        example: "cortex_recall(query='database connection pool')"
-        best_for: "查歷史決策、已知風險、跨專案的經驗教訓"
-
-      - trigger: "概念關聯查詢"
-        tool: "cortex_relate"
-        description: "查詢一個概念在哪些專案/模組中出現"
-        example: "cortex_relate(concept_name='Authentication')"
-        best_for: "架構決策時了解概念的跨專案分布"
-
-      - trigger: "全局概覽"
-        tool: "cortex_overview"
-        description: "Meta Graph 的 Project/Module/Concept 統計和 top concepts"
-        best_for: "快速了解跨專案知識圖譜"
-
-      - trigger: "複雜跨專案圖查詢"
-        tool: "cortex_cypher"
-        description: "直接用 Cypher 查詢 Meta Graph（Project, Module, Concept 及其關係）"
-        example: "cortex_cypher(query=\"MATCH (c:Concept) RETURN c.name, c.role ORDER BY c.name\")"
-        best_for: "模組相似度分析、跨專案概念網路、共享概念發現"
-
-    do_not_use_cortex:
-      - "當前專案內的代碼搜尋 → 用 kenaz_lsp_* / Grep"
-      - "精確字串/正則搜尋 → 用 Grep"
-      - "單一專案的 symbol 關係 → 用 kenaz_lsp_callers / kenaz_lsp_references"
-
-  # =============================================================================
-  # COR-004: Cortex 工具鏈使用流程
-  # =============================================================================
-  - id: "COR-004"
-    title: "Cortex 工具鏈使用流程"
-    severity: "should"
-
-    recommended_flows:
-      architecture_decision: |
-        架構決策前的跨專案調研：
-        cortex_overview → cortex_relate → cortex_search
-        1. cortex_overview 了解全局概念圖
-        2. cortex_relate 查詢目標概念在哪些專案/模組出現
-        3. cortex_search 找具體實現作為參考
-
-      reuse_discovery: |
-        尋找可複用實現：
-        cortex_search → cortex_relate → Grep
-        1. cortex_search(exclude_current=true) 找其他專案的相似實現
-        2. cortex_relate 確認概念層面的關聯
-        3. Grep 在當前專案確認是否已有類似實現
-
-      historical_knowledge: |
-        查詢歷史經驗：
-        cortex_recall → synapse_recall
-        1. cortex_recall 查跨專案歷史（所有專案的 Rune/Sigil）
-        2. synapse_recall 查當前專案的具體 symbol 知識
-
-    tool_summary:
-      cortex_status: "跨專案數據概覽（每個專案的 Synapse/memory 可用性、Rune/Sigil 計數）"
-      cortex_recall_contract: |
-        Propagation contract (TASK_1034):
-          1. synapse_inscribe(projectPath=X) writes to project X's memory.db.
-          2. The inscribe path triggers trigger_auto_sync (cortex/sync.rs) which
-             upserts the rune into ~/.kenaz/cortex/global_memory.db.
-          3. cortex_recall runs sync_all() on every invocation as a safety net,
-             so a freshly inscribed rune should be visible within the same call.
-          4. Timing budget: inscribe → cortex_recall visibility must be < 10s.
-             If longer, investigate sync.rs trigger_auto_sync path.
-        Query semantics:
-          - Queries are sanitized and tokens are joined with " OR " by default
-            (MatchMode::Any). Natural-language queries with extra keywords still
-            match runes whose content covers a subset of the tokens.
-          - Pass match_mode="all" (or "and") to force strict AND intersection
-            when you need every token to appear. Pass match_mode="any" (or "or")
-            to be explicit about the default.
-          - BM25 rank is folded into scoring so better lexical matches rank
-            higher (mirrors synapse recall TASK_1029).
-          - SQLite FTS5 uses 'porter unicode61' tokenization: case-insensitive,
-            underscore-separated tokens split (e.g. "generate_ddx" →
-            "generate" + "ddx"). CJK characters are not tokenized — use
-            English content (see MEM-LANG-001).
-      cortex_sync: "手動觸發全局記憶同步（從各專案的 memory.db 匯入 global_memory.db）"
-      cortex_search: "跨專案語義搜尋（embedding similarity，結果含 project_name）"
-      cortex_recall: "跨專案認知回憶（FTS5 搜尋所有專案的 Rune + Sigil）"
-      cortex_relate: "概念→專案/模組映射（Concept → BELONGS_TO → Module → HAS_MODULE → Project）"
-      cortex_overview: "Meta Graph 全局概覽（節點/關係計數 + top concepts）"
-      cortex_cypher: "Meta Graph Cypher 查詢（Project, Module, Concept, HAS_MODULE, SIMILAR_TO, RELATES_TO, BELONGS_TO）"
-
-# =============================================================================
-# 快速參考
-# =============================================================================
-quick_reference:
-  cortex_search:
-    strength: "跨專案語義搜尋、找其他專案的參考實現"
-    weakness: "需要各專案已 Synapse 索引"
-    best_for: "避免重複造輪子、架構決策參考"
-
-  cortex_recall:
-    strength: "跨專案歷史知識回憶、Rune/Sigil 搜尋"
-    best_for: "查歷史決策、已知風險、跨專案經驗"
-
-  cortex_relate:
-    strength: "概念→專案/模組的完整映射"
-    best_for: "了解概念跨專案分布、架構視角分析"
-
-  cortex_cypher:
-    strength: "任意 Meta Graph 查詢"
-    weakness: "需了解 Meta Graph schema（Project, Module, Concept）"
-    best_for: "模組相似度、共享概念、跨專案耦合分析"

package/core/.rule/general/memory-language.yaml

@@ -1,67 +0,0 @@
-# .rule/general/memory-language.yaml
-# Memory Language Constraint — All agent memory write operations must use English
-# Priority: This rule applies to all agents using Synapse and Hippocampus memory tools.
-# Root cause: SQLite unicode61 FTS5 tokenizer does not properly tokenize CJK characters
-# (e.g., 限制 → 限 + 制), making multi-char CJK term queries unreliable. Agent-level
-# constraint is more robust and consistent than patching the tokenizer.
-
-_meta:
-  category: "general"
-  priority: 1
-  applies_to:
-    - "ai_agent"
-  last_updated: "2026-03-21"
-
-rules:
-  # =============================================================================
-  # MEM-LANG-001: English-Only Memory Write Operations
-  # =============================================================================
-  - id: "MEM-LANG-001"
-    title: "English-only for all agent memory write operations"
-    description: |
-      All agent memory write operations must use English for searchable content fields.
-      Root cause: SQLite unicode61 FTS5 tokenizer does not properly tokenize CJK
-      characters, making Chinese queries return 0 results from episode_recall and
-      synapse_recall. Agent-level enforcement is more robust than patching FTS5.
-    severity: "must"
-
-    scope:
-      enforce_english:
-        synapse_inscribe:
-          - "content field"
-          - "context field"
-        hippocampus_episode_start:
-          - "scope field"
-          - "lesson field"
-        hippocampus_episode_append:
-          - "content field"
-        hippocampus_episode_close:
-          - "summary field"
-          - "lesson field"
-
-      allowed_chinese:
-        - "task titles (TASK_XXX.yaml title field)"
-        - "user-facing output (responses visible to the user)"
-        - "code content (preserve source code as-is, including comments)"
-        - "task descriptions and acceptance criteria"
-
-    rationale: |
-      SQLite unicode61 tokenizer splits CJK characters individually:
-        "KuzuDB UNION ALL 限制" → tokens: [kuzu, db, union, all, 限, 制]
-      A query for "限制" (two chars) fails to match because no single token equals "限制".
-      Writing memory content in English avoids this tokenization problem entirely.
-
-    enforcement: |
-      Before calling any memory write tool, translate content/summary/lesson/scope fields
-      to English. Code snippets, file paths, and symbol names may remain in their original
-      form. Task titles and user-facing output are NOT affected by this rule.
-
-    examples:
-      - wrong: |
-          synapse_inscribe(content="KuzuDB UNION ALL 有已知限制：子查詢不支援")
-        correct: |
-          synapse_inscribe(content="KuzuDB UNION ALL has known limitation: subqueries not supported")
-      - wrong: |
-          hippocampus_episode_close(summary="修復了 kuzu destructor crash 問題")
-        correct: |
-          hippocampus_episode_close(summary="Fixed kuzu destructor crash in cleanup path")