agent-comms 2.18.0 → 2.18.1

package/.claude-plugin/marketplace.json

@@ -15,7 +15,7 @@
         "url": "https://github.com/ExaDev/agent-comms.git"
       },
       "description": "Cross-harness LLM agent communication mesh — rooms, DMs, and presence",
-      "version": "2.18.0"
+      "version": "2.18.1"
     }
   ]
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-comms",
   "description": "Cross-harness LLM agent communication mesh — rooms, DMs, and presence",
-  "version": "2.18.0",
+  "version": "2.18.1",
   "author": {
     "name": "ExaDev"
   },

package/README.md

@@ -2,7 +2,7 @@
 
 [![GitHub](https://img.shields.io/badge/GitHub-181717?logo=github&logoColor=white)](https://github.com/ExaDev/agent-comms)
 [![npm](https://img.shields.io/badge/npm-CB3837?logo=npm&logoColor=white)](https://www.npmjs.com/package/agent-comms)
-[![version](https://img.shields.io/badge/version-2.18.0-blue)](https://github.com/ExaDev/agent-comms/releases/tag/v2.18.0)
+[![version](https://img.shields.io/badge/version-2.18.1-blue)](https://github.com/ExaDev/agent-comms/releases/tag/v2.18.1)
 [![CI](https://img.shields.io/github/actions/workflow/status/ExaDev/agent-comms/ci.yml?branch=main)](https://github.com/ExaDev/agent-comms/actions)
 
 Cross-harness communication mesh for LLM agents: rooms, DMs, presence, and visibility over TCP with zero filesystem dependencies.

package/dist/core/mcp-registry-retry.d.ts

@@ -0,0 +1,9 @@
+export declare const INITIAL_RETRY_DELAY_MS = 15000;
+export declare const MAX_RETRY_DELAY_MS = 120000;
+export declare const RETRY_BACKOFF_MULTIPLIER = 2;
+export declare const MAX_TOTAL_RETRY_MS: number;
+/** The next delay in the doubling-with-cap backoff schedule, given the delay just used. */
+export declare function nextRetryDelayMs(previousDelayMs: number): number;
+/** Recognises the MCP registry's own npm-propagation-lag error text -- the specific, recoverable failure worth retrying, as opposed to any other publish failure. */
+export declare function isNpmPropagationLag(output: string): boolean;
+//# sourceMappingURL=mcp-registry-retry.d.ts.map

package/dist/core/mcp-registry-retry.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-registry-retry.d.ts","sourceRoot":"","sources":["../../src/core/mcp-registry-retry.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,sBAAsB,QAAS,CAAC;AAC7C,eAAO,MAAM,kBAAkB,SAAU,CAAC;AAC1C,eAAO,MAAM,wBAAwB,IAAI,CAAC;AAC1C,eAAO,MAAM,kBAAkB,QAAiB,CAAC;AAEjD,2FAA2F;AAC3F,wBAAgB,gBAAgB,CAAC,eAAe,EAAE,MAAM,GAAG,MAAM,CAKhE;AAED,qKAAqK;AACrK,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAK3D"}

package/dist/core/mcp-registry-retry.js

@@ -0,0 +1,18 @@
+// Pure retry logic for scripts/publish-mcp-registry.ts, kept here rather than in the script itself so it's testable under src/test/ -- tsconfig.json's rootDir is src/, so a test there can't import from scripts/ (outside that root), while a script importing from src/ is the normal direction. The script itself keeps the actual Date.now()/spawnSync-driven retry loop, which is inherently imperative and time-based; this module holds only the two decisions that loop makes that are worth asserting deterministically.
+// The MCP registry validates a publish against the npm registry, where the version semantic-release published seconds earlier may not be visible yet. The registry's own error text says to wait and retry, so retry that failure specifically instead of failing the release job on propagation lag.
+//
+// Confirmed insufficient in production (ExaDev/agent-comms, 2026-09-13, v2.18.0): the original fixed [15, 30, 60, 120] schedule (225s total) exhausted and failed the release job while npm's own CDN still hadn't propagated the just-published version -- a real, observed lag longer than that budget, not a hypothetical one. The release job carries no timeout-minutes of its own, so there's no tight external deadline forcing a small retry budget.
+export const INITIAL_RETRY_DELAY_MS = 15_000;
+export const MAX_RETRY_DELAY_MS = 120_000;
+export const RETRY_BACKOFF_MULTIPLIER = 2;
+export const MAX_TOTAL_RETRY_MS = 15 * 60 * 1000;
+/** The next delay in the doubling-with-cap backoff schedule, given the delay just used. */
+export function nextRetryDelayMs(previousDelayMs) {
+    return Math.min(previousDelayMs * RETRY_BACKOFF_MULTIPLIER, MAX_RETRY_DELAY_MS);
+}
+/** Recognises the MCP registry's own npm-propagation-lag error text -- the specific, recoverable failure worth retrying, as opposed to any other publish failure. */
+export function isNpmPropagationLag(output) {
+    return (output.includes("was not found") &&
+        output.includes("A newly published release can take a moment"));
+}
+//# sourceMappingURL=mcp-registry-retry.js.map

package/dist/core/mcp-registry-retry.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-registry-retry.js","sourceRoot":"","sources":["../../src/core/mcp-registry-retry.ts"],"names":[],"mappings":"AAAA,mgBAAmgB;AAEngB,sSAAsS;AACtS,EAAE;AACF,6bAA6b;AAC7b,MAAM,CAAC,MAAM,sBAAsB,GAAG,MAAM,CAAC;AAC7C,MAAM,CAAC,MAAM,kBAAkB,GAAG,OAAO,CAAC;AAC1C,MAAM,CAAC,MAAM,wBAAwB,GAAG,CAAC,CAAC;AAC1C,MAAM,CAAC,MAAM,kBAAkB,GAAG,EAAE,GAAG,EAAE,GAAG,IAAI,CAAC;AAEjD,2FAA2F;AAC3F,MAAM,UAAU,gBAAgB,CAAC,eAAuB;IACtD,OAAO,IAAI,CAAC,GAAG,CACb,eAAe,GAAG,wBAAwB,EAC1C,kBAAkB,CACnB,CAAC;AACJ,CAAC;AAED,qKAAqK;AACrK,MAAM,UAAU,mBAAmB,CAAC,MAAc;IAChD,OAAO,CACL,MAAM,CAAC,QAAQ,CAAC,eAAe,CAAC;QAChC,MAAM,CAAC,QAAQ,CAAC,6CAA6C,CAAC,CAC/D,CAAC;AACJ,CAAC"}

package/dist/test/mcp-registry-retry.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=mcp-registry-retry.test.d.ts.map

package/dist/test/mcp-registry-retry.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-registry-retry.test.d.ts","sourceRoot":"","sources":["../../src/test/mcp-registry-retry.test.ts"],"names":[],"mappings":""}

package/dist/test/mcp-registry-retry.test.js

@@ -0,0 +1,33 @@
+import { describe, it } from "node:test";
+import assert from "node:assert/strict";
+import { INITIAL_RETRY_DELAY_MS, MAX_RETRY_DELAY_MS, MAX_TOTAL_RETRY_MS, isNpmPropagationLag, nextRetryDelayMs, } from "../core/mcp-registry-retry.js";
+describe("nextRetryDelayMs", () => {
+    it("doubles the previous delay", () => {
+        assert.equal(nextRetryDelayMs(INITIAL_RETRY_DELAY_MS), INITIAL_RETRY_DELAY_MS * 2);
+    });
+    it("caps at MAX_RETRY_DELAY_MS", () => {
+        assert.equal(nextRetryDelayMs(MAX_RETRY_DELAY_MS), MAX_RETRY_DELAY_MS);
+        assert.equal(nextRetryDelayMs(MAX_RETRY_DELAY_MS * 10), MAX_RETRY_DELAY_MS);
+    });
+    it("accumulates to comfortably exceed the previous, confirmed-insufficient 225-second retry budget (agent-comms v2.18.0's release job exhausted a fixed [15, 30, 60, 120] schedule while npm's own CDN still hadn't propagated the just-published version)", () => {
+        const previousBudgetMs = (15 + 30 + 60 + 120) * 1000;
+        let delayMs = INITIAL_RETRY_DELAY_MS;
+        let totalMs = 0;
+        while (totalMs < MAX_TOTAL_RETRY_MS) {
+            totalMs += delayMs;
+            delayMs = nextRetryDelayMs(delayMs);
+        }
+        assert.ok(totalMs > previousBudgetMs);
+        assert.ok(totalMs >= MAX_TOTAL_RETRY_MS);
+    });
+});
+describe("isNpmPropagationLag", () => {
+    it("recognises the MCP registry's own npm-propagation-lag error text", () => {
+        const output = "registry validation failed for package 0 (agent-comms): NPM package 'agent-comms' exists, but version '2.18.0' was not found (status: 404). A newly published release can take a moment to appear on the registry. Wait and retry, or publish version '2.18.0' before registering it";
+        assert.equal(isNpmPropagationLag(output), true);
+    });
+    it("does not misclassify an unrelated failure as propagation lag", () => {
+        assert.equal(isNpmPropagationLag("permission denied"), false);
+    });
+});
+//# sourceMappingURL=mcp-registry-retry.test.js.map

package/dist/test/mcp-registry-retry.test.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-registry-retry.test.js","sourceRoot":"","sources":["../../src/test/mcp-registry-retry.test.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,EAAE,EAAE,MAAM,WAAW,CAAC;AACzC,OAAO,MAAM,MAAM,oBAAoB,CAAC;AACxC,OAAO,EACL,sBAAsB,EACtB,kBAAkB,EAClB,kBAAkB,EAClB,mBAAmB,EACnB,gBAAgB,GACjB,MAAM,+BAA+B,CAAC;AAEvC,QAAQ,CAAC,kBAAkB,EAAE,GAAG,EAAE;IAChC,EAAE,CAAC,4BAA4B,EAAE,GAAG,EAAE;QACpC,MAAM,CAAC,KAAK,CACV,gBAAgB,CAAC,sBAAsB,CAAC,EACxC,sBAAsB,GAAG,CAAC,CAC3B,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,4BAA4B,EAAE,GAAG,EAAE;QACpC,MAAM,CAAC,KAAK,CAAC,gBAAgB,CAAC,kBAAkB,CAAC,EAAE,kBAAkB,CAAC,CAAC;QACvE,MAAM,CAAC,KAAK,CAAC,gBAAgB,CAAC,kBAAkB,GAAG,EAAE,CAAC,EAAE,kBAAkB,CAAC,CAAC;IAC9E,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,wPAAwP,EAAE,GAAG,EAAE;QAChQ,MAAM,gBAAgB,GAAG,CAAC,EAAE,GAAG,EAAE,GAAG,EAAE,GAAG,GAAG,CAAC,GAAG,IAAI,CAAC;QACrD,IAAI,OAAO,GAAG,sBAAsB,CAAC;QACrC,IAAI,OAAO,GAAG,CAAC,CAAC;QAChB,OAAO,OAAO,GAAG,kBAAkB,EAAE,CAAC;YACpC,OAAO,IAAI,OAAO,CAAC;YACnB,OAAO,GAAG,gBAAgB,CAAC,OAAO,CAAC,CAAC;QACtC,CAAC;QACD,MAAM,CAAC,EAAE,CAAC,OAAO,GAAG,gBAAgB,CAAC,CAAC;QACtC,MAAM,CAAC,EAAE,CAAC,OAAO,IAAI,kBAAkB,CAAC,CAAC;IAC3C,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC;AAEH,QAAQ,CAAC,qBAAqB,EAAE,GAAG,EAAE;IACnC,EAAE,CAAC,kEAAkE,EAAE,GAAG,EAAE;QAC1E,MAAM,MAAM,GACV,sRAAsR,CAAC;QACzR,MAAM,CAAC,KAAK,CAAC,mBAAmB,CAAC,MAAM,CAAC,EAAE,IAAI,CAAC,CAAC;IAClD,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,8DAA8D,EAAE,GAAG,EAAE;QACtE,MAAM,CAAC,KAAK,CAAC,mBAAmB,CAAC,mBAAmB,CAAC,EAAE,KAAK,CAAC,CAAC;IAChE,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-comms",
-  "version": "2.18.0",
+  "version": "2.18.1",
   "description": "Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and real-time push delivery over TCP",
   "type": "module",
   "packageManager": "pnpm@10.33.0",