kenaz 0.3.3 → 0.3.6

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

@@ -12,16 +12,29 @@ ARGUMENTS 含 `[專案: X]` 或 `--project-path X` → PROJECT_PATH = X，下方
 
 ## 每件工作的做法
 - **自己做**：小而明確的修正（約 30 行內、單一檔案或少數檔案）→ 直接改，跑最近的測試，提交。
-- **開卡派工**：中型、可平行、或高風險路徑的工作 → `task-api.js create` 寫清楚驗收條件，再派 subagent（細節讀 `.specialist/Ansuz/RULES.md` 的 Dispatch）。
+- **開卡派工**：中型、可平行、或高風險路徑的工作：
+  1. 用 `kenaz_task_create` 開卡（`projectPath` = 目前專案；寫清楚 requirements、acceptance criteria、scope paths）。查卡、改狀態用 `kenaz_task_list` / `kenaz_task_get` / `kenaz_task_update`。
+  2. 產生派工內容：`node .formation/tools/dispatch.js --skill=do --task=TASK_XXX --dispatch-mode=subagent`（加 `--project-path`；Codex 加 `--harness=codex`）。把輸出 JSON 的 `promptText` 交給 subagent，`agentParams` 照用（模型不要自己換）。
+  3. subagent 在 worktree 裡改完並 commit；你驗證後合併。
 - 開卡前先確認 scope 與驗收條件對準真正的問題，不要照著錯的假設派工。
 
 ## 驗證（合併前一定做，強度跟風險相稱）
 - 走**真實路徑**：實際執行會被使用者用到的那條路（真的安裝、真的啟動、真的收發訊息），不只看單元測試。
 - 有**對照組**：證明測試在舊程式上會失敗，或修改前後結果不同。
 - subagent 回報「未驗證」的項目，由你補驗或明講仍未驗證。
-- 合併用 `.specialist/Ansuz/tools/verify-and-land.js` 或 `git merge` 後跑相關測試；Rust 測試只走 `npm run test:rust` / `dev/scripts/rust-verify-worktree.js`。
+- 合併：`git merge` 後跑相關測試（或 `node .specialist/Ansuz/tools/verify-and-land.js`），用這個專案自己的測試指令。
+- 檔案長度：verify-and-land 合併前會跑 `check-file-size`（警告 1000 / 上限 2000 行，既有超長檔只擋「未配套拆分的增長」）；被擋就按職責拆成 module / component / hook。
+- 只在 Kenaz 核心 repo 本身：Rust 測試走 `npm run test:rust` / `dev/scripts/rust-verify-worktree.js`。
 
 ## 回報
 用用戶的語言。說清楚：做了什麼、怎麼驗證的、還有什麼沒驗證或需要用戶決定。不說「應該可以」。
 
+## Kenaz 本身出問題時：先回報再繞過（wish / field report）
+Kenaz 的工具、hook、安裝、peer 訊息、派工擋住或拖慢工作時（指令失敗、回傳錯的資料、少了能力、行為不如預期），**繞過之前**先呼叫 `kenaz_wish_create`。scope=kenaz 的 wish 會自動送到 Kenaz 團隊成為 field report。
+- `projectPath`：目前專案路徑；`scope`：`kenaz`（Kenaz 本身的問題）或 `project`（只跟這個專案有關）
+- `wish_type`：`bug`（壞了）／`feature`（缺能力，內容寫：需求、現在哪裡不夠、建議做法、還有誰受益）／`question`
+- `content`：一行重現步驟 + 預期 vs 實際 + 版本（`npx kenaz doctor` 那幾行）；附上 session id。不要貼金鑰或 token。
+- 一個問題只報一次；報完照常用替代做法把工作完成，並在回報裡告訴用戶已送出 wish。
+- 用戶直接說「回報這個問題」時也用同一個工具（`source`=`user`）。
+
 需要更多規則時（用戶授權自主、派工前、合併前）讀 `.specialist/Ansuz/RULES.md`。

package/core/.claude/hooks/__tests__/task-2395-project-registration.test.js

@@ -0,0 +1,84 @@
+'use strict';
+// TASK_2395: kenaz init and the first turn-context call per session ask the server to register the
+// project (POST /api/projects/register). The stub server stands in for the Rust route: it writes a
+// temp-HOME projects.json idempotently, so the real ~/.kenaz is never touched.
+const test = require('node:test');
+const assert = require('node:assert/strict');
+const fs = require('node:fs');
+const os = require('node:os');
+const path = require('node:path');
+const http = require('node:http');
+const { spawn } = require('node:child_process');
+
+const REPO = path.resolve(__dirname, '..', '..', '..');
+const KENAZ_MODE = path.join(REPO, 'plugins', 'kenaz', 'scripts', 'kenaz-mode.js');
+const TURN_CONTEXT = path.join(REPO, '.claude', 'hooks', 'turn-context.js');
+
+const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'k2395-'));
+const home = path.join(tmp, 'home');
+const proj = path.join(tmp, 'Ashfall-game');
+fs.mkdirSync(path.join(home, '.kenaz'), { recursive: true });
+fs.mkdirSync(proj, { recursive: true });
+const registryFile = path.join(home, '.kenaz', 'projects.json');
+let posts = 0;
+let server;
+let port;
+
+test.before(async () => {
+  server = http.createServer((req, res) => {
+    let body = '';
+    req.on('data', (c) => { body += c; });
+    req.on('end', () => {
+      if (req.method === 'POST' && req.url === '/api/projects/register') {
+        posts += 1;
+        const p = JSON.parse(body).projectPath;
+        let doc = { projects: [] };
+        try { doc = JSON.parse(fs.readFileSync(registryFile, 'utf8')); } catch { /* new */ }
+        const hit = doc.projects.find((x) => x.path === p);
+        if (!hit) doc.projects.push({ id: 'proj_' + doc.projects.length, name: path.basename(p), path: p });
+        fs.writeFileSync(registryFile, JSON.stringify(doc));
+        res.setHeader('Content-Type', 'application/json');
+        return res.end(JSON.stringify({ success: true, created: !hit }));
+      }
+      res.statusCode = 404;
+      res.end('{}');
+    });
+  });
+  await new Promise((r) => server.listen(0, '127.0.0.1', r));
+  port = server.address().port;
+});
+test.after(() => { server.close(); fs.rmSync(tmp, { recursive: true, force: true }); });
+
+function run(script, args, input) {
+  return new Promise((resolve) => {
+    const env = { ...process.env, HOME: home, USERPROFILE: home, CLAUDE_PROJECT_DIR: proj, KENAZ_HTTP_PORT: String(port) };
+    const child = spawn(process.execPath, [script, ...args], { cwd: proj, env });
+    let out = '';
+    child.stdout.on('data', (c) => { out += c; });
+    child.stderr.on('data', (c) => { out += c; });
+    child.on('close', () => resolve(out));
+    child.stdin.end(input || '');
+  });
+}
+const registered = () => JSON.parse(fs.readFileSync(registryFile, 'utf8')).projects.filter((p) => p.path === proj);
+
+test('kenaz init registers the project, and a second init does not duplicate it', async () => {
+  await run(KENAZ_MODE, ['init']);
+  assert.equal(registered().length, 1);
+  assert.ok(fs.existsSync(path.join(proj, '.kenaz', 'project.yaml')));
+  await run(KENAZ_MODE, ['init']);
+  assert.equal(registered().length, 1);
+  assert.ok(posts >= 2, 'init asks the server every time (the server is the idempotent part)');
+});
+
+test('turn-context registers once per session, again for a new session', async () => {
+  const before = posts;
+  const payload = (sid) => JSON.stringify({ session_id: sid });
+  await run(TURN_CONTEXT, [], payload('sess-1'));
+  assert.equal(posts, before + 1);
+  await run(TURN_CONTEXT, [], payload('sess-1'));
+  assert.equal(posts, before + 1, 'same session: no second call');
+  await run(TURN_CONTEXT, [], payload('sess-2'));
+  assert.equal(posts, before + 2, 'new session asks again');
+  assert.equal(registered().length, 1);
+});

package/core/.claude/hooks/handoff-staleness.js

@@ -20,7 +20,7 @@
  * (HANDOFF_STALE_AFTER_MS) — see TASK_1837/TASK_1838.
  *
  * Dispatch detection (TASK_1830 measurement — two routes, two trace families):
- *   1. kenaz_dispatch / Formation route → .formation/.active-dispatches.json
+ *   1. Formation dispatch route → .formation/.active-dispatches.json
  *      (written by Rust, kenaz.rs). Kept for that route.
  *   2. sub-agent route (Agent tool — the DEFAULT since 2026-06-09) never touches
  *      that file. Its in-project trace is the dispatch brief
@@ -104,7 +104,7 @@ try {
   const { toolUseMentionsAny, taskIdNeedles } = require('./_ansuz-conversation');
   const candidateNeedles = [];
   try {
-    // Route 1: kenaz_dispatch / Formation registry (Rust writer; entries carry taskId).
+    // Route 1: Formation registry (entries carry taskId).
     if (fs.existsSync(dispatchFile)) {
       const dispatches = JSON.parse(fs.readFileSync(dispatchFile, 'utf8'));
       if (Array.isArray(dispatches)) {

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