@sema-agent/server 3.21.0 → 3.22.0

package/dist/plugins/workflow-run-store-sql.js

@@ -29,11 +29,15 @@ export function slimOversizeRun(run, maxBytes) {
     blob = JSON.stringify(step2);
     return Buffer.byteLength(blob) <= maxBytes ? blob : null;
 }
-/** Dual-dialect durable `WorkflowRunStore`. See the file header for the dialect-delta ledger. */
+/** Dual-dialect durable `WorkflowRunStore`. See the file header for the dialect-delta ledger.
+ *  `onWarn` (optional, same shape as the completion-inbox's {@link InboxWarn}) is the C5 trace channel for
+ *  `update`'s oversize-slim degrade (see there) — omit it and construction/behavior is unchanged (additive). */
 export class SqlWorkflowRunStore {
     db;
-    constructor(db) {
+    onWarn;
+    constructor(db, onWarn) {
         this.db = db;
+        this.onWarn = onWarn;
     }
     /** Pick the dialect's SQL text. Both statements stay written out at the call site ON PURPOSE. */
     q(tidb, pg) {
@@ -70,6 +74,10 @@ export class SqlWorkflowRunStore {
         if (Buffer.byteLength(blob) > MAX_RUN_BLOB_BYTES) {
             // Oversize degrade (1.108 review fix): slim the payload so the write — critically the TERMINAL one —
             // still lands (a `false` here would never be retried with a smaller payload; see slimOversizeRun).
+            // C5 (2026-07-31): the degrade drops real data (phases/agents/groups → []) — that must leave a trace
+            // reaching whoever can act on it, not just a same-shaped `true` return. `onWarn` is optional so a
+            // caller that hasn't wired a sink yet keeps building/running unchanged.
+            this.onWarn?.("workflow_run_blob_oversize_slimmed", { id, scope, fullBytes: Buffer.byteLength(blob), capBytes: MAX_RUN_BLOB_BYTES });
             const slim = slimOversizeRun({ ...run, id, scope }, MAX_RUN_BLOB_BYTES);
             if (slim === null)
                 return false; // even the skeleton is oversize — keep the prior revision
@@ -342,10 +350,11 @@ export class SqlWorkflowNotifyJournalStore {
         };
     }
 }
-/** MySQL-protocol (TiDB) bindings — historical class names + ctor shapes preserved. */
+/** MySQL-protocol (TiDB) bindings — historical class names preserved; `onWarn` is an ADDITIVE optional 2nd
+ *  ctor arg (existing 1-arg call sites are unaffected — see {@link SqlWorkflowRunStore}'s C5 trace channel). */
 export class TiDBWorkflowRunStore extends SqlWorkflowRunStore {
-    constructor(pool) {
-        super(mysqlDriver(pool));
+    constructor(pool, onWarn) {
+        super(mysqlDriver(pool), onWarn);
     }
 }
 export class TiDBWorkflowCompletionInbox extends SqlWorkflowCompletionInbox {
@@ -358,10 +367,11 @@ export class TiDBWorkflowNotifyJournalStore extends SqlWorkflowNotifyJournalStor
         super(mysqlDriver(pool));
     }
 }
-/** PostgreSQL bindings — historical class names + ctor shapes preserved. */
+/** PostgreSQL bindings — historical class names preserved; `onWarn` is an ADDITIVE optional 2nd ctor arg
+ *  (existing 1-arg call sites are unaffected — see {@link SqlWorkflowRunStore}'s C5 trace channel). */
 export class PgWorkflowRunStore extends SqlWorkflowRunStore {
-    constructor(pool) {
-        super(pgDriver(pool));
+    constructor(pool, onWarn) {
+        super(pgDriver(pool), onWarn);
     }
 }
 export class PgWorkflowCompletionInbox extends SqlWorkflowCompletionInbox {

package/dist/session-sync.js

@@ -310,9 +310,12 @@ export async function importSession(bundle, getBlob, dstBackend, importingPrinci
     //    entirely (the snapshot/policy/anchor replay below is idempotent and still runs to heal anything missing). A
     //    destination without the replace seam can't accept a session at all → throw.
     // 🔴 同上(`session-sync-content.ts` 顶注):`identical` 只说明 id 集合相等,不说明内容相同。这条路上
-    // `bundle.entries` 与目的端日志都在手上 ⇒ 直接比内容摘要;不符就照常改写(不抛错、不 409)。
-    const dstEntriesForContent = await ownerAware(dstBackend).exportEntries?.(sessionId).catch(() => null) ?? null;
-    const contentEqual = rel.relation === "identical" && identicalIdsAlsoIdenticalContent(bundle.entries, dstEntriesForContent);
+    // `bundle.entries` 与目的端日志都在手上 ⇒ 直接比内容摘要;不符就照常改写(不抛错、不 409)。复用 §7 已经
+    // 读到的 `dstEntries`(同一个 dstBackend/sessionId)——这两次读之间 dst 未被任何写触碰(overwrite-dst 擦除
+    // 只在 relation 为 fork/stale 时才跑,identical 分支不可能落进那条腿),不必也不该对同一行重新 exportEntries
+    // 一次(旧实现还用 `.catch(() => null)` 把这次读的故障裸吞成"目的端为空",见下方 identicalIdsAlsoIdenticalContent
+    // 对 null 的处置——一次真实的店读故障会被悄悄当成"内容不等"而不是 fail-loud)。
+    const contentEqual = rel.relation === "identical" && identicalIdsAlsoIdenticalContent(bundle.entries, dstEntries);
     if (rel.relation !== "identical" || !contentEqual) {
         const session = ownerAware(dstBackend);
         const replaceEntries = session.replaceEntries?.bind(session);

package/package.json

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