@sema-agent/client-core 0.11.8 → 0.11.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -23,7 +23,9 @@ Renamed from **`@sema-agent/wire-cc-adapter`** (0.1.x, deprecated — see *Migra
23
23
 
24
24
  ## Scope
25
25
 
26
- - **Today (0.10.0)** — the adapter seam, the whole `adapt()` pipeline (all 14 A-layer arms plus the
26
+ **Version:** 0.11.9
27
+
28
+ - **Today** — the adapter seam, the whole `adapt()` pipeline (all 14 A-layer arms plus the
27
29
  B/D/E tool-card layers), the notification/caps/model families, the adapter kernel (stream driver
28
30
  + downstream projectors), the request-shaping surface **for both lanes** (interactive and the
29
31
  headless `-p` print lane), the fleet/panel projections and the subagent wire family, the workflow
@@ -39,9 +41,22 @@ Renamed from **`@sema-agent/wire-cc-adapter`** (0.1.x, deprecated — see *Migra
39
41
 
40
42
  ## Dependencies
41
43
 
42
- - **Zero runtime dependencies** (`"dependencies": {}`), `sideEffects: false`.
43
- - **Peer / type-only**: `@sema-agent/agent-types` owns the CC session vocabulary (today's only
44
- import `SDKMessage`, type-only), `@sema-agent/sdk` owns the wire contract.
44
+ - **Runtime dependencies:** `diff` (jsdiff 9 — zero transitive deps, pure JS, browser-safe). It is
45
+ the T20 client-side hunk computation; core ruled that hunks belong to the client, so keeping it
46
+ out of this package would mean three re-implementations (TUI / web / desktop). The portability
47
+ guard pins the runtime dependency set with an *equality* check, so this list cannot drift.
48
+ `sideEffects: false`.
49
+ - **Peers:**
50
+ - `@sema-agent/agent-types` — the CC session vocabulary (`SDKMessage` and friends). **Type-only**:
51
+ it ships no runtime code at all.
52
+ - `@sema-agent/sdk` — the wire contract. **Value-level, not type-only**: `AgentClient`,
53
+ `SseIdleError`, `probeHealth`, `APIError` and `TaskStopConflictError` are imported as values in
54
+ five modules, and the browser bundle really bundles the SDK through (the portability guard would
55
+ exit 3 rather than quietly mark it external).
56
+ - The declared floor is `>=0.1.9`, and it is *witnessed*: the guard checks that an actually
57
+ installed SDK at that line still exports every value-level symbol this package imports and still
58
+ declares `TaskStats.costMicroUsd` (the key `costOrNull` reads). A floor nobody ever ran is a
59
+ promise, not a contract.
45
60
  - The direction is constitutional: **sdk (wire) + agent-types (vocabulary) → this package**,
46
61
  and neither depends back.
47
62
 
@@ -181,13 +196,30 @@ both sides — what it records is why a compensation exists and when it can be d
181
196
 
182
197
  ```bash
183
198
  npm install
184
- node scripts/run-client-core-pure-test.mjs # 1058 consumer-view checks (22 + 140 + 208 + 59 + 101 + 96 + 241 + 163 + 28); no CLI tree needed
185
- node scripts/run-client-core-portability-test.mjs # 39 checks: kernel + A-layer + index closures, browser bundle
186
- node scripts/run-client-core-diff-test.mjs # 1397 checks: differential + replay-id + ledger
199
+ npm test # = node scripts/run-client-core-all-gates.mjs runs every suite below
187
200
  ```
188
201
 
202
+ `npm test` is a **collecting** runner, not a `&&` chain: a suite that exits 3 (SKIP, its material is
203
+ absent) does not short-circuit the ones after it, and the runner prints the three-part verdict
204
+ itself (FAILED names + skipped names + arithmetic reconciliation). All-SKIP reports exit 3, never 0.
205
+
206
+ | Suite | What it guards |
207
+ |---|---|
208
+ | `scripts/run-client-core-pure-test.mjs` | Consumer-view behaviour of every moved-in module; segment floors (B1–B8 + C) that only move up |
209
+ | `scripts/run-client-core-portability-test.mjs` | Kernel / A-layer / index import closures, the runtime-dependency equality gate, barrel reachability, and a real esbuild `--platform=browser` bundle |
210
+ | `scripts/run-client-core-diff-test.mjs` | Differential equivalence against the CLI reference bridge + replay-id invariant + ledger round-trip |
211
+ | `scripts/run-seat-contract-keys-test.mjs` | The seat IPC contract: verb list ↔ SPEC ↔ types, element-wise |
212
+ | `scripts/run-approval-frame-keys-test.mjs` | The tool-approval frame key mirror, element-wise against the SDK's runtime anchor |
213
+ | `scripts/run-print-bash-iserror-test.mjs` | The print lane's Bash `is_error` authority (structured over regex) |
214
+ | `scripts/run-sdk-floor-test.mjs` | The SDK version floor — and, more to the point, that the *installed* type declarations still carry the keys this package reads |
215
+ | `scripts/run-engine-vocab-floor-test.mjs` | Engine-mirrored vocabularies (structured card whitelist, self-reported tool face, control verbs, recogniser sets) against the *installed* `@sema-agent/core` |
216
+ | `scripts/run-public-surface-test.mjs` | The outward promises: the npm export surface baseline, the peer floor witness, and this README's claims |
217
+
189
218
  Each suite carries a floor that only moves up — a refactor that stops executing a group of
190
- assertions is a failure, not a quieter pass.
219
+ assertions is a failure, not a quieter pass. Guards anchor on the **installed artefact's content**
220
+ rather than on a version number, a directory name or a count: a version string can lie, a type
221
+ declaration cannot, and a count has no discriminating power when the content changes but the
222
+ cardinality does not.
191
223
 
192
224
  The portability guard walks the value-level import closure of the stream driver (asserting zero
193
225
  Node builtins, zero react, zero shell debug edge, closure size under its ceiling) and then really
@@ -19,15 +19,10 @@
19
19
  * is a ThinkingLevel (off|minimal|low|medium|high|xhigh|max); `auto` (let engine default), `ultracode` (a
20
20
  * separate mode, future slice), numeric and unset all OMIT — the engine then uses its own default.
21
21
  */
22
- const REASONING_EFFORTS = new Set([
23
- 'off',
24
- 'minimal',
25
- 'low',
26
- 'medium',
27
- 'high',
28
- 'xhigh',
29
- 'max',
30
- ]);
22
+ const REASONING_EFFORT_TUPLE = ['off', 'minimal', 'low', 'medium', 'high', 'xhigh', 'max'];
23
+ const _effortPins = [true, true];
24
+ void _effortPins;
25
+ const REASONING_EFFORTS = new Set(REASONING_EFFORT_TUPLE);
31
26
  /**
32
27
  * Project a picked `EffortValue` (string level | number | undefined) → the wire `reasoningEffort`, or
33
28
  * undefined to OMIT. Returns the value verbatim iff it is a core ThinkingLevel; everything else (auto,
@@ -130,6 +130,14 @@ export declare function deriveAgentLabel(agentType: string | undefined, agentNam
130
130
  *
131
131
  * 集合 = core `RESERVED_AGENT_NAMES`(subagent.ts)的 CC-parity PascalCase 形 + goal 模式的
132
132
  * `DeclareDone`。引擎 ≥ core 1.176 经 `canonicalToolName` 发 PascalCase。
133
+ *
134
+ * 🔴 [2006] A-CC-4(2026-07-29):此表此前**零门看守**,而 core 早已把子代委派工具改名成
135
+ * `Agent`(`DEFAULT_SUBAGENT_TOOL_NAME`;`Task`/`Fork` 退成 `OLD_TO_NEW` 旧名,`Fork` 还进了
136
+ * `TOMBSTONED_TOOLS`)。表里缺 `Agent` ⇒ 今天绝大多数 fleet 行的 description(引擎发的正是
137
+ * canonical 形 `Agent`)**压制不掉**,控制面动词照样泄漏进行正文 —— 正是本函数存在的理由被
138
+ * 静默架空。看守从此是 engine-vocab 门对**实装 core** `RESERVED_AGENT_NAMES` 的等值门;
139
+ * `Fork` 作为**登记旧名**保留(老引擎仍可能发;压制集多一个只多压制、不误伤真工具),
140
+ * 而"登记"本身要过门 —— 登记项必须是 core 认过的改名/墓碑词。
133
141
  */
134
142
  export declare const CONTROL_TOOL_VERBS: ReadonlySet<string>;
135
143
  /** 行的活动正文:控制面动词 ⇒ 空(187 从不显示它),否则原样。 */
@@ -82,8 +82,17 @@ export function deriveAgentLabel(agentType, agentName, name, id) {
82
82
  *
83
83
  * 集合 = core `RESERVED_AGENT_NAMES`(subagent.ts)的 CC-parity PascalCase 形 + goal 模式的
84
84
  * `DeclareDone`。引擎 ≥ core 1.176 经 `canonicalToolName` 发 PascalCase。
85
+ *
86
+ * 🔴 [2006] A-CC-4(2026-07-29):此表此前**零门看守**,而 core 早已把子代委派工具改名成
87
+ * `Agent`(`DEFAULT_SUBAGENT_TOOL_NAME`;`Task`/`Fork` 退成 `OLD_TO_NEW` 旧名,`Fork` 还进了
88
+ * `TOMBSTONED_TOOLS`)。表里缺 `Agent` ⇒ 今天绝大多数 fleet 行的 description(引擎发的正是
89
+ * canonical 形 `Agent`)**压制不掉**,控制面动词照样泄漏进行正文 —— 正是本函数存在的理由被
90
+ * 静默架空。看守从此是 engine-vocab 门对**实装 core** `RESERVED_AGENT_NAMES` 的等值门;
91
+ * `Fork` 作为**登记旧名**保留(老引擎仍可能发;压制集多一个只多压制、不误伤真工具),
92
+ * 而"登记"本身要过门 —— 登记项必须是 core 认过的改名/墓碑词。
85
93
  */
86
94
  export const CONTROL_TOOL_VERBS = new Set([
95
+ 'Agent',
87
96
  'Task',
88
97
  'Fork',
89
98
  'StructuredOutput',
@@ -30,8 +30,6 @@ import { type PermissionMode, type PermissionModeField } from './permissionWireC
30
30
  import { type EnvLike } from './hostEnv.js';
31
31
  /** 部署旋钮 env 键名(settings.json env 块 → 1a-envseed → process.env 同车道)。 */
32
32
  export declare const HEADLESS_PERMISSION_MODE_ENV = "SEMA_HEADLESS_PERMISSION_MODE";
33
- /** wire 词表(permissionWireCaps.PermissionMode 的运行时镜像;大小写敏感——与 CC flag choices 一致)。
34
- * 'auto'(分类器批3,[907]):server ≥1.209 五模式表认;老 server coerce 未知词 → "default" 只紧不松。 */
35
33
  export declare const HEADLESS_PERMISSION_WIRE_MODES: readonly PermissionMode[];
36
34
  export type HeadlessPermissionResolution = {
37
35
  /** 直接展开进 TaskRequest 的字段({} = 不 stamp,现状 absent-mode)。 */
@@ -32,13 +32,10 @@ import { hostEnv } from './hostEnv.js';
32
32
  export const HEADLESS_PERMISSION_MODE_ENV = 'SEMA_HEADLESS_PERMISSION_MODE';
33
33
  /** wire 词表(permissionWireCaps.PermissionMode 的运行时镜像;大小写敏感——与 CC flag choices 一致)。
34
34
  * 'auto'(分类器批3,[907]):server ≥1.209 五模式表认;老 server coerce 未知词 → "default" 只紧不松。 */
35
- export const HEADLESS_PERMISSION_WIRE_MODES = [
36
- 'default',
37
- 'plan',
38
- 'acceptEdits',
39
- 'bypassPermissions',
40
- 'auto',
41
- ];
35
+ const HEADLESS_PERMISSION_WIRE_MODE_TUPLE = ['default', 'plan', 'acceptEdits', 'bypassPermissions', 'auto'];
36
+ const _headlessPermissionModePins = [true, true];
37
+ void _headlessPermissionModePins;
38
+ export const HEADLESS_PERMISSION_WIRE_MODES = HEADLESS_PERMISSION_WIRE_MODE_TUPLE;
42
39
  /**
43
40
  * argv 里的 `--permission-mode <v>` / `--permission-mode=<v>`(后者/后出现者赢,commander 同语义)与
44
41
  * `--dangerously-skip-permissions`(= bypassPermissions;`--permission-mode` 在场时让位)。
@@ -255,23 +255,10 @@ export interface StartSessionOptions {
255
255
  * ComposerMode 加一档而宿主闭集门不认的那天,红在编译期而不是用户提交那一刻。
256
256
  */
257
257
  export type PermissionModeIntent = "default" | "plan" | "acceptEdits" | "bypassPermissions" | "auto";
258
- /** The closed set the inbound gate checks. CLOSED deliberately, unlike `outcome` above: this word
259
- * ORIGINATES in our own renderer and goes OUT to a wire that 400s on anything else, so an unknown
260
- * value is a local bug we want reported at the door — not an unknown future wire word we must
261
- * tolerate. (The direction of travel is what decides open vs closed, not the field's shape.) */
262
258
  export declare const PERMISSION_MODE_INTENTS: readonly PermissionModeIntent[];
263
259
  /** Per-task attachment cap — the server's own limit (`attachmentIds` > 16 ⇒ 400). Gated here so the
264
260
  * seat gets a precise local error instead of a wire 400 halfway through a turn. */
265
261
  export declare const ATTACHMENT_IDS_PER_TASK_CAP = 16;
266
- /** The per-turn `reasoningEffort` accept-set — core's ThinkingLevel tiers, re-exported from the
267
- * package's own wire projection (`effortWire.ReasoningEffort`) rather than re-typed here.
268
- *
269
- * CLOSED for the same reason `PERMISSION_MODE_INTENTS` is: the word ORIGINATES in our own composer
270
- * and travels OUT to a wire that 400s (fail-loud) on an unknown tier — so an unknown value is a
271
- * local bug we want reported at the seat's door, not a future wire word to tolerate. `ultracode` is
272
- * deliberately NOT a tier here: in CC it is a standalone `settings.ultracode` preset boolean that
273
- * COEXISTS with `xhigh` (see `SeatTurnSettings`), and folding it into this axis is exactly how the
274
- * orchestration axis gets eaten by the reasoning axis. */
275
262
  export declare const SEAT_REASONING_EFFORTS: readonly ReasoningEffort[];
276
263
  /** The `settings` sub-object a seat turn may carry. A CLOSED set with its own name list + pin,
277
264
  * exactly like the top-level request: `SEND_MESSAGE_REQUEST_KEYS` checks `keyof SendMessageRequest`
@@ -118,13 +118,14 @@ export const CHROME_EVENT_KINDS = [
118
118
  * ORIGINATES in our own renderer and goes OUT to a wire that 400s on anything else, so an unknown
119
119
  * value is a local bug we want reported at the door — not an unknown future wire word we must
120
120
  * tolerate. (The direction of travel is what decides open vs closed, not the field's shape.) */
121
- export const PERMISSION_MODE_INTENTS = [
121
+ const PERMISSION_MODE_INTENT_TUPLE = [
122
122
  "default",
123
123
  "plan",
124
124
  "acceptEdits",
125
125
  "bypassPermissions",
126
126
  "auto",
127
127
  ];
128
+ export const PERMISSION_MODE_INTENTS = PERMISSION_MODE_INTENT_TUPLE;
128
129
  /** Per-task attachment cap — the server's own limit (`attachmentIds` > 16 ⇒ 400). Gated here so the
129
130
  * seat gets a precise local error instead of a wire 400 halfway through a turn. */
130
131
  export const ATTACHMENT_IDS_PER_TASK_CAP = 16;
@@ -137,7 +138,7 @@ export const ATTACHMENT_IDS_PER_TASK_CAP = 16;
137
138
  * deliberately NOT a tier here: in CC it is a standalone `settings.ultracode` preset boolean that
138
139
  * COEXISTS with `xhigh` (see `SeatTurnSettings`), and folding it into this axis is exactly how the
139
140
  * orchestration axis gets eaten by the reasoning axis. */
140
- export const SEAT_REASONING_EFFORTS = [
141
+ const SEAT_REASONING_EFFORT_TUPLE = [
141
142
  "off",
142
143
  "minimal",
143
144
  "low",
@@ -146,6 +147,7 @@ export const SEAT_REASONING_EFFORTS = [
146
147
  "xhigh",
147
148
  "max",
148
149
  ];
150
+ export const SEAT_REASONING_EFFORTS = SEAT_REASONING_EFFORT_TUPLE;
149
151
  export const SEAT_TURN_SETTINGS_KEYS = ["ultracode"];
150
152
  // ───────────────────────────── validators (CC dual-gate posture) ─────────────────────────────
151
153
  export function isLocalSessionRecord(s) {
@@ -423,5 +425,6 @@ const _seatContractPins = [
423
425
  true, true, true, true, true, true, true, true, true,
424
426
  true, true, true, true, true, true, true, true,
425
427
  true, true,
428
+ true, true, true, true,
426
429
  ];
427
430
  void _seatContractPins;
@@ -46,6 +46,11 @@ export const STRUCTURED_DETAIL_TYPES = new Set([
46
46
  'update',
47
47
  'bash',
48
48
  'notebook-edit',
49
+ // 🔴 [2006] A-CC-3(2026-07-29):`notebook` = Read 读 .ipynb 的投影卡(core RB-227,filePath +
50
+ // projected cells)。此前本表漏它而 core 照发 `tool_end.structured` ⇒ `structuredDetailType()`
51
+ // 返 undefined ⇒ 那张卡退回**正则解模型面文本**([assert-absence-check-fallback-layers] 同族)。
52
+ // 看守从「size===30 计数钉」换成对**实装 core** `CC_DETAIL_TYPES` 的等值门(engine-vocab 门)。
53
+ 'notebook',
49
54
  'text',
50
55
  'grep',
51
56
  'glob',
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sema-agent/client-core",
3
- "version": "0.11.8",
3
+ "version": "0.11.9",
4
4
  "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).",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -20,6 +20,7 @@
20
20
  "sideEffects": false,
21
21
  "scripts": {
22
22
  "build": "tsc -p tsconfig.json",
23
+ "prepare": "npm run build",
23
24
  "test": "node scripts/run-client-core-all-gates.mjs"
24
25
  },
25
26
  "dependencies": {
@@ -27,7 +28,7 @@
27
28
  },
28
29
  "peerDependencies": {
29
30
  "@sema-agent/agent-types": ">=0.2.0",
30
- "@sema-agent/sdk": ">=0.1.0"
31
+ "@sema-agent/sdk": ">=0.1.9"
31
32
  },
32
33
  "devDependencies": {
33
34
  "@sema-agent/agent-types": "^0.2.0",