@sema-agent/client-core 0.12.2 → 0.13.0

package/dist/adapter/runStream.js

@@ -4,6 +4,105 @@ import { terminalToSdkResult } from './downstream/terminalToSdkResult.js';
 import { publishSubagentContentEvent } from '../subagentContentStore.js';
 /** 本文件发的 chrome 事件全在 leader lane(子代内容在上面就被 divert 走了)。 */
 const MAIN = { lane: 'main' };
+/**
+ * 409 session-busy 拒绝的 **canonical errorCode**([2377]C-1,server main `049ff2c`,随 5.0.0 发)。
+ * 引擎把它 stamp 在 `done{status:'failed'}` / `failed` 终帧上,壳据此**结构判读**,不再读人话。
+ */
+const ACTIVE_RUN_BUSY_ERROR_CODE = 'conflict.session_active_run';
+/**
+ * 判别一个**原始 AgentEvent** 是不是 409 active-run 拒收终帧;非 busy ⇒ null。
+ * 判据=结构两腿(canonical `errorCode` 优先 → `activeTaskId` 在场);人话文案腿已随 #117 提货
+ * 退役(§B8 禁按错误文案判别)。两种 wire 真形:
+ *   ① `done{result:{status:'failed', errorCode|activeTaskId,…}}`(交互 tasks/stream 腿,409 骑终帧);
+ *   ② `failed{errorCode|activeTaskId,…}`(任何把它投影成 failed 臂的上游形)。
+ */
+export function activeRunBusySignal(ev) {
+    if (typeof ev !== 'object' || ev === null || !('type' in ev))
+        return null;
+    const type = ev.type;
+    let carrier;
+    if (type === 'done') {
+        const result = ev.result;
+        if (typeof result !== 'object' || result === null)
+            return null;
+        if (result.status !== 'failed')
+            return null;
+        carrier = result;
+    }
+    else if (type === 'failed') {
+        carrier = ev;
+    }
+    else {
+        return null;
+    }
+    const cls = classifyActiveRunBusy({
+        errorCode: typeof carrier.errorCode === 'string' ? carrier.errorCode : undefined,
+        activeTaskId: carrier.activeTaskId,
+    });
+    if (!cls.busy)
+        return null;
+    const status = carrier.activeTaskStatus;
+    const rawGate = carrier.pendingGate;
+    let pendingGate = null;
+    if (typeof rawGate === 'object' && rawGate !== null) {
+        const k = rawGate.kind;
+        const d = rawGate.decidePath;
+        pendingGate = {
+            kind: typeof k === 'string' && k.length > 0 ? k : null,
+            decidePath: typeof d === 'string' && d.length > 0 ? d : null,
+        };
+    }
+    return {
+        activeTaskId: cls.handle,
+        activeTaskStatus: typeof status === 'string' && status.length > 0 ? status : null,
+        pendingGate,
+    };
+}
+/**
+ * 结构位优先的 409 判别(REF-CC-054 / dup-03 + 域词表-02,§B8 禁按错误文案判别)。
+ *
+ * 顺序即优先级:①引擎 canonical `errorCode`(结构位,机器码);②`activeTaskId` 在场(同样是
+ * 结构性判据,[1833] G10 起就在 wire 上)。③人话子串锚已于 2026-08-03 随 #117 提货退役(见上)。
+ *
+ * 事故出处:此前整条判别是 `errText.includes(锚) || typeof activeTaskId === 'string'`,而 2026-07-31
+ * 才发现锚曾是**全等**式、在今天的任何引擎上一次都命中不了 —— 判别一直只靠 activeTaskId 那一半在兜。
+ * 上游把人话加长一句判别就死一半,这正是 B8 要禁的那类定时炸弹。
+ */
+function classifyActiveRunBusy(input) {
+    const handle = typeof input.activeTaskId === 'string' && input.activeTaskId.length > 0 ? input.activeTaskId : null;
+    if (input.errorCode === ACTIVE_RUN_BUSY_ERROR_CODE)
+        return { busy: true, handle };
+    if (typeof input.activeTaskId === 'string')
+        return { busy: true, handle };
+    return { busy: false, handle };
+}
+/**
+ * 已上报过的未知帧类型(REF-CC-057:每种臂只吼一次,免得一条流刷屏)。
+ * 🔴 单例登记见 `docs/refactor/p1-scan/singleton-manifest.json`:复制两份的后果 = 同一种臂多打
+ * 几行 stderr,不影响正确性(dupRisk=low)。
+ */
+const reportedDroppedTypes = new Set();
+/**
+ * 未知/畸形帧的**留痕**(§C5 丢弃必须留痕,且痕迹要到得了能处置它的人)。
+ *
+ * 为什么是 `console.error` 而不是 `hostLog`:runStream 是**可移植内核**,portability 门对它的
+ * 传递闭包断言「零 Node 内建 + 文件数上限 6」,值级 import `host.ts` 会当场把闭包撑破。
+ * console 在 Node 与浏览器都在,与 `host.ts` 自己那条「口没装就吼一声」的 miss 提示同款姿势。
+ * 🔴 已知限制(诚实披露):Ink 挂载后宿主会吞 console,所以 TUI 里这行未必上屏 —— 那正是
+ * `EventProjection.dropped` 存在的意义:想在自己那一端把它渲出来的宿主,读返回值即可。
+ */
+function reportDroppedFrame(why, type) {
+    if (reportedDroppedTypes.has(type))
+        return;
+    reportedDroppedTypes.add(type);
+    // eslint-disable-next-line no-console
+    console.error(`[client-core] dropped an engine frame (${why}): type="${type}" — this build's projector has no arm ` +
+        'for it (engine newer than the client, or a malformed frame). It renders NOWHERE.');
+}
+/** 测试钩:清空「已上报过的臂」去重表(去重是**跨调用**状态,不清就只有第一条用例看得见)。 */
+export function _resetDroppedFrameReportForTest() {
+    reportedDroppedTypes.clear();
+}
 /**
  * Drive one AgentEvent source into a CC SDKMessage stream.
  *
@@ -94,8 +193,14 @@ async function* runStreamInner(events, ctx, handle = {}) {
                 if (!isSubFlow && ctx.emitChrome) {
                     try {
                         // engineUsage = [2295] 裁 ② 逐字原形(additive 键,契约见 seam.ts 本臂 doc):
-                        // 总量/命中率消费面吃它,镜像 usage 保纯。
-                        void ctx.emitChrome({ kind: 'last_turn_usage', laneProof: MAIN, usage, engineUsage: ev.usage });
+                        // 总量/命中率消费面吃它,镜像 usage 保纯。eopt:additive 键按「诚实缺席」= 键不在
+                        // (与 turn_end.usage 本身「整体 optional,缺席≠空对象」同一语义,不是「键在值 undefined」)。
+                        void ctx.emitChrome({
+                            kind: 'last_turn_usage',
+                            laneProof: MAIN,
+                            usage,
+                            ...(ev.usage !== undefined ? { engineUsage: ev.usage } : {}),
+                        });
                     }
                     catch { /* fail-soft — statusline 退回 null,原语义 */ }
                 }
@@ -139,14 +244,19 @@ async function* runStreamInner(events, ctx, handle = {}) {
                 // 本层只负责:识别 + 说真话。
                 const activeTaskId = failedResult?.activeTaskId ??
                     (ev.type === 'failed' ? ev.activeTaskId : undefined);
-                // 🔴 2026-07-31:锚必须是 `includes` 不是全等 —— 引擎发的原文是
-                // 「session already has an active run — POST /v1/runs/{activeTaskId}/cancel stops it …」
-                // (server dist/http/routes/tasks.js,3.10.0/3.18.0 逐字同形),比锚长。原来的全等式在
-                // 今天的任何引擎上**一次都命中不了**,整条判别一直只靠 activeTaskId 那一半在兜。
-                const isActiveRunBusy = errText.includes('session already has an active run') || typeof activeTaskId === 'string';
+                // REF-CC-054:判别**结构位两腿**(errorCode → activeTaskId;文案兜底腿 2026-08-03 已退役),
+                // 判别体见文件上方 `classifyActiveRunBusy`。
+                const busy = classifyActiveRunBusy({
+                    errorCode: ev.type === 'failed' ? ev.errorCode : failedResult?.errorCode,
+                    activeTaskId,
+                });
                 // 件14 rev2 (2026-07-14): provider max_tokens cap rejection (e.g. glm-5.2 preset 131072 >
                 // a third-party gateway's 128000) → append the way out. Keyword match on the upstream text,
                 // supplement never mask (raw provider words stay on the row).
+                // 🟢 B8 ALLOW 清单登记(REF-CC-域词表-08,属主=client-core 规范重构轮,单列一类:命中只
+                // 流向字符串拼接、不流向 if/return——supplement-only,零控制流。误判方向单侧:误命中只多
+                // 一行提示,误失效只少一行提示,行为面(哪一行 API Error / isError)不受影响。别把它跟
+                // 会改判别方向的判据(域词表-01/02 那种)混进同一张门里整体豁免)。
                 const maxTokHint = /max_tokens/i.test(errText)
                     ? '\nyour provider caps max_tokens lower — lower it in /model (press m, or M to type a value)'
                     : '';
@@ -158,8 +268,8 @@ async function* runStreamInner(events, ctx, handle = {}) {
                 //     重启引擎捞不回来(boot 期孤儿回收只捞 running)、时间型 reap 挂在
                 //     APPROVAL_TIMEOUT_SEC(默认 0 ⇒ 整条腿不跑),唯一兜底窗是 30 天。
                 // 换成真话 + 真的存在的两条动作(引擎的 cancel 端点 / 换一个会话)。
-                const busyHandle = typeof activeTaskId === 'string' && activeTaskId.length > 0 ? activeTaskId : null;
-                const rowText = isActiveRunBusy
+                const busyHandle = busy.handle;
+                const rowText = busy.busy
                     ? `This session is locked by an earlier run${busyHandle ? ` (run ${busyHandle})` : ''} that ` +
                         `has not been released, so this message was NOT sent. Nothing releases it on its own — ` +
                         `cancel that run (POST /v1/runs/${busyHandle ?? '<id>'}/cancel), or start a new session.`
@@ -192,9 +302,15 @@ async function* runStreamInner(events, ctx, handle = {}) {
             yield terminalToSdkResult(ev, ctx);
             return;
         }
-        // Every other arm → zero-or-one renderable SDKMessage.
-        const msg = eventToSdkMessage(ev, ctx);
-        if (msg)
-            yield msg;
+        // Every other arm → typed three-state projection(REF-CC-058)。
+        const projection = eventToSdkMessage(ev, ctx);
+        if (projection.kind === 'message') {
+            yield projection.message;
+            continue;
+        }
+        // REF-CC-057:`dropped` 是「引擎发了一帧、这个 build 渲不出来」——**必须留痕**;
+        // `none` 是设计内无可渲染臂(usage 折叠/终帧代理/HITL 登记),不留痕才是对的。
+        if (projection.kind === 'dropped')
+            reportDroppedFrame(projection.why, projection.type);
     }
 }

package/dist/adapter/types.d.ts

@@ -65,8 +65,8 @@ export interface EmitContext {
 }
 /** Stamp `uuid` + `session_id` onto a freshly-built arm body. */
 export declare function stamp<T extends {
-    uuid?: string;
-    session_id?: string;
+    uuid?: string | undefined;
+    session_id?: string | undefined;
 }>(ctx: EmitContext, body: T): T & {
     uuid: string;
     session_id: string;

package/dist/agentSession/backgroundView.js

@@ -1,3 +1,4 @@
+import { abortableSleep } from '../abortableSleep.js';
 import { errCodes } from '../controlRouter.js';
 import { engineWireDebugEnabled } from '../engineWireTarget.js';
 import { hostLog } from '../host.js';
@@ -217,20 +218,6 @@ export function createBackgroundView(client, opts) {
             notify();
         }
     }
-    /** abort 感知的 sleep:dispose 立即唤醒并清定时器(不留悬挂 timer 拖住宿主进程)。 */
-    function sleep(ms) {
-        return new Promise((resolve) => {
-            const timer = setTimeout(() => {
-                abort.signal.removeEventListener('abort', onAbort);
-                resolve();
-            }, ms);
-            const onAbort = () => {
-                clearTimeout(timer);
-                resolve();
-            };
-            abort.signal.addEventListener('abort', onAbort, { once: true });
-        });
-    }
     async function loop() {
         while (!disposed && !abort.signal.aborted) {
             try {
@@ -242,7 +229,9 @@ export function createBackgroundView(client, opts) {
             }
             if (disposed || abort.signal.aborted)
                 return;
-            await sleep(intervalMs);
+            // REF-CC-147:abort 感知的 sleep(dispose 立即唤醒并清定时器,不留悬挂 timer 拖住宿主
+            // 进程)——本函数原实现已抽成共享叶 ../abortableSleep.js,workflowClient.ts 同款消费。
+            await abortableSleep(intervalMs, abort.signal);
         }
     }
     void loop();

package/dist/agentsWireCaps.d.ts

@@ -1,3 +1,4 @@
+import { type EngineProbeOpts } from './engineWireSdk.js';
 export declare const MAX_TASK_AGENTS = 32;
 export declare const MAX_AGENT_NAME_CHARS = 64;
 export declare const MAX_AGENT_TEXT_CHARS = 4096;
@@ -78,12 +79,7 @@ export declare function projectAgentsForWire(defs: readonly AgentDefLike[], deps
  * 语义变形)。差分:SDK 恒 stamp x-agent-principal(缺省 'anon:shell-live'),原手抄缺 principal
  * 时省略该头——principal-first 宪法姿势,fail-open 改善(engineWireSdk 头注记账)。
  */
-export declare function engineSupportsTaskAgents(baseUrl: string, opts?: {
-    fetchImpl?: typeof fetch;
-    timeoutMs?: number;
-    authToken?: string;
-    principal?: string;
-}): Promise<boolean | undefined>;
+export declare function engineSupportsTaskAgents(baseUrl: string, opts?: EngineProbeOpts): Promise<boolean | undefined>;
 export type WireConfig = {
     baseUrl: string;
     authToken?: string;
@@ -98,6 +94,14 @@ export declare function prepareTaskAgentsWireWith(cfg: WireConfig, projector: Pr
 /**
  * 有界就绪门(liveClient.stream 首帧前 await;缺省 4s 上限)。prepare 未 kick(mock 车道/测试)或
  * 超时 ⇒ 立即放行(本 turn 不带 agents,fail-soft)。永不抛。
+ *
+ * 🔴 域词表-13(RB-447 同形):这个 race 的唯一有界退出臂**绝不 unref**——它是被调用方真
+ * await 的控制流(liveClient.ts `await awaitTaskAgentsWire()`),不是后台保活豁免;unref 会让
+ * 宿主进程能在它 settle 前提前退出,届时这个 await 永远等不到结果。对照组:
+ * askGateWire.ts 的 budget 定时器同样 unref,但它挂在无人 await 的 `void Promise.race(...)` 上,
+ * 后果只是丢一行 warn——两处形状相同后果不同,分野在于「这个 promise 有没有被 await」,不能
+ * 套用同一个 unref 兼容套(见 unrefTimer.ts 头注)。race settle 后 clearTimeout 掉该句柄
+ * (此前完全没有 clear,超时臂即使先输也留着一个已到期的句柄)。
  */
 export declare function awaitTaskAgentsWire(timeoutMs?: number): Promise<void>;
 /**

package/dist/agentsWireCaps.js

@@ -277,17 +277,31 @@ export function prepareTaskAgentsWireWith(cfg, projector) {
 /**
  * 有界就绪门(liveClient.stream 首帧前 await;缺省 4s 上限)。prepare 未 kick(mock 车道/测试)或
  * 超时 ⇒ 立即放行(本 turn 不带 agents,fail-soft)。永不抛。
+ *
+ * 🔴 域词表-13(RB-447 同形):这个 race 的唯一有界退出臂**绝不 unref**——它是被调用方真
+ * await 的控制流(liveClient.ts `await awaitTaskAgentsWire()`),不是后台保活豁免;unref 会让
+ * 宿主进程能在它 settle 前提前退出,届时这个 await 永远等不到结果。对照组:
+ * askGateWire.ts 的 budget 定时器同样 unref,但它挂在无人 await 的 `void Promise.race(...)` 上,
+ * 后果只是丢一行 warn——两处形状相同后果不同,分野在于「这个 promise 有没有被 await」,不能
+ * 套用同一个 unref 兼容套(见 unrefTimer.ts 头注)。race settle 后 clearTimeout 掉该句柄
+ * (此前完全没有 clear,超时臂即使先输也留着一个已到期的句柄)。
  */
 export async function awaitTaskAgentsWire(timeoutMs = 4000) {
     if (!preparedPromise)
         return;
-    await Promise.race([
-        preparedPromise.catch(() => { }),
-        new Promise(resolve => {
-            const t = setTimeout(resolve, timeoutMs);
-            t.unref?.();
-        }),
-    ]);
+    let timeoutHandle;
+    try {
+        await Promise.race([
+            preparedPromise.catch(() => { }),
+            new Promise(resolve => {
+                timeoutHandle = setTimeout(resolve, timeoutMs);
+            }),
+        ]);
+    }
+    finally {
+        if (timeoutHandle !== undefined)
+            clearTimeout(timeoutHandle);
+    }
 }
 /**
  * 同步读面(liveClient.toLiveRequest 消费):当前投影好的 agents 载荷。每次读取后 kick 一次后台

package/dist/argvFlagValue.d.ts

@@ -0,0 +1,41 @@
+/**
+ * src/argvFlagValue.ts — shared CC/commander-style "last flag value" argv-scan primitive
+ * (REF-CC-143 / REF-CC-dup-07, P3 wave1 卡C-argv, 2026-08-01;缺值策略位补于 wave1 回炉,
+ * blocker 修复,同日).
+ *
+ * Five call sites (limitsWire / sandboxWire / scenarioWire / headlessPermissionModeWire —
+ * interactiveToolsWire's own copy folds away entirely per REF-CC-dup-10, delegating to
+ * headlessPermissionModeWire instead) each hand-rolled the identical loop: scan everything
+ * before a bare `--` (positionals are never flags), accept both `--name <v>` and `--name=<v>`
+ * forms, repeated flag ⇒ LAST wins (commander convention).
+ *
+ * 缺值策略(收编口径,`onMissingValue` 显式位):当某一次 occurrence 的值缺席/长得像另一个 flag
+ * 时,这个共用叶提供两种可命名的处置——**调用方选,不由本叶替调用方决定**:
+ *   · `'invalidate'`(缺省,limitsWire/sandboxWire/scenarioWire 用这个):那次缺值让整个旗的最终
+ *     取值塌缩成「有旗、无值」(`{present:true}`,raw 缺席)——与这三处一直以来的 fail-LOUD 立场
+ *     一致:重复旗严格 LAST occurrence 定生死,哪怕最后一次是缺值也不会回落到更早的合法值。
+ *   · `'latch-previous'`(headlessPermissionModeWire 用这个):那次缺值被当作「这次 occurrence 没
+ *     提供新信息」,直接跳过,锁存(latch)住之前已经取到的合法值不动——这是收编前那份手写循环
+ *     的原语义(`if (typeof v === 'string' && !v.startsWith('-')) { mode = v }`,缺值分支从不碰
+ *     `mode`),收编成共用叶不能悄悄把它改造成 invalidate 语义。
+ * 两种策略都遵守同一条不变量:**从未出现过合法值** ⇒ 恒回 `{present:true}`(raw 缺席),从不
+ * 编造一个值;调用方各自决定「有旗无值」之后怎么办(fail-loud 用法提示,或落到下一车道)。
+ */
+/** `lastFlagValue` 的判别式返回型(非法组合 `{present:false, raw:'x'}` 在类型层就不可构造)。 */
+export type FlagValue = {
+    present: false;
+} | {
+    present: true;
+    raw?: string;
+};
+/** 缺值(occurrence 存在但值缺席/长得像另一个 flag)时的处置策略——见上方模块 doc。 */
+export type OnMissingFlagValue = 'invalidate' | 'latch-previous';
+/**
+ * Pull the LAST value of a `--name <v>` / `--name=<v>` flag out of an argv slice (everything
+ * before a bare `--` — positionals are never flags). Returns:
+ *   {present:false}                 — flag absent
+ *   {present:true, raw}             — flag present with a value token (possibly empty string)
+ *   {present:true, raw:undefined}   — flag present but no value was ever captured (see
+ *                                      `onMissingValue` for what "captured" means across repeats)
+ */
+export declare function lastFlagValue(argv: readonly string[], name: string, onMissingValue?: OnMissingFlagValue): FlagValue;

package/dist/argvFlagValue.js

@@ -0,0 +1,69 @@
+/**
+ * src/argvFlagValue.ts — shared CC/commander-style "last flag value" argv-scan primitive
+ * (REF-CC-143 / REF-CC-dup-07, P3 wave1 卡C-argv, 2026-08-01;缺值策略位补于 wave1 回炉,
+ * blocker 修复,同日).
+ *
+ * Five call sites (limitsWire / sandboxWire / scenarioWire / headlessPermissionModeWire —
+ * interactiveToolsWire's own copy folds away entirely per REF-CC-dup-10, delegating to
+ * headlessPermissionModeWire instead) each hand-rolled the identical loop: scan everything
+ * before a bare `--` (positionals are never flags), accept both `--name <v>` and `--name=<v>`
+ * forms, repeated flag ⇒ LAST wins (commander convention).
+ *
+ * 缺值策略(收编口径,`onMissingValue` 显式位):当某一次 occurrence 的值缺席/长得像另一个 flag
+ * 时,这个共用叶提供两种可命名的处置——**调用方选,不由本叶替调用方决定**:
+ *   · `'invalidate'`(缺省,limitsWire/sandboxWire/scenarioWire 用这个):那次缺值让整个旗的最终
+ *     取值塌缩成「有旗、无值」(`{present:true}`,raw 缺席)——与这三处一直以来的 fail-LOUD 立场
+ *     一致:重复旗严格 LAST occurrence 定生死,哪怕最后一次是缺值也不会回落到更早的合法值。
+ *   · `'latch-previous'`(headlessPermissionModeWire 用这个):那次缺值被当作「这次 occurrence 没
+ *     提供新信息」,直接跳过,锁存(latch)住之前已经取到的合法值不动——这是收编前那份手写循环
+ *     的原语义(`if (typeof v === 'string' && !v.startsWith('-')) { mode = v }`,缺值分支从不碰
+ *     `mode`),收编成共用叶不能悄悄把它改造成 invalidate 语义。
+ * 两种策略都遵守同一条不变量:**从未出现过合法值** ⇒ 恒回 `{present:true}`(raw 缺席),从不
+ * 编造一个值;调用方各自决定「有旗无值」之后怎么办(fail-loud 用法提示,或落到下一车道)。
+ */
+/**
+ * Pull the LAST value of a `--name <v>` / `--name=<v>` flag out of an argv slice (everything
+ * before a bare `--` — positionals are never flags). Returns:
+ *   {present:false}                 — flag absent
+ *   {present:true, raw}             — flag present with a value token (possibly empty string)
+ *   {present:true, raw:undefined}   — flag present but no value was ever captured (see
+ *                                      `onMissingValue` for what "captured" means across repeats)
+ */
+export function lastFlagValue(argv, name, onMissingValue = 'invalidate') {
+    const eq = `${name}=`;
+    let present = false;
+    let raw;
+    let valueMissing = false;
+    for (let i = 0; i < argv.length; i++) {
+        const a = argv[i];
+        if (a === undefined)
+            continue;
+        if (a === '--')
+            break; // positionals — never flags
+        if (a === name) {
+            present = true;
+            const nxt = argv[i + 1];
+            if (nxt === undefined || nxt.startsWith('-')) {
+                // a value that LOOKS like another flag (or is plain missing) is not a value.
+                if (onMissingValue === 'latch-previous')
+                    continue; // keep whatever raw/valueMissing already hold
+                valueMissing = true;
+                raw = undefined;
+                continue;
+            }
+            valueMissing = false;
+            raw = nxt;
+            i++; // consume the value token
+        }
+        else if (a.startsWith(eq)) {
+            present = true;
+            valueMissing = false;
+            raw = a.slice(eq.length);
+        }
+    }
+    if (!present)
+        return { present: false };
+    if (valueMissing || raw === undefined)
+        return { present: true };
+    return { present: true, raw };
+}

package/dist/attachmentsWireCaps.d.ts

@@ -27,8 +27,9 @@
  * changes.
  */
 import { type EnvLike } from './hostEnv.js';
-/** The env key the shell reads. `off|0|false|none` ⇒ no stamp; `full|all` ⇒ all five producers;
- *  unset/anything else ⇒ the CC-parity default pair. */
+/** The env key the shell reads. An {@link envFlagOff} spelling(REF-CC-141 dup-02 单源:
+ *  `0`/`false`/`no`/`off`/`none`)⇒ no stamp; `full|all` ⇒ all five producers; unset/anything else
+ *  ⇒ the CC-parity default pair. */
 export declare const ATTACHMENTS_ENV: "SEMA_ATTACHMENTS";
 /** Mirror of core `TaskSpec.attachments` (types.ts:1139) — literal-true unions. */
 export interface AttachmentsSpec {

package/dist/attachmentsWireCaps.js

@@ -27,8 +27,10 @@
  * changes.
  */
 import { hostEnv } from './hostEnv.js';
-/** The env key the shell reads. `off|0|false|none` ⇒ no stamp; `full|all` ⇒ all five producers;
- *  unset/anything else ⇒ the CC-parity default pair. */
+import { envFlagOff } from './envFlag.js';
+/** The env key the shell reads. An {@link envFlagOff} spelling(REF-CC-141 dup-02 单源:
+ *  `0`/`false`/`no`/`off`/`none`)⇒ no stamp; `full|all` ⇒ all five producers; unset/anything else
+ *  ⇒ the CC-parity default pair. */
 export const ATTACHMENTS_ENV = 'SEMA_ATTACHMENTS';
 /**
  * ENV source → the `TaskRequest.attachments` stamp. Returns `undefined` (⇒ no field) on explicit
@@ -36,7 +38,7 @@ export const ATTACHMENTS_ENV = 'SEMA_ATTACHMENTS';
  */
 export function attachmentsForRequest(env = hostEnv()) {
     const raw = (env[ATTACHMENTS_ENV] ?? '').trim().toLowerCase();
-    if (raw === 'off' || raw === '0' || raw === 'false' || raw === 'none')
+    if (envFlagOff(raw))
         return undefined;
     if (raw === 'full' || raw === 'all') {
         return { todoReminder: true, changedFiles: true, planModeReminder: true, backgroundTasks: true, toolsDelta: true };

package/dist/classifierVerdictWire.d.ts

@@ -24,6 +24,14 @@
  * 🔴 fail-soft 铁律:识别不中一律静默走原路,绝不伤害事件流。
  * 🔴 UNTRUSTED:reason 为分类器(模型)产文,只渲染绝不回喂;通知行截断 ≤80(207 同款)。
  */
+/**
+ * 🟢 B8 ALLOW 清单登记(REF-CC-域词表-05,属主=client-core 规范重构轮,到期复议=core 改这句
+ * deny message 文案时或 2026-Q4 复审以先到者为准):文本匹配 + 非文本结构性合取前置
+ * (`ev.type==='tool_end' && ev.isError===true`,见 `classifierDenyFromToolEnd`)。同批同表的
+ * 另两处:`detachWire.ts` `DETACH_DURABLE_OFF_400_ANCHOR`(server 契约话)、
+ * `subagent/engineTaskHandleWire.ts` `STOP_CONFLICT_CODES`(SDK typed 缺席回落)——三处互指,
+ * 理由逐条写在各自站点。
+ */
 /** core hooks.js 分类器 deny message 的机器签名(逐字锚;lockstep:core 改文案这里必须跟)。 */
 export declare const CLASSIFIER_DENY_SIGNATURE = "auto-mode classifier blocked this call";
 export interface ClassifierDenyVerdict {

package/dist/classifierVerdictWire.js

@@ -24,6 +24,14 @@
  * 🔴 fail-soft 铁律:识别不中一律静默走原路,绝不伤害事件流。
  * 🔴 UNTRUSTED:reason 为分类器(模型)产文,只渲染绝不回喂;通知行截断 ≤80(207 同款)。
  */
+/**
+ * 🟢 B8 ALLOW 清单登记(REF-CC-域词表-05,属主=client-core 规范重构轮,到期复议=core 改这句
+ * deny message 文案时或 2026-Q4 复审以先到者为准):文本匹配 + 非文本结构性合取前置
+ * (`ev.type==='tool_end' && ev.isError===true`,见 `classifierDenyFromToolEnd`)。同批同表的
+ * 另两处:`detachWire.ts` `DETACH_DURABLE_OFF_400_ANCHOR`(server 契约话)、
+ * `subagent/engineTaskHandleWire.ts` `STOP_CONFLICT_CODES`(SDK typed 缺席回落)——三处互指,
+ * 理由逐条写在各自站点。
+ */
 /** core hooks.js 分类器 deny message 的机器签名(逐字锚;lockstep:core 改文案这里必须跟)。 */
 export const CLASSIFIER_DENY_SIGNATURE = 'auto-mode classifier blocked this call';
 /** 通知 reason 段截断(CC 207 L696763 同款 80 → 79+…)。 */

package/dist/cloudConfigWireCaps.d.ts

@@ -33,17 +33,28 @@ export type { McpServerSpec };
 type Rec = Record<string, unknown>;
 /** Env lookup shape (process.env or a test fixture). */
 export type { EnvLike };
+/** REF-CC-157(midband-05,fix-outright) 丢弃理由的四态之一——仿 skillsMissingBody 给 mcp 域补留痕:
+ *  一个打错字的 server name/字段此前会在用户毫无感知的情况下从 wire 上消失。 */
+export type CloudMcpDropReason = 'disabled' | 'missing-field' | 'unknown-transport' | 'capped';
+export interface CloudMcpDroppedServer {
+    /** 能取到就带上(未取到 name 的原始行——比如整条不是对象——留空,调用方仍能报「有 N 行没生效」)。 */
+    name?: string;
+    reason: CloudMcpDropReason;
+}
 export interface CloudMcpProjection {
     specs: McpServerSpec[];
     /** env NAMES referenced by envRefs/headerRefs that resolve to nothing in `env` (the ref is DROPPED —
      *  fail-closed on the value, loud in the caller's warning line). */
     missingEnv: string[];
+    /** REF-CC-157:每一条被丢弃的原始 mcp server 行 + 丢弃理由,登记进 CloudProjection 供宿主警示。 */
+    droppedServers: CloudMcpDroppedServer[];
 }
 /**
  * Project the registry's mcp domain (`config.mcp.servers`, registry-core McpServerSpec — the CENTER shape
  * with envRefs/headerRefs) → the SDK/core wire `McpServerSpec[]` (real env/header VALUES, resolved from the
  * shell env). Disabled servers are skipped; unknown transport kinds are skipped (never mis-mapped); the
- * result is capped at MCP_CAPS.items exactly like the local `.mcp.json` projection.
+ * result is capped at MCP_CAPS.items exactly like the local `.mcp.json` projection. Every skip is recorded
+ * in `droppedServers` (REF-CC-157) — nothing vanishes from the wire silently.
  */
 export declare function cloudMcpToSpecs(servers: unknown, env: EnvLike): CloudMcpProjection;
 /**
@@ -61,6 +72,17 @@ export declare function cloudSkillsToSpecs(manifestSkills: unknown, resolveBody:
  * semantics: no enabled models ⇒ env-catalog fallback).
  */
 export declare function cloudModelsToDoc(models: unknown): Rec | null;
+export interface CloudDroppedModel {
+    /** 能取到就带上;整条丢弃是因为二者都缺时,两个字段都可能不在。 */
+    id?: string;
+    name?: string;
+}
+/**
+ * REF-CC-157(midband-05,fix-outright):`config.models.models` 里被 `cloudModelsToDoc` 过滤掉的原始
+ * 条目(缺 `name` 或 `id`)——仿 `skillsMissingBody` 的形状,重扫同一份原始数组产出丢弃清单,让调用方
+ * 能警示用户「你的 model 配置有 N 行没生效」,而不是让一个打错字的字段静默从目录消失。
+ */
+export declare function cloudModelsDropped(models: unknown): CloudDroppedModel[];
 /** ENABLED model names in a models doc (banner/status display + "did the cloud catalog apply" checks). */
 export declare function cloudModelNames(doc: Rec | null): string[];
 /** `apiKeyEnv` NAMES referenced by enabled models that resolve to nothing in `env` — the engine child would
@@ -99,6 +121,11 @@ export interface CloudProjection {
     scope: string;
     /** Skills present in the manifest whose body could not be resolved (skipped on the wire). */
     skillsMissingBody: string[];
+    /** REF-CC-157(midband-05):mcp 域被丢弃的原始 server 行(disabled/missing-field/unknown-transport/
+     *  capped 四态之一)——仿 skillsMissingBody 的留痕机制,此前 mcp/models 两域零回执。 */
+    droppedMcpServers: CloudMcpDroppedServer[];
+    /** REF-CC-157:models 域被丢弃的原始条目(缺 name 或 id)。 */
+    droppedModels: CloudDroppedModel[];
     /** S3 execution-lane policy ([580]① / registry-core 0.8). Consumed by the sandbox policy-lock seam;
      *  ⚠️ client-enforced ADVISORY (P5=A) — the engine gate is service [580]. */
     execution: CloudExecutionProjection;