@sema-agent/server 5.1.1 → 5.2.0

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/active-run-conflict.js

@@ -18,12 +18,18 @@ export const ACTIVE_RUN_CONFLICT_BASE_TEXT = "session already has an active run
 /** gate.kind → 它的那一个 resume 入口(sessionId/taskId 寻址,无秘密)。 */
 export function resumeEntryForGate(kind, ids) {
     switch (kind) {
+        // tool_approval / policy_ask 不是 core 现役 kind(wire 集=WIRE_GATE_KINDS 六个,type 门双向等值)——
+        // 这两臂是**耐久历史行容忍**([2373] D 类):旧 core 铸的 checkpoint 行可能带旧 kind 名,店里读出来
+        // 仍要给出真出路;不是对上游新帧的兼容臂,别当 [2354] 清理对象误删。
         case "tool_approval":
         case "human":
         case "irreversible_ask":
         case "policy_ask":
             return `/v1/approvals/${ids.sessionId}/decide`;
         case "plan_review":
+        // needs_review 与 plan_review 同入口(TASKS-RUNS-8 附注,[2400] 审计补臂):routes/tasks.ts 的
+        // needs_review park 注明文「resumable via /plan_review」——此前缺臂 ⇒ 409 体 pendingGate 丢指引。
+        case "needs_review":
             return `/v1/assistant/tasks/${ids.taskId}/plan_review`;
         case "resource_limit":
             return `/v1/assistant/tasks/${ids.taskId}/resume`;

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

@@ -508,8 +508,10 @@ async function handleApprovalsAssistantBody(req, res, url, ctx, miss) {
                 // verify-reject): an unbound decide can consume a gate that was SWAPPED after the operator's GET (see
                 // gate A, approve lands on gate B) — tolerable as a one-shot legacy quirk, NOT as the mint of a
                 // SESSION-PERSISTENT auto-approval for a tool the operator never saw. remember is a NEW contract, so
-                // it can demand the strict calling shape (the BFF already receives boundCallId/checkpointToken on the
-                // pending row). Plain decide without remember keeps the legacy unbound fallback untouched.
+                // it can demand the strict calling shape — the BFF receives boundCallId on the pending row
+                // (HITL-7 注纠,[2400] 审计:checkpointToken 从不上 pending 行,listPending 的 SELECT 无 token 列;
+                // 下面的门是「或」关系,boundCallId 单独即满足,所以旧措辞没造成真故障)。
+                // Plain decide without remember keeps the legacy unbound fallback untouched.
                 if (!body.checkpointToken && !body.boundCallId) {
                     sendError(res, 400, "remember_requires_binding", "remember requires the decision binding (echo checkpointToken and/or boundCallId from the pending approval)");
                     return;

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/routes/runs.js

@@ -542,7 +542,13 @@ async function handleRunsBody(req, res, url, ctx, miss) {
         try {
             body = (await readJson(req));
         }
-        catch {
+        catch (e) {
+            // TASKS-RUNS-5([2400] 审计):readJson 的 HttpError(413 超限)原样透传——裸 catch 折成
+            // 400 invalid_json 会让 9 MiB 合法 JSON 被报「JSON 非法」(compact 腿是既有对照组正确形)。
+            if (e instanceof HttpError) {
+                sendError(res, e.status, httpErrorCode(e.status, e.code), e.message);
+                return;
+            }
             sendError(res, 400, "request.invalid_json", "invalid JSON body");
             return;
         }
@@ -856,7 +862,11 @@ async function handleRunsBody(req, res, url, ctx, miss) {
         try {
             body = (await readJson(req));
         }
-        catch {
+        catch (e) {
+            if (e instanceof HttpError) {
+                sendError(res, e.status, httpErrorCode(e.status, e.code), e.message);
+                return;
+            } // TASKS-RUNS-5 同族
             sendError(res, 400, "request.invalid_json", "invalid JSON body");
             return;
         }
@@ -1187,7 +1197,11 @@ async function handleRunVerbsBody(req, res, url, ctx, miss) {
         try {
             body = (await readJson(req));
         }
-        catch {
+        catch (e) {
+            if (e instanceof HttpError) {
+                sendError(res, e.status, httpErrorCode(e.status, e.code), e.message);
+                return;
+            } // TASKS-RUNS-5 同族
             sendError(res, 400, "request.invalid_json", "invalid JSON body");
             return;
         }

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

@@ -159,17 +159,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/dist/runs.js

@@ -697,8 +697,10 @@ promptManifests) {
             }
             // E12 (shell-host contract): after a COMPLETED run, pull core's opt-in post-completion prompt suggestions (a fire-and-forget
             // pass in core; suggestions() never rejects + resolves to [] when off / not completed / empty). UNTRUSTED model
-            // text for the shell UI ONLY → redact + persist as a `suggestions` event so the shell reads it off the events tail
-            // (like model_usage); NEVER re-fed to a model. Gated on a COMPLETED terminal — a suspended/parked/failed leg has
+            // text for the shell UI ONLY → redact + persist as a `suggestions` event on the durable ledger; NEVER re-fed to a
+            // model. ⚠️ 读法(TASKS-RUNS-1 注漂移修,[2400] 审计):它落账在 setTerminal **之后**,而 live tail
+            // (sse-log)在终态时有意**不投递**这一帧(见 sse-log.ts 注)——消费契约是 `await result()` 后从
+            // `GET /v1/runs/:id` 的 RunRecord.suggestions 读,**不是**从 events tail 等它。 Gated on a COMPLETED terminal — a suspended/parked/failed leg has
             // none (core also returns [] for a non-completed task; the explicit status gate avoids the needless call + pins the
             // completed-only contract rather than depending on core's guard).
             if (spec.suggestNextPrompts && reached?.kind === "done" && reached.result.status === "completed") {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "5.1.1",
+  "version": "5.2.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",