fix(daemon): preserve run lifecycle timestamps across stale message PUTs

The stale-snapshot guard protected events/content/run-status/ownership but
a snapshot that omits startedAt/endedAt still nulled the daemon-written
run timestamps via upsertMessage — and saved.endedAt feeds persisted-run
telemetry, so a terminal message lost its timing data (looper review on
#6418).

Preserve stored startedAt/endedAt alongside the other daemon-owned fields
in the stale-write branch, and assert in the regression test that the
timestamps survive repeated stale PUTs.

Author: YOMXXX

apps/daemon/src/routes/project/conversations.ts

@@ -245,6 +245,11 @@ export function registerProjectConversationRoutes(app: Express, ctx: RegisterPro
       content: stored.content ?? '',
       lastRunEventId: stored.lastRunEventId,
       runStatus: stored.runStatus,
+      // Daemon-written lifecycle timestamps; a stale snapshot that omits them
+      // would otherwise null out started_at / ended_at (and endedAt feeds
+      // persisted-run telemetry).
+      startedAt: stored.startedAt,
+      endedAt: stored.endedAt,
     };
   };
 

apps/daemon/tests/stale-message-snapshot-preserves-daemon-events.test.ts

@@ -43,6 +43,8 @@ type StoredMessage = {
   lastRunEventId?: string | null;
   events?: PersistedEvent[];
   feedback?: { rating?: number };
+  startedAt?: number;
+  endedAt?: number;
 };
 
 type RunHandles = {
@@ -160,6 +162,9 @@ describe('stale web message snapshot does not wipe daemon-owned run events', ()
       'early daemon-persisted event should survive stale web snapshot PUTs',
     ).toBe(true);
     expect(after?.runStatus).toBe('succeeded');
+    // Daemon-written lifecycle timestamps survive the stale PUTs too.
+    expect(after?.startedAt).toBe(before?.startedAt);
+    expect(after?.endedAt).toBe(before?.endedAt);
     // Client-owned metadata writes still land on daemon-backed messages.
     expect(after?.feedback?.rating).toBe(1);
   });