@threadbase-sh/streamer 1.44.3 → 1.44.4

package/dist/cli.cjs

@@ -147568,7 +147568,12 @@ function managedToResponse(s3, ptyAttached) {
     // the durable registry, so it is a previous run's session with no process
     // behind it — `resumable`, and `historical` rather than `managed`
     // (docs/plans/live-sessions-persistence-plan.md §4, Phase 1).
-    lifecycle: ptyAttached ? "attached" : s3.rehydrated ? "resumable" : s3.failureReason != null ? "failed" : "completed",
+    // A session this run itself put on hold (grace timer, explicit hold_session,
+    // idle reaper) is the other exception: the PTY is gone the same way an exit
+    // leaves it gone, but the conversation is still resumable, not terminal —
+    // `putOnHold` records that by leaving `statusSource: "shutdown"` (the only
+    // place either runner sets it), so it is checked here alongside `rehydrated`.
+    lifecycle: ptyAttached ? "attached" : s3.rehydrated || s3.statusSource === "shutdown" ? "resumable" : s3.failureReason != null ? "failed" : "completed",
     lifecycleSource: ptyAttached ? s3.reconciled ? "reconcile" : "spawn" : s3.rehydrated ? "reconcile" : "exit",
     // We own its PTY, so `status` is the authoritative signal — no inferred
     // `activity` is attached for managed sessions.
@@ -148422,7 +148427,14 @@ var StreamerServer = class {
           // even though the registry has one — the name only appeared after a
           // restart rebuilt the row as a stub. Guarded so a runner that has not
           // derived one yet cannot blank a name set by enrichResumedSessionAsync.
-          ...session.sessionName != null && { sessionName: session.sessionName }
+          ...session.sessionName != null && { sessionName: session.sessionName },
+          // Without mirroring this, SessionStore's copy is frozen at whatever
+          // `addManaged` saw at spawn ("spawn") forever, because updateManaged
+          // is a partial merge — so managedToResponse can never tell a
+          // grace-timer/idle-reaper hold (statusSource "shutdown") apart from a
+          // genuine process exit ("process-exit"), and reports both as
+          // `lifecycle: "completed"`. See managedToResponse in session-store.ts.
+          ...session.statusSource != null && { statusSource: session.statusSource }
         });
         this.managedSessionsRepo?.recordStatus(
           session.id,