@sema-agent/server 5.1.2 → 5.3.0

package/dist/boot/stores.js

@@ -253,7 +253,10 @@ export async function openStores(ctx) {
             mailboxStore = new TiDBMailboxStore(mysqlPool);
         }
         else if (backend?.kind === "local") {
-            mailboxStore = new FileMailboxStore(config.localDataRoot ?? localRoot);
+            // #113([2399]③→[2408] core 5.2.0 补座):腐读披露——照 roster 同形;torn-tail 静默=core 有意边界。
+            mailboxStore = new FileMailboxStore(config.localDataRoot ?? localRoot, {
+                onCorruptRead: (info) => logger.warn("mailbox_corrupt_read", { path: info.path, reason: info.reason }),
+            });
         }
         if (mailboxStore)
             logger.info("mailbox_store_enabled", { backend: pgPool ? "pg" : mysqlPool ? "tidb" : "file" });

package/dist/fleet/fleet-bus.js

@@ -668,7 +668,10 @@ export function fleetBackgroundChildPublisher(bus, log) {
         // 现状 core 只在 terminal 事件带此键(三发射点亲核)⇒ 本透传对旧 core 惰性;core 停 spawn/tick
         // 源头补上即通,tick 臂(下方 :78x)早已同姿。server 不自行以 sessionId 推导——fork lane 的
         // forkTranscriptId 与 sessionId 的等价关系归 core 所有,不在消费端烙死。
-        bus.publishTask({ id: e.taskId, name: redactSecrets(e.description ?? e.name ?? e.taskId), ...(e.agentType ? { agentType: redactSecrets(e.agentType) } : {}), ...rowTags(m), status: "running", tokens: 0, ...(e.transcriptId ? { transcriptId: e.transcriptId } : {}) });
+        // [2400] FLEET-WORKFLOWS-7:[2070]③「名不铸」的第四处——spawn 双缺 description/name 时此前 `?? e.taskId`
+        // 拿 a* handle 冒充显示名;tick 臂只在 name 在场才发 + 总线 MERGE ⇒ 假名永久留行。缺席不铸,与其余三处同判。
+        const spawnName = e.description ?? e.name;
+        bus.publishTask({ id: e.taskId, ...(spawnName !== undefined ? { name: redactSecrets(spawnName) } : {}), ...(e.agentType ? { agentType: redactSecrets(e.agentType) } : {}), ...rowTags(m), status: "running", tokens: 0, ...(e.transcriptId ? { transcriptId: e.transcriptId } : {}) });
         dlog("bg_child_event", { kind: "spawn", taskId: e.taskId, sessionScoped: e.sessionScoped, scope: m.tenantScope, hostSessionId: m.hostSessionId ?? null, parentTaskId: m.parentTaskId ?? null });
     };
     const handleTick = (e, m) => {

package/dist/http/routes/capabilities.js

@@ -127,12 +127,13 @@ async function handleCapabilitiesBody(req, res, url, ctx, miss) {
             subagentResume: Boolean(deps.subagentSteerRegistry) && Boolean(deps.runStore),
             // TaskRequest.settings (client per-request SemaSettings stamp) → projected into the engine TIGHTEN-ONLY
             // (deny-wins, after the deployment + operator baseline). v1 wires permissions + permissionMode (default/
-            // acceptEdits/plan — `bypassPermissions` is NEVER honored from settings) + model + outputStyle. `env` is
-            // DEFERRED (TaskSpec deliberately has no per-task env injection) — advertised here so the client never
-            // silently loses a setting (it can warn the user / withhold those fields).
+            // acceptEdits/plan — `bypassPermissions` is NEVER honored from settings) + model + outputStyle.
+            // `env`([2400] X-8):与真消费点同谓词——resolve-spec 的 setSessionShellEnv 只在 cwdHonored
+            // (单用户 host lane)注入 shell env;其余 lane 收到即警告忽略。此前硬编码 false 是「TaskSpec 无
+            // per-task env 注入」时代的陈旧断言(R-survey shellEnv seam 落地后失真=说没有但其实有,活能力被藏)。
             // `hooks`(hook-runner 阶段一):TRUE 当本部署会真跑 hook 命令 = 单用户闸(hook 命令跑在
             // worker host,class ② 能力授予;resolveSpec 的 taskHooks 装配同一谓词)。多租户 = false(收到警告忽略)。
-            taskSettings: { permissions: true, permissionMode: true, model: true, outputStyle: true, env: false, hooks: deps.config.requirePrincipal !== true },
+            taskSettings: { permissions: true, permissionMode: true, model: true, outputStyle: true, env: cwdHonored(deps.config), hooks: deps.config.requirePrincipal !== true },
             // [1476] R1 / [1478] R2: TaskRequest.appendSystemPrompt is accepted top-level → TaskSpec.appendSystemPrompt
             // (first-class lane for the shell's product-knowledge block). A shell probes THIS flag: false/absent ⇒ fall
             // back to the settings.outputStyle ride-along (older servers fold that into the same spec field).

package/dist/http/wire-types.d.ts

@@ -10,6 +10,10 @@ import type { AgentDefinition, McpServerSpec } from "@sema-agent/core";
 export interface TaskRequestBody {
     objective: string;
     sessionId?: string;
+    /** dispatch-gateway failover 幂等第二级:caller-minted 任务 id(uuidv7)。同 owner 重放同 id ⇒ 幂等重放;
+     *  异 owner ⇒ 409 `conflict.run_exists`;非 uuidv7 ⇒ 400 `request.id_invalid`(routes/runs.ts:192-208 真验收)。
+     *  [2400] TR-16 连带:此键此前只活在 runs.ts 读点,导出类型漏declared——CAPS-OPS-13 同族第 9 键。 */
+    taskId?: string;
     images?: Array<{
         data: string;
         mimeType: string;
@@ -159,17 +163,30 @@ export interface TaskRequestBody {
         timeoutSec?: number;
         maxOutputTokens?: number;
         maxTurns?: number;
+        deadlineNudge?: false;
+        callCapByDeadline?: false;
+        gracefulFinalize?: false;
     };
     /** design/133 (core 1.251) + G1 (core 1.253): turn-boundary attachment reminders (todo / changed-files /
-     *  plan-mode) + one-shot boundary notices (post-compaction background-task recap / deferred-tools delta). */
+     *  plan-mode) + one-shot boundary notices (post-compaction background-task recap / deferred-tools delta).
+     *  [2400] CAPS-OPS-13:本类型经 src/index.ts 导出给 embedder——键集必须与真验收面(spec-fields.ts
+     *  normalizeAttachments 10 键 / normalizeLimits 6 键)同源;此前少 8 键 ⇒ agentListing:false(唯一能关
+     *  core 默认开列表注入的通道)与三个 deadline opt-out 在类型面失踪。agentListing/skillsListing 是
+     *  boolean 透传(core DEFAULT-ON,explicit false 才关);budgetUsd/mcpInstructions 只认 literal true;
+     *  limits 三个 opt-out 只认 literal false(normalizer 同判)。 */
     attachments?: {
         todoReminder?: boolean;
+        todoReminderMode?: "baseline" | "off";
         changedFiles?: boolean | {
             maxFiles?: number;
         };
         planModeReminder?: boolean;
+        budgetUsd?: true;
         backgroundTasks?: boolean;
         toolsDelta?: boolean;
+        mcpInstructions?: true;
+        agentListing?: boolean;
+        skillsListing?: boolean;
     };
     /** C1 (core 1.219, subagent viewing pane): opt-in — forward a delegated child's live CONTENT events
      *  (text_delta/reasoning_delta/tool_start/tool_end, each stamped `parentToolCallId`) onto this run's stream/durable

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "5.1.2",
+  "version": "5.3.0",
   "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": "^5.1.0",
+    "@sema-agent/core": "^5.2.0",
     "@sema-agent/registry-core": "^0.13.0",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",
@@ -68,7 +68,7 @@
     "sharp": "^0.35.3"
   },
   "devDependencies": {
-    "@sema-agent/sdk": "^4.1.0",
+    "@sema-agent/sdk": "^4.2.0",
     "@types/libsodium-wrappers": "^0.7.14",
     "@types/node": "22.10.2",
     "@types/pg": "^8.20.0",