@lynn123411/dsh-ask-user-grilling 0.2.3 → 0.2.5

package/README.md

@@ -1,18 +1,16 @@
 # @lynn123411/dsh-ask-user-grilling
 
-DSH 侧的 grilling 适配层（输送机制）：把 Matt Pocock 的 grilling 流程在 DSH 里的提问环节做成工具级硬约束。本插件只提供 `ask_user_grilling`，不提供任何 plan-mode 工具——共识达成后不自动进入 plan mode，交还用户决定下一步。分工：本插件负责「在 DSH 里怎么问」的工具层；grilling 纪律文案里散文预告 + 表单投递写在工具描述与 matt-* 预设 vendor 的 `skills/grilling/SKILL.md` 里（`matt-ptc` 另含 PTC 投递指引），子代理停轮纪律只写在工具描述里（软纪律、无硬拦）、不进 SKILL（避免诱导模型派遣子代理），preset persona 保持原厂原样不做任何修改。
+DSH 原生 `ask_user_question`（[`@deepseek-ai/dsh-tool-ask-user`](https://www.npmjs.com/package/@deepseek-ai/dsh-tool-ask-user)）的**表单呈现变体**：与原生共用同一条 `ctx.userQuestions` seam，工具描述与全部参数描述**与原生逐字相同**，只改表单本身的呈现——强制多选、并自动追加一道轮末补充题。因此它可以直接顶替原生工具而不带来任何提示词漂移，本身不施加任何额外纪律或约束。
 
 > ⚠️ **安装约束：本插件是 preset 工具行消费的 Cordis 插件，严禁加入 profile `package.json` 的 `dsh.profile.bundles`**（bundle 层必须在包内声明 `dsh.bundle`，本插件没有，加入会导致启动报错）。只需通过 `pnpm add` / `dsh plugin --profile web add` 进入 dependencies 即可，preset 的工具行会直接从 node_modules 解析本包。
 
 ## 特性
 
-- **ask_user_grilling**：本 preset 唯一的提问工具（grilling 轮次与一切其他提问都走它——`tool-ask-user` 行已从三份 preset 删除）。
-  - **子代理等齐（软纪律，无硬拦）**：若本轮派了子代理且下轮依赖其结论，优先**结束当前回合**、等全部结算后再问——事实没回就先问只会浪费一轮；子代理运行时提问不再被拒绝；
-  - **强制多选**：所有问题一律多选（schema 不提供关闭开关；此行为刻意**不写入工具描述**——模型若知道只能多选，会为避免互斥选项而影响出题质量，见「描述即纪律」）；
-  - **补充机制**：每题末尾的补充输入框由 UI 自动渲染、轮末补充题由代码自动追加，两者都不依赖模型也不写入描述（模型自加补充项只会与它们重复）；仅当轮末补充输入非空时才应再开一轮；
-  - **题干引导**：要求题干只含问题本身、不重复选项文本（仅模型侧引导，不做硬校验——避免误伤自然提及选项名称的题干）；
-  - **描述即纪律**：工具描述保持精简，只承载工具必知项（以 `lib/index.js` 实物为准：唯一提问工具路由、散文预告 + 同一回合一次投递、字段映射与推荐标记、id 规则、勿自加收尾题、子代理等齐软纪律（无硬闸门））；投递协议细节由技能旁注 DSH delivery 承载，不与工具描述重复；停轮纪律不在技能里写，只由本工具描述现教（软纪律，无硬闸门）。
-- 轮次收尾不自动进入 plan mode：grilling 达成共识后由用户决定继续方式（直接执行、或需要方案时自行 `/plan on`）。
+- **ask_user_grilling**：与原生 `ask_user_question` 同形同名同描述，只改呈现。
+  - **强制多选**：所有问题一律多选——schema 不提供 `multi_select` 参数，也就没有关闭开关。此行为刻意**不写入工具描述**（描述与原生逐字一致）：模型不知道只能多选，才不会为避免互斥选项而影响出题质量；
+  - **轮末补充题**：每次调用由代码自动追加一道「这轮还有什么要补充或调整的吗？（无需补充）」，每题末尾的补充输入框则由 UI 自动渲染——两者都不依赖模型、也不写入描述，模型自加补充项只会与它们重复；
+  - **id 前缀保护**：`__grill_` 开头的 id 会被拒绝（该前缀归自动追加的轮末补充题所有），保证两者不会撞 id；模型侧的 id 描述与原生一致，正常出题不会触发；
+  - **同一条 seam**：直接调 `ctx.userQuestions.ask`，与原生工具走同一通道、行为一致。
 
 ## 安装
 
@@ -22,4 +20,4 @@ dsh plugin --profile web add @lynn123411/dsh-ask-user-grilling
 
 已发布至 npm，供三个 matt 预设（`matt-standard` / `matt-ptc` / `matt-cordis`）使用（preset 的工具行直接消费本包）。
 
-**本地开发**：临时联调可将本目录复制到 `~/.dsh/profiles/web/node_modules/@lynn123411/dsh-ask-user-grilling/`（preset 的工具行会直接从 node_modules 解析），但裸拷贝是未注册状态：`pnpm install` / `dsh plugin add|remove` 等任何 profile 同步都会把它当 extraneous 清掉，并导致三份 matt preset 从模式选择里消失（2026-09-08 真实事故，见 `patches/matt-presets-bootstrap/README.md` §四）——“被清重拷”只是重复踩坑。注意：**不要**把它加进 profile `package.json` 的 `dsh.profile.bundles`（bundle 层必须在包内声明 `dsh.bundle`，否则启动报错）。含未发布改点时调完即发版，再用 `pnpm add` 回装为注册版本。
+**本地开发**：临时联调可将本目录复制到 `~/.dsh/profiles/web/node_modules/@lynn123411/dsh-ask-user-grilling/`（preset 的工具行会直接从 node_modules 解析），但裸拷贝是未注册状态：`pnpm install` / `dsh plugin add|remove` 等任何 profile 同步都会把它当 extraneous 清掉，并导致三份 matt preset 从模式选择里消失（roster 对每份 preset 做行可解析性健康检查，插件被剪即整份隐藏）——“被清重拷”只是重复踩坑。注意：**不要**把它加进 profile `package.json` 的 `dsh.profile.bundles`（bundle 层必须在包内声明 `dsh.bundle`，否则启动报错）。含未发布改点时调完即发版，再用 `pnpm add` 回装为注册版本。

package/lib/index.js

@@ -2,19 +2,18 @@ import { defineTool } from "@deepseek-ai/dsh-tools";
 import "@deepseek-ai/dsh-user-questions";
 
 /**
- * @lynn123411/dsh-ask-user-grilling — DSH delivery adaptations for grilling
- * rounds (mattpocock/skills). No skill file is modified; this package only
- * hardens how rounds are asked inside DSH.
+ * @lynn123411/dsh-ask-user-grilling — a presentation variant of the native
+ * `ask_user_question` (`@deepseek-ai/dsh-tool-ask-user`). Same capability seam
+ * (ctx.userQuestions) and the same tool/parameter descriptions verbatim; only
+ * the rendered form differs.
  *
  * ask_user_grilling:
- *   - no hard gate on running subagents: waiting for settlement is description-level discipline only (soft, was R1)
- *   - forces multi-select on every question (R2)
- *   - appends a round-end supplement question (R3) — per-question supplement is
- *     via the built-in custom input ("Type your answer" / "输入你的答案"), no
- *     extra per-question "Supplement" option to avoid duplication with that
- *     field (see image.png issue: checkbox + input were redundant)
- *   - stem/option separation is guidance only — never rejects stems (R4
- *     relaxed: substring checks false-positive on legitimate stems)
+ *   - forces multi-select on every question — the schema offers no opt-out
+ *   - appends a round-end supplement question; per-question supplement goes
+ *     through the built-in custom input ("Type your answer" / "输入你的答案"),
+ *     so no extra per-question option is added (it would duplicate that field)
+ *   - rejects question ids using the reserved `__grill_` prefix, so the
+ *     auto-appended question can never be shadowed
  */
 const name = "tool-ask-user-grilling";
 const inject = ["tools", "userQuestions"];
@@ -32,12 +31,12 @@ const ROUND_END_QUESTION = {
 function apply(ctx) {
   ctx.tools.register(defineTool({
     name: "ask_user_grilling",
-    description: "Ask the user questions as a form — the only question tool in these presets; route every user-facing question through here, grilling rounds and all other questions alike. For a grilling round, deliver the round the skill had you announce in the message text — the SAME round, ONE call, in the same turn; the prose and the form must match one-to-one. Map each announced question to the fields below (title → header, body → question, the A/B/C choices → options; recommendation as below). Each question needs a stable id matching the Q-number you announced, never starting with __grill_ (reserved for the auto-appended round-end supplement question — never add your own catch-all/\"anything else?\" question; a non-empty supplement input reshapes the tree: ask a further round, and stop asking once the user confirms shared understanding). Mark your recommended option by appending \"(Recommended)\" to its label (any position; if it isn't an option, state it briefly in the question text). If you dispatched subagents whose findings the next round depends on, prefer ending your turn and waiting until all of them have settled before asking — asking the frontier before the facts arrive wastes a round.",
+    description: "Ask the user a concise question when you need confirmation, a choice, or missing information before proceeding. Send one or more questions, each with a stable id that will be echoed in the answer.",
     parameters: {
       questions: {
         type: "array",
         required: true,
-        description: "The current round's questions (round/frontier protocol: see the grilling skill). Each needs a stable id, a stem and options.",
+        description: "Questions to ask the user before continuing.",
         items: {
           type: "object",
           additionalProperties: true,
@@ -45,20 +44,20 @@ function apply(ctx) {
             id: {
               type: "string",
               required: true,
-              description: "Stable id for this question; echoed in the answer. Must NOT start with __grill_ (reserved prefix).",
+              description: "Stable id for this question; echoed in the answer.",
             },
             question: {
               type: "string",
               required: true,
-              description: "The question stem — write only the question. The A/B/C choices belong in options, never in the stem.",
+              description: "The specific question to ask the user.",
             },
             header: {
               type: "string",
-              description: "Optional short heading, e.g. \"Q2 — Deadline\".",
+              description: "Optional short heading for the question, such as \"Confirm\" or \"Choose Mode\".",
             },
             options: {
               type: "array",
-              description: "Choices to show the user. Mark your recommended option by appending \"(Recommended)\" to its label; any list position is fine.",
+              description: "Optional choices to show the user. If you recommend one, put it first and append \"(Recommended)\" to that label.",
               items: {
                 type: "object",
                 additionalProperties: true,
@@ -99,6 +98,7 @@ function apply(ctx) {
           },
           answers: {
             type: "array",
+            required: true,
             description: "One entry per question, in the order asked.",
             items: {
               type: "object",
@@ -128,8 +128,8 @@ function apply(ctx) {
     },
     async execute(args, exec) {
       // 1. input validation: reserved id prefix guard only (the round-end
-      //    question owns __grill_). Stem/option separation (R4) is guidance,
-      //    NOT enforced: substring matching rejected legitimate stems (e.g. a
+      //    question owns __grill_). Stem/option separation is guidance, NOT
+      //    enforced: substring matching would reject legitimate stems (e.g. a
       //    stem that naturally mentions an option name), so no stem check may
       //    refuse a round — a bad stem is preferable to a false rejection.
       const violations = [];
@@ -146,7 +146,7 @@ function apply(ctx) {
         };
       }
 
-      // 2. transform: force multi-select (R2); per-question supplement is via the built-in custom input ("Type your answer"/"输入你的答案") — no extra option is added to avoid duplication with that field
+      // 2. transform: force multi-select; per-question supplement is via the built-in custom input ("Type your answer"/"输入你的答案") — no extra option is added to avoid duplication with that field
       const questions = args.questions.map((question) => ({
         id: question.id,
         question: question.question,
@@ -160,8 +160,11 @@ function apply(ctx) {
         multiSelect: true,
       }));
 
-      // 3. round-end supplement question (R3) — single "无需补充" option; supplement is via custom input, so no "I have something to add" option (duplicates that field)
-      questions.push(ROUND_END_QUESTION);
+      // 3. round-end supplement question — single "无需补充" option; supplement is via custom input, so no "I have something to add" option (duplicates that field)
+      questions.push({
+        ...ROUND_END_QUESTION,
+        options: ROUND_END_QUESTION.options.map((option) => ({ ...option })),
+      });
 
       // 4. ask through the userQuestions seam (UI renders from the service)
       const answer = await ctx.userQuestions.ask({

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lynn123411/dsh-ask-user-grilling",
-  "version": "0.2.3",
-  "description": "DSH delivery adaptations for grilling rounds: ask_user_grilling (sole question tool / forced multi-select / round-end supplement / stem guidance). Does not modify any skill file.",
+  "version": "0.2.5",
+  "description": "Form-presentation variant of the native ask_user_question: same tool and parameter descriptions verbatim, forced multi-select, plus an auto-appended round-end supplement question.",
   "type": "module",
   "main": "lib/index.js",
   "exports": {
@@ -14,9 +14,9 @@
   ],
   "license": "MIT",
   "peerDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-tools": "^0.1.2-alpha.1",
-    "@deepseek-ai/dsh-user-questions": "^0.1.2-alpha.1"
+    "@deepseek-ai/cordis": "^4.0.2",
+    "@deepseek-ai/dsh-tools": "^0.1.5-rc.1",
+    "@deepseek-ai/dsh-user-questions": "^0.1.5-rc.1"
   },
   "engines": {
     "node": "^22.19 || >=24"