@zhushanwen/pi-ask-user 7.2.0 → 7.2.2

package/ARCHITECTURE.md

@@ -57,7 +57,7 @@ Source: 10 files in `src/`, ~2085 lines total.
 
 `AnswerValue` (`types.ts`) is the single structured answer model — `{ selected: string[]; other: string | null }`. The old internal/proto double model is gone: proto `AskUserOption.value` equaled `label` (both were the same string), so the proto layer consumes the same single model (`Result.answers: Record<string, AnswerValue>`, key = question text).
 
-Serialization happens **once, at the protocol boundary**: `encodeAnswer(value, { key, multiSelect })` in `answer-codec.ts` converts an `AnswerValue` into proto answers entries, byte-aligned with `@xyz-agent/extension-protocol` helpers' decode contract (`getAskUserAnswer` / `getAskUserOther`):
+Serialization happens **once, at the protocol boundary**: `encodeAnswer(value, { key, multiSelect })` in `answer-codec.ts` converts an `AnswerValue` into proto answers entries, byte-aligned with `@zhushanwen/extension-protocol` helpers' decode contract (`getAskUserAnswer` / `getAskUserOther`):
 
 - 单选：`answers[key] = selected[0]`
 - 多选：`answers[key] = JSON.stringify(selected)`
@@ -176,7 +176,7 @@ Constants: `SPLIT_PANE_MIN_WIDTH = 84`, `SPLIT_PANE_LEFT_MIN = 32`, `SPLIT_PANE_
 
 ## Spec cross-reference
 
-The original spec files (`.xyz-harness/2026-06-15-ask-user/`) are no longer in the repo — this table is self-contained (FR = functional requirement from the original spec). Implementation anchors:
+The original spec files (`.taiji-harness/2026-06-15-ask-user/`) are no longer in the repo — this table is self-contained (FR = functional requirement from the original spec). Implementation anchors:
 
 | Spec | Implemented in |
 |------|----------------|

package/README.md

@@ -10,7 +10,7 @@ The tool's primary caller is the LLM. This README covers both **how an agent sho
 pi install npm:@zhushanwen/pi-ask-user
 ```
 
-> **Dev-only symlink**: during local development you may symlink this package into `~/.pi/agent/extensions/` for debugging, but **never use the symlinked copy for daily work**. Local directory discovery has an `index.ts` fallback that masks a missing `pi` manifest field — npm-installed copies then silently fail to load. See the repo root CLAUDE.md "扩展安装红线".
+> **Dev-only symlink**: during local development you may symlink this package into `~/.pi/agent/extensions/` for debugging, but **never use the symlinked copy for daily work**. Local directory discovery has an `index.ts` fallback that masks a missing `pi` manifest field — npm-installed copies then silently fail to load. See `docs/extensions/extension-conventions.md` "扩展安装红线".
 
 ## When to use
 
@@ -138,7 +138,7 @@ All three are consistent and point the same direction. If you tune behavior, edi
 
 ## Spec reference
 
-The original design spec (requirements, functional requirements FR-x, acceptance criteria AC-x, E2E test cases) predates this repository — the original spec files are no longer in the repo. The FR cross-reference table in ARCHITECTURE.md is self-contained: each entry names the behavior and where it is implemented in this codebase.
+Design spec files are not kept in this repo. The FR cross-reference table in ARCHITECTURE.md is self-contained: each entry names the behavior and where it is implemented in this codebase.
 
 ## License
 

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@zhushanwen/pi-ask-user",
-  "version": "7.2.0",
+  "version": "7.2.2",
   "description": "Inline adaptive ask_user tool for Pi — single/multi-question structured input with split-pane preview and an inline free-text editor.",
   "type": "module",
   "main": "index.ts",
-  "xyz-agent": {
+  "taiji": {
     "role": "universal"
   },
   "pi": {
@@ -29,7 +29,7 @@
     "ARCHITECTURE.md"
   ],
   "dependencies": {
-    "@xyz-agent/extension-protocol": "0.11.0",
+    "@zhushanwen/extension-protocol": "0.11.0",
     "@zhushanwen/pi-ext-guards": "0.4.0",
     "@zhushanwen/pi-extension-logger": "0.6.0"
   },

package/src/__tests__/answer-codec.test.ts

@@ -1,9 +1,9 @@
 // src/__tests__/answer-codec.test.ts
 // encodeAnswer 单向序列化 round-trip 测试（TC-09）。
-// 反向验证用 @xyz-agent/extension-protocol 的解码 helper（getAskUserAnswer / getAskUserOther）
+// 反向验证用 @zhushanwen/extension-protocol 的解码 helper（getAskUserAnswer / getAskUserOther）
 // ——该 helper 是 proto answers 格式的唯一解码 SSOT，encode 输出必须与其字节级对齐。
 // m1 增量（TC-01）：property-based describe 作为 5 个确定性用例的随机化超集补充。
-import { getAskUserAnswer, getAskUserOther } from "@xyz-agent/extension-protocol";
+import { getAskUserAnswer, getAskUserOther } from "@zhushanwen/extension-protocol";
 import fc from "fast-check";
 import { describe, expect, it } from "vitest";
 

package/src/__tests__/channel-handler.test.ts

@@ -10,7 +10,7 @@
 //     （single/multi/Other 三种答案形态，经 encodeAnswer 序列化）。
 //   - 取消（askUserInteract/custom 返回 null 或 cancelled）→ {cancelled: true}
 //   - 输入校验（channelPayload 缺失/无 questions）→ {cancelled: true}
-import type { AskUserQuestion } from "@xyz-agent/extension-protocol";
+import type { AskUserQuestion } from "@zhushanwen/extension-protocol";
 import { describe, expect, it } from "vitest";
 
 import { createAskUserChannelHandler } from "../channel-handler";

package/src/__tests__/index.test.ts

@@ -522,7 +522,7 @@ describe("execute — inline render (FR-3)", () => {
 	});
 });
 
-// ── RPC 模式（xyz-agent GUI 富交互协议）──────────────────
+// ── RPC 模式（taiji GUI 富交互协议）──────────────────
 // hasUI=false + ui.select 存在 → 走 askUserInteract（select 通道 + ASK_USER_MARKER）。
 // select 的返回值是前端 JSON.stringify 的 AskUserAnswers，index.ts 做格式转换。
 describe("execute — RPC mode (askUserInteract via select channel)", () => {

package/src/answer-codec.ts

@@ -1,6 +1,6 @@
 // src/answer-codec.ts
 // AnswerValue → proto answers 条目的单向序列化（协议边界 SSOT）。
-// 与 @xyz-agent/extension-protocol helpers.ts 的解码契约字节级对齐：
+// 与 @zhushanwen/extension-protocol helpers.ts 的解码契约字节级对齐：
 //   - 单选：answers[key] = selected[0]
 //   - 多选：answers[key] = JSON.stringify(selected)
 //   - Other：answers[`${key}__other`] = other

package/src/channel-handler.ts

@@ -2,7 +2,7 @@
 //
 // ask_user channel handler：把 subagent 子进程的 ask_user 请求透传到主进程 UI 渲染。
 //
-// 设计（关键决策）：askUserInteract（@xyz-agent/extension-protocol）只在 RPC 模式可用
+// 设计（关键决策）：askUserInteract（@zhushanwen/extension-protocol）只在 RPC 模式可用
 // （内部 isGuiCapable 检查 mode==='rpc'，TUI 下抛错）。所以 handler 按 ctx.mode 分流：
 //   - RPC：转发器——调 askUserInteract(guiCtx, protoQuestions)，复用 select 通道 +
 //     ASK_USER_MARKER 契约，主进程 ctx.ui.select 经 GUI sidecar 渲染（不进 parseSpawnLine，
@@ -21,7 +21,7 @@ import {
 	type AskUserAnswers,
 	askUserInteract,
 	type AskUserQuestion,
-} from "@xyz-agent/extension-protocol";
+} from "@zhushanwen/extension-protocol";
 
 import { AskUserComponent } from "./component";
 import { encodeAnswer } from "./answer-codec";
@@ -71,7 +71,7 @@ function protoToInternalQuestions(protoQuestions: AskUserQuestion[]): Question[]
  * 内部 Result.answers：key = question 全文，value = 结构化 AnswerValue
  * （selected = option label 数组，other = Other 自由文本）。
  *
- * proto AskUserAnswers 契约（@xyz-agent/extension-protocol）：
+ * proto AskUserAnswers 契约（@zhushanwen/extension-protocol）：
  *   - key = question.header ?? question 全文
  *   - 单选：value = 选中项 label string
  *   - 多选：value = JSON.stringify(选中项 label 数组)

package/src/index.ts

@@ -8,7 +8,7 @@ import {
 	type AskUserQuestion,
 	getAskUserAnswer,
 	getAskUserOther,
-} from "@xyz-agent/extension-protocol";
+} from "@zhushanwen/extension-protocol";
 import { toErrorMessage } from "@zhushanwen/pi-ext-guards";
 
 import { createAskUserChannelHandler } from "./channel-handler";
@@ -176,7 +176,7 @@ function protoAnswersToResult(
 }
 
 /**
- * RPC 模式（xyz-agent GUI）交互入口。
+ * RPC 模式（taiji GUI）交互入口。
  *
  * 走 askUserInteract（select 通道 + ASK_USER_MARKER），前端 AskUserOverlay 渲染富交互 UI。
  * 返回 Result（正常/取消），或抛错（select 异常 / 非 RPC 模式调用了此函数）。
@@ -295,7 +295,7 @@ Don't:
 				);
 			}
 
-			// 4. 交互执行：TUI 走 ctx.ui.custom，RPC（xyz-agent GUI）走 askUserInteract。
+			// 4. 交互执行：TUI 走 ctx.ui.custom，RPC（taiji GUI）走 askUserInteract。
 			// 注意：hasUI 在 TUI 和 RPC 模式都为 true（dialog-capable），不能用于区分——
 			// 用 ctx.mode === 'rpc' 判定 GUI 渲染通道。
 			const useRpc = ctx.mode === "rpc";