@inetafrica/open-claudia 3.0.27 → 3.0.28

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## v3.0.28 — /upgrade stops crying wolf on a slow roll
+
+- **A client-side `/upgrade` timeout is no longer reported as a failure.** When the bot runs inside an AgentSpace pod, `/upgrade` calls the control plane, which triggers a fire-and-forget rollout and returns 202. If the pod is mid-roll its own in-flight request gets cut off, so the 15s HTTP wait would expire and the bot announced "Upgrade request failed … timeout" — a false negative that invited repeated re-runs (and a storm of redundant rollouts, seen as 11 ReplicaSets in 7 minutes). A timed-out request now surfaces as **pending** ("sent but the reply timed out — likely because I'm already restarting; give it a minute"), and the request timeout is raised 15s → 30s.
+- **Pairs with a control-plane probe fix (the actual root cause).** The pod's `/health` probes carried no `timeoutSeconds`, so k8s defaulted it to 1s; a cold-start event-loop stall past 1s flapped the liveness probe and SIGTERM'd the pod in a restart loop. That fix — explicit `timeoutSeconds: 5` on every probe and liveness `failureThreshold` 3 → 5 — ships in the agent-space control plane and reaches existing pods on their next reconcile (`/cluster sync`).
+- **Agent-space / OpenClaw:** no new deps, no new env, no schema change; Docker image builds identically (FROM the pre-baked `:base`). Existing pods pick this up on their next approved upgrade.
+
 ## v3.0.27 — Agency ledger, advisory "what's next", owner-guardrail capture, and a reboot that waits for the turn to end
 
 - **`/agenda` — one read-only work list across everything (Track B0).** A new aggregator normalises your persistent tasks, `spaces mine`, and connector inbox/notifications into a single list (source, title, status, due, staleness, blocked-on, last-touched). Pure visibility — it reads, it never acts. `/agency` is an alias.

package/core/handlers.js

@@ -624,7 +624,7 @@ async function requestAgentSpaceUpgrade() {
       res.on("end", () => resolve({ status: res.statusCode, body: data }));
     });
     req.on("error", (e) => resolve({ status: 0, body: String(e.message || e) }));
-    req.setTimeout(15000, () => { req.destroy(new Error("timeout")); });
+    req.setTimeout(30000, () => { req.destroy(new Error("timeout")); });
     req.end();
   });
 }
@@ -678,6 +678,14 @@ register({
           await send("Upgrade requested — AgentSpace will pull latest image and restart, see you in a minute.");
           return;
         }
+        // A client-side timeout is not a failure: the control plane triggers the
+        // rollout fire-and-forget, and a pod being rolled is exactly when its own
+        // in-flight request gets cut off. Framing it as "failed" invites a retry
+        // storm of redundant rollouts, so surface it as pending instead.
+        if (result && result.status === 0 && /timeout/i.test(result.body || "")) {
+          await send("Upgrade request sent but the reply timed out — likely because I'm already restarting. Give it a minute before re-running; I should come back on the new image.");
+          return;
+        }
         await send(`Upgrade request failed (status ${result?.status || "?"}). ${(result?.body || "").slice(0, 300)}`);
         return;
       } catch (e) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inetafrica/open-claudia",
-  "version": "3.0.27",
+  "version": "3.0.28",
   "description": "An always-on, provider-agnostic coding-agent harness for Claude Code and OpenAI Codex via chat",
   "main": "bot.js",
   "bin": {

package/test-provider-language.js

@@ -32,18 +32,17 @@ assert.doesNotMatch(setup, /Your Claude Code bot is connected|Description=Claude
 
 const pkg = JSON.parse(read("package.json"));
 assert.match(pkg.description, /provider-agnostic coding-agent harness/i);
-// 3.0.27 approved by Sumeet 2026-07-15 ("work through till it's done and push it
-// out"): the non-gated architecture batch. (1) X0 — always-on prompt-budget
-// instrumentation: measure the fixed floor vs per-turn recall payload, telemetry
-// only (no prompt change, no trim). (2) B0 — /agenda read-only work ledger
-// (tasks + Spaces + notifications). (3) B1 — /next advisory deliberation that
-// proposes a pick and acts on nothing. (4) C0/C1 — owner-guardrail capture:
-// "from now on / never / stop" statements become always-loaded lessons (asked or
-// auto-captured with announce + one-tap undo), owner-only, never from externals.
-// (5) Turn-aware reboot: the Telegram 10-min poll-wedge backstop defers its
-// self-exit while any turn is running/queued so a restart never interrupts
-// in-flight work. B2+ autonomy and Track A stay gated.
-assert.strictEqual(pkg.version, "3.0.27", "release version must remain unchanged without explicit approval");
+// 3.0.28 approved by Sumeet 2026-07-15 ("Yep fix them up just ensure no data
+// loss"): the bot-side half of the restart-loop fix. When /upgrade runs inside
+// an AgentSpace pod it calls the control plane, which fires a rollout and
+// returns 202; if the pod is mid-roll its own in-flight request is cut off, so
+// the client HTTP wait expired and the bot announced "Upgrade request failed …
+// timeout" — a false negative that invited a retry storm of redundant rollouts.
+// A timed-out request now surfaces as pending (not failed), and the request
+// timeout is raised 15s->30s. Pairs with the control-plane probe fix (explicit
+// timeoutSeconds + higher liveness threshold) that removes the root-cause
+// SIGTERM flapping. No autonomy change; B2+ and Track A stay gated.
+assert.strictEqual(pkg.version, "3.0.28", "release version must remain unchanged without explicit approval");
 for (const keyword of ["claude", "codex", "coding-agent", "provider-agnostic"]) {
   assert.ok(pkg.keywords.includes(keyword), `package keyword missing: ${keyword}`);
 }