@sema-agent/client-core 0.77.0 → 0.77.2

package/dist/seatContract.d.ts

@@ -1,574 +1,135 @@
-/**
- * seatContract — desktop/web **座位 IPC 契约的单一真源**(design/159 B18,2026-07-29)。
- *
- * 搬迁前的形:同一份契约有**两份声明**,而且跨仓名字零重合 ——
- *   · `sema-desktop/src/shared/localSessions.ts`  = 15 个类型 + 3 个词表常量 + 6 个校验器 + SPEC(生产端)
- *   · `sema-web-client/ui/lib/desktop/local-sessions-transport.ts` = 9 个 `Seat*` 本地重声明(消费端)
- * 两边名字不同 ⇒ **编译器永远不会告诉你它们漂了**。实测已经漂了(见下「漂移清单」),其中
- * `LocalSessionEvent.outcome` 那一条是真 bug:宿主发了词、消费端的镜像里根本没有这个位,
- * 于是「拒绝 / TTL 到点 / 人点了允许」在屏上长得一模一样 —— 正是 localSessions 自己在
- * 「接缝记账」里写下的第 1 条,它一直没被销账的原因就是没有任何机制会让它红。
- *
- * 落点为什么是本包:desktop 与 web 都已经依赖 `@sema-agent/client-core`(0.11.5),而本文件是
- * **纯类型 + 常量 + 纯谓词**,零值级 import、零 Node 内建 ⇒ 不动本包的可移植闭包(portability 门的
- * `EXPECTED_PACKAGES_INDEX` 一个字不变)。
- * ⚠️ 两条 `import type`(`./effortWire.js` 的 `ReasoningEffort`、`./seam.js` 的 `LaneProof`)都是
- * **类型边**:portability 门走值级传递闭包时按规则剥掉 type-only import(门里 `/^\s*type\b/` 那一跳),
- * bundle 里一个字节都不多。写成 import 而不是就地复刻,是因为「座位闭集」与「wire 投影闭集」必须是
- * **同一套词**——复刻一份就等于埋一条只有真用户能发现的漂移(拨盘上的档在座位 lane 上静默到不了引擎;
- * 车道证明在座位面变成一个「有位无证」的空对象)。
- *
- * ── 搬迁时按「真源为准」收敛的漂移(逐条,web 侧镜像 → 本文件)────────────────────────────
- *  🔴 D1 `LocalSessionEvent.outcome` —— web 镜像整位缺席 ⇒ `tool_permission_resolved` 只会清面,
- *      不会告诉用户为什么工具没跑。**真 bug**,本批只做「位补回来」;把词渲成可见痕迹是渲染面的活。
- *  D2 `SendMessageRequest.permissionMode` —— web 镜像是裸 `string`,真源是闭集 `PermissionModeIntent`,
- *      而宿主入站门 `requireOptionalPermissionMode` 是**会抛的闭集门**。今日两边词表逐字相等
- *      (web `ComposerMode` 五档 ≡ `PERMISSION_MODE_INTENTS` 五档,已核),所以是**潜伏**不是现症:
- *      ComposerMode 哪天加一档,裸 string 一路放行到宿主门口才抛。收敛成闭集后当天编译红。
- *  D3 `AttachmentUploadReceipt.sha256` / `ToolPermissionRequest.createdAtMs` / `StartSessionOptions.cwd`
- *      / `.excludeTools` / `LocalSessionRecord.queuedMessages`·`model`·`engineSessionId` ——
- *      web 镜像缺位。都是「没接线」不是「接错线」(web 侧今日无消费点,已核),收敛后位在、待接。
- *  D4 `LocalSessionEvent.request` —— 真源有这个位,**宿主从不发**(session-host 零处写 `request:`);
- *      web 镜像没有它反而与运行时事实一致。真源保留该位(CC `fQe` 的 form 位),记在这里免得
- *      下一棒把「web 没有」当成漏。
- *  D5 `EipcStoreClient.getStateSync` web 侧是 optional、真源是 required;`SeatSessionDirectoryRow.createdAt`
- *      web 侧 optional、真源 required。两条都是「更弱」方向,收敛到真源即可(宿主校验器
- *      `isLocalSessionRecord` 本来就要求 createdAt 在场,运行时保证一直成立)。
- *  · web 侧**没有**镜像、因而至今拿不到的面:队列三动词 / setFocusedSession / setModel /
- *    focusedSessionState / settingsState / `CHROME_EVENT_KINDS` / `ATTACHMENT_IDS_PER_TASK_CAP`。
- *    本文件导出后它们对 web 首次可见(接不接线是渲染面的决定)。
- *
- * ── 🔴 wave2 卡E-seat 的**破坏性契约变更**(2026-08-02,REF-CC-064~070/072~074;发包说明点名)──
- *  ① `EipcMethodSpec.validate` / `EipcStoreSpec.validate` → **改名 `check`**,返回形从 `boolean`
- *     升成 `true | SeatValidationFailure`(REF-CC-069)。改名是**安全机制不是洁癖**:老消费点写的是
- *     `if (m.validate && !m.validate(v))`,而失败**对象是真值** ⇒ 那一行会把「不合格」读成「合格」,
- *     门从 fail-closed 静默变成 fail-open。改名让每个旧调用点在编译期红,而不是在运行期悄悄放行。
- *  ② `ToolPermissionRequest.createdAt: number` → **`createdAtMs`**(REF-CC-067):同一文件里
- *     `LocalSessionRecord.createdAt` 是 ISO 串,两个同名位两种域两种类型;epoch 单位入名(A4)。
- *  ③ `ToolPermissionRequest.boundCallId` + `.boundInputHash` → **合成 `toctouBinding`**
- *     (REF-CC-070):注释一直把它称作 pair,而类型/门此前各查各的,半个 pair 照样过门。
- *  ④ `LocalSessionEvent.chrome.laneProof` **可选 → 必填**且升成命名类型 `LaneProof`(REF-CC-064)——
- *     出站门本来就要求它在场,类型却说可以缺席:一个照着这份「单一真源」写的宿主编译全绿、
- *     事件被整条丢掉、而门只回 boolean 说不出为什么。这条是本卡的 bug 修复位。
- *  ⑤ `LocalSessionEvent.type` / `.chrome.kind` / `.permissionMode` 三个位闭集化(REF-CC-065)。
- *  ⑥ `uploadAttachment` 入参、`getTranscript`/`searchSessions` 返回形、三个 store 状态形全部提成
- *     具名 interface(REF-CC-072/073/074),SPEC 里 13 个内联匿名 validator 收成具名 `check*`。
- *  三端消费坐标见本批 commit message 的「候提货单」节。
- *
- * ── 沿革(以下正文自 sema-desktop/src/shared/localSessions.ts 逐字迁入)──────────────────────
- * LocalSessions — the desktop host's session service contract, FORM-ported from the CC desktop
- * app's `claude.web / LocalSessions` eipc interface (212 methods there; FIRST BATCH here = the four
- * families clay scoped: session lifecycle / event subscription / interrupt / approvals).
- *
- * Naming: CC ns `claude.web` → `sema.web` (brand table). Method names kept verbatim where the CC
- * method exists (`start`/`stop`/`interrupt`/`sendMessage`/`onEvent`/`onToolPermissionRequest`/
- * `respondToToolPermission` are all real CC LocalSessions methods — see the 854-channel census).
- *
- * ══ 🔴 证据等级标注:本文件的 CC 断言取自**桌面 unpack**,本地语料库不可复验 ════════════════
- *
- * (test [5087] 提出的「语料**种类**缺口」,cli [5088] 认领三件之①,随 0.42.0 落;判据形见下)
- *
- * 本文件里所有以「CC 如何如何」为形的断言 —— 上面那句「212 methods / 854-channel census /
- * 方法名逐字保留」、下面 `checkLocalSessionEvent` 的「CC 的 `fQe` 逐字段对照」、以及一切引
- * `.vite/build/index.chunk-*.js` 坐标的句子 —— **证据等级 = 桌面 unpack(CC Electron app 的
- * `.vite/build` 产物),本地语料库不可复验**。
- *
- * 为什么这一条必须写在这里(而不是只写进台账):
- *   · 本仓手边可复验的参照语料**只覆盖终端 CLI 形态**的静态产物,**没有**桌面壳的 unpack 产物。
- *     这不是「语料版本旧」,是**产物形态不对** —— 拿 CLI 形态的语料去 grep 桌面壳里的符号只会得到
- *     零命中,而零命中在这里**既不能证真也不能证伪**;
- *   · 「CC 取证纪律」要求 CC 断言的合法证据只有两种:本机 claude 实测,或语料二进制直证。本文件
- *     的这一批两种都够不着 ⇒ 断言**保留**(它当初是照着真产物写的),但**必须带着这个等级一起读**;
- *   · 🔴 **这段注释随 `dist/*.d.ts` 出包**,三端读到的就是它。只把等级写进不进 tarball 的台账,
- *     消费端读到的仍是一句看起来可复验、实际不可复验的断言(与本文件 `workerBadge` 出身订正
- *     同一条理由)。
- *
- * **对下游的判据**:凡要对这些断言做「CC 到底是不是这样」的复核,**别拿终端 CLI 形态的语料当反证**
- * ——零命中是语料形态缺口的必然结果,不是断言错。真正的复核路只有一条:取一份 CC 桌面版
- * unpack 产物再对照(已在册为独立小件,做成后参照语料库增桌面形态子目录)。
- *
- * Event payload contract: ported in FORM from CC's `onEvent` runtime validator `fQe`
- * (unpack `.vite/build/index.chunk-CnWKsyE_.js:369773`;**证据等级:桌面 unpack,本地语料库
- * 不可复验** —— 见上方标注段). The load-bearing property we keep
- * byte-faithful ([1832] axiom 2, independently proven by CC's own code): on an otherwise
- * fully-schema'd IPC surface, the `message`/`messages` fields (= CC session-vocabulary SDKMessage
- * bodies, our transcript plane) are UNVALIDATED passthrough positions, while every other field is a
- * 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";
 import type { LaneProof } from "./seam.js";
 import type { QuestionAnswer } from "./liveQuestionStore.js";
 import type { ToolApprovalDelegation } from "./hitl/toolApprovalWire.js";
-/** 一次门校验的失败说明。 */
 export interface SeatValidationFailure {
-    /** 人可读的失败原因,恒在场且非空(宿主日志里那一行的正文)。 */
     reason: string;
-    /** 出错的那个键名(嵌套位用点号,如 `chrome.laneProof`)。
-     *  缺席 = 这次失败**不归属某一个字段**(整体不是对象 / 是跨字段的联合判据)⇒ 宿主日志只打
-     *  `service.method` + `reason`,**绝不**回落成 `"unknown"` 或空串当字段名 —— 编出来的字段名会把
-     *  排查引到一个根本没出问题的位上(§B10 同族:缺席要如实渲缺席,不是造一个值)。 */
     field?: string;
 }
-/**
- * 门的返回形:成功恰是 `true`(**只有一种写法**,消费端 `=== true` 判定即可),失败带原因。
- *
- * 🔴 为什么不是 `boolean`:这一族门是 fail-closed 的(见 `EipcMethodSpec.check` 的头注),false 时
- * 整条事件/结果都不发。而 boolean 里没有任何位能说出是哪个字段哪条规则不过 —— 渲染端的现象是
- * 「这个面偶尔什么都不来」,宿主端的现象是零日志,两端都无从下手(REF-CC-064 就是这么被埋住的)。
- * 🔴 为什么消费端必须写 `=== true` 而不是 `if (!check(v))`:失败是**对象**(真值)。老写法会把
- * 不合格读成合格 —— 这正是本批把位名从 `validate` 改成 `check` 的原因:让老写法编译期就红。
- */
 export type SeatValidation = true | SeatValidationFailure;
 export type EipcMethodKind = "invoke" | "event";
 export interface EipcMethodSpec {
     kind: EipcMethodKind;
-    /** invoke: validates the impl's RESULT before it crosses back to the renderer (CC's outbound
-     *  schema gate — `Result from method "<m>" in interface "<S>" failed to pass validation`).
-     *  event: validates the PAYLOAD before `webContents.send` (CC's dispatcher-side validator, the
-     *  `fQe` position for `LocalSessions.onEvent`). Absent = any result/payload passes (CC has
-     *  `void`-returning methods with trivially-true validators).
-     *  🔴 位名 `check`(REF-CC-069,原 `validate`):返回 `true | SeatValidationFailure`,消费端必须
-     *  写 `if (verdict !== true)` 并把 `reason`/`field` 打进宿主日志 —— 一条被门吃掉的事件从此可诊断。 */
     check?: (value: unknown) => SeatValidation;
 }
 export interface EipcStoreSpec {
-    /** Validates the STATE payload both on read replies and on update pushes (fail-closed like the
-     *  method gates). Absent = any state passes. 位名与返回形同 `EipcMethodSpec.check`。 */
     check?: (state: unknown) => SeatValidation;
 }
 export interface EipcServiceSpec {
     ns: string;
     service: string;
     methods: Record<string, EipcMethodSpec>;
-    /** `$store$` reactive states owned by this service (CC codegen form; see eipcStoreChannel). */
     stores?: Record<string, EipcStoreSpec>;
 }
-/** Neutral session record (CC's `session` position is schema-gated by `aM`; ours is this shape). */
 export interface LocalSessionRecord {
-    /** Host-minted stable session id — the id every event carries (CC form: sessionId on every event). */
     sessionId: string;
-    /** Engine (service)-minted session id, known after the first reply; absent before it. */
     engineSessionId?: string;
-    /** 这条会话钉住的模型 id。缺席 = 宿主没为它钉模型 ⇒ 每轮走部署默认(`SeatModelCatalog.defaultId`);
-     *  消费端渲那个默认名,**不要**渲空串或「未知模型」(部署默认是一个真实存在的答案)。 */
     model?: string;
-    /** 会话标题。缺席 = 还没有标题(首轮之前 / 摘要未回)⇒ 消费端渲「新会话」占位,不要渲空行。 */
     title?: string;
     isRunning: boolean;
-    /** ISO-8601 串(host clock)。与 `ToolPermissionRequest.createdAtMs` **不同域**:那一位是 epoch 毫秒数
-     *  (REF-CC-067 给它加了单位后缀,免得渲染端写出跨两种行复用的 `formatCreatedAt`)。 */
     createdAt: string;
-    /** 最近一次活动时刻(ISO-8601)。缺席 = 自建起没有任何活动 ⇒ 列表按 `createdAt` 排序,
-     *  **不要**把缺席当成 0 时刻(那会把新会话排到列表最底)。 */
     lastActivityAt?: string;
-    /** Host-side deferred queue (CC `deferredSends` seat, in submit order — drives the queued-message
-     *  bar). Present (possibly empty) whenever the host projects the record during a running turn. */
     queuedMessages?: Array<{
         uuid: string;
         text: string;
     }>;
-    /** [C111] B1(clay 裁「加」,2026-08-08):**快照提示位** —— `true` = 写入方(session-host)当时
-     *  确知该会话停在人门上(enterPark/reparkIfStillPending 盖戳,settleTurn 清);缺席 = **未知**
-     *  (旧账本/旧端写的记录),**不是** `false` 的断言。消费端(recents/会话列表)只在 `true` 渲
-     *  「等审批」徽标,缺席/false 不渲 —— 绝不把未知渲成安全。重启恢复端必须先按引擎 approvals
-     *  registry 对账再回写:盘上的 `parked` 是过去的声明,不直接当现势渲。 */
     parked?: boolean;
 }
-/**
- * `ToolPermissionRequest.requestId` 的**域词表**(FIX⑥,2026-08-07)—— 三端唯一真源。
- *
- * 🔴 前缀不是装饰:它**就是**决断的路由依据(session-host 按它挑 wire 动词)。一个域外的 requestId
- * 意味着「这条决断无处可去」,所以校验器对它 fail-loud 而不是放行(此前门只校「是不是串」,
- * 于是 desktop 早就在用的 `plan:` 既不在枚举里、也不会被任何一处说出来)。
- */
 export declare const TOOL_PERMISSION_REQUEST_ID_DOMAINS: readonly ["live:", "durable:", "question:", "elicit:", "plan:"];
 export type ToolPermissionRequestIdDomain = (typeof TOOL_PERMISSION_REQUEST_ID_DOMAINS)[number];
-/** 读口:requestId → 它的域。未登记前缀 / 非串 ⇒ `undefined`(诚实缺席,绝不猜一个域)。 */
 export declare function toolPermissionRequestIdDomain(requestId: unknown): ToolPermissionRequestIdDomain | undefined;
-/**
- * **正向铸口**:域 + 域内 id → `ToolPermissionRequest.requestId`(P-26,2026-08-12)。
- *
- * 沿革:此前本文件只有域表与读口 {@link toolPermissionRequestIdDomain},**没有铸口** —— 于是每个
- * 铸方(session-host 的五条 park 臂、各端的合成行)各自手抄 `` `live:${id}` `` 这样的模板串。手抄
- * 模板串的失效形不是编译红,是**运行期路由到一个不存在的目标**:少个冒号 / 抄错域 / id 是
- * `undefined` 时静默铸出 `"live:undefined"`,而读口对这三种坏键里的后两种照样「认得出域」,所以
- * 谁都不会响。铸口在场之后,这一类错在**铸的那一行**就被拒。
- *
- * 🔴 **往返性**(本口的契约,门里有断言):对任何登记域 `d` 与合法 id,
- *    `toolPermissionRequestIdDomain(toolPermissionRequestId(d, id)) === d` 恒成立 ——
- *    铸出来的键必被读口认回**同一个**域,`isToolPermissionRequest` / `LOCAL_SESSIONS_SPEC` 的
- *    域校验也必然放行(三处读的是同一张 {@link TOOL_PERMISSION_REQUEST_ID_DOMAINS})。
- *
- * 🔴 **坏入参一律 throw,绝不静默吐坏键**:铸口的整个价值就在于「坏键铸不出来」,返回
- * `undefined` 只会把 `${undefined}` 推到下一行的模板串里(与 `honest-absence` 同族的取舍:
- * 缺席要说出来,而这里连「缺席」都不该发生 —— 调用方手上没有合法 id 就不该走到铸这一步)。
- * 三条拒绝各自对应一个真实误用:
- *   ① 域不在词表(含忘了尾冒号的 `"live"`)—— 域外键 = 这条决断无处可去,与读口/校验器同判据;
- *   ② id 非串 / 空串 —— `"live:"` 是半截键,读口却照样认出 `live:` 域,故必须在铸时拦;
- *   ③ id **本身**已经带着某个登记域前缀 —— 典型误用 = 把一条铸好的 requestId 当 id 再喂进来,
- *      得到 `"live:live:ap-1"`(往返性仍成立、校验器仍放行,只有决断落地时才发现目标不存在)。
- *      ⚠️ 这条不拦「id 里含冒号」:`durable:<engineSessionId>:<callId>` 的 id 段天生带冒号。
- *
- * 错误文本只带**域**与判据,不回显 id 原文(id 段可能含 session/call 标识,错误路径也是外溢面)。
- */
 export declare function toolPermissionRequestId(domain: ToolPermissionRequestIdDomain, id: string): string;
-/** design/80 D-1 的 TOCTOU 绑定**对**(REF-CC-070:此前是两个互不相干的 optional,半个 pair 照样过门)。
- *  一位承载整对 ⇒「只有 callId 没有 inputHash」在类型层不可表达,门里也不用再补联合判据。 */
 export interface ToctouBinding {
     callId: string;
     inputHash: string;
 }
 export declare const TOCTOU_BINDING_KEYS: readonly ["callId", "inputHash"];
-/** HITL request row (CC's `request` position is schema-gated by `S1`; ours is this shape, projected
- *  from the sema wire's PendingCheckpoint — see session-host). */
 export interface ToolPermissionRequest {
-    /** Stable request key — echo back on respondToToolPermission. FIVE id domains, prefix-tagged
-     *  (the prefix is what routes the decision back to the right wire verb — see session-host);
-     *  词表真源 = {@link TOOL_PERMISSION_REQUEST_ID_DOMAINS},读口 = {@link toolPermissionRequestIdDomain}:
-     *   `live:<approvalId>`               = LIVE in-band tool-approval face (frame rides the token
-     *                                       stream; unanswered → engine fail-CLOSED deny at its TTL);
-     *   `durable:<engineSessionId>:<callId>` = the durable checkpoint class (approvals inbox);
-     *   `question:<questionId>`           = LIVE `AskUserQuestion` (the agent's own structured ask;
-     *                                       unanswered → engine fail-OPEN: the model takes the
-     *                                       headless default `{answers:[]}` at the 5-min TTL, which is
-     *                                       why leaving this family unrendered is silent, [1947] 红④);
-     *   `elicit:<elicitationId>`          = LIVE inbound-MCP elicitation (a server asks the user for
-     *                                       form input mid-tool-call);
-     *   `plan:<checkpointId>`             = plan-review park(FIX⑥ 2026-08-07 补登记)—— 决断路由到
-     *                                       `assistant.planReview`,**不是** `/decide`(server 对走错
-     *                                       门的调用回 409 `gate_not_plan_review`)。desktop 的
-     *                                       session-host 早已在铸这个前缀,而本枚举只写了四域:
-     *                                       域表说四个、现实跑五个,靠「域外的行长什么样」做判断的
-     *                                       消费端于是各猜各的。
-     *  The LIVE domains are same-replica + non-durable: a late/duplicate decision 404s, which the
-     *  host treats as "already released" (dismiss), never as a retryable error. */
     requestId: string;
     sessionId: string;
-    /** For the two ask families this is the CC tool vocabulary name the renderer branches on:
-     *  `AskUserQuestion` (question domain) / `McpElicitation` (elicit domain).
-     *  缺席或 `null` = wire 没给工具名(旧 server / 通用审批行)⇒ 消费端走**通用**审批卡,
-     *  绝不猜工具名(猜错就是把 Bash 的确认框渲成别的工具的)。 */
     toolName?: string | null;
-    /** The ENGINE's tool-call id (`call_…`) — the SAME id the assistant message's `tool_use` block
-     *  carries, so a renderer can key the approval onto the tool card that actually raised it.
-     *  Present on tool-approval rows from server ≥1.307; `null` when the wire did not offer one
-     *  (old server, or the ask families, which have no tool call of their own). NEVER synthesized. */
     toolCallId?: string | null;
-    /** UNTRUSTED, service-redacted tool args / question payload (render-only, never re-fed).
-     *  🔴 缺席语义(REF-CC-066):门**刻意不校验**这一位(见 SEAT_VALIDATOR_KEY_COVERAGE 的豁免登记),
-     *  所以消费端拿到的可能是 undefined、也可能是任意形状。`question:` 域的整张卡押在 `input.questions`
-     *  上 ⇒ 缺席/畸形时渲染端必须显式渲「问题内容不可用」并把决断按钮留给 deny 侧,
-     *  **绝不**渲一张空卡(空卡看起来像「没有问题要问」,而真相是「问题丢了」)。 */
     input?: unknown;
-    /** UNTRUSTED, service-redacted engine ask text (live face only) — display only.
-     *  缺席 = 这一族(durable 行)本来就没有引擎问句 ⇒ 渲染端用工具名 + 参数摘要成句,不要留空。 */
     message?: string;
-    /** design/80 D-1 TOCTOU binding pair (durable face only) — echo VERBATIM into the decision.
-     *  🔴 出站**只读**位:回程的 verbatim 回显由宿主自己的登记表做(session-host 的
-     *  `row.boundCallId/boundInputHash`),`ToolPermissionDecision` 因此没有对应席位 —— 渲染端
-     *  拿到它只为展示,绝不需要(也不该)自己回传。
-     *  缺席 = 这一行不是 durable 域(live/question/elicit 三域没有绑定对)⇒ 消费端不渲绑定摘要。 */
     toctouBinding?: ToctouBinding;
-    /** 行的诞生时刻,**epoch 毫秒**(单位入名,A4;时钟来源 = 宿主本地 `Date.now()`,不是引擎时钟 ⇒
-     *  与转录里的引擎时间戳不可直接相减)。缺席 = wire 那一行没带时间(旧 server 的 durable 行)⇒
-     *  消费端渲「刚刚」或不渲时间,**绝不**回落成 0(那会渲成 1970)。 */
     createdAtMs?: number;
-    /** 治理强制位([C130] 补键,2026-08-08;server ≥7.5.0,语义原样来自
-     *  `ApprovalCardRequest.governanceForced`):此门来自部署治理层,「permission-mode overrides
-     *  do not apply」。🔴 缺席 ≠ `false`:键**只在为真时在场**,缺席 = 无治理来源证据(真的非治理
-     *  ask 与 server 判据够不着的形共用缺席)⇒ 渲染端绝不渲「可用表态绕开」,也绝不合成治理徽标。
-     *  唯一合法供给 = 宿主(session-host)从已过 hitl wire 门的 `ApprovalCardRequest` **透传**,
-     *  绝不自铸;为 `false` 的值不该出现在座位面上(条件 stamp 纪律与 wire 门同款)。 */
     governanceForced?: true;
-    /** 委派出处链([C130] 补键;core 5.9.0 W1,原样来自 `ApprovalCardRequest.delegation`,形 =
-     *  hitl 的命名类型,单一真源)。只读展示增强——卡说清这只 ask 从哪一层子代浮上来;`agentName`
-     *  UNTRUSTED-for-display(纯文本渲染,零注入面)。缺席 = 非子代 ask 或 wire 没给 ⇒ 不渲委派行。
-     *  坏形处置与 hitl wire 门同款纪律:**读坏形降缺席**,绝不因展示键拒掉整条审批行。 */
     delegation?: ToolApprovalDelegation;
 }
-/**
- * 座位事件名的**闭集**(REF-CC-065):这是三端唯一的事件名真源。
- *
- * 方向判据(本文件 `PERMISSION_MODE_INTENTS` 头注立的那条):词由**我们自己的宿主**铸出、发往渲染端,
- * 因此闭集 —— 拼错一个字母在编译期红,而不是变成一条谁也不认识、被 switch 默默丢掉的事件。
- * 与 `outcome`(wire 铸词,开集)的区别正是「谁铸的词」,不是「字段像不像枚举」。
- * 词表 = sema-desktop `session-host` 的 emit 面实测八词。
- */
 declare const SEAT_EVENT_TYPE_TUPLE: readonly ["start", "close", "session_updated", "message", "stream_event", "chrome_event", "error", "tool_permission_resolved"];
 export type SeatEventType = (typeof SEAT_EVENT_TYPE_TUPLE)[number];
 export declare const SEAT_EVENT_TYPES: readonly SeatEventType[];
-/** Chrome arms wired to the renderer position (batch 4); other arms stay host-side on the ring. */
 declare const CHROME_EVENT_KIND_TUPLE: readonly ["panel_task", "notification_terminal", "prompt_suggestions", "subagent_lifecycle"];
 export type ChromeEventKind = (typeof CHROME_EVENT_KIND_TUPLE)[number];
-/**
- * 🔴 BREAKING(REF-CC-065,2026-08-02):公开面类型从 `readonly string[]` **收窄**成
- * `readonly ChromeEventKind[]`。与 `PERMISSION_MODE_INTENTS` / `SEAT_REASONING_EFFORTS` 那两条
- * **不同**:那两个本来就已经是闭集类型,加元组只是补「类型→常量」那半边、公开面一个字没变;
- * 这一个的公开面**真的变了**,所以它是本批第四处破坏性契约变更,不是「同上理由」的搭车项。
- *
- * 谁受影响(实测消费坐标,提货单同条):`sema-desktop/src/main/session-host.ts:1752`
- * `CHROME_EVENT_KINDS.includes(event.kind)` —— 那里的 `event: ChromeEvent` 是 seam.ts 的 17 词
- * 判别式联合,收窄后 `includes()` 的入参类型只认这 4 个词 ⇒ TS2345,提货当天编译红。
- * 迁移形:`(CHROME_EVENT_KINDS as readonly string[]).includes(event.kind)`,或先按 `ChromeEventKind`
- * 做一次显式收窄再进这一支。sema-web-client / sema-cli 实测零命中。
- */
 export declare const CHROME_EVENT_KINDS: readonly ChromeEventKind[];
-/** chrome 信封的**必填**键(REF-CC-064:`laneProof` 此前类型可选、门必填,两边说的不是一句话)。 */
 export interface SeatChromeEnvelopeBase {
     kind: ChromeEventKind;
-    /** 车道证明([1617] 家族一等公民)。**必填**:出站门本来就要求它在场,类型说可选 = 一个合规的
-     *  生产者编译全绿、事件被整条静默丢弃。缺席在这条 lane 上不是「降级」,是「这帧不该发出来」。 */
     laneProof: LaneProof;
 }
-/** 臂自身的载荷键随 `kind` 变(client-core `ChromeEvent` 的判别式联合),故留 index 位;
- *  必填两位由 `SeatChromeEnvelopeBase` 承载,键集钉也钉在它上面。 */
 export interface SeatChromeEnvelope extends SeatChromeEnvelopeBase {
     [k: string]: unknown;
 }
 export declare const SEAT_CHROME_ENVELOPE_KEYS: readonly ["kind", "laneProof"];
 export interface LocalSessionEvent {
-    /** 事件名(闭集 `SEAT_EVENT_TYPES`)—— 消费端的判别位,switch 可穷举。 */
     type: SeatEventType;
     sessionId: string;
-    /** 🔴 transcript-plane passthrough (SDKMessage body) — deliberately UNVALIDATED (fQe posture). */
     message?: unknown;
-    /** 🔴 transcript-plane passthrough batch — array-checked only, elements unvalidated (fQe posture). */
     messages?: unknown[];
-    /** 人可读的失败说明(仅 `error` 事件)。缺席 = 这条事件不是失败事件 ⇒ 渲染端不要因为「没有 error」
-     *  就把一次真失败渲成成功;判失败看的是 `type === "error"`,不是这一位在不在。 */
     error?: string;
-    /** 失败的**类别**(宿主自铸:`turn_failed` / `plan_review_failed` …)。缺席 = 宿主没有给这次失败分类
-     *  ⇒ 渲染端只渲 `error` 文本,不要猜类别、也不要按文案分类(§B8)。 */
     errorCategory?: string;
-    /** 引擎/传输层状态码(有则透传)。缺席 = 这次失败没有码可报(本地异常)⇒ 不渲码位,**绝不**渲 0。 */
     code?: number;
-    /** CC `fQe` 的 form 位。🔴 **本宿主从不发这个位**(session-host 零处写 `request:`;HITL 行走
-     *  独立的 `onToolPermissionRequest` 通道)—— 位保留是为了与 CC 的 fQe 逐位同形,消费端不该
-     *  为它写分支(见文件头 D4)。 */
     request?: ToolPermissionRequest;
-    /** 自由文本载荷(CC fQe 的 `data` 位,本宿主目前不发)。缺席 = 没有附带文本,消费端不渲这一行。 */
     data?: string;
-    /** 引用来源列表(CC fQe 的 `sources` 位,本宿主目前不发)。缺席 = 没有来源可标 ⇒ 不渲来源脚注;
-     *  空数组与缺席同义(都表示「没有来源」),渲染端不必区分。 */
     sources?: string[];
-    /** 本轮生效的权限模式回显(闭集,与入站 `SendMessageRequest.permissionMode` 同一套词)。
-     *  缺席 = 宿主没有回显模式(今日常态:session-host 零处发这一位)⇒ 渲染端继续显示 composer 自己的
-     *  模式徽标,**不要**因为缺席就把徽标降回 `default`(那是把「没说」渲成「说了 default」)。
-     *  🔴 闭集的前提是「词由我们自己铸」:哪天改成回显**引擎的** effective mode(wire 铸的词),
-     *  必须同批把这一位降级成开集,理由与 `outcome` 逐字相同。 */
     permissionMode?: PermissionModeIntent;
-    /** 会话行快照(`start`/`close`/`session_updated` 带)。缺席 = 这条事件不携带会话态 ⇒ 消费端
-     *  沿用 store 里的现有行,**不要**当成「会话没了」。 */
     session?: LocalSessionRecord;
-    /** 触发这条事件的用户消息 uuid(`message` 事件带)。缺席 = 这条事件不属于某条用户消息(引擎侧自发)
-     *  ⇒ 渲染端把它挂在当前 turn 上,不要另开一条用户气泡。 */
     userMessageUuid?: string;
-    /** CC form:本条 `message` 之前宿主已清过屏(`/clear` 语义)。缺席 ≡ false(没清过)——
-     *  这一位只在为真时出现,消费端按「缺席 = 不清屏」处理即可。 */
     hasPreClearSession?: boolean;
-    /** On `tool_permission_resolved`: which request settled (so a native notification for it can be
-     *  dismissed — CC `closePermissionNotification(requestId)`). 缺席 = 这条不是审批收面事件。 */
     requestId?: string;
-    /**
-     * On `tool_permission_resolved`: HOW it settled ([1947] 红③). Without this the renderer only ever
-     * learned that a card should disappear — a TTL expiry, a disconnect-settle and a human's own
-     * "allow" were indistinguishable, so a REFUSAL rendered as a card silently vanishing and the user
-     * was never told why the tool did not run.
-     *
-     * Words currently emitted (see HITL_RESOLUTION_OUTCOMES): the tool-approval wire's own
-     * `allowed`/`denied`/`expired`, the question wire's `answered`/`unanswered`, the elicitation
-     * wire's `accept`/`decline`/`cancel`. ABSENT is meaningful and honest: the durable inbox sweep
-     * learns only that a row is gone, never why.
-     *
-     * 🔴 Validated as a plain string, NOT against a closed set, deliberately: the words originate on
-     * the wire, and a fail-closed gate keyed to today's vocabulary would DROP THE WHOLE EVENT (card
-     * stuck on screen forever) the day the server adds an outcome word. Renderers branch on the words
-     * they know and treat an unknown one as "settled, reason unknown".
-     */
     outcome?: string;
-    /** On `chrome_event`: one client-core ChromeEvent arm (the NEUTRAL typed chrome vocabulary —
-     *  [1832] axiom 2's non-transcript half). Only the renderer-wired arm kinds cross the wire
-     *  (see CHROME_EVENT_KINDS); the outbound gate checks kind membership + the laneProof discipline.
-     *  缺席 = 这条不是 chrome 事件(按 `type` 判别,不要按这一位在不在判别)。 */
     chrome?: SeatChromeEnvelope;
 }
-/**
- * The resolution words the host currently puts on `tool_permission_resolved.outcome` ([1947] 红③).
- * DOCUMENTARY + test anchor only — the gate does NOT enforce membership (see the field's doc: a
- * closed set would fail-close the whole event on the day the wire grows a word). Grouped by family:
- *  - tool approval (wire `ToolApprovalFrame.outcome`, + our own settle sweep): allowed/denied/expired
- *  - question      (wire `QuestionFrame.outcome`):                             answered/unanswered
- *  - elicitation   (wire `ElicitationFrame.action`):                           accept/decline/cancel
- */
 export declare const HITL_RESOLUTION_OUTCOMES: readonly string[];
-/**
- * 接缝记账 — what the HOST now guarantees vs what a RENDERER still owes ([1947] 红③/红④ split).
- *
- * The host half is done and pinned by desktop's `scripts/run-hitl-frame-transit-fence-test.mjs`:
- * every live ask family reaches `onToolPermissionRequest` with its own requestId domain, every
- * resolution reaches `onEvent` with an `outcome`, and every decision routes to the right wire verb.
- *
- * The renderer half is where these become VISIBLE, and until it lands the data is present but
- * unread (stating it plainly so nobody reads "the host emits it" as "the user sees it"):
- *  1. `tool_permission_resolved.outcome` — an `expired` / `denied` / `unanswered` resolution must
- *     leave a visible refusal trace. Today the seat transport clears the surface and drops the
- *     word, so a refusal is still indistinguishable from an approval on screen.
- *     🔴 B18(2026-07-29)查明这条一直不销账的**机制原因**:web 侧的镜像类型里连 `outcome` 这个
- *     位都没有,所以「没读」在两边都编译得过。本批把位收进真源 = 让它至少可见于类型面。
- *  2. `toolCallId` — now real (not null), so an approval can be anchored to the tool card that
- *     raised it instead of "the most recent tool_start" (an anchor that lands on the wrong card
- *     when a prior tool is still running).
- *  3. `question:` rows need NO new renderer code: they arrive as `toolName: "AskUserQuestion"` with
- *     `input.questions`, which is exactly what the seat's ask-user-question surface already reads,
- *     and its answer envelope is exactly what this host expects back.
- *  4. 座位 wire 补齐批 (2026-07-28) closed two entries that used to live here as "如实,未做":
- *     `permissionMode` now has a seat on `sendMessage` (was: the composer's Plan badge never
- *     crossed and the turn ran with the engine default), and the attachment BYTE channel exists
- *     (`uploadAttachment` + `sendMessage.attachmentIds`) — so a seat renderer no longer has to
- *     simulate "attachment ready" for a file nothing received. What is still NOT here, stated
- *     plainly: plan REVISE feedback text (the decide face has no `reason` seat, so revise maps to
- *     a bare deny) and a per-session `permissionMode` write (the wire's is per-TURN only).
- *  5. `elicit:` rows have no dedicated surface yet: they fall through to the generic approval card,
- *     which shows the MCP server's prompt and can accept/decline but CANNOT collect form values.
- *     A real form surface (built from `input.requestedSchema`) is the renderer's remaining piece;
- *     until then an approve carries no content — the host never invents form values. That generic
- *     card also offers "Always allow (this session)", which this domain has no concept of: the host
- *     ignores `remember` here rather than pretend, so the renderer should hide that control for
- *     `elicit:` rows (a button that changes nothing is the false-affordance family again).
- */
 export interface StartSessionOptions {
-    /** 起会话时钉的模型 id。缺席 = 用部署默认(`SeatModelCatalog.defaultId`),这是一个真实答案而不是错误。 */
     model?: string;
-    /** 起会话时给的标题。缺席 = 宿主不铸标题(记录里的 `title` 随后也缺席,渲染端渲「新会话」)。 */
     title?: string;
-    /** Working directory for the session's hand tools (TaskRequest.cwd). Default = a per-session dir
-     *  under the host's workspace base. A UI that picks a project directory passes it here — CC desktop
-     *  form (session.cwd / worktreePath). Honored only on the local host-adapter engine. */
     cwd?: string;
-    /** Wire TRUE-UNMOUNT list (TaskRequest.excludeTools, server ≥1.221): named tools' schemas never
-     *  reach the model for ANY turn of this session. Tighten-only. */
     excludeTools?: string[];
 }
-/**
- * PERMISSION MODE INTENT — the RAW mode the composer is showing, carried verbatim to the engine as
- * `TaskRequest.permissionMode` (SDK types.d.ts:259; the SERVICE interprets it, axis-aware and
- * tighten-only: `plan` ⇒ mount `present_plan` + read-only hands = CC EnterPlanMode).
- *
- * 🔴 Why this seat exists at all (红批注 web#1): without it, a user who switched the composer to
- * Plan mode inside the desktop seat got a turn that ran with the engine's DEFAULT mode — the badge
- * said "plan", the engine was never told, and the agent happily edited files. A mode the UI shows
- * but never sends is the false-affordance family with teeth.
- *
- * The vocabulary is the wire's own (identical to the web client's `ComposerMode`), so the seat
- * passes the word through unchanged rather than re-deriving core fields locally — one interpretation
- * across TUI + web + desktop. 🔴 B18 起 web 侧的镜像位也是这个闭集(此前是裸 `string`):
- * ComposerMode 加一档而宿主闭集门不认的那天,红在编译期而不是用户提交那一刻。
- */
 export type PermissionModeIntent = "default" | "plan" | "acceptEdits" | "bypassPermissions" | "auto";
 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;
 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).
-     *  缺席 = 没开这个预设(≡ false);渲染端按缺席渲「关」,不必区分缺席与显式 false。 */
     ultracode?: boolean;
 }
 export declare const SEAT_TURN_SETTINGS_KEYS: readonly ["ultracode"];
 export interface SendMessageRequest {
     sessionId: string;
     text: string;
-    /** 本轮临时换模型。缺席 = 用会话钉住的模型(`LocalSessionRecord.model`),再缺席才是部署默认。 */
     model?: string;
-    /** Client-supplied echo key for the user message (CC form: userMessageUuid); minted if absent. */
     userMessageUuid?: string;
-    /** Composer permission mode for THIS turn → `TaskRequest.permissionMode`. Omit/`default` ⇒ no stamp. */
     permissionMode?: PermissionModeIntent;
-    /** Pre-uploaded attachment handles (`uploadAttachment` receipts) → `TaskRequest.attachmentIds`.
-     *  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;
-    /**
-     * 这一轮把**子代的正文帧**转发到父流上 → `TaskRequest.forwardSubagentEvents`。缺席 = 不开
-     * (父流只有进度帧,没有子代的 text/reasoning/tool 帧)。
-     *
-     * 🔴 **能力位说的是「这个键被接受」,不是「它已经开着」**:引擎的 `capabilities.forwardSubagentEvents`
-     *    是一个恒真的**受理位**,把它读成「转发已生效」的消费方会接出一个**永远空着**的子代转录面,
-     *    而能力面一直在回答「是」。⇒ 想要子代正文,**每一轮都得自己带这个键**。
-     * 🔴 结构性缺席故事与 `reasoningEffort` 同款:闭集载体就是这条 lane 本身,不在集里 = 「这一轮要不要
-     *    看子代正文」这个决定在座位 lane 上**没有位置可放**。座位端此前只能整条放弃子代转录面
-     *    (或绕开闭集从逃生口塞一个没登记的键上 wire —— 那是本包整张契约存在的理由所要消灭的形)。
-     */
     forwardSubagentEvents?: boolean;
-    /**
-     * 这一轮**保留已结束的子代会话**以便日后续跑 → `TaskRequest.retainSubagentSessions`。
-     * `true` = 按引擎默认保留;对象形调保留**窗口**(`ttlMs`)与**条数**(`max`)。缺席 = 不保留。
-     *
-     * 🔴 **过大的请求会被引擎悄悄收紧、而不是拒绝**(server 侧 clamp:窗口上限 24 小时、条数上限 64)。
-     *    ⇒ 渲染端**不许**把自己请求的值当成生效值回显 —— 那是替引擎说了一句它没说的话;要显示生效值
-     *    就去读引擎那一面,读不到就诚实留白。
-     * 🔴 它是「子代续跑」那条路的**另一半**:续跑能力位可以是真、路由可以在,调用照样会被拒 ——
-     *    因为保留是**逐 run**的、且默认关。只看能力位就渲一个「继续这个子代」的入口 = 假 affordance。
-     * 🔴 结构性缺席故事同上:此前座位 lane 没有这一位,于是「这条会话要不要留子代」只能由部署默认决定,
-     *    而那与「端替用户做了这个决定」不是一回事。
-     */
     retainSubagentSessions?: boolean | {
         ttlMs?: number;
         max?: number;
     };
-    /** Per-turn settings sub-object → `TaskRequest.settings`. Closed shape (`SeatTurnSettings`);
-     *  today's only member is the `ultracode` preset boolean. */
     settings?: SeatTurnSettings;
-    /** 本轮 scenario 拨盘选择([C131] 补载体,2026-08-08)→ `TaskRequest.scenario`。**开集**(SDK
-     *  `Scenario = KnownScenario | (string & {})` 同姿态——部署可注册自有场景,座位面不替它闭集)。
-     *  缺席 = 不 stamp,由部署解析默认场景(assignment 链)。错误面是响亮的 typed 400:名字不在
-     *  部署词表 ⇒ `scenario_unknown`(body 带 live 词表 `known`);在词表但不在本 principal
-     *  allowlist ⇒ `scenario_not_allowed`(带 allowlist)——渲染端可据此渲有效选项,不猜不折叠。
-     *  此前的结构性缺席与 `reasoningEffort` 同款:闭集载体就是 lane 本身,不在集里 = 拨盘的选择
-     *  在座位 lane 上没有位置可放(web [C131]① 记账的九键无载体形)。 */
     scenario?: string;
 }
-/** `uploadAttachment` 入参(REF-CC-074:此前是导出方法签名里的 3 成员内联匿名形,直接命中 B4)。 */
 export interface AttachmentUploadRequest {
-    /** 本地文件名。服务端会自己 sanitize 出 `AttachmentUploadReceipt.name`,渲染端显示的是**回执**那个。 */
     name: string;
-    /** MIME 类型。缺席 = 让服务端自己嗅探(它有权拒 415);消费端不要自己编一个 `application/octet-stream`
-     *  —— 编出来的类型会让服务端把本可识别的文件当二进制。 */
     mimeType?: string;
     bytes: Uint8Array;
 }
 export declare const ATTACHMENT_UPLOAD_REQUEST_KEYS: readonly ["name", "mimeType", "bytes"];
-/** 只带会话 id 的入参(interrupt/stop 共用;REF-CC-074 同族,1 成员形也统一成具名)。 */
 export interface SessionScopedRequest {
     sessionId: string;
 }
-/** `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
- *  materializes, so the renderer must display THAT one. */
 export interface AttachmentUploadReceipt {
     id: string;
     name: string;
@@ -576,64 +137,30 @@ export interface AttachmentUploadReceipt {
     sha256: string;
     sizeBytes: number;
 }
-/** One row of the seat's model catalog (`GET /v1/models`, non-secret projection: the service already
- *  strips baseUrl/apiKey/headers). `contextWindow`/`maxOutputTokens` are soft-degrade extras. */
 export interface SeatModelInfo {
     id: string;
-    /** 展示名。缺席 = 部署没给展示名 ⇒ 渲染端显示 `id` 本身(不要显示空串)。 */
     name?: string;
-    /** 供应商名。缺席 = 部署没标供应商 ⇒ 不渲供应商标签,**不要**回落成 "unknown"。 */
     provider?: string;
-    /** 上下文窗口 token 数(statusline 的 Context 环分母)。缺席 = 引擎没报这个量 ⇒ 环渲不确定态,
-     *  绝不按某个猜测值算百分比([honest-absence-not-fabricated-zero])。 */
     contextWindow?: number;
-    /** 单次回复上限 token 数。缺席 = 引擎没报 ⇒ 不渲这一行。 */
     maxOutputTokens?: number;
 }
-/** `listModels` envelope. `defaultId` = the deployment's resolved default model id (display only —
- *  the per-turn choice always rides `sendMessage({model})`). */
 export interface SeatModelCatalog {
     models: SeatModelInfo[];
-    /** 缺席 = 部署没有解析出默认模型 ⇒ 渲染端不要给「默认」打勾,也不要自己挑第一行冒充默认。 */
     defaultId?: string;
 }
 export interface SendMessageAck {
     sessionId: string;
     userMessageUuid: string;
-    /** true = a turn was running, the message entered the deferred queue (CC sendMessage semantics)
-     *  instead of starting a turn; absent/false = the turn started immediately. */
     queued?: boolean;
 }
-/**
- * One decision, four wire verbs — the requestId's domain picks which (session-host routes it):
- *  `live:`     → POST /v1/tool-approvals/:id/respond   (allow | allow_session | deny)
- *  `durable:`  → POST /v1/approvals/:sessionId/decide  (+ the TOCTOU binding pair, echoed verbatim)
- *  `question:` → POST /v1/questions/:id/respond        (approve ⇒ `answer`; deny ⇒ `{answers:[]}`,
- *                the wire's own NO_HUMAN — releases the ask NOW instead of hanging it to its TTL)
- *  `elicit:`   → POST /v1/elicitations/:id/respond     (approve ⇒ accept + `updatedInput` as the
- *                form content; deny ⇒ decline)
- */
 export interface ToolPermissionDecision {
     sessionId: string;
     requestId: string;
     decision: "approve" | "deny";
-    /** AskUserQuestion answer (approve only) — `{answers:[{header, selected: string[], note?}]}`,
-     *  keyed by the question's HEADER, `selected` echoing the EXACT option labels the user saw (core
-     *  fences `selected ⊆ options`). Malformed shapes are refused at the door, never coerced: a
-     *  silently emptied answer is the user's choice being thrown away without anyone noticing.
-     *  REF-CC-038(2026-08-02):typed as `QuestionAnswer`(hitlBridge's `AskAnswer` at the entry
-     *  level) — this was `unknown` before, the 4th of 4 divergent copies of the same shape.
-     *  缺席 = 这不是 question 域的决断(或是 deny)⇒ 宿主发 wire 自己的 NO_HUMAN 形(REF-CC-066)。 */
     answer?: QuestionAnswer;
-    /** Approve-with-edit rewritten args (design/37 last-wins). On the `elicit:` domain this position
-     *  carries the submitted FORM CONTENT — a flat record of `string|number|boolean|string[]`
-     *  (the only shape the wire accepts; anything else is refused, not filtered).
-     *  缺席 = 原样批准(不改参数);`elicit:` 域缺席 = 没有表单内容,宿主绝不代填。 */
     updatedInput?: unknown;
-    /** "Don't ask again this session" (approve only). 缺席 = 只批这一次。 */
     remember?: "session";
 }
-/** Renderer-side `$store$` client (CC form: read + subscribe; `update` channel is the push). */
 export interface EipcStoreClient<T> {
     getState(): Promise<T>;
     getStateSync(): T;
@@ -641,87 +168,58 @@ export interface EipcStoreClient<T> {
 }
 export interface SettingsState {
     defaultModel: string | null;
-    /** 引擎版本串。缺席 = 宿主还没连上引擎(启动窗口)⇒ 渲染端渲「连接中」,不要渲空版本号。 */
     engineVersion?: string;
-    /** 引擎数据根目录。缺席 = 同上(还不知道)⇒ 不渲路径行,不要渲 "~" 之类的猜测值。 */
     dataRoot?: string;
 }
 export interface SessionSearchResult {
     sessionId: string;
-    /** 命中会话的标题。缺席 = 该会话没有标题 ⇒ 结果行渲「新会话」+ 片段,不要渲空标题行。 */
     title?: string;
     matches: Array<{
         snippet: string;
     }>;
 }
 export declare const SESSION_SEARCH_RESULT_KEYS: readonly ["sessionId", "title", "matches"];
-/** `searchSessions` 返回形(REF-CC-072:此前是 SPEC 里的内联匿名 validator 之一;
- *  它从不校 `title` 那一半归 REF-CC-073,见 `SESSION_SEARCH_RESULT_KEYS`)。 */
 export interface SessionSearchEnvelope {
     results: SessionSearchResult[];
 }
-/** `getTranscript` 返回形(REF-CC-073:此前内联匿名、无 interface、无键集、无钉)。
- *  `messages` = transcript 面直通批(fQe 姿态:只校数组形,元素是 CC SDKMessage 体,刻意不校)。 */
 export interface GetTranscriptResult {
     sessionId: string;
     messages: unknown[];
 }
 export declare const GET_TRANSCRIPT_RESULT_KEYS: readonly ["sessionId", "messages"];
-/** interrupt 回执(CC form:true = 真打断了一轮在跑的 turn,false = 当时没有在跑的 turn)。 */
 export interface InterruptAck {
     interrupted: boolean;
 }
-/** stop 回执(false = 会话本来就不在跑,不是错误)。 */
 export interface StopAck {
     stopped: boolean;
 }
-/** 通用「收到了」回执(respondToToolPermission / setFocusedSession)。 */
 export interface OkAck {
     ok: boolean;
 }
-/** `sessionsState` store 的状态形。 */
 export interface SessionsState {
     sessions: LocalSessionRecord[];
 }
-/** `focusedSessionState` store 的状态形(`null` = 没有会话被聚焦,是一个真实状态不是缺席)。 */
 export interface FocusedSessionState {
     sessionId: string | null;
 }
-/** Renderer-facing surface exposed by the mainView preload as `sema.web.LocalSessions`. */
 export interface LocalSessionsApi {
     start(opts?: StartSessionOptions): Promise<LocalSessionRecord>;
     sendMessage(req: SendMessageRequest): Promise<SendMessageAck>;
     interrupt(req: SessionScopedRequest): Promise<InterruptAck>;
     stop(req: SessionScopedRequest): Promise<StopAck>;
     respondToToolPermission(req: ToolPermissionDecision): Promise<OkAck>;
-    /** Queue family (CC LocalSessionManager semantics; booleans, false = too-late/no-op form). */
     cancelQueuedMessage(sessionId: string, userMessageUuid: string): Promise<boolean>;
-    /** CC signature: (sessionId, uuid, TARGET uuid) — position the message relative to the target
-     *  (after it when moving down, before it when moving up); NOT an index. */
     reorderQueuedMessage(sessionId: string, userMessageUuid: string, targetUserMessageUuid: string): Promise<boolean>;
     promoteQueuedMessage(sessionId: string, userMessageUuid: string): Promise<boolean>;
-    /** CC census verbs (batch 4). setFocusedSession(null) clears focus. */
     setFocusedSession(sessionId: string | null): Promise<OkAck>;
     setModel(sessionId: string, model: string): Promise<boolean>;
     getTranscript(sessionId: string): Promise<GetTranscriptResult>;
     searchSessions(query: string): Promise<SessionSearchEnvelope>;
-    /** Attachment BYTE channel (红批注 web#1 的另一半). Upload first, then reference the receipt id
-     *  from `sendMessage({attachmentIds})`. Rejects (413/415/501 → thrown typed error) surface to the
-     *  renderer as-is: a shelf row that says "ready" for a file the engine never received is the
-     *  same lie as a mode badge that never crossed the wire. */
     uploadAttachment(req: AttachmentUploadRequest): Promise<AttachmentUploadReceipt>;
-    /** Read-only model catalog (engine `GET /v1/models`). Empty `models` = the deployment offers no
-     *  catalog; the renderer must degrade honestly rather than fall back to a fixture list. */
     listModels(): Promise<SeatModelCatalog>;
-    /** [C115]/[C117] 模型配置写 verb:把选定的 catalog 条目落成宿主配置(settings.json env 块)。
-     *  写盘语义归宿主实现(desktop main 复用 cli buildModelEnv 键映射+updateSettingsForSource 锁形+
-     *  RETIRED_MODEL_ENV_TOMBSTONES 墓碑);契约只定形与诚实位。🔴 req.apiKey 是敏感位:validator
-     *  校形不校值,任何 throw/log/ack 绝不回显 req(错误消息只说哪个键缺/形错,不带值);
-     *  requiresRestart 必须如实渲(改完不重启=假 affordance)。 */
     applyModelConfig(req: ApplyModelConfigRequest): Promise<ApplyModelConfigResult>;
     onEvent(cb: (ev: LocalSessionEvent) => void): () => void;
     onToolPermissionRequest(cb: (req: ToolPermissionRequest) => void): () => void;
-    /** `$store$` reactive states (read + subscribe; writes go through the verbs above). */
     sessionsStateStore: EipcStoreClient<SessionsState>;
     focusedSessionStateStore: EipcStoreClient<FocusedSessionState>;
     settingsStateStore: EipcStoreClient<SettingsState>;
@@ -730,8 +228,6 @@ export declare function isLocalSessionRecord(s: unknown): s is LocalSessionRecor
 export declare function isToolPermissionRequest(r: unknown): r is ToolPermissionRequest;
 export declare function isLocalSessionEvent(v: unknown): v is LocalSessionEvent;
 export declare function isAttachmentUploadReceipt(v: unknown): v is AttachmentUploadReceipt;
-/** 与 cli applyOnboard.CatalogEntry 逐键同形(真源对齐:cli 侧以 satisfies 断言钉住两形不漂——
- *  包不反向依赖壳,故此处独立铸型)。api 闭集;apiKey 敏感位(校形不校值,零回显)。 */
 export interface SeatCatalogEntry {
     providerId: string;
     providerName: string;
@@ -745,46 +241,23 @@ export interface SeatCatalogEntry {
 }
 export interface ApplyModelConfigRequest {
     defaultModel: SeatCatalogEntry;
-    /** 缺席 = 与 default 同(宿主不写 MODEL_CHEAP_ID)。 */
     cheapModel?: SeatCatalogEntry;
 }
 export interface ApplyModelConfigResult {
     ok: boolean;
-    /** ok:false 时必在(GUI 要能渲原因);同样零敏感值回显。 */
     reason?: string;
-    /** 必须如实渲(改完不重启=假 affordance,[C115] 预登记)。 */
     requiresRestart: boolean;
 }
 export declare function isSeatModelCatalog(v: unknown): v is SeatModelCatalog;
 export declare function isSendMessageAck(v: unknown): v is SendMessageAck;
 export declare const LOCAL_SESSIONS_SPEC: EipcServiceSpec;
-/** verb 名清单 = `LOCAL_SESSIONS_SPEC.methods` 应有的键集(逐元素相等,门里断言)。 */
 export declare const SEAT_METHOD_NAMES: readonly ["start", "sendMessage", "interrupt", "stop", "respondToToolPermission", "cancelQueuedMessage", "reorderQueuedMessage", "promoteQueuedMessage", "setFocusedSession", "setModel", "getTranscript", "searchSessions", "uploadAttachment", "listModels", "applyModelConfig", "onEvent", "onToolPermissionRequest"];
-/** `$store$` 属性名清单;SPEC 的 store 键 + `"Store"` 必须逐条等于这里的名字(门里断言)。 */
 export declare const SEAT_STORE_PROPS: readonly ["sessionsStateStore", "focusedSessionStateStore", "settingsStateStore"];
-/** 事件式(main→renderer push)的 verb —— SPEC 里 `kind: "event"` 的那一撮,门里逐元素对账。 */
 export declare const SEAT_EVENT_METHOD_NAMES: readonly ["onEvent", "onToolPermissionRequest"];
 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", "toctouBinding", "createdAtMs", "governanceForced", "delegation"];
 export declare const LOCAL_SESSION_RECORD_KEYS: readonly ["sessionId", "engineSessionId", "model", "title", "isRunning", "createdAt", "lastActivityAt", "queuedMessages", "parked"];
 export declare const SEND_MESSAGE_REQUEST_KEYS: readonly ["sessionId", "text", "model", "userMessageUuid", "permissionMode", "attachmentIds", "reasoningEffort", "retainBackgroundProcesses", "forwardSubagentEvents", "retainSubagentSessions", "settings", "scenario"];
-/**
- * **座位键 → 引擎请求位**的出身表(0.62.0;`SEND_MESSAGE_REQUEST_KEYS` 的逐键出身登记)。
- *
- * 为什么要有它:座位 lane 的载荷是一个**闭集接口**,而它的绝大多数位最终是要**原样落到引擎请求
- * 体上**的。这两件事此前没有任何东西把它们接起来 —— 一个座位位可以叫一个引擎请求体上**根本不存在**
- * 的名字(端照着它写、上了 wire 被引擎整键忽略,面上是「开关点了没反应」这类静默缺席),而引擎请求
- * 体新长出一个位时,也没有任何信号说「座位 lane 还没有它的席位」。本表把每个座位键的出身写成**数据**:
- *   · `taskRequestKey` —— 这个位**原样转投**引擎请求体的同名/异名位。常驻门拿它对**装在盘上的**
- *     sdk 型面逐名核(型直读,不手抄):名字不在引擎请求体上 ⇒ 当天红。
- *   · `seatOnly` —— 这个位**不上 wire**,只活在座位 lane 上;字符串写清它是什么、为什么不转投。
- *
- * 🔴 `sessionId` 是**同名不同义**的典型:座位这一位是**座位会话句柄**(渲染端持有的本地 id),而引擎
- *    请求体上那个同名位是**引擎会话 id**(座位记录里另有 `engineSessionId` 承载)。两者恰好同名,
- *    把它登记成「转投」会让下一个人以为直接透传就行 —— 那是把本地句柄当引擎会话送上 wire。
- * 🔴 `text` 是**异名转投**:座位说 `text`,引擎请求体那一位叫 `objective`。异名不是问题,**没记账**
- *    才是;本表就是那本账。
- */
 export declare const SEAT_SEND_MESSAGE_KEY_ORIGINS: {
     readonly sessionId: {
         readonly seatOnly: "座位会话句柄(渲染端持有的本地 id);引擎会话 id 由座位记录的 `engineSessionId` 承载 —— 与引擎请求体上的同名位**同名不同义**,绝不直传";
@@ -825,29 +298,6 @@ export declare const SEAT_SEND_MESSAGE_KEY_ORIGINS: {
 };
 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"];
-/**
- * 校验器覆盖表(REF-CC-068)—— 每个校验器**逐键**声明:哪些位真被校验、哪些位**刻意**不校验。
- *
- * 为什么需要它:`防再漂钉` 封的是「interface ↔ 名字常量 ↔ SPEC」两跳,**校验器这条链此前没人钉**。
- * 给一个 interface 加一个必填位,门全绿,而新位从此不过校验(fail-closed 面出现缺口)。
- * 正确做法不是「全键必查」—— 本文件有真正**刻意不查**的位(transcript 面直通),所以豁免必须显式登记
- * 并带理由。门里对每个位投毒:说校验的必拒、说豁免的必过 ⇒ 这张表不可能变成一段过期的说明文字。
- *
- * 🔴 覆盖范围(wave2 回炉批 2026-08-02 补齐,首版只登了 6 个而发包说明写的是「每个校验器」——
- * 那 8 个没登的恰好就是 REF-CC-072 本批新提名的那批 `check*`,实测「加一个必填位、全门照绿」在它们
- * 身上仍然全开,即这张表自称堵死的失效形当时并没有被堵死):
- *   · **SPEC 面 15 个具名 `check`,14 个对象形在本表登记**,余下 1 个(裸布尔回执)逐形豁免;
- *   · 另加 4 个**嵌套**形(SeatModelInfo / SessionSearchResult / ToctouBinding /
- *     SeatChromeEnvelopeBase)—— 它们不是 SPEC 面的直接 check,但父校验器的覆盖表只登记得到
- *     `models` / `results` / `toctouBinding` / `chrome` 这一个顶层键,给**子形**加必填位同样全绿;
- *   · 合计 **18 条**。两个不适用的形逐形写在 `SEAT_VALIDATOR_COVERAGE_EXEMPT` 里。
- * 完备性不靠这段话:门里逐条比对 `LOCAL_SESSIONS_SPEC` 每个 method/store 的 `check` **函数引用**
- * 必须落在「本表 ∪ 豁免表」里 —— 再加一条 verb 而不登记,门当场红。
- *
- * `check` 位存的是**函数引用本身**(不是名字):名字查表要靠一张 guards 映射,而那张映射漏一行
- * 就是又一个没人看见的缺口;引用相等是机械的。`guard` 位只在该形另有公开面 `is*` 谓词时登记,
- * 门里额外校「谓词与 check 判决一致」。
- */
 export declare const SEAT_VALIDATOR_KEY_COVERAGE: {
     readonly LocalSessionRecord: {
         readonly guard: "isLocalSessionRecord";
@@ -963,11 +413,6 @@ export declare const SEAT_VALIDATOR_KEY_COVERAGE: {
         readonly unchecked: readonly [];
     };
 };
-/**
- * 逐形豁免(REF-CC-068 的另一半):**不适用**覆盖表的具名校验器 —— 每条写清为什么,以及它的判别力
- * 由谁承担。这张表存在的唯一理由是让「本表 ∪ 覆盖表 ⊇ SPEC 面全部 check」这条完备性钉能机械成立:
- * 没有它,「某个 check 没登记」和「某个 check 不该登记」在门里长得一模一样。
- */
 export declare const SEAT_VALIDATOR_COVERAGE_EXEMPT: readonly [{
     readonly label: "BooleanAck";
     readonly check: (v: unknown) => SeatValidation;