@sema-agent/server 3.3.0 → 3.4.1

package/dist/http/routes/approvals-assistant.js

@@ -3,7 +3,7 @@ import { principalFrom, verifyDirectDoorProof, MAX_APPROVAL_REASON_CHARS } from
 import { redactedPreview } from "../../trace/redact.js";
 import { sleep } from "../sse-log.js";
 import { sendJson, sendError, sseHeaders } from "../send.js";
-import { gatedPrincipal, explicitOperatorOk, isOperator, explicitOperator } from "../principal-gate.js";
+import { gatedPrincipal, explicitOperatorOk, isOperator } from "../principal-gate.js";
 // design/80 seam #2 (assistant-scheduler): graceful preempt (durable yield) + resource_limit resume of one task.
 export const ASSISTANT_PREEMPT_RE = /^\/v1\/assistant\/tasks\/([^/]+)\/preempt$/;
 export const ASSISTANT_RESUME_RE = /^\/v1\/assistant\/tasks\/([^/]+)\/resume$/;
@@ -155,13 +155,35 @@ async function handleApprovalsAssistantBody(req, res, url, ctx, miss) {
                 // 🔴 STRIP the resume `token` (the unexposed secret capability — resume is by sessionId, never the
                 // token) AND the RAW `toolInput` (core bounds but does NOT redact it — redaction is
                 // the consumer's job). Re-emit the REDACTED `input` instead.
-                const { token: _token, toolInput: _rawToolInput, ...safe } = s;
-                // `input` = a REDACTED preview of the projected (bounded, RAW) tool_input. Only `tool_approval` gates
-                // carry it (resource_limit / plan_review have none ⇒ toolInput undefined ⇒ input null). NOT the old
-                // bug (raw rich row + decide-binding); the decide-binding still lives only on /v1/approvals.
+                // 🔴 EXPLICIT projection([2029] cli 批准的收窄,辖域=仅本 inbox 面)—— 此前是「剥 token/toolInput、
+                // 其余整行展开」,于是 core summarizeCheckpoint 在 tool_approval 门上填的 toolName/toolCallId/preview/
+                // principal/sourceTaskId/contentKind 全部漏上 wire(其中 preview 还没过脱敏,而它同源的 toolInput 是
+                // 显式脱敏的)。四客户端仓结构性零消费(inbox verb 无调用点,[2029] 取证),按 §2 原意收成显式白名单:
+                // §1 镜像键(OMIT-when-absent)+ 两个显式 nullable 的 enrichment(objective/input)。富行
+                // (toolName/toolCallId/decide 绑定)只住 /v1/approvals —— 那面有具名消费者(desktop session-host
+                // 冷恢复),不在本刀辖域。`input` = REDACTED preview,只有 tool_approval 门携带(其余 ⇒ null)。
                 const input = s.toolInput != null ? redactedPreview(s.toolInput) : null;
-                return { ...safe, objective: ctx?.body?.objective ?? null, input };
-            }))).sort((a, b) => (b.severity ?? 0) - (a.severity ?? 0)); // severity DESC (listByScope is created_at ASC; stable → oldest-first within a tier)
+                return {
+                    sessionId: s.sessionId,
+                    scope: s.scope,
+                    createdAt: s.createdAt,
+                    ...(s.gateKind !== undefined ? { gateKind: s.gateKind } : {}),
+                    ...(s.severity !== undefined ? { severity: s.severity } : {}),
+                    ...(s.spentMicroUsd !== undefined ? { spentMicroUsd: s.spentMicroUsd } : {}),
+                    ...(s.deadline !== undefined ? { deadline: s.deadline } : {}),
+                    objective: ctx?.body?.objective ?? null,
+                    input,
+                };
+            }))
+            // severity DESC, then **explicitly** oldest-first within a tier ([2027] 第五节欠单②,红先绿后:
+            // test/assistant-triage-ordering.test.ts)。旧姿势只比 severity,靠「listByScope 是 created_at ASC
+            // + Array#sort 稳定」来兑现 §2 那句 oldest-first —— 而那个前提**只在本仓的 SQL 后端成立**
+            // (checkpoint-store-sql.ts 的 `ORDER BY created_at ASC`):core 的 `CheckpointStore.listByScope` 接口
+            // 零顺序声明,InMemory/File 两个实现直接遍历 Map(LOCAL 车道包的正是 File store)⇒ 那句承诺过去是
+            // **后端相关**的。比较器自带兜底后它与 store 顺序无关。形与 listPending 的同族 sort 逐字一致
+            // (checkpoint-store-sql.ts `|| a.createdAt - b.createdAt`)。createdAt 缺席(pre-1.116 投影的老行)
+            // 计 0 = 档内最老:确定性优于「看它恰好落在哪」。
+            ).sort((a, b) => (b.severity ?? 0) - (a.severity ?? 0) || (a.createdAt ?? 0) - (b.createdAt ?? 0));
             sendJson(res, 200, { inbox }); // CheckpointSummary (token-stripped) + objective, severity-prioritized — the assistant single inbox
             return;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "3.3.0",
+  "version": "3.4.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",
@@ -53,7 +53,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": "^2.1.0",
+    "@sema-agent/core": "^2.2.0",
     "@sema-agent/registry-core": "^0.10.24",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",

package/dist/finance/cost-taxonomy.d.ts

@@ -1,34 +0,0 @@
-export interface InfraCostRates {
-    toolCallMicroUsd: number;
-    sandboxSecMicroUsd: number;
-    egressGbMicroUsd: number;
-}
-export interface InfraUsage {
-    toolCalls: number;
-    sandboxWalltimeMs: number;
-    egressBytes: number;
-}
-export interface InfraCostBreakdown {
-    toolCallMicroUsd: number;
-    sandboxWalltimeMicroUsd: number;
-    egressMicroUsd: number;
-    totalMicroUsd: number;
-}
-export interface LlmCostBreakdown {
-    llmRootMicroUsd: number;
-    nestedSubagentMicroUsd: number;
-    memoryConsolidationMicroUsd: number;
-    compactionMicroUsd: number;
-}
-export interface SupervisorCostBreakdown {
-    llm: LlmCostBreakdown | null;
-    infra: InfraCostBreakdown;
-    totalMicroUsd: number;
-}
-export declare function infraCost(usage: InfraUsage, rates: InfraCostRates): InfraCostBreakdown;
-export declare function composeSupervisorCost(llm: LlmCostBreakdown | null, llmTotalMicroUsd: number, infra: InfraCostBreakdown): SupervisorCostBreakdown;
-export declare function hasInfraPricing(r: InfraCostRates): boolean;
-export declare function infraUsageFromEvents(events: ReadonlyArray<{
-    type?: string;
-}>, runDurationMs: number): InfraUsage;
-//# sourceMappingURL=cost-taxonomy.d.ts.map

package/dist/finance/cost-taxonomy.js

@@ -1,26 +0,0 @@
-const nonNeg = (n) => (Number.isFinite(n) && n > 0 ? n : 0);
-export function infraCost(usage, rates) {
-    const toolCallMicroUsd = nonNeg(usage.toolCalls) * nonNeg(rates.toolCallMicroUsd);
-    const sandboxWalltimeMicroUsd = (nonNeg(usage.sandboxWalltimeMs) / 1000) * nonNeg(rates.sandboxSecMicroUsd);
-    const egressMicroUsd = (nonNeg(usage.egressBytes) / 1_000_000_000) * nonNeg(rates.egressGbMicroUsd);
-    return {
-        toolCallMicroUsd,
-        sandboxWalltimeMicroUsd,
-        egressMicroUsd,
-        totalMicroUsd: toolCallMicroUsd + sandboxWalltimeMicroUsd + egressMicroUsd,
-    };
-}
-export function composeSupervisorCost(llm, llmTotalMicroUsd, infra) {
-    return { llm, infra, totalMicroUsd: nonNeg(llmTotalMicroUsd) + infra.totalMicroUsd };
-}
-export function hasInfraPricing(r) {
-    return r.toolCallMicroUsd > 0 || r.sandboxSecMicroUsd > 0 || r.egressGbMicroUsd > 0;
-}
-export function infraUsageFromEvents(events, runDurationMs) {
-    return {
-        toolCalls: events.reduce((n, e) => (e.type === "tool_start" ? n + 1 : n), 0),
-        sandboxWalltimeMs: nonNeg(runDurationMs),
-        egressBytes: 0,
-    };
-}
-//# sourceMappingURL=cost-taxonomy.js.map

package/dist/sema-registry.d.ts

@@ -1,41 +0,0 @@
-/**
- * Sema-registry adapter — pull the effective config from sema-registry and apply it OVER the
- * env-derived defaults (env = fallback, center = override). Follows the "universal internal
- * schema → translate at the boundary" pattern, with our security boundary kept:
- *
- *   - the CENTER owns the LOGICAL config: the model roster (names/capabilities/tier), the role map,
- *     and team templates;
- *   - the SERVICE env still owns the SECRETS: API keys stay in env (the center never stores a secret);
- *     keys are per-model via `apiKeyEnv` → `config.modelApiKeyEnv` → the spec's `getApiKeyAndHeaders`
- *     (core 1.45), so each model/cascade-rung authenticates with its own upstream key.
- *
- * Per-model `baseUrl` IS transported (a catalog model may live on a different gateway;
- * core brain honors model.baseUrl, absent = "" = boot-env endpoint).
- *
- * Hot-reload status (复审 2026-07-29 P1-11 — 亲读判定,取代此处旧的 "models/roles are restart-to-apply"
- * TODO, which went stale when `mutateInPlace` landed):
- *   - models/roles/roster/teams/projects/autonomy — **HOT**. `applyEffective` mutates `config.models`/
- *     `config.roles` IN PLACE, and core's Runner reads `this.deps.models/roles` per task off that very
- *     reference. Both brains re-resolve `model.baseUrl || config.baseUrl` inside `buildRequest()` on every
- *     call (core 2.1.0 `brain/openai.js` + `brain/anthropic.js`), so a moved gateway takes effect on the
- *     next task with no restart.
- *   - the same plane under a **tier-frozen** Runner — deferred, not hot: core expands a PRIVATE catalog copy
- *     at construction, so `main` defers the whole plane and the `models-tiers` restart slice signals.
- *   - **`degrade-route`** — the one genuinely boot-frozen catalog consumer left: reactive degrade
- *     (`MODEL_DEGRADE_REACTIVE`) bakes the target Model + its gateway + its key into the brain composition
- *     at boot. It cannot be hot-applied without rebuilding the brain, so it is registered on the existing
- *     restartRequired /health contract instead (see `restart-signal.ts`). Fail-loud beats serving a stale
- *     gateway silently on the rate-limit path.
- *   - skills/mcp/scenarios/runtime-gates — restart-to-apply by construction (baked into the boot wiring).
- *
- * (design/158 A13, internal-lossless) This module is now a FACADE: the implementation lives in
- * `src/config-center/` split by responsibility group (HTTP client / EffectiveConfig application /
- * restart-signal detection / skills+MCP consumption). Every symbol below is re-exported UNCHANGED —
- * existing `from "./sema-registry.js"` / `from "../sema-registry.js"` imports need zero changes.
- */
-export { fetchEffective, fetchPrincipalCaps, ConfigCenterHttpError, fetchSkillContent, fetchPromptArtifact, fetchPromptBlob, } from "./config-center/http-client.js";
-export { mutateInPlace, applyEffective, applyRuntimeGates, applyRuntimeHot, resolveDefaultModelName, logEffectiveDiff, runtimeHasActiveGate, } from "./config-center/apply-effective.js";
-export { restartReasons, planeHasActiveTiers, modelPlaneChanged, type RestartSlice, type RestartSliceCtx, type RestartSignal, } from "./config-center/restart-signal.js";
-export { applyCenterSkills, resolveMcpServers, mcpForScenario } from "./config-center/skills-mcp.js";
-export type { CenterSkillManifest, CenterMcpServer, EffectiveConfig, ExecutionRuling, SessionMirrorRuling, } from "./config-center/types.js";
-//# sourceMappingURL=sema-registry.d.ts.map

package/dist/sema-registry.js

@@ -1,40 +0,0 @@
-/**
- * Sema-registry adapter — pull the effective config from sema-registry and apply it OVER the
- * env-derived defaults (env = fallback, center = override). Follows the "universal internal
- * schema → translate at the boundary" pattern, with our security boundary kept:
- *
- *   - the CENTER owns the LOGICAL config: the model roster (names/capabilities/tier), the role map,
- *     and team templates;
- *   - the SERVICE env still owns the SECRETS: API keys stay in env (the center never stores a secret);
- *     keys are per-model via `apiKeyEnv` → `config.modelApiKeyEnv` → the spec's `getApiKeyAndHeaders`
- *     (core 1.45), so each model/cascade-rung authenticates with its own upstream key.
- *
- * Per-model `baseUrl` IS transported (a catalog model may live on a different gateway;
- * core brain honors model.baseUrl, absent = "" = boot-env endpoint).
- *
- * Hot-reload status (复审 2026-07-29 P1-11 — 亲读判定,取代此处旧的 "models/roles are restart-to-apply"
- * TODO, which went stale when `mutateInPlace` landed):
- *   - models/roles/roster/teams/projects/autonomy — **HOT**. `applyEffective` mutates `config.models`/
- *     `config.roles` IN PLACE, and core's Runner reads `this.deps.models/roles` per task off that very
- *     reference. Both brains re-resolve `model.baseUrl || config.baseUrl` inside `buildRequest()` on every
- *     call (core 2.1.0 `brain/openai.js` + `brain/anthropic.js`), so a moved gateway takes effect on the
- *     next task with no restart.
- *   - the same plane under a **tier-frozen** Runner — deferred, not hot: core expands a PRIVATE catalog copy
- *     at construction, so `main` defers the whole plane and the `models-tiers` restart slice signals.
- *   - **`degrade-route`** — the one genuinely boot-frozen catalog consumer left: reactive degrade
- *     (`MODEL_DEGRADE_REACTIVE`) bakes the target Model + its gateway + its key into the brain composition
- *     at boot. It cannot be hot-applied without rebuilding the brain, so it is registered on the existing
- *     restartRequired /health contract instead (see `restart-signal.ts`). Fail-loud beats serving a stale
- *     gateway silently on the rate-limit path.
- *   - skills/mcp/scenarios/runtime-gates — restart-to-apply by construction (baked into the boot wiring).
- *
- * (design/158 A13, internal-lossless) This module is now a FACADE: the implementation lives in
- * `src/config-center/` split by responsibility group (HTTP client / EffectiveConfig application /
- * restart-signal detection / skills+MCP consumption). Every symbol below is re-exported UNCHANGED —
- * existing `from "./sema-registry.js"` / `from "../sema-registry.js"` imports need zero changes.
- */
-export { fetchEffective, fetchPrincipalCaps, ConfigCenterHttpError, fetchSkillContent, fetchPromptArtifact, fetchPromptBlob, } from "./config-center/http-client.js";
-export { mutateInPlace, applyEffective, applyRuntimeGates, applyRuntimeHot, resolveDefaultModelName, logEffectiveDiff, runtimeHasActiveGate, } from "./config-center/apply-effective.js";
-export { restartReasons, planeHasActiveTiers, modelPlaneChanged, } from "./config-center/restart-signal.js";
-export { applyCenterSkills, resolveMcpServers, mcpForScenario } from "./config-center/skills-mcp.js";
-//# sourceMappingURL=sema-registry.js.map