@sema-agent/client-core 0.11.14 → 0.11.16

package/dist/hitl/askGateWire.js

@@ -1,30 +1,46 @@
 import { HitlBridge } from './hitlBridge.js';
 import { publishQuestionFrame, registerLocalQuestionResponder, hasQuestionOverlay, } from '../liveQuestionStore.js';
 import { hostLog } from '../host.js';
+import { createSessionSlot, DEFAULT_SESSION_KEY } from '../sessionSlot.js';
 import { isFsApprovalGate, toolNameIsFsWrite, surfaceFsApprovalAndDecide, isToolApprovalFrame, isFromSubagent, surfaceToolApprovalFrameAndRespond, } from './toolApprovalWire.js';
 import { classifierDenyFromToolEnd } from '../classifierVerdictWire.js';
-let hostSurface = null;
-let hostSurfaceMisses = 0;
+// W1(design/161):sessionKey → 注册表;零参 API = DEFAULT_SESSION_KEY 兼容层(cli 装配不动)。
+const hostSurfaceByKey = createSessionSlot();
+const hostSurfaceMissesByKey = new Map();
 /** 装 HITL 宿主面(传 null 卸)。返回还原函数。 */
 export function installHitlHostSurface(surface) {
-    const prev = hostSurface;
-    hostSurface = surface;
+    return installHitlHostSurfaceFor(DEFAULT_SESSION_KEY, surface);
+}
+/** W1 带 key 变体:装/卸某会话的 HITL 宿主面(多会话宿主每会话一键,互不顶盖)。 */
+export function installHitlHostSurfaceFor(sessionKey, surface) {
+    const prev = hostSurfaceByKey.get(sessionKey);
+    hostSurfaceByKey.set(sessionKey, surface);
     return () => {
-        hostSurface = prev;
+        hostSurfaceByKey.set(sessionKey, prev);
     };
 }
 /** 🔴 宿主自检:恒应为 0。非 0 = 有 HITL 副作用发生时口不在,那一行 warn / 那条记账丢了。 */
 export function hitlHostSurfaceMisses() {
-    return hostSurfaceMisses;
+    return hitlHostSurfaceMissesFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体(miss 计数逐键)。 */
+export function hitlHostSurfaceMissesFor(sessionKey) {
+    return hostSurfaceMissesByKey.get(sessionKey) ?? 0;
+}
+/** W1 读端:某会话的 HITL 宿主面(未装 = null;**不计 miss** —— miss 只在副作用真发生时计)。 */
+export function hitlHostSurfaceFor(sessionKey) {
+    return hostSurfaceByKey.get(sessionKey) ?? null;
 }
 /** 测试钩:卸口 + 清计数。 */
 export function _resetHitlHostSurfaceForTest() {
-    hostSurface = null;
-    hostSurfaceMisses = 0;
+    hostSurfaceByKey.clear();
+    hostSurfaceMissesByKey.clear();
 }
 function surface() {
-    if (hostSurface === null)
-        hostSurfaceMisses++;
+    const hostSurface = hitlHostSurfaceFor(DEFAULT_SESSION_KEY);
+    if (hostSurface === null) {
+        hostSurfaceMissesByKey.set(DEFAULT_SESSION_KEY, (hostSurfaceMissesByKey.get(DEFAULT_SESSION_KEY) ?? 0) + 1);
+    }
     return hostSurface;
 }
 /**

package/dist/hitl/toolApprovalWire.d.ts

@@ -61,10 +61,18 @@ export interface ApprovalCardRequest {
 export type ApprovalCardPort = (req: ApprovalCardRequest) => Promise<ApprovalCardDecision>;
 /** 装卡口(传 null 卸)。返回还原函数。 */
 export declare function installApprovalCardPort(port: ApprovalCardPort | null): () => void;
+/** W1 带 key 变体:装/卸某会话的卡口(多会话宿主每会话一键,互不顶盖)。 */
+export declare function installApprovalCardPortFor(sessionKey: string, port: ApprovalCardPort | null): () => void;
 /** 🔴 宿主自检:恒应为 0。非 0 = 有 gate 到达时卡口不在,那次审批走了 fail-closed 路径。 */
 export declare function approvalCardPortMisses(): number;
+/** W1 带 key 变体(miss 计数逐键)。 */
+export declare function approvalCardPortMissesFor(sessionKey: string): number;
 /** 卡口在不在(壳原文 `getLeaderToolUseConfirmQueue()` 那个存在性判据的等价物)。 */
 export declare function hasApprovalCardPort(): boolean;
+/** W1 带 key 变体。 */
+export declare function hasApprovalCardPortFor(sessionKey: string): boolean;
+/** W1 读端:某会话的卡口(未装 = null;**不计 miss** —— miss 只在决断腿真到达时计)。 */
+export declare function approvalCardPortFor(sessionKey: string): ApprovalCardPort | null;
 /** 测试钩:卸口 + 清计数(只卸口不清计数会让「未装配时 misses 为 0」的断言恒假 —— host.ts 同款教训)。 */
 export declare function _resetApprovalCardPortForTest(): void;
 /**

package/dist/hitl/toolApprovalWire.js

@@ -1,5 +1,6 @@
 import { HitlBridge } from './hitlBridge.js';
 import { hostLog } from '../host.js';
+import { createSessionSlot, DEFAULT_SESSION_KEY } from '../sessionSlot.js';
 import { readEngineActiveBgTasks } from '../fleet/fleetLedger.js';
 /** fs 写权限 gate 判定:未来的一等 kind(tool_approval)或按 toolName(server 桥首批=fs 写三件,
  *  [820] 表)。AskUserQuestion 永不进这里(ask 桥先判)。 */
@@ -36,28 +37,48 @@ export function structurallyEqual(a, b) {
         return false;
     return ka.every(k => structurallyEqual(a[k], b[k]));
 }
-let cardPort = null;
-let cardPortMisses = 0;
+// W1(design/161):sessionKey → 注册表;零参 API = DEFAULT_SESSION_KEY 兼容层(cli 装配不动)。
+const cardPortByKey = createSessionSlot();
+const cardPortMissesByKey = new Map();
+function bumpCardPortMiss(sessionKey) {
+    cardPortMissesByKey.set(sessionKey, (cardPortMissesByKey.get(sessionKey) ?? 0) + 1);
+}
 /** 装卡口(传 null 卸)。返回还原函数。 */
 export function installApprovalCardPort(port) {
-    const prev = cardPort;
-    cardPort = port;
+    return installApprovalCardPortFor(DEFAULT_SESSION_KEY, port);
+}
+/** W1 带 key 变体:装/卸某会话的卡口(多会话宿主每会话一键,互不顶盖)。 */
+export function installApprovalCardPortFor(sessionKey, port) {
+    const prev = cardPortByKey.get(sessionKey);
+    cardPortByKey.set(sessionKey, port);
     return () => {
-        cardPort = prev;
+        cardPortByKey.set(sessionKey, prev);
     };
 }
 /** 🔴 宿主自检:恒应为 0。非 0 = 有 gate 到达时卡口不在,那次审批走了 fail-closed 路径。 */
 export function approvalCardPortMisses() {
-    return cardPortMisses;
+    return approvalCardPortMissesFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体(miss 计数逐键)。 */
+export function approvalCardPortMissesFor(sessionKey) {
+    return cardPortMissesByKey.get(sessionKey) ?? 0;
 }
 /** 卡口在不在(壳原文 `getLeaderToolUseConfirmQueue()` 那个存在性判据的等价物)。 */
 export function hasApprovalCardPort() {
-    return cardPort !== null;
+    return hasApprovalCardPortFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体。 */
+export function hasApprovalCardPortFor(sessionKey) {
+    return approvalCardPortFor(sessionKey) !== null;
+}
+/** W1 读端:某会话的卡口(未装 = null;**不计 miss** —— miss 只在决断腿真到达时计)。 */
+export function approvalCardPortFor(sessionKey) {
+    return cardPortByKey.get(sessionKey) ?? null;
 }
 /** 测试钩:卸口 + 清计数(只卸口不清计数会让「未装配时 misses 为 0」的断言恒假 —— host.ts 同款教训)。 */
 export function _resetApprovalCardPortForTest() {
-    cardPort = null;
-    cardPortMisses = 0;
+    cardPortByKey.clear();
+    cardPortMissesByKey.clear();
 }
 /**
  * 共享卡面:弹 vendored CC 三选卡(PermissionRequest)→ 等用户决断。两条腿共用:
@@ -67,8 +88,9 @@ export function _resetApprovalCardPortForTest() {
  * (accept-session 升 intent,[816] 壳侧承诺② —— 与决断通道无关,两腿都要)由**宿主卡口**做。
  */
 export function surfaceApprovalCard(req) {
+    const cardPort = approvalCardPortFor(DEFAULT_SESSION_KEY);
     if (cardPort === null) {
-        cardPortMisses++;
+        bumpCardPortMiss(DEFAULT_SESSION_KEY);
         return Promise.resolve({
             kind: 'failed',
             reason: 'no approval card port installed (print/non-REPL mode, or host forgot installApprovalCardPort)',
@@ -85,7 +107,7 @@ export function surfaceApprovalCard(req) {
  */
 export async function surfaceFsApprovalAndDecide(deps, taskId, argsByCall, signal) {
     if (!hasApprovalCardPort()) {
-        cardPortMisses++;
+        bumpCardPortMiss(DEFAULT_SESSION_KEY);
         return { kind: 'failed', reason: 'no approval card port installed (print/non-REPL mode)' };
     }
     // pending 行 = gate 的权威源 + D-1 绑定 surface(与 ask 桥同姿势)。

package/dist/host.d.ts

@@ -96,23 +96,39 @@ export interface HostPorts {
  * 返回一个还原函数(测试/热重载用)。
  */
 export declare function installHost(ports: HostPorts): () => void;
+/**
+ * W1 带 key 变体:装配某会话的宿主口(多会话宿主每会话一键,互不顶盖;合并语义与零参同)。
+ * ⚠️ 入参不含 `queue` —— 通知队列在 W1 仍是包级单例(notifications.ts 不在五槽位切口内),
+ * per-session 队列归后续工单;要装队列走零参 `installHost({ queue })`。
+ */
+export declare function installHostFor(sessionKey: string, ports: Omit<HostPorts, 'queue'>): () => void;
 /** 日志(缺席 = 静默,**不计 miss**:诊断面本就是可选的)。 */
 export declare function hostLog(level: AdapterLogLevel, msg: string, data?: unknown): void;
 /** 行式探针(缺席 = 静默,不计 miss:同上)。 */
 export declare function hostProbe(channel: string, line: string): void;
 /** settings 口(缺席 = undefined + 计 miss:漏装会让 hooks 整条 wire 静默空掉)。 */
 export declare function hostSettings(): SettingsPort | undefined;
+/** W1 带 key 变体(缺席语义与零参同:undefined + 计该键 miss)。 */
+export declare function hostSettingsFor(sessionKey: string): SettingsPort | undefined;
 /** fs 口(缺席 = undefined + 计 miss)。 */
 export declare function hostFs(): FsPort | undefined;
+/** W1 带 key 变体。 */
+export declare function hostFsFor(sessionKey: string): FsPort | undefined;
 /** 定时器口(缺席 = undefined,不计 miss:T40 竞速本就允许不启用)。 */
 export declare function hostTimers(): TimersPort | undefined;
+/** W1 带 key 变体(同零参:不计 miss)。 */
+export declare function hostTimersFor(sessionKey: string): TimersPort | undefined;
 /** session 口(缺席 = undefined + 计 miss:漏装会让整条 durable 子代读面 404 静默哑掉)。 */
 export declare function hostSession(): SessionPort | undefined;
+/** W1 带 key 变体。 */
+export declare function hostSessionFor(sessionKey: string): SessionPort | undefined;
 /**
  * 🔴 宿主自检出口 —— 恒应为空对象。非空 = 有口漏装,**对应的面已经在静默失效**。
  * 含通知队列的 miss(从 notifications.ts 汇过来,宿主只需看这一个数)。
  */
 export declare function hostPortMisses(): Record<string, number>;
+/** W1 带 key 变体。⚠️ 通知队列是包级单例,其 miss 只折进 DEFAULT_SESSION_KEY 键的视图。 */
+export declare function hostPortMissesFor(sessionKey: string): Record<string, number>;
 /**
  * 测试钩:清空装配与计数。
  * 🔴 队列那一路必须走 `_resetNotificationQueuePortForTest()` 而不是 `installNotificationQueuePort(null)`

package/dist/host.js

@@ -1,11 +1,19 @@
+import { DEFAULT_SESSION_KEY } from './sessionSlot.js';
 import { _resetNotificationQueuePortForTest, installNotificationQueuePort, notificationQueuePortMisses, } from './notifications.js';
-let host = {};
-const misses = Object.create(null);
-const warned = new Set();
-function miss(name) {
-    misses[name] = (misses[name] ?? 0) + 1;
-    if (!warned.has(name)) {
-        warned.add(name);
+const hostByKey = new Map();
+function hostSlot(sessionKey) {
+    let slot = hostByKey.get(sessionKey);
+    if (!slot) {
+        slot = { state: {}, misses: Object.create(null), warned: new Set() };
+        hostByKey.set(sessionKey, slot);
+    }
+    return slot;
+}
+function miss(sessionKey, name) {
+    const slot = hostSlot(sessionKey);
+    slot.misses[name] = (slot.misses[name] ?? 0) + 1;
+    if (!slot.warned.has(name)) {
+        slot.warned.add(name);
         // eslint-disable-next-line no-console
         console.error(`[client-core] host port "${name}" NOT installed — the surface it drives is silently inert. ` +
             'Host must call installHost({ ' +
@@ -21,58 +29,90 @@ function miss(name) {
  * 返回一个还原函数(测试/热重载用)。
  */
 export function installHost(ports) {
-    const prev = { ...host };
+    const restore = installHostFor(DEFAULT_SESSION_KEY, ports);
+    if ('queue' in ports)
+        installNotificationQueuePort(ports.queue ?? null);
+    return restore;
+}
+/**
+ * W1 带 key 变体:装配某会话的宿主口(多会话宿主每会话一键,互不顶盖;合并语义与零参同)。
+ * ⚠️ 入参不含 `queue` —— 通知队列在 W1 仍是包级单例(notifications.ts 不在五槽位切口内),
+ * per-session 队列归后续工单;要装队列走零参 `installHost({ queue })`。
+ */
+export function installHostFor(sessionKey, ports) {
+    const slot = hostSlot(sessionKey);
+    const prev = { ...slot.state };
     if ('log' in ports)
-        host.log = ports.log;
+        slot.state.log = ports.log;
     if ('probe' in ports)
-        host.probe = ports.probe;
+        slot.state.probe = ports.probe;
     if ('timers' in ports)
-        host.timers = ports.timers;
+        slot.state.timers = ports.timers;
     if ('settings' in ports)
-        host.settings = ports.settings;
+        slot.state.settings = ports.settings;
     if ('fs' in ports)
-        host.fs = ports.fs;
+        slot.state.fs = ports.fs;
     if ('session' in ports)
-        host.session = ports.session;
-    if ('queue' in ports)
-        installNotificationQueuePort(ports.queue ?? null);
+        slot.state.session = ports.session;
     return () => {
-        host = prev;
+        slot.state = prev;
     };
 }
 /** 日志(缺席 = 静默,**不计 miss**:诊断面本就是可选的)。 */
 export function hostLog(level, msg, data) {
-    host.log?.(level, msg, data);
+    hostSlot(DEFAULT_SESSION_KEY).state.log?.(level, msg, data);
 }
 /** 行式探针(缺席 = 静默,不计 miss:同上)。 */
 export function hostProbe(channel, line) {
-    host.probe?.(channel, line);
+    hostSlot(DEFAULT_SESSION_KEY).state.probe?.(channel, line);
 }
 /** settings 口(缺席 = undefined + 计 miss:漏装会让 hooks 整条 wire 静默空掉)。 */
 export function hostSettings() {
-    return host.settings ?? miss('settings');
+    return hostSettingsFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体(缺席语义与零参同:undefined + 计该键 miss)。 */
+export function hostSettingsFor(sessionKey) {
+    return hostSlot(sessionKey).state.settings ?? miss(sessionKey, 'settings');
 }
 /** fs 口(缺席 = undefined + 计 miss)。 */
 export function hostFs() {
-    return host.fs ?? miss('fs');
+    return hostFsFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体。 */
+export function hostFsFor(sessionKey) {
+    return hostSlot(sessionKey).state.fs ?? miss(sessionKey, 'fs');
 }
 /** 定时器口(缺席 = undefined,不计 miss:T40 竞速本就允许不启用)。 */
 export function hostTimers() {
-    return host.timers;
+    return hostTimersFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体(同零参:不计 miss)。 */
+export function hostTimersFor(sessionKey) {
+    return hostSlot(sessionKey).state.timers;
 }
 /** session 口(缺席 = undefined + 计 miss:漏装会让整条 durable 子代读面 404 静默哑掉)。 */
 export function hostSession() {
-    return host.session ?? miss('session');
+    return hostSessionFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体。 */
+export function hostSessionFor(sessionKey) {
+    return hostSlot(sessionKey).state.session ?? miss(sessionKey, 'session');
 }
 /**
  * 🔴 宿主自检出口 —— 恒应为空对象。非空 = 有口漏装,**对应的面已经在静默失效**。
  * 含通知队列的 miss(从 notifications.ts 汇过来,宿主只需看这一个数)。
  */
 export function hostPortMisses() {
-    const out = { ...misses };
-    const q = notificationQueuePortMisses();
-    if (q > 0)
-        out.queue = q;
+    return hostPortMissesFor(DEFAULT_SESSION_KEY);
+}
+/** W1 带 key 变体。⚠️ 通知队列是包级单例,其 miss 只折进 DEFAULT_SESSION_KEY 键的视图。 */
+export function hostPortMissesFor(sessionKey) {
+    const out = { ...hostSlot(sessionKey).misses };
+    if (sessionKey === DEFAULT_SESSION_KEY) {
+        const q = notificationQueuePortMisses();
+        if (q > 0)
+            out.queue = q;
+    }
     return out;
 }
 /**
@@ -82,9 +122,6 @@ export function hostPortMisses() {
  * 让「未装配时 misses 为空」这类断言恒假(B4 首写时就撞上了)。
  */
 export function _resetHostForTest() {
-    host = {};
-    for (const k of Object.keys(misses))
-        delete misses[k];
-    warned.clear();
+    hostByKey.clear();
     _resetNotificationQueuePortForTest();
 }

package/dist/index.d.ts

@@ -182,6 +182,7 @@ export * from './adapter/runStream.js';
 export * from './request/taskRequest.js';
 export * from './clientSlice.js';
 export * from './host.js';
+export { DEFAULT_SESSION_KEY } from './sessionSlot.js';
 export * from './scratchpadWireCaps.js';
 export * from './toolResult.js';
 export * from './diff/patch.js';
@@ -217,3 +218,5 @@ export * from './hitl/approvalsFeed.js';
 export * from './compensations.js';
 export * from './request/printNotification.js';
 export * from './seatContract.js';
+export * from './agentSession/contract.js';
+export * from './agentSession/backgroundView.js';

package/dist/index.js

@@ -197,6 +197,10 @@ export * from './clientSlice.js';
 // 包级宿主装配(per-turn 的 AdapterContext 之外的那一层:settings / fs / queue / timers)。
 // 🔴 `installNotificationQueuePort` 仍是队列的真源出口,`installHost({queue})` 只是直通它。
 export * from './host.js';
+// W1(design/161):五个模块级单槽位的 per-session 注册表键。零参旧 API 全部等价于用这个键调
+// `*For(sessionKey, …)` 变体;多会话宿主(desktop)每会话一键。`createSessionSlot` 是包内实现件,
+// 刻意不出 barrel(公面只承诺键与各槽位的 *For API)。
+export { DEFAULT_SESSION_KEY } from './sessionSlot.js';
 // B2 判给 B4 的宿主耦合件之一(小的那件,同时是 FsPort 的端到端证明)。
 export * from './scratchpadWireCaps.js';
 // ── B5 批:工具结果卡 B/D/E 层 + T20 客户端 diff(2026-07-27)────────────────────────────────
@@ -290,3 +294,11 @@ export * from './request/printNotification.js';
 //    → `LOCAL_SESSIONS_SPEC` 键集(run-seat-contract-keys-test 运行期对账)。加 verb 忘了加 SPEC
 //    的后果不是报错而是 preload 不注册 channel、渲染端读到 undefined(假 affordance 家族)。
 export * from './seatContract.js';
+// ── design/161 实现批 A:后台任务归一视图平行入口(2026-07-30)────────────────────────────────
+// 契约收敛物 contract.ts 随首件实现落地转正常出口(「实现落地一件出口一件」——
+// createBackgroundView 是第一件;portability 门 TYPE_ONLY_MODULES 同批摘除该登记)。
+// contract.ts 仍是纯类型零运行时,`export *` 在 dist 里是空转发 —— 类型面从此进公面。
+export * from './agentSession/contract.js';
+// 两源(assistant.tasks 跨 session 调度总览 + fleet 常驻 SSE 快照)独立拉取独立降级的归一投影;
+// 两张 status 映射表 never 卫兵穷举;'not-configured' 判别姿势见文件头注。
+export * from './agentSession/backgroundView.js';

package/dist/liveQuestionStore.d.ts

@@ -1,8 +1,3 @@
-/**
- * ⇄ B1 批搬迁(2026-07-27,多端改造设计稿 §2.4.1-B):cli src/sema/liveQuestionStore.ts 逐字搬入(零依赖;壳侧改 re-export)。
- * 本模块自持 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).
@@ -80,11 +75,18 @@ export declare function registerLocalQuestionResponder(id: string, fn: RespondFn
  * break the live stream drain (the run must keep flowing; a lost frame just headless-defaults the ask).
  */
 export declare function publishQuestionFrame(frame: QuestionFrame): void;
+/** W1 keyed variant: publish to ONE session's overlay (multi-session hosts demux by their own key). */
+export declare function publishQuestionFrameFor(sessionKey: string, frame: QuestionFrame): void;
 /** 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 declare function hasQuestionOverlay(): boolean;
+/** W1 keyed variant. */
+export declare function hasQuestionOverlayFor(sessionKey: string): boolean;
 /** Subscribe the UI overlay to live question frames. Returns an unsubscribe. Last writer wins (one overlay). */
 export declare function onQuestionFrame(handler: QuestionFrameHandler): () => void;
+/** 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 declare function onQuestionFrameFor(sessionKey: string, handler: QuestionFrameHandler): () => void;
 /** Publish the live client's `questions.respond` binding (called from createLiveConversationClient). `null`
  *  clears it (offline/mock → respondToQuestion rejects cleanly). */
 export declare function setQuestionRespond(fn: RespondFn | null): void;

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/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/workflowClient.d.ts

@@ -15,6 +15,26 @@ export interface LiveWorkflowController {
         runId: string | null;
         lastError: string | null;
     };
+    /**
+     * Subscribe to "the projected snapshot changed" — fired on the FIRST successful `get()` and on every
+     * subsequent re-project. Returns an unsubscribe.
+     *
+     * WHY (clay 2026-07-30 症状②「入场蹲卡」): every host polls `snapshot()` on its own 1s interval, so a
+     * `get()` that answered in 50ms still took up to 1s to reach the screen — a purely self-inflicted delay,
+     * and during that window the panel renders its not-yet-resolved fill. The interval stays (it also drives
+     * the wall-clock cells: idle/duration/waiting), but the FIRST resolve no longer waits for a tick.
+     *
+     * 🔴 SUBSCRIBE-AND-RECONCILE: if a snapshot has ALREADY resolved by the time you subscribe, the callback fires
+     * ONCE synchronously from `subscribe` itself. Without this the notify arm and the subscribe arm do not share a
+     * premise — a host that renders (snapshot null) → subscribes in an effect loses the notify entirely whenever
+     * `get()` won that race, and falls back to waiting a full poll tick. That is exactly the residual outlier the
+     * entry-latency fence caught (2 of 3 runs ≈200-340ms, 1 run ≈1026ms = one whole tick).
+     *
+     * Contract: the callback runs INSIDE the source's own loop (or synchronously from `subscribe`) — hosts must only
+     * schedule a re-render from it, never re-enter the controller synchronously. A throwing callback is swallowed so
+     * one bad subscriber cannot kill the background consumer.
+     */
+    subscribe(onChange: () => void): () => void;
     /** abort the underlying SSE stream + stop the background loop (host unmount). */
     dispose(): void;
 }