@botbuddy/cli 1.33.1 → 1.33.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botbuddy/cli",
-  "version": "1.33.1",
+  "version": "1.33.2",
   "description": "BotBuddy — Swarm coordination CLI for multi-agent workflows",
   "type": "module",
   "bin": {

package/src/stack.mjs

@@ -805,7 +805,13 @@ export async function waitForLease(leaseId, isDone, isFailed, { timeoutSec, auth
 
 const isActive = (s) => s === "active";
 const nonQueued = (s) => s != null && s !== "queued";
-const isReaped = (s) => s === "reaping" || s === "reaped";
+// BOT-1822 (Codex round 3 P2): `reap_failed` is a distinct terminal wake
+// (accept_stack_lease_receipt's fenced-reap-failure branch) alongside the real
+// DB states "reaping"/"reaped" — a wait parked on isReaped as its failure
+// predicate must end on it too, or a `reap_failed` wake that arrives while
+// still waiting for activation is silently dropped and the wait parks until
+// its full timeout instead of surfacing the failure immediately.
+const isReaped = (s) => s === "reaping" || s === "reaped" || s === "reap_failed";
 
 /** Read-only pressure gate used before local managed-stack provisioning. */
 export async function runLocalExecPreflight(opts, runCommand = runDockerCommand) {
@@ -1833,8 +1839,38 @@ export async function runStackLifecycle(opts, childArgv, adapters = {}) {
       return cleanupResult = { ok: false, error: release?.error || release?.data?.code || "release failed" };
     }
     if (release.data.state === "reaped") return cleanupResult = { ok: true, state: "reaped" };
-    const reaped = await wait(leaseId, (state) => state === "reaped", () => false, { timeoutSec: opts.reapTimeout, auth: rpc.auth });
+    // BOT-1822 (Codex P2 round 2, extended round 3): `reap_failed` is synthetic
+    // (never a real DB state), so a Helper's failed receipt landing in the split
+    // second between this release RPC returning and the wait below registering
+    // cannot be replayed from the spine's initial snapshot the way every other
+    // signal type can — the wake is already behind the cursor, and the initial
+    // snapshot only surfaces the durable `reaping` state, which neither
+    // predicate accepts. Recover the durable failure reason directly:
+    // `stack_leases.error` (which `get_stack_lease` already returns) holds the
+    // most recent failure message regardless of which live signal was or
+    // wasn't seen.
+    const durableReapFailure = (read) => (read?.ok && read.data?.success && read.data.state === "reaping" && read.data.error)
+      ? { ok: false, error: `the lease is still reaping and may still hold containers — ${read.data.error}` }
+      : null;
+    // BOT-1822 (Codex round 3 P2): check BEFORE opening the wait, not only after
+    // it times out — a failure already persisted must be reported at once
+    // instead of burning the entire --reap-timeout waiting for a wake that will
+    // never arrive because it predates the wait's registration.
+    const preCheck = durableReapFailure(await api.get(leaseId));
+    if (preCheck) return cleanupResult = preCheck;
+    // BOT-1822 (Codex P2): a signed reap that FAILS on a provisioned (fenced) lease
+    // emits `state: "reap_failed"` — a distinct terminal outcome, never a real DB
+    // state — instead of leaving this wait to park until --reap-timeout on a reap
+    // that already failed. Report that specific outcome instead of the generic
+    // "was not proven" timeout message.
+    const reaped = await wait(leaseId, (state) => state === "reaped", (state) => state === "reap_failed", { timeoutSec: opts.reapTimeout, auth: rpc.auth });
     if (reaped?.woke || reaped?.state === "reaped") return cleanupResult = { ok: true, state: "reaped" };
+    if (reaped?.failed) return cleanupResult = { ok: false, error: "the signed reap failed and the lease may still hold containers (fenced) — see stack hygiene" };
+    // Belt-and-braces: the same race can still slip between the pre-check above
+    // and the wait registering (or the wait's own live-signal miss), so recheck
+    // once more before falling back to a generic timeout/error message.
+    const postCheck = durableReapFailure(await api.get(leaseId));
+    if (postCheck) return cleanupResult = postCheck;
     return cleanupResult = { ok: false, error: reaped?.timeout ? `signed reap did not arrive within ${opts.reapTimeout}s` : (reaped?.error || "signed reap was not proven") };
     })();
     return cleanupPromise;
@@ -1944,11 +1980,29 @@ export async function runStackLifecycle(opts, childArgv, adapters = {}) {
     }
     if (state !== "active") {
       activeWaitAbort = new AbortController();
-      const active = await wait(leaseId, (s) => s === "active", (s) => s === "reaped", { timeoutSec: provisionTimeout, auth: rpc.auth, signal: activeWaitAbort.signal });
+      // BOT-1822 (Codex P2 round 2): a provision failure now emits a live
+      // `reaping` signal (accept_stack_lease_receipt's provision-failed branch),
+      // so this wait must treat it as terminal too — not just `reaped` — or the
+      // live-wake fix is defeated: the run would still burn the FULL
+      // provisionTimeout before the belt-and-braces recheck below ever notices
+      // the lease is no longer provisioning. isReaped (== "reaping" || "reaped")
+      // already covers both; cmdUp's equivalent waits use it for this reason.
+      const active = await wait(leaseId, (s) => s === "active", isReaped, { timeoutSec: provisionTimeout, auth: rpc.auth, signal: activeWaitAbort.signal });
       activeWaitAbort = null;
       if (active?.interrupted || receivedSignal) { const cleanup = await requestCleanup(); return { exitCode: SIGNAL_EXIT[receivedSignal], outcome: "interrupted", leaseId, cleanup }; }
-      if (active?.timeout) { const cleanup = await requestCleanup(); return { exitCode: EXIT.TIMEOUT, outcome: "timeout", leaseId, error: `physical provision did not reach active in ${provisionTimeout}s`, cleanup }; }
-      if (active?.failed || active?.error || active?.auth) { const cleanup = await requestCleanup(); return { exitCode: active?.auth ? EXIT.AUTH : EXIT.LEASE_FAILED, outcome: "error", leaseId, error: active?.error || "lease was reaped before active", cleanup }; }
+      if (active?.timeout) {
+        // BOT-1822 belt-and-braces: the zero-poll wait can still miss a live
+        // `stack_lease` signal (an older server before this fix, a relay hiccup,
+        // BOT-1816's class of dropped wakes) even though the lease genuinely went
+        // active. One direct read before declaring a timeout tells that apart from
+        // a lease that truly never provisioned, instead of reaping a healthy stack.
+        const recheck = await api.get(leaseId);
+        if (!(recheck?.ok && recheck.data?.success && recheck.data.state === "active")) {
+          const cleanup = await requestCleanup();
+          return { exitCode: EXIT.TIMEOUT, outcome: "timeout", leaseId, error: `physical provision did not reach active in ${provisionTimeout}s`, cleanup };
+        }
+      }
+      if (active?.failed || active?.error || active?.auth) { const cleanup = await requestCleanup(); return { exitCode: active?.auth ? EXIT.AUTH : EXIT.LEASE_FAILED, outcome: "error", leaseId, error: active?.error || `lease ${active?.state ?? "failed"} before reaching active`, cleanup }; }
     }
     const current = await api.get(leaseId);
     if (!current?.ok || !current.data?.success || current.data.state !== "active" || !current.data.connection || typeof current.data.connection !== "object") {