kenaz 0.3.11 → 0.3.13

package/core/.specialist/tools/rea-detect.js

@@ -13,6 +13,9 @@ const os = require('os');
 const path = require('path');
 
 const SETUP_CMD = 'npx rea-agents setup';
+// Run without a terminal (an agent running it), setup has no client picked and installs nothing
+// (field report 2026-10-11: plannedActions []), so the suggestion names the clients explicitly.
+const setupCmd = (clients) => (clients.length ? `${SETUP_CMD} ${clients.map((c) => `--client ${c}`).join(' ')} --yes` : SETUP_CMD);
 const DECLINE_FILE = path.join('.kenaz', 'rea.json');
 
 const readJson = (f) => { try { return JSON.parse(fs.readFileSync(f, 'utf8')); } catch (_) { return null; } };
@@ -35,7 +38,8 @@ function detectRea({ home = os.homedir(), projectPath = process.cwd(), env = pro
   const codexHome = env.CODEX_HOME || path.join(home, '.codex');
   const codex = /^\s*\[mcp_servers\.rea\]\s*$/m.test(readText(path.join(codexHome, 'config.toml')));
   const declined = !!(readJson(path.join(projectPath, DECLINE_FILE)) || {}).declined;
-  return { claude, codex, installed: claude || codex, declined, nodeOk: reaNodeOk(env.KENAZ_REA_NODE_VERSION || process.versions.node) };
+  const clients = [fs.existsSync(path.join(home, '.claude.json')) && 'claude_code', fs.existsSync(codexHome) && 'codex'].filter(Boolean);
+  return { claude, codex, installed: claude || codex, setupCmd: setupCmd(clients), declined, nodeOk: reaNodeOk(env.KENAZ_REA_NODE_VERSION || process.versions.node) };
 }
 
 /** One banner line, or null when the user declined in this project. */
@@ -46,7 +50,7 @@ function reaBannerLine(d) {
   }
   if (d.declined) return null;
   const node = d.nodeOk ? '' : `; needs Node >=22.19/24.11 (found ${process.versions.node}), upgrade Node first`;
-  return `[rea] not installed: when the user names a reference product, suggest once \`${SETUP_CMD}\`${node}; on "no" run node "${__filename}" decline (RULES.md "REA")`;
+  return `[rea] not installed: when the user names a reference product, suggest once \`${d.setupCmd || SETUP_CMD}\` (the user runs it in their terminal, then restarts the agent)${node}; on "no" run node "${__filename}" decline (RULES.md "REA")`;
 }
 
 function decline(projectPath) {

package/core/.synapse/memory-shared.json.sync

@@ -0,0 +1 @@
+9514604:1791570255334075800

package/core/KENAZ_CORE_VERSION

@@ -1 +1 @@
-0.3.11
+0.3.13

package/core/dev/plans/CLI_FIRST_INSTALL_FLOW.md

@@ -1,154 +1,120 @@
-# CLI-first install and first-run flow (TASK_2367)
+# CLI-first 安裝與首次使用流程（TASK_2367 / TASK_2376）
 
-Status: DRAFT for user review. Target flow: install once -> `claude` in the project folder -> `/kenaz init` -> `/Ansuz`.
-Yggdrasil via `/kenaz ygg join`, Alaya via `k-cli alaya register` (device code), Dashboard only for viewing.
+狀態：**待用戶審閱**（2026-10-11 改寫為中文並更新到現況）。
+目標流程：`npx kenaz install` 一次 → 在專案資料夾開 `claude` → `/kenaz init` → `/kenaz:Ansuz`。
+Yggdrasil 用 `kenaz ygg create` / `kenaz ygg join <key>`；Alaya 用 `kenaz alaya register`（機碼註冊，不需登入）。Dashboard 已退役。
 
-## 1. Pieces and where they live
+## 1. 組成與位置
 
-| Piece | What | Location |
+| 元件 | 是什麼 | 位置 |
 |---|---|---|
-| kenaz-server | headless backend (loopback, port 18080 with fallback), MCP + HTTP | binary `kenaz-server[.exe]` (cargo `--no-default-features --features server`) |
-| kenaz-core | plugins, hooks, scripts, rules the plugin and server read | dir holding `plugins/kenaz`; the server reads tasks via `KENAZ_SOURCE_DIR=<kenaz-core>` |
-| kenaz plugin | `/kenaz` command + hooks | `<kenaz-core>/plugins/kenaz` |
-| installer | `node dashboard/scripts/install-kenaz-cli.js install\|uninstall\|status` | this card |
-| user state | service launcher, logs, `~/.kenaz/` | per-user home |
-| project state | `.kenaz/` in each project | never touched by uninstall |
+| npm `kenaz` | CLI（install / uninstall / status / doctor / init / ygg / alaya / subagent / launch / stats / learn）＋打包好的 kenaz-core | `npx kenaz ...` |
+| `@kenazai/server-<os>-<cpu>` | kenaz-server 執行檔（無視窗後端：MCP + HTTP，只聽本機，port 18080，被占用時往後找） | 安裝後在 `~/.kenaz/bin/` |
+| kenaz-core | plugin、hooks、腳本、規則（plugin 與 server 都讀它） | 安裝後在 `~/.kenaz/core/` |
+| kenaz plugin | `/kenaz` 指令、`/kenaz:Ansuz` 與 hooks | `~/.kenaz/core/plugins/kenaz` |
+| 使用者層資料 | 服務啟動器、log、專案清單、憑證、教訓（`~/.kenaz/knowledge`） | `~/.kenaz/` |
+| 專案資料 | 任務、日誌、專案設定 | 每個專案的 `.kenaz/`，**解除安裝永遠不動** |
 
-kenaz-core location: the repo root in dev/mother installs; otherwise the bundled `kenaz-core` next to the binary (same candidates the Rust `peer_mod::resolve_plugin_dir` uses). Installer: `--core-dir`, else `KENAZ_CORE_DIR`, else the repo root of the script. Binary: `--server-bin`, else `<core>/../kenaz-server`, `<core>/bin/`, `dashboard/src-tauri/target/release/`, `~/.kenaz/bin/`.
+## 2. 以服務方式執行的東西
 
-## 2. What runs as a service
+只有 `kenaz-server`：每個使用者一份（不需系統管理員、不是系統服務），登入時啟動，只聽本機。
 
-Only `kenaz-server`, per user (no admin, no system service), started at logon, loopback only. The installer writes a launcher/unit and starts it.
-
-| OS | Mechanism | Files |
+| 作業系統 | 方式 | 檔案 |
 |---|---|---|
-| Windows (implemented, real) | per-user Scheduled Task `KenazServer`, trigger at logon, runs `wscript.exe ~\.kenaz\kenaz-server.vbs` (hidden window, sets `KENAZ_SOURCE_DIR`). If `schtasks /Create` is refused (ONLOGON may need elevation) falls back to a `KenazServer.vbs` in the user Startup folder and starts it now | `~\.kenaz\kenaz-server.vbs` |
-| macOS (template written, untested) | launchd user agent `ai.kenaz.server`, RunAtLoad + KeepAlive, `launchctl load -w` | `~/Library/LaunchAgents/ai.kenaz.server.plist` |
-| Linux (template written, untested) | `systemd --user` unit `kenaz-server.service`, `enable --now`; headless boxes need `loginctl enable-linger $USER` | `~/.config/systemd/user/kenaz-server.service` |
-
-Templates are generated by `install-kenaz-cli.js` (`launchdPlist`, `systemdUnit`, `winVbs`) and unit-tested as strings; only Windows is exercised for real.
-
-mcp.json: the server follows the owner rule in `server_boot.rs` (it does not rewrite `~/.claude/mcp.json` when the Dashboard owns it).
+| Windows | 使用者層排程工作 `KenazServer`（登入時觸發，執行隱藏視窗的 `wscript.exe ~\.kenaz\kenaz-server.vbs`）。若 `schtasks /Create` 被拒（登入觸發可能需要管理員權限），改放「啟動」資料夾的 `KenazServer.vbs` 並立即啟動 | `~\.kenaz\kenaz-server.vbs` |
+| macOS | launchd 使用者代理 `ai.kenaz.server`（RunAtLoad + KeepAlive） | `~/Library/LaunchAgents/ai.kenaz.server.plist` |
+| Linux（有 systemd） | `systemd --user` 的 `kenaz-server.service`；無人登入的主機需 `loginctl enable-linger $USER` | `~/.config/systemd/user/kenaz-server.service` |
+| Linux（無 systemd：容器、WSL1、精簡主機）（TASK_2413） | crontab 加一行標記過的 `@reboot`（只取代自己那行，其他保留）並立即在背景啟動；連 crontab 都沒有時，立即啟動並印出要加進開機腳本的指令 | `~/.kenaz/kenaz-server.log` |
 
-## 3. Plugin registration
+`kenaz doctor` 會顯示目前的服務模式（systemd / launchd / windows task / startup launcher / cron / manual）。
 
-Chosen path: `CLAUDE_CODE_PLUGIN_DIRS` in `~/.claude/settings.json` `env`, same as kenaz-peer (proven 2026-10-03). The installer appends `<kenaz-core>/plugins/kenaz`:
-- merge, never replace; idempotent; slash/case-insensitive identity (Windows `;`, else `:` separator)
-- one-time backup `settings.json.bak-kenaz-peer` (same name as Rust, so there is one pristine backup), atomic tmp+rename
-- malformed JSON or odd shape is reported and left untouched
-- gates: `claude --version` >= 2.1.287 (else skipped with a "run `claude update`" message, rerun install afterwards), `KENAZ_SKIP_CLAUDE_PROVISION=1` opt-out, plugin dir must contain `hooks/hooks.json`
+## 3. Plugin 登錄（Claude Code）
 
-Alternative considered: a Claude Code plugin marketplace. Better update story and no settings edit, but needs a published marketplace repo and consent flow; revisit when kenaz-core is distributed publicly. The env-var path needs nothing external.
+在 `~/.claude/settings.json` 的 `env.CLAUDE_CODE_PLUGIN_DIRS` 加入 `~/.kenaz/core/plugins/kenaz`：
+- 只合併、不覆蓋；重複執行結果相同；路徑比對不分斜線方向與大小寫
+- 第一次修改前備份一份 `settings.json.bak-kenaz-peer`，寫入用暫存檔＋改名（不會寫一半）
+- JSON 格式壞掉時只回報、不動它
+- 前提：`claude --version` >= 2.1.287（太舊會跳過並提示 `claude update`）
 
-Unification debt: this duplicates the Rust `features/project/peer_mod.rs` logic in Node (installer must work before any Rust binary runs). Later: have the Rust path register `plugins/kenaz` too (or call a shared CLI subcommand) and drop the Node copy. Both write the same env var and backup, so they coexist.
+Codex：`setup-codex.js` 寫入 `~/.codex/config.toml` 的 MCP 設定、原生 hooks 與 `/prompts:kenaz`。升級時會把舊路徑、舊參數的 kenaz hooks 換成新的（TASK_2418），不動使用者自己的 hooks。
 
-## 4. First run
+## 4. 首次使用
 
-1. `claude` in any folder (plugin auto-loaded, no `--plugin-dir`).
-2. `/kenaz init` creates `.kenaz/project.yaml`, probes `/api/health`, and prints the optional steps and the next step. It does not force them:
-   - Yggdrasil: `/kenaz ygg join <key>` (also `status`, `leave`)
-   - Alaya: `k-cli alaya register` (device code, approve in any browser)
-   - Next: `/Ansuz`
-3. If the backend is down, init says so and points at `install-kenaz-cli.js install`.
+1. 在任何資料夾執行 `claude`（plugin 自動載入，不需 `--plugin-dir`）。
+2. `/kenaz init`：建立 `.kenaz/project.yaml`、確認後端有回應，並列出可選步驟（不強制）：
+   - 團隊協作：`kenaz ygg create`（自建房間金鑰並加入，把金鑰給隊友）或 `kenaz ygg join <key>`
+   - Alaya：`kenaz alaya register`（機碼註冊，立即可用）
+   - 下一步：`/kenaz:Ansuz`
+3. 後端沒回應時，init 會說明並指向 `npx kenaz install`。
 
-## 5. Upgrade and uninstall
+## 5. 升級與解除安裝
 
-- Upgrade: replace kenaz-core and the binary, rerun `install` (idempotent: registration stays "already", launcher is rewritten, task recreated with /F). Stop the old server first on Windows (`schtasks /End /TN KenazServer`) if the binary is locked.
-- Uninstall: `install-kenaz-cli.js uninstall` removes only our entry from `CLAUDE_CODE_PLUGIN_DIRS`, deletes the scheduled task / Startup launcher / plist / unit and the launcher file. Project `.kenaz/` data and `~/.kenaz/` memory data stay. The settings backup stays.
-- `status` reports plugin registration and service state. `--dry-run` prints the plan for any command and changes nothing.
+- **自動更新**：kenaz-server 會從簽章過的 feed 自行更新（執行檔＋kenaz-core＋plugin），重新啟動後生效。
+- **手動升級**：`npx kenaz@latest install`。會先停掉「這個路徑」的舊 server（不會依名稱砍其他程序）、換新檔、**明確重啟服務**，再用 `/api/health` 確認跑的是新版本；版本不符會警告並印出重啟指令（TASK_2418）。
+- **解除安裝**：`npx kenaz uninstall` 只移除我們加的 plugin 項目、服務啟動器與 `~/.kenaz/core`、`~/.kenaz/bin`。**專案的 `.kenaz/` 與 `~/.kenaz` 的使用者資料保留**，settings 備份也保留。
+- `status` 顯示 plugin 登錄與服務狀態；任何指令加 `--dry-run` 只印計畫、不改東西。
 
-## 6. Verification
+## 6. 驗收
 
-Automated (done): `node --test dashboard/scripts/install-kenaz-cli.test.js plugins/kenaz/scripts/kenaz.test.js` (temp home only).
+自動化（已完成）：installer、CLI、Codex hooks 的 node 測試只用暫存 home，不碰真實環境。
 
-Acceptance "clean Windows user profile" is PENDING and must be run by the user:
-1. New Windows user (or VM), install Node and `claude` >= 2.1.287; copy kenaz-core and `kenaz-server.exe`.
-2. `node dashboard\scripts\install-kenaz-cli.js install --dry-run --core-dir <core> --server-bin <exe>` and read the plan.
-3. Rerun without `--dry-run`. Expect: `plugin: added`, scheduled task `KenazServer` (or Startup launcher), server answering `http://127.0.0.1:18080/api/health`.
-4. `mkdir test-proj; cd test-proj; claude` then `/kenaz init`, then `/Ansuz`. Expect Ansuz boots with no `--plugin-dir`.
-5. `... uninstall`. Expect `plugin: removed`, task gone (`schtasks /Query /TN KenazServer` fails), `test-proj\.kenaz` still present.
+**乾淨 Windows 環境實測（待用戶執行，等下一次發版後）**：
+1. 準備乾淨環境：Windows Sandbox（控制台 → 開啟或關閉 Windows 功能 → 勾「Windows 沙箱」→ 重開機），或新建一個本機 Windows 帳號。
+2. 在裡面安裝 Node.js（LTS）與 Claude Code，登入 Claude。
+3. `npx kenaz install`。預期：plugin 已登錄、排程工作或啟動資料夾啟動器、`http://127.0.0.1:18080/api/health` 有回應、最後的版本確認為 ok。
+4. 新建空資料夾 → `claude` → `/kenaz init` → `/kenaz:Ansuz`。預期：Ansuz 正常開機，不需 `--plugin-dir`。
+5. `npx kenaz doctor`：每列應為 ok 或 skip。
+6. `npx kenaz uninstall`。預期：plugin 已移除、服務啟動器已刪、測試資料夾的 `.kenaz` 仍在。
+7. 記下每一步卡住、看不懂、或需要額外動作的地方，回報給 Ansuz。
 
-## 7. Open points
+## 7. 未決事項
 
-- macOS/Linux paths are untested; ONLOGON elevation behaviour on Windows needs the clean-profile run to confirm which branch is taken.
-- Packaging: who ships kenaz-core + binary to `~/.kenaz/bin` (release pipeline, not this card).
-- `k-cli` itself is not yet installed by this script; Alaya registration assumes it is on PATH.
+- macOS 與 Linux 的服務步驟目前只有單元測試，真機只有 Windows 實際跑過（field report 顯示 macOS 用戶已在使用，升級重啟問題已修，待下一版驗證）。
+- Windows 在沒有管理員權限時會走「啟動資料夾」路線；乾淨環境實測要確認實際走哪一條。
+- Codex 桌面版（managed daemon）目前無法即時推送 peer 訊息，改為下一次提問時拉取（TASK_2419，調查記錄見 `dev/specs/peer/CODEX_MANAGED_DAEMON.md`）。
 
-## 8. Decisions (user, 2026-10-09)
-- **Distribution: npm package** - `npx kenaz install` (name `kenaz` is free on npm as of 2026-10-09; publishing needs the user's npm account and explicit OK). Per-platform `kenaz-server` binaries ship as optional platform packages (esbuild pattern: `@kenazai/server-win32-x64`, `-darwin-arm64`, `-darwin-x64`, `-linux-x64`, `-linux-arm64`).
-- **Both harnesses:** the installer detects Claude Code and/or Codex. Claude Code -> plugin registration (this doc, section 3). Codex -> `.formation/bifrost/setup-codex.js` (MCP in ~/.codex/config.toml, native hooks, AGENTS.md).
-- **Platforms: Windows, macOS and Linux in the first release.**
-- **Node.js is a prerequisite** (both harnesses already need it); the installer checks the version and explains how to get it.
-- **Updates: kenaz-server self-updates** (binary + kenaz-core + plugin) from the release feed, with signature verification.
-- **Codex parity with Claude Code:** MCP tools, Yggdrasil commands, Ansuz flow and Codex-native subagent dispatch (TASK_2315).
+## 8. 已定案的決策（用戶，2026-10-09 起）
 
-## 9. npm package `kenaz` (TASK_2377)
+- **發佈：npm**。`npx kenaz install`；各平台執行檔是選用的平台套件（`@kenazai/server-win32-x64`、`-darwin-arm64`、`-darwin-x64`、`-linux-x64`、`-linux-arm64`）。
+- **兩種 harness 都支援**：偵測到 Claude Code 就登錄 plugin，偵測到 Codex 就設定 MCP 與 hooks。
+- **平台**：Windows、macOS、Linux 首版就支援。
+- **Node.js 是前提**（兩種 harness 本來就需要）；installer 會檢查版本並說明怎麼裝。
+- **更新**：kenaz-server 自行更新，有簽章驗證。
+- **Codex 與 Claude Code 對等**：MCP 工具、Yggdrasil 指令、Ansuz 流程、Codex 原生 subagent 派工。
+- **發版**：等用戶說「發版」才發（緊急修正除外）。Windows 與 Linux 在本機建置，只有 macOS 在 GitHub Actions 建置以節省費用（流程見記憶 `reference_npm_cli_release`）。
 
-Layout: `packages/kenaz` (CLI + staged kenaz-core), `packages/server-{win32-x64,darwin-arm64,darwin-x64,linux-x64,linux-arm64}` (`@kenazai/server-*`, `bin/` filled by CI, gitignored). All versions move in lockstep with `dashboard/src-tauri/Cargo.toml`.
+## 9. npm 套件結構（TASK_2377）
 
-- `kenaz install|uninstall|status|doctor [--dry-run] [--home d] [--no-service] [--no-claude] [--no-codex] [--server-bin p]`.
-- install: Node >= 18 check; copy packaged kenaz-core to `~/.kenaz/core` and the platform binary dir to `~/.kenaz/bin`; record `~/.kenaz/install.json`; Claude Code (if `claude` on PATH) via `install-kenaz-cli.js` (both plugins + service); Codex (if `codex` on PATH) via `setup-codex.js` (MCP, native hooks, `/prompts:kenaz`). Neither is reimplemented.
-- uninstall reverses both (`setup-codex.js uninstall()` removes only the MCP entry, shim hook blocks and prompt it added) and deletes core/bin/install.json; project `.kenaz/` is never touched.
-- doctor: node version, core version, server binary, `/api/health` reachable, Claude plugins registered, Codex MCP + hooks. Exit 1 on any FAIL.
-- `prepack` runs `scripts/stage.js`: stages core with the same git-tracked whitelist as the Dashboard bundle (`kenaz-core-staging.js`, ~19 MB) and vendors `install-kenaz-cli.js`.
-- Release: `.gitlab-ci.yml` cross-builds the 5 targets (native runners; darwin-x64 cross-compiled on the M1 runner), packs tarballs as artifacts, `publish` is manual and does not call npm.
-- Local check: `npm pack ./packages/kenaz` etc., install into a prefix, run with `--home <tmp>` (never the real home).
-- Open: the server loads `libonnxruntime` via `ORT_DYLIB_PATH`; CI ships it next to the binary in `bin/`, but the service launchers do not set `ORT_DYLIB_PATH` yet. macOS/Linux service steps and all 5 CI build jobs are unverified until a pipeline/Mac run.
+- `packages/kenaz`：CLI＋打包的 kenaz-core（`prepack` 跑 `scripts/stage.js`，只收 git 追蹤的白名單檔案）。
+- `packages/server-*`：各平台執行檔；版本與 `dashboard/src-tauri/Cargo.toml` 同步。
+- install：檢查 Node 版本 → 複製 kenaz-core 到 `~/.kenaz/core`、執行檔到 `~/.kenaz/bin` → 記錄 `~/.kenaz/install.json` → Claude Code 與 Codex 各自設定 → 啟動並確認服務。
+- doctor：Node 版本、core 版本、server 執行檔、`/api/health`、服務模式、Claude plugin、Codex MCP 與 hooks；任何 FAIL 以代碼 1 結束。
+- 本機檢查：`npm pack` 後裝到暫存前綴，用 `--home <暫存目錄>` 執行（絕不用真實 home）。
 
-## 10. 從 Dashboard 遷移 (TASK_2389)
+## 10. 從 Dashboard 遷移（TASK_2389 / TASK_2396）
 
-範圍：只偵測並提示。CLI 不會結束 Dashboard 行程、不改登錄檔或 Startup 資料夾。原因：`kenaz-server` 與 Dashboard 都綁 port 18080，不能同時執行。
+Dashboard（Tauri 桌面 app）已於 2026-10-11 從 repo 移除，kenaz-server 是唯一後端。已安裝的 Dashboard 可繼續用但不再更新。兩者都綁 port 18080，不能同時執行；CLI 只偵測並提示，不會替你結束 Dashboard。
 
 ### 給使用者的步驟（可直接貼進公告）
 
-1. 在系統匣（右下角）對 Kenaz Dashboard（BLOCK ACTION）按右鍵，選「結束 / Quit」，確認程式完全關閉。
-2. 開啟 Dashboard 設定，關閉「開機時啟動 / Launch at startup」，避免登入後它又佔回 port 18080。
+1. 在系統匣（右下角）對 Kenaz Dashboard 按右鍵，選「結束 / Quit」，確認程式完全關閉。
+2. 開啟 Dashboard 設定，關閉「開機時啟動」，避免登入後它又占回 port 18080。
 3. 在終端機執行：`npx kenaz install`
 4. 到專案資料夾執行 `claude`，再輸入 `/kenaz init`。
 5. 驗證：`npx kenaz doctor`，每一列應為 ok 或 skip。
 
-若 Dashboard 還在執行，`npx kenaz install` 會印出上面的步驟並以非零碼結束，不會啟動服務。只想先裝 plugin 與 core、暫不啟動服務：加 `--keep-dashboard`。
-要改回 Dashboard：從開始選單啟動它，並在設定中重新開啟「開機時啟動」。`kenaz uninstall` 結束時會印出同樣的提示。
+Dashboard 還在執行時，`npx kenaz install` 會印出上面的步驟並結束，不會啟動服務；只想先裝 plugin 與 core：加 `--keep-dashboard`。
 
-### 資料共用，不需搬移（已讀程式確認）
+### 資料共用，不需搬移
 
 | 資料 | 位置 |
 |---|---|
 | 專案清單 | `~/.kenaz/projects.json` |
 | 憑證 / relay key / 各專案 Yggdrasil key | `~/.kenaz/credentials.yaml` |
 | 偏好設定 | `~/.kenaz/config.json` |
-| Synapse 記憶 | `<專案>/.synapse/db/memory.db` |
 | 任務、日誌 | `<專案>/.kenaz/` |
 | Peer 收件匣 | `peer_dir(project_root)/inbox.sqlite` |
 
-只有 Dashboard 自己的 webview、LSP 快取與 `.env.local` 放在 `%LOCALAPPDATA%\Kenaz Dashboard`，CLI 不使用。Dashboard 不寫使用者層級的 hooks，只在啟動時補各專案的 post-commit hook（`hook_installer.rs`），所以不需要 marker 檔。
-
-### doctor 為什麼檢查 plugin 路徑
-
-Dashboard 執行時（`peer_mod.rs`）會重新登錄自己 kenaz-core 內的 `kenaz-peer`；自 TASK_2384 起登錄會取代舊副本，所以重新啟動 Dashboard 會把 `CLAUDE_CODE_PLUGIN_DIRS` 的 `kenaz-peer` 改回它的路徑。`kenaz doctor` 會列出：Dashboard 是否執行 / 已安裝、18080 的持有者、`CLAUDE_CODE_PLUGIN_DIRS` 是否指向 Dashboard 的 core。
+記憶系統（Synapse 等）已於 2026-10-11 移除（TASK_2411），舊的 `.synapse/` 與 `~/.kenaz/cortex/*.db` 留在磁碟上、不再使用；教訓改用 `kenaz learn`。
 
-### Dashboard 退役 (TASK_2396，2026-10-11)
-
-Dashboard（Tauri 桌面 app + Next.js 前端）已從 repo 移除，`kenaz-server` 是唯一後端，`cargo build`（預設 feature `server`）直接產出它。
-
-- 已安裝的 Dashboard 不會被動到：最後一版安裝檔與 Supabase `kenaz-release/latest.json` 都保留，既有安裝可繼續用，但不會再收到更新。
-- 遷移步驟同上方「給使用者的步驟」：結束 Dashboard、關閉「開機時啟動」、`npx kenaz install`、`/kenaz init`、`npx kenaz doctor`。資料（專案、憑證、任務、記憶）都在 `~/.kenaz` 與 `<專案>/.kenaz`，不需搬移。
-- 回到舊版 Dashboard 只能用當初的安裝檔；repo 內不再有它的建置腳本（`build:kenaz`、`publish-release`、`editions/`、`PUBLISH_UPDATE`）。
-
-gui 行為去向（盤點自 `gui_app.rs`、`commands.rs`、`updater.rs`、24 個 `#[cfg(feature = "gui")]`）：
-
-| 行為 | 去向 |
-|---|---|
-| HTTP/MCP 啟動、port fallback、health watchdog、peer/presence/claude provision pollers | 已在 `server_boot::start_http_server`（TASK_2357/2369） |
-| PluginManager + MCP servers、Yggdrasil remote poll、field report loops | 已在 `start_headless_services`（TASK_2369/2394） |
-| KENAZ_SOURCE_DIR 解析、mcp.json 擁有者規則、env/tracing 初始化 | 已在 `server_boot`（`resolve_server_source_dir`、`should_rewrite_mcp`、`init_process`） |
-| 自動更新 | 已由 `infrastructure/self_update.rs` 取代（ed25519 簽章 feed）；Tauri updater 與 `/api/dashboard/*` 更新路由刪除 |
-| 視窗、splash、webview 重啟守衛、WTS 解鎖監看 | 刻意移除（無 webview） |
-| 系統匣、close-to-tray、開機自啟 | 刻意移除（服務由 `kenaz install` 的 service launcher 負責） |
-| `kenaz://` deep link、single-instance、Agent Hub 核准卡 | 刻意移除（hub 的 sites/sessions 狀態與 HTTP 路由保留） |
-| 語音 PTT、剪貼簿/檔案選取 tauri command、pty-server sidecar、claude-bridge、Next.js sidecar | 刻意移除（只有前端使用） |
-| Tauri `#[tauri::command]` 包裝（scheduler、single_agent、script、config 等） | 刻意移除；對應 HTTP 路由原本就存在，函式本體保留 |
-| `.env.local` 載入與 TUNNEL_SIGNING_SECRET 自動產生、tunnel token 寫回 | 未搬：kenaz-server 不載入 `.env.local`，tunnel 相關環境變數須自行以環境變數提供（見交接回報的未驗證項） |
-| 啟動時 `auto_seed_project_config`（寫入 `~/.kenaz/projects.json` 的 core 項目） | 未搬：由 `kenaz install` / `/kenaz init` 登錄專案 |
-| 啟動時 cortex seed merge（`merge_seed_if_needed`） | 刻意移除（記憶系統凍結，merge 核心 `merge_seed_at` 留待記憶卡處理） |
-| 退出清理與 self-kill watchdog | 刻意移除；kenaz-server 在 ctrl-c 時關閉 LSP 並 shutdown HTTP |
+Dashboard 各項行為的去向（哪些已搬進 kenaz-server、哪些刻意移除）記錄在 git 歷史中此檔 2026-10-11 之前的版本。

package/core/dev/scripts/correction-detect-eval.js

@@ -0,0 +1,70 @@
+#!/usr/bin/env node
+/**
+ * correction-detect-eval.js (TASK_2426) — replays real user prompts from Claude Code
+ * transcripts through the correction detector. Read-only.
+ *   node dev/scripts/correction-detect-eval.js [--transcripts <dir>] [--show 20]
+ * Default dir: ~/.claude/projects/<current project, path separators/colons -> "-">.
+ * Prints prompts scanned, fire rate (target <= 10%) and the first N fired prompts (80 chars).
+ */
+'use strict';
+const fs = require('fs');
+const os = require('os');
+const path = require('path');
+const { isCorrection } = require('../../.claude/hooks/correction-detect');
+
+function arg(name, dflt) {
+  const i = process.argv.indexOf('--' + name);
+  return i > 0 && process.argv[i + 1] ? process.argv[i + 1] : dflt;
+}
+
+function defaultDir() {
+  const slug = path.resolve(process.cwd()).replace(/[^A-Za-z0-9]/g, '-');
+  return path.join(os.homedir(), '.claude', 'projects', slug);
+}
+
+function listJsonl(dir) {
+  const out = [];
+  for (const e of fs.readdirSync(dir, { withFileTypes: true })) {
+    const p = path.join(dir, e.name);
+    if (e.isDirectory()) out.push(...listJsonl(p));
+    else if (e.name.endsWith('.jsonl')) out.push(p);
+  }
+  return out;
+}
+
+function userText(rec) {
+  if (!rec || rec.type !== 'user' || rec.isMeta || rec.isSidechain) return '';
+  const c = rec.message && rec.message.content;
+  if (typeof c === 'string') return c;
+  if (Array.isArray(c) && !c.some((b) => b && b.type === 'tool_result')) {
+    return c.filter((b) => b && b.type === 'text').map((b) => b.text).join('\n');
+  }
+  return '';
+}
+
+function main() {
+  const dir = arg('transcripts', defaultDir());
+  const show = Number(arg('show', 20));
+  let scanned = 0;
+  const fired = [];
+  for (const file of listJsonl(dir)) {
+    let text;
+    try { text = fs.readFileSync(file, 'utf8'); } catch (_) { continue; }
+    for (const line of text.split('\n')) {
+      if (!line) continue;
+      let rec;
+      try { rec = JSON.parse(line); } catch (_) { continue; }
+      const t = userText(rec).trim();
+      if (!t) continue;
+      scanned++;
+      if (isCorrection(t)) fired.push(t);
+    }
+  }
+  const rate = scanned ? (100 * fired.length / scanned) : 0;
+  console.log('dir: ' + dir);
+  console.log('prompts scanned: ' + scanned);
+  console.log('fired: ' + fired.length + ' (' + rate.toFixed(1) + '%, target <= 10%)');
+  fired.slice(0, show).forEach((p, i) => console.log((i + 1) + '. ' + p.replace(/\s+/g, ' ').slice(0, 80)));
+}
+
+main();

package/core/dev/specs/peer/CODEX_MANAGED_DAEMON.md

@@ -0,0 +1,54 @@
+# Codex desktop managed daemon as a peer push target (TASK_2419, field report d200d31d)
+
+## Problem
+
+The Codex desktop "Work" app (codex 0.162.x) talks to a managed `codex app-server` daemon. Kenaz's Bifrost launcher
+(`.formation/bifrost/launch.js`, TASK_2167) only registers the ws_url of an app-server it starts itself
+(`.kenaz/codex/sessions.json`). With the desktop app nothing is registered, so `/api/peer/status` showed
+`delivery_mode=none, sessions=[]` and the poller logged NO_TARGET, although mail was stored and the
+UserPromptSubmit `--pull` hook (`codex-hook-shim.js`) does deliver it on the next prompt.
+
+## Findings (evidence, codex-cli 0.162.0 on this machine, read-only)
+
+1. `codex app-server --help`: `--listen <URL>` accepts `stdio://` (default), `unix://`, `unix://PATH`, `ws://IP:PORT`, `off`.
+   Subcommands: `daemon` (bootstrap/start/restart/stop/version/enable-remote-control), `proxy` ("Proxy stdio bytes to the
+   running app-server control socket", `--sock <SOCKET_PATH>`). WS auth flags: `--ws-auth capability-token|signed-bearer-token`,
+   `--ws-token-file`, `--ws-shared-secret-file` (apply to ws listeners).
+2. The managed daemon is discoverable on disk, no env var needed: `$CODEX_HOME/app-server-control/app-server-control.sock`
+   (default `~/.codex/app-server-control/`), plus `$CODEX_HOME/app-server-daemon/daemon.pid`, `settings.json`
+   (`remoteControlEnabled:false`). Both existed here. It is a unix-domain socket (default path), not a ws://host:port.
+3. Protocol (`codex app-server generate-json-schema --out <tmp>`, ClientRequest.json) has the methods needed:
+   `initialize`, `thread/list`, `thread/loaded/list`, `thread/read`, `thread/resume`, `turn/start`, `turn/steer`,
+   `turn/interrupt`, `thread/inject_items`. So injection into a thread is possible in principle (the same methods
+   `codex_wake.rs::deliver_interactive` already uses over ws for launcher-started servers).
+4. Auth on the unix control socket: none visible; access control is filesystem permission of the socket owner.
+
+## Why Kenaz does not push into it (decision)
+
+- Unverified transport: whether the `unix://` listener speaks the same WebSocket framing as `ws://` is not confirmed here
+  (no daemon was started or connected; real user state must not be touched). `codex_wake.rs` uses `tokio_tungstenite::connect_async`
+  (TCP ws only); a unix-socket client would be new, and tokio `UnixStream` does not exist on Windows (AF_UNIX there needs another crate).
+- Target ambiguity: the desktop app owns many threads; `thread/loaded/list` does not say which one the user is looking at. Guessing
+  wrongly injects a turn into the wrong conversation.
+- Safety: push is deliberately opt-in (`codex_push: true`, user decision 2026-10-02) because an injected turn drives a full-access
+  agent from untrusted peer text. A socket that any same-user process can drive, with a guessed thread, widens that.
+
+Conclusion: not supported safely today. Degraded mode is made explicit instead.
+
+## What changed
+
+- `GET /api/peer/status`: when no push/pull session exists but a managed daemon is detected
+  (`codex_managed_daemon_in`, `peer_delivery_mode.rs`) a session `{agent:"codex", session_id:"codex-managed-daemon",
+  delivery_mode:"pull-on-prompt"}` is added; `delivery_mode` becomes `pull-on-prompt` with a Codex-specific note
+  (no push channel; mail arrives on the next prompt via `--pull`; run `node .formation/bifrost/codex-doctor.js`).
+  `kenaz ygg status` (plugins/kenaz/scripts/ygg.js) relays that mode/note unchanged.
+- NO_TARGET log detail (`peer_delivery_state::no_claude_reason`): TASK_2410 had already replaced the misleading
+  "claude not found on PATH" for Codex nodes; it now says "Codex managed daemon detected: no push channel ... via the --pull hook"
+  when the daemon is present, instead of "Codex not started via the Kenaz launcher".
+- `codex-doctor.js`: `diagnose()` returns `managed_daemon` and adds an informational note (does not fail `ok`).
+
+## Possible future push (not done)
+
+Confirm ws-over-unix framing against a temp `CODEX_HOME` daemon, add a unix transport to `AppServerClient`, require
+`codex_push: true`, and pick the thread via an explicit user choice (or the thread whose last hook-shim pull was most recent)
+rather than guessing. Until then use the pull path, or start Codex via `launch.js` with `codex_push: true`.

package/core/dev/specs/peer/setup-codex-hooks.test.js

@@ -20,3 +20,41 @@ test('missingHookEvents reports unregistered events and registerHooks fills exac
   const cfg = fs.readFileSync(path.join(home, 'config.toml'), 'utf8');
   assert.equal((cfg.match(/\[\[hooks\.UserPromptSubmit\.hooks\]\]/g) || []).length, 1);
 });
+
+// TASK_2418: a kenaz block from an old checkout, or a UserPromptSubmit block without --pull, is stale: rewritten once.
+test('stale kenaz hook blocks (old checkout path, missing --pull) are detected and replaced exactly once; user hooks stay', () => {
+  const home = fs.mkdtempSync(path.join(os.tmpdir(), 'codex-home-'));
+  process.env.CODEX_HOME = home;
+  const s = require('../../../.formation/bifrost/setup-codex.js');
+  const cur = s.getHookShimPath(process.cwd()).split('\\').join('/');
+  const old = '/old/checkout/.formation/bifrost/openai/codex-hook-shim.js';
+  const h = (ev, cmd) => ['[[hooks.' + ev + ']]', '', '[[hooks.' + ev + '.hooks]]', 'type = "command"', "command = '" + cmd + "'", 'timeout = 15', ''];
+  const cfgPath = path.join(home, 'config.toml');
+  fs.writeFileSync(cfgPath, [
+    'model = "x"', '',
+    ...h('Stop', 'node user-hook.js'),
+    '# kenaz-dashboard native hooks (TASK_1733) -- auto-registered by setup-codex.js',
+    ...h('PreToolUse', 'node "' + old + '"'),
+    ...h('PostToolUse', 'node "' + cur + '"'),
+    ...h('UserPromptSubmit', 'node "' + cur + '"'),
+    ...h('SessionStart', 'node "' + cur + '"'),
+    ...h('Stop', 'node "' + old + '"'),
+  ].join('\n'));
+  assert.deepEqual(s.missingHookEvents(), ['PreToolUse', 'UserPromptSubmit', 'Stop']);
+  assert.equal(s.areHooksAlreadyRegistered(process.cwd()), true); // PostToolUse/SessionStart are current
+  s.registerHooks(() => {}, process.cwd(), s.missingHookEvents());
+  assert.deepEqual(s.missingHookEvents(), []);
+  const cfg = fs.readFileSync(cfgPath, 'utf8');
+  for (const ev of ['PreToolUse', 'PostToolUse', 'UserPromptSubmit', 'SessionStart', 'Stop']) {
+    const n = (cfg.match(new RegExp('\\[\\[hooks\\.' + ev + '\\.hooks\\]\\][^\\[]*codex-hook-shim\\.js', 'g')) || []).length;
+    assert.equal(n, 1, ev + ' has exactly one kenaz handler');
+  }
+  assert.ok(!cfg.includes('/old/checkout'));
+  assert.match(cfg, /UserPromptSubmit\.hooks\]\][^\[]*--pull/);
+  assert.ok(cfg.includes('node user-hook.js') && cfg.includes('model = "x"'));
+  assert.equal((cfg.match(/kenaz-dashboard native hooks/g) || []).length, 1);
+  // uninstall removes the rewritten blocks and still keeps the user's
+  s.uninstall({ silent: true });
+  const after = fs.readFileSync(cfgPath, 'utf8');
+  assert.ok(!after.includes('codex-hook-shim.js') && after.includes('node user-hook.js'));
+});

package/core/dev/spikes/task2145-evidence-20261004/backend-log-excerpt.txt

@@ -0,0 +1,56 @@
+2026-10-03T21:07:10.515249Z  INFO MCP tool call tool="synapse_efe_feedback" plugin=None
+2026-10-03T21:07:45.377199Z  INFO MCP tool call tool="alaya_recall" plugin=None
+2026-10-03T21:07:53.574088Z  WARN [session_watcher] reflex check: role=assistant, text_len=119, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:07:53.574900Z  WARN [session_watcher] reflex check: role=assistant, text_len=119, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:07:54.168238Z  INFO MCP tool call tool="cortex_recall" plugin=None
+2026-10-03T21:07:54.372461Z  INFO MCP tool call tool="alaya_recall" plugin=None
+2026-10-03T21:07:54.728901Z  INFO MCP tool call tool="hippocampus_episode_recall" plugin=None
+2026-10-03T21:07:55.213271Z  INFO MCP tool call tool="synapse_health" plugin=None
+2026-10-03T21:08:37.929534Z  WARN [session_watcher] reflex check: role=assistant, text_len=2101, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:08:37.930488Z  WARN [session_watcher] reflex check: role=assistant, text_len=2101, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:10:36.990645Z  INFO MCP tool call tool="synapse_efe_feedback" plugin=None
+2026-10-03T21:10:37.101533Z  INFO MCP tool call tool="synapse_efe_feedback" plugin=None
+2026-10-03T21:10:47.558693Z  WARN [session_watcher] reflex check: role=assistant, text_len=153, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:10:47.558790Z  WARN [session_watcher] reflex check: role=assistant, text_len=153, blocks=1, project_path=Some("C:/Users/user/Documents/GitHub/KenazAI")
+2026-10-03T21:12:34.601726Z  INFO backend logging initialized version="0.2.263" pid=8024 started_at=2026-10-04 05:12:34.601 profile="debug" log_path=C:\Users\user\AppData\Local\Kenaz Dashboard\backend.log
+2026-10-03T21:12:34.601803Z  INFO startup mark label="after_init_tracing" t_ms=3 thread=main
+2026-10-03T21:12:35.010413Z  INFO startup mark label="setup_entry" t_ms=411 thread=main
+2026-10-03T21:12:35.015743Z  INFO startup mark label="mcp_servers_spawn_issued" t_ms=417 thread=main
+2026-10-03T21:12:35.015846Z  INFO startup mark label="mcp_servers_task_entered" t_ms=417 thread=tokio-runtime-worker
+2026-10-03T21:12:35.016550Z  INFO startup mark label="mcp_servers_start_done" t_ms=417 thread=tokio-runtime-worker
+2026-10-03T21:12:35.262343Z  INFO startup mark label="onnx_preload_dylib_done" t_ms=663 thread=main
+2026-10-03T21:12:35.262445Z  INFO startup mark label="onnx_warmup_thread_spawn_issued" t_ms=663 thread=main
+2026-10-03T21:12:35.262574Z  INFO startup mark label="delta_graph_recovery_thread_spawn_issued" t_ms=664 thread=main
+2026-10-03T21:12:35.262763Z  INFO startup mark label="sleep_cycle_daemon_spawn_issued" t_ms=664 thread=main
+2026-10-03T21:12:35.262754Z  INFO startup mark label="onnx_warmup_begin" t_ms=664 thread=onnx-warmup
+2026-10-03T21:12:35.262886Z  INFO startup mark label="delta_graph_recovery_begin" t_ms=664 thread=delta-gap-recovery
+2026-10-03T21:12:35.265586Z  INFO startup mark label="http_sidecar_task_spawn_issued" t_ms=667 thread=main
+2026-10-03T21:12:35.265647Z  INFO startup mark label="auto_index_watcher_spawn_issued" t_ms=667 thread=main
+2026-10-03T21:12:35.265727Z  INFO startup mark label="http_sidecar_task_entered" t_ms=667 thread=tokio-runtime-worker
+2026-10-03T21:12:35.265789Z  INFO startup mark label="setup_fn_returning" t_ms=667 thread=main
+2026-10-03T21:12:35.265824Z  INFO startup mark label="auto_index_watcher_task_entered" t_ms=667 thread=tokio-runtime-worker
+2026-10-03T21:12:35.291199Z  INFO [synapse] IS_INDEXING set — indexing started project=C:/Users/user/Documents/GitHub/KenazAI mode="incremental"
+2026-10-03T21:12:35.291229Z  INFO [synapse] reindex phase transition phase="init" project=C:/Users/user/Documents/GitHub/KenazAI
+2026-10-03T21:12:35.358777Z  INFO Loading ONNX embedding model [query] (ArcticEmbedXs, dim=384) from C:\Users\user\Documents\GitHub\KenazAI\dashboard\src-tauri\target\debug\resources\onnx\arctic-embed-xs
+2026-10-03T21:12:35.635924Z  INFO Embedding engine [query] loaded successfully (ArcticEmbedXs, dim=384, outputs=["last_hidden_state"], token_type_ids=true)
+2026-10-03T21:12:35.636005Z  INFO startup mark label="onnx_warmup_done" t_ms=1037 thread=onnx-warmup
+2026-10-03T21:12:36.101980Z  INFO startup mark label="http_server_start_begin" t_ms=1503 thread=tokio-runtime-worker
+2026-10-03T21:12:36.119887Z  INFO startup mark label="http_server_start_ready" t_ms=1521 thread=tokio-runtime-worker
+2026-10-03T21:12:36.122223Z  INFO synapse worker forwarder configuration workers_enabled=true current_project=C:/Users/user/Documents/GitHub/KenazAI
+2026-10-03T21:12:36.122290Z  INFO reaper armed leaseless_idle_secs=300 leased_idle_secs=900 tick_secs=60 per_worker_rss_cap_mb=400 total_rss_cap_mb=1200 max_workers=3
+2026-10-03T21:12:36.275465Z  INFO startup mark label="ready_wait_end" t_ms=1676 thread=tokio-runtime-worker
+2026-10-03T21:12:37.479820Z  INFO [synapse] reindex phase transition phase="kuzu_write_start:2_files" project=C:/Users/user/Documents/GitHub/KenazAI
+2026-10-03T21:12:37.815038Z ERROR [conn pool] GRAPH CORRUPT SUSPECT for C:/Users/user/Documents/GitHub/KenazAI\.synapse\db\graph: Failed to DETACH DELETE Symbol nodes for dashboard/src-tauri/src/features/synapse/scanner.rs: Query execution failed: kuzu native exception 0xC0000005 — no further kuzu calls will be issued against this Database for the rest of this process's lifetime (persisted; the next start will also refuse it). Recovery: rebuild_graph.
+2026-10-03T21:12:37.815639Z ERROR [synapse] dashboard/src-tauri/src/features/synapse/scanner.rs write hit a native ACCESS_VIOLATION — graph marked corrupt_suspect, aborting the round instead of quarantining just this file: Failed to DETACH DELETE Symbol nodes for dashboard/src-tauri/src/features/synapse/scanner.rs: Query execution failed: kuzu native exception 0xC0000005
+2026-10-03T21:12:37.815845Z ERROR Incremental index round aborted mid-batch (with_connection closure returned Err): Failed to DETACH DELETE Symbol nodes for dashboard/src-tauri/src/features/synapse/scanner.rs: Query execution failed: kuzu native exception 0xC0000005. Recording phase=failed and NOT advancing last_commit_hash, so the file(s) that caused this are retried (re-appear in the git diff) on the next incremental cycle instead of being permanently skipped.
+2026-10-03T21:12:37.823713Z  INFO [synapse] IS_INDEXING cleared project=C:/Users/user/Documents/GitHub/KenazAI
+2026-10-03T21:12:39.477700Z  INFO [synapse spool] drain: attempted=1 replayed=0 still_pending=1 dead_lettered=0
+2026-10-03T21:12:40.139564Z  INFO startup mark label="session_watcher_start_begin" t_ms=5541 thread=tokio-runtime-worker
+2026-10-03T21:12:40.139634Z  INFO startup mark label="session_watcher_start_done" t_ms=5541 thread=tokio-runtime-worker
+2026-10-03T21:12:40.139740Z  INFO [session_watcher] Watching "C:\\Users\\user\\.claude\\projects\\C--Users-user-Documents-GitHub-KenazAI" (notify + polling fallback)
+2026-10-03T21:12:44.502961Z  INFO startup mark label="synapse_kuzu_memorydb_open_done" t_ms=9904 thread=delta-gap-recovery
+2026-10-03T21:12:44.680900Z  INFO startup mark label="delta_graph_recovery_done" t_ms=10082 thread=delta-gap-recovery
+2026-10-03T21:12:44.706667Z  INFO startup mark label="heat_cache_load_done" t_ms=10108 thread=delta-gap-recovery
+2026-10-03T21:13:01.645377Z  INFO MCP tool call tool="synapse_efe_feedback" plugin=None
+2026-10-03T21:13:01.645462Z  INFO MCP tool call tool="synapse_efe_feedback" plugin=None
+2026-10-03T21:13:01.650906Z  INFO MCP tool call tool="synapse_cypher" plugin=None

package/core/dev/spikes/task2145-evidence-20261004/graph_corrupt_suspect.marker

@@ -0,0 +1 @@
+Failed to DETACH DELETE Symbol nodes for dashboard/src-tauri/src/features/synapse/scanner.rs: Query execution failed: kuzu native exception 0xC0000005

package/core/plugins/kenaz/commands/Ansuz.md

@@ -8,7 +8,8 @@ ARGUMENTS 含 `[專案: X]` 或 `--project-path X` → PROJECT_PATH = X，下方
 ## Boot（一次 Bash，無其他儀式）
 1. Turn Context 若有 `[session] session_id=<id>`，記住 `<id>`。
 2. 執行 `node "${CLAUDE_PLUGIN_ROOT}/hooks/core-resolve.js" .specialist/tools/ansuz-boot-fast.js`（有 `<id>` 加 `--conversation-id="<id>"`；有 PROJECT_PATH 加 `--project-path`）。
-3. 把 banner 轉述給用戶（Bash 輸出在 UI 會摺疊），並依 `📋 Open cards` 直接提出議程。
+3. banner 有 `📎 Project handoff` 時，**先用 Read 讀 → 標記的那份全文**（不用問用戶），以它為準接續上一個 session。
+4. 把 banner 轉述給用戶（Bash 輸出在 UI 會摺疊），依 handoff 的 R 段與 `📋 Open cards` 直接提出議程。
 
 ## 每件工作的做法
 - **自己做**：小而明確的修正（約 30 行內、單一檔案或少數檔案）→ 直接改，跑最近的測試，提交。
@@ -16,6 +17,7 @@ ARGUMENTS 含 `[專案: X]` 或 `--project-path X` → PROJECT_PATH = X，下方
   1. 用 `kenaz_task_create` 開卡（`projectPath` = 目前專案；寫清楚 requirements、acceptance criteria、scope paths）。查卡、改狀態用 `kenaz_task_list` / `kenaz_task_get` / `kenaz_task_update`。
   2. 產生派工內容：`node "${CLAUDE_PLUGIN_ROOT}/hooks/core-resolve.js" .formation/tools/dispatch.js --skill=do --task=TASK_XXX --dispatch-mode=subagent`（有 PROJECT_PATH 加 `--project-path`）。把輸出 JSON 的 `promptText` 交給 subagent，`agentParams` 照用（模型不要自己換）。
   3. subagent 在 worktree 裡改完並 commit；你驗證後合併。
+     若輸出是 `executor` 區塊（模型為 `codex:<id>` / `deepseek:<model>`，無 agentParams）：用 Bash run_in_background 執行 `executor.command`，等完成通知，讀 `executor.resultFile`（ok、commits；`no commits` = 失敗），再照常驗證並合併 `executor.branchName`。
 - 開卡前先確認 scope 與驗收條件對準真正的問題，不要照著錯的假設派工。
 
 ## 驗證（合併前一定做，強度跟風險相稱）
@@ -24,6 +26,12 @@ ARGUMENTS 含 `[專案: X]` 或 `--project-path X` → PROJECT_PATH = X，下方
 - subagent 回報「未驗證」的項目，由你補驗或明講仍未驗證。
 - 合併：`git merge` 後跑相關測試（或 `node "${CLAUDE_PLUGIN_ROOT}/hooks/core-resolve.js" .specialist/Ansuz/tools/verify-and-land.js`），用這個專案自己的測試指令。
 
+## 交接（handoff，ISBAR）
+用戶說交接／暫停／換 session、context 快滿、或結束時仍有未完成的工作 → 寫交接：
+1. `node "${CLAUDE_PLUGIN_ROOT}/hooks/core-resolve.js" .specialist/tools/handoff-doc.js new --topic "<主題>" --session <id>`（有 PROJECT_PATH 加 `--project-path`），建立 `<專案>/.kenaz/handoffs/<日期時間>-<主題>.md`，I 段已自動填好。
+2. 用 Edit 填 S（現況）、B（背景：用戶決定原話、相關卡與 commit）、A（已驗證／未驗證／風險）、R（下一個 session 第一步、待用戶決定的事）。寫給「沒看過這段對話的人」，不寫空泛句。
+3. 一份交接一個檔，不覆寫舊的；下一個 session 的 boot 會自動列出並讀最新那份。
+
 ## 回報與提問
 - 一律用用戶的語言（中文訊息 → 中文回覆，含提問選項）。
 - 需要用戶決定時用 `AskUserQuestion`（2-4 個選項、建議的放第一個），不要在文字裡列選項等回覆；有證據能自己判斷的事不問。
@@ -38,5 +46,7 @@ Kenaz 的工具、hook、安裝、peer、派工擋住或拖慢工作時，**繞
 ## 參考產品（REA）與學習教訓
 - banner `[rea]` 行：用戶提到參考產品時，有 REA 就提議分析，沒有就提示一次 `npx rea-agents setup`（範圍見 RULES.md 的 REA）。
 - 用戶糾正/重複指示、推翻決定、或驗證抓到失敗時，自動寫教訓並在回報點名一行：`node "${CLAUDE_PLUGIN_ROOT}/hooks/core-resolve.js" .specialist/tools/lessons.js add --scope user|project --type pref|fact|pitfall|check --text "..."`（規則見 RULES.md 的 Lessons）。
+- banner 出現 `[lessons] N to graduate`：跑 `kenaz learn review`，提議把排第一的教訓改成代碼（測試、hook 檢查或專案 CLAUDE.md/AGENTS.md 規則，這是首選結果）；糾正若與既有教訓相符屬於重複（recurrence），不是新教訓（`add` 會自動累加）。
+- banner 出現 `[learn] N history items to review`：跑 `kenaz learn review`，每個歷史項目（返工、executor 失敗、blocked 卡、handoff 風險行）有現成的 `kenaz learn add ... --source harvest:<id>`，值得記的補上 why 後執行，其餘忽略；指標建議（各 rigor 一次過率、返工最多的檔案）只建議給用戶，不自行套用。詳見 RULES.md。
 
 需要更多規則時（授權自主、派工前、合併前、參考產品、寫教訓）讀 `${CLAUDE_PLUGIN_ROOT}/../../.specialist/Ansuz/RULES.md`。

package/core/plugins/kenaz/commands/kenaz.md

@@ -1,12 +1,14 @@
 ---
-description: Switch or show the Kenaz mode (off | assist | full | status | init), or set up Yggdrasil (ygg join|status|leave)
-argument-hint: off|assist|full|status|init|ygg
+description: Switch or show the Kenaz mode (off | assist | full | status | init), set up Yggdrasil (ygg join|status|leave), or show/set the subagent model (subagent [set <id>|unset] [--rigor r])
+argument-hint: off|assist|full|status|init|ygg|subagent
 allowed-tools: Bash(node:*)
 ---
-Run exactly this and report its output (one line for modes; the full block for `ygg`), nothing else:
+Run exactly this and report its output (one line for modes; the full block for `ygg` and `subagent`), nothing else:
 
 `node "${CLAUDE_PLUGIN_ROOT}/scripts/kenaz-mode.js" $ARGUMENTS`
 
 Modes: full = guidance + all hooks; assist = silent telemetry/bookkeeping hooks only (no context injection); off = every Kenaz hook exits immediately. init creates .kenaz/project.yaml so hooks act in a fresh project.
 
 `ygg join <key> [--project|--global]` stores the Yggdrasil connection key (default: this project's own slot) and activates collaboration here; `ygg status` shows room, node, relay, peers and mail (key masked); `ygg leave` removes this project's key. Needs kenaz-server running (installed by `npx kenaz install`).
+
+`subagent` shows the subagent (dispatch) model per rigor for this project; `subagent set <id> [--rigor low|medium|high]` changes it, `subagent unset [--rigor r]` reverts (writes .kenaz/dashboard-models.json). Ansuz itself runs on this session's model (/model).

package/core/plugins/kenaz/scripts/kenaz-mode.js

@@ -10,6 +10,12 @@ if (arg === 'ygg') {
   const r = require('child_process').spawnSync(process.execPath, [path.join(__dirname, 'ygg.js'), ...process.argv.slice(3)], { stdio: 'inherit' });
   process.exit(r.status === null ? 1 : r.status);
 }
+if (arg === 'subagent' || arg === 'model') {
+  // Subagent (dispatch) model: subagent [set <id>|unset] [--rigor r]; same as `kenaz subagent`, for this project
+  const tool = path.join(__dirname, '..', '..', '..', '.formation', 'tools', 'dispatch-model.js');
+  const r = require('child_process').spawnSync(process.execPath, [tool, ...process.argv.slice(3), '--project-path', projectDir()], { stdio: 'inherit' });
+  process.exit(r.status === null ? 1 : r.status);
+}
 const dir = projectDir();
 if (MODES.includes(arg)) {
   setMode(arg, dir);