@xqyz/xq-cli 0.3.3 → 0.3.4

package/CHANGELOG.md

@@ -8,6 +8,23 @@
 
 发布日期以 npm 官方仓库记录为准。发布前必须先更新本文件，再执行版本发布。
 
+## [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 响应依据阶段化选择

package/package.json

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

package/src/cli.mjs

@@ -1928,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) {