@love-moon/conductor-sdk 0.7.6 → 0.7.7

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @love-moon/conductor-sdk
 
+## 0.7.7
+
+### Patch Changes
+
+- 400f3a7: Report a terminal task status when a stop request finds no active process, so a
+  task whose Fire already died converges instead of sitting in `killing` forever.
+
+  Drop queued terminal status events before an in-place restart reuses a working
+  directory. The durable upstream outbox lives inside that directory, so an
+  undelivered `KILLED` from the previous run was flushed on startup and killed the
+  task that had just finished resuming.
+
 ## 0.7.6
 
 ### Patch Changes

package/dist/outbox/store.d.ts

@@ -21,6 +21,30 @@ export declare class DurableUpstreamOutboxStore {
         payload: Record<string, unknown>;
     }): DurableUpstreamEvent;
     remove(stableId: string): void;
+    /**
+     * Discard queued terminal `task_status_update` events (KILLED / COMPLETED).
+     *
+     * This outbox lives INSIDE the fire's working directory, and an in-place
+     * restart deliberately re-uses that same directory (the daemon sets
+     * `CONDUCTOR_RESUME_CWD` so `--resume` finds the original project). That
+     * means a terminal status the PREVIOUS run failed to deliver — e.g. its
+     * websocket dropped while it was being stopped — is still sitting on disk
+     * when the NEXT run starts, and the startup flush delivers it against the
+     * task that was just brought back to life. The server marks the task
+     * `killed`, then answers the newly-attached fire with
+     * `stop_task(task_already_killed)` and shoots it down seconds after it
+     * finished resuming.
+     *
+     * A terminal status from a superseded run is definitionally obsolete: the
+     * task has since been restarted, so "that run ended" is no longer news the
+     * server can act on correctly. Drop those and keep everything else —
+     * `sdk_message` entries are real conversation content that must still be
+     * delivered, and `task_stop_ack` / `agent_command_ack` are idempotent
+     * bookkeeping whose delivery actually clears stale server-side outbox rows.
+     *
+     * Returns the dropped entries so callers can log exactly what was discarded.
+     */
+    dropPendingTerminalStatusEvents(): DurableUpstreamEvent[];
     markRetry(stableId: string, delayMs: number): DurableUpstreamEvent | null;
     listReady(nowMs?: number): DurableUpstreamEvent[];
     nextRetryDelay(nowMs?: number): number | null;

package/dist/outbox/store.js

@@ -19,6 +19,16 @@ const sleepSync = (ms) => {
         }
     }
 };
+// Terminal statuses as published by `conductor daemon` (see cli/src/daemon.js,
+// which sends the upper-case wire form). Compared case-insensitively so a
+// future lower-case producer does not silently bypass the check.
+const TERMINAL_TASK_STATUSES = new Set(['killed', 'completed']);
+const isTerminalStatusEvent = (entry) => {
+    if (entry.eventType !== 'task_status_update')
+        return false;
+    const status = entry.payload?.status;
+    return typeof status === 'string' && TERMINAL_TASK_STATUSES.has(status.trim().toLowerCase());
+};
 const sanitizeScopeId = (scopeId) => scopeId
     .trim()
     .replace(/[^a-zA-Z0-9._-]+/g, '_')
@@ -66,6 +76,40 @@ export class DurableUpstreamOutboxStore {
             this.saveUnlocked(entries);
         });
     }
+    /**
+     * Discard queued terminal `task_status_update` events (KILLED / COMPLETED).
+     *
+     * This outbox lives INSIDE the fire's working directory, and an in-place
+     * restart deliberately re-uses that same directory (the daemon sets
+     * `CONDUCTOR_RESUME_CWD` so `--resume` finds the original project). That
+     * means a terminal status the PREVIOUS run failed to deliver — e.g. its
+     * websocket dropped while it was being stopped — is still sitting on disk
+     * when the NEXT run starts, and the startup flush delivers it against the
+     * task that was just brought back to life. The server marks the task
+     * `killed`, then answers the newly-attached fire with
+     * `stop_task(task_already_killed)` and shoots it down seconds after it
+     * finished resuming.
+     *
+     * A terminal status from a superseded run is definitionally obsolete: the
+     * task has since been restarted, so "that run ended" is no longer news the
+     * server can act on correctly. Drop those and keep everything else —
+     * `sdk_message` entries are real conversation content that must still be
+     * delivered, and `task_stop_ack` / `agent_command_ack` are idempotent
+     * bookkeeping whose delivery actually clears stale server-side outbox rows.
+     *
+     * Returns the dropped entries so callers can log exactly what was discarded.
+     */
+    dropPendingTerminalStatusEvents() {
+        return this.withLock(() => {
+            const entries = this.loadUnlocked();
+            const dropped = entries.filter(isTerminalStatusEvent);
+            if (dropped.length === 0) {
+                return [];
+            }
+            this.saveUnlocked(entries.filter((entry) => !isTerminalStatusEvent(entry)));
+            return dropped;
+        });
+    }
     markRetry(stableId, delayMs) {
         return this.withLock(() => {
             const entries = this.loadUnlocked();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@love-moon/conductor-sdk",
-  "version": "0.7.6",
+  "version": "0.7.7",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lovemoon-ai/conductor.git"
@@ -33,5 +33,5 @@
     "typescript": "^5.6.3",
     "vitest": "^2.1.4"
   },
-  "gitCommitId": "c939df2"
+  "gitCommitId": "26b2dbb"
 }