@ai-setting/roy-agent-core 1.7.70 → 1.7.71

package/dist/shared/@ai-setting/roy-agent-core-4jjwewvw.js

@@ -0,0 +1,182 @@
+// src/env/task/tools/completion-copy.ts
+var TASK_COMPLETE_ITEM_BY_ITEM = "按子项逐条验收";
+var TASK_COMPLETION_HINT_ANCHOR = "TASK_COMPLETION_HINT";
+var TASK_COMPLETE_VERIFY_DUTY = "核实义务";
+
+// src/env/task/prompt/task-discipline.ts
+var TASK_DISCIPLINE_LIFECYCLE = `### Task Lifecycle (7 steps, 0-6)
+
+> Tasks are the **first-class citizen**. Follow this lifecycle for every task:
+
+0. CHECK TASK CONTEXT OR SEARCH
+   - If \`[当前 Task #N]\` is in the context → use \`task_get #N\` directly, skip searching.
+   - Otherwise use \`task_list\` / \`task_search\` to find related tasks.
+   - If found → reuse, extend, and update (see the reuse rules in step 1).
+     If not found → proceed to step 1.
+   - **Orient before creating**: read the existing tree with
+     \`task_tree(depth=1)\` (\`depth=2\` for bigger trees) and decide whether the
+     work belongs to an existing root (attach via \`parent_task_id\`) or is
+     genuinely new. Keep **root tasks ≤ 10**; prefer attaching to an existing
+     thematic root over spawning a new root. Never hardcode ids — read them
+     from \`task_tree\`.
+
+1. CREATE or REUSE
+   - No existing task → create a new one with title, description, goals.
+   - Existing task → reuse via \`task_get\`, then \`task_update\`:
+     * Append new context to description and goals (preserve the old content)
+     * Add / extend \`goals_and_expected_deliverables\`
+     * Create an operation record documenting the continuation
+     * Set priority and due date if any
+     * If the original task was completed → reset status to \`active\`
+       and reset progress to a reasonable value
+
+2. GATHER CONTEXT (never skip)
+   - Read description, goals, current_status
+   - Check \`parent_task_id\` for sub-tasks
+   - Read the operation history: \`task_operation_list\` (~20 recent records)
+   - Review recent operations for history and decisions
+   - Working without context risks: outdated goals, missed decisions,
+     duplicated work, misalignment with the parent task
+
+3. EXECUTE
+   - Use the available tools, skills and workflows to satisfy the task
+     description and goals.
+   - Long-running work: for work longer than 5 minutes, record a milestone
+     with \`task_operation_create\` as you go, so the user can see progress.
+   - Several independent sub-tasks may run in parallel (background \`bash &\`
+     or parallel ReAct steps).
+   - **边干边记** — milestones are recorded **while working**;
+     **禁止事后批量补**（do not defer them to one batch at the end）.
+   - Note: \`task_create\` / \`task_update\` already create operation records
+     automatically — do not create duplicates by hand.
+
+4. TRACK
+   - Update progress (0-100%) as the work advances
+   - Update status: todo → active → completed
+   - Record \`current_status\` with human-readable progress
+
+5. RECORD — operation records (see Operation Discipline below)
+
+6. COMPLETE — \`task_complete\` after item-by-item verification
+   (see Complete Discipline below)`;
+var TASK_DISCIPLINE_OPERATION = `### Operation Record — 双维度分工规范
+
+**Record milestones as you work** — call \`task_operation_create\` the moment a
+stage is reached, **not after the fact** (not in a batch at the end).
+
+**操作记录必须严格区分两个维度，二者配套记录、各司其职**：
+
+#### 维度 1：状态/里程碑（"达到什么"）— 必填维度
+使用 \`task_operation_create\` 的 milestone_* 主字段：
+- **milestone_type**：里程碑类型（create / progress / milestone / problem / solution / decision / review / completed / workflow_extracted）
+- **milestone_title**：里程碑标题（一行）
+- **milestone_description**：达成的状态/结果描述（可长可短）
+
+#### 维度 2：过程（"如何达到"）— 可选但推荐维度
+使用 \`task_operation_create\` 的 \`process_description\` 字段：
+- 字符范围硬约束 100-500 字符 (100–500 characters)
+- 内容：采取的策略 + 工具步骤概要
+- 完整过程通过 sessionId 回查 session
+
+#### 双维度配合铁律
+- ❌ **不要把 action 当状态**：旧 \`action_*\` 命名偏动作/行为层，不能表达"此刻达到什么"；现在统一改用 \`milestone_*\`。
+- ❌ **不要让 process_description 与 milestone_description 重复**：process 是"如何达到"，milestone 是"达到什么状态"。
+- ✅ **配套记录**：每个有意义的 operation 都应同时包含两者；不写 process 时，detail 应通过 sessionId 回查。
+- ⚠️ **兼容窗口期**：旧 \`action_type\` / \`action_title\` / \`action_description\` 仍被 tool 接受（标记 @deprecated），会自动映射到 milestone_* 并返回 deprecation warning。
+
+#### 范例（双维度齐全的 operation 记录）
+\`\`\`json
+{
+  "task_id": 123,
+  "milestone_type": "milestone",
+  "milestone_title": "GREEN 通过：milestone_* schema/storage/tool 全链路",
+  "milestone_description": "21/21 测试通过，包含 4 个 action_* alias 兼容测试",
+  "process_description": "TDD RED 写 4 个失败测试覆盖 storage/tool；迁移 004 rename 列；rowToOperation 同时输出双字段兼容；tool zod preprocess 自动映射 action_*"
+}
+\`\`\``;
+var TASK_DISCIPLINE_GOALS = `### Goals 子项拆分规则
+
+\`goals_and_expected_deliverables\` **MUST** be written as
+**numbered sub-items** (编号子项) that can each be verified
+one by one (逐条验收) — for \`type=normal\` tasks:
+
+1. 实现 X（含文件路径）
+2. 测试 Y 覆盖 Z 场景（pass/fail 计数）
+3. 文档 W 落盘到 <path>
+
+⚠️ For \`type=longterm\` / \`type=cycle\` tasks there is no
+per-item completion acceptance（不走逐条 complete 验收）, so the
+MUST above does not apply; for those, it is **strongly recommended**
+(建议) to split goals into staged, individually checkable sub-items
+(阶段性可判子项) instead of one vague sentence.
+
+Why: when the task is completed, the completion hook
+(task:after.complete) judges the whole goal against the
+operation-record chain, using each sub-item as fine-grained
+evidence (逐条对照的依据). Vague one-line goals (一句话模糊目标，
+如「做好 X」「完成调研」) give the judge nothing to check
+and make a completion hint much more likely.
+
+Reference the four atomic assertion forms (Task #4768
+四原子形态) when writing each sub-item:
+
+- 文件断言 (file assertion): file exists / size / content grep
+- 进程断言 (process assertion): command exit code / stdout match
+- 测试断言 (test assertion): pass/fail counts, no NEW fail
+- 状态断言 (state assertion): version number / HTTP 200 / status field`;
+var TASK_DISCIPLINE_COMPLETE = `### Task Complete — 核实义务
+
+Before calling \`task_complete\`, you MUST:
+
+1. Read the task's \`goal\` (description) and \`delivery\` (goals_and_expected_deliverables) fields.
+   - Use \`task_get(task_id=<id>)\` to fetch the full task record.
+2. **Validate whether each goal sub-item was achieved** — accept the goal
+   **item-by-item** (${TASK_COMPLETE_ITEM_BY_ITEM}).
+   - Goals should be numbered sub-items (编号子项). Check
+     each sub-item against the operation-record chain (操作记录链) and the
+     deliverable evidence (context.deliverable_storage_path).
+   - The completion hook (task:after.complete) judges the whole goal vs.
+     deliverables; numbered sub-items give it finer-grained evidence to
+     reason with (逐条对照的证据粒度). If it detects that the goal or
+     deliverables appear unmet, the task context will carry a
+     \`[${TASK_COMPLETION_HINT_ANCHOR}]\`.
+   - **If you receive a [${TASK_COMPLETION_HINT_ANCHOR}]**, you MUST verify it
+     (${TASK_COMPLETE_VERIFY_DUTY}): re-read the task via \`task_get\`, then do exactly one of:
+     (a) 确认未完成 → \`task_update(task_id=<id>, status=todo)\` to **reopen**
+         the task and continue the work; or
+     (b) 确认已完成 → \`task_operation_create\` (milestone_type=decision,
+         milestone_title=<一行结论>) **state why** the sub-items are actually
+         met (说明理由).
+     Never ignore it (不允许无视).
+   - If the goal and delivery mismatch **without** a hint, either:
+     (a) extend the task via \`task_update\`, or
+     (b) record the discrepancy via \`task_operation_create\`
+         (milestone_type=decision) — the reason **must** land in the
+         operation record (必须落到操作记录里), not merely a line in
+         your final report (不能只在报告里带一句).
+3. **Provide \`deliverable_storage_path\`** parameter with the deliverable's address.
+   It may name **multiple paths** (multiple deliverables), space-separated
+   (\`/tmp/report.md /tmp/diff.patch\`) — the judge splits on whitespace as
+   well as \`,\` \`;\` \`、\` and \` + \`. A local path may also be written in its
+   \`file://\` form (\`file:///tmp/report.md\`) — the scheme is stripped and the
+   path kept. Declare **every** artefact you produced: a path left out reads
+   as "not produced".
+   - Feishu doc URL (e.g., https://my.feishu.cn/docx/abc)
+   - Local file path (e.g., /tmp/report.md)
+   - Git branch or worktree path (e.g., feature/my-feature)
+   - GitHub commit URL or PR URL
+   - Cloud drive URL (e.g., https://my.feishu.cn/file/abc)
+   - Or any other locator that points to where the work product lives
+
+The \`deliverable_storage_path\` will be persisted to the task's
+\`context.deliverable_storage_path\` for future reference and traceability.`;
+var TASK_DISCIPLINE_PROMPT = [
+  TASK_DISCIPLINE_LIFECYCLE,
+  TASK_DISCIPLINE_OPERATION,
+  TASK_DISCIPLINE_GOALS,
+  TASK_DISCIPLINE_COMPLETE
+].join(`
+
+`);
+
+export { TASK_COMPLETE_ITEM_BY_ITEM, TASK_COMPLETION_HINT_ANCHOR, TASK_COMPLETE_VERIFY_DUTY, TASK_DISCIPLINE_LIFECYCLE, TASK_DISCIPLINE_OPERATION, TASK_DISCIPLINE_GOALS, TASK_DISCIPLINE_COMPLETE, TASK_DISCIPLINE_PROMPT };

package/dist/shared/@ai-setting/{roy-agent-core-x3xpkx84.js → roy-agent-core-5repth1n.js}

@@ -1,6 +1,6 @@
 import {
   builtInHandlers
-} from "./roy-agent-core-npvejsg8.js";
+} from "./roy-agent-core-zsbh9bfv.js";
 import {
   envKeyToConfigKey
 } from "./roy-agent-core-7hh0brvs.js";

package/dist/shared/@ai-setting/{roy-agent-core-h5vmff8w.js → roy-agent-core-7sj9xs9c.js}

@@ -5,8 +5,9 @@ import {
 import {
   TASK_COMPLETE_ITEM_BY_ITEM,
   TASK_COMPLETE_VERIFY_DUTY,
-  TASK_COMPLETION_HINT_ANCHOR
-} from "./roy-agent-core-6m4bw8jy.js";
+  TASK_COMPLETION_HINT_ANCHOR,
+  TASK_DISCIPLINE_GOALS
+} from "./roy-agent-core-4jjwewvw.js";
 import {
   getEnvContextOrEmpty,
   init_env_context,
@@ -217,6 +218,9 @@ function inheritChildContext(args) {
 
 // src/env/task/tools/create-tool.ts
 var logger2 = createLogger("task:tools:create");
+var TASK_DISCIPLINE_GOALS_INDENTED = TASK_DISCIPLINE_GOALS.split(`
+`).map((l) => l.trim() ? "      " + l : l).join(`
+`);
 function extractDecisionHint(contextJson) {
   if (!contextJson)
     return;
@@ -320,37 +324,7 @@ function createTaskTool(taskComponent) {
         - Depth ≤ 5 (avoid deep nesting)
         - Same-theme tasks cluster under one parent
         - Long-tail/stranded tasks should be archived or merged
-
-      ## ⚠️ Goals 子项拆分规则 (Task #4791)
-
-      \`goals_and_expected_deliverables\` **MUST** be written as
-      **numbered sub-items** (编号子项) that can each be verified
-      one by one (逐条验收) — for \`type=normal\` tasks:
-
-        1. 实现 X（含文件路径）
-        2. 测试 Y 覆盖 Z 场景（pass/fail 计数）
-        3. 文档 W 落盘到 <path>
-
-      ⚠️ For \`type=longterm\` / \`type=cycle\` tasks there is no
-      per-item completion acceptance（不走逐条 complete 验收）, so the
-      MUST above does not apply; for those, it is **strongly recommended**
-      (建议) to split goals into staged, individually checkable sub-items
-      (阶段性可判子项) instead of one vague sentence.
-
-      Why: when the task is completed, the completion hook
-      (task:after.complete) judges the whole goal against the
-      operation-record chain, using each sub-item as fine-grained
-      evidence (逐条对照的依据). Vague one-line goals (一句话模糊目标，
-      如「做好 X」「完成调研」) give the judge nothing to check and
-      make a completion hint much more likely.
-
-      Reference the four atomic assertion forms (Task #4768
-      四原子形态) when writing each sub-item:
-
-        - 文件断言 (file assertion): file exists / size / content grep
-        - 进程断言 (process assertion): command exit code / stdout match
-        - 测试断言 (test assertion): pass/fail counts, no NEW fail
-        - 状态断言 (state assertion): version number / HTTP 200 / status field
+      ${TASK_DISCIPLINE_GOALS_INDENTED}
 
       ## ⚠️ Spatial + Temporal Context (Task #2325)
 

package/dist/shared/@ai-setting/{roy-agent-core-27f59kjv.js → roy-agent-core-9geem94g.js}

@@ -1,6 +1,6 @@
 import {
   builtInPrompts
-} from "./roy-agent-core-vaz9350j.js";
+} from "./roy-agent-core-zv8bswpw.js";
 import {
   getXDGPath
 } from "./roy-agent-core-qxnbvgwe.js";

package/dist/shared/@ai-setting/{roy-agent-core-hx46nhh1.js → roy-agent-core-k13pxrpk.js}

@@ -1,6 +1,9 @@
 import {
   getSharedEventStore
 } from "./roy-agent-core-na18zwj0.js";
+import {
+  WORKFLOW_EXTRACT_PROMPT
+} from "./roy-agent-core-zv8bswpw.js";
 import {
   createCompatibleDatabase,
   init_sqlite_task_store
@@ -8,9 +11,6 @@ import {
 import {
   TaskHookPoints
 } from "./roy-agent-core-1pg0fepg.js";
-import {
-  WORKFLOW_EXTRACT_PROMPT
-} from "./roy-agent-core-vaz9350j.js";
 import {
   assertNoLeakage,
   buildHintText,
@@ -24,7 +24,7 @@ import {
 import {
   LarkCardPatchNotifier,
   humanizeValue
-} from "./roy-agent-core-tadj19vp.js";
+} from "./roy-agent-core-46rv4d7d.js";
 import {
   validateWorkflowDefinition
 } from "./roy-agent-core-yr1mryb8.js";

package/dist/shared/@ai-setting/{roy-agent-core-nersksh1.js → roy-agent-core-mwa6apzx.js}

@@ -7,7 +7,7 @@ import {
 import {
   BackgroundTaskManager,
   createDelegateTool
-} from "./roy-agent-core-0j94tj1z.js";
+} from "./roy-agent-core-101qtkyc.js";
 import {
   TaskEntityEventTypes
 } from "./roy-agent-core-8gxth0eh.js";
@@ -22,7 +22,7 @@ import {
   searchTasksTool,
   treeTasksTool,
   updateTaskTool
-} from "./roy-agent-core-h5vmff8w.js";
+} from "./roy-agent-core-7sj9xs9c.js";
 import {
   createOperationTool,
   deleteOperationTool,

package/dist/shared/@ai-setting/{roy-agent-core-npvejsg8.js → roy-agent-core-zsbh9bfv.js}

@@ -13,17 +13,17 @@ import {
   createPerTaskGroupChatPlugin,
   extractPerTaskChatId,
   extractPerTaskChatName
-} from "./roy-agent-core-hx46nhh1.js";
+} from "./roy-agent-core-k13pxrpk.js";
 import {
   getSharedEventStore
 } from "./roy-agent-core-na18zwj0.js";
 import {
   createLarkCliWorkflowNotifyHook
-} from "./roy-agent-core-8bjj3d1b.js";
+} from "./roy-agent-core-1w9y7mxj.js";
 import {
   LarkCardPatchNotifier,
   buildTaskCard
-} from "./roy-agent-core-tadj19vp.js";
+} from "./roy-agent-core-46rv4d7d.js";
 import {
   normalizeLarkAtMentions
 } from "./roy-agent-core-m880qz3y.js";
@@ -1720,6 +1720,85 @@ var listCommand = {
   }
 };
 
+// src/env/event-source/reset-command.ts
+import { connect } from "net";
+var DEFAULT_SOCKET_PATH = "/tmp/deamon-for-roy.sock";
+var RESET_ACK_TIMEOUT_MS = 3000;
+function resolveSocketPath() {
+  return process.env.ROY_DAEMON_SOCKET || DEFAULT_SOCKET_PATH;
+}
+async function requestReset(socketPath, reason) {
+  return new Promise((resolve) => {
+    let sock;
+    try {
+      sock = connect(socketPath);
+    } catch (e) {
+      resolve({ confirmed: false, reason: e.message });
+      return;
+    }
+    let settled = false;
+    const finish = (confirmed, why) => {
+      if (settled)
+        return;
+      settled = true;
+      clearTimeout(timer);
+      sock.destroy();
+      resolve({ confirmed, reason: why });
+    };
+    const timer = setTimeout(() => finish(false, `daemon 未在 ${RESET_ACK_TIMEOUT_MS}ms 内确认`), RESET_ACK_TIMEOUT_MS);
+    sock.once("connect", () => {
+      sock.write(JSON.stringify({ type: "reset", reason }) + `
+`);
+    });
+    let buf = "";
+    sock.on("data", (d) => {
+      buf += d.toString();
+      const idx = buf.indexOf(`
+`);
+      if (idx < 0)
+        return;
+      try {
+        const ack = JSON.parse(buf.slice(0, idx));
+        if (ack.type === "ack" && ack.action === "respawning") {
+          finish(true, "daemon 已确认");
+        } else {
+          finish(false, `daemon 回复异常: ${buf.slice(0, idx)}`);
+        }
+      } catch (e) {
+        finish(false, `daemon 回复解析失败: ${e.message}`);
+      }
+    });
+    sock.once("error", (e) => finish(false, `连接 daemon 失败: ${e.message}`));
+  });
+}
+function buildResetCard(text) {
+  return renderTextCard("\uD83D\uDD04 重启请求", text);
+}
+var resetCommand = {
+  name: "reset",
+  description: "请求 deamon-for-roy 重启本进程（SIGTERM 后用最新构建的 roy-agent-local 重新拉起）",
+  usage: "##command##: reset [reason]",
+  async execute(ctx) {
+    const reason = ctx.args.join(" ") || undefined;
+    const socketPath = resolveSocketPath();
+    const { confirmed, reason: why } = await requestReset(socketPath, reason);
+    if (confirmed) {
+      const text2 = "✅ 已请求重启：daemon 将停止本进程并用最新版本重新拉起，请稍候片刻。";
+      return {
+        ok: true,
+        output: { text: text2, card: buildResetCard(text2), kind: "card" }
+      };
+    }
+    const text = `⚠️ 未能联系 daemon，重启请求未生效（${why}）。
+` + `socket: ${socketPath}
+` + `请检查 deamon-for-roy 是否在运行；本进程将继续工作，不会中断。`;
+    return {
+      ok: true,
+      output: { text, card: buildResetCard(text), kind: "card" }
+    };
+  }
+};
+
 // src/env/event-source/command-registry.ts
 var logger2 = createLogger("command-registry");
 var COMMAND_PREFIX = "##command##:";
@@ -1812,6 +1891,7 @@ function getGlobalCommandRegistry() {
     const registry = new CommandRegistry;
     registry.register(fallbackModelCommand);
     registry.register(listCommand);
+    registry.register(resetCommand);
     g.__royCommandRegistry = registry;
   }
   return g.__royCommandRegistry;

package/dist/shared/@ai-setting/{roy-agent-core-vaz9350j.js → roy-agent-core-zv8bswpw.js}

@@ -1,8 +1,9 @@
 import {
   TASK_COMPLETE_ITEM_BY_ITEM,
   TASK_COMPLETE_VERIFY_DUTY,
-  TASK_COMPLETION_HINT_ANCHOR
-} from "./roy-agent-core-6m4bw8jy.js";
+  TASK_COMPLETION_HINT_ANCHOR,
+  TASK_DISCIPLINE_PROMPT
+} from "./roy-agent-core-4jjwewvw.js";
 
 // src/env/prompt/prompts-index.ts
 var builtInPrompts = {
@@ -832,163 +833,7 @@ roy-agent <command> <subcmd> --help
 | \`delegate_task\` | 子 agent 委托入口，由 \`default\` 接待员独占 | 直接用 \`bash\` / \`read_file\` / \`edit_file\` 等工具自己完成任务；若是真正的复杂多步任务，建议用户切换到 \`default\` agent |
 | \`stop_task\` | 后台进程管理入口，由 \`default\` 接待员独占 | 你无法启动后台进程，自然不需要 \`stop_task\` |
 
-### Task Lifecycle
-
-Follow this lifecycle for every task:
-
-\`\`\`text
-┌─────────────────────────────────────────────────────────────────┐
-│ 0. CHECK TASK CONTEXT OR SEARCH                                  │
-│    - First: Check if [当前 Task #N] is in the context            │
-│      If yes → use \`task_get #N\` directly, skip to step 1      │
-│    - If no taskId in context:                                    │
-│      Use \`task_list\` to search for existing related tasks      │
-│    - If found → reuse, extend, and update (see rules below)     │
-│    - If not found → proceed to step 1                           │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 1. CREATE (task_create) OR REUSE (task_get + task_update)       │
-│    - No existing task → Create new with title, desc, goals      │
-│    - Existing task → Reuse via task_get, then task_update:      │
-│      * Append new context to description (preserve old)         │
-│      * Add/extend goals_and_expected_deliverables               │
-│      * Create operation record documenting the continuation     │
-│    - Set priority (low/medium/high) and due date (if any)       │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 2. GATHER CONTEXT (task_get + task_operation_list)              │
-│    - Read description, goals, current_status                      │
-│    - Check parent_task_id for sub-tasks                          │
-│    - Review recent operations for history and decisions           │
-│                                                                   │
-│ ⚠️ REQUIRED: Never skip this step. Working without context       │
-│    risks: outdated goals, missed decisions, duplicated work        │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 3. EXECUTE                                                       │
-│    - 利用各种工具和能力，skill，workflow等来解决任务达到任务描述 │ 
-│      和任务目标要求                                               │
-│                                                                   │
-│ Long-running work guidance:                                       │
-│    - 超过 5 分钟的复杂任务：用 \`task_operation_create\`         │
-│      记录里程碑，让用户能看到实时进展                                │
-│    - 多个独立子任务可并行：用 \`bash &\` 后台启动或                │
-│      拆分成多个并行 ReAct 步骤                                       │
-│                                                                   │
-│ ⚠️ Note: 不需要手动调用 \`task_operation_create\` 跟踪           │
-│    task_create / task_update 等操作也会自动创建记录。            │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 4. TRACK (task_update)                                           │
-│    - Update progress (0-100%) as work advances                  │
-│    - Update status: todo → active → completed                    │
-│    - Can also set paused or cancelled status                    │
-│    - Record current_status with human-readable progress           │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 5. RECORD (task_operation_create) — **双维度分工**               │
-│    - **状态/里程碑维度**：用 milestone_type / milestone_title /   │
-│      milestone_description 描述"达成的状态/里程碑"。             │
-│    - **过程维度**：用 process_description（100-500 字符）         │
-│      简要记录"如何达到"——采取了什么策略 + 工具步骤概要。         │
-│    - ⚠️ **不要把 action 当状态**，也不要让 process_description 与  │
-│      milestone_description 重复。                               │
-│    - 完整过程通过 sessionId 回查 session 历史。                  │
-│    - 这些记录形成任务的历史与上下文。                            │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│ 6. COMPLETE (task_complete)                                      │
-│    - Mark task as completed (progress=100%, status=completed)   │
-│    - ${TASK_COMPLETE_ITEM_BY_ITEM}: check each goal sub-item    │
-│      against the operation-record chain + deliverable evidence  │
-│    - If a [${TASK_COMPLETION_HINT_ANCHOR}] appears in task      │
-│      context, you MUST ${TASK_COMPLETE_VERIFY_DUTY}: reopen     │
-│      (task_update status=todo) or record why it is met          │
-│      (task_operation_create decision). Never ignore it.         │
-│    - Create completion operation record                         │
-└─────────────────────────────────────────────────────────────────┘
-\`\`\`
-
-### Task Update Rules
-
-When reusing an existing task, you MUST follow these rules:
-
-1. **Append, don't replace** — When using \`task_update\`, the \`description\` and \`goals\` fields MUST **preserve existing content** and append new content after it.
-2. **Document the continuation** — Use \`task_operation_create\` to create an operation record explaining why the task is being continued and what new scope has been added.
-3. **Reset the status** — If the original task was completed, change status to \`active\` and reset progress to a reasonable value.
-
-### Task Properties
-
-| Property | Description |
-|----------|-------------|
-| **title** | Brief task title |
-| **description** | Detailed description of what needs to be done |
-| **goals_and_expected_deliverables** | Clear success criteria and expected outputs |
-| **status** | todo → active → completed (or paused, cancelled) |
-| **progress** | 0-100 percentage of completion |
-| **current_status** | Human-readable status describing current work |
-| **priority** | low, medium, high |
-| **parent_task_id** | Parent task ID (if this is a sub-task) |
-
-### Task Operation Record — 双维度分工规范 (Task #2211)
-
-**操作记录必须严格区分两个维度，二者配套记录、各司其职**：
-
-#### 维度 1：状态/里程碑（"达到什么"）— 必填维度
-使用 \`task_operation_create\` 的 milestone_* 主字段：
-- **milestone_type**：里程碑类型（create / progress / milestone / problem / solution / decision / review / completed）
-- **milestone_title**：里程碑标题（一行）
-- **milestone_description**：达成的状态/结果描述（可长可短）
-
-#### 维度 2：过程（"如何达到"）— 可选但推荐维度
-使用 \`task_operation_create\` 的 \`process_description\` 字段：
-- 字符范围硬约束 100-500 字符
-- 内容：采取的策略 + 工具步骤概要
-- 完整过程通过 sessionId 回查 session
-
-#### 双维度配合铁律
-- ❌ **不要把 action 当状态**：旧 \`action_*\` 命名偏动作/行为层，不能表达"此刻达到什么"；现在统一改用 \`milestone_*\`。
-- ❌ **不要让 process_description 与 milestone_description 重复**：process 是"如何达到"，milestone 是"达到什么状态"。
-- ✅ **配套记录**：每个有意义的 operation 都应同时包含两者；不写 process 时，detail 应通过 sessionId 回查。
-- ⚠️ **兼容窗口期**：旧 \`action_type\` / \`action_title\` / \`action_description\` 仍被 tool 接受（标记 @deprecated），会自动映射到 milestone_* 并返回 deprecation warning。
-
-#### 范例（双维度齐全的 operation 记录）
-\`\`\`json
-{
-  "task_id": 123,
-  "milestone_type": "milestone",
-  "milestone_title": "GREEN 通过：milestone_* schema/storage/tool 全链路",
-  "milestone_description": "21/21 测试通过，包含 4 个 action_* alias 兼容测试",
-  "process_description": "TDD RED 写 4 个失败测试覆盖 storage/tool；迁移 004 rename 列；rowToOperation 同时输出双字段兼容；tool zod preprocess 自动映射 action_*"
-}
-\`\`\`
-
-### Task Context Awareness
-
-**Before starting any task-related work, you MUST gather context:**
-
-**Step 0: Check for Task ID in Context**
-- If the system provides \`[当前 Task #N]\` in the context messages:
-  Use \`task_get #N\` directly — this is your confirmed task. **Skip searching.**
-- If no taskId is provided, use \`task_list\` to search for existing related tasks.
-
-**Then gather full context:**
-1. **Read task details**: Use \`task_get\` to read description, goals, status
-2. **Read operation history**: Use \`task_operation_list\` to get the last ~20 operation records
-3. **Read parent context** (if \`parent_task_id\` exists): Understand overall goal
-
-**Why context matters**: Without it, you risk:
-- Working on outdated or wrong goals
-- Missing critical decisions made in operations
-- Losing parent task alignment
-- Duplicating or conflicting work
-
+${TASK_DISCIPLINE_PROMPT}
 ### {{memory}}`,
   coding: `You are an expert coding assistant.
 

package/dist/test-utils/ipc-test-server.d.ts

@@ -0,0 +1,10 @@
+export interface TestIpcServer {
+    socketPath: string;
+    /** last parsed JSON request received from a client */
+    lastRequest: Record<string, unknown> | null;
+    start(): Promise<void>;
+    stop(): Promise<void>;
+}
+export declare function createIpcServer(opts?: {
+    replyDelayMs?: number;
+}): TestIpcServer;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-setting/roy-agent-core",
-  "version": "1.7.70",
+  "version": "1.7.71",
   "type": "module",
   "description": "Core SDK for roy-agent - Environment, Components, Tools, Sessions, Tasks",
   "main": "./dist/index.js",
@@ -13,6 +13,11 @@
       "require": "./dist/index.js",
       "default": "./dist/index.js"
     },
+    "./env/task/prompt": {
+      "import": "./dist/env/task/prompt/index.js",
+      "types": "./dist/env/task/prompt/index.d.ts",
+      "default": "./dist/env/task/prompt/index.js"
+    },
     "./env/task/plugins": {
       "import": "./dist/env/task/plugins/index.js",
       "types": "./dist/env/task/plugins/index.d.ts",

package/dist/shared/@ai-setting/roy-agent-core-6m4bw8jy.js

@@ -1,6 +0,0 @@
-// src/env/task/tools/completion-copy.ts
-var TASK_COMPLETE_ITEM_BY_ITEM = "按子项逐条验收";
-var TASK_COMPLETION_HINT_ANCHOR = "TASK_COMPLETION_HINT";
-var TASK_COMPLETE_VERIFY_DUTY = "核实义务";
-
-export { TASK_COMPLETE_ITEM_BY_ITEM, TASK_COMPLETION_HINT_ANCHOR, TASK_COMPLETE_VERIFY_DUTY };