@ai-setting/roy-agent-core 1.7.57 → 1.7.59

package/dist/env/error-reply.d.ts

@@ -57,9 +57,10 @@
  *   都不得向上抛，绝不污染原始错误传播链
  * - **有硬超时**：兜底 reply 在 5s 内一定 settle（超时 kill 子进程）。
  *   否则 lark-cli 卡住会把 `QueryExecutor` 的 rethrow 拖死 → 事件队列堵死
- * - **复用现有机制**：spawn 参数形态与 `LarkCliNotificationChannel` /
- *   `event-source-handlers.sendLarkMessage` 保持一致（`--profile` 前置、
- *   messageId → `+messages-reply`、chatId → `+messages-send`）
+ * - **复用现有机制**：spawn 参数形态与 `event-source-handlers.sendLarkMessage`
+ *   / `lark-card-patch-notifier.buildSendCardArgs` / `telemetry-notice.buildLarkSendArgs`
+ *   保持一致（`--profile` 前置、messageId → `+messages-reply`、
+ *   chatId → `+messages-send`、**两支都显式 `--as bot`**）
  * - **去重**：同一 triggerEvent（messageId）只回一次；chat-only 通道走
  *   5 分钟窗口，**不会**把整个群永久封锁；发送失败回滚去重标记
  * - **无 channel 不崩但也不静默**：本地 REPL / `act` 没有飞书上下文 → debug；

package/dist/env/event-source/event-source-handlers.d.ts

@@ -5,7 +5,7 @@
  * 支持通过 handleRule.plugins 加载外部 Plugin
  */
 import { ChildProcess } from "child_process";
-import type { EventSourceConfig, EventSourceHandler, EventSourceInstance, EventSourceStatus, EventSourceEventHandler, EventMetadata, ReplyChannel, RecommendedAction } from "./types";
+import type { EventSourceConfig, EventSourceHandler, EventSourceInstance, EventSourceStatus, EventSourceEventHandler, EventMetadata, ReplyChannel, RecommendedAction, RuleNoticeInfo } from "./types";
 import { timerHandler } from "./timer-handler";
 import { bountyIMHandler } from "./bounty-im-handler";
 import { bountyCliHandler } from "./bounty-cli-handler";
@@ -469,6 +469,16 @@ export declare class LarkCliInstance implements EventSourceInstance {
      */
     private sendLarkMessage;
 }
+/**
+ * 渲染「系统回执」小节 —— 告诉主 agent：群里**已经**看到了什么。
+ *
+ * 三种状态必须分开，否则 agent 会二选一地犯两种错：
+ *   - 已送达却把「已超时」再讲一遍 → 重复刷屏
+ *   - 未送达却以为发了 → 用户永远不知道任务结束了（正是 #4561 的现场）
+ *
+ * @param headline 事件标题句（未送达时要求 agent 自己讲清这个事实）
+ */
+export declare function renderRuleNoticeSection(ruleNotice: RuleNoticeInfo | undefined, headline: string): string;
 /**
  * LarkCli Handler
  */

package/dist/env/event-source/index.d.ts

@@ -3,7 +3,7 @@
  *
  * 导出所有 EventSource 相关的类型、类和函数
  */
-export type { EventSourceStatus, EventSourceType, EventSourceConfig, EventMetadata, RecommendedAction, ReplyChannel, EventSourceEventPayload, EventSourceEvent, EventSourceEventHandler, EventSourceStatusChangeEvent, EventSourcePersistenceConfig, EventSourceInstance, EventSourceHandler, EventSourceInitHook, EventSourceComponentInterface, EventSourceAgentHandlerConfig, } from "./types";
+export type { EventSourceStatus, EventSourceType, EventSourceConfig, EventMetadata, RecommendedAction, ReplyChannel, EventSourceEventPayload, EventSourceEvent, EventSourceEventHandler, EventSourceStatusChangeEvent, EventSourcePersistenceConfig, EventSourceInstance, EventSourceHandler, EventSourceInitHook, EventSourceComponentInterface, EventSourceAgentHandlerConfig, NotifyChannelInfo, RuleNoticeInfo, } from "./types";
 export { EventSourceInitHooks } from "./types";
 export { BUILT_IN_EVENT_SOURCE_TYPES, BUILT_IN_EVENT_SOURCE_TYPE_LIST } from "./types";
 export { isBuiltInEventSourceType, isValidEventSourceType, getDefaultConfigForType, validateEventSourceConfig, } from "./types";

package/dist/env/event-source/index.js

@@ -11,7 +11,7 @@ import {
   larkCliHandler,
   resolveBountyIMSystemPrompt,
   timerHandler
-} from "../../shared/@ai-setting/roy-agent-core-jw5ar4p0.js";
+} from "../../shared/@ai-setting/roy-agent-core-6q5m1qk5.js";
 import {
   BUILT_IN_EVENT_SOURCE_TYPES,
   BUILT_IN_EVENT_SOURCE_TYPE_LIST,

package/dist/env/event-source/types.d.ts

@@ -580,6 +580,55 @@ export interface ReplyContext {
     /** lark-cli profile（用于 im +messages-reply --profile） */
     profile?: string;
 }
+/**
+ * 触发渠道信息（渠道无关的最小集合）。
+ *
+ * 由 CLI EventHandler 从 trigger event + handler.extractReplyContext 解析后
+ * 传给 buildNotifyHandlePrompt，让 prompt 能按**真实渠道**渲染：
+ *   - 渠道类型（lark-cli / bounty-im / timer / ...）
+ *   - 群 ID / 群聊还是私聊
+ *   - 触发消息 ID、发送者、profile
+ *
+ * ★ 为什么不让每个 handler 自己从 triggerEvent 里抠字段：
+ *   bounty-im 用 from/to 邮箱、lark 用 chatId/messageId，字段名完全不同；
+ *   统一在这里归一化，handler 只负责渲染「怎么发」。
+ */
+export interface NotifyChannelInfo {
+    /** EventSource 类型（lark-cli / bounty-im / timer / ...） */
+    esType: string;
+    /** 回复目标会话 ID（飞书为 oc_xxx） */
+    chatId?: string;
+    /** 群聊 / 私聊 / 未知（飞书 trigger event metadata.chatType） */
+    chatType?: "group" | "p2p" | "unknown";
+    /** 触发消息 ID（飞书为 om_xxx）；reply 这条可保持话题线索 */
+    messageId?: string;
+    /** 触发者 ID（飞书为 ou_xxx） */
+    senderId?: string;
+    /** 多 appId 场景的 lark-cli profile */
+    profile?: string;
+    /** 回复方式：reply=回复触发消息 / send=新消息 / none=无可用通道 */
+    replyKind?: "reply" | "send" | "none";
+}
+/**
+ * 规则化回执（rule-based direct notice）的投递结果。
+ *
+ * 终态事件（completed / timeout）在进 lane 之前，会先用 telemetry 同一套
+ * 发送器直发一条**保底**消息到触发群；这里把「发没发出去」如实带给主 agent，
+ * 避免 prompt 谎称「已发送」而 agent 又重复/遗漏关键信息。
+ */
+export interface RuleNoticeInfo {
+    /** 是否尝试过直发（false = 该事件类型不在规则回执白名单） */
+    attempted: boolean;
+    /** 是否确实送到群里 */
+    delivered: boolean;
+    chatId?: string;
+    /** 实际发出的文案（送达时带，便于 prompt 里告知「回执已经说了什么」） */
+    text?: string;
+    /** 送达时刻（epoch ms） */
+    sentAt?: number;
+    /** 失败原因（未送达时带） */
+    error?: string;
+}
 /**
  * buildNotifyHandlePrompt 输入
  */
@@ -591,6 +640,12 @@ export interface BuildNotifyHandlePromptInput {
         description?: string;
         result?: string;
         error?: string;
+        /**
+         * 子 session ID —— 超时 / 失败后如需**续跑**，主 agent 可直接
+         * `delegate_task(existingSubSessionId=<此值>, ...)` 让子代理继承历史继续推进，
+         * 不必从零重来。
+         */
+        subSessionId?: string;
     };
     /** 触发整个 delegate_task 的原始 event（从 EventStore 反查） */
     triggerEvent: PersistedEvent;
@@ -605,6 +660,19 @@ export interface BuildNotifyHandlePromptInput {
      * 让主 agent 拿到的回复命令带上正确的 `--profile`。
      */
     profile?: string;
+    /**
+     * 触发渠道信息（渠道无关，由调用方归一化后传入）。
+     *
+     * 缺省时 handler 自行从 triggerEvent 反查（向后兼容）。
+     */
+    channel?: NotifyChannelInfo;
+    /**
+     * 规则化回执的投递结果。
+     *
+     * 缺省 = 本事件不直发回执（如 failed / stopped / ask_user），
+     * prompt 需要引导 agent 把结果完整讲清楚。
+     */
+    ruleNotice?: RuleNoticeInfo;
 }
 /**
  * buildNotifyHandlePrompt 输出

package/dist/env/index.d.ts

@@ -16,7 +16,7 @@ export type { Task, TaskOperation, TaskStatus, TaskPriority, ActionType, CreateT
 export { McpComponent, } from "./mcp";
 export type { McpComponentConfig, McpComponentOptions, McpPath, McpServerConfig, McpServerStatus, DiscoveredMcpServer, } from "./mcp";
 export { EventSourceComponent, larkCliHandler, builtInHandlers, } from "./event-source/event-source-component";
-export type { EventSourceConfig, EventSourceStatus, EventSourceType, EventSourceEvent, EventSourceEventPayload, EventSourceEventHandler, EventSourceStatusChangeEvent, EventSourcePersistenceConfig, EventSourceComponentInterface, EventSourceHandler, EventSourceInstance, EventSourceAgentHandlerConfig, BUILT_IN_EVENT_SOURCE_TYPES, } from "./event-source/types";
+export type { EventSourceConfig, EventSourceStatus, EventSourceType, EventSourceEvent, EventSourceEventPayload, EventSourceEventHandler, EventSourceStatusChangeEvent, EventSourcePersistenceConfig, EventSourceComponentInterface, EventSourceHandler, EventSourceInstance, EventSourceAgentHandlerConfig, NotifyChannelInfo, RuleNoticeInfo, BUILT_IN_EVENT_SOURCE_TYPES, } from "./event-source/types";
 export { EventSourceInitHooks, isValidEventSourceType, isBuiltInEventSourceType, getDefaultConfigForType, validateEventSourceConfig, } from "./event-source/types";
 export { WorkflowComponent, } from "./workflow/workflow-component";
 export type { WorkflowComponentConfig, } from "./workflow/workflow-component";

package/dist/env/index.js

@@ -3,19 +3,19 @@ import {
 } from "../shared/@ai-setting/roy-agent-core-84rs0c8d.js";
 import {
   TaskComponent
-} from "../shared/@ai-setting/roy-agent-core-ewcc5qdt.js";
+} from "../shared/@ai-setting/roy-agent-core-991pk4ss.js";
 import"../shared/@ai-setting/roy-agent-core-amkqnyzy.js";
 import"../shared/@ai-setting/roy-agent-core-7q4wdze2.js";
 import"../shared/@ai-setting/roy-agent-core-vh0qzb24.js";
 import"../shared/@ai-setting/roy-agent-core-rn57psp0.js";
 import"../shared/@ai-setting/roy-agent-core-8gxth0eh.js";
-import"../shared/@ai-setting/roy-agent-core-1sfbs57v.js";
+import"../shared/@ai-setting/roy-agent-core-6bradb0j.js";
 import"../shared/@ai-setting/roy-agent-core-14bq77wr.js";
 import {
   EventSourceComponent,
   builtInHandlers,
   larkCliHandler
-} from "../shared/@ai-setting/roy-agent-core-jw5ar4p0.js";
+} from "../shared/@ai-setting/roy-agent-core-6q5m1qk5.js";
 import {
   EventSourceInitHooks,
   getDefaultConfigForType,

package/dist/env/plugin/index.js

@@ -86,7 +86,9 @@ ${options.content}`;
           "--chat-id",
           chatId,
           "--markdown",
-          normalizedContent
+          normalizedContent,
+          "--as",
+          "bot"
         ];
       }
       if (profile) {

package/dist/env/plugin/lark-cli-notification-channel.d.ts

@@ -19,10 +19,19 @@
  *
  * ## spawn lark-cli
  *
- * - messageId 走 `lark-cli im +messages-reply --message-id <id> --markdown <md>`
- * - chatId 走 `lark-cli im +messages-send --chat-id <id> --markdown <md>`
+ * - messageId 走 `lark-cli im +messages-reply --message-id <id> --markdown <md> --as bot`
+ * - chatId 走 `lark-cli im +messages-send --chat-id <id> --markdown <md> --as bot`
  * - profile 不为 undefined 时在 args 头部插入 `--profile <name>`
  *
+ * ⚠️ **两支都必须显式 `--as bot`**（Task #4557）。chatId 分支历史上漏了，
+ * 不带 flag 时 lark-cli 用默认身份 = **user（真人账号）** 发出 →
+ * `lark-cli event consume im.message.receive_v1` 只看「是不是 user 发的」→
+ * 自己的通知被同一个 consumer 回灌成「用户消息」→ 又跑一次完整 agent run。
+ * Task #4552 在同类路径实测回灌率 **5/11 = 45%**，补 flag 后 **0/5 = 0%**
+ * （证据：本机 E2E 报告 `reports/4552-a1-real-e2e.md` §6（`reports/` 被 .gitignore 忽略，未入库））。
+ * 本 channel 虽 `@deprecated` 但仍是 opt-in 可启用实现，所以同样必须修。
+ * 失败即 reject → 由 `send()` 层 swallow + warn，**绝不降级成 user**。
+ *
  * ## 失败处理
  *
  * - spawn 失败 / exit code != 0 → swallow（log warn，notification 失败不污染 Plugin 主流程）

package/dist/env/task/delegate/delegate-tool.d.ts

@@ -49,6 +49,20 @@ export interface BackgroundTaskStartedPayload {
     parentSessionId: string;
     description: string;
     subagentType: string;
+    /**
+     * ★ Task #4552 (A1)：任务启动时刻（epoch ms）。
+     *
+     * 消费端（CLI EventHandler）把 telemetry 降级成一条纯 IM 进展提示后，
+     * 文案要回答「跑了多久」，只能从这里读。缺失时文案降级（不渲染「已跑」）。
+     */
+    startedAt?: number;
+    /**
+     * ★ Task #4552 (A1)：本任务被允许的运行时长（毫秒）。
+     *
+     * 让用户看到「预计 17:23 超时（timeout 5h）」，避免以为「早该有结论了」——
+     * 这正是 Task #4552 报障的认知错位（用户 16:40 以为超时，实际 17:23 才超）。
+     */
+    timeoutMs?: number;
 }
 export interface BackgroundTaskProgressPayload {
     backgroundTaskId: string;
@@ -58,6 +72,10 @@ export interface BackgroundTaskProgressPayload {
     progress?: number;
     description?: string;
     associatedTaskId?: number;
+    /** ★ Task #4552 (A1)：见 BackgroundTaskStartedPayload.startedAt */
+    startedAt?: number;
+    /** ★ Task #4552 (A1)：见 BackgroundTaskStartedPayload.timeoutMs */
+    timeoutMs?: number;
 }
 export interface BackgroundTaskCompletedPayload {
     backgroundTaskId: string;
@@ -191,6 +209,14 @@ export interface BackgroundTask {
     /** Timestamp of the latest lifecycle state change or progress notification. */
     lastUpdatedAt?: number;
     startedAt?: number;
+    /**
+     * ★ Task #4552 (A1)：本任务被允许的运行时长（毫秒，createTask 时确定）。
+     *
+     * 存到 task 上而不是每次重算：progress 心跳发生在 20 分钟后，那时
+     * `timeout` 参数已不在作用域内，只能靠这里。同时保证 started / progress
+     * 两条通知给出同一个超时时刻。
+     */
+    timeoutMs?: number;
     completedAt?: number;
     result?: string;
     error?: string;

package/dist/env/task/delegate/index.js

@@ -3,7 +3,7 @@ import {
   BackgroundTaskManager,
   createDelegateTool,
   createStopTool
-} from "../../../shared/@ai-setting/roy-agent-core-1sfbs57v.js";
+} from "../../../shared/@ai-setting/roy-agent-core-6bradb0j.js";
 import"../../../shared/@ai-setting/roy-agent-core-14bq77wr.js";
 import"../../../shared/@ai-setting/roy-agent-core-2ctyjy62.js";
 import"../../../shared/@ai-setting/roy-agent-core-1pg0fepg.js";

package/dist/env/task/index.js

@@ -5,7 +5,7 @@ import {
   TaskPriorityEnum,
   TaskStatusEnum,
   TaskTypeEnum
-} from "../../shared/@ai-setting/roy-agent-core-ewcc5qdt.js";
+} from "../../shared/@ai-setting/roy-agent-core-991pk4ss.js";
 import"../../shared/@ai-setting/roy-agent-core-amkqnyzy.js";
 import"../../shared/@ai-setting/roy-agent-core-7q4wdze2.js";
 import"../../shared/@ai-setting/roy-agent-core-vh0qzb24.js";
@@ -13,7 +13,7 @@ import"../../shared/@ai-setting/roy-agent-core-rn57psp0.js";
 import {
   TaskEntityEventTypes
 } from "../../shared/@ai-setting/roy-agent-core-8gxth0eh.js";
-import"../../shared/@ai-setting/roy-agent-core-1sfbs57v.js";
+import"../../shared/@ai-setting/roy-agent-core-6bradb0j.js";
 import"../../shared/@ai-setting/roy-agent-core-14bq77wr.js";
 import {
   SQLiteTaskStore,

package/dist/index.js

@@ -63,13 +63,13 @@ import {
 } from "./shared/@ai-setting/roy-agent-core-84rs0c8d.js";
 import {
   TaskComponent
-} from "./shared/@ai-setting/roy-agent-core-ewcc5qdt.js";
+} from "./shared/@ai-setting/roy-agent-core-991pk4ss.js";
 import"./shared/@ai-setting/roy-agent-core-amkqnyzy.js";
 import"./shared/@ai-setting/roy-agent-core-7q4wdze2.js";
 import"./shared/@ai-setting/roy-agent-core-vh0qzb24.js";
 import"./shared/@ai-setting/roy-agent-core-rn57psp0.js";
 import"./shared/@ai-setting/roy-agent-core-8gxth0eh.js";
-import"./shared/@ai-setting/roy-agent-core-1sfbs57v.js";
+import"./shared/@ai-setting/roy-agent-core-6bradb0j.js";
 import"./shared/@ai-setting/roy-agent-core-14bq77wr.js";
 import {
   BountyIMInstance,
@@ -83,7 +83,7 @@ import {
   larkCliHandler,
   resolveBountyIMSystemPrompt,
   timerHandler
-} from "./shared/@ai-setting/roy-agent-core-jw5ar4p0.js";
+} from "./shared/@ai-setting/roy-agent-core-6q5m1qk5.js";
 import {
   BUILT_IN_EVENT_SOURCE_TYPES,
   BUILT_IN_EVENT_SOURCE_TYPE_LIST,

package/dist/shared/@ai-setting/{roy-agent-core-1sfbs57v.js → roy-agent-core-6bradb0j.js}

@@ -1207,6 +1207,7 @@ class BackgroundTaskManager {
       status: "pending",
       createdAt,
       lastUpdatedAt: createdAt,
+      timeoutMs: timeout || DEFAULT_TIMEOUT,
       abortController,
       similarTaskIds,
       triggerEventId,
@@ -1219,7 +1220,9 @@ class BackgroundTaskManager {
       subSessionId: subSession.id,
       parentSessionId,
       description,
-      subagentType
+      subagentType,
+      startedAt: createdAt,
+      timeoutMs: timeout || DEFAULT_TIMEOUT
     };
     this.publishBackgroundEvent(BackgroundTaskEventTypes.STARTED, startedPayload, parentSessionId, triggerEventId, replyChannelSnapshot);
     this.executeTask(taskIdGen, prompt, timeout, parentSessionId).catch((err) => {
@@ -1403,7 +1406,9 @@ class BackgroundTaskManager {
         parentSessionId,
         description: task.description,
         status: task.status,
-        associatedTaskId: task.associatedTaskId
+        associatedTaskId: task.associatedTaskId,
+        startedAt: task.createdAt,
+        timeoutMs: task.timeoutMs
       };
       this.publishBackgroundEvent(BackgroundTaskEventTypes.PROGRESS, progressPayload, parentSessionId, task.triggerEventId, task.replyChannel);
     }, PROGRESS_INTERVAL);

package/dist/shared/@ai-setting/{roy-agent-core-jw5ar4p0.js → roy-agent-core-6q5m1qk5.js}

@@ -1402,7 +1402,9 @@ function spawnLarkReply(options) {
         "--chat-id",
         chatId,
         "--markdown",
-        normalizedContent
+        normalizedContent,
+        "--as",
+        "bot"
       ];
     } else {
       finish(new Error("No target specified for failure reply"));
@@ -2501,7 +2503,6 @@ class LarkCliInstance {
           chatId: replyChannel.chatId,
           userId: replyChannel.params?.userId,
           content: text,
-          as: "bot",
           profile
         });
       },
@@ -2510,7 +2511,6 @@ class LarkCliInstance {
           chatId: replyChannel.chatId,
           userId: replyChannel.params?.userId,
           content: markdown,
-          as: "bot",
           format: "markdown",
           profile
         });
@@ -2520,7 +2520,6 @@ class LarkCliInstance {
           chatId: replyChannel.chatId,
           userId: replyChannel.params?.userId,
           content: JSON.stringify(content),
-          as: "bot",
           profile
         });
       },
@@ -2529,7 +2528,6 @@ class LarkCliInstance {
           await this.sendLarkMessage({
             messageId: replyChannel.messageId,
             content: JSON.stringify(content),
-            as: "bot",
             profile
           });
         }
@@ -2538,16 +2536,16 @@ class LarkCliInstance {
   }
   async sendLarkMessage(options) {
     return new Promise((resolve, reject) => {
-      const { chatId, userId, messageId, content, as: identity, format = "text", profile } = options;
+      const { chatId, userId, messageId, content, format = "text", profile } = options;
       const normalizedContent = normalizeLarkAtMentions(content);
       const contentFlag = format === "markdown" ? "--markdown" : "--text";
       const args = ["im"];
       if (messageId) {
-        args.push("+messages-reply", "--message-id", messageId, "--as", identity, contentFlag, normalizedContent);
+        args.push("+messages-reply", "--message-id", messageId, "--as", "bot", contentFlag, normalizedContent);
       } else if (chatId) {
-        args.push("+messages-send", "--chat-id", chatId, "--as", identity, contentFlag, normalizedContent);
+        args.push("+messages-send", "--chat-id", chatId, "--as", "bot", contentFlag, normalizedContent);
       } else if (userId) {
-        args.push("+messages-send", "--user-id", userId, "--as", identity, contentFlag, normalizedContent);
+        args.push("+messages-send", "--user-id", userId, "--as", "bot", contentFlag, normalizedContent);
       } else {
         reject(new Error("No target specified for sending message"));
         return;
@@ -2623,6 +2621,24 @@ function describeNotifyEvent(type, taskId, desc) {
       return { headline: `Sub-agent 更新了 Task #${taskId}「${desc}」。`, actionable };
   }
 }
+function renderRuleNoticeSection(ruleNotice, headline) {
+  if (!ruleNotice || !ruleNotice.attempted) {
+    return `（本事件不直发规则回执）
+` + `→ 你的回复要把结果讲**完整**（用户只能从你这条消息知道结论）。`;
+  }
+  if (ruleNotice.delivered) {
+    const when = ruleNotice.sentAt ? new Date(ruleNotice.sentAt).toLocaleTimeString("zh-CN", {
+      hour12: false,
+      hour: "2-digit",
+      minute: "2-digit"
+    }) : "";
+    const sent = ruleNotice.text ? `：「${ruleNotice.text.replace(/\s*\n+\s*/g, " ")}」` : "";
+    return `✅ 系统已于 ${when || "刚才"} 把下面这条发到群里${sent}
+` + `→ 你的回复**只发增量**：不要再重复「任务已结束」这类回执原文，` + `直接讲结论/交付 + 下一步选项。`;
+  }
+  return `❌ **回执未送达**（原因：${ruleNotice.error ?? "unknown"}）
+` + `→ 用户目前**还不知道**「${headline}」这件事，必须由你在回复里讲清楚，` + `并且不要假装系统已经通知过。`;
+}
 var larkCliHandler = {
   type: "lark-cli",
   validateConfig(config) {
@@ -2685,47 +2701,67 @@ var larkCliHandler = {
       senderOpenId: input.triggerEvent.metadata?.senderId ?? input.triggerEvent.senderId,
       profile: input.profile
     };
-    const profileFlag = ctx.profile ? `--profile ${ctx.profile} ` : "";
+    const esType = input.channel?.esType ?? ctx.esType ?? "lark-cli";
+    const chatId = input.channel?.chatId || ctx.chatId;
+    const messageId = input.channel?.messageId || ctx.messageId;
+    const senderId = input.channel?.senderId || ctx.senderOpenId;
+    const chatType = input.channel?.chatType ?? "unknown";
+    const profile = input.channel?.profile ?? ctx.profile;
+    const profileFlag = profile ? `--profile ${profile} ` : "";
     const desc = input.notifyEvent.description ?? "(未命名任务)";
     const result = input.subAgentResult.summary ?? input.notifyEvent.result ?? "";
     const notifyType = input.notifyEvent.type;
     const taskId = input.notifyEvent.taskId ?? "?";
     const { headline, actionable } = describeNotifyEvent(notifyType, taskId, desc);
+    const chatTypeLabel = chatType === "group" ? "群聊" : chatType === "p2p" ? "私聊" : "会话类型未知";
+    const canReply = Boolean(chatId);
+    const receiptSection = renderRuleNoticeSection(input.ruleNotice, headline);
+    const replyCommand = messageId ? `lark-cli ${profileFlag}im +messages-reply --message-id ${messageId} --chat-id ${chatId} --as bot --markdown '<你的回复>'` : `lark-cli ${profileFlag}im +messages-send --chat-id ${chatId} --as bot --markdown '<你的回复>'`;
+    const scopeWord = chatType === "group" ? "群聊" : chatType === "p2p" ? "私聊" : "会话";
     const promptText = actionable ? `
 ## Notify Event: ${notifyType}
 
 ${headline}
 
-### Trigger event（原始飞书消息，来自 EventStore 反查）
-- ES: lark-cli
-- **chatId: ${ctx.chatId}**  ← 关键！必须回复到这里
-- **messageId: ${ctx.messageId}**  ← 必须 reply 这条
-- sender: ${ctx.senderOpenId}
-${ctx.profile ? `- profile: ${ctx.profile}  ← 调用 lark-cli 必须带 --profile
+### 触发渠道（EventSource）
+- ES: ${esType}（飞书，${chatTypeLabel}）
+- **chatId: ${chatId || "(缺失)"}**  ← 关键！必须发到这里
+- **messageId: ${messageId || "(缺失)"}**  ← ${messageId ? "reply 这条，保持话题线索" : "无触发消息，用 +messages-send"}
+- sender: ${senderId || "(未知)"}
+${input.notifyEvent.subSessionId ? `- 子 session: ${input.notifyEvent.subSessionId}  ← 如需续跑：delegate_task(existingSubSessionId=<此值>, prompt=<新要求>)
+` : ""}${profile ? `- profile: ${profile}  ← 调用 lark-cli 必须带 --profile
 ` : ""}
+### 系统回执（rule-based 直发）
+${receiptSection}
+
 ### Sub-agent 输出
 ${result}
 
-### \uD83D\uDC49 你应该这样做
-用 lark-cli 调 im +messages-reply：
-  lark-cli ${profileFlag}im +messages-reply --message-id ${ctx.messageId} --chat-id ${ctx.chatId} --as bot --msg-type text --content '<你的回复>'
+### \uD83D\uDC49 你要做什么
+1. 用 2~5 行总结：这次完成了什么 / 卡在哪（依据上面的输出与子 session）
+2. 给出 1~3 个下一步选项（继续推进 / 拆小 / 放弃），并**问用户选哪个**
+3. 用 lark-cli 把回复发到上面的${scopeWord}（见下）
+
+### 发送方式（渠道 = lark-cli）
+${canReply ? `  ${replyCommand}` : `⚠️ 没有可用的 chatId —— 无法投递到触发会话。请在会话内汇报，并说明「未投递」的原因。`}
 
 ⚠️ 不要 fallback 到 lastReplyChannel 或 metadata.replyChannel — 那个 chatId
 可能跟用户原始消息的 chatId 不一致（参见 #4035/#4038/#4039 bug）。
+⚠️ 必须 --as bot（否则会被自己的 lark-cli consumer 当用户消息回灌）；不要用 user 身份。
 ` : `
 ## Notify Event: ${notifyType}
 
 ${headline}
 
-### Trigger event
-- ES: lark-cli
-- chatId: ${ctx.chatId}
-- messageId: ${ctx.messageId}
+### 触发渠道（EventSource）
+- ES: ${esType}（${chatTypeLabel}）
+- chatId: ${chatId || "(缺失)"}
+- messageId: ${messageId || "(缺失)"}
 
 （这是中间态通知：仅作状态同步，**不要**回复用户，也不要调用 lark-cli 发消息。
 等收到 task.background.completed / failed / timeout / stopped 终态通知后再回复。）
 `;
-    const systemHint = actionable ? `回复必须用 lark-cli im +messages-reply（${profileFlag.trim() ? `带 ${profileFlag.trim()}；` : ""}` + `chatId=${ctx.chatId} / messageId=${ctx.messageId} 来自 trigger event，不要 fallback。` : `这是 ${notifyType} 中间态通知，不要回复用户；仅等待终态通知。`;
+    const systemHint = actionable ? `回复必须用 lark-cli im +messages-reply（${profileFlag.trim() ? `带 ${profileFlag.trim()}；` : ""}` + `chatId=${chatId} / messageId=${messageId} 来自 trigger event（esType=${esType}），不要 fallback。` + (input.ruleNotice?.delivered ? "系统回执已送达，只发增量。" : "") : `这是 ${notifyType} 中间态通知，不要回复用户；仅等待终态通知。`;
     return { promptText, systemHint };
   },
   setRunner(runner) {

package/dist/shared/@ai-setting/{roy-agent-core-ewcc5qdt.js → roy-agent-core-991pk4ss.js}

@@ -27,7 +27,7 @@ import {
   BackgroundTaskManager,
   createDelegateTool,
   createStopTool
-} from "./roy-agent-core-1sfbs57v.js";
+} from "./roy-agent-core-6bradb0j.js";
 import {
   SQLiteTaskStore,
   getDefaultTaskDbPath

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-setting/roy-agent-core",
-  "version": "1.7.57",
+  "version": "1.7.59",
   "type": "module",
   "description": "Core SDK for roy-agent - Environment, Components, Tools, Sessions, Tasks",
   "main": "./dist/index.js",