@sema-agent/client-core 0.77.1 → 0.78.0

package/dist/cloudConfigWireCaps.d.ts

@@ -1,92 +1,28 @@
-/**
- * ⇄ B2 批搬迁(2026-07-27,多端改造设计稿 §3 B2):cli src/sema/cloudConfigWireCaps.ts 搬入(依赖 mcpWireCaps/skillsWireCaps,同批)。
- */
-/**
- * src/sema/cloudConfigWireCaps.ts — PURE projections for the CLOUD CONFIG WIRE (P2): the registry's
- * GET /api/v1/effective body → the same wire shapes the LOCAL loaders produce, so flipping the
- * config-source switch swaps the SOURCE without changing a single downstream contract:
- *
- *   config.mcp.servers   → `McpServerSpec[]`   (== mcpWire loadMcpSpecs output → TaskRequest.mcpServers)
- *   config.skills.skills → `SkillSpec[]`       (== skillsWire loadSkillSpecs output → TaskRequest.skills;
- *                                               the v1 wire is a MANIFEST — content replaced by contentHash —
- *                                               so the body is injected via `resolveBody(contentHash)`)
- *   config.models        → config.d/models.json document (registry-core ModelsConfig IS the engine's
- *                                               FileConfigStore models.json shape — verbatim passthrough,
- *                                               written to a SHADOW config.d root, never the user's own)
- *   rosters              → names only (v1 thinnest seam: display + reference; the /api/v1/effective wire
- *                                               STRIPS rosters — registry-core resolve-roster `shipped()` —
- *                                               so the IO half pulls the domain raw when it can)
- *
- * SECRET BOUNDARY: the registry NEVER ships secret values — mcp transports carry `envRefs`/`headerRefs`
- * (target key → an ENV NAME) and models carry `apiKeyEnv`. The projection resolves env-NAME refs against the
- * SHELL's env (the engine child inherits it), and reports the names that resolve to nothing so callers can warn.
- *
- * Split from cloudConfigWire.ts (the IO half: token/fetch/cache/shadow-write) so this file is esbuild-bundleable
- * alone for the assertion suite — it imports only erased types + the sibling pure caps modules.
- */
 import type { SkillSpec } from '@sema-agent/sdk';
 import type { McpServerSpec } from './mcpWireCaps.js';
 import type { EnvLike } from './hostEnv.js';
-/** The SDK wire shape TaskRequest.mcpServers carries (the SDK barrel doesn't re-export McpServerSpec by
- *  name — derive it from TaskRequest so this stays the EXACT wire type, never a drifting copy). */
 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. Every skip is recorded
- * in `droppedServers` (REF-CC-157) — nothing vanishes from the wire silently.
- */
 export declare function cloudMcpToSpecs(servers: unknown, env: EnvLike): CloudMcpProjection;
-/**
- * Project the /api/v1/effective skills MANIFEST (content replaced by `contentHash` — registry-core
- * toSkillsManifest) → the capped wire `SkillSpec[]`. `resolveBody(contentHash)` supplies each body (the IO
- * half caches bodies by hash; null ⇒ the skill is SKIPPED — a nameless/bodyless SkillSpec is a 400). Same
- * caps + dedupe as the local projection (skillsWireCaps), so the wire is well-formed by construction.
- */
 export declare function cloudSkillsToSpecs(manifestSkills: unknown, resolveBody: (contentHash: string) => string | null): SkillSpec[];
-/**
- * The registry's models domain (registry-core ModelsConfig) IS the engine's `config.d/models.json` contract
- * (the same zod schema parses both — engine CONFIG_PROVIDER=local FileConfigStore lane), so the projection is
- * a VALIDATION-LITE PASSTHROUGH: keep exactly {models, roles, atModelAllowlist}, drop everything else, and
- * return null when there is no well-formed models array (caller then writes an empty catalog — engine
- * 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
- *  route those models with no key (a mid-session 401 the user can't diagnose); callers warn up front. */
 export declare function cloudModelMissingKeyEnv(doc: Rec | null, env: EnvLike): string[];
 export interface CloudSessionMirrorProjection {
     engineUrl: string;
@@ -95,43 +31,21 @@ export interface CloudSessionMirrorProjection {
 export interface CloudExecutionProjection {
     required: boolean;
     allowedLanes: string[];
-    /** registry-core 0.10.1 `execution.sessionMirror`(附B 单C):org 默认会话镜像目标两层配置。
-     *  null = 未下发/形状不对(INERT — 缺省零行为差;misshapen 绝不猜出一个镜像目标)。 */
     sessionMirror: CloudSessionMirrorProjection | null;
 }
-/** Project the registry's execution domain (registry-core 0.8 ExecutionPolicy — `{required, allowedLanes}`,
- *  allowedLanes = OPEN string vocab, [580]④; 0.10.1 adds `sessionMirror{engineUrl, required}` — additive).
- *  Defensive like every other projection: a missing/misshapen domain (an 0.7 registry) yields the schema
- *  defaults `{required:false, allowedLanes:["host"], sessionMirror:null}` — never a throw, never an
- *  accidental lock-ON, and never a guessed mirror target (engineUrl must be a non-empty string or the
- *  whole sessionMirror is dropped: a mirror carries session content + a Bearer, we don't improvise one). */
 export declare function cloudExecutionToPolicy(execution: unknown): CloudExecutionProjection;
-/** Roster names from a rosters domain value ({rosters:[{name,…}]}). The /api/v1/effective wire strips
- *  rosters (control-plane only), so the IO half feeds this from the raw scoped domain GET when readable. */
 export declare function cloudRosterNames(rostersValue: unknown): string[];
 export interface CloudProjection {
     mcp: McpServerSpec[];
     skills: SkillSpec[];
-    /** The shadow config.d/models.json document (null = registry shipped no well-formed models domain). */
     modelsDoc: Rec | null;
     modelNames: string[];
     rosterNames: string[];
-    /** env NAMES referenced by the cloud config (mcp refs + model apiKeyEnv) missing from the shell env. */
     missingEnv: string[];
     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;
 }
-/**
- * Project one /api/v1/effective BODY (fresh or cached — the fallback path MUST produce the identical shape)
- * into everything the shell consumes. Pure: bodies + env are injected.
- */
 export declare function projectEffectiveBody(body: unknown, skillBodies: Record<string, string>, env: EnvLike, rostersValue?: unknown): CloudProjection;

package/dist/cloudConfigWireCaps.js

@@ -3,13 +3,6 @@ import { toCappedSpec } from './skillsWireCaps.js';
 const asRec = (v) => (typeof v === 'object' && v !== null && !Array.isArray(v) ? v : undefined);
 const asArr = (v) => (Array.isArray(v) ? v : []);
 const asStr = (v) => (typeof v === 'string' && v.length > 0 ? v : undefined);
-/**
- * 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. Every skip is recorded
- * in `droppedServers` (REF-CC-157) — nothing vanishes from the wire silently.
- */
 export function cloudMcpToSpecs(servers, env) {
     const specs = [];
     const missingEnv = [];
@@ -20,8 +13,6 @@ export function cloudMcpToSpecs(servers, env) {
     for (const raw of asArr(servers)) {
         const s = asRec(raw);
         const name = s ? asStr(s.name) : undefined;
-        // cap first: everything past MCP_CAPS.items is dropped regardless of what it looks like — this is
-        // the reason it never got evaluated, so report it as such (not as a false 'missing-field').
         if (specs.length >= MCP_CAPS.items) {
             drop(name, 'capped');
             continue;
@@ -42,8 +33,6 @@ export function cloudMcpToSpecs(servers, env) {
                 drop(name, 'missing-field');
                 continue;
             }
-            // envRefs: target ENV key → ENV NAME holding the value (center never stores the secret). Resolve
-            // against the shell env — the engine child inherits it, so stdio spawn sees the same values.
             const envOut = {};
             for (const [target, ref] of Object.entries(asRec(t.envRefs) ?? {})) {
                 const refName = asStr(ref);
@@ -89,7 +78,7 @@ export function cloudMcpToSpecs(servers, env) {
             };
         }
         else {
-            drop(name, 'unknown-transport'); // unknown transport kind — skip, never mis-map (same posture as the local sse/ws skip)
+            drop(name, 'unknown-transport');
             continue;
         }
         const allowTools = asArr(s.allowTools).filter((a) => typeof a === 'string');
@@ -98,33 +87,11 @@ export function cloudMcpToSpecs(servers, env) {
             transport,
             ...(allowTools.length > 0 ? { allowTools } : {}),
             ...(s.elicitation === true ? { elicitation: true } : {}),
-            // ── 0.64.2 族扫(cli L-167① 的**同形存量第二处**)─────────────────────────────────────
-            // 病形与 `mcpWireCaps.mcpConfigToSpec` **逐字同一条**:这也是一次逐键白名单重建,而
-            // settings-schema 的 mcp 段上有**解析透明键**(`z.unknown()`;1.10.0 两员 `source` / `toolFaces`,2.0.0 同形〔2026-09-16 核〕)。
-            // 上游对 `toolFaces` 的成文是「三条腿(请求 / config-center / 本地 config.d)同一条规则」——
-            // 本函数正是 **config-center 那条腿落到请求面**的投影,只修本地那条 = 同形存量留一半:
-            // 用 center 下发配置的部署,运维声明的 per-tool 面照样在包边界被静默剥掉。
-            // 🔴 **原样过境,不校形**(理由见 `mcpWireCaps.ts` 模块顶注与 `McpConfigLike.toolFaces` 的注):
-            //    形的判决属引擎摄入侧;包在这里判一次形,判严了就把运维声明的保护静默吞掉。
-            // 🔴 **`source` 同样不在这条腿上**:它是部署面的分组标签,而本函数的产物是**请求面**
-            //    `McpServerSpec`(sdk 8.8.0 上没有这个键)。两条腿的记账逐字相同。
-            // 🔴 **两条腿刻意不共用一个函数,改由门同源**:跨文件共用要么给公面加一个没有外部消费者的
-            //    名字,要么把这一行抽成一个新叶子(闭包/单例账各加一笔)。这里的「规则」只有一行
-            //    (键在场 ⇒ 原样铸),真正会漂的是**哪些键算透明** —— 那张表的属主在上游,而
-            //    `run-additive-key-passthrough-test.mjs` G7 段是从**实装 schema** 取表、对**两条腿各对一次账**,
-            //    任一条漏一个键当天红。⇒ 单一真源在上游 + 机械门,不是两份各自为政的判断。
             ...(s.toolFaces !== undefined ? { toolFaces: s.toolFaces } : {}),
         });
     }
     return { specs, missingEnv: [...new Set(missingEnv)], droppedServers };
 }
-// ── skills: config.skills.skills (MANIFEST) + bodies → SkillSpec[] ───────────────────────────────────────
-/**
- * Project the /api/v1/effective skills MANIFEST (content replaced by `contentHash` — registry-core
- * toSkillsManifest) → the capped wire `SkillSpec[]`. `resolveBody(contentHash)` supplies each body (the IO
- * half caches bodies by hash; null ⇒ the skill is SKIPPED — a nameless/bodyless SkillSpec is a 400). Same
- * caps + dedupe as the local projection (skillsWireCaps), so the wire is well-formed by construction.
- */
 export function cloudSkillsToSpecs(manifestSkills, resolveBody) {
     const specs = [];
     const seen = new Set();
@@ -147,14 +114,6 @@ export function cloudSkillsToSpecs(manifestSkills, resolveBody) {
     }
     return specs;
 }
-// ── models: config.models → shadow config.d/models.json document ─────────────────────────────────────────
-/**
- * The registry's models domain (registry-core ModelsConfig) IS the engine's `config.d/models.json` contract
- * (the same zod schema parses both — engine CONFIG_PROVIDER=local FileConfigStore lane), so the projection is
- * a VALIDATION-LITE PASSTHROUGH: keep exactly {models, roles, atModelAllowlist}, drop everything else, and
- * return null when there is no well-formed models array (caller then writes an empty catalog — engine
- * semantics: no enabled models ⇒ env-catalog fallback).
- */
 export function cloudModelsToDoc(models) {
     const m = asRec(models);
     if (!m || !Array.isArray(m.models))
@@ -169,11 +128,6 @@ export function cloudModelsToDoc(models) {
         ...(Array.isArray(m.atModelAllowlist) ? { atModelAllowlist: m.atModelAllowlist } : {}),
     };
 }
-/**
- * REF-CC-157(midband-05,fix-outright):`config.models.models` 里被 `cloudModelsToDoc` 过滤掉的原始
- * 条目(缺 `name` 或 `id`)——仿 `skillsMissingBody` 的形状,重扫同一份原始数组产出丢弃清单,让调用方
- * 能警示用户「你的 model 配置有 N 行没生效」,而不是让一个打错字的字段静默从目录消失。
- */
 export function cloudModelsDropped(models) {
     const m = asRec(models);
     if (!m || !Array.isArray(m.models))
@@ -182,14 +136,13 @@ export function cloudModelsDropped(models) {
     for (const e of m.models) {
         const r = asRec(e);
         if (r && asStr(r.name) && asStr(r.id))
-            continue; // kept by cloudModelsToDoc — not dropped
+            continue;
         const id = r ? asStr(r.id) : undefined;
         const name = r ? asStr(r.name) : undefined;
         out.push({ ...(id ? { id } : {}), ...(name ? { name } : {}) });
     }
     return out;
 }
-/** ENABLED model names in a models doc (banner/status display + "did the cloud catalog apply" checks). */
 export function cloudModelNames(doc) {
     if (!doc)
         return [];
@@ -200,8 +153,6 @@ export function cloudModelNames(doc) {
     })
         .filter((n) => !!n);
 }
-/** `apiKeyEnv` NAMES referenced by enabled models that resolve to nothing in `env` — the engine child would
- *  route those models with no key (a mid-session 401 the user can't diagnose); callers warn up front. */
 export function cloudModelMissingKeyEnv(doc, env) {
     if (!doc)
         return [];
@@ -216,12 +167,6 @@ export function cloudModelMissingKeyEnv(doc, env) {
     }
     return [...out];
 }
-/** Project the registry's execution domain (registry-core 0.8 ExecutionPolicy — `{required, allowedLanes}`,
- *  allowedLanes = OPEN string vocab, [580]④; 0.10.1 adds `sessionMirror{engineUrl, required}` — additive).
- *  Defensive like every other projection: a missing/misshapen domain (an 0.7 registry) yields the schema
- *  defaults `{required:false, allowedLanes:["host"], sessionMirror:null}` — never a throw, never an
- *  accidental lock-ON, and never a guessed mirror target (engineUrl must be a non-empty string or the
- *  whole sessionMirror is dropped: a mirror carries session content + a Bearer, we don't improvise one). */
 export function cloudExecutionToPolicy(execution) {
     const e = asRec(execution);
     const lanes = asArr(e?.allowedLanes).filter((l) => typeof l === 'string' && l.length > 0);
@@ -230,23 +175,15 @@ export function cloudExecutionToPolicy(execution) {
     return {
         required: e?.required === true,
         allowedLanes: lanes.length > 0 ? lanes : ['host'],
-        // trailing-slash normalization matches engineTarget.normalizeEngineUrl (origin/no-op comparisons downstream)
         sessionMirror: mirrorUrl ? { engineUrl: mirrorUrl.replace(/\/+$/, ''), required: m?.required === true } : null,
     };
 }
-// ── rosters: v1 thinnest seam (names for display / model-order reference) ────────────────────────────────
-/** Roster names from a rosters domain value ({rosters:[{name,…}]}). The /api/v1/effective wire strips
- *  rosters (control-plane only), so the IO half feeds this from the raw scoped domain GET when readable. */
 export function cloudRosterNames(rostersValue) {
     const r = asRec(rostersValue);
     return asArr(r?.rosters)
         .map((e) => asStr(asRec(e)?.name))
         .filter((n) => !!n);
 }
-/**
- * Project one /api/v1/effective BODY (fresh or cached — the fallback path MUST produce the identical shape)
- * into everything the shell consumes. Pure: bodies + env are injected.
- */
 export function projectEffectiveBody(body, skillBodies, env, rostersValue) {
     const b = asRec(body) ?? {};
     const config = asRec(b.config) ?? {};

package/dist/compensations.d.ts

@@ -1,64 +1,12 @@
-/**
- * compensations.ts — **补偿层登记表**(B6 引入,设计稿 §2 补偿表 T1–T60 的落码侧账本)。
- *
- * ## 为什么要有这张表
- *
- * 搬迁把「壳替引擎补的那 60 件事」分成三种命运:整条进包 / **拆两半**(判定归库、执行留宿主)/
- * 留宿主。前两种里最危险的是**拆**:它天然是 [paired-mechanisms-must-share-premise] 的形状 ——
- * 库这半以为「宿主会做另一半」,宿主那半以为「库已经处理了」,两半各自都对、组合零结果。
- * 而且这种失效**不报错**,只是某个面悄悄空掉。
- *
- * ⇒ 与 `CHROME_ARMS` / `CLIENT_VERBS` 同一套纪律:**把义务做成数据**,让它可被断言,而不是
- * 散在注释里。pure 门对本表跑三条:①id 唯一 ②每条 `split` 的 `chromeArm` 必须真在
- * `CHROME_ARMS` 里 ③而且必须是 `required: true` —— 拆缝对面的义务若是「可选」,那这一刀就等于
- * 在多端上静默丢行为。
- *
- * ## 它不是什么
- *
- * 🔴 **不是 `ADAPTER_DIVERGENCES`**。那张表登记的是「adapt() 与 cli `sdkMessagesToCcEvents`
- * **行为不同**」的地方,差分守卫按它豁免比对。本表里的东西两侧**行为相同**(补偿是从 cli 原样
- * 搬过来的),登记的是「这条补偿为什么存在、上游到货后什么时候能删」。把回落臂写进 DIVERGENCES
- * 会让差分表撒谎 —— 那等于宣布两侧在这里不等价,而它们是等价的。
- *
- * ## 增长方式
- *
- * 每批只登记**这一批处置掉**的条目(B6 = P5 那八条)。不预先把 T1–T60 全填进来:填了但没落码的
- * 行只会让表看起来完整而实际没有判别力([probe-must-prove-it-speaks])。
- */
 import { type ChromeArmKind } from './seam.js';
 export interface CompensationRecord {
-    /** census 编号(设计稿 §2 补偿表 T1–T60)。 */
     id: string;
-    /** 它补的是什么(一句话;完整说明在落码处的注释里,那里是真源)。 */
     what: string;
-    /** `in-library` = 整条进包;`split` = 判定归库、执行留宿主。 */
     disposition: 'in-library' | 'split';
-    /** 库这一半落在哪(模块 / 函数)。 */
     libraryHalf: string;
-    /** 拆缝对面的宿主义务经由哪个 chrome 臂交付(`in-library` 恒 null)。 */
     chromeArm: ChromeArmKind | null;
-    /** 宿主那一半要做什么(`in-library` 恒 null)。 */
     hostHalf: string | null;
-    /**
-     * 退休条件 —— 上游到货后这条补偿可以删或简化;`null` = 它不是补偿而是**长期职责**
-     * (删了就是丢功能,不是清债)。
-     */
     retireOn: string | null;
 }
-/**
- * B6 P5 处置的八条(T32/T34/T47/T48/T49 整条进包 · T35/T36/T44 拆)+ **B7 完成事件族五条**
- * (T1/T2/T3/T25/T53,全部「只搬不删」—— P1-3 未到货)。
- *
- * 🔴 事实核对(B6 余项批实测,不是照抄设计稿):这八条的落码**都发生在 B4**
- * (`adapt.ts` A 层第 14 臂 `task_progress` 收官那一批),本批做的是**核实 + 登记 + 定案**,
- * 不是重新搬一遍。核实方式 = 逐条在 `adapt.ts` 找到落码点并配上断言,见 pure 门 B6 段。
- */
 export declare const MIGRATED_COMPENSATIONS: readonly CompensationRecord[];
-/**
- * 自检:每条 `split` 的宿主义务(若经 chrome 臂交付)必须真在 `CHROME_ARMS` 里,而且是
- * `required: true`。返回违规条目;**恒应为空数组**。
- *
- * 🔴 判据锚在「决定结果的量」上:拆缝对面若挂在一个 `required:false` 的臂上,宿主可以合法不实现,
- * 于是这一刀就是「库不做了、端也不做」——正是配对机制两半各自都对、组合零结果的那个形状。
- */
 export declare function compensationSplitViolations(): string[];

package/dist/compensations.js

@@ -1,39 +1,4 @@
-/**
- * compensations.ts — **补偿层登记表**(B6 引入,设计稿 §2 补偿表 T1–T60 的落码侧账本)。
- *
- * ## 为什么要有这张表
- *
- * 搬迁把「壳替引擎补的那 60 件事」分成三种命运:整条进包 / **拆两半**(判定归库、执行留宿主)/
- * 留宿主。前两种里最危险的是**拆**:它天然是 [paired-mechanisms-must-share-premise] 的形状 ——
- * 库这半以为「宿主会做另一半」,宿主那半以为「库已经处理了」,两半各自都对、组合零结果。
- * 而且这种失效**不报错**,只是某个面悄悄空掉。
- *
- * ⇒ 与 `CHROME_ARMS` / `CLIENT_VERBS` 同一套纪律:**把义务做成数据**,让它可被断言,而不是
- * 散在注释里。pure 门对本表跑三条:①id 唯一 ②每条 `split` 的 `chromeArm` 必须真在
- * `CHROME_ARMS` 里 ③而且必须是 `required: true` —— 拆缝对面的义务若是「可选」,那这一刀就等于
- * 在多端上静默丢行为。
- *
- * ## 它不是什么
- *
- * 🔴 **不是 `ADAPTER_DIVERGENCES`**。那张表登记的是「adapt() 与 cli `sdkMessagesToCcEvents`
- * **行为不同**」的地方,差分守卫按它豁免比对。本表里的东西两侧**行为相同**(补偿是从 cli 原样
- * 搬过来的),登记的是「这条补偿为什么存在、上游到货后什么时候能删」。把回落臂写进 DIVERGENCES
- * 会让差分表撒谎 —— 那等于宣布两侧在这里不等价,而它们是等价的。
- *
- * ## 增长方式
- *
- * 每批只登记**这一批处置掉**的条目(B6 = P5 那八条)。不预先把 T1–T60 全填进来:填了但没落码的
- * 行只会让表看起来完整而实际没有判别力([probe-must-prove-it-speaks])。
- */
 import { CHROME_ARMS } from './seam.js';
-/**
- * B6 P5 处置的八条(T32/T34/T47/T48/T49 整条进包 · T35/T36/T44 拆)+ **B7 完成事件族五条**
- * (T1/T2/T3/T25/T53,全部「只搬不删」—— P1-3 未到货)。
- *
- * 🔴 事实核对(B6 余项批实测,不是照抄设计稿):这八条的落码**都发生在 B4**
- * (`adapt.ts` A 层第 14 臂 `task_progress` 收官那一批),本批做的是**核实 + 登记 + 定案**,
- * 不是重新搬一遍。核实方式 = 逐条在 `adapt.ts` 找到落码点并配上断言,见 pure 门 B6 段。
- */
 export const MIGRATED_COMPENSATIONS = [
     {
         id: 'T32',
@@ -42,7 +7,6 @@ export const MIGRATED_COMPENSATIONS = [
         libraryHalf: 'adapt.ts bindTaskCard()',
         chromeArm: null,
         hostHalf: null,
-        // 见下方 P1-2 定案段:FIFO 那一臂**不删**,它是 tolerate-absent 的保护臂。
         retireOn: 'P1-2 到货且达标线 ≥ server 1.290(typed parentToolCallId 在每条 tick 上恒在)后,' +
             'FIFO 回落臂可删 —— 但只在**确认不再支持老引擎**时删,见 bindTaskCard 的 old-engine fallback 注释',
     },
@@ -53,7 +17,7 @@ export const MIGRATED_COMPENSATIONS = [
         libraryHalf: 'adapt.ts liveBoundPanelTasks + settlePanelTasks(cardId===null) 防御 sweep',
         chromeArm: null,
         hostHalf: null,
-        retireOn: null, // 长期职责:只要子代不发终态 tick,这个三态就得有
+        retireOn: null,
     },
     {
         id: 'T35',
@@ -80,7 +44,7 @@ export const MIGRATED_COMPENSATIONS = [
         libraryHalf: 'adapt.ts E 层 ② —— structured task/task-list 的判定 + 归一',
         chromeArm: 'task_ledger_sync',
         hostHalf: '按 toolUseId 幂等落盘(cli engineTaskListSync 的 fs 面;web 宿主落 BFF/本地存储)',
-        retireOn: null, // 长期职责:落盘位置本来就是端决策
+        retireOn: null,
     },
     {
         id: 'T47',
@@ -99,16 +63,8 @@ export const MIGRATED_COMPENSATIONS = [
         chromeArm: null,
         hostHalf: 'footer 行过滤 isFooterTaskRow/filterFooterTaskRows —— 含「丢弃所有无 parentId 顶层行」' +
             '这条**端专属决策**(主 run 头部行由端自己合成渲染),留 TUI',
-        // 🔴 这条的写者与读者**都在库内**(设计稿 §2.4.1-B 已裁):做成 chrome 臂会让「宿主没接线 ⇒
-        //    Set 恒空 ⇒ 判据④ 静默失效」复活,所以 chromeArm 恒 null,拆的是**过滤策略**不是台账。
         retireOn: 'P1-2 到货后 fleet 行自带 parentToolCallId ⇒ 双生行不需要按尾段查',
     },
-    // ── B7 处置的五条(完成事件族 T1/T2/T3/T25/T53)──────────────────────────────────────────────
-    // 🔴 **P1-3(完成事件单一权威)未到货 ⇒ 这五条全是「只搬不删」**:四道去重原样保留。
-    //    每条的 `retireOn` 写的就是「P1-3 到货后**降哪一道**」——退役条件必须是**可执行的判据**,
-    //    不是「以后再说」。设计稿 §3 B7:「P1-3 到货 ⇒ 四道去重降到一道 + 删 XML 反解回植」。
-    //    ⚠️ 「降到一道」不等于「删三道」:下面 T53 行逐道写清了哪一道是权威、另外三道各防什么,
-    //    否则到货那天没人分得清哪些能删([anchor-on-the-deciding-quantity]:先定这个量门控什么)。
     {
         id: 'T1',
         what: '三个跨 turn 台账(渲染去重 / 跨通道记账 / 完成卡已入队)—— completion inbox 是 at-least-once,' +
@@ -118,7 +74,6 @@ export const MIGRATED_COMPENSATIONS = [
             '适配器实例的 renderedNotifications;序列化口 exportLedger/importLedger',
         chromeArm: null,
         hostHalf: null,
-        // 长期职责:只要投递是 at-least-once,客户端就得有去重记忆。P1-3 换的是**键**不是台账。
         retireOn: null,
     },
     {
@@ -157,15 +112,6 @@ export const MIGRATED_COMPENSATIONS = [
         id: 'T53',
         what: '同一次完成四通道扇出 ⇒ 四道去重(设计稿列为最贵 #4)',
         disposition: 'in-library',
-        // 四道各自防什么(P1-3 到货那天要按这个清单逐道判,别一刀切):
-        //  ① renderedNotifications(键=T2)—— 防**同一帧重放**(durable re-attach / at-least-once 重投)。
-        //     ⇒ P1-3 后这一道**留**,只是键换成 completionId。这是「降到一道」里的那一道。
-        //  ② isWorkflowCompletionCardEnqueued —— 防「Path B 已入队的完成卡」与「Path A 推送帧」双投。
-        //     ⇒ P1-3 后可删:两条通道带同一 completionId,①就能盖住。
-        //  ③ isEngineWorkflowNotified(workflow_complete 臂首行)—— 防补发通道在引擎已 server-side
-        //     inject 之后再喂一遍。⇒ P1-3 后可删,同②。
-        //  ④ dropQueuedNotificationsForRun —— 回声到达时把还躺在队列里的同 run 条目捞回来。
-        //     ⇒ **不是去重是撤单**,P1-3 后仍需要(队列里那条已经排上了,得有人撤)。
         libraryHalf: 'adapt.ts task_notification / workflow_complete 两臂的四道门(逐道说明见本行上方注释)',
         chromeArm: null,
         hostHalf: null,
@@ -182,13 +128,6 @@ export const MIGRATED_COMPENSATIONS = [
         retireOn: 'P1-2 到货后 content 帧自带 taskId ⇒ alias 学习整条可删',
     },
 ];
-/**
- * 自检:每条 `split` 的宿主义务(若经 chrome 臂交付)必须真在 `CHROME_ARMS` 里,而且是
- * `required: true`。返回违规条目;**恒应为空数组**。
- *
- * 🔴 判据锚在「决定结果的量」上:拆缝对面若挂在一个 `required:false` 的臂上,宿主可以合法不实现,
- * 于是这一刀就是「库不做了、端也不做」——正是配对机制两半各自都对、组合零结果的那个形状。
- */
 export function compensationSplitViolations() {
     const byKind = new Map(CHROME_ARMS.map(a => [a.kind, a]));
     const bad = [];