@sema-agent/server 7.72.0 → 7.73.1

package/dist/spec-fields.d.ts

@@ -96,7 +96,8 @@ export declare function taskAgentsSpecFragment(raw: unknown, requirePrincipal: b
 export declare function retainBackgroundProcessesFromBody(raw: unknown, requirePrincipal: boolean | undefined, warn: (event: string, fields: Record<string, unknown>) => void): true | undefined;
 /** [ref]② — body.{excludeTools,deferTools} → `TaskSpec.{excludeTools,deferTools}`(core 1.314 工具面
  *  控制批)。语义:excludeTools=roster 真卸载(schema 字节不上 wire,manifest 如实收窄);deferTools=
- *  [ref] 延迟披露(占位上 wire,ToolSearch 激活 materialize)。两位 tighten-only(core 继承不变量:
+ *  [ref] 延迟披露(占位上 wire,ToolSearch 激活 materialize;**core 7.15.0 [ref] 起它是唯一不受那道
+ *  10% 阈值门的延迟来源** —— 按字面恒延迟、不计量,引擎自选的候选集才受门)。两位 tighten-only(core 继承不变量:
  *  union 进全部子 spawn 路径),per-run 工具面收窄无跨租户面 ⇒ 无租户门(interactiveTools 同姿势)。
  *  DEFENSIVE(resume 重放不过 HTTP 400 门):非数组 ⇒ undefined;项非非空字符串 ⇒ 逐项 DROP;空数组 ⇒
  *  undefined(不挂键=core 缺省,byte-compat)。HTTP 门另有 fail-loud 400(提交面邻居姿势)。 */
@@ -109,7 +110,8 @@ export declare function toolNameListFromBody(raw: unknown): string[] | undefined
  *  **呈现**轴,它与 `deferMode` / `deferTools` 的延迟披露轴**无耦合** —— 上一行提 deferTools 只是在借它
  *  的「无租户门」姿势作类比。「引擎缺省 simple」这句本身在 core 5.40.0 上仍逐字为真
  *  (`core/types.d.ts:133`:default "simple"),本批亲验未变。
- *  真正的 defer 轴对表(core 5.40.0 起 `deferMode:"auto"` 不再 sweep 内建)记在
+ *  真正的 defer 轴对表(core 5.40.0 起 `deferMode:"auto"` 不再 sweep 内建;7.15.0 起它不再是第二道门,
+ *  只是把候选集拓宽后走同一道阈值门)记在
  *  `src/capabilities/tool-defer.ts` 的头注 —— 别把两根轴的结论写到一处。
  *  DEFENSIVE(resume 重放不过 HTTP 400 门):非法值 ⇒ undefined;提交面另有 fail-loud 400(邻居姿势)。 */
 export declare function promptProfileFromBody(raw: unknown): "simple" | "classic" | undefined;

package/dist/tool-approval.js

@@ -852,7 +852,7 @@ export class ToolApprovalCoordinator {
         };
         const windowBudgetMs = reachability === "unreached" ? this.unreachedTtlMs : this.ttlMs;
         const effectiveWindowMs = effectiveAskWindowMs(windowBudgetMs, this.windowMarginMs, origin.legDeadlineMonotonic, performance.now());
-        const expiresAtMs = Date.now() + effectiveWindowMs;
+        const expiresAtMs = Math.ceil(Date.now() + effectiveWindowMs);
         let askId;
         let batchId;
         const card = this.askStore ? buildApprovalCard(frame, req, req.requiresRealApproval === true) : undefined;

package/dist/trace/core-keyset-guard.d.ts

@@ -17,7 +17,7 @@
  * ⑨⑩([ref],2026-08-31)把两个最大的 wire 面也纳入:TaskSpec 按「server 有无写点」记 Wired/Unwired,
  * TaskResult 按「转发/摘除」记 Forwarded/Stripped —— 谁改 resolve-spec.ts / runs.ts 的发射点谁同步本文件。
  */
-import type { TaskNotificationPayload, SemaProvenance, BackgroundChildEvent, RosterEntry, AskRequest, CheckpointSummary, TaskEvent, TraceEvent, MailboxMessage, MailboxAppendMessage, TaskSpec, TaskResult, WiringManifest, GateOutcome, GateDisposition, Settlement, PausedCause } from "@sema-agent/core";
+import type { TaskNotificationPayload, SemaProvenance, BackgroundChildEvent, RosterEntry, AskRequest, CheckpointSummary, TaskEvent, TraceEvent, MailboxMessage, MailboxAppendMessage, TaskSpec, TaskResult, WiringManifest, GateOutcome, GateDisposition, Settlement, PausedCause, WorkflowRun } from "@sema-agent/core";
 import type { ToolApprovalFrame } from "../tool-approval.js";
 /** 编译期断言:T 必须收敛到 never(有残余键 = tsc 红)。
  *  🔴 **导出**([ref] U1/U2):本仓「词表闭集,未处置成员=编译红」的钉法只许有**一个**形 ——
@@ -148,6 +148,10 @@ type _GuardSettlementReverse = AssertAllKeysHandled<Exclude<SettlementProjected,
 type SettlementWhoProjected = "party" | "approver" | "window";
 type _GuardSettlementWho = AssertAllKeysHandled<Exclude<SettlementWhoKeys, SettlementWhoProjected>>;
 type _GuardSettlementWhoReverse = AssertAllKeysHandled<Exclude<SettlementWhoProjected, SettlementWhoKeys>>;
+type WorkflowRunForwarded = "id" | "scope" | "status" | "startedAt" | "endedAt" | "createdAt" | "rev" | "name" | "description" | "result" | "error" | "errorCode" | "agentFailures" | "stats" | "phases" | "agents" | "groups";
+type WorkflowRunStripped = "sourceTaskId" | "originatingSessionId" | "effectiveArgs" | "budgetOvershoot" | "timeoutInterruption" | "resultFull" | "completionId" | "resume" | "journalSkips";
+type _GuardWorkflowRun = AssertAllKeysHandled<Exclude<keyof WorkflowRun, WorkflowRunForwarded | WorkflowRunStripped>>;
+type _GuardWorkflowRunReverse = AssertAllKeysHandled<Exclude<WorkflowRunForwarded | WorkflowRunStripped, keyof WorkflowRun>>;
 export type CoreKeysetGuards = [
     _GuardNotification,
     _GuardNotificationReverse,
@@ -217,7 +221,9 @@ export type CoreKeysetGuards = [
     _GuardSettlement,
     _GuardSettlementReverse,
     _GuardSettlementWho,
-    _GuardSettlementWhoReverse
+    _GuardSettlementWhoReverse,
+    _GuardWorkflowRun,
+    _GuardWorkflowRunReverse
 ];
 export {};
 //# sourceMappingURL=core-keyset-guard.d.ts.map

package/dist/trace/project.d.ts

@@ -119,6 +119,21 @@ export declare function toolStartEventData(ev: {
     eventId?: string;
     parentToolCallId?: string;
 }): Record<string, unknown>;
+/**
+ * 🔴 **筛子是一只总函数**(S-239,codex 对抗复审 r1 [medium] 亲核复现后修)—— 上面纪律②许诺的
+ * 「坏形 ⇒ report + withhold,**不抛**」此前是靠**逐条枚举**坏形兑现的,枚举不到的那些照样抛:
+ * `projectSettlement` 对 `note` / `who.approver` 先 `redactSecrets` 再截断,而 `redactSecrets` 在 ≥2^23
+ * 的单段上爆回溯栈(`RangeError`,S-102/S-106 登记的既有上界,见 `redact.ts` 该行顶注),两条叶各能抛一次。
+ *
+ * 抛出去的代价按腿算,而且一条比一条重:写腿落账那处的 `.catch` 看不到**同步**投影期的异常;读腿上它
+ * 直接逃出 `formatEvent` / 投影函数 —— 账本裸回放腿的那一次会当场断流(那一行不上帧、游标不前进、后面的
+ * `done` 永远到不了、重连恒复现同一处),而 `gate-outcome-defective` 那一格还不涨。
+ *
+ * ⇒ 兑现方式从「枚举」换成**结构**:任何逃出投影的异常同走既有的那一口 report + withhold。规则因此变少
+ * (不是「守住已知的 N 种坏形」而是「坏字节一律 withhold」),上面那几道具名形门留着只为**诊断串更准**。
+ * ⛔ **刻意不动**「先脱敏后截断」的次序:截断在前会把跨界的密钥切成半截明文留在输出里,而且它只治
+ * `note` 一条叶(`approver` 同病)—— 那是给一个类打两个特判,正是本仓要消掉的形。
+ */
 export declare function screenedGate(v: unknown): GateOutcome | undefined;
 /**
  * 🔴 **耐久行的**门记录读口(7.72.0;`screenedGate` 的读腿孪生)—— 先把本仓自己写过的**旧拼法**读成它
@@ -132,6 +147,34 @@ export declare function screenedGate(v: unknown): GateOutcome | undefined;
  * 不改原对象(调用方与账本共享引用):归一时换一只信封,原记录一个字节不动。
  */
 export declare function screenedStoredGate(v: unknown): GateOutcome | undefined;
+/**
+ * 🔴 **账本裸回放面的读腿一步**(S-239)—— `GET /v1/runs/:id/events`(`http/routes/runs.ts` 的
+ * `formatEvent`)对每一行走这一口,把行上的 `GateOutcome` 交给**同一只** {@link screenedStoredGate}。
+ *
+ * ## 它补的是哪一格
+ * 7.72.0 把耐久读边界收成一只筛子,但点名的读腿只有两条({@link toolResultFieldsOf} 的投影回放、
+ * `/decide` 幂等回放体)。**账本裸回放**是第三条,而它此前只过 `redactLedgerEventData` —— 那只函数
+ * 对 `tool_end` 型**逐字不动**(它管的是 `done.result` / `failed.errorMessage` / park 行三族)。
+ * 于是同一条账本行在本仓三张读面上有**两种**读法:
+ *  · 本仓 7.64.0–7.71.0 自己写下的 `origin:"unresolvable"` —— 投影面读成今天的名字,裸回放面原样
+ *    透出一个 core 今天判**非成员**的词(消费端按闭集分派 ⇒ 落进它的 default 臂);
+ *  · 第三方 producer / 坏世代写下的集外词与破不变量的记录 —— 投影面整条 withhold + 计数,裸回放面
+ *    直接上 wire,而 `gate-outcome-defective` 那一格不涨(运维看不见有 producer 在发坏记录)。
+ *
+ * ## 为什么是这一形(而不是在路由里加一只筛)
+ * 筛子仍然只有一只,归一表仍然只有一张 —— 本函数只是把**第三条读腿**接到它上面,规则因此从
+ * 「三条读腿里有两条筛」回到「凡耐久读腿上的 `GateOutcome` 一律过 `screenedStoredGate`,零例外」。
+ * 它按**型**分派而不是按调用点,所以将来第二个携带 `GateOutcome` 的账本型只需把
+ * {@link GATE_BEARING_LEDGER_EVENT_TYPE} 扩成词表,读腿一行都不用改。
+ *
+ * ## 与写腿的关系(别再走回头路)
+ * 写腿的对偶是 `redactLedgerEventData`(三孪生 store 的 `appendEvent` 落库前),它**不该**长出本函数
+ * 这一步:归一只认读腿,写腿保持严格(理由全文见 {@link RETIRED_ASK_ORIGIN_SPELLINGS} 的边界划清二)。
+ * 两只函数因此是「共用的脱敏汇点 + 读腿独有的筛」这一层关系,不是同一只函数的两种模式。
+ *
+ * 不改原对象(调用方与账本共享引用):有变更时换一只信封,原记录一个字节不动。
+ */
+export declare function screenedStoredEventData(type: string, data: unknown): unknown;
 /** The durable `tool_end` payload (shared by both append sites). E1: the model-facing `output` is UNTRUSTED RAW
  *  from core (file/shell/API bodies) — core only SIZE-bounds it (`truncated`), REDACTION is ours (same contract as
  *  `tool_start.args`); never re-fed to a model. E2: identity. Absent `output` ⇒ the tool produced no content body.

package/dist/trace/project.js

@@ -90,6 +90,15 @@ const RETIRED_ASK_ORIGIN_SPELLINGS = {
     unresolvable: "ancestor_marked",
 };
 export function screenedGate(v) {
+    try {
+        return screenedGateOrThrow(v);
+    }
+    catch (e) {
+        recordFailOpen("server.trace.gate-outcome-defective", `projection threw: ${e instanceof Error ? `${e.name}: ${e.message}` : "non-Error throw"}`);
+        return undefined;
+    }
+}
+function screenedGateOrThrow(v) {
     if (v === null || typeof v !== "object")
         return undefined;
     const g = v;
@@ -133,6 +142,23 @@ export function screenedStoredGate(v) {
     const renamed = typeof g.origin === "string" ? RETIRED_ASK_ORIGIN_SPELLINGS[g.origin] : undefined;
     return screenedGate(renamed === undefined ? g : { ...g, origin: renamed });
 }
+const GATE_BEARING_LEDGER_EVENT_TYPE = "tool_end";
+export function screenedStoredEventData(type, data) {
+    if (type !== GATE_BEARING_LEDGER_EVENT_TYPE)
+        return data;
+    if (data === null || typeof data !== "object" || Array.isArray(data))
+        return data;
+    const d = data;
+    if (d.gate === undefined)
+        return data;
+    const gate = screenedStoredGate(d.gate);
+    if (gate === undefined) {
+        const withheld = { ...d };
+        delete withheld.gate;
+        return withheld;
+    }
+    return { ...d, gate };
+}
 const SETTLEMENT_PARTIES = new Set(["person", "engine", "host", "none"]);
 function projectSettlement(st) {
     const whoV = st.who;

package/dist/usage-analytics.d.ts

@@ -72,10 +72,20 @@ export interface UsageTotals {
 export declare function usageSummary(rows: UsageRow[]): UsageTotals;
 export type UsageMetric = "tasks" | "tokensIn" | "tokensOut" | "costUsd";
 export type UsageGranularity = "hour" | "day";
-/** GET /v1/usage/series — 时间序列(UTC 桶;空桶不发行,消费方按需补零)。 */
+/**
+ * GET /v1/usage/series — 时间序列(UTC 桶;空桶不发行,消费方按需补零)。
+ *
+ * 🔴 **行带 `estimated`**(S-228):与 {@link usageSummary} / {@link usageBreakdown} **同轴同谓词** ——
+ * 三个读面的桶都是同一只 {@link UsageTotals},由同一条 {@link foldRow} 折出来,所以「这个数字不精确」
+ * 的四个来源(旧行 fallback / per-model echo 缺键 / 缺 `usageBasis` 的 legacy 口径 / 行自陈
+ * `usageMissing` 的下界)在三面上是**同一句话**。修前只有 series 的出口把这一位扔了:桶里塞进一条
+ * 「没量到」的行,折线与一段真的低消耗在 wire 上逐字同形 —— 而那两件事的处置相反。
+ * 不新开判据、不加第二条轴:出口多投一个已经算好的位。
+ */
 export declare function usageSeries(rows: UsageRow[], metric: UsageMetric, granularity: UsageGranularity): Array<{
     t: string;
     v: number;
+    estimated: boolean;
 }>;
 export type UsageDimension = "principal" | "model";
 /** GET /v1/usage/breakdown — 按维度分桶。dimension=model 时按 per-model echo 展开(一行可贡献多个 model 桶;

package/dist/usage-analytics.js

@@ -54,7 +54,7 @@ export function usageSeries(rows, metric, granularity) {
     }
     return [...buckets.entries()]
         .sort((a, b) => a[0] - b[0])
-        .map(([b, t]) => ({ t: new Date(b).toISOString(), v: metric === "costUsd" ? round6(t.costUsd) : t[metric] }));
+        .map(([b, t]) => ({ t: new Date(b).toISOString(), v: metric === "costUsd" ? round6(t.costUsd) : t[metric], estimated: t.estimated }));
 }
 export function usageBreakdown(rows, dimension) {
     const buckets = new Map();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "7.72.0",
+  "version": "7.73.1",
   "description": "Sema Server — the server/API implementation layer for Sema, wiring core, registry, model providers, and cloud agent execution. Built on @sema-agent/core.",
   "type": "module",
   "license": "BUSL-1.1",
@@ -54,7 +54,7 @@
     "build:binary:run-local:darwin-arm64": "bun build --compile --target=bun-darwin-arm64 src/run-local.ts --outfile dist/run-local-darwin-arm64"
   },
   "dependencies": {
-    "@sema-agent/core": "7.14.0",
+    "@sema-agent/core": "7.16.0",
     "@sema-agent/settings-schema": "1.10.0",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",