@sema-agent/client-core 0.19.0 → 0.20.1

package/dist/retryStatus.js

@@ -6,23 +6,87 @@
  *   retrying     → error    → '✻ API error · Retrying in Ns'(非终态;187 硬编码 'API error')
  *   rate_limited → error    → '✻ Usage limit reached · Retrying in Ns'(rateLimits 真 ⇒ 终态)
  *   circuit_open → error    → '✻ <detail|Service temporarily unavailable> · Retrying in Ns'
- * 绝不捏造 attempt 计数——只用引擎真给的 phase/detail/retryInSec。
+ *   recovered    → null     → 覆盖层摘掉(重试**成功**,不是错误 —— 见下)
+ *   gave_up      → error+terminal → '✻ <detail>'(重试用尽的终态;与 recovered 反向。**打 terminal 位**,
+ *                                    渲染面据此不得再接「· Retrying in Ns」——已经没有下一次了)
+ * 绝不捏造 attempt 计数——只用引擎真给的 phase / detail / retryInSec / retryInMs / attempt / maxRetries。
+ *
+ * 🔴 员数与字段补全(2026-08-08,#3004 跟修批)。此前本文件只列 4 相 + 3 字段,而引擎侧
+ * (core `BrainStatusPhase` / `BrainStatus`,dist/core/types.d.ts)是 **6 相 + 6 字段**,server 两腿的
+ * `brainStatusEventData`(dist/trace/project.js)把 attempt/maxRetries/retryInMs 全发。两处后果:
+ *   · `recovered`(引擎重试**成功**的终态)落 `default:` 臂 ⇒ 被渲成 `kind:'error'`,即
+ *     「刚刚恢复」被渲成「API error · Retrying」—— 方向完全相反的谎报;
+ *   · attempt/maxRetries/retryInMs 在本层被剥掉 ⇒ `RetryStatus` 上早就留好的 attempt/maxRetries
+ *     两位恒缺席。这不是「不许编造」(那条纪律没错),是**供给方给了却没接**。
+ * 反漂移腿:`scripts/run-engine-vocab-floor-test.mjs` G2-b/G2-c 拿下面两张运行期镜像对**实装
+ * @sema-agent/core** 的 `BrainStatusPhase` / `BrainStatus` 逐词逐键对账 —— 引擎再加相/加键,那边先红。
+ */
+/**
+ * core `BrainStatusPhase` 的**运行期值拷贝**(engine-vocab 门 G2-b 拿它对实装 core 对账)。
+ * 引擎侧是闭集,**读时按开集处理** —— 一个部署可以在自己的通道上冒出别的相,认得的分支照走,
+ * 认不得的落 `default:` 兜底(见 {@link mapBrainStatusToRetry} 末臂)。
+ */
+export const BRAIN_STATUS_PHASES = [
+    'rate_limited',
+    'retrying',
+    'reconnecting',
+    'circuit_open',
+    'recovered',
+    'gave_up',
+];
+/**
+ * 上面那个 interface 的**运行期键镜像**(照 `TOOL_APPROVAL_FRAME_KEYS_MIRROR` 先例):
+ * engine-vocab 门 G2-c 拿它与 core `BrainStatus` 的键集逐元素比 ⇒ 引擎 additive 增键当天红。
+ * 下面两个类型钉保证镜像与 interface 之间不可能漂移(少键/多键都是编译错)。
+ */
+export const BRAIN_STATUS_PAYLOAD_KEYS = [
+    'phase',
+    'detail',
+    'retryInSec',
+    'retryInMs',
+    'attempt',
+    'maxRetries',
+];
+const _brainStatusKeyPin = [true, true];
+void _brainStatusKeyPin;
+/**
+ * BrainStatus 载荷 → spinner 行状态。
+ *
+ * 返回 **`null` = 没有覆盖层**(不是「不知道」):今天只有 `recovered` 走这条 —— 引擎明说这次重试
+ * 已经成功,行就该摘掉。此前本函数返回型钉死非空,于是 `recovered` 只能被塞进 error 臂。
  */
 export function mapBrainStatusToRetry(p, nowMs) {
-    const deadline = nowMs + Math.max(0, p.retryInSec ?? 0) * 1000;
+    // 退避剩余量:ms 位在场就用 ms(1200ms 用 sec 位会被 ceil 成 2s,行上少一秒多一秒都是谎)。
+    const remainingMs = typeof p.retryInMs === 'number' ? p.retryInMs : (p.retryInSec ?? 0) * 1000;
+    const deadline = nowMs + Math.max(0, remainingMs);
+    /** 引擎真给的计数才落位;缺席 ⇒ 键不 stamp(诚实缺席,不造 0)。 */
+    const counts = {
+        ...(typeof p.attempt === 'number' ? { attempt: p.attempt } : {}),
+        ...(typeof p.maxRetries === 'number' ? { maxRetries: p.maxRetries } : {}),
+    };
     switch (p.phase) {
+        // 🔴 引擎直报「恢复」:摘行。绝不落 error 臂 —— 那是把成功渲成失败。
+        case 'recovered':
+            return null;
         case 'reconnecting':
-            return { kind: 'stalled', deadline };
+            return { kind: 'stalled', deadline, ...counts };
         case 'rate_limited':
-            return { kind: 'error', deadline, error: { formatted: '', rateLimits: {} } };
+            return { kind: 'error', deadline, ...counts, error: { formatted: '', rateLimits: {} } };
         case 'circuit_open':
             return {
                 kind: 'error',
                 deadline,
+                ...counts,
                 error: { formatted: p.detail ?? 'Service temporarily unavailable', isNetworkDown: true },
             };
+        // 重试用尽:仍是错误行(与 recovered 反向,绝不许一起归成「结束了 ⇒ 清行」),但**打终态位** ——
+        // 实装 core 的 finally 只发 `{phase, detail}`(detail = 'retries exhausted' / 'cancelled while
+        // retrying'),既没有计数也没有 retryIn*,所以「不会再重试了」这件事**只能**由本位表达;
+        // 靠 attempt===maxRetries 去推是错的(供给方根本不发那两位)。
+        case 'gave_up':
+            return { kind: 'error', deadline, terminal: true, ...counts, error: { formatted: p.detail ?? '' } };
         case 'retrying':
         default:
-            return { kind: 'error', deadline, error: { formatted: '' } };
+            return { kind: 'error', deadline, ...counts, error: { formatted: '' } };
     }
 }

package/dist/seam.d.ts

@@ -375,7 +375,50 @@ export type ChromeEvent = {
     kind: 'plan_review_park';
     laneProof: LaneProof;
     result: unknown;
-};
+}
+/**
+ * FIX⑦(2026-08-07,黑板 [3017]/[3020];core 5.14.0 design/171 新 `TaskEvent` 臂,server 7.4.0
+ * 起真上 SSE)——「**谁把什么喂进了这条 run**」的生命周期账本帧:objective / 实时 steer /
+ * nextTurn / parked-steer 续跑 / wake 五个载体共用一个投影点。
+ *
+ * 🔴 **本帧不带正文**(core 的臂里就没有 text 字段)—— 所以它归 chrome 而不是 transcript,
+ * 而且宿主**不许**据此铸任何一行「用户说了…」的转录:那会是替引擎编一句它没说过的话。
+ * 宿主消费义务(全部可选,fail-soft):把它记进会话审计/时间线(「12:03 operator 通过 steer
+ * 注入了一条指令」),或在 HUD 上闪一下。什么都不做也是合法的 —— 本臂存在的第一价值是
+ * **不再落 `unknown_arm` 被丢弃**(账本帧丢了,壳就说不出「这条 run 被谁插过话」)。
+ * `actor.hostAsserted` 是消费端唯一能判「这个署名可信吗」的位:渲署名而不渲这个位 = 把一个
+ * 未经验证的名字渲成可信的(core 自己的 `[from …]` 渲染就是靠它决定加不加 `(unverified)`)。
+ */
+ | HumanInputChromeEvent;
+/**
+ * `human_input` 臂的署名(core `ActorAssertion` 的投影;server 已 redact 后上帧)。
+ * 🔴 `hostAsserted` 是消费端**唯一**能判「这个署名可信吗」的位 —— 渲 `id` 而不渲它,
+ * 等于把一个未经验证的名字渲成可信的。
+ */
+export interface HumanInputActor {
+    id?: string;
+    hostAsserted?: boolean;
+    issuer?: string;
+}
+/** {@link ChromeEvent} 的 `human_input` 臂(具名:本仓 typeshape 门对内联匿名形有棘轮)。 */
+export interface HumanInputChromeEvent {
+    kind: 'human_input';
+    laneProof: LaneProof;
+    /** 载体:objective / steer / next_turn / parked_steer / wake …(core 开集,原样透传)。 */
+    carrier: string;
+    inputId?: string;
+    sessionSeq?: number;
+    /** 入口来源(oa / cc-mcp / portal …)。 */
+    source?: string;
+    delivery?: string;
+    /** 宿主从入口凭据派生的身份串(server 已 redact)。UNTRUSTED-for-display。 */
+    issuer?: string;
+    actor?: HumanInputActor;
+    entryId?: string;
+    /** 引擎铸的**稳定事件身份** —— durable 腿按 `Last-Event-ID` 续读会重放同一条账本帧,宿主
+     *  落审计/时间线时**按这个键幂等**(`inputId`/`entryId` 都是可选位,靠不住)。 */
+    eventId?: string;
+}
 /** `ChromeEvent` 的判别键(臂名)—— 覆盖率断言与宿主装配自检都锚在它上。 */
 export type ChromeArmKind = ChromeEvent['kind'];
 /**

package/dist/seam.js

@@ -35,6 +35,12 @@ const CHROME_ARM_TABLE = {
     prompt_suggestions: { required: false, duty: '推 composer 上方 chips(绝不回喂模型)' },
     last_turn_usage: { required: true, duty: '落最近一次 turn 真 usage(statusline 回落源)' },
     plan_review_park: { required: true, duty: '弹 plan 审批卡(fail-soft,不挡后续终态帧)' },
+    // FIX⑦:账本帧,**不带正文** ⇒ 义务是可选的(记进审计/时间线即可);🔴 硬约束是**不许**据此
+    // 铸转录行,渲署名时必须带上 `actor.hostAsserted` 的可信度标注。
+    human_input: {
+        required: false,
+        duty: '可选:记进会话审计/时间线(谁把什么喂进了这条 run)。绝不铸 transcript 行(本帧不带正文);渲署名必须跟渲 actor.hostAsserted 的可信度标注',
+    },
 };
 /**
  * chrome 臂**覆盖率断言出口**(§8-1 裁决的一半:client-core 定接口不定实现)。

package/dist/seatContract.d.ts

@@ -150,6 +150,17 @@ export interface LocalSessionRecord {
      *  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;
 /** design/80 D-1 的 TOCTOU 绑定**对**(REF-CC-070:此前是两个互不相干的 optional,半个 pair 照样过门)。
  *  一位承载整对 ⇒「只有 callId 没有 inputHash」在类型层不可表达,门里也不用再补联合判据。 */
 export interface ToctouBinding {
@@ -160,8 +171,9 @@ 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. FOUR id domains, prefix-tagged
-     *  (the prefix is what routes the decision back to the right wire verb — see session-host):
+    /** 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);
@@ -170,8 +182,14 @@ export interface ToolPermissionRequest {
      *                                       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).
-     *  The three LIVE domains are same-replica + non-durable: a late/duplicate decision 404s, which the
+     *                                       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;
@@ -595,6 +613,12 @@ export interface LocalSessionsApi {
     /** 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). */
@@ -606,11 +630,36 @@ 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;
+    baseUrl: string;
+    api: "anthropic-messages" | "openai-completions";
+    apiKey?: string;
+    modelId: string;
+    contextWindow: number;
+    maxTokens: number;
+    cheapHint?: boolean;
+}
+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", "onEvent", "onToolPermissionRequest"];
+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"` 的那一撮,门里逐元素对账。 */
@@ -681,6 +730,11 @@ export declare const SEAT_VALIDATOR_KEY_COVERAGE: {
         readonly validated: readonly ["models", "defaultId"];
         readonly unchecked: readonly [];
     };
+    readonly ApplyModelConfigResult: {
+        readonly check: (v: unknown) => SeatValidation;
+        readonly validated: readonly ["ok", "requiresRestart", "reason"];
+        readonly unchecked: readonly [];
+    };
     readonly SendMessageAck: {
         readonly guard: "isSendMessageAck";
         readonly check: (v: unknown) => SeatValidation;
@@ -760,6 +814,6 @@ export declare const SEAT_VALIDATOR_COVERAGE_EXEMPT: readonly [{
 }, {
     readonly label: "LaneProof";
     readonly check: (v: unknown) => SeatValidation;
-    readonly why: "判别式联合:必填键面随 `lane` 臂而变(subagent 要 parentToolCallId、workflow 要 via+key),而覆盖表的方法是「一个最小合法体 + 逐键投毒」—— 那套方法在它身上没有判别力(main 臂对另外两臂的伴随位本来就不该拒,投毒过了不代表漏校)。判别力由 `LANE_PROOF_LANE_TUPLE` ⇄ seam.ts 车道联合的双向 `Covers` + F 段逐臂投毒(空对象 / 非对象 / 未登记车道词)承担。";
+    readonly why: string;
 }];
 export {};

package/dist/seatContract.js

@@ -98,6 +98,26 @@ const isObject = (v) => typeof v === "object" && v !== null;
 const isAbsent = (v) => typeof v === "undefined";
 const optionalString = (v) => isAbsent(v) || typeof v === "string";
 const inTuple = (tuple, v) => tuple.includes(v);
+/**
+ * `ToolPermissionRequest.requestId` 的**域词表**(FIX⑥,2026-08-07)—— 三端唯一真源。
+ *
+ * 🔴 前缀不是装饰:它**就是**决断的路由依据(session-host 按它挑 wire 动词)。一个域外的 requestId
+ * 意味着「这条决断无处可去」,所以校验器对它 fail-loud 而不是放行(此前门只校「是不是串」,
+ * 于是 desktop 早就在用的 `plan:` 既不在枚举里、也不会被任何一处说出来)。
+ */
+export const TOOL_PERMISSION_REQUEST_ID_DOMAINS = [
+    "live:",
+    "durable:",
+    "question:",
+    "elicit:",
+    "plan:",
+];
+/** 读口:requestId → 它的域。未登记前缀 / 非串 ⇒ `undefined`(诚实缺席,绝不猜一个域)。 */
+export function toolPermissionRequestIdDomain(requestId) {
+    if (typeof requestId !== "string")
+        return undefined;
+    return TOOL_PERMISSION_REQUEST_ID_DOMAINS.find((d) => requestId.startsWith(d));
+}
 export const TOCTOU_BINDING_KEYS = ["callId", "inputHash"];
 /**
  * 座位事件名的**闭集**(REF-CC-065):这是三端唯一的事件名真源。
@@ -250,6 +270,10 @@ const checkToolPermissionRequest = (r) => {
         return bad("tool permission request is not an object");
     if (typeof r.requestId !== "string")
         return bad("requestId must be a string", "requestId");
+    // FIX⑥:域(前缀)就是决断的路由依据 —— 认不出域 = 这条决断无处可去,fail-closed 而不是放行。
+    if (toolPermissionRequestIdDomain(r.requestId) === undefined) {
+        return bad(`requestId must carry a registered domain prefix (${TOOL_PERMISSION_REQUEST_ID_DOMAINS.join("|")})`, "requestId");
+    }
     if (typeof r.sessionId !== "string")
         return bad("sessionId must be a string", "sessionId");
     if (!isAbsent(r.toolName) && r.toolName !== null && typeof r.toolName !== "string") {
@@ -417,6 +441,22 @@ const checkSeatModelInfo = (m, index) => {
     }
     return true;
 };
+/** applyModelConfig ack 校验:布尔形 + reason 条件在场(ok:false ⇒ 必带非空 reason)。
+ *  🔴 错误消息零回显 req/ack 值——本 verb 载荷带 apiKey,校验层是回显面之一。 */
+const checkApplyModelConfigResult = (v) => {
+    if (!isObject(v))
+        return bad("applyModelConfig result is not an object");
+    if (typeof v.ok !== "boolean")
+        return bad("ok must be a boolean", "ok");
+    if (typeof v.requiresRestart !== "boolean")
+        return bad("requiresRestart must be a boolean", "requiresRestart");
+    if (v.ok === false && (typeof v.reason !== "string" || v.reason.length === 0)) {
+        return bad("reason must be a non-empty string when ok is false", "reason");
+    }
+    if (v.reason !== undefined && typeof v.reason !== "string")
+        return bad("reason must be a string when present", "reason");
+    return true;
+};
 const checkSeatModelCatalog = (v) => {
     if (!isObject(v))
         return bad("model catalog is not an object");
@@ -548,6 +588,7 @@ export const LOCAL_SESSIONS_SPEC = {
         searchSessions: { kind: "invoke", check: checkSessionSearchEnvelope },
         uploadAttachment: { kind: "invoke", check: checkAttachmentUploadReceipt },
         listModels: { kind: "invoke", check: checkSeatModelCatalog },
+        applyModelConfig: { kind: "invoke", check: checkApplyModelConfigResult },
         onEvent: { kind: "event", check: checkLocalSessionEvent },
         onToolPermissionRequest: { kind: "event", check: checkToolPermissionRequest },
     },
@@ -573,6 +614,7 @@ export const SEAT_METHOD_NAMES = [
     "searchSessions",
     "uploadAttachment",
     "listModels",
+    "applyModelConfig",
     "onEvent",
     "onToolPermissionRequest",
 ];
@@ -730,6 +772,11 @@ export const SEAT_VALIDATOR_KEY_COVERAGE = {
         validated: ["models", "defaultId"],
         unchecked: [],
     },
+    ApplyModelConfigResult: {
+        check: checkApplyModelConfigResult,
+        validated: ["ok", "requiresRestart", "reason"],
+        unchecked: [],
+    },
     SendMessageAck: {
         guard: "isSendMessageAck",
         check: checkSendMessageAck,
@@ -815,7 +862,11 @@ export const SEAT_VALIDATOR_COVERAGE_EXEMPT = [
     {
         label: "LaneProof",
         check: (v) => checkLaneProof(v, "laneProof"),
-        why: "判别式联合:必填键面随 `lane` 臂而变(subagent 要 parentToolCallId、workflow 要 via+key),而覆盖表的方法是「一个最小合法体 + 逐键投毒」—— 那套方法在它身上没有判别力(main 臂对另外两臂的伴随位本来就不该拒,投毒过了不代表漏校)。判别力由 `LANE_PROOF_LANE_TUPLE` ⇄ seam.ts 车道联合的双向 `Covers` + F 段逐臂投毒(空对象 / 非对象 / 未登记车道词)承担。",
+        why: "判别式联合:必填键面随 `lane` 臂而变(subagent 要 parentToolCallId、workflow 要 via+key),而覆盖表的方法是「一个最小合法体 + 逐键投毒」—— 那套方法在它身上没有判别力(main 臂对另外两臂的伴随位本来就不该拒,投毒过了不代表漏校)。" +
+            "🔴 FIX④(2026-08-07 订正):本条此前自称判别力由「F 段**逐臂**投毒(空对象 / 非对象 / **未登记车道词**)」承担 —— 全树实扫,那三样里只有**空对象**与**非对象**真的存在(run-seat-contract-keys-test.mjs F 段)," +
+            "「未登记车道词」实际只钉了 `lane: 7`(非串,证明不了闭集成员判定在场),「逐臂」(subagent 缺 parentToolCallId / workflow 缺 via+key)则是**零覆盖**。也就是说这条豁免曾经拿三件不存在的判据给自己背书。" +
+            "现势(判据锚在真存在的东西上):① `LANE_PROOF_LANE_TUPLE` ⇄ seam.ts 车道联合的双向 `Covers`(本文件 `_seatContractPins`,加车道不跟 ⇒ 编译红);" +
+            "② run-client-core-pure-test.mjs **FIX7 段 ④** —— 未登记车道词 / subagent 缺伴随位 / workflow 缺 via 或 key 三条投毒 + 两条逐臂正控 + 一条「main 臂不被过紧误拒」负控,全部直接喂本条的 `check`。",
     },
 ];
 /** 双向覆盖钉:`Exclude` 两个方向都必须塌成 `never`,少一个键红、多一个键也红。

package/dist/skillsWireCaps.d.ts

@@ -8,17 +8,44 @@
  * loader graph (loadSkillsDir / loadPluginCommands pull analytics/signals/fs). It imports ONLY the `SkillSpec`
  * type (erased at build), so a test can esbuild-bundle THIS file alone — no runtime side effects.
  *
- * The caps mirror the SDK `TaskRequest.skills` server caps (types.ts:82): ≤10 items, name ≤64, description
- * ≤1024, content ≤32768 — a violation is a 400, so we truncate/limit HERE to make the live request well-formed
+ * The caps mirror the server's `validateUserSkills` hard limits: ≤10 items, name ≤64, description ≤1024,
+ * content ≤1MB — a violation is a 400, so we truncate/limit HERE to make each FIELD well-formed
  * by construction.
+ *
+ * 🔴 措辞收窄(2026-08-08 codex 复审命中):原文写「make the live request well-formed by construction」——
+ * 那是**过头的承诺**,本模块只管每个字段的**逐字段**帽,管不到整请求。server 那边 10 项 × 1MB 与
+ * 它自己 8MB 的 `MAX_BODY` 是两个互不知情的帽,所以极端技能集仍可能整请求 400/413。本层不加
+ * 「按剩余预算偷偷多截一点」的聚合补偿:那恰好把一个响亮的 400 换回一次静默截断(= 本次修掉的病)。
+ * 该治的是 server 两帽的一致性;此处只把承诺说准。
  */
 import type { SkillSpec } from '@sema-agent/sdk';
-/** Server caps for `TaskRequest.skills` (SDK types.ts:82 — violations are a 400). */
+/**
+ * Server caps for `TaskRequest.skills` — violations are a 400 (server `validateUserSkills`).
+ *
+ * 🔴 对照坐标(2026-08-08 修正,#3004 跟修批;取证方式 = 直读 shipped 产物,不信任何注释):
+ *   · `items` / `name` / `description` —— server `dist/http/server.js` `validateUserSkills`:
+ *     `MAX_USER_SKILLS = 10`、name 上限字面量 `64`、description 上限字面量 `1024`(7.5.0 实测)。
+ *   · `content` —— server `MAX_SKILL_CONTENT_CHARS = 1_048_576`(`dist/http/server.js`),它自己的
+ *     头注点名这是 core `SKILL_CONTENT_MAX_CHARS` 的同值孪生(core `dist/core/runner/synthetic-tools.js`
+ *     的 `SKILL_CONTENT_MAX_CHARS = 1024 * 1024`);core 1.293 起技能正文**零截断、超 1MB 整拒**。
+ *
+ * 🔴 此前这一键钉 `32768` —— 那不是「上游改小了」,而是**一开始就抄错**:32768 是 server 的
+ * `MAX_OUTPUT_SCHEMA_CHARS`(另一个量)。错值的后果不是 400、是**静默截到 1/32**:`toCappedSpec`
+ * 在发请求前就把技能正文切掉,模型看见的 SKILL.md 少一大截,而链上任何一层都不会响一声。
+ *
+ * 反漂移腿:`scripts/run-engine-vocab-floor-test.mjs` 的 G2-a 段拿本键对**实装 @sema-agent/core**
+ * 的 `SKILL_CONTENT_MAX_CHARS` 逐值对账(devDep 钉在本仓,不靠兄弟树物料)——上游改门,那边先红。
+ *
+ * ⚠️ 留给上游的一处**上游内部张力**(如实记录,本层不代偿):server 允许 10 条 × 1MB = 10MB 技能,
+ * 而它自己的整体 body 帽是 8MB(`MAX_BODY`)—— 极端组合会整请求 400/413。这是 server 两个帽之间的
+ * 事,壳侧不做「按剩余预算偷偷多截一点」的补偿:那正好会把一个**响亮的 400** 换回一次**静默截断**,
+ * 即本次修的这个病。真要治,治在 server 的两帽一致性上。
+ */
 export declare const SKILL_CAPS: {
     readonly items: 10;
     readonly name: 64;
     readonly description: 1024;
-    readonly content: 32768;
+    readonly content: 1048576;
 };
 /** The minimal shape of a loaded skill `Command` this projection reads (a structural subset of CC's Command,
  *  cast at the call site so we stay decoupled from the wide Command union). */

package/dist/skillsWireCaps.js

@@ -1,5 +1,26 @@
-/** Server caps for `TaskRequest.skills` (SDK types.ts:82 — violations are a 400). */
-export const SKILL_CAPS = { items: 10, name: 64, description: 1024, content: 32768 };
+/**
+ * Server caps for `TaskRequest.skills` — violations are a 400 (server `validateUserSkills`).
+ *
+ * 🔴 对照坐标(2026-08-08 修正,#3004 跟修批;取证方式 = 直读 shipped 产物,不信任何注释):
+ *   · `items` / `name` / `description` —— server `dist/http/server.js` `validateUserSkills`:
+ *     `MAX_USER_SKILLS = 10`、name 上限字面量 `64`、description 上限字面量 `1024`(7.5.0 实测)。
+ *   · `content` —— server `MAX_SKILL_CONTENT_CHARS = 1_048_576`(`dist/http/server.js`),它自己的
+ *     头注点名这是 core `SKILL_CONTENT_MAX_CHARS` 的同值孪生(core `dist/core/runner/synthetic-tools.js`
+ *     的 `SKILL_CONTENT_MAX_CHARS = 1024 * 1024`);core 1.293 起技能正文**零截断、超 1MB 整拒**。
+ *
+ * 🔴 此前这一键钉 `32768` —— 那不是「上游改小了」,而是**一开始就抄错**:32768 是 server 的
+ * `MAX_OUTPUT_SCHEMA_CHARS`(另一个量)。错值的后果不是 400、是**静默截到 1/32**:`toCappedSpec`
+ * 在发请求前就把技能正文切掉,模型看见的 SKILL.md 少一大截,而链上任何一层都不会响一声。
+ *
+ * 反漂移腿:`scripts/run-engine-vocab-floor-test.mjs` 的 G2-a 段拿本键对**实装 @sema-agent/core**
+ * 的 `SKILL_CONTENT_MAX_CHARS` 逐值对账(devDep 钉在本仓,不靠兄弟树物料)——上游改门,那边先红。
+ *
+ * ⚠️ 留给上游的一处**上游内部张力**(如实记录,本层不代偿):server 允许 10 条 × 1MB = 10MB 技能,
+ * 而它自己的整体 body 帽是 8MB(`MAX_BODY`)—— 极端组合会整请求 400/413。这是 server 两个帽之间的
+ * 事,壳侧不做「按剩余预算偷偷多截一点」的补偿:那正好会把一个**响亮的 400** 换回一次**静默截断**,
+ * 即本次修的这个病。真要治,治在 server 的两帽一致性上。
+ */
+export const SKILL_CAPS = { items: 10, name: 64, description: 1024, content: 1_048_576 };
 /** Build one capped `SkillSpec`, or null when there is no usable name/body. description folds in `whenToUse`
  *  (CC's progressive-disclosure metadata is name+description+whenToUse) so the engine's Skill tool can select
  *  it. All three fields are truncated to the server caps. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/client-core",
-  "version": "0.19.0",
+  "version": "0.20.1",
   "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",
@@ -28,12 +28,12 @@
   },
   "peerDependencies": {
     "@sema-agent/agent-types": ">=0.2.0",
-    "@sema-agent/sdk": ">=6.3.0"
+    "@sema-agent/sdk": ">=6.9.0"
   },
   "devDependencies": {
     "@sema-agent/agent-types": "^0.2.0",
     "@sema-agent/core": "^5.10.0",
-    "@sema-agent/sdk": "^6.3.0",
+    "@sema-agent/sdk": "^6.9.0",
     "esbuild": "^0.27.4",
     "typescript": "^6.0.2"
   }