@xqyz/xq-cli 0.3.2 → 0.3.4

package/CHANGELOG.md

@@ -10,6 +10,75 @@
 
 ## [Unreleased]
 
+## [0.3.4 / WorkBuddy Plugin 0.10.10] - 2026-08-19
+
+### 快速模式新任务生成链路修复
+
+- 对齐喜鹊 Web：新任务先调用 `/task/preSet` 保存用户配置，其中 `requirement`、`rating`、`plan` 允许为空；随后调用 `/proxy/multiBiddingChoice` 触发后台解析流程。
+- 禁止新任务由 xq-cli 直接调用 `/task/generateByRequirement`，避免抢在 `autoGenerateDirectoryJobHandler` 补齐解析结果之前提交空字段，造成任务停留在大纲解析阶段。
+- 保留历史任务兼容逻辑：仅 `task_status=0` 继续直接调用 `/task/generateByRequirement`。
+- 新增新任务与历史任务两条回归测试。
+
+### WorkBuddy 响应依据完整预览
+
+- “选择大纲依据”卡片改为三个页签：融合响应、仅格式要求、仅评分要求。
+- 页签切换只读取后端返回的完整候选目录树，不会提交 `referenceType` 或改变任务状态。
+- 用户只有点击“按当前思路生成大纲”才会调用既有单次提交链路；仍保留重复提交拦截。
+
+## [0.3.3 / WorkBuddy Plugin 0.10.9] - 2026-08-19
+
+### WorkBuddy 响应依据阶段化选择
+
+- 首次标书配置卡移除“响应依据”，避免在后端候选目录生成前提前提交 `referenceType`。
+- 新增独立依据选择阶段，展示喜鹊返回的三套真实目录预览；选择后只调用依据提交接口并继续同一 `cid` / `runId`。
+- 增加重复提交保护，重复选择不会重新上传、创建任务或提交不同依据。
+- 同步 WorkBuddy MCP App、Skill、Connector 文档与回归测试。
+- xq-cli 新增 `plan reference-select`，依据选择复用原任务且不重复提交篇幅等基础参数。
+
+## [WorkBuddy Plugin 0.10.8] - 2026-08-18
+
+### 规划模式目录修改安全性
+
+- `xique_prepare_directory_update` 改为显式递归目录结构，目录名称使用 `text`，同时兼容并自动归一化旧调用中的 `title` / `name`。
+- 保存前读取后台当前完整目录，自动保留已有节点 ID；遗漏根节点或子节点时默认拒绝，避免局部目录请求被后台解释为删除其他章节。
+- 修复目录修改预览始终显示“根节点数=0”，现在从 `requestPreview.directories` 返回准确的根节点数、总节点数和 ID 保留统计。
+- 保存确认绑定预览时的后台目录签名；确认期间目录变化时拒绝写入。后台保存失败会返回真实原因和“重新查看、重新预览、重新确认”动作，禁止自动重复请求。
+- 保存成功后仍停留在 `directory-review`，不会启动正文；新增覆盖字段归一化、完整树校验、ID 保留、失败单次消费和成功保存的回归测试。
+
+## [WorkBuddy Plugin 0.10.7] - 2026-08-17
+
+### 规划模式目录确认卡
+
+- 修复 `xique_directory_confirmation` 未声明 MCP App 面板元数据，WorkBuddy 只显示文本而不生成目录确认卡的问题。
+- 目录确认准备结果改为紧凑摘要，始终显式返回真实一次性 `confirmationId`，避免完整目录树截断后被误用 `cid`。
+- 目录确认卡和正文继续动作按 `runId`、目录签名自动恢复错误的 `cid`，并支持“确认目录并生成正文”作为有效确认语句。
+- 增加目录确认卡展示、ID 恢复、单次确认和正文门禁回归测试。
+
+## [WorkBuddy Plugin 0.10.6] - 2026-08-17
+
+### 规划模式目录审阅
+
+- 修复 Connector 将目录命令拼成 `xq-cli directory directory view/update`，导致目录已经生成后报 `Unknown directory action: directory` 并停在目录审阅阶段的问题。
+- `xique_directory_view`、目录修改预览和目录修改保存现在分别正确调用 `directory view` / `directory update`，不会重复顶层命令。
+- 增加目录查看、预览修改、确认保存的参数级回归测试，并用真实任务 `a653d3b6e6274a2c91f29bcb28712690` 验证可读回完整 9 章目录。
+
+## [WorkBuddy Plugin 0.10.5] - 2026-08-17
+
+### 规划模式确认调用
+
+- 修复 Connector 调用带子命令的 `xq-cli` 时将 `--json` 放在子命令前，导致 `plan confirm-outline` 被解析为 `plan status` 的问题。
+- 确认智能解读后现在会真正执行 `plan confirm-outline`，从而按前端顺序调用 `setPlanModePhase(1)` 和 `/task/generateDirectoryByCid`。
+- 增加真实参数顺序回归测试；当 CLI 返回错误命令时报告协议错误，不再伪装成后端大纲生成阻塞。
+
+## [WorkBuddy Plugin 0.10.4] - 2026-08-17
+
+### 规划模式确认链路
+
+- 修复 WorkBuddy 将 cid 错传为 confirmationId 时无法继续生成大纲的问题。
+- 智能解读确认卡按同一 runId 自动恢复真实的一次性确认记录，并继续调用 `/task/generateDirectoryByCid`。
+- 新增回归测试覆盖错误 ID、单次消费和同一 runId 恢复。
+
+
 ## [0.3.2] - 2026-08-17
 
 ### xq-cli / WorkBuddy 规划模式
@@ -17,6 +86,7 @@
 - 规划模式首次 `outline --plan-mode 1` 在解析完成后明确返回“智能解读待审核”，不再误报大纲已完成或提前进入正文。
 - WorkBuddy 新增智能解读审核、补充/修正暂存和确认续跑流程；确认时才调用喜鹊 `generateDirectoryByCid` 生成大纲。
 - 新增 CLI 与 WorkBuddy 回归测试，验证同一 `cid` / `runId` 不重复提交。
+- WorkBuddy Plugin `0.10.3` 修正 MCP 初始化指令和内置命令，明确规划模式必须先审核智能解读，再确认生成大纲。
 
 ### xq-cli `0.3.1` / WorkBuddy `0.10.1`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xqyz/xq-cli",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "CLI for xique bid-book task workflows",
   "type": "module",
   "scripts": {

package/src/cli.mjs

@@ -473,6 +473,7 @@ Examples
   xq-cli plan status --cid <cid> --json
   xq-cli plan feedback --cid <cid> --text "Add the missing service boundary"
   xq-cli plan confirm-outline --cid <cid> --yes --wait
+  xq-cli plan reference-select --cid <cid> --reference-type 0 --yes --wait
   xq-cli plan outline-ai-adjust --cid <cid> --prompt "Split chapter 2 into implementation and quality control" --out D:\\output\\
   xq-cli plan outline-ai-apply --cid <cid> --file D:\\output\\outline-ai-<cid>.json --yes
   xq-cli plan directory-generate --cid <cid> --yes --wait
@@ -926,6 +927,10 @@ async function handlePlan(args, state) {
         case 'correction':
             await handlePlanFeedback(args, state);
             return;
+        case 'reference-select':
+        case 'select-reference':
+            await handlePlanReferenceSelection(args, state);
+            return;
         case 'confirm-outline':
         case 'outline-confirm':
         case 'generate-outline':
@@ -973,14 +978,16 @@ async function handlePlan(args, state) {
 async function handlePlanStatus(args, state) {
     const client = createAuthorizedClient(args, state);
     const cid = resolveCid(args, state);
-    const [taskResponse, outlineResponse, contentResponse] = await Promise.all([
+    const [taskResponse, outlineResponse, contentResponse, referenceResponse] = await Promise.all([
         getJson(client, `/task/getTaskDetail/${encodeURIComponent(cid)}`, {}, { retries: DEFAULT_RETRY_COUNT }),
         fetchOutlineDetail(client, cid),
         fetchContentDetail(client, cid),
+        fetchReferenceStatusSafe(client, cid),
     ]);
     const taskDetail = taskResponse?.data || {};
     const outlineDetail = outlineResponse?.data || {};
     const contentDetail = contentResponse?.data || {};
+    const referenceDetail = referenceResponse?.data || {};
     const phase = normalizePlanModePhase(taskDetail.plan_mode_phase);
     const payload = {
         command: 'plan-status',
@@ -991,15 +998,23 @@ async function handlePlanStatus(args, state) {
         taskDetail,
         outlineDetail,
         contentDetail,
+        referenceDetail,
+        referenceStatus: normalizeReferenceStatus(referenceDetail.status),
+        referenceOptions: buildOutlineReferenceChoices(referenceDetail),
         pendingFeedback: normalizePlanFeedback(state.tasks?.[cid]?.planFeedback).length,
     };
     saveTaskSnapshot(state, cid, pickTaskSnapshot({ ...taskDetail, ...contentDetail }));
+    saveTaskSnapshot(state, cid, {
+        referenceStatus: normalizeReferenceStatus(referenceDetail.status),
+        referenceOptions: buildOutlineReferenceChoices(referenceDetail),
+    });
     outputResult(args, payload, [
         `plan status: cid=${cid}`,
         `planMode: ${describeEnumValue(PLAN_MODE_OPTIONS, normalizePlanModeValue(taskDetail.planMode) ?? taskDetail.planMode)}`,
         `phase: ${formatPlanModePhase(phase)}`,
         `outline: ${outlineDetail.outline_status ? 'ready' : 'not-ready'} (${countOutlineRoots({ outlineDetail })} root chapters)`,
         `directory: task_status=${contentDetail.task_status ?? taskDetail.task_status ?? '-'}, directory_status=${contentDetail.directory_portion_status ?? taskDetail.directory_portion_status ?? '-'}`,
+        `reference: status=${normalizeReferenceStatus(referenceDetail.status) ?? '-'}, selected=${state.tasks?.[cid]?.outlineReferenceType ?? '-'}`,
         `pending feedback: ${payload.pendingFeedback}`,
     ]);
     return payload;
@@ -1040,6 +1055,65 @@ async function handlePlanFeedback(args, state) {
     return payload;
 }
 
+async function handlePlanReferenceSelection(args, state) {
+    const client = createAuthorizedClient(args, state);
+    const cid = resolveCid(args, state);
+    const referenceType = parseOutlineReferenceType(stringOption(args, 'referenceType'));
+    if (referenceType === null) {
+        throw new Error('plan reference-select requires --reference-type 0, 1, 2, merge, format, or score.');
+    }
+
+    const snapshot = await hydrateTaskSnapshot(client, state, cid);
+    const previous = parseOutlineReferenceType(snapshot.outlineReferenceType);
+    if (previous !== null) {
+        if (previous !== referenceType) {
+            throw new Error('该任务已经提交过其他响应依据，不能二次修改；请继续查询同一 cid。');
+        }
+        const payload = {
+            command: 'plan-reference-select',
+            cid,
+            referenceType,
+            alreadyApplied: true,
+            duplicateRequestPrevented: true,
+        };
+        outputResult(args, payload, [
+            `reference selection already applied: cid=${cid}, referenceType=${referenceType}`,
+            'duplicate request prevented; continue querying the same task.',
+        ]);
+        return payload;
+    }
+
+    const referenceStatus = await fetchReferenceStatusSafe(client, cid);
+    const referencePhase = normalizeReferenceStatus(referenceStatus?.data?.status);
+    if (referencePhase !== null && referencePhase !== 1) {
+        throw new Error('当前任务不在等待响应依据选择阶段（status=' + referencePhase + '），请先查询 plan status。');
+    }
+    await confirmPlanAction(args, 'select outline reference basis', [
+        `referenceType: ${referenceType}`,
+        'only the backend reference-selection endpoint will be called; the task will not be recreated.',
+    ]);
+    await submitOutlineReferenceType(client, cid, referenceType);
+    saveTaskSnapshot(state, cid, { outlineReferenceType: referenceType, referenceStatus: 1 });
+
+    const waitResult = booleanOption(args, 'wait')
+        ? await waitForOutlineReady(client, state, cid, snapshot.uuid, { ...args, referenceType: undefined }, referenceType)
+        : null;
+    const payload = {
+        command: 'plan-reference-select',
+        cid,
+        referenceType,
+        responseSubmitted: true,
+        waitResult,
+    };
+    outputResult(args, payload, [
+        `reference selection submitted: cid=${cid}, referenceType=${referenceType}`,
+        waitResult?.phase === 'ready'
+            ? `outline ready: rootChapters=${countOutlineRoots(waitResult)}`
+            : 'outline generation is continuing; query plan status for the same task.',
+    ]);
+    return payload;
+}
+
 async function handlePlanOutlineConfirmation(args, state) {
     const client = createAuthorizedClient(args, state);
     const cid = resolveCid(args, state);
@@ -1854,28 +1928,30 @@ function buildOutlineParams(snapshot, args) {
 }
 
 async function triggerOutlineGeneration(client, snapshot, params) {
-    await postJson(client, '/task/preSet', params);
-
-    // task_status=6 means "file parsing" in the Xique backend. It is not a
-    // signal that this is a multi-bid/EPC task. Only route through the
-    // special-selection endpoint when the caller actually supplied a
-    // multi-bid or EPC selection; ordinary tasks must use the normal
-    // generation endpoint even while the task is transitioning from parse.
-    const hasSpecialSelection = Boolean(
-        String(params.multiBidId ?? snapshot.multiBidId ?? '').trim()
-        || String(params.epcEngineerType ?? snapshot.epcEngineerType ?? '').trim()
-    );
-    if (hasSpecialSelection) {
-        await getJson(client, '/proxy/multiBiddingChoice', compactObject({
-            uuid: snapshot.uuid,
-            multiBidId: params.multiBidId ?? snapshot.multiBidId,
-            epcEngineerType: normalizeEpcEngineerTypeForProxy(params.epcEngineerType ?? snapshot.epcEngineerType),
-        }));
-        return 'multiBiddingChoice';
+    // The web flow has two deliberately different paths:
+    //
+    // * legacy tasks (task_status === 0) already contain the parsed
+    //   requirement/rating/plan fields, so they go straight to
+    //   generateByRequirement;
+    // * newly parsed tasks must only persist the user's configuration with
+    //   preSet, then call multiBiddingChoice. That endpoint wakes the async
+    //   parser, and autoGenerateDirectoryJobHandler later fills the three
+    //   parsed fields before it invokes generateByRequirement.
+    //
+    // Calling generateByRequirement here for a new task races that job and
+    // sends empty parsed fields, which leaves the web task stuck in parsing.
+    if (Number(snapshot.task_status) === 0) {
+        await postJson(client, '/task/generateByRequirement', params);
+        return 'generateByRequirement';
     }
 
-    await postJson(client, '/task/generateByRequirement', params);
-    return 'generateByRequirement';
+    await postJson(client, '/task/preSet', params);
+    await getJson(client, '/proxy/multiBiddingChoice', compactObject({
+        uuid: snapshot.uuid,
+        multiBidId: params.multiBidId ?? snapshot.multiBidId,
+        epcEngineerType: normalizeEpcEngineerTypeForProxy(params.epcEngineerType ?? snapshot.epcEngineerType),
+    }));
+    return 'multiBiddingChoice';
 }
 
 async function preparePlanningAnalysis(client, params) {
@@ -2226,9 +2302,9 @@ async function pollTaskUntil(client, state, cid, args, isDone, formatProgress) {
     });
 }
 
-async function waitForOutlineReady(client, state, cid, uuid, args) {
+async function waitForOutlineReady(client, state, cid, uuid, args, initialSubmittedReferenceType = null) {
     const handledIssues = new Set();
-    let submittedReferenceType = null;
+    let submittedReferenceType = initialSubmittedReferenceType;
 
     return pollUntil(async () => {
         const [taskDetail, outlineDetail, referenceStatus] = await Promise.all([