kenaz 0.3.2 → 0.3.3

package/core/.agents/skills/typesafe-ai/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 TypeSafe AI
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 TypeSafe AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/core/.agents/skills/typesafe-ai/SKILL.md

@@ -1,149 +1,149 @@
----
-name: typesafe-ai
-license: MIT
-description: >
-  Build AI-powered software with TypeSafe: small units of AI intelligence you
-  can use like programming primitives. Its System One models, including Jev,
-  turn natural language and application state into typed judgments and
-  probabilities that code can combine. Use when a feature needs programmable
-  common sense, when brainstorming what AI could make possible in an app, or
-  when an LLM prompt-and-parse step could become a structured decision.
-  Applications include routing, ranking, extraction, verification, and
-  interactive experiences; these are starting points, not the limits.
-  Read live docs and cookbooks to find useful patterns and discover new combinations.
----
-
-# Build with TypeSafe
-
-TypeSafe makes units of AI intelligence usable like programming primitives: small
-judgments you can compose into larger capabilities. Its **System One models** return
-fast, focused judgments that software can consume directly. **Jev** is TypeSafe's
-flagship and first System One model. It understands natural language and returns
-typed answers and probabilities rather
-than generating text or reasoning explanations. Code owns the workflow; the model
-supplies programmable common sense where ordinary code needs semantic understanding.
-
-## Read the live docs
-
-**The live TypeSafe docs are the source of truth. Read them as part of the task.**
-This skill gives direction; the docs carry current concepts, prompting guidance,
-API contracts, SDK usage, models, limits, and worked examples.
-
-- Start with the [documentation index](https://docs.typesafe.ai/llms.txt) to discover
-  relevant pages and cookbooks. Use targeted reads rather than loading the entire site.
-- Mintlify serves Markdown by appending `.md` to a page path, for example
-  [how to build with TypeSafe](https://docs.typesafe.ai/concepts/how-to-build-with-system-one.md).
-  Follow links from the index; convert extensionless documentation page links to
-  `.md` when useful. Resolve relative links against `https://docs.typesafe.ai`.
-- Before writing an integration, read the current API or chosen SDK page and the
-  question guidance relevant to the design. For a new workflow, also inspect the
-  closest cookbook: it often shows a better decomposition than a generic classifier.
-- If the index is unavailable, use the direct links below or the site's navigation.
-  If Markdown fetching fails, try the normal page. If live access is unavailable,
-  use available local docs or installed SDK types, state that limitation, and avoid
-  inventing version-dependent details.
-
-| Task | Start here; follow the relevant details |
-| --- | --- |
-| Understand the programming model | [System One](https://docs.typesafe.ai/concepts/system-one.md), [building guide](https://docs.typesafe.ai/concepts/how-to-build-with-system-one.md) |
-| Explore what to build | [Use-case map](https://docs.typesafe.ai/concepts/use-case-map.md), then relevant cookbooks from the index |
-| Prepare inputs and questions | [State](https://docs.typesafe.ai/concepts/state.md), [primitives](https://docs.typesafe.ai/primitives.md), then the chosen primitive's page |
-| Decide how to handle uncertainty | [Confidence](https://docs.typesafe.ai/confidence.md) |
-| Write API code | [HTTP API](https://docs.typesafe.ai/api.md), [Python SDK](https://docs.typesafe.ai/sdk/python.md), or [JavaScript SDK](https://docs.typesafe.ai/sdk/javascript.md) |
-| Update an older integration | [Migration guide](https://docs.typesafe.ai/migrating-to-v1.md) and the installed SDK's current reference |
-
-## Find the useful shape
-
-Start from the behavior the user wants: what will the application show, select,
-change, or hand off? Work backward to the judgments it needs. Keep known rules,
-calculations, exact lookups, and execution in code. Preserve the user's chosen stack
-and scope; add TypeSafe where semantic understanding helps.
-
-When brainstorming or choosing an architecture, consider more than classification.
-The patterns below are starting points: combine primitives around the user's goal,
-including ideas that do not fit an established recipe.
-
-- **Route and fill known arguments.** A request can select a handler and its typed
-  parameters. Ask useful branch-specific questions up front and consume only the
-  relevant answers. Explore [function calling](https://docs.typesafe.ai/cookbooks/function_calling.md)
-  and [speculative fan-out](https://docs.typesafe.ai/patterns/fan-out.md).
-- **Select instead of generate.** Find candidate values or source spans in code,
-  use a judgment to select the intended one, then copy or normalize it. Code can
-  also assemble source text into a formatted document or reading guide. Explore
-  [value extraction](https://docs.typesafe.ai/cookbooks/pre_parsed_value_extraction_cookbook.md)
-  and [structure recovery](https://docs.typesafe.ai/cookbooks/autoformat.md).
-- **Find and judge evidence.** Retrieve candidates, compare their relevance to a
-  query, and select useful context. Explore [reranking](https://docs.typesafe.ai/cookbooks/rerank_typesafe.md)
-  and [hierarchical classification](https://docs.typesafe.ai/cookbooks/hierarchical_classification.md).
-- **Turn judgments into reusable data.** Score dimensions once, then let code or
-  user controls change weights, thresholds, rankings, and views. With labeled
-  outcomes, those signals can become classical ML features. Explore
-  [composite scoring](https://docs.typesafe.ai/patterns/composite-scoring.md) and
-  [feature discovery](https://docs.typesafe.ai/cookbooks/autoresearch_feature_discovery.md).
-- **Verify and escalate.** Check specific claims or fields against their evidence;
-  send uncertain or failing cases to a person or reasoning model. Explore
-  [citation checks](https://docs.typesafe.ai/cookbooks/citation_check.md) and
-  [extraction cascades](https://docs.typesafe.ai/cookbooks/sde_cascade.md).
-- **Respond to changing state.** Code can retain goals and observations while fresh
-  judgments guide the next bounded step. Keep inferred state distinct from observed
-  facts, and check freshness before applying a result to a changed situation.
-
-For open-ended requests, offer the few directions that best serve the user's goal
-and recommend a starting point. For a concrete request, choose the relevant pattern
-and build; a brainstorm is not a mandatory detour.
-
-## Design the judgments
-
-Choose by what the answer means, then read the relevant primitive page:
-
-| Need | Primitive | Important distinction |
-| --- | --- | --- |
-| One of a defined set | [Choice](https://docs.typesafe.ai/primitives/choice.md) | Picks one option; its distribution compares competing options |
-| Whether a condition holds | [Noul](https://docs.typesafe.ai/primitives/noul.md) | Probability of yes; no separate confidence; use one per label when several may apply |
-| Degree along a described dimension | [Score](https://docs.typesafe.ai/primitives/score.md) | Probability-weighted position on ordered levels; use comparable per-item Scores for graded ranking |
-
-Give each question enough relevant **state** to answer: source text, identities,
-relationships, policies, and current facts. Prefer named JSON fields when context
-has several parts. Put the judgment in **instructions** and define its possible
-answers in **criteria**. Question IDs are for code and are not sent to the model;
-include complete meaning in the question. Reference nested state with backticked
-paths such as `ticket.messages[0].text`.
-
-Ask one narrow, coherent judgment per question. Split independently useful dimensions,
-without destroying the relationship being judged. A bounded action selection or
-contextual interpretation is valid; atomic does not mean literal fact extraction
-or a one-sentence limit. Strings work for simple questions. Use structured objects
-or arrays when definitions, contrasts, exclusions, or examples clarify instructions
-or criteria. Score levels must describe concrete situations and stand on their own.
-
-Keep the needed answers available. Include a no-match outcome when nothing may fit;
-use a separate presence judgment when it is independently useful. For source-value
-selection, check candidate coverage: the model cannot choose an omitted value.
-
-## Compose and verify
-
-**Ask independent questions over the same state together**, including useful
-speculative questions. They run in parallel and cannot see one another's answers.
-State each speculative premise explicitly; code consumes the applicable answers.
-A second request is warranted when an earlier answer is needed to fetch evidence,
-construct new state, or determine the next options. Extra questions still use tokens;
-measure actual request budgets, cost, and end-to-end latency.
-
-Use probabilities and confidence to guide behavior, with thresholds evaluated on
-the user's data and consequences. Choice/Score confidence summarizes distribution
-concentration, not overall workflow correctness or permission to act. A Noul near
-0.5 means similar probability for yes and no, not medium intensity. Several
-acceptable alternatives can also spread probability; low confidence need not
-invalidate a harmless preference choice. Ignore uncertainty on unused branches.
-
-Keep policy explicit and raw judgments reusable. Weighted scores suit compensating
-preferences; an “any serious violation” rule needs separate conditions. Changing a
-weight or display filter need not rerun inference when evidence and question meanings
-are unchanged. Typed output guarantees the interface, not truth. System One models
-are trained for calibrated decisions; validate their performance in the target domain.
-
-Test representative cases and the resulting application behavior. For failures,
-inspect the exact state, questions, candidates, answers, composition, and observed
-outcome. Separate missing evidence, model errors, code errors, and service failures.
-Treat cookbook thresholds and demo results as examples to evaluate, not universal
-rules or permanent model limitations. Keep API credentials server-side in web apps.
+---
+name: typesafe-ai
+license: MIT
+description: >
+  Build AI-powered software with TypeSafe: small units of AI intelligence you
+  can use like programming primitives. Its System One models, including Jev,
+  turn natural language and application state into typed judgments and
+  probabilities that code can combine. Use when a feature needs programmable
+  common sense, when brainstorming what AI could make possible in an app, or
+  when an LLM prompt-and-parse step could become a structured decision.
+  Applications include routing, ranking, extraction, verification, and
+  interactive experiences; these are starting points, not the limits.
+  Read live docs and cookbooks to find useful patterns and discover new combinations.
+---
+
+# Build with TypeSafe
+
+TypeSafe makes units of AI intelligence usable like programming primitives: small
+judgments you can compose into larger capabilities. Its **System One models** return
+fast, focused judgments that software can consume directly. **Jev** is TypeSafe's
+flagship and first System One model. It understands natural language and returns
+typed answers and probabilities rather
+than generating text or reasoning explanations. Code owns the workflow; the model
+supplies programmable common sense where ordinary code needs semantic understanding.
+
+## Read the live docs
+
+**The live TypeSafe docs are the source of truth. Read them as part of the task.**
+This skill gives direction; the docs carry current concepts, prompting guidance,
+API contracts, SDK usage, models, limits, and worked examples.
+
+- Start with the [documentation index](https://docs.typesafe.ai/llms.txt) to discover
+  relevant pages and cookbooks. Use targeted reads rather than loading the entire site.
+- Mintlify serves Markdown by appending `.md` to a page path, for example
+  [how to build with TypeSafe](https://docs.typesafe.ai/concepts/how-to-build-with-system-one.md).
+  Follow links from the index; convert extensionless documentation page links to
+  `.md` when useful. Resolve relative links against `https://docs.typesafe.ai`.
+- Before writing an integration, read the current API or chosen SDK page and the
+  question guidance relevant to the design. For a new workflow, also inspect the
+  closest cookbook: it often shows a better decomposition than a generic classifier.
+- If the index is unavailable, use the direct links below or the site's navigation.
+  If Markdown fetching fails, try the normal page. If live access is unavailable,
+  use available local docs or installed SDK types, state that limitation, and avoid
+  inventing version-dependent details.
+
+| Task | Start here; follow the relevant details |
+| --- | --- |
+| Understand the programming model | [System One](https://docs.typesafe.ai/concepts/system-one.md), [building guide](https://docs.typesafe.ai/concepts/how-to-build-with-system-one.md) |
+| Explore what to build | [Use-case map](https://docs.typesafe.ai/concepts/use-case-map.md), then relevant cookbooks from the index |
+| Prepare inputs and questions | [State](https://docs.typesafe.ai/concepts/state.md), [primitives](https://docs.typesafe.ai/primitives.md), then the chosen primitive's page |
+| Decide how to handle uncertainty | [Confidence](https://docs.typesafe.ai/confidence.md) |
+| Write API code | [HTTP API](https://docs.typesafe.ai/api.md), [Python SDK](https://docs.typesafe.ai/sdk/python.md), or [JavaScript SDK](https://docs.typesafe.ai/sdk/javascript.md) |
+| Update an older integration | [Migration guide](https://docs.typesafe.ai/migrating-to-v1.md) and the installed SDK's current reference |
+
+## Find the useful shape
+
+Start from the behavior the user wants: what will the application show, select,
+change, or hand off? Work backward to the judgments it needs. Keep known rules,
+calculations, exact lookups, and execution in code. Preserve the user's chosen stack
+and scope; add TypeSafe where semantic understanding helps.
+
+When brainstorming or choosing an architecture, consider more than classification.
+The patterns below are starting points: combine primitives around the user's goal,
+including ideas that do not fit an established recipe.
+
+- **Route and fill known arguments.** A request can select a handler and its typed
+  parameters. Ask useful branch-specific questions up front and consume only the
+  relevant answers. Explore [function calling](https://docs.typesafe.ai/cookbooks/function_calling.md)
+  and [speculative fan-out](https://docs.typesafe.ai/patterns/fan-out.md).
+- **Select instead of generate.** Find candidate values or source spans in code,
+  use a judgment to select the intended one, then copy or normalize it. Code can
+  also assemble source text into a formatted document or reading guide. Explore
+  [value extraction](https://docs.typesafe.ai/cookbooks/pre_parsed_value_extraction_cookbook.md)
+  and [structure recovery](https://docs.typesafe.ai/cookbooks/autoformat.md).
+- **Find and judge evidence.** Retrieve candidates, compare their relevance to a
+  query, and select useful context. Explore [reranking](https://docs.typesafe.ai/cookbooks/rerank_typesafe.md)
+  and [hierarchical classification](https://docs.typesafe.ai/cookbooks/hierarchical_classification.md).
+- **Turn judgments into reusable data.** Score dimensions once, then let code or
+  user controls change weights, thresholds, rankings, and views. With labeled
+  outcomes, those signals can become classical ML features. Explore
+  [composite scoring](https://docs.typesafe.ai/patterns/composite-scoring.md) and
+  [feature discovery](https://docs.typesafe.ai/cookbooks/autoresearch_feature_discovery.md).
+- **Verify and escalate.** Check specific claims or fields against their evidence;
+  send uncertain or failing cases to a person or reasoning model. Explore
+  [citation checks](https://docs.typesafe.ai/cookbooks/citation_check.md) and
+  [extraction cascades](https://docs.typesafe.ai/cookbooks/sde_cascade.md).
+- **Respond to changing state.** Code can retain goals and observations while fresh
+  judgments guide the next bounded step. Keep inferred state distinct from observed
+  facts, and check freshness before applying a result to a changed situation.
+
+For open-ended requests, offer the few directions that best serve the user's goal
+and recommend a starting point. For a concrete request, choose the relevant pattern
+and build; a brainstorm is not a mandatory detour.
+
+## Design the judgments
+
+Choose by what the answer means, then read the relevant primitive page:
+
+| Need | Primitive | Important distinction |
+| --- | --- | --- |
+| One of a defined set | [Choice](https://docs.typesafe.ai/primitives/choice.md) | Picks one option; its distribution compares competing options |
+| Whether a condition holds | [Noul](https://docs.typesafe.ai/primitives/noul.md) | Probability of yes; no separate confidence; use one per label when several may apply |
+| Degree along a described dimension | [Score](https://docs.typesafe.ai/primitives/score.md) | Probability-weighted position on ordered levels; use comparable per-item Scores for graded ranking |
+
+Give each question enough relevant **state** to answer: source text, identities,
+relationships, policies, and current facts. Prefer named JSON fields when context
+has several parts. Put the judgment in **instructions** and define its possible
+answers in **criteria**. Question IDs are for code and are not sent to the model;
+include complete meaning in the question. Reference nested state with backticked
+paths such as `ticket.messages[0].text`.
+
+Ask one narrow, coherent judgment per question. Split independently useful dimensions,
+without destroying the relationship being judged. A bounded action selection or
+contextual interpretation is valid; atomic does not mean literal fact extraction
+or a one-sentence limit. Strings work for simple questions. Use structured objects
+or arrays when definitions, contrasts, exclusions, or examples clarify instructions
+or criteria. Score levels must describe concrete situations and stand on their own.
+
+Keep the needed answers available. Include a no-match outcome when nothing may fit;
+use a separate presence judgment when it is independently useful. For source-value
+selection, check candidate coverage: the model cannot choose an omitted value.
+
+## Compose and verify
+
+**Ask independent questions over the same state together**, including useful
+speculative questions. They run in parallel and cannot see one another's answers.
+State each speculative premise explicitly; code consumes the applicable answers.
+A second request is warranted when an earlier answer is needed to fetch evidence,
+construct new state, or determine the next options. Extra questions still use tokens;
+measure actual request budgets, cost, and end-to-end latency.
+
+Use probabilities and confidence to guide behavior, with thresholds evaluated on
+the user's data and consequences. Choice/Score confidence summarizes distribution
+concentration, not overall workflow correctness or permission to act. A Noul near
+0.5 means similar probability for yes and no, not medium intensity. Several
+acceptable alternatives can also spread probability; low confidence need not
+invalidate a harmless preference choice. Ignore uncertainty on unused branches.
+
+Keep policy explicit and raw judgments reusable. Weighted scores suit compensating
+preferences; an “any serious violation” rule needs separate conditions. Changing a
+weight or display filter need not rerun inference when evidence and question meanings
+are unchanged. Typed output guarantees the interface, not truth. System One models
+are trained for calibrated decisions; validate their performance in the target domain.
+
+Test representative cases and the resulting application behavior. For failures,
+inspect the exact state, questions, candidates, answers, composition, and observed
+outcome. Separate missing evidence, model errors, code errors, and service failures.
+Treat cookbook thresholds and demo results as examples to evaluate, not universal
+rules or permanent model limitations. Keep API credentials server-side in web apps.

package/core/.claude/commands/Ansuz.md

@@ -1,38 +1,27 @@
-## 專案路徑解析（Project Path Resolution · 最先執行）
-
-在執行任何步驟前，先從 `/Ansuz` 的 ARGUMENTS 解析 PROJECT_PATH：
-- 格式 `[專案: X]` → PROJECT_PATH = X
-- 格式 `--project-path X` → PROJECT_PATH = X
-- 無此格式（cwd = core，一般情況）→ PROJECT_PATH 為空，全程不附加任何 flag，行為完全不變
-
-PROJECT_PATH 有值時，必須下傳至：下方快速 Boot 的 ansuz-boot-fast.js 呼叫（附加 `--project-path "<PROJECT_PATH>"`）。
-
----
+## 專案路徑
+ARGUMENTS 含 `[專案: X]` 或 `--project-path X` → PROJECT_PATH = X，下方 boot 腳本與 task-api / dispatch 呼叫都附加 `--project-path "<PROJECT_PATH>"`。沒有就留空，什麼都不加。
 
 # Ansuz boot
 
-你是 **Ansuz**，Kenaz 的 PM：理解需求、設計任務、選擇派工方式、派工、驗證、回報。先查現況、先確認 scope，再動手。
-
-日常規則在 CLAUDE.md 與記憶索引裡。**以下時機讀 `.specialist/Ansuz/RULES.md`**：用戶授權自主時、派工前、合併／landing 前、寫 handoff 時、boot banner 出現 `[pin:...]` 時。（2026-10-07 盲測：常駐的 17.5 KB elixir 開機 prompt 不改變這些行為，已退役，見 dev/research/ansuz-boot-ablation/RESULTS.md。）
-
----
-
-## 快速 Boot（唯一路徑 · 無 gate；舊 `--full` 流程已封存於 dev/archive/ansuz/BOOT_FULL.md）
-
-main thread 直接做輕量 Phase 0：**不 spawn sub-agent、不跑 phase-gate、不寫 mirror、不 emit ritual markers**。只印 banner、歸檔上一世 handoff。
-
-> 若解析出 PROJECT_PATH，下方腳本呼叫附加 `--project-path "<PROJECT_PATH>"`。
+你是 **Ansuz**，Kenaz 的 orchestrator：理解需求，依情境決定自己動手或拆任務派給 subagent，合併前在真實路徑上驗證，然後回報。先查現況、確認 scope，再動手。
 
-0. **（TASK_2222 · 必做）取得真實 session_id**：本輪 Turn Context 若含 `[session] session_id=<id>`，記住 `<id>`（本 session 專屬；單槽檔 `last_prompt_session.json` 會被並行 session 覆寫，不可用）。之後：
-   - 第 2 步附加 `--conversation-id=<id>`；
-   - 每次呼叫 `ansuz_handoff_snapshot`（或其他接受 `session_id` 的工具）一律帶 `session_id=<id>`。
-   - 找不到這行時省略兩者，腳本有 fallback。
+## Boot（一次 Bash，無其他儀式）
+1. Turn Context 若有 `[session] session_id=<id>`，記住 `<id>`。
+2. 執行 `node .specialist/tools/ansuz-boot-fast.js`（有 `<id>` 加 `--conversation-id="<id>"`；有 PROJECT_PATH 加 `--project-path`）。
+3. 把 banner 轉述給用戶（Bash 輸出在 UI 會摺疊），並依 `📋 Open cards` 直接提出議程。
 
+## 每件工作的做法
+- **自己做**：小而明確的修正（約 30 行內、單一檔案或少數檔案）→ 直接改，跑最近的測試，提交。
+- **開卡派工**：中型、可平行、或高風險路徑的工作 → `task-api.js create` 寫清楚驗收條件，再派 subagent（細節讀 `.specialist/Ansuz/RULES.md` 的 Dispatch）。
+- 開卡前先確認 scope 與驗收條件對準真正的問題，不要照著錯的假設派工。
 
-2. **跑 boot 腳本**（一個 Bash 呼叫）：
-   `node .specialist/tools/ansuz-boot-fast.js`（子專案附加 `--project-path "<PROJECT_PATH>"`；有 `<id>` 時附加 `--conversation-id="<id>"`）
-   印出 banner（peer / 任務 / Wishes / ANOMALY / handoff）並歸檔上一世 handoff。
+## 驗證（合併前一定做，強度跟風險相稱）
+- 走**真實路徑**：實際執行會被使用者用到的那條路（真的安裝、真的啟動、真的收發訊息），不只看單元測試。
+- 有**對照組**：證明測試在舊程式上會失敗，或修改前後結果不同。
+- subagent 回報「未驗證」的項目，由你補驗或明講仍未驗證。
+- 合併用 `.specialist/Ansuz/tools/verify-and-land.js` 或 `git merge` 後跑相關測試；Rust 測試只走 `npm run test:rust` / `dev/scripts/rust-verify-worktree.js`。
 
-3. **Relay banner**：把腳本 stdout 轉述給用戶（Bash 輸出在 UI 是摺疊的）。顯示 pin 行時，後續所有 synapse_*/hippocampus_*/cortex_* MCP 呼叫與 specialist CLI 呼叫皆需帶 `projectPath`/`--project-path <pin>`。
+## 回報
+用用戶的語言。說清楚：做了什麼、怎麼驗證的、還有什麼沒驗證或需要用戶決定。不說「應該可以」。
 
-4. **Phase 0 完成** → 直接進 Phase 1+。banner 的 `📋 Open cards` 已含每張卡的 id / 優先度 / 標題 / STATUS，**第一個回應就依此提議程**，不要再跑 task-api list；只在要動某張卡時才 `task-api get`。
+需要更多規則時（用戶授權自主、派工前、合併前）讀 `.specialist/Ansuz/RULES.md`。

package/core/.claude/hooks/_ansuz-conversation.js

@@ -22,6 +22,7 @@ const path = require('path');
 
 const MARKERS = [
   '<command-name>/Ansuz</command-name>', // user typed /Ansuz
+  '<command-name>/kenaz:Ansuz</command-name>', // typed through the kenaz plugin (npm install)
   '# Ansuz boot', // .claude/commands/Ansuz.md body since the elixir boot prompt was retired (2026-10-07)
   'session.js prompt Ansuz --mode=assembled', // older Ansuz.md body (transcripts before 2026-10-07)
   '# Ansuz -- Specialist Prompt', // assembled prompt handed over as a user message (headless)

package/core/.claude/hooks/_ansuz-conversation.test.js

@@ -88,3 +88,9 @@ test('the current Ansuz.md body (no boot prompt, 2026-10-07) is still recognised
   const mention = JSON.stringify({ type: 'user', message: { role: 'user', content: 'what is in .specialist/Ansuz/RULES.md?' } });
   assert.equal(lineIsAnsuzEntry(mention), false);
 });
+
+test('plugin-namespaced /kenaz:Ansuz is recognised as an Ansuz session', () => {
+  const { lineIsAnsuzEntry } = require('./_ansuz-conversation');
+  const line = JSON.stringify({ type: 'user', message: { role: 'user', content: '<command-name>/kenaz:Ansuz</command-name>' } });
+  assert.strictEqual(lineIsAnsuzEntry(line), true);
+});

package/core/.claude/hooks/_run-user-prompt.js

@@ -33,14 +33,10 @@ const path = require('path');
 const { Readable } = require('stream');
 
 const DEFAULT_HOOKS = [
-  'handoff-staleness.js',
-  'fatigue-check.js',
   'daemon-outbox-hook.js',
   // TASK_2218: ansuz-session-pin.js is called from turn-context.js (every install layout runs that hook).
   'turn-context.js',
   'task-bridge.js',
-  'lease-touch.js',
-  'stream-delta.js',
 ];
 
 const HARD_CAP_MS = 10000;

package/core/.claude/hooks/_run-user-prompt.test.js

@@ -69,12 +69,11 @@ test('runner replays stdin, traps exits, concatenates stdout, exits 0', () => {
   assert.ok(elapsed < 5000, 'runner drained promptly, took ' + elapsed + ' ms');
 });
 
-test('default list is the seven UserPromptSubmit hooks in settings order', () => {
+test('default list is the three UserPromptSubmit hooks in settings order', () => {
   // TASK_2218: the pin writer is invoked from turn-context.js, not listed here.
   const { DEFAULT_HOOKS } = require(RUNNER);
   assert.deepStrictEqual(DEFAULT_HOOKS, [
-    'handoff-staleness.js', 'fatigue-check.js', 'daemon-outbox-hook.js', 'turn-context.js',
-    'task-bridge.js', 'lease-touch.js', 'stream-delta.js',
+    'daemon-outbox-hook.js', 'turn-context.js', 'task-bridge.js',
   ]);
   for (const f of DEFAULT_HOOKS) assert.ok(fs.existsSync(path.join(__dirname, f)), f + ' exists');
 });

package/core/.claude/hooks/session-init.ps1

@@ -1,49 +1,49 @@
-# Session Start Hook - 显示 Command 选择菜单
-# 当新 session 启动时，提示 Claude 显示可用的 Agent 指令供用户选择
-
-param()
-
-# 读取 stdin 获取 session 信息
-$input = [Console]::In.ReadToEnd()
-$sessionInfo = $input | ConvertFrom-Json -ErrorAction SilentlyContinue
-
-# 检查是否是新启动（不是 resume）
-$source = $sessionInfo.source
-if ($source -eq "startup" -or $source -eq "clear") {
-    # Canary is generated by session.js (buildAssembledPrompt) — not duplicated here.
-
-    # 返回 additionalContext，触发 Claude 显示选择菜单
-    $menuContext = @"
-[SESSION_INIT_TRIGGER]
-新 session 已启动。请立即使用 AskUserQuestion 工具向用户展示 Agent 选择菜单：
-
-可用的 Agent 指令：
-- /產品 - 需求分析、任务规划、PRD 撰写
-- /設計 - UI/UX 设计、设计规范、视觉稿
-- /architect - 系统架构设计
-- /進度 - 查看开发进度
-- /init - 初始化新专案
-
-请用 AskUserQuestion 让用户选择要使用的模式，选项包括：
-1. 产品需求分析 (/產品)
-2. UI/UX 设计 (/設計)
-3. Pipeline 开发 (/dev)
-4. 系统架构设计 (/architect)
-5. 自由对话（不使用特定 Agent）
-
-用户选择后，自动调用对应的 Skill。
-"@
-
-    $additionalContext = $menuContext
-
-    $context = @{
-        hookSpecificOutput = @{
-            hookEventName = "SessionStart"
-            additionalContext = $additionalContext
-        }
-    } | ConvertTo-Json -Depth 10 -Compress
-
-    Write-Output $context
-}
-
-exit 0
+# Session Start Hook - 显示 Command 选择菜单
+# 当新 session 启动时，提示 Claude 显示可用的 Agent 指令供用户选择
+
+param()
+
+# 读取 stdin 获取 session 信息
+$input = [Console]::In.ReadToEnd()
+$sessionInfo = $input | ConvertFrom-Json -ErrorAction SilentlyContinue
+
+# 检查是否是新启动（不是 resume）
+$source = $sessionInfo.source
+if ($source -eq "startup" -or $source -eq "clear") {
+    # Canary is generated by session.js (buildAssembledPrompt) — not duplicated here.
+
+    # 返回 additionalContext，触发 Claude 显示选择菜单
+    $menuContext = @"
+[SESSION_INIT_TRIGGER]
+新 session 已启动。请立即使用 AskUserQuestion 工具向用户展示 Agent 选择菜单：
+
+可用的 Agent 指令：
+- /產品 - 需求分析、任务规划、PRD 撰写
+- /設計 - UI/UX 设计、设计规范、视觉稿
+- /architect - 系统架构设计
+- /進度 - 查看开发进度
+- /init - 初始化新专案
+
+请用 AskUserQuestion 让用户选择要使用的模式，选项包括：
+1. 产品需求分析 (/產品)
+2. UI/UX 设计 (/設計)
+3. Pipeline 开发 (/dev)
+4. 系统架构设计 (/architect)
+5. 自由对话（不使用特定 Agent）
+
+用户选择后，自动调用对应的 Skill。
+"@
+
+    $additionalContext = $menuContext
+
+    $context = @{
+        hookSpecificOutput = @{
+            hookEventName = "SessionStart"
+            additionalContext = $additionalContext
+        }
+    } | ConvertTo-Json -Depth 10 -Compress
+
+    Write-Output $context
+}
+
+exit 0

package/core/.claude/settings.json

@@ -33,16 +33,6 @@
         ]
       }
     ],
-    "Stop": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node -e \"const d=process.env.CLAUDE_PROJECT_DIR||process.cwd();process.chdir(d);require(d+'/.claude/hooks/lease-release.js')\""
-          }
-        ]
-      }
-    ],
     "UserPromptSubmit": [
       {
         "hooks": [
@@ -82,33 +72,6 @@
           }
         ],
         "matcher": "TaskCreate|TaskUpdate"
-      },
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node -e \"const d=process.env.CLAUDE_PROJECT_DIR;process.chdir(d);require(d+'/.claude/hooks/handoff-snapshot-on-commit.js')\""
-          }
-        ],
-        "matcher": "Bash"
-      },
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node -e \"const d=process.env.CLAUDE_PROJECT_DIR;process.chdir(d);require(d+'/.claude/hooks/handoff-snapshot-on-question.js')\""
-          }
-        ],
-        "matcher": "AskUserQuestion"
-      },
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node -e \"const d=process.env.CLAUDE_PROJECT_DIR;process.chdir(d);require(d+'/.claude/hooks/handoff-snapshot-on-decision.js')\""
-          }
-        ],
-        "matcher": "mcp__kenaz-dashboard__synapse_inscribe"
       }
     ]
   },