@reconcrap/boss-recommend-mcp 2.1.6 → 2.1.7

package/README.md

@@ -477,6 +477,7 @@ Trae-CN / 长对话防循环建议：
 
 - `run_recommend` 与 `start_recommend_pipeline_run` 是同一个异步 MCP 启动入口，但不会跳过同步确认流程。
 - `prepare_recommend_pipeline_run` / `boss-recommend-mcp prepare-run` 只做参数门禁；它不启动筛选。普通 MCP 宿主现在运行时，prepare READY 后继续调用 `run_recommend` / `start_recommend_pipeline_run`，不要改用 CLI fallback。
+- `prepare_recommend_pipeline_run` 的 READY 响应会带 `prepared_only=true`、`run_started=false`、`recommended_next_tool=start_recommend_pipeline_run`、`alternate_next_tool=run_recommend` 和 `next_action.do_not_call_prepare_again=true`；agent 应直接照这个字段继续下一步。
 - `schedule_recommend_pipeline_run` / `boss-recommend-mcp schedule-run` 是推荐页定时启动的唯一推荐路径；它创建真实 package-owned detached scheduler，并返回 `schedule_id`。
 - 定时心跳默认 120 秒一次；`updated_at` 仍会在阶段或进度变化时刷新。
 - 每个 run 会持久化到 `~/.boss-recommend-mcp/runs/<run_id>.json`（可通过 `BOSS_RECOMMEND_HOME` 覆盖）。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reconcrap/boss-recommend-mcp",
-  "version": "2.1.6",
+  "version": "2.1.7",
   "description": "Unified MCP pipeline for recommend-page filtering and screening on Boss Zhipin",
   "keywords": [
     "boss",

package/skills/boss-recommend-pipeline/SKILL.md

@@ -96,6 +96,7 @@ description: "Use when users want Boss recommend-page filtering/screening via bo
 - 准备/门禁工具：`prepare_recommend_pipeline_run`
   - 用途：只校验参数是否完整，不启动筛选任务。
   - 要求：若用户要“现在启动”，返回 `status=READY` 且 `cron_ready=true` 后，下一步必须调用 MCP 工具 `run_recommend` 或 `start_recommend_pipeline_run`，禁止改用 CLI fallback。只有用户要“稍后/cron/定时启动”时，才继续创建定时任务。
+  - READY 响应会带 `prepared_only=true`、`run_started=false`、`recommended_next_tool=start_recommend_pipeline_run`、`alternate_next_tool=run_recommend`、`next_action.do_not_call_prepare_again=true`；必须照这些字段继续，不得再次调用 prepare。
   - 若返回 `NEED_INPUT` / `NEED_CONFIRMATION` / `FAILED`：继续补齐 `pending_questions` 或修复登录/页面/config；不得先创建 cron。
 - Cron 创建工具：`schedule_recommend_pipeline_run`
   - 用途：保存已经 READY 的完整 payload，并启动 package-owned detached scheduler；到点后由包内 worker 直接调用 `start_recommend_pipeline_run`。

package/src/recommend-mcp.js

@@ -1563,13 +1563,33 @@ export function prepareRecommendPipelineRunTool({ workspaceRoot = "", args = {}
     };
   }
   const { parsed, normalized } = prepared;
+  const nextAction = {
+    immediate_run: {
+      recommended_next_tool: "start_recommend_pipeline_run",
+      alternate_next_tool: "run_recommend",
+      same_arguments: true
+    },
+    scheduled_run: {
+      recommended_next_tool: "schedule_recommend_pipeline_run",
+      same_arguments: true,
+      requires_schedule_field: true
+    },
+    do_not_call_prepare_again: true,
+    do_not_use_cli_fallback_when_mcp_tools_available: true
+  };
   return {
     status: "READY",
     cron_ready: true,
+    prepared_only: true,
+    run_started: false,
+    recommended_next_tool: nextAction.immediate_run.recommended_next_tool,
+    alternate_next_tool: nextAction.immediate_run.alternate_next_tool,
+    next_action: nextAction,
+    message: "READY only means the payload passed validation; prepare_recommend_pipeline_run did not start a run. To start now, call start_recommend_pipeline_run or run_recommend with the same arguments. Do not call prepare_recommend_pipeline_run again, and do not use CLI fallback when MCP tools are available.",
     review: parsed.review,
     post_action: {
       requested: normalized.postAction,
-      execute_post_action: args.dry_run_post_action === true ? false : args.execute_post_action !== false,
+      execute_post_action: args.dry_run_post_action === true ? false : args.execute_post_action !== false,
       max_greet_count: normalized.maxGreetCount
     },
     target_count_semantics: TARGET_COUNT_SEMANTICS