@sema-agent/server 3.2.1 → 3.4.0

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

@@ -155,12 +155,25 @@ 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 };
+                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,
+                };
             }))).sort((a, b) => (b.severity ?? 0) - (a.severity ?? 0)); // severity DESC (listByScope is created_at ASC; stable → oldest-first within a tier)
             sendJson(res, 200, { inbox }); // CheckpointSummary (token-stripped) + objective, severity-prioritized — the assistant single inbox
             return;

package/dist/http/routes/capabilities.js

@@ -233,9 +233,12 @@ async function handleCapabilitiesBody(req, res, url, ctx, miss) {
             // only on the single-user host lane with SCHEDULER_ENABLED (multi-tenant routes scheduling to center).
             scheduler: Boolean(deps.config.schedulerEnabled && deps.config.requirePrincipal !== true && deps.config.remoteExec?.provider === "host"),
             // 2c session-sync (P1d): the /v1/sessions/:id/sync/* peer routes (manifest/blobs/import/plan). True only when
-            // the whole backend + the entry export seam + a snapshot store are all wired (so export/import + blob transfer
-            // all resolve) — absent backend ⇒ false (the routes 501); "says yes ⟺ route works".
-            sessionSync: Boolean(deps.backend && deps.sessionStorage?.exportEntries && deps.fileSnapshotStore),
+            // the whole backend + the entry export seam + the STAGED-import seam + a snapshot store are all wired (so
+            // export/import + blob transfer all resolve) — absent backend ⇒ false (the routes 501); "says yes ⟺ route works".
+            // [2024](cli 取证)beginImportStaging 必须入谓词:此前只查旧三项,而暖缓存包装店恰好转发了那三项、
+            // 漏了 staging 族 ⇒ caps 报 true 而 PUSH Phase A 恒 501 —— 「says yes ⟺ route works」被实测证否。
+            // 功能半场(包装店补转发)已同批修;这里是诚实半场,兜住任何「能导出但不能 staged 导入」的店形。
+            sessionSync: Boolean(deps.backend && deps.sessionStorage?.exportEntries && deps.sessionStorage?.beginImportStaging && deps.fileSnapshotStore),
             // SendUserFile(S3 双轨公网直链,契约 settled 2026-07-14):flag=READY 语义(F7 codex 审)——
             // emitter 存在(=工具真挂载,lane/租户/签发面三门在 main.ts 已判)∧ 公网端点在场(publicEndpoint
             // 缺席时 issue()/prepareDirectUpload() 一律 fail-loud,工具挂着也必失败)。"says yes ⟺ 调用真能

package/dist/http/routes/session-sync.js

@@ -1,9 +1,9 @@
 import { once } from "node:events";
 import { randomBytes, createHash } from "node:crypto";
-import { sessionLogDigest, sessionLogDigestsComparable, uuidv7, StreamingImportValidator, SessionError, SessionPolicyError } from "@sema-agent/core";
+import { sessionLogDigest, sessionLogDigestsComparable, StreamingImportValidator, SessionError, SessionPolicyError } from "@sema-agent/core";
 import { StringDecoder } from "node:string_decoder";
-import { exportSession, exportSessionManifest, importSession, classifySyncRelationshipByIds, SyncConflictError, stagingIdFor } from "../../session-sync.js";
-import { isUuidV7, isUuidShape } from "../../security.js";
+import { exportSessionManifest, classifySyncRelationshipByIds, SyncConflictError } from "../../session-sync.js";
+import { isUuidShape } from "../../security.js";
 import { sendJson, sendError, msg } from "../send.js";
 import { gatedPrincipal, explicitOperatorOk } from "../principal-gate.js";
 /** 2c session-sync PUT /sync/blobs/:hash per-blob upload cap. A snapshot blob is ONE file's bytes, bounded by core's
@@ -51,9 +51,11 @@ async function handleSessionSyncBody(req, res, url, ctx, miss) {
     const { pendingStagings, importLeases, touchImportLease, cleanupStaging } = ctx.local.sessionSync;
     // ── 2c session-sync (P1d) — the cloud as a SYNC PEER (docs/DESIGN-session-sync.md §15 + §5–§10) ──────────────
     // The real 2c topology is TWO PROCESSES (the local shell's local backend + this cloud service); these routes let
-    // the local peer PULL a session's whole state out of the cloud or PUSH its own in. exportSession/importSession
-    // (src/session-sync.ts) fan out across ALL four session subsystems (entries + fileSnapshot + sessionPolicy +
-    // resumeAnchor) — they need the WHOLE backend (deps.backend), not the individual stores. Every route is
+    // the local peer PULL a session's whole state out of the cloud or PUSH its own in. Both halves are STREAMING
+    // implementations that fan out across ALL four session subsystems (entries + fileSnapshot + sessionPolicy +
+    // resumeAnchor) IN-ROUTE (PULL = exportSessionManifest + keyset-paged NDJSON; PUSH = two-phase staging re-running
+    // the §8 fanout below) — they need the WHOLE backend (deps.backend), not the individual stores. The whole-bundle
+    // exportSession/importSession orchestrators are NOT called here (#51 死码判定,见 src/session-sync.ts 顶注). Every route is
     // owner-gated like fork/delete (§9): a PULL 404s a non-owner (no exfiltration oracle); a PUSH re-stamps the
     // imported owner to the AUTHENTICATED principal (the bundle's owner is ignored). 501 when no durable session
     // store is wired (parity with fork: capability says yes ⟺ the route resolves).

package/dist/http/server.d.ts

@@ -138,11 +138,17 @@ export interface ServiceStoreDeps {
     /** SendUserFile 账本(多租户治理面):scope↔object 映射的读面 GET /v1/sendfile-links。present ⇔ 签发面
      *  已配 AND 有 store backend(main.ts 建;写点在两条 send lane 的 withLedgerRecording)。 */
     sendFileLedger?: import("../plugins/send-file-ledger.js").SendFileLedger;
-    /** 2c session-sync (P1d) — the WHOLE durable backend, so the `/v1/sessions/:id/sync/*` routes can call
-     *  exportSession/importSession (src/session-sync.ts), which fan out across ALL four session subsystems
-     *  (session entries + fileSnapshot blobs/manifests + sessionPolicy + resumeAnchor) in the §8 fail-closed atomic
-     *  order. The individual stores above are wired for the per-feature routes; the sync routes need the backend
-     *  itself because the orchestrator coordinates the four together (a route can't reassemble it from the parts —
+    /** 2c session-sync (P1d) — the WHOLE durable backend, so the `/v1/sessions/:id/sync/*` routes can fan out across
+     *  ALL four session subsystems (session entries + fileSnapshot blobs/manifests + sessionPolicy + resumeAnchor)
+     *  in the §8 fail-closed atomic order.
+     *  🔴 2026-07-29 纠正:这里原写「…so the routes can call **exportSession/importSession**」——**不成立**。
+     *  两条路由早已是**流式**实现(PULL=exportSessionManifest + keyset 分页 NDJSON;PUSH=两阶段 staging,
+     *  §8 扇出**在路由内自己重写了一遍**,直接调各 store),`grep exportSession src/http/` 零调用点。
+     *  那两个整包编排器现为 **test-only**(见 src/session-sync.ts 顶注的判定与机器门)。留着这句错指路的
+     *  代价是:下一个人会以为整包路径还活着,并按它去推断内存/原子性行为(而 importSession 恰是 §1.5 的
+     *  OOM 形)。理由仍成立、结论改了 —— backend 依旧要整个传,因为四个 store 必须同源。
+     *  The individual stores above are wired for the per-feature routes; the sync routes need the backend
+     *  itself because they coordinate the four together (a route can't reassemble it from the parts —
      *  `backend.session()`/`fileSnapshot()`/`sessionPolicy()`/`resumeAnchor()` must come from ONE backend). Present
      *  whenever a durable backend (tidb/pg/local) is; absent on the env-only/no-backend worker (the routes 501). */
     backend?: StoreBackend;

package/dist/http/server.js

@@ -6,7 +6,6 @@ import { decideParkedAgent, findParkedAgentForCheckpoint } from "../parked-decid
 import { matchCatalogModel } from "../model-select.js";
 import {} from "../config-center/facade.js";
 import { HttpError, principalFrom, verifiedPrincipal, setSsoPrincipal, ssoVerifiedPrincipal, setSsoScope, isUuidV7, verifyDirectDoorProof } from "../security.js";
-import { exportSession, importSession } from "../session-sync.js";
 import {} from "../memory-sync.js";
 import { MAX_SETTINGS_OUTPUT_STYLE_CHARS, MAX_SETTINGS_PERMISSION_RULES, MAX_SETTINGS_ENV_VARS, MAX_SETTINGS_ENV_KEY_CHARS, MAX_SETTINGS_ENV_VALUE_CHARS } from "../task-settings.js";
 import { parseHooksConfig } from "../hooks/hook-runner.js";

package/dist/main.js

@@ -676,9 +676,11 @@ async function main() {
         imageBakes,
         outcomeSink: outcomeSink ? outcomeSink : undefined, // P2: GET /v1/outcomes 读面(design/73 §7.2 仪表盘底料)
         sendFileLedger: sendFileLedger ? sendFileLedger : undefined, // SendUserFile 账本读面:GET /v1/sendfile-links(owner-scope 镜像 sessions list)
-        // 2c session-sync (P1d): the WHOLE backend so the /v1/sessions/:id/sync/* routes can call exportSession/
-        // importSession (they fan out across session entries + fileSnapshot + sessionPolicy + resumeAnchor, which must
-        // come from ONE backend in the §8 atomic order). Undefined-safe: the env-only/no-backend worker 501s the routes.
+        // 2c session-sync (P1d): the WHOLE backend, because the /v1/sessions/:id/sync/* routes fan out across session
+        // entries + fileSnapshot + sessionPolicy + resumeAnchor, which must come from ONE backend in the §8 atomic
+        // order. (2026-07-29 纠正:原写「so the routes can call exportSession/importSession」——路由早已是流式实现,
+        // 不调那两个整包编排器;它们现为 test-only,判定见 src/session-sync.ts 顶注。理由不变,指路改对。)
+        // Undefined-safe: the env-only/no-backend worker 501s the routes.
         backend: backend ? backend : undefined,
     };
     /** 进程内活体协调面(本副本 only,重启即空:HITL 协调器/可 steer 句柄注册表/总线/收件箱) */

package/dist/plugins/caching-session-store.d.ts

@@ -1,5 +1,6 @@
 import type { AcquiredSession, SessionStore, SessionTreeEntry } from "@sema-agent/core";
 import type { SessionListItem } from "../security.js";
+import type { StagingHandle } from "../session-sync-kernel.js";
 export interface CachingOptions {
     /** Idle seconds a woken session is kept warm. 0 disables caching (pure passthrough). */
     ttlSec: number;
@@ -79,6 +80,17 @@ export declare class CachingSessionStore implements SessionStore {
     /** 轴A #1(1.254):core B-17 forget 面(evict 本地 + 转发 inner 可选面)。 */
     forget?: (sessionId: string) => void | Promise<void>;
     readonly importEntries?: (sessionId: string, owner: string | null, entries: SessionTreeEntry[]) => Promise<void>;
+    /** [2024](cli 取证)2c session-sync P1d-β — delegated STAGED import seam. 此前 staging 族不在本类的逐方法
+     *  转发白名单里 ⇒ 默认部署(SESSION_CACHE_TTL_SEC=300 把真店包进本类)PUSH Phase A 恒 501
+     *  `capability.session_store_required`,而 capabilities().sessionSync 谓词三项(backend/exportEntries/
+     *  fileSnapshotStore)都被转发了 ⇒ 照报 true(能力面谎)。转发形:handle 的 `commit` 是唯一写真 id 的
+     *  时刻,成功后逐出该 id 的暖 handle + S25 指纹(importEntries/replaceEntries 同纪律);`abort` 只丢
+     *  staging 行、不碰真 id ⇒ 不逐出。 */
+    readonly beginImportStaging?: (realSessionId: string, token: string) => StagingHandle;
+    /** Staging 清扫面(kernel `ImportStagingStore.sweepStagingSessions`)。当下 reaper 走 `backend.session()`
+     *  裸店、不经本包装,但 security.ts 的 OwnerAwareSessionStore 契约列了它 —— 经 sessionStorage 消费的
+     *  未来调用方不该静默 no-op,与 beginImportStaging 同批补齐(同一类白名单缺口)。 */
+    readonly sweepStagingSessions?: () => Promise<number>;
     /** 2c session-sync (§7/§8) — delegated IDEMPOTENT replace; like importEntries it writes durable state under
      *  `sessionId`, so a stale warm handle for that id is evicted on success (next acquire re-wakes from the new log). */
     readonly replaceEntries?: (sessionId: string, owner: string | null, entries: SessionTreeEntry[]) => Promise<void>;

package/dist/plugins/caching-session-store.js

@@ -55,6 +55,17 @@ export class CachingSessionStore {
     /** 轴A #1(1.254):core B-17 forget 面(evict 本地 + 转发 inner 可选面)。 */
     forget;
     importEntries;
+    /** [2024](cli 取证)2c session-sync P1d-β — delegated STAGED import seam. 此前 staging 族不在本类的逐方法
+     *  转发白名单里 ⇒ 默认部署(SESSION_CACHE_TTL_SEC=300 把真店包进本类)PUSH Phase A 恒 501
+     *  `capability.session_store_required`,而 capabilities().sessionSync 谓词三项(backend/exportEntries/
+     *  fileSnapshotStore)都被转发了 ⇒ 照报 true(能力面谎)。转发形:handle 的 `commit` 是唯一写真 id 的
+     *  时刻,成功后逐出该 id 的暖 handle + S25 指纹(importEntries/replaceEntries 同纪律);`abort` 只丢
+     *  staging 行、不碰真 id ⇒ 不逐出。 */
+    beginImportStaging;
+    /** Staging 清扫面(kernel `ImportStagingStore.sweepStagingSessions`)。当下 reaper 走 `backend.session()`
+     *  裸店、不经本包装,但 security.ts 的 OwnerAwareSessionStore 契约列了它 —— 经 sessionStorage 消费的
+     *  未来调用方不该静默 no-op,与 beginImportStaging 同批补齐(同一类白名单缺口)。 */
+    sweepStagingSessions;
     /** 2c session-sync (§7/§8) — delegated IDEMPOTENT replace; like importEntries it writes durable state under
      *  `sessionId`, so a stale warm handle for that id is evicted on success (next acquire re-wakes from the new log). */
     replaceEntries;
@@ -116,6 +127,29 @@ export class CachingSessionStore {
                 this.evict(sessionId);
             };
         }
+        if (ownerAware.beginImportStaging) {
+            // [2024] staged import(P1d-β)经包装店贯通:handle 逐字段代理,只有 `commit`(唯一写真 id 的时刻)
+            // 加了成功后逐出——与上面 importEntries/replaceEntries 完全同款的纪律;abort 不写真 id,不逐出。
+            const begin = ownerAware.beginImportStaging.bind(inner);
+            this.beginImportStaging = (realSessionId, token) => {
+                const h = begin(realSessionId, token);
+                return {
+                    stagingId: h.stagingId,
+                    realSessionId: h.realSessionId,
+                    appendBatch: (entries) => h.appendBatch(entries),
+                    commit: async (owner, o) => {
+                        const r = await h.commit(owner, o);
+                        if (this.cache.has(realSessionId))
+                            opts.onConflictEvict?.(realSessionId); // S25: a warm entry was live → stale-affinity fingerprint
+                        this.evict(realSessionId);
+                        return r;
+                    },
+                    abort: () => h.abort(),
+                };
+            };
+        }
+        if (ownerAware.sweepStagingSessions)
+            this.sweepStagingSessions = ownerAware.sweepStagingSessions.bind(inner);
         if (ownerAware.deleteSession) {
             // A durable delete must also drop the deleted session from THIS warm cache (else a stale cached handle
             // could keep serving a purged session until its idle TTL). Wrap to evict on success.

package/dist/session-sync.d.ts

@@ -89,7 +89,26 @@ export interface SessionManifest {
  *
  * NB (P1d-α): the HTTP PULL no longer uses this — it uses {@link exportSessionManifest} (entries lifted off the wire)
  * + the keyset-paged `exportEntriesStream` NDJSON route so memory is bounded by ROW COUNT, not the whole-log array.
- * exportSession (entries-inline) STAYS for the local same-process import path, P1d-β (PUSH), and the tests.
+ *
+ * 🔴 **TEST-ONLY(2026-07-29 死码判定,#51 / [2012] cli 反查;上一版这段 NB 的结论已过期)**。
+ * 上面那句「STAYS for the local same-process import path, P1d-β (PUSH), and the tests」**三条里两条已不成立**:
+ * 逐条亲验(`grep -rn 'exportSession\|importSession' src/`)——
+ *   · **本地同进程 import 路径**:不存在这样的调用点(全仓零处);
+ *   · **P1d-β(PUSH)**:路由改成了两阶段 staging + NDJSON 流,§8 扇出**在路由里自己重写了一遍**
+ *     (`src/http/routes/session-sync.ts` 的 commit 链直接调 `handle.commit` / `importManifest` / `putRules` /
+ *     `resumeAnchorStore`),**不经过** {@link importSession};
+ *   · **tests**:成立,且是**唯一**成立的一条(三个测试文件在用)。
+ * 还有两处**只 import 不调用**的死接线(`src/http/server.ts` / `src/http/routes/session-sync.ts`)——本次已摘;
+ * 它们能活到今天是因为 tsconfig 没开 `noUnusedLocals`。这两个函数也**不在发布公面**上
+ * (`package.json` 的 exports 只有 `.` / `./main` / `./package.json`,`src/index.ts` 不 re-export 本模块)。
+ *
+ * **为什么本批只判定 + 上机器门,没有直接删**:两个仍在用它们的测试文件
+ * (`session-sync-fanout-characterization` / `session-sync-fanout-crash-recovery`)是 §8 崩溃/重试幂等语义的
+ * **唯一可执行验证**,并且其中 B4/G1 两笔 `it.fails` 记的是 `classifySyncRelationshipByIds` 的**分类缺口**——
+ * 而那个分类器**在活路由上仍被调用**(`routes/session-sync.ts:312` / `:632`)。直接删函数=连带删掉两套
+ * 覆盖与一笔**仍然有效**的欠账记账,那正是本仓 `vitest.config.ts` 里写死的判据「覆盖丢失伪装成绿,
+ * 比假红更坏」。⇒ **删除的前置条件**是先把 B4/G1 重锚到活的流式路径上;做完那件,这两个函数连同它们的
+ * 测试可一并摘除。判定与机器门见 `test/session-sync-routes.test.ts` 的「死码判定」describe。
  */
 export declare function exportSession(sessionId: string, srcBackend: StoreBackend): Promise<{
     bundle: SessionBundle;

package/dist/session-sync.js

@@ -30,7 +30,26 @@ function ownerAware(backend) {
  *
  * NB (P1d-α): the HTTP PULL no longer uses this — it uses {@link exportSessionManifest} (entries lifted off the wire)
  * + the keyset-paged `exportEntriesStream` NDJSON route so memory is bounded by ROW COUNT, not the whole-log array.
- * exportSession (entries-inline) STAYS for the local same-process import path, P1d-β (PUSH), and the tests.
+ *
+ * 🔴 **TEST-ONLY(2026-07-29 死码判定,#51 / [2012] cli 反查;上一版这段 NB 的结论已过期)**。
+ * 上面那句「STAYS for the local same-process import path, P1d-β (PUSH), and the tests」**三条里两条已不成立**:
+ * 逐条亲验(`grep -rn 'exportSession\|importSession' src/`)——
+ *   · **本地同进程 import 路径**:不存在这样的调用点(全仓零处);
+ *   · **P1d-β(PUSH)**:路由改成了两阶段 staging + NDJSON 流,§8 扇出**在路由里自己重写了一遍**
+ *     (`src/http/routes/session-sync.ts` 的 commit 链直接调 `handle.commit` / `importManifest` / `putRules` /
+ *     `resumeAnchorStore`),**不经过** {@link importSession};
+ *   · **tests**:成立,且是**唯一**成立的一条(三个测试文件在用)。
+ * 还有两处**只 import 不调用**的死接线(`src/http/server.ts` / `src/http/routes/session-sync.ts`)——本次已摘;
+ * 它们能活到今天是因为 tsconfig 没开 `noUnusedLocals`。这两个函数也**不在发布公面**上
+ * (`package.json` 的 exports 只有 `.` / `./main` / `./package.json`,`src/index.ts` 不 re-export 本模块)。
+ *
+ * **为什么本批只判定 + 上机器门,没有直接删**:两个仍在用它们的测试文件
+ * (`session-sync-fanout-characterization` / `session-sync-fanout-crash-recovery`)是 §8 崩溃/重试幂等语义的
+ * **唯一可执行验证**,并且其中 B4/G1 两笔 `it.fails` 记的是 `classifySyncRelationshipByIds` 的**分类缺口**——
+ * 而那个分类器**在活路由上仍被调用**(`routes/session-sync.ts:312` / `:632`)。直接删函数=连带删掉两套
+ * 覆盖与一笔**仍然有效**的欠账记账,那正是本仓 `vitest.config.ts` 里写死的判据「覆盖丢失伪装成绿,
+ * 比假红更坏」。⇒ **删除的前置条件**是先把 B4/G1 重锚到活的流式路径上;做完那件,这两个函数连同它们的
+ * 测试可一并摘除。判定与机器门见 `test/session-sync-routes.test.ts` 的「死码判定」describe。
  */
 export async function exportSession(sessionId, srcBackend) {
     const session = ownerAware(srcBackend);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "3.2.1",
+  "version": "3.4.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",
@@ -53,8 +53,8 @@
     "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/registry-core": "^0.10.21",
+    "@sema-agent/core": "^2.2.0",
+    "@sema-agent/registry-core": "^0.10.24",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",
     "mysql2": "^3.22.4",
@@ -67,7 +67,7 @@
     "sharp": "^0.35.3"
   },
   "devDependencies": {
-    "@sema-agent/sdk": "^1.0.0",
+    "@sema-agent/sdk": "^1.1.0",
     "@types/libsodium-wrappers": "^0.7.14",
     "@types/node": "22.10.2",
     "@types/pg": "^8.20.0",