@sema-agent/client-core 0.2.0 → 0.4.0

package/dist/ultracodeWireCaps.js

@@ -0,0 +1,159 @@
+/**
+ * ⇄ B2 批搬迁(2026-07-27,多端改造设计稿 §3 B2):cli src/sema/ultracodeWireCaps.ts 逐字搬入(零依赖;🔴 模块级 ultracodePreset 是 sticky 单实例态,写口 setUltracodePreset 与读口 ultracodeForWire 必须同实例)。
+ */
+/**
+ * src/sema/ultracodeWireCaps.ts — the shell's TWO opt-in sources for the CC-parity `settings.ultracode` PRESET,
+ * projected onto `TaskRequest.settings.ultracode` (a typed boolean the SERVICE — ai-agent-service 1.48.0 — reads
+ * and EXPANDS to `thinking:"max"` + `selfOrchestration:true`; both core's existing orthogonal axes, fail-closed
+ * gates unchanged). design/111 (core/search AI 2026-06-30): ultracode is a STANDALONE settings boolean folding
+ * "max thinking × workflow orchestration", surfaced in sema as the top notch of the `/effort` dial.
+ *
+ * Two sources, ONE structured-spec output (`settings.ultracode:true` — never prompt text):
+ *
+ *  ① L2 dial preset (STICKY): the `/effort ultracode` pick. The effort dial COERCES the reasoning axis to `xhigh`
+ *     (overrides/effort.tsx executeEffortSema — "ultracode runs at xhigh effort"), which would LOSE the
+ *     orchestration axis. So the dial separately latches this module-level preset: ON when `ultracode` is picked,
+ *     OFF when any OTHER effort level is picked (a sticky session setting, like CC's settings.ultracode boolean).
+ *
+ *  ② L3 keyword (PER-TURN): a client-side scan of the REAL human turn input for the literal word "ultracode".
+ *     🔴 RED LINE (design/111 L3, the ONLY injection risk): scan ONLY the human's current-turn submission, BEFORE
+ *     any untrusted content (tool results / file reads / web / subagent / MCP) is concatenated. NEVER scan the
+ *     assembled prompt server-side — a malicious file containing "ultracode" would be a privilege-escalation
+ *     injection. The keyword is a UX convenience switch, NOT a security decision point: privilege STILL passes the
+ *     service's fail-closed per-principal `allowWorkflows` gate (core deliberately refuses prompt scanning,
+ *     prepare-task.ts:1612 — that boundary is correct). The output is a STRUCTURED spec (the boolean), never
+ *     injected prompt text.
+ *
+ * Both sources are OR'd live-side by `toTaskRequest`; the SAME `SEMA_LIVE_BASEURL` gate the other capability wires
+ * use keeps the mock request shape unchanged (the stamp IS the opt-in; absent ⇒ the engine never expands ultracode).
+ *
+ * The PRESET state is module-level (mirrors seamQuery's seam* injectors): the dial (a React override) latches it,
+ * the seam reads it. The KEYWORD scan is a PURE function (caller passes the human input) so it bundles + unit-tests
+ * without React/AppState.
+ */
+import { hostEnv } from './hostEnv.js';
+/** STICKY L2 preset: latched ON by the `/effort ultracode` dial pick, OFF by any other effort pick. Module-level
+ *  (one shell process = one session) — the same single-namespace assumption seamQuery's session state uses. */
+let ultracodePreset = false;
+/** Latch the dial preset. `effort.tsx` calls this whenever an effort level is APPLIED: `true` for the `ultracode`
+ *  notch, `false` for every other level (so switching the dial OFF ultracode clears the workflow-orchestration axis
+ *  while the reasoning axis follows the picked level). */
+export function setUltracodePreset(on) {
+    ultracodePreset = on === true;
+}
+/** Read the sticky dial preset (the L2 source). */
+export function getUltracodePreset() {
+    return ultracodePreset;
+}
+/** Test/boot reset — clears the latched preset (e.g. a fresh session). */
+export function _resetUltracodePreset() {
+    ultracodePreset = false;
+}
+/** Word-boundary, case-insensitive scan for the literal keyword. A bare mention ("ultracode") anywhere in the
+ *  human's own turn text counts (CC-style UX toggle); the server's `allowWorkflows` gate is the real guard, so a
+ *  false-positive (the user discussing the word) only requests the preset — it cannot escalate past the gate. */
+const ULTRACODE_KEYWORD = /\bultracode\b/i;
+/**
+ * L3 keyword source: `true` iff the REAL human turn input contains the "ultracode" keyword, else `undefined`.
+ * 🔴 The caller MUST pass ONLY the human's current-turn submission (seamQuery's `objective`, derived from the
+ * projectable user message) — NOT any assembled/untrusted content. Returns `true | undefined` (never `false`) to
+ * mirror the strict additive-stamp discipline of the other wire caps (a stamped `false` would needlessly change
+ * the default request shape).
+ */
+export function ultracodeFromInput(humanInput) {
+    return typeof humanInput === 'string' && ULTRACODE_KEYWORD.test(humanInput) ? true : undefined;
+}
+/**
+ * Combine the two sources into the structured spec the seam stamps. `true` when EITHER the sticky dial preset is on
+ * OR the human's current-turn input contains the keyword; otherwise `undefined` (⇒ no stamp ⇒ default behaviour).
+ * Returns `true | undefined` so the seam can spread `...(ultracode ? { ultracode } : {})` without changing the
+ * default request shape. The CALLER gates this to LIVE mode (mock parity).
+ */
+export function ultracodeForRequest(humanInput) {
+    return getUltracodePreset() || ultracodeFromInput(humanInput) ? true : undefined;
+}
+/** [1044]②裁 B 激活源 a(clay 拍):用户当轮说 "workflow"(词边界、大小写不敏感)⇒ 该 turn 激活
+ *  Workflow 暴露。与 ultracode 线同一注入红线:只扫真人当轮输入(objective),绝不扫组装后内容。
+ *  消费接线=[1052]① 收官形(workflowDeferForRequest,core 1.314 deferTools 首班到货后点亮)。
+ *  [1486] 词表扩(2026-07-21,「启动 Agent Team 走成三 fork」白盒定谳):多 agent 语义族也激活——
+ *  run_workflow 描述里的路由映射句(multi-agent orchestration…fan out agents)defer 后模型读不到,
+ *  「agent team/multi-agent/swarm/多agent/编排」类输入落进可见工具面的理性变通(三 fork)。命中即
+ *  当轮全量上 wire(翻转只发生在激活当轮,前缀缓存语义不变)。终态=Agent Team 真入口(案A,
+ *  [1484]/[1485])落地后此词有真归宿,本词表是过渡补丁。 */
+const WORKFLOW_KEYWORD = /\bworkflows?\b|\bagent[ -]?teams?\b|\bmulti[ -]?agent\b|\bswarms?\b|多\s?agent|多智能体|编排/i;
+export function workflowFromInput(humanInput) {
+    return typeof humanInput === 'string' && WORKFLOW_KEYWORD.test(humanInput) ? true : undefined;
+}
+/** Env escape hatch for the deferred-Workflow factory default: `SEMA_WORKFLOW_DEFER=0/false/no/off` restores the
+ *  pre-[1052] always-exposed shape (schema bytes back in the prefix). Anything else (incl. unset) = defer ON. */
+export const WORKFLOW_DEFER_ENV = 'SEMA_WORKFLOW_DEFER';
+function deferOptedOut(env) {
+    const raw = env[WORKFLOW_DEFER_ENV];
+    const s = typeof raw === 'string' ? raw.trim().toLowerCase() : '';
+    return s === '0' || s === 'false' || s === 'no' || s === 'off';
+}
+/**
+ * [1052]① 收官形(clay 裁 B 的 core deferred 机制件,cli 接线半场):Workflow「全局默认开但不暴露」——
+ * 未命中激活源的 TaskRequest 带 `deferTools:["Workflow"]`(core 1.314 对已挂载工具做 design/36 延迟披露:
+ * 占位符上 wire、schema 字节撤出缓存前缀、ToolSearch 可激活=中途激活通路);命中任一激活源 ⇒ `undefined`
+ * (不 defer=名字+schema 全量上 wire):
+ *   a) 用户当轮说 "workflow"(workflowFromInput,只扫真人输入);
+ *   b) "ultracode" 关键词(L3,同一红线);
+ *   c) `/effort ultracode` sticky dial(L2 preset)。
+ * CALLER 前置两门:live 门(mock 形不变)+ selfOrchestration stamp 存在(opt-out 时 Workflow 根本不挂载,
+ * defer 无意义)。前缀缓存注记:defer↔不 defer 的翻转只发生在真人激活当轮,与 CC 209 ToolSearch materialize
+ * 同一形——非激活轮的前缀指纹稳定([1044]② clay 硬约束 ii 的解)。
+ */
+export function workflowDeferForRequest(humanInput, env = hostEnv()) {
+    if (deferOptedOut(env))
+        return undefined;
+    if (getUltracodePreset() || ultracodeFromInput(humanInput) || workflowFromInput(humanInput))
+        return undefined;
+    return ['Workflow'];
+}
+/** [1077]④ 低频工具惰性注入:`SEMA_DEFER_TOOLS=<csv>`(wire 名)追加进 deferTools(core 1.314
+ *  延迟披露腿)。**缺省翻转已裁(clay [1212]⑤,2026-07-19)**:九件低频工具缺省 defer——判决数=
+ *  -2,484 tok/首调用+多轮 gate 零行为退化;defer≠禁用(占位符在,模型 ToolSearch 随取)。
+ *  逃生门:`SEMA_DEFER_LOWFREQ=0/false/no/off` 关缺省名单(九件恢复全量上前缀)。 */
+export const DEFER_TOOLS_ENV = 'SEMA_DEFER_TOOLS';
+export const DEFER_LOWFREQ_ENV = 'SEMA_DEFER_LOWFREQ';
+/** clay 裁定的缺省惰性名单([1076]④ 评测九件原单,[1090]② 判决数)。 */
+export const DEFAULT_LOWFREQ_DEFER = [
+    'Glob',
+    'Grep',
+    'LSP',
+    'RepoMap',
+    'Monitor',
+    'Now',
+    'AgentTranscript',
+    'ReadToolResult',
+    'ReportBlocked',
+];
+function extraDeferFromEnv(env) {
+    const raw = env[DEFER_TOOLS_ENV];
+    if (typeof raw !== 'string' || raw.trim().length === 0)
+        return [];
+    return raw
+        .split(',')
+        .map((s) => s.trim())
+        .filter((s) => s.length > 0);
+}
+function lowFreqOptedOut(env) {
+    const raw = env[DEFER_LOWFREQ_ENV];
+    const s = typeof raw === 'string' ? raw.trim().toLowerCase() : '';
+    return s === '0' || s === 'false' || s === 'no' || s === 'off';
+}
+/**
+ * The FULL deferTools list for a request: the Workflow default-defer lane (activation sources, see
+ * {@link workflowDeferForRequest}) + the DEFAULT low-frequency list (clay [1212]⑤, opt-out via
+ * SEMA_DEFER_LOWFREQ) + the SEMA_DEFER_TOOLS extra list, deduped. An activation hit removes ONLY
+ * Workflow (the user asked for it by name); the other lanes are source-independent. Empty ⇒
+ * `undefined` (no stamp, request shape unchanged).
+ */
+export function deferToolsForRequest(humanInput, env = hostEnv()) {
+    const workflowLane = workflowDeferForRequest(humanInput, env) ?? [];
+    const lowFreqLane = lowFreqOptedOut(env) ? [] : DEFAULT_LOWFREQ_DEFER;
+    const extra = extraDeferFromEnv(env).filter((name) => name !== 'Workflow' || workflowLane.length > 0);
+    const merged = [...new Set([...workflowLane, ...lowFreqLane, ...extra])];
+    return merged.length > 0 ? merged : undefined;
+}

package/dist/webSearchWireCaps.d.ts

@@ -0,0 +1,54 @@
+/**
+ * ⇄ B2 批搬迁(2026-07-27,多端改造设计稿 §3 B2):cli src/sema/webSearchWireCaps.ts 逐字搬入(零依赖)。
+ */
+/**
+ * src/sema/webSearchWireCaps.ts — PURE projection: the shell's WebSearch backend config → the @sema-ai
+ * `SemaSettings.webSearch` wire shape carried on `TaskRequest.settings.webSearch`.
+ *
+ * The SERVICE consumes `body.settings.webSearch` — ai-agent-service `src/plugins/web-search.ts`
+ * `webSearchConfigFromSettings(raw)` reads a per-request `{ provider, apiKey?, endpoint?, maxResults? }` that
+ * WINS over the deployment-env backend, gated to the single-user host lane (a per-request endpoint/apiKey is a
+ * capability config; on multi-tenant it would be SSRF, so multi-tenant uses ONLY the deploy-env backend —
+ * design/107). The service validates `provider ∈ brave | tavily | searxng` and DROPS a missing/invalid provider
+ * (it never throws — a bad config falls back to the deploy-env backend). We mirror that exact validation here so
+ * the shell never stamps a config the service would reject.
+ *
+ * Two config sources, ENV wins (the primary / verify lane):
+ *   - ENV: `SEMA_WEBSEARCH_PROVIDER` / `_ENDPOINT` / `_API_KEY` / `_MAX_RESULTS` (SEMA_-namespaced, distinct from
+ *     the SERVICE's own deploy `WEB_SEARCH_*` env so the shell config never collides with the worker's).
+ *   - settings.json: a CC-parity `webSearch` section (the SettingsSchema outer `.passthrough()` preserves it).
+ *
+ * PURE — no env/file IO of its OWN (callers pass `env` / `raw`), so it bundles + unit-tests without the heavy
+ * settings graph, exactly like mcpWireCaps. The CALLER (seamQuery / seamQueryEngine) gates the env read to LIVE
+ * mode so the mock request shape never changes; webSearch presence IS the opt-in (no extra flag needed).
+ */
+import { type EnvLike } from './hostEnv.js';
+/** The search providers the service backend speaks (web-search.ts `WebSearchProvider`). */
+export type WebSearchProvider = 'brave' | 'tavily' | 'searxng';
+/** The `SemaSettings.webSearch` wire shape — mirrors the service's per-request parser input
+ *  (web-search.ts `webSearchConfigFromSettings`: `{ provider, apiKey?, endpoint?, maxResults? }`). */
+export interface WebSearchSettings {
+    provider: WebSearchProvider;
+    /** API key (brave/tavily). The service keeps it in a closure — it never reaches the model or the tool args. */
+    apiKey?: string;
+    /** SearXNG base URL (REQUIRED for searxng); for brave/tavily an optional base-URL override. */
+    endpoint?: string;
+    /** Max results returned to the model (the service clamps 1..20; default 10). */
+    maxResults?: number;
+}
+/** The four env keys the shell reads. SEMA_-namespaced so they never collide with the worker's deploy
+ *  `WEB_SEARCH_*` env (the service reads BOTH — a per-request body.settings.webSearch WINS over its env). */
+export declare const WEBSEARCH_ENV: {
+    readonly provider: "SEMA_WEBSEARCH_PROVIDER";
+    readonly endpoint: "SEMA_WEBSEARCH_ENDPOINT";
+    readonly apiKey: "SEMA_WEBSEARCH_API_KEY";
+    readonly maxResults: "SEMA_WEBSEARCH_MAX_RESULTS";
+};
+/** ENV source → WebSearchSettings, or undefined when no/invalid provider (⇒ no stamp; service uses its env/none). */
+export declare function webSearchFromEnv(env?: EnvLike): WebSearchSettings | undefined;
+/** settings.json `webSearch` section (UNTRUSTED passthrough value) → WebSearchSettings, mirroring the service's
+ *  `webSearchConfigFromSettings`. Missing/invalid provider ⇒ undefined (omit). NEVER throws. */
+export declare function webSearchFromSettings(raw: unknown): WebSearchSettings | undefined;
+/** Resolve the effective WebSearch config: ENV wins (the primary lane), else the settings.json section.
+ *  Undefined ⇒ no stamp (the service falls back to its deploy-env backend, or ships no WebSearch tool). */
+export declare function resolveWebSearch(env?: EnvLike, settingsRaw?: unknown): WebSearchSettings | undefined;

package/dist/webSearchWireCaps.js

@@ -0,0 +1,76 @@
+/**
+ * ⇄ B2 批搬迁(2026-07-27,多端改造设计稿 §3 B2):cli src/sema/webSearchWireCaps.ts 逐字搬入(零依赖)。
+ */
+/**
+ * src/sema/webSearchWireCaps.ts — PURE projection: the shell's WebSearch backend config → the @sema-ai
+ * `SemaSettings.webSearch` wire shape carried on `TaskRequest.settings.webSearch`.
+ *
+ * The SERVICE consumes `body.settings.webSearch` — ai-agent-service `src/plugins/web-search.ts`
+ * `webSearchConfigFromSettings(raw)` reads a per-request `{ provider, apiKey?, endpoint?, maxResults? }` that
+ * WINS over the deployment-env backend, gated to the single-user host lane (a per-request endpoint/apiKey is a
+ * capability config; on multi-tenant it would be SSRF, so multi-tenant uses ONLY the deploy-env backend —
+ * design/107). The service validates `provider ∈ brave | tavily | searxng` and DROPS a missing/invalid provider
+ * (it never throws — a bad config falls back to the deploy-env backend). We mirror that exact validation here so
+ * the shell never stamps a config the service would reject.
+ *
+ * Two config sources, ENV wins (the primary / verify lane):
+ *   - ENV: `SEMA_WEBSEARCH_PROVIDER` / `_ENDPOINT` / `_API_KEY` / `_MAX_RESULTS` (SEMA_-namespaced, distinct from
+ *     the SERVICE's own deploy `WEB_SEARCH_*` env so the shell config never collides with the worker's).
+ *   - settings.json: a CC-parity `webSearch` section (the SettingsSchema outer `.passthrough()` preserves it).
+ *
+ * PURE — no env/file IO of its OWN (callers pass `env` / `raw`), so it bundles + unit-tests without the heavy
+ * settings graph, exactly like mcpWireCaps. The CALLER (seamQuery / seamQueryEngine) gates the env read to LIVE
+ * mode so the mock request shape never changes; webSearch presence IS the opt-in (no extra flag needed).
+ */
+import { hostEnv } from './hostEnv.js';
+/** The four env keys the shell reads. SEMA_-namespaced so they never collide with the worker's deploy
+ *  `WEB_SEARCH_*` env (the service reads BOTH — a per-request body.settings.webSearch WINS over its env). */
+export const WEBSEARCH_ENV = {
+    provider: 'SEMA_WEBSEARCH_PROVIDER',
+    endpoint: 'SEMA_WEBSEARCH_ENDPOINT',
+    apiKey: 'SEMA_WEBSEARCH_API_KEY',
+    maxResults: 'SEMA_WEBSEARCH_MAX_RESULTS',
+};
+/** Validate a provider EXACTLY as the service does (trim + lowercase; only the three known providers). */
+function normProvider(v) {
+    const p = typeof v === 'string' ? v.trim().toLowerCase() : '';
+    return p === 'brave' || p === 'tavily' || p === 'searxng' ? p : undefined;
+}
+/** Parse a positive integer maxResults (string env or number); undefined when absent/invalid (service clamps). */
+function normMax(v) {
+    const n = typeof v === 'number' ? v : Number(v);
+    return Number.isFinite(n) && n > 0 ? Math.floor(n) : undefined;
+}
+/** Assemble a `WebSearchSettings`, omitting empty optionals (never stamp `apiKey:''`/`endpoint:''`/`maxResults:0`). */
+function build(provider, apiKey, endpoint, maxResults) {
+    const max = normMax(maxResults);
+    return {
+        provider,
+        ...(typeof apiKey === 'string' && apiKey ? { apiKey } : {}),
+        ...(typeof endpoint === 'string' && endpoint ? { endpoint } : {}),
+        ...(max ? { maxResults: max } : {}),
+    };
+}
+/** ENV source → WebSearchSettings, or undefined when no/invalid provider (⇒ no stamp; service uses its env/none). */
+export function webSearchFromEnv(env = hostEnv()) {
+    const provider = normProvider(env[WEBSEARCH_ENV.provider]);
+    if (!provider)
+        return undefined;
+    return build(provider, env[WEBSEARCH_ENV.apiKey], env[WEBSEARCH_ENV.endpoint], env[WEBSEARCH_ENV.maxResults]);
+}
+/** settings.json `webSearch` section (UNTRUSTED passthrough value) → WebSearchSettings, mirroring the service's
+ *  `webSearchConfigFromSettings`. Missing/invalid provider ⇒ undefined (omit). NEVER throws. */
+export function webSearchFromSettings(raw) {
+    if (!raw || typeof raw !== 'object')
+        return undefined;
+    const s = raw;
+    const provider = normProvider(s.provider);
+    if (!provider)
+        return undefined;
+    return build(provider, s.apiKey, s.endpoint, s.maxResults);
+}
+/** Resolve the effective WebSearch config: ENV wins (the primary lane), else the settings.json section.
+ *  Undefined ⇒ no stamp (the service falls back to its deploy-env backend, or ships no WebSearch tool). */
+export function resolveWebSearch(env = hostEnv(), settingsRaw) {
+    return webSearchFromEnv(env) ?? webSearchFromSettings(settingsRaw);
+}

package/dist/workflow.d.ts

@@ -1,18 +1,50 @@
 /**
- * workflow 车道纯函数(抽自 sema-cli footerRowBelt/workflowTaskOutputProjection,围栏见
- * cli 仓 frameLaneGuards/taskOutputWorkflowEnvelope 套;[1617] 幽灵行家族的判别资产)。
+ * workflow 车道纯函数 + workflow-agent 台账。
+ *
+ * 沿革(B1 批,2026-07-27):0.2.0 时本文件是 cli `footerRowBelt.ts` / `workflowTaskOutputProjection.ts`
+ * 的**双份抄件**;B1 批按设计稿 §2.4.1-A/B 裁决「以壳侧现文件为真身、包内不留两份实现」:
+ *   · `parseWorkflowPollEnvelope` / `projectWorkflowTaskOutput` = cli `workflowTaskOutputProjection.ts`
+ *     的逐字搬入(0.2.0 抄件漏了 `agent_runs[].errorCode` 类型位,已按真身补齐);
+ *   · `rowIdTail` / `isWorkflowAgentTaskId` / `recordWorkflowAgentTaskId` / `isKnownWorkflowAgentTaskId`
+ *     = cli `footerRowBelt.ts` 的**belt 半场**(判据①④),按设计稿 §2.4.1-B「拆」搬入。
+ *     ⚠️ 留在 TUI 的是 `isFooterTaskRow` / `filterFooterTaskRows`(判据②③)—— 那两条含
+ *     「丢弃所有无 parentId 顶层行」的**端专属决策**(主 run 头部行由壳侧 fleetClient 合成渲染,
+ *     设计稿 §2.4.2-B),壳侧文件改成 import 本包的四个出口 + 自留那两个函数。
+ *   🔴 台账(`workflowAgentTaskIds`)是 module 级单实例:壳侧 bridge 的 task_progress lane 门写、
+ *     壳侧 belt 的 `isFooterTaskRow` 读 —— 两边都必须走**本包同一个模块实例**,否则台账写进一个
+ *     副本、读另一个副本(判据④ 静默失效,幽灵行回归)。
+ *
+ * 围栏见 cli 仓 frameLaneGuards / taskOutputWorkflowEnvelope / footerRowBelt 套;
+ * [1617] 幽灵行家族的判别资产。
  */
-/** core 1.356 BCE 合成 workflow-agent id 形:wa+16hex。
+/** 复合行键(`<runId> <taskId>`,fleet-bus fleetRunPublisher.childId)的尾段 = 引擎 taskId。
+ *  导出给壳侧 belt 半场复用(判据②③ 的行 id 归一);包内 fleetAgentPanelProjection 保留了它
+ *  自己的同语义私有副本(零依赖叶模块纪律,drift 由两侧测试各自锁)。 */
+export declare function rowIdTail(id: string): string;
+/** core 1.356 BCE 合成 workflow-agent id 形:wa+16hex(判据①)。
  *  真实 fleet 子行 id 是 `${runId} ${engineTaskId}` 复合形——必须取空白分隔尾段再匹配
- *  (cli footerRowBelt 原版语义;codex 对抗复审抓的等价性破坏,0.1.1 修)。 */
+ *  (cli footerRowBelt 原版语义;codex 对抗复审抓的等价性破坏,0.1.1 修)。
+ *  upstreamBridge 的 task_progress 前台 lane 门在 wire 无 workflowRunId 时(server <a76bd77,
+ *  黑板 [1619]:1.272.0 投影白名单仍剥该键)以此为次级判别——与 belt 双判据同模板。 */
 export declare function isWorkflowAgentTaskId(taskId: string): boolean;
-/** TaskOutput workflow 轮询信封识别(core task-registry formatWorkflowRun 真形:
- *  {task_id, type:"workflow", status, name?, …};type+task_id 双门,非该形返回 null)。 */
+export declare function recordWorkflowAgentTaskId(taskId: string): void;
+export declare function isKnownWorkflowAgentTaskId(taskId: string): boolean;
+/** 测试钩:清台账(壳侧原版无此口——module 级 Set 在壳里靠进程边界隔离;包内多组断言同进程跑,
+ *  必须能清,否则前一组的登记污染后一组)。 */
+export declare function __resetWorkflowAgentTaskIdsForTests(): void;
+/**
+ * TaskOutput legacy 腿(tool_end 无 structured)的 workflow 信封识别(#49 C3)。
+ * 判据=core task-registry formatWorkflowRun 真形:`{task_id, type:"workflow", status, name?, …}`
+ * ——type 判别位 + task_id 字符串双门,非该形返回 null(绝不误吞 bash/agent 轮询)。
+ */
 export declare function parseWorkflowPollEnvelope(body: string): {
     taskId: string;
     status: string;
     name?: string;
 } | null;
-/** workflow 轮询 JSON → 人话多行投影(agents 汇总行 + per-agent ✓/✗ 明细 + note/error 尾透传);
- *  非 JSON 原样返回(fail-soft)。 */
+/**
+ * workflow 轮询 JSON → 人话多行投影(agents 汇总行 + per-agent ✓/✗ 明细 + note/error 尾透传);
+ * 非 JSON 原样返回(fail-soft,`description [status]` 行仍在)。
+ * 输入=引擎 formatWorkflowRun 的 JSON 原文(core 1.352 起带 agent_runs per-agent 明细 + 失败 note 指路)。
+ */
 export declare function projectWorkflowTaskOutput(jsonSrc: string): string;

package/dist/workflow.js

@@ -1,16 +1,66 @@
 /**
- * workflow 车道纯函数(抽自 sema-cli footerRowBelt/workflowTaskOutputProjection,围栏见
- * cli 仓 frameLaneGuards/taskOutputWorkflowEnvelope 套;[1617] 幽灵行家族的判别资产)。
+ * workflow 车道纯函数 + workflow-agent 台账。
+ *
+ * 沿革(B1 批,2026-07-27):0.2.0 时本文件是 cli `footerRowBelt.ts` / `workflowTaskOutputProjection.ts`
+ * 的**双份抄件**;B1 批按设计稿 §2.4.1-A/B 裁决「以壳侧现文件为真身、包内不留两份实现」:
+ *   · `parseWorkflowPollEnvelope` / `projectWorkflowTaskOutput` = cli `workflowTaskOutputProjection.ts`
+ *     的逐字搬入(0.2.0 抄件漏了 `agent_runs[].errorCode` 类型位,已按真身补齐);
+ *   · `rowIdTail` / `isWorkflowAgentTaskId` / `recordWorkflowAgentTaskId` / `isKnownWorkflowAgentTaskId`
+ *     = cli `footerRowBelt.ts` 的**belt 半场**(判据①④),按设计稿 §2.4.1-B「拆」搬入。
+ *     ⚠️ 留在 TUI 的是 `isFooterTaskRow` / `filterFooterTaskRows`(判据②③)—— 那两条含
+ *     「丢弃所有无 parentId 顶层行」的**端专属决策**(主 run 头部行由壳侧 fleetClient 合成渲染,
+ *     设计稿 §2.4.2-B),壳侧文件改成 import 本包的四个出口 + 自留那两个函数。
+ *   🔴 台账(`workflowAgentTaskIds`)是 module 级单实例:壳侧 bridge 的 task_progress lane 门写、
+ *     壳侧 belt 的 `isFooterTaskRow` 读 —— 两边都必须走**本包同一个模块实例**,否则台账写进一个
+ *     副本、读另一个副本(判据④ 静默失效,幽灵行回归)。
+ *
+ * 围栏见 cli 仓 frameLaneGuards / taskOutputWorkflowEnvelope / footerRowBelt 套;
+ * [1617] 幽灵行家族的判别资产。
  */
-/** core 1.356 BCE 合成 workflow-agent id 形:wa+16hex。
+/** 复合行键(`<runId> <taskId>`,fleet-bus fleetRunPublisher.childId)的尾段 = 引擎 taskId。
+ *  导出给壳侧 belt 半场复用(判据②③ 的行 id 归一);包内 fleetAgentPanelProjection 保留了它
+ *  自己的同语义私有副本(零依赖叶模块纪律,drift 由两侧测试各自锁)。 */
+export function rowIdTail(id) {
+    return id.split(/\s+/).pop() ?? id;
+}
+/** core 1.356 BCE 合成 workflow-agent id 形:wa+16hex(判据①)。
  *  真实 fleet 子行 id 是 `${runId} ${engineTaskId}` 复合形——必须取空白分隔尾段再匹配
- *  (cli footerRowBelt 原版语义;codex 对抗复审抓的等价性破坏,0.1.1 修)。 */
+ *  (cli footerRowBelt 原版语义;codex 对抗复审抓的等价性破坏,0.1.1 修)。
+ *  upstreamBridge 的 task_progress 前台 lane 门在 wire 无 workflowRunId 时(server <a76bd77,
+ *  黑板 [1619]:1.272.0 投影白名单仍剥该键)以此为次级判别——与 belt 双判据同模板。 */
 export function isWorkflowAgentTaskId(taskId) {
-    const tail = taskId.split(/\s+/).pop() ?? taskId;
-    return /^wa[0-9a-f]{16}$/.test(tail);
+    return /^wa[0-9a-f]{16}$/.test(rowIdTail(taskId));
+}
+// ── 判据④:bridge task_progress lane 门台账([1641])────────────────────────────────────────────
+// bridge 的 workflow lane 门(帧带 workflowRunId 的权威判定)把子代 taskId 登记进来,行按尾段查。
+// ③④ 互为兜底:③(集合级双生识别,TUI 半场)不依赖时序但要求 wa 行在场;④ 不依赖 wa 行但要求
+// 本壳在读该 run 的会话流。
+const workflowAgentTaskIds = new Set();
+const MAX_WORKFLOW_TASK_IDS = 4096;
+export function recordWorkflowAgentTaskId(taskId) {
+    if (!taskId)
+        return;
+    workflowAgentTaskIds.delete(taskId);
+    workflowAgentTaskIds.add(taskId);
+    if (workflowAgentTaskIds.size > MAX_WORKFLOW_TASK_IDS) {
+        const oldest = workflowAgentTaskIds.values().next().value;
+        if (oldest !== undefined)
+            workflowAgentTaskIds.delete(oldest);
+    }
+}
+export function isKnownWorkflowAgentTaskId(taskId) {
+    return workflowAgentTaskIds.has(taskId);
+}
+/** 测试钩:清台账(壳侧原版无此口——module 级 Set 在壳里靠进程边界隔离;包内多组断言同进程跑,
+ *  必须能清,否则前一组的登记污染后一组)。 */
+export function __resetWorkflowAgentTaskIdsForTests() {
+    workflowAgentTaskIds.clear();
 }
-/** TaskOutput workflow 轮询信封识别(core task-registry formatWorkflowRun 真形:
- *  {task_id, type:"workflow", status, name?, …};type+task_id 双门,非该形返回 null)。 */
+/**
+ * TaskOutput legacy 腿(tool_end 无 structured)的 workflow 信封识别(#49 C3)。
+ * 判据=core task-registry formatWorkflowRun 真形:`{task_id, type:"workflow", status, name?, …}`
+ * ——type 判别位 + task_id 字符串双门,非该形返回 null(绝不误吞 bash/agent 轮询)。
+ */
 export function parseWorkflowPollEnvelope(body) {
     try {
         const j = JSON.parse(body);
@@ -26,8 +76,11 @@ export function parseWorkflowPollEnvelope(body) {
         return null;
     }
 }
-/** workflow 轮询 JSON → 人话多行投影(agents 汇总行 + per-agent ✓/✗ 明细 + note/error 尾透传);
- *  非 JSON 原样返回(fail-soft)。 */
+/**
+ * workflow 轮询 JSON → 人话多行投影(agents 汇总行 + per-agent ✓/✗ 明细 + note/error 尾透传);
+ * 非 JSON 原样返回(fail-soft,`description [status]` 行仍在)。
+ * 输入=引擎 formatWorkflowRun 的 JSON 原文(core 1.352 起带 agent_runs per-agent 明细 + 失败 note 指路)。
+ */
 export function projectWorkflowTaskOutput(jsonSrc) {
     try {
         const j = JSON.parse(jsonSrc);
@@ -35,19 +88,24 @@ export function projectWorkflowTaskOutput(jsonSrc) {
         if (j.agents && typeof j.agents.done === 'number' && typeof j.agents.total === 'number') {
             parts.push(`agents: ${j.agents.done}/${j.agents.total} done${typeof j.agents.failed === 'number' && j.agents.failed > 0 ? ` (${j.agents.failed} failed)` : ''}`);
         }
+        // per-agent 明细([1411]③/[1408] 围栏 M1):✓/✗ label [status] — error 首行/output 摘要。
+        // 缺席(老 core)零行=形状不变。
         if (Array.isArray(j.agent_runs)) {
             for (const r of j.agent_runs) {
                 if (!r || typeof r !== 'object')
                     continue;
                 const label = typeof r.label === 'string' && r.label.length > 0 ? r.label : '(agent)';
                 const st = typeof r.status === 'string' ? r.status : '?';
-                const errLine = typeof r.error === 'string' && r.error.length > 0 ? ` — ${r.error.split('\n')[0].slice(0, 120)}` : '';
+                const errLine = typeof r.error === 'string' && r.error.length > 0
+                    ? ` — ${r.error.split('\n')[0].slice(0, 120)}`
+                    : '';
                 const outLine = !errLine && typeof r.output === 'string' && r.output.length > 0
                     ? ` — ${r.output.split('\n')[0].slice(0, 80)}`
                     : '';
                 parts.push(`  ${st === 'completed' ? '✓' : st === 'failed' ? '✗' : '·'} ${label} [${st}]${errLine}${outLine}`);
             }
         }
+        // note 尾透传(core 失败指路:TaskOutput+resumeFromRunId)——不留死胡同(围栏 M2)。
         if (typeof j.note === 'string' && j.note.length > 0)
             parts.push(j.note);
         if (typeof j.error === 'string' && j.error.length > 0)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/client-core",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "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",