fix(gateway): identify failed terminal persistence

steipete · steipete · commit 715a99416658 · 2026-07-03T21:55:44.000+01:00
diff --git a/src/gateway/server-chat.agent-events.test.ts b/src/gateway/server-chat.agent-events.test.ts
@@ -2540,8 +2540,9 @@ describe("agent event handler", () => {
       updatedAt: 2_100,
       abortedLastRun: false,
     });
+    expect(logErrorMock).toHaveBeenCalledTimes(1);
     expect(logErrorMock).toHaveBeenCalledWith(
-      "gateway: failed to persist terminal session lifecycle event for run run-failed-write: Error: disk full sk-abc…3456",
+      "gateway: terminal session persistence failed session=session-failed-write run=run-failed-write error=Error: disk full sk-abc…3456",
     );
     expect(markTrackedRunTerminalPersisted).not.toHaveBeenCalled();
   });
diff --git a/src/gateway/server-chat.ts b/src/gateway/server-chat.ts
@@ -719,7 +719,7 @@ export function createAgentEventHandler({
           })
           .catch((err: unknown) => {
             logError(
-              `gateway: failed to persist terminal session lifecycle event for run ${evt.runId}: ${formatForLog(err)}`,
+              `gateway: terminal session persistence failed session=${formatForLog(sessionKey)} run=${formatForLog(evt.runId)} error=${formatForLog(err)}`,
             );
             // Persistence recovery remains tracked by the controller entry, but
             // subscribers still need a terminal projection instead of hanging.
