@sema-agent/client-core 0.11.15 → 0.11.17

package/dist/liveQuestionStore.js

@@ -3,43 +3,10 @@
  * 本模块自持 AskUserQuestion 的 wire 词汇(SDK 0.0.44 删掉了 questions 资源导出),搬入后这套
  * 类型随包发布 —— web/桌面端的 HITL 覆盖层与 TUI 共用同一份 QuestionFrame/QuestionAnswer 形。
  */
-/**
- * src/sema/liveQuestionStore.ts — the SIDE-CHANNEL for §4④ live-stream AskUserQuestion (the conversation-seam
- * twin of liveSessionStore.ts).
- *
- * WHY THIS EXISTS
- * ---------------
- * In TOC (two-process) the MODEL runs in the engine; its `AskUserQuestion` tool fires on core's
- * `RunnerDeps.onQuestion` seam and the service (question.ts, 1.61.0) emits a NAMED SSE frame
- * (`event: question` / `event: question_complete`) that INTERLEAVES on the same live token stream as the
- * AgentEvents. That frame is NOT an AgentEvent arm (it is a DISTINCT vocabulary, exactly like elicitation) —
- * so it must be DEMUXED out of the transcript-render pipeline and routed to an interactive DIALOG overlay
- * instead. This tiny, dependency-FREE module is that route: liveClient WRITES the demuxed frame here (on each
- * `question`/`question_complete`) and publishes its `client.questions.respond` binding; the UI overlay
- * (main.tsx / REPL) READS the frames and answers via `respondToQuestion`. Same shape as liveSessionStore /
- * rewindAnchorStore — the overlay stays testable (no @sema-ai/sdk graph) and seamQuery/normalizeToolNames are
- * untouched.
- *
- * 🔴 LIVE-ONLY + SAME-REPLICA (the `steer()`-class of HITL): the service parks the answer promise in-memory,
- * so a respond that lands after the TTL (5 min) / after answer / on another replica → 404. No durable resume
- * anchor — a mid-question disconnect just lets the run proceed with the headless default (the model never
- * hangs). The overlay must therefore treat `respondToQuestion` as best-effort (a 404 = "already released",
- * dismiss the dialog, never retry).
- *
- * 🔴 UNTRUSTED: the `questions` payload is model-authored (service secret-redacted, but still UNTRUSTED for
- * display). The overlay RENDERS it; it must NEVER be re-fed to a model. The answer the overlay sends back is
- * fenced by CORE (`selected ⊆ options`, `note` untrusted-fenced) — the overlay must echo the EXACT option
- * labels the user saw, never fabricate one.
- */
-/* ── LOCAL wire types (owned HERE, not @sema-ai/sdk) ─────────────────────────────────────────────
- * SDK 0.0.44 DELETED the `questions` resource (engine 1.163 parks the run `suspended` instead of
- * emitting `question` SSE frames — see liveHitlAskWire.ts), and with it the QuestionFrame /
- * QuestionAnswer / AskQuestion exports. The shell still speaks this vocabulary INTERNALLY (synthetic
- * frames from liveHitlAskWire / planReviewWire + the legacy 1.61-era SSE demux in liveClient), so the
- * types now live in THIS dependency-free module — the store this whole seam already routes through.
- * Shapes are the ones the shell actually produces/consumes (askq-wire-probe + overlay usage), byte-
- * compatible with the old wire payload `{type,questionId,questions?,outcome?}`. */
-let frameHandler = null;
+import { createSessionSlot, DEFAULT_SESSION_KEY } from './sessionSlot.js';
+// W1(design/161):frameHandler 槽位改 sessionKey → 注册表;零参 API = DEFAULT_SESSION_KEY
+// 兼容层(cli 装配不动)。respondFn / localResponders 不在 W1 五槽位切口内,维持原样。
+const frameHandlerByKey = createSessionSlot();
 let respondFn = null;
 /** SHELL-LOCAL question responders (plan-review approval cards etc. — synthetic frames whose id does
  *  NOT exist engine-side, so POST /v1/questions/:id/respond would 404). Registered per-questionId by
@@ -59,6 +26,11 @@ export function registerLocalQuestionResponder(id, fn) {
  * break the live stream drain (the run must keep flowing; a lost frame just headless-defaults the ask).
  */
 export function publishQuestionFrame(frame) {
+    publishQuestionFrameFor(DEFAULT_SESSION_KEY, frame);
+}
+/** W1 keyed variant: publish to ONE session's overlay (multi-session hosts demux by their own key). */
+export function publishQuestionFrameFor(sessionKey, frame) {
+    const frameHandler = frameHandlerByKey.get(sessionKey);
     if (!frameHandler)
         return;
     try {
@@ -71,14 +43,23 @@ export function publishQuestionFrame(frame) {
 /** Whether a UI overlay is currently subscribed (liveHitlAskWire gates on this: print/non-REPL mode has no
  *  dialog to park on, so the suspended terminal must fall through honestly instead of hanging the stream). */
 export function hasQuestionOverlay() {
-    return frameHandler !== null;
+    return hasQuestionOverlayFor(DEFAULT_SESSION_KEY);
+}
+/** W1 keyed variant. */
+export function hasQuestionOverlayFor(sessionKey) {
+    return frameHandlerByKey.get(sessionKey) !== undefined;
 }
 /** Subscribe the UI overlay to live question frames. Returns an unsubscribe. Last writer wins (one overlay). */
 export function onQuestionFrame(handler) {
-    frameHandler = handler;
+    return onQuestionFrameFor(DEFAULT_SESSION_KEY, handler);
+}
+/** W1 keyed variant: one overlay PER sessionKey (last writer wins within a key; keys never clobber
+ *  each other — the r1 E2 dual-session hazard this registry exists to close). */
+export function onQuestionFrameFor(sessionKey, handler) {
+    frameHandlerByKey.set(sessionKey, handler);
     return () => {
-        if (frameHandler === handler)
-            frameHandler = null;
+        if (frameHandlerByKey.get(sessionKey) === handler)
+            frameHandlerByKey.set(sessionKey, undefined);
     };
 }
 /** Publish the live client's `questions.respond` binding (called from createLiveConversationClient). `null`
@@ -104,6 +85,6 @@ export function respondToQuestion(id, answer, opts) {
 }
 /** Test-only reset. */
 export function _resetLiveQuestionStore() {
-    frameHandler = null;
+    frameHandlerByKey.clear();
     respondFn = null;
 }

package/dist/notifications.d.ts

@@ -182,9 +182,11 @@ type BgTaskStatusProbe = (taskId: string) => Promise<{
     terminal: boolean;
     status: string;
 } | null>;
+/** 委派 prompt 取件口(行消费端建行/详情页兜底用)。未登记 ⇒ undefined(诚实缺席)。 */
+export declare function outstandingBgTaskPrompt(taskId: string): string | undefined;
 export declare function installBgTaskStatusProbe(probe: BgTaskStatusProbe): void;
 /** bridge 在 Agent async_launched 回执(structured type:'agent')经过时登记。幂等;已通知不再登记。 */
-export declare function registerOutstandingBgTask(taskId: string, description: string): void;
+export declare function registerOutstandingBgTask(taskId: string, description: string, prompt?: string): void;
 export declare function isOwnWorkflowRun(runId: string): boolean;
 /** 本壳亲手启动过的 workflow run 列表(Set 插入序 = 启动序;/workflows 命令的目标 run 选择用,
  *  cmd-workflows.tsx——fleet source 无行可选时的兜底 id 源)。 */

package/dist/notifications.js

@@ -388,12 +388,31 @@ export function installWorkflowStatusProbe(probe) {
 }
 const outstandingBgTasks = new Map();
 let bgStatusProbe = null;
+/**
+ * R4(clay 五报 07-31)委派 prompt 台账:`async_launched` 回执带全 {task_id, description, prompt}
+ * 三件,但此前 prompt 只进消息 payload(ctrl+o expand 那条腿),任务行/详情页(↓ manage)取不到,
+ * 只能绕道等引擎 running 期不发的 transcriptId 去转录读面捞 ⇒ Prompt 节恒空。
+ * 这里按行 id 记一份(与 fleet 行 rowIdTail 同 keyspace),行消费端建行时取用。
+ * 与 outstandingBgTasks 分开存:后者随通知摘除,prompt 在行的整个生命周期都要可取。
+ * process-lifetime 有界:bg 子代数量 = 人手派发量级,不设逐出。
+ */
+const bgTaskPrompts = new Map();
+/** 委派 prompt 取件口(行消费端建行/详情页兜底用)。未登记 ⇒ undefined(诚实缺席)。 */
+export function outstandingBgTaskPrompt(taskId) {
+    return bgTaskPrompts.get(taskId);
+}
 export function installBgTaskStatusProbe(probe) {
     bgStatusProbe = probe;
 }
 /** bridge 在 Agent async_launched 回执(structured type:'agent')经过时登记。幂等;已通知不再登记。 */
-export function registerOutstandingBgTask(taskId, description) {
-    if (!taskId || notifiedRunIds.has(taskId) || outstandingBgTasks.has(taskId))
+export function registerOutstandingBgTask(taskId, description, prompt) {
+    if (!taskId)
+        return;
+    // prompt 台账先记(与 watcher 登记的幂等早退解耦:重复回执/已通知任务的 prompt 仍要可取)。
+    if (typeof prompt === 'string' && prompt.length > 0 && !bgTaskPrompts.has(taskId)) {
+        bgTaskPrompts.set(taskId, prompt);
+    }
+    if (notifiedRunIds.has(taskId) || outstandingBgTasks.has(taskId))
         return;
     outstandingBgTasks.set(taskId, { registeredAt: Date.now(), description });
     ensureWatchTimer();

package/dist/request/taskRequest.d.ts

@@ -81,6 +81,8 @@ export interface TaskRequestInput {
     attachments?: Record<string, unknown>;
     /** 预上传附件句柄(`uploadAttachment` 回执 id)。空数组 = 没带附件 ⇒ 整键不 stamp。 */
     attachmentIds?: readonly string[];
+    /** 排除工具名单(SDK 真 wire 键;desktop 座位面在发)。空数组 = 不排除 ⇒ 整键不 stamp。 */
+    excludeTools?: readonly string[];
     finalVerification?: boolean;
     limits?: Record<string, unknown>;
     interactiveTools?: false;

package/dist/request/taskRequest.js

@@ -34,6 +34,7 @@ export const REQUEST_FIELD_MATRIX = [
     //    B4 从壳的三个构造器逐行读出来的,那时这条车道只有壳一个消费者。`attachmentIds` 是**反过来**
     //    的第一条:它今天只有 web/desktop 在发,壳反而没有这个入口。别把本节读成「壳独有」。
     { field: 'attachmentIds', lanes: ['interactive'], live: true, why: '附件**字节通道**(uploadAttachment 回执 id;server ≥1.289 绑定会话并把文件物化进 run 的 attachments/)。有上传入口的端才有 id 可引用:web/desktop 有,壳走 images / 本地文件路径,`-p` 车道连 uploadAttachment 都没有 ⇒ print 缺席是**没有来源**,不是漏。🔴 与上面的 `attachments` 同名不同物(那是 turn 边界的配置键),两条永远不许合并' },
+    { field: 'excludeTools', lanes: ['interactive'], live: true, why: 'design/161 W3(2026-07-30):真 wire 键(SDK types `excludeTools`)且早在 seatContract `START_SESSION_OPTION_KEYS` 里,却是 desktop 手写 taskReq 的第 9 键、矩阵外——而 stamp 门对未登记键**静默丢弃**,真实危险形=「用户显式排除的工具被静默放回」(权限方向回归,类型层不报)。今天只有 desktop 在发;壳的工具面走 roster/interactiveTools 另一条路,print 无排除入口' },
     { field: 'settings.ultracode', lanes: ['interactive'], live: true, why: 'design/111:sticky `/effort ultracode` 拨盘 + 当轮关键词嗅探,两个来源都只在交互面存在', gap: true },
     { field: 'systemPrompt', lanes: ['interactive'], live: false, why: 'CC QueryParams.systemPrompt;print 腿的 params 没有这一位' },
     { field: 'reasoningEffort', lanes: ['interactive'], live: false, why: '`/effort` 拨盘存在 AppState,print 无 AppState', gap: true },
@@ -115,6 +116,10 @@ export function buildTaskRequest(input, lane) {
         ...(on('attachmentIds', input.attachmentIds) && (input.attachmentIds?.length ?? 0) > 0
             ? { attachmentIds: [...(input.attachmentIds ?? [])] }
             : {}),
+        // 同款空数组语义:「不排除任何工具」不 stamp(缺席与空排除在 wire 上等价,发小的那个)。
+        ...(on('excludeTools', input.excludeTools) && (input.excludeTools?.length ?? 0) > 0
+            ? { excludeTools: [...(input.excludeTools ?? [])] }
+            : {}),
         ...(on('clientContext', input.clientContext) ? { clientContext: input.clientContext } : {}),
         ...(on('scratchpadDir', input.scratchpadDir) ? { scratchpadDir: input.scratchpadDir } : {}),
         ...(on('finalVerification', input.finalVerification)

package/dist/sessionSlot.d.ts

@@ -0,0 +1,26 @@
+/**
+ * sessionSlot.ts — W1(design/161):包内「模块级可变单槽位」的 per-session 注册表最小工厂。
+ *
+ * 背景(design/161 复审 r1 E2):包内五个模块级单槽位(host.ts `host` / askGateWire
+ * `hostSurface` / toolApprovalWire `cardPort` / liveQuestionStore `frameHandler` /
+ * engineWireTarget `installed`)与多会话宿主(desktop)正面冲突 —— 两个并行会话互相顶盖
+ * (A 会话的审批卡弹到 B 的面上 / B 的 responder 覆盖 A 的)。W1 把这五个槽位改成
+ * `Map<sessionKey, T>` 注册表:
+ *   · **零参旧 API = DEFAULT_SESSION_KEY 兼容层**(cli 的 module-load 装配一行不动,
+ *     default 键路径与改前单变量行为逐字节等价);
+ *   · 带 key 的 `*For(sessionKey, …)` 变体给多会话宿主用,每会话一键,互不顶盖。
+ * 契约锚 = `agentSession/contract.ts` 的 `AgentSessionConfig.sessionKey`。
+ *
+ * 🔴 本文件只管「存取」,不带任何业务语义 —— miss 计数、fail-soft 文言、还原/合并语义都留在
+ * 各槽位模块里(五个槽位形状略异,强行归一就是过度设计)。
+ */
+/** 零参旧 API 的兼容键(cli 单会话装配走它;多会话宿主每会话一键,别用这个值当会话 id)。 */
+export declare const DEFAULT_SESSION_KEY = "__default__";
+/** per-session 槽位存取面。`get` 未装过 = undefined(各槽位模块自己 `?? null` 归一)。 */
+export interface SessionSlot<T> {
+    get(key: string): T | undefined;
+    /** `undefined` = 卸下该键(与「从未装过」同态 —— 槽位模块的 prev-还原语义靠它闭合)。 */
+    set(key: string, value: T | undefined): void;
+    clear(): void;
+}
+export declare function createSessionSlot<T>(): SessionSlot<T>;

package/dist/sessionSlot.js

@@ -0,0 +1,31 @@
+/**
+ * sessionSlot.ts — W1(design/161):包内「模块级可变单槽位」的 per-session 注册表最小工厂。
+ *
+ * 背景(design/161 复审 r1 E2):包内五个模块级单槽位(host.ts `host` / askGateWire
+ * `hostSurface` / toolApprovalWire `cardPort` / liveQuestionStore `frameHandler` /
+ * engineWireTarget `installed`)与多会话宿主(desktop)正面冲突 —— 两个并行会话互相顶盖
+ * (A 会话的审批卡弹到 B 的面上 / B 的 responder 覆盖 A 的)。W1 把这五个槽位改成
+ * `Map<sessionKey, T>` 注册表:
+ *   · **零参旧 API = DEFAULT_SESSION_KEY 兼容层**(cli 的 module-load 装配一行不动,
+ *     default 键路径与改前单变量行为逐字节等价);
+ *   · 带 key 的 `*For(sessionKey, …)` 变体给多会话宿主用,每会话一键,互不顶盖。
+ * 契约锚 = `agentSession/contract.ts` 的 `AgentSessionConfig.sessionKey`。
+ *
+ * 🔴 本文件只管「存取」,不带任何业务语义 —— miss 计数、fail-soft 文言、还原/合并语义都留在
+ * 各槽位模块里(五个槽位形状略异,强行归一就是过度设计)。
+ */
+/** 零参旧 API 的兼容键(cli 单会话装配走它;多会话宿主每会话一键,别用这个值当会话 id)。 */
+export const DEFAULT_SESSION_KEY = '__default__';
+export function createSessionSlot() {
+    const values = new Map();
+    return {
+        get: (key) => values.get(key),
+        set: (key, value) => {
+            if (value === undefined)
+                values.delete(key);
+            else
+                values.set(key, value);
+        },
+        clear: () => values.clear(),
+    };
+}

package/dist/toolResult.js

@@ -75,6 +75,13 @@ export const STRUCTURED_DETAIL_TYPES = new Set([
     'fork',
     'enter-plan-mode',
     'exit-plan-mode',
+    // core 2.7.0 跟车四型(engine-vocab 等值门抓获,[dep-bump-follow-on] 计数钉族):本表只判
+    // 「structured 在场」,switch 认不得的照旧走 text 回落 —— 加型=让正则反解对新卡退位,不加型
+    // =把引擎的结构化当裸对象。
+    'file_unchanged',
+    'worktree',
+    'monitor-start',
+    'path_not_in_root',
 ]);
 /** structured 在场判别:顶层 `type` ∈ 白名单 ⇒ 返回该 type,否则 undefined(= 不在场)。 */
 export function structuredDetailType(structured) {
@@ -610,7 +617,7 @@ modelText) {
             if (agentId === undefined || typeof s.description !== 'string' || typeof s.prompt !== 'string') {
                 return null;
             }
-            registerOutstandingBgTask(agentId, s.description);
+            registerOutstandingBgTask(agentId, s.description, s.prompt);
             return {
                 toolUseResult: {
                     isAsync: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/client-core",
-  "version": "0.11.15",
+  "version": "0.11.17",
   "description": "Client-side session runtime shared by every sema human client (TUI / web / desktop): sema wire frames (AgentEvent) -> CC session vocabulary (SDKMessage) with dual-plane output (transcript/chrome), deterministic transcript ids, lane discipline as a type, and the notification/dedup ledgers. Every CC-skin shape is collected here so the wire itself stays neutral. Blackboard [1832] design axioms; [1651]/[1652]/[1653] signed seam design. Renamed from @sema-agent/wire-cc-adapter (0.1.x).",
   "license": "MIT",
   "type": "module",