@sema-agent/server 2.0.1 → 3.0.0

package/dist/plugins/remote-env-host.d.ts

@@ -43,7 +43,8 @@ export interface HostEnvConfig {
      *  reports `supported:false` → INERT (no scheduler tools). Injected at boot only on the single-user host lane. */
     scheduler?: SchedulerCapability;
     /** design/103 background shell: `false` → INERT (multi-tenant host lane gate). Default (undefined) = on for the
-     *  single-user TOC host lane. `HOST_BG_ENABLED=false` is an additional global kill switch(旧名 HOST_BG_DISABLED=true 兼容期内仍认)。 */
+     *  single-user TOC host lane. `HOST_BG_ENABLED=false` is an additional global kill switch(🪦 旧名
+     *  `HOST_BG_DISABLED` 自 server 3.0.0 起是 fail-loud 墓碑:设了即拒启并指路新名,不再被读取)。 */
     backgroundShell?: boolean;
 }
 export declare class RemoteHostExecutionEnv implements RemoteExecutionEnv, SchedulerCapability, BackgroundShellCapability {

package/dist/run-local.js

@@ -291,7 +291,8 @@ export async function runLocal(argv, deps = {}) {
     // TOC local LSP (core 1.190): run-local IS the pure-local host lane, so mount core's `NodeLspManager` (local
     // child_process language servers over stdio, CC `services/lsp` parity) on the host lane. Default ON (degrades
     // gracefully to grep/read if a server binary is absent); `LSP_HOST_ENABLED=false` opts out (design/158 B4 split
-    // this lane off `LSP_ENABLED`, which still works as a back-compat opt-out). `requirePrincipal !== true`
+    // this lane off `LSP_ENABLED`; 🪦 server 3.0.0 起 `LSP_ENABLED=false` 是 fail-loud 墓碑,拒启指路新名,
+    // 不再是可用的 opt-out)。`requirePrincipal !== true`
     // keeps it uniform with main.ts (a no-op here — run-local is single-user — but never relies on that). Both runners.
     const lspManager = hostRx && config.lspHostEnabled && config.requirePrincipal !== true ? new NodeLspManager({ log: (event, fields) => logger.info(event, fields) }) : undefined;
     // Long-term memory (design/138 S1): run-local IS the single-user lane, so the file-based memory ENGINE is

package/dist/session-titler.d.ts

@@ -29,6 +29,7 @@ export interface SessionTitlerDeps {
     llm(opts: {
         prompt: string;
         timeoutMs: number;
+        model?: string;
     }): Promise<{
         ok: true;
         text: string;
@@ -47,7 +48,8 @@ export interface SessionTitlerDeps {
 }
 export interface SessionTitler {
     /** Fire-and-forget: maybe generate + persist a title for this session. Never throws, never blocks the caller. */
-    maybeTitle(sessionId: string, objective: string): void;
+    /** `model`([1992]②)= 本 turn 真实驱动的模型——带上则标题 hook 同链路,不再裸落 env 缺省。 */
+    maybeTitle(sessionId: string, objective: string, model?: string): void;
 }
 export declare const TITLE_MAX_CHARS = 80;
 /** Single line, control chars stripped, hard cap; surrounding quotes (a common LLM tic) trimmed. */

package/dist/session-titler.js

@@ -65,7 +65,7 @@ export function createSessionTitler(deps) {
         deps.logger?.warn?.("session_title_failed", { ...meta, note: "同 cause 后续降为 debug 级" });
     };
     return {
-        maybeTitle(sessionId, objective) {
+        maybeTitle(sessionId, objective, model) {
             if (!sessionId || !objective.trim())
                 return;
             if (seen.has(sessionId))
@@ -93,7 +93,7 @@ export function createSessionTitler(deps) {
                     deps.metrics?.inc("session_title_total", { outcome: "already_titled" });
                     return;
                 }
-                const r = await deps.llm({ prompt: buildTitlePrompt(objective), timeoutMs: LLM_TIMEOUT_MS });
+                const r = await deps.llm({ prompt: buildTitlePrompt(objective), timeoutMs: LLM_TIMEOUT_MS, model });
                 if (!r.ok) {
                     deps.metrics?.inc("session_title_total", { outcome: "llm_failed" });
                     logFailure(sessionId, r.error);

package/dist/trace/project.js

@@ -510,7 +510,10 @@ export function mapTraceEvent(type, seq, data) {
         case "failed":
             // BL-13: redact at the read boundary too (defense-in-depth) — covers any errorMessage that reached the
             // log un-redacted via another write path; idempotent on the BL-12-redacted catch-path message.
-            return { event: "error", data: { code: "WORKER_DOWN", message: redactSecrets(String(data.errorMessage ?? "run failed")) } };
+            // A1/A6/B(复审 2026-07-29):error 帧统一为 `{ type:"error", errorCode, message }` —— 与 sse-log /
+            // approvals 的帧同形。这一处是 3.0.0 摘 legacy `code` 键时的漏网:帧在 src/trace/ 铸,而当时的门只扫
+            // src/http/,于是"SSE error 帧机器键统一为 errorCode"的公开声明与 wire 上跑的东西不一致(门是绿的)。
+            return { event: "error", data: { type: "error", errorCode: "WORKER_DOWN", message: redactSecrets(String(data.errorMessage ?? "run failed")) } };
         default:
             return null; // compacted etc. — not a client trace event
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "2.0.1",
+  "version": "3.0.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",
@@ -23,7 +23,9 @@
     "!dist/run-local-linux-x64",
     "!dist/run-local-darwin-arm64",
     "skills",
-    "deploy/sema-up"
+    "deploy/sema-up",
+    "USAGE.md",
+    "MIGRATION.md"
   ],
   "bin": {
     "run-local": "dist/run-local.js",
@@ -51,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.0.0",
+    "@sema-agent/core": "^2.1.0",
     "@sema-agent/registry-core": "^0.10.21",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",