@shgroup/dsh-serenity-hooks 1.37.0 → 1.38.0

package/lib/index.js

@@ -5,8 +5,8 @@ import { i as cccRootForExec, n as agentCwdFor, o as listCccs, r as cccRootForCw
 import { a as readWeixinCredential, c as weixinInboundDir, d as LOCALSTORE_SCOPES, f as checkLocalstoreGitCompliance, g as runLocalStore, h as readStore, i as matchWeixinRoute, l as weixinSessionIdFor, m as readGitTrack, n as extractWeixinText, o as readWeixinSettings, p as localstorePath, r as hasVoiceItem, s as sanitizeFileName$1, t as extractWeixinMedia } from "./weixin-route-B2ajFypI.js";
 import { a as readSkiffRoles, c as roleMsmWhitelist, d as systemPromptSource, f as trajectorySubset, i as isSkiffSessionId, l as roleToolWhitelist, n as buildSkiffBasePrompt, o as resolveRoleSystemPrompt, r as createRolePromptReader, s as resolveSkiffKind } from "./skiff-role-CEHL5cek.js";
 import { a as unregisterSkiffSession$1, i as skiffSessionSnapshot$1, n as skiffRoleFor$1, r as skiffSessionInfo$1, t as registerSkiffSession$1 } from "./skiff-registry-FTjoWQTQ.js";
-import { _ as sessionsRoot, a as DEFAULT_SESSION_SCOPE, b as summarize, c as createSession, d as getActiveSessionInfo, f as listSessions, g as sessionEvents$1, h as resolveSessionByTitle, i as resolveSessionTrajectoryLabel, l as extractSessionMdPathFromText, m as readActiveSessionMd, n as listBoundSessionIds, o as TRAJECTORY_ACTIONS, p as parseSessionContextFromEvents, r as readLastBound, s as clearActiveSessionInfo, t as appendBound, u as findSession, v as setActiveSessionInfo, x as useSession, y as showSession } from "./trajectory-bound-DETSEBpL.js";
-import { a as splitDueWakes, i as loadWakeRegistry, n as addWake, o as updateWake, r as listWakes, t as WAKE_CATCH_UP_MS } from "./wake-registry-Cj2aSHME.js";
+import { _ as sessionsRoot, a as DEFAULT_SESSION_SCOPE, b as summarize, c as createSession, d as getActiveSessionInfo, f as listSessions, g as sessionEvents$1, h as resolveSessionByTitle, i as resolveSessionTrajectoryLabel, l as extractSessionMdPathFromText, m as readActiveSessionMd, o as TRAJECTORY_ACTIONS, p as parseSessionContextFromEvents, r as readLastBound, s as clearActiveSessionInfo, t as appendBound, u as findSession, v as setActiveSessionInfo, x as useSession, y as showSession } from "./trajectory-bound-U3ZU_mI6.js";
+import { a as WAKE_CATCH_UP_MS, i as registerDisposer, n as sendToTrajectory, o as addWake, r as wakeSchedulerState, s as listWakes, t as registerWakeScheduler } from "./wake-scheduler-Ebdyvzuq.js";
 import { a as FACE_PORTS, c as MECHANISM_PORTS, i as ACP_HTTP_PORT, l as SKIFF_DEBUG_PORT, n as registerSettingsSection, o as GATEWAY_PORT, s as MAIN_WEB_PORT, t as readSimpleSettings, u as WEIXIN_SEND_PORT } from "./settings-section-DMDUoQum.js";
 import { a as markdownToPlainText, c as sendTyping, i as getUpdates, l as sniffImageExt, n as downloadMedia, o as sendFileMessage, r as getConfig, s as sendTextMessage, t as TypingStatus } from "./weixin-api-CtFYm53S.js";
 import z from "@deepseek-ai/schemastery";
@@ -955,7 +955,7 @@ const NPX_BIN = process.platform === "win32" ? "npx.cmd" : "npx";
 const ACC_CATALOG = `═══ ACC Usage Catalog ═══
 Directory of ACC capabilities — each area lists where to go for details (guides live with their feature; this catalog only points).
 
-  ① 轨迹本体          → container_trajectory（list/show/create/use + rebuild 超限重建 + wake-later 未来一次性唤醒）
+  ① 轨迹本体          → container_trajectory（list/show/create/use + rebuild 超限重建 + wake-later 未来一次性唤醒 + send-message 即时投递）
                          原 logbook 已并入（v1.33 用户裁决：废除 logbook 词）；close/archive 删（归档走 container_fs mv），
                          health/qa/summary 分别并入 use / list，hook-develop-guide 并进 container_admin msm guide
   ② 认知质量框架      → praxis（eap/neat/cce 三合一——可实践理论注入，section 渐进披露，无参即目录）
@@ -966,6 +966,7 @@ Directory of ACC capabilities — each area lists where to go for details (guide
   ④ 角色与对外面      → container_admin role（Skiff 认知子集角色：guide/validate/apply/list——skiff_admin 已并入）
                          ACP（程序化 JSON-RPC 3100）/ Skiff 问答页（公网 ask）——面板「外部能力」组
   ⑤ 自主与接入        → container_trajectory wake-later（跨轨迹的"未来时刻 + 一条 message"；fire-and-forget，无回执无回收）
+                         container_trajectory send-message（跨轨迹的**即时**递送：live 目标立即注入，非 live 冷载入——等效于直接 wake；**有同步回执**）
                          weixin 微信桥（配置/扫码/路由/消息 hook——CCC 侧 weixin-doctor MSM：msm("weixin-doctor", ["guide"])）
   ⑥ CCC 配置总览      → container_admin msm ccc-config（9 段：handyman/sessionKeeper/localstore/hooks/safeMode/skiff/trajectory/weixin/**exclusiveTools**）
   ⑦ 注册表与安全      → mech-registry.json 由 container_admin msm register/deregister 管理（写保护——不可直接编辑）
@@ -1866,7 +1867,7 @@ function waitAgentIdle(ctx, agent) {
 }
 //#endregion
 //#region src/skiff-core.ts
-const PLUGIN_SOURCE$6 = {
+const PLUGIN_SOURCE$5 = {
 	kind: "plugin",
 	plugin: "dsh-serenity-hooks"
 };
@@ -2274,7 +2275,7 @@ async function askSkiff(ctx, agent, question, eventsStart, options) {
 			type: "text",
 			text: question
 		}],
-		source: PLUGIN_SOURCE$6
+		source: PLUGIN_SOURCE$5
 	}));
 	await waitAgentIdle(ctx, agent);
 	const answer = lastAssistantText$2(agent);
@@ -2972,6 +2973,10 @@ function createHandymanTool(ctx) {
 * `container_trajectory`，无别名）——trajectory 是一等概念
 * （SESSION.md 是它的持久身体），本工具管它的**载体生命周期 + 一次性时间安排**。
 * 动作收敛为 **6 个**：list / show / create / use / rebuild / wake-later。
+* 🔴 2026-09-16（所有者裁决）：**第 7 个动作 `send-message`（即时投递）**
+*    ——与 `wake-later` 共用取用通路，差别只在**时刻**（现在 vs 未来）与**回执**（有 vs 无）；
+*    实现落在 `wake-scheduler.ts` 的 `sendToTrajectory()`（"怎么把一句话送到一条轨迹"是调度器的知识）。
+*    设计稿 = `docs/trajectory-send-message-design.md`（v0.2 定稿）。
 *
 * 与旧面（logbook 11 动作 + trajectory 12 动作）的对应（用户逐条裁决，R↓）：
 *   · `summary` → 并入 `list`（全库统计随清单一起给）
@@ -3114,13 +3119,13 @@ function renderText$3(value) {
 function createTrajectoryTool(ctx) {
 	return defineTool({
 		name: "container_trajectory",
-		description: "Trajectory (AGENT_SESSIONS/ — the persistent body of a trajectory; the dsh conversation is only its rebuildable carrier). Lifecycle + one-shot scheduling: list (inventory with stats and anomaly marks) / show (read one SESSION.md) / create / use (activate for this conversation, with inline integrity check) / rebuild (clear-and-rebuild the current conversation in place, Ship of Theseus) / wake-later (schedule ONE message to any trajectory at a future instant — fire-and-forget: no receipt, no recall, no panel). create requires --desc <desc> [--goal] or --issue <ticket> (exactly one) plus --summary (≤20 chars). use requires --summary (≤20 chars) and may pass --force to switch away from the currently-bound trajectory. rebuild requires --summary (next-phase summary ≤20 chars) + optional --note (task focus for the rebuilt self). wake-later requires target (S### or AGENT_SESSIONS dir name) + at (RFC3339 or +30m/+2h) + message. The summary is appended to the dsh session title (S###-YYYY-MM-DD-<summary>); the S### id and date stay server-derived.",
+		description: "Trajectory (AGENT_SESSIONS/ — the persistent body of a trajectory; the dsh conversation is only its rebuildable carrier). Lifecycle + delivery: list (inventory with stats and anomaly marks) / show (read one SESSION.md) / create / use (activate for this conversation, with inline integrity check) / rebuild (clear-and-rebuild the current conversation in place, Ship of Theseus) / wake-later (schedule ONE message to any trajectory at a future instant — fire-and-forget: no receipt, no recall, no panel) / send-message (deliver ONE message to a trajectory RIGHT NOW — live: injected immediately; not live: cold-resumed, i.e. equivalent to a direct wake; returns a synchronous receipt). create requires --desc <desc> [--goal] or --issue <ticket> (exactly one) plus --summary (≤20 chars). use requires --summary (≤20 chars) and may pass --force to switch away from the currently-bound trajectory. rebuild requires --summary (next-phase summary ≤20 chars) + optional --note (task focus for the rebuilt self). wake-later requires target (S### or AGENT_SESSIONS dir name) + at (RFC3339 or +30m/+2h) + message. send-message requires target + message. Its receipt means the message was QUEUED into the target (it does NOT mean the target ran or replied; a busy target applies it at its next round boundary). The summary is appended to the dsh session title (S###-YYYY-MM-DD-<summary>); the S### id and date stay server-derived.",
 		parameters: {
 			action: {
 				type: "string",
 				enum: [...TRAJECTORY_ACTIONS],
 				required: true,
-				description: "Subcommand: list (inventory + stats + anomaly marks) / show (S### or dir name or fuzzy keyword) / create (--desc or --issue) / use (activate context; inline integrity check — pass silent, problems reported as hints, not errors) / rebuild (clear-and-rebuild current conversation — requires --summary + optional --note) / wake-later (one future instant + one message, delivered to target trajectory)"
+				description: "Subcommand: list (inventory + stats + anomaly marks) / show (S### or dir name or fuzzy keyword) / create (--desc or --issue) / use (activate context; inline integrity check — pass silent, problems reported as hints, not errors) / rebuild (clear-and-rebuild current conversation — requires --summary + optional --note) / wake-later (one future instant + one message, delivered to target trajectory) / send-message (deliver one message RIGHT NOW: live target injected immediately, non-live cold-resumed like a direct wake; returns a synchronous receipt)"
 			},
 			name: {
 				type: "string",
@@ -3156,7 +3161,7 @@ function createTrajectoryTool(ctx) {
 			},
 			target: {
 				type: "string",
-				description: "wake-later: target trajectory (S### or AGENT_SESSIONS directory name)"
+				description: "wake-later/send-message: target trajectory (S### or AGENT_SESSIONS directory name)"
 			},
 			at: {
 				type: "string",
@@ -3164,7 +3169,7 @@ function createTrajectoryTool(ctx) {
 			},
 			message: {
 				type: "string",
-				description: "wake-later: the single message delivered to the target trajectory"
+				description: "wake-later/send-message: the single message delivered to the target trajectory"
 			}
 		},
 		output: {
@@ -3271,6 +3276,24 @@ function createTrajectoryTool(ctx) {
 						output: `✓ 已登记唤醒\n${renderWakeEntry(res.entry)}`
 					};
 				}
+				case "send-message": {
+					if (!args.target || !args.message) throw new Error("send-message requires target (S### or dir name) + message");
+					const sendScope = agentScope$2(exec);
+					const res = await sendToTrajectory(ctx, root, args.target, args.message, resolveSessionTrajectoryLabel(exec.agent?.session, sendScope === "default" ? "" : sendScope));
+					if (!res.ok) return {
+						ok: false,
+						error: res.detail
+					};
+					return {
+						ok: true,
+						output: [
+							"✓ 已即时投递",
+							`  · ${res.detail}`,
+							"  · 语义：消息**已进入目标队列**；目标若正在跑轮次，则在**轮次边界**生效（不打断当前轮）。",
+							"  · ⚠️ 回执只到「已入队」——**不表示**目标已执行或已答复。判\"目标真的动了\"须看它自己的 SESSION.md（文件级判据）。"
+						].join("\n")
+					};
+				}
 				default: throw new Error(`Unknown action: ${args.action}`);
 			}
 		}
@@ -4767,7 +4790,7 @@ function trajectoryCompactionReminderText(input) {
 	if (escalated) return `${eventToken("compaction")} ${facts} — you have been reminded repeatedly and have NOT compacted SESSION.md. This is now mandatory: STOP the current task step, load eap (praxis eap), rewrite SESSION.md, then resume. ${principles} ${frontmatterGuard} This reminder persists until the file is under the limit.`;
 	return `${eventToken("compaction")} ${facts}. Pause the current work and compact this trajectory's log (SESSION.md) before continuing — that log is the persistent body of this trajectory, and its size is operational entropy (H_op) the container pays on every read. ${principles} ${frontmatterGuard} After rewriting, resume the paused work; this reminder stops once the file is under the limit.`;
 }
-const PLUGIN_SOURCE$5 = {
+const PLUGIN_SOURCE$4 = {
 	kind: "plugin",
 	plugin: "dsh-serenity-hooks"
 };
@@ -4853,7 +4876,7 @@ function registerKeeper(ctx, opts = {}) {
 		if (blocks.length === 0) return downstream;
 		const reminderAll = createUserMessage({
 			content: blocks,
-			source: PLUGIN_SOURCE$5
+			source: PLUGIN_SOURCE$4
 		});
 		if (downstream.kind === "block") return {
 			kind: "block",
@@ -5575,7 +5598,7 @@ function toolsBlock() {
 		"The ACC (this plugin) provides the following built-in tools:",
 		"",
 		"  container_fs — container filesystem operations (15 subcommands: root/resolve/exists/list/tree/relative/mkdir/rm/mv/cp/touch/append/reveal/info/find)",
-		"  container_trajectory — one trajectory: its persistent body (SESSION.md) + its timeline. Lifecycle: list (inventory + stats) / show / create / use (activate; inline integrity check — silent when fine) / rebuild (clear-and-rebuild this conversation in place, Ship of Theseus); scheduling: wake-later (one future instant + one message to any trajectory; fire-and-forget — no receipt, no recall)",
+		"  container_trajectory — one trajectory: its persistent body (SESSION.md) + its timeline. Lifecycle: list (inventory + stats) / show / create / use (activate; inline integrity check — silent when fine) / rebuild (clear-and-rebuild this conversation in place, Ship of Theseus); delivery: wake-later (one future instant + one message to any trajectory; fire-and-forget — no receipt, no recall) / send-message (deliver one message RIGHT NOW; live target injected immediately, non-live cold-resumed like a direct wake — returns a synchronous receipt)",
 		"  dashboard    — always-on container instruments: health (CCC three-principle check + registry integrity) / time (now) / wait (N seconds)",
 		"  container_git— git operations (status/commit/push/log)",
 		"  msm          — execute a registered CCC MSM: msm(name, args); partial name returns candidates; inspect=true shows usage",
@@ -6117,7 +6140,7 @@ function accIdentityText(root, configPaths = DEFAULT_SERENITY_CONFIG_PATHS, entr
 	}
 	return lines.join("\n");
 }
-const PLUGIN_SOURCE$4 = {
+const PLUGIN_SOURCE$3 = {
 	kind: "plugin",
 	plugin: "dsh-serenity-hooks"
 };
@@ -6135,7 +6158,7 @@ function accMessage(root, configPaths, entrySkillMaxChars) {
 	}];
 	return createUserMessage({
 		content,
-		source: PLUGIN_SOURCE$4
+		source: PLUGIN_SOURCE$3
 	});
 }
 /** 每 agent 是否已注入过（进程内存态） */
@@ -8696,7 +8719,7 @@ var rebuild_exports = /* @__PURE__ */ __exportAll({
 	sanitizeFocusLine: () => sanitizeFocusLine,
 	stripAckSuffix: () => stripAckSuffix
 });
-const PLUGIN_SOURCE$3 = {
+const PLUGIN_SOURCE$2 = {
 	kind: "plugin",
 	plugin: "dsh-serenity-hooks"
 };
@@ -9015,7 +9038,7 @@ function registerRebuildTurnHook(ctx) {
 						type: "text",
 						text: `${eventToken("rebuild")} The conversation has been cleared and rebuilt. Follow the anchor instructions above now: read the persistent trajectory (SESSION.md) and continue the work automatically from the last checkpoint.`
 					}],
-					source: PLUGIN_SOURCE$3
+					source: PLUGIN_SOURCE$2
 				}));
 				writeRebuildDiag(resolveSerenityRootFor(agent), {
 					sessionId: id,
@@ -11278,7 +11301,7 @@ function buildRebuke(hits) {
 const rebukeStates = /* @__PURE__ */ new Map();
 //#endregion
 //#region src/output-guard-seam.ts
-const PLUGIN_SOURCE$2 = {
+const PLUGIN_SOURCE$1 = {
 	kind: "plugin",
 	plugin: "dsh-serenity-hooks"
 };
@@ -11339,7 +11362,7 @@ function registerOutputGuardHook(ctx) {
 					type: "text",
 					text: buildRebuke(hits)
 				}],
-				source: PLUGIN_SOURCE$2
+				source: PLUGIN_SOURCE$1
 			}));
 		} catch (error) {
 			console.warn(`[serenity-hooks] output-guard steer failed: ${String(error?.message ?? error)}`);
@@ -12101,463 +12124,6 @@ qInput.focus()
 </html>`;
 }
 //#endregion
-//#region src/host/effect.ts
-/** 已告警的标签（进程级去重：重复装配/多测试替身不刷屏，但绝不静默） */
-const warnedLabels = /* @__PURE__ */ new Set();
-/**
-* 登记一个卸载时执行的清理。
-* @param ctx 宿主插件上下文
-* @param label 日志标签（定位是哪个资源未装配）
-* @param cleanup 卸载时执行；抛错被吞掉（不阻断其它清理）
-* @returns 是否成功装配（false = 宿主无 `ctx.effect`，已告警）
-*/
-function registerDisposer(ctx, label, cleanup) {
-	const effect = ctx?.effect;
-	if (typeof effect !== "function") {
-		if (!warnedLabels.has(label)) {
-			warnedLabels.add(label);
-			console.warn(`[serenity-hooks] ✗ 资源拆卸未装配（${label}）：ctx.effect 不可用（宿主契约缺失）`);
-		}
-		return false;
-	}
-	try {
-		effect.call(ctx, () => () => {
-			try {
-				cleanup();
-			} catch (err) {
-				console.warn(`[serenity-hooks] ✗ 资源清理失败（${label}）: ${String(err?.message ?? err)}`);
-			}
-		}, `dsh-serenity-hooks: ${label}`);
-		return true;
-	} catch (err) {
-		console.warn(`[serenity-hooks] ✗ 资源拆卸注册失败（${label}）: ${String(err?.message ?? err)}`);
-		return false;
-	}
-}
-//#endregion
-//#region src/clock-runtime.ts
-/**
-* clock-runtime.ts — **时钟运行时工厂**（S142 §38 复审候选 C6b，路径 **P2**）
-*
-* 本仓有**两条各自独立运行**的 5min 时钟：
-*   · 唤醒调度器（`wake-scheduler.ts`，一次性唤醒，D58）
-*   · autopilot 时钟（`autopilot-trajectory.ts`，周期自唤醒，D59）
-* 二者的**业务判据完全不同**（谁来扫 / 扫什么 / 投递给谁 / 按什么周期），但**引擎骨架逐字同形**
-* ——进程态 + 快照 + 复位 + `startTimer` + tick 外壳 + 事件接线 + disposer + `timer.unref()`。
-* 本条把**引擎**抽到本工厂，**各钟仍各持自己的定时器与自己的串行链**。
-*
-* ───────────────────────────────────────────────────────────────────────────
-* 🔴 硬约束一：**两条时钟绝不可共用"排队执行"的链**（这是 P2 与 P1 的分界判据）
-*
-* autopilot 每轮要跑该 CCC 的**偏见脚本**（`fetchBiasContent`，超时 60s），可能阻塞数十秒；
-* 若与唤醒调度器共用一条串行链，会把另一条一起**卡住**（一次性唤醒被无关的偏见脚本拖住）。
-* ⇒ 本工厂把 `chain` 作为**每实例私有状态**：`createClock()` 调用一次 = 一条独立的串行域。
-*    实例之间**零共享**（无模块级单例、无共享 Promise、无共享 map）。
-* ⚠️ 若日后有人把 `chain` 提到模块级"省一次分配"，**两条时钟的隔离即刻失效**——不许。
-*
-* 🔴 硬约束二：**武装门只判全局闸**（`gate()`），**不判"本次有无目标"**
-*
-* 2026-09-14 F 段实测缺陷：旧实现把"有 live CCC"当**武装前置条件**，而宿主刚重启时 live 会话
-* 必为空，且**"恢复旧会话"不触发 `session/created`**（只有新建会）⇒ 启动瞬间判定落空 =
-* **时钟永久不武装**（实测 6.6h 零 tick）。⇒ 现在「**全局闸开即武装**」，"有无目标"降级为
-* tick 内的廉价判定。**武装与"本次有无目标"是两件事，本工厂不得把二者耦合。**
-*
-* 🔴 硬约束三：**两条闸必须继续分开传**（v1.34 S-1 解耦）
-*
-* 唤醒调度器 `wakeSchedulerEnabled`（**缺省开**）｜autopilot `autopilotWakeEnabled`
-* （**缺省关**）——取值方向相反。工厂取 `gate` **回调**（每次现读），**不做**任何合并或缓存。
-*
-* ───────────────────────────────────────────────────────────────────────────
-* 两条时钟**逐项语义差**（`ClockOptions` 的每个可配项都对应下表一行，不是随意的灵活性）：
-*
-* | 项 | 唤醒调度器 | autopilot | 工厂表达 |
-* |----|-----------|-----------|---------|
-* | `chain` | 有（全局串行） | 有（全局串行） | **总是私有**（硬约束一） |
-* | `lastTickLog` | 有（逐行摘要） | **无** | `logFrom` 不给 = 不记 |
-* | `ticks` 记账 | 工厂在 body **完成后**记 | **本钟**在同步段记 | `bodyCountsTick` + `begin` |
-* | body 返回类型 | `string[]`（人读摘要） | `void` | 泛型 `T` |
-* | 启动日志 | 固定串 | 含启用 CCC 计数 | `startLog: () => string` |
-* | body 异常兜底 | 留痕 + `console.warn` | 同 | 工厂统一（**吞异常不改语义**） |
-*
-* ───────────────────────────────────────────────────────────────────────────
-* **本工厂是"加法式"重构**（P2 的性质）：不新增任何判定逻辑，只把同形骨架收成一份代码；
-* 两个模块仍各自导出 `wakeSchedulerState()` / `autopilotClockState()` 与各自的
-* `__reset…ForTest()`，**对外可观测面（字段名与语义）零变化**——`acc-diag` ①b 段、
-* `container-status.ts:containerClocks()` 与面板都在读它们（见该文件 :225–250 的设计红线）。
-*
-* 为什么**不**取 P1（真合并成一个 `setInterval` + 两条策略）——2026-09-15 所有者裁决：
-* P1 只多省 ~20 行，却要把 `armed` 拆成"宿主 + 每策略"两层、并强行分开串行域，
-* 即**动两条正在跑的时钟的骨架**；**不值当**（裁决原文见 SESSION §12.8②）。
-*/
-/**
-* tick 周期（**5 分钟**）。
-*
-* 2026-09-15 S142「ACC 侧 autopilot 退场」：本值原从 `autopilot-core.ts` 导入（`TICK_MS`），
-* 但该模块随 autopilot 退场，而**本模块的唯一消费者是唤醒调度器**（`wake-scheduler`）——
-* 值本身与 autopilot 无关 ⇒ 随消费者归位到本模块（不再依赖 autopilot 判据层）。
-*
-* ⚠️ 语义不得变：该值同时是**报告文案的来源**（"等下个 Nmin tick"），历史上曾因文案写死
-* 10min 与实现 5min 不符而误导排查（§12.7 文案纠错）。
-*/
-const TICK_MS = 3e5;
-/**
-* 挂事件 → 触发 `start()`（**每个事件一次 try/catch 吞异常**：事件通道缺失不阻断时钟）。
-*
-* 为什么吞异常：宿主（headless profile 等）可能没有事件通道；**启动时已 `start()` 过一次**，
-* 事件只是"跟上面板开关 / 新会话"的热启动补丁，缺它不该让整个装配抛错。
-* @param on 宿主的 `on`（可能不存在）
-* @param ctx `on` 的 `this`（宿主 API 常要求绑定）
-* @param clock 目标时钟
-* @param events 事件名列表（回调恒为 `() => clock.start()`）
-*/
-function attachClockEvents(ctx, clock, events) {
-	const on = ctx?.on;
-	if (typeof on !== "function") return;
-	for (const name of events) try {
-		on.call(ctx, name, () => clock.start());
-	} catch {}
-}
-/**
-* 建一条时钟（**每钟各调一次**——本工厂**不是**单例，调用次数 = 时钟条数）。
-*
-* 顺序忠实于既有实现：`start()` 先武装并立即跑一次 tick → 再挂事件。
-* 拆卸由调用方经 `registerDisposer(ctx, label, clock.dispose)` 落到宿主的 `ctx.effect`。
-* @param opts 见 {@link ClockOptions}（每项对应一条既有的语义差）
-* @returns 该钟的 `{start, dispose, snapshot, reset}`
-*/
-function createClock(opts) {
-	const runtime = {
-		armed: false,
-		armedAt: null,
-		lastTickAt: null,
-		ticks: 0,
-		lastSkipReason: null
-	};
-	if (opts.logFrom) runtime.lastTickLog = [];
-	const st = {
-		timer: null,
-		chain: Promise.resolve(),
-		runtime,
-		wired: false,
-		opts
-	};
-	/** 记一次 tick（工厂内部与 body 共用同一实现——只有一处会计逻辑） */
-	const countTick = () => {
-		runtime.lastTickAt = Date.now();
-		runtime.ticks += 1;
-	};
-	/** 逐行打印（`logFrom` 缺省 ⇒ 本钟无 tick 日志，整段为死代码路径） */
-	const emit = (lines) => {
-		if (!opts.logFrom) return;
-		for (const line of lines) console.log(`${opts.logFrom.prefix}${line}`);
-	};
-	const tick = () => {
-		if (!opts.gate()) {
-			runtime.lastSkipReason = opts.gateOffReason;
-			return;
-		}
-		if (opts.begin) try {
-			opts.begin();
-		} catch (err) {
-			console.warn(`[serenity-hooks] ✗ tick 前置异常: ${String(err?.message ?? err)}（${opts.label}）`);
-			return;
-		}
-		st.chain = st.chain.then(async () => {
-			try {
-				const value = await opts.body();
-				if (!opts.bodyCountsTick) countTick();
-				if (opts.logFrom) {
-					runtime.lastTickLog = opts.logFrom.lines(value);
-					emit(runtime.lastTickLog);
-				}
-			} catch (err) {
-				const msg = `✗ tick 异常: ${String(err?.message ?? err)}`;
-				if (opts.logFrom) runtime.lastTickLog = [msg];
-				console.warn(`[serenity-hooks] ${msg}（${opts.label}）`);
-			}
-		});
-	};
-	/**
-	* 幂等启动 + 武装门：**已武装 → 原样返回**（防重复起定时器）；
-	* **闸关 → 不武装**（零资源占用）；闸开则**无条件**武装（硬约束二：不判"有无目标"）。
-	*/
-	const start = () => {
-		if (st.timer) return;
-		if (opts.events && !st.wired) {
-			st.wired = true;
-			attachClockEvents(opts.ctx, api, opts.events);
-		}
-		if (!opts.gate()) return;
-		st.timer = setInterval(tick, TICK_MS);
-		st.timer.unref();
-		runtime.armed = true;
-		runtime.armedAt = Date.now();
-		console.log(opts.startLog());
-		if (opts.immediate !== false) tick();
-	};
-	const dispose = () => {
-		if (st.timer) {
-			clearInterval(st.timer);
-			st.timer = null;
-		}
-		runtime.armed = false;
-		runtime.armedAt = null;
-		opts.onDispose?.();
-	};
-	const api = {
-		start,
-		dispose,
-		snapshot: () => ({
-			enabled: opts.gate(),
-			...runtime,
-			...runtime.lastTickLog ? { lastTickLog: [...runtime.lastTickLog] } : {}
-		}),
-		noteSkipReason: (reason) => {
-			runtime.lastSkipReason = reason;
-		},
-		countTick,
-		enqueue: (work) => {
-			st.chain = st.chain.then(work, () => void 0).then(() => void 0, (err) => {
-				console.warn(`[serenity-hooks] ✗ 串行任务异常（${opts.label}）: ${String(err?.message ?? err)}`);
-			});
-		},
-		reset: () => {
-			if (st.timer) {
-				clearInterval(st.timer);
-				st.timer = null;
-			}
-			runtime.armed = false;
-			runtime.armedAt = null;
-			runtime.lastTickAt = null;
-			runtime.ticks = 0;
-			runtime.lastSkipReason = null;
-			if (opts.logFrom) runtime.lastTickLog = [];
-			st.wired = false;
-			opts.onReset?.();
-		}
-	};
-	return api;
-}
-//#endregion
-//#region src/wake-scheduler.ts
-const PLUGIN_SOURCE$1 = {
-	kind: "plugin",
-	plugin: "dsh-serenity-hooks"
-};
-/**
-* 解析条目的 target（`S###` 或完整目录名）→ 目录名 + SESSION.md 路径。
-* @param root CCC 根
-* @param target 条目里的目标标识
-* @returns 命中返回目录信息，未命中 null
-*/
-function resolveWakeTarget(root, target) {
-	const found = findSession(sessionsRoot(root), target);
-	if (!found) return null;
-	const mdPath = join(found.path, "SESSION.md");
-	if (!existsSync(mdPath)) return null;
-	return {
-		dirName: basename(found.path),
-		mdPath
-	};
-}
-/**
-* 全局闸：**只看 `wakeSchedulerEnabled`**（缺省**开**；显式 `false` 才关）。
-*
-* ⚠️ 2026-09-15 用户裁决（S-1 **解耦**）：「auto-trajectory 的开关**只关闭 auto-trajectory 唤醒**」。
-* ⇒ 本函数**不得**再把 `autopilotEnabled`（周期自唤醒闸）作为回退键 —— 旧实现是
-* `trajectoryEnabled === true || autopilotEnabled === true`，后果实测：所有者关掉 auto-trajectory 后，
-* **一次性唤醒 `wake-later` 被连带关掉**，注册表条目静默滞留（当日 6.6h 零 tick）。
-* 缺省由 false 改 true 的理由：唤醒注册表已是一等机制（D58），条目**全部由人类/agent 显式登记**
-* 未来时刻（无环境自主性），不需要"默认关"的实验保护；代价 = 一个 unref 的 5min 空检查。
-*
-* 设置服务不可用 → 关（保守；异常由日志与 `dashboard health` 响亮暴露，不静默）。
-*/
-function wakeSchedulerEnabled() {
-	try {
-		return readSimpleSettings().wakeSchedulerEnabled !== false;
-	} catch {
-		return false;
-	}
-}
-/**
-* 🔴 **本钟的串行域**（C6b 硬约束）：`clock.chain` 是**本实例私有**的——
-* 与 autopilot 的串行链**零共享**。autopilot 每轮跑 CCC 偏见脚本可能阻塞数十秒，
-* 共用链会把一次性唤醒一起卡住（这正是 P1 被否、取 P2 的理由，见 SESSION §12.8②）。
-*
-* **为什么这里是模块级常量**（而不是 `registerWakeScheduler` 的局部量）：本钟的进程态是
-* **进程级可观测面**（`acc-diag` ①b / `containerClocks` 在读），且 `wakeSchedulerState()` /
-* `__resetWakeSchedulerStateForTest()` 是**公开导出**、可在未装配时被调用 ⇒ 实例必须**恒在**
-* （旧实现的 `schedulerRuntime` 也正是模块级常量）。装配只做 `clock.start()`。
-*/
-/** 本钟的装配项（`ctx` 由 {@link registerWakeScheduler} 在装配点填入） */
-const clockOpts = {
-	label: "trajectory 唤醒调度器",
-	ctx: void 0,
-	events: ["session/created", "serenity/settings-changed"],
-	gate: wakeSchedulerEnabled,
-	gateOffReason: "唤醒调度器闸关闭（wakeSchedulerEnabled=false）",
-	body: () => runWakeTick(clockOpts.ctx),
-	logFrom: {
-		prefix: "[serenity-hooks] trajectory 唤醒 ",
-		lines: (lines) => lines
-	},
-	startLog: () => "[serenity-hooks] ✓ trajectory 唤醒调度器启动（5min tick）"
-};
-const clock = createClock(clockOpts);
-/** 调度器进程态快照（只读；`enabled` = 全局闸**当前**值，便于区分"未武装"与"闸关"） */
-function wakeSchedulerState() {
-	return clock.snapshot();
-}
-/**
-* 取目标 agent：live 优先 → 冷会话走 sessionController.resolveAgent → 标题回退。
-* @param ctx 插件上下文
-* @param root CCC 根
-* @param dirName 目标 trajectory 目录名
-* @returns 命中返回 agent 与取得方式（how 进 lastResult，便于诊断）；未命中返回原因
-*/
-async function acquireWakeAgent(ctx, root, dirName) {
-	const agents = hostAgents(ctx);
-	const ids = listBoundSessionIds(root, dirName);
-	for (const id of ids) {
-		const live = agents?.get?.(id);
-		if (live) return {
-			agent: live,
-			how: `live(bound ${id})`
-		};
-	}
-	if (ids.length > 0) {
-		const sc = hostService(ctx, "sessionController");
-		const resolved = sc?.resolveAgent;
-		if (typeof resolved !== "function") return { error: `目标会话未加载且 sessionController 不可用（headless profile？）——绑定 id: ${ids[0]}` };
-		const id = ids[0];
-		try {
-			const out = await resolved.call(sc, id);
-			if (out?.agent) return {
-				agent: out.agent,
-				how: `cold-resume(${id})`
-			};
-			return { error: `sessionController.resolveAgent 未返回 agent（${id}）: ${String(out?.error ?? "未知原因")}` };
-		} catch (err) {
-			return { error: `冷会话载入失败（${id}）: ${String(err?.message ?? err)}` };
-		}
-	}
-	return { error: `无绑定会话记录（AGENT_SESSIONS/.bindings.json 中无 ${dirName}）——目标轨迹需先被 container_trajectory use 激活过` };
-}
-/** 唤醒消息（唤起即投递正文：身份锚定 + 唤醒信息 + 任务） */
-function buildWakeText(entry, target) {
-	return [
-		`[trajectory 唤醒] 到点（登记于 ${entry.createdAt}，发起者 ${entry.createdBy || "未知"}，id ${entry.id}）。`,
-		"",
-		`身份锚定：继续 ${target.dirName} 的 trajectory（SESSION.md: ${target.mdPath}）。`,
-		"",
-		"唤醒信息：",
-		entry.message,
-		"",
-		"任务：按上述唤醒信息继续本轨迹的工作；完成后把进展写入 SESSION.md。"
-	].join("\n");
-}
-/**
-* 投递一条唤醒（fire-and-forget：`followup` 入队即返回，不等模型结果）。
-* @param ctx 插件上下文
-* @param root CCC 根
-* @param entry 唤醒条目
-* @returns 投递结果（写回 lastResult）
-*/
-async function deliverWake(ctx, root, entry) {
-	const target = resolveWakeTarget(root, entry.target);
-	if (!target) return {
-		ok: false,
-		detail: `目标 trajectory 未命中（${entry.target}）`
-	};
-	const acquired = await acquireWakeAgent(ctx, root, target.dirName);
-	if ("error" in acquired) return {
-		ok: false,
-		detail: acquired.error
-	};
-	try {
-		acquired.agent.followup(createUserMessage({
-			content: [{
-				type: "text",
-				text: buildWakeText(entry, target)
-			}],
-			source: PLUGIN_SOURCE$1
-		}));
-	} catch (err) {
-		return {
-			ok: false,
-			detail: `投递失败（${acquired.how}）: ${String(err?.message ?? err)}`
-		};
-	}
-	return {
-		ok: true,
-		detail: `已投递 ${target.dirName}（${acquired.how}）`
-	};
-}
-/**
-* 本 tick 要扫的 CCC 根集合（**并集**）。
-*
-* C2（S142 2026-09-15 Q5）：原实现是 `collectLiveCccs`——**只认 live 会话** ⇒
-* "完全冷掉的 CCC 不能自唤醒自己"（已知边界）。现改为 `ccc-roots.listCccs` 的并集枚举
-* （工作区注册表 ∪ 持久化会话 ∪ live 会话）：**没有 live 会话的 CCC 也会被扫到**。
-*
-* ⚠️ 边界（本步**只**改"枚举哪些 CCC"，**不改**"怎么找到要交付的 agent"）：
-* 把 message 交给某条 trajectory 仍必须靠 **live 会话**解析（见本文件
-* `acquireWakeAgent`）；无 live 会话时该 CCC 只是**被扫到、
-* 无交付对象** ⇒ `deliverWake` 返回 `无绑定会话记录…`，条目回 `pending` 并留痕。
-* 因此本函数**不得**让 tick 抛错（异常一律由调用方 tick 兜住，见 `runWakeTick` 的 try）。
-* @param ctx 插件上下文
-* @returns CCC 根列表（无任何来源 → `[]`）
-*/
-async function collectWakeCccs(ctx) {
-	return (await listCccs(ctx)).map((e) => e.root);
-}
-/** 一次调度 tick：遍历已知 CCC → 到期项串行投递 / 超窗项置 missed；返回人读摘要 */
-async function runWakeTick(ctx) {
-	const log = [];
-	const roots = await collectWakeCccs(ctx).catch(() => []);
-	if (roots.length === 0) {
-		clock.noteSkipReason("无已知 CCC 可扫（等某个会话/工作区出现）");
-		return log;
-	}
-	clock.noteSkipReason(null);
-	for (const root of roots) {
-		const { registry, error } = loadWakeRegistry(root);
-		if (error) {
-			log.push(`✗ ${root}: ${error}`);
-			continue;
-		}
-		const { due, expired } = splitDueWakes(registry, Date.now(), WAKE_CATCH_UP_MS);
-		for (const e of expired) {
-			updateWake(root, e.id, {
-				state: "missed",
-				lastResult: `超过补跑窗口（${WAKE_CATCH_UP_MS / 36e5}h）未投递`
-			});
-			log.push(`· ${root}: ${e.id} → missed（超补跑窗口）`);
-		}
-		for (const e of due) {
-			const res = await deliverWake(ctx, root, e);
-			updateWake(root, e.id, {
-				state: res.ok ? "delivered" : "pending",
-				attempts: e.attempts + 1,
-				lastResult: res.detail,
-				deliveredAt: res.ok ? (/* @__PURE__ */ new Date()).toISOString() : null
-			});
-			log.push(`· ${root}: ${e.id} → ${res.ok ? "delivered" : `重试（${res.detail}）`}`);
-		}
-	}
-	return log;
-}
-/**
-* 装配调度器（index.ts apply 调用）：5min tick + 生命周期 disposer +
-* 会话出现/settings 变化时热启动（与 autopilot 同款触发面，互不干扰）。
-* @param ctx 插件上下文
-*/
-function registerWakeScheduler(ctx) {
-	clockOpts.ctx = ctx;
-	clock.start();
-	registerDisposer(ctx, "trajectory 唤醒调度器", () => clock.dispose());
-}
-//#endregion
 //#region src/weixin-output-guard.ts
 const PLUGIN_SOURCE = {
 	kind: "plugin",

package/lib/tools/trajectory.d.ts

@@ -5,6 +5,10 @@
  * `container_trajectory`，无别名）——trajectory 是一等概念
  * （SESSION.md 是它的持久身体），本工具管它的**载体生命周期 + 一次性时间安排**。
  * 动作收敛为 **6 个**：list / show / create / use / rebuild / wake-later。
+ * 🔴 2026-09-16（所有者裁决）：**第 7 个动作 `send-message`（即时投递）**
+ *    ——与 `wake-later` 共用取用通路，差别只在**时刻**（现在 vs 未来）与**回执**（有 vs 无）；
+ *    实现落在 `wake-scheduler.ts` 的 `sendToTrajectory()`（"怎么把一句话送到一条轨迹"是调度器的知识）。
+ *    设计稿 = `docs/trajectory-send-message-design.md`（v0.2 定稿）。
  *
  * 与旧面（logbook 11 动作 + trajectory 12 动作）的对应（用户逐条裁决，R↓）：
  *   · `summary` → 并入 `list`（全库统计随清单一起给）