@sema-agent/client-core 0.11.6 → 0.11.7

package/dist/request/taskRequest.d.ts

@@ -79,6 +79,8 @@ export interface TaskRequestInput {
     promptProfile?: string;
     enableFork?: boolean;
     attachments?: Record<string, unknown>;
+    /** 预上传附件句柄(`uploadAttachment` 回执 id)。空数组 = 没带附件 ⇒ 整键不 stamp。 */
+    attachmentIds?: readonly string[];
     finalVerification?: boolean;
     limits?: Record<string, unknown>;
     interactiveTools?: false;

package/dist/request/taskRequest.js

@@ -28,7 +28,12 @@ export const REQUEST_FIELD_MATRIX = [
     { field: 'finalVerification', lanes: ['print'], live: true, why: 'P1-1 终验:无人值守车道才需要引擎自证;交互 REPL 由人当场看结果。#106 裁 B(让位+告知)后交互面默认关' },
     { field: 'limits', lanes: ['print'], live: true, why: 'P2-3-b:`-p` 的预算护栏(--max-* flag 族),交互 REPL 由人随时 Esc' },
     { field: 'interactiveTools', lanes: ['print'], live: true, why: '[909]B 件3:无人值守 stamp false,从 roster 源头灭掉 AskUserQuestion/plan 门。交互车道 stamp false 等于自废武功' },
-    // ── TUI 独有 ────────────────────────────────────────────────────────────────────────────────
+    // ── interactive 车道独有 ────────────────────────────────────────────────────────────────────
+    // ⚠️ 「interactive」**不等于**「TUI」:web 的 BFF lane 也报 `interactive`
+    //    (`sema-web-client` `WEB_REQUEST_LANE`)。下面多数条目的理由写的是壳的 TUI 面 —— 它们是
+    //    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: '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 },
@@ -106,6 +111,10 @@ export function buildTaskRequest(input, lane) {
         ...(on('promptProfile', input.promptProfile) ? { promptProfile: input.promptProfile } : {}),
         ...(on('enableFork', input.enableFork) ? { enableFork: input.enableFork } : {}),
         ...(on('attachments', input.attachments) ? { attachments: input.attachments } : {}),
+        // 空数组按 `images` 同款处理:没带附件与「带了 0 个附件」在 wire 上是同一件事,发小的那个。
+        ...(on('attachmentIds', input.attachmentIds) && (input.attachmentIds?.length ?? 0) > 0
+            ? { attachmentIds: [...(input.attachmentIds ?? [])] }
+            : {}),
         ...(on('clientContext', input.clientContext) ? { clientContext: input.clientContext } : {}),
         ...(on('scratchpadDir', input.scratchpadDir) ? { scratchpadDir: input.scratchpadDir } : {}),
         ...(on('finalVerification', input.finalVerification)

package/dist/seatContract.d.ts

@@ -10,8 +10,12 @@
  * 「接缝记账」里写下的第 1 条,它一直没被销账的原因就是没有任何机制会让它红。
  *
  * 落点为什么是本包:desktop 与 web 都已经依赖 `@sema-agent/client-core`(0.11.5),而本文件是
- * **纯类型 + 常量 + 纯谓词**,零 import、零 Node 内建 ⇒ 不动本包的可移植闭包(portability 门的
+ * **纯类型 + 常量 + 纯谓词**,零值级 import、零 Node 内建 ⇒ 不动本包的可移植闭包(portability 门的
  * `EXPECTED_PACKAGES_INDEX` 一个字不变)。
+ * ⚠️ 唯一一条 `import type`(`./effortWire.js` 的 `ReasoningEffort`)是**类型边**:portability 门
+ * 走值级传递闭包时按规则剥掉 type-only import(门里 `/^\s*type\b/` 那一跳),bundle 里一个字节都
+ * 不多。写成 import 而不是就地复刻那七档,是因为「座位闭集」与「wire 投影闭集」必须是**同一套词**
+ * ——复刻一份就等于埋一条只有真用户能发现的漂移(拨盘上的档在座位 lane 上静默到不了引擎)。
  *
  * ── 搬迁时按「真源为准」收敛的漂移(逐条,web 侧镜像 → 本文件)────────────────────────────
  *  🔴 D1 `LocalSessionEvent.outcome` —— web 镜像整位缺席 ⇒ `tool_permission_resolved` 只会清面,
@@ -50,6 +54,7 @@
  * neutral typed position. Our implementation体 differs (sema wire via @sema-agent/sdk +
  * @sema-agent/client-core), the contract shape does not.
  */
+import type { ReasoningEffort } from "./effortWire.js";
 export type EipcMethodKind = "invoke" | "event";
 export interface EipcMethodSpec {
     kind: EipcMethodKind;
@@ -258,6 +263,29 @@ export declare const PERMISSION_MODE_INTENTS: readonly PermissionModeIntent[];
 /** Per-task attachment cap — the server's own limit (`attachmentIds` > 16 ⇒ 400). Gated here so the
  *  seat gets a precise local error instead of a wire 400 halfway through a turn. */
 export declare const ATTACHMENT_IDS_PER_TASK_CAP = 16;
+/** The per-turn `reasoningEffort` accept-set — core's ThinkingLevel tiers, re-exported from the
+ *  package's own wire projection (`effortWire.ReasoningEffort`) rather than re-typed here.
+ *
+ *  CLOSED for the same reason `PERMISSION_MODE_INTENTS` is: the word ORIGINATES in our own composer
+ *  and travels OUT to a wire that 400s (fail-loud) on an unknown tier — so an unknown value is a
+ *  local bug we want reported at the seat's door, not a future wire word to tolerate. `ultracode` is
+ *  deliberately NOT a tier here: in CC it is a standalone `settings.ultracode` preset boolean that
+ *  COEXISTS with `xhigh` (see `SeatTurnSettings`), and folding it into this axis is exactly how the
+ *  orchestration axis gets eaten by the reasoning axis. */
+export declare const SEAT_REASONING_EFFORTS: readonly ReasoningEffort[];
+/** The `settings` sub-object a seat turn may carry. A CLOSED set with its own name list + pin,
+ *  exactly like the top-level request: `SEND_MESSAGE_REQUEST_KEYS` checks `keyof SendMessageRequest`
+ *  (top-level names), so a dotted `"settings.ultracode"` entry could never be pinned by `Covers` —
+ *  the shape that stays consistent with the existing closed sets is one top-level key plus a nested
+ *  closed set of its own. */
+export interface SeatTurnSettings {
+    /** CC's `settings.ultracode` PRESET boolean (max thinking × workflow orchestration, service ≥1.48.0
+     *  reads `body.settings.ultracode` and expands it). NOT a seventh effort tier — the dial separately
+     *  coerces the reasoning axis to `xhigh`, and collapsing the two loses the orchestration half
+     *  (`ultracodeWireCaps` in this package records that semantics verbatim). */
+    ultracode?: boolean;
+}
+export declare const SEAT_TURN_SETTINGS_KEYS: readonly ["ultracode"];
 export interface SendMessageRequest {
     sessionId: string;
     text: string;
@@ -270,6 +298,23 @@ export interface SendMessageRequest {
      *  Bytes never ride this call: they went up once through the dedicated verb and the engine
      *  materializes them into the run's `attachments/` dir. */
     attachmentIds?: string[];
+    /** Per-turn `/effort` dial pick → `TaskRequest.reasoningEffort`. Omit ⇒ the engine's own default.
+     *  Closed set (`SEAT_REASONING_EFFORTS`) — gate it at the host's door, not at the wire.
+     *
+     *  🔴 Why this position exists (web 收编第一批, 2026-07-29): it did NOT, and the absence was
+     *  STRUCTURAL — the seat lane's only payload is this closed-set interface, so the composer's effort
+     *  dial had nowhere to put the user's pick and the web client honestly disabled the control on the
+     *  desktop seat lane. "The control is missing" was the visible symptom; the missing wire position
+     *  was the cause. */
+    reasoningEffort?: ReasoningEffort;
+    /** Keep this turn's background processes alive past the turn boundary → `TaskRequest.
+     *  retainBackgroundProcesses`. Same structural-absence story as `reasoningEffort` above; the
+     *  shell's lane defaults it ON (2026-07-26 flip), so a seat that cannot send it is not "defaulting
+     *  to the same thing" — it is letting the ENGINE's default decide, which is a different decision. */
+    retainBackgroundProcesses?: boolean;
+    /** Per-turn settings sub-object → `TaskRequest.settings`. Closed shape (`SeatTurnSettings`);
+     *  today's only member is the `ultracode` preset boolean. */
+    settings?: SeatTurnSettings;
 }
 /** `uploadAttachment` receipt — the SDK's `AttachmentInfo` verbatim (server POST /v1/attachments 201).
  *  `name` is the SERVER's sanitized basename, not the local filename: it is the name the engine
@@ -436,6 +481,6 @@ export declare const SEAT_EVENT_METHOD_NAMES: readonly ["onEvent", "onToolPermis
 export declare const LOCAL_SESSION_EVENT_KEYS: readonly ["type", "sessionId", "message", "messages", "error", "errorCategory", "code", "request", "data", "sources", "permissionMode", "session", "userMessageUuid", "hasPreClearSession", "requestId", "outcome", "chrome"];
 export declare const TOOL_PERMISSION_REQUEST_KEYS: readonly ["requestId", "sessionId", "toolName", "toolCallId", "input", "message", "boundCallId", "boundInputHash", "createdAt"];
 export declare const LOCAL_SESSION_RECORD_KEYS: readonly ["sessionId", "engineSessionId", "model", "title", "isRunning", "createdAt", "lastActivityAt", "queuedMessages"];
-export declare const SEND_MESSAGE_REQUEST_KEYS: readonly ["sessionId", "text", "model", "userMessageUuid", "permissionMode", "attachmentIds"];
+export declare const SEND_MESSAGE_REQUEST_KEYS: readonly ["sessionId", "text", "model", "userMessageUuid", "permissionMode", "attachmentIds", "reasoningEffort", "retainBackgroundProcesses", "settings"];
 export declare const TOOL_PERMISSION_DECISION_KEYS: readonly ["sessionId", "requestId", "decision", "answer", "updatedInput", "remember"];
 export declare const START_SESSION_OPTION_KEYS: readonly ["model", "title", "cwd", "excludeTools"];

package/dist/seatContract.js

@@ -10,8 +10,12 @@
  * 「接缝记账」里写下的第 1 条,它一直没被销账的原因就是没有任何机制会让它红。
  *
  * 落点为什么是本包:desktop 与 web 都已经依赖 `@sema-agent/client-core`(0.11.5),而本文件是
- * **纯类型 + 常量 + 纯谓词**,零 import、零 Node 内建 ⇒ 不动本包的可移植闭包(portability 门的
+ * **纯类型 + 常量 + 纯谓词**,零值级 import、零 Node 内建 ⇒ 不动本包的可移植闭包(portability 门的
  * `EXPECTED_PACKAGES_INDEX` 一个字不变)。
+ * ⚠️ 唯一一条 `import type`(`./effortWire.js` 的 `ReasoningEffort`)是**类型边**:portability 门
+ * 走值级传递闭包时按规则剥掉 type-only import(门里 `/^\s*type\b/` 那一跳),bundle 里一个字节都
+ * 不多。写成 import 而不是就地复刻那七档,是因为「座位闭集」与「wire 投影闭集」必须是**同一套词**
+ * ——复刻一份就等于埋一条只有真用户能发现的漂移(拨盘上的档在座位 lane 上静默到不了引擎)。
  *
  * ── 搬迁时按「真源为准」收敛的漂移(逐条,web 侧镜像 → 本文件)────────────────────────────
  *  🔴 D1 `LocalSessionEvent.outcome` —— web 镜像整位缺席 ⇒ `tool_permission_resolved` 只会清面,
@@ -124,6 +128,25 @@ export const PERMISSION_MODE_INTENTS = [
 /** Per-task attachment cap — the server's own limit (`attachmentIds` > 16 ⇒ 400). Gated here so the
  *  seat gets a precise local error instead of a wire 400 halfway through a turn. */
 export const ATTACHMENT_IDS_PER_TASK_CAP = 16;
+/** The per-turn `reasoningEffort` accept-set — core's ThinkingLevel tiers, re-exported from the
+ *  package's own wire projection (`effortWire.ReasoningEffort`) rather than re-typed here.
+ *
+ *  CLOSED for the same reason `PERMISSION_MODE_INTENTS` is: the word ORIGINATES in our own composer
+ *  and travels OUT to a wire that 400s (fail-loud) on an unknown tier — so an unknown value is a
+ *  local bug we want reported at the seat's door, not a future wire word to tolerate. `ultracode` is
+ *  deliberately NOT a tier here: in CC it is a standalone `settings.ultracode` preset boolean that
+ *  COEXISTS with `xhigh` (see `SeatTurnSettings`), and folding it into this axis is exactly how the
+ *  orchestration axis gets eaten by the reasoning axis. */
+export const SEAT_REASONING_EFFORTS = [
+    "off",
+    "minimal",
+    "low",
+    "medium",
+    "high",
+    "xhigh",
+    "max",
+];
+export const SEAT_TURN_SETTINGS_KEYS = ["ultracode"];
 // ───────────────────────────── validators (CC dual-gate posture) ─────────────────────────────
 export function isLocalSessionRecord(s) {
     const e = s;
@@ -381,6 +404,11 @@ export const SEND_MESSAGE_REQUEST_KEYS = [
     "userMessageUuid",
     "permissionMode",
     "attachmentIds",
+    // 2026-07-29(web 收编第一批②):三位补齐。此前座位 lane **结构性**拿不到它们 —— 闭集就是
+    // 载体本身,不在集里 = 那个决定在这条 lane 上根本没有位置可放。
+    "reasoningEffort",
+    "retainBackgroundProcesses",
+    "settings",
 ];
 export const TOOL_PERMISSION_DECISION_KEYS = [
     "sessionId",
@@ -394,5 +422,6 @@ export const START_SESSION_OPTION_KEYS = ["model", "title", "cwd", "excludeTools
 const _seatContractPins = [
     true, true, true, true, true, true, true, true, true,
     true, true, true, true, true, true, true, true,
+    true, true,
 ];
 void _seatContractPins;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/client-core",
-  "version": "0.11.6",
+  "version": "0.11.7",
   "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",