@relaymessenger/openclaw-plugin 0.4.8-staging.7 → 0.4.8-staging.9

package/contracts/relay-v1.lock.json

@@ -1,16 +1,16 @@
 {
   "relayServer": {
     "repository": "RelayMessenger/Relay-Server",
-    "commit": "b4478d218d71b1f0c2bdcc0a90de37503a03ea7c",
+    "commit": "bf085edc35814d4c991f94e6b430aab5df3fd686",
     "openapiPath": "contracts/developer/openapi.yaml",
-    "sha256": "0711806487853a7962d5f85e35895244019411fb6b6436a37d250a604e05969c"
+    "sha256": "baf2839ae8df9d1478f7a8c8457e99f54f4a1563c8439fc7ff05bb2492a7e6f4"
   },
   "relaySdk": {
     "package": "@relaymessenger/sdk",
-    "version": "0.3.7-staging.7",
-    "integrity": "sha512-yjFfQSwlVXFZjQCRAM9ozjm2WYG6VGs4wI3WZHtHn9+P6Smputdaog/5Z73ClePWuzhQWewDMpviSYQ2dTevgA==",
-    "operationsSha256": "ecd5095dee3924ba4b984435101d39380efabecc8f252cd82567b341005b2a19",
-    "workspaceOpenapiSha256": "0711806487853a7962d5f85e35895244019411fb6b6436a37d250a604e05969c",
+    "version": "0.3.7-staging.12",
+    "integrity": "sha512-qFTDN5uZ/xt/5nlSDEvs3Lsxn2ej6OaQHuRJrsgXy7+2KYMH5IELjN2QeFMe4PzQdhiH7EbC2XgtrcV6EdbfMw==",
+    "operationsSha256": "e094bf711e65ec5d37c2ca0203cf589be5747308aef8d590fd7cc5af0ac71564",
+    "workspaceOpenapiSha256": "baf2839ae8df9d1478f7a8c8457e99f54f4a1563c8439fc7ff05bb2492a7e6f4",
     "usedOperations": [
       {
         "method": "GET",

package/dist/src/inbound.js

@@ -58,9 +58,8 @@ export function buildRelayInboundFacts(event) {
     const selection = selectionReply(event.data.parts, event.data.reply_to);
     const fromAgent = event.data.sender_handle.kind === "agent";
     // Another agent's Message is named by the answer, as Relay's CLI bridges
-    // do (packages/cli/src/bridge-turn.ts, PR 366): Relay's A2A door gives a
-    // calling agent only the answer whose reply_to names its Message
-    // (Relay-Server a2a.ts replyTo). A Message that opens with buttons or a
+    // do (packages/cli/src/bridge-turn.ts, PR 366), so an agent that sent
+    // several knows which one is answered. A Message that opens with buttons or a
     // selection is not named: an agent may not reply to those parts, and a
     // reply names part 0.
     const opening = event.data.parts[0]?.type;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@relaymessenger/openclaw-plugin",
-  "version": "0.4.8-staging.7",
+  "version": "0.4.8-staging.9",
   "description": "Native Relay channel plugin for OpenClaw",
   "license": "MIT",
   "type": "module",
@@ -37,7 +37,7 @@
     "prepack": "npm run build"
   },
   "dependencies": {
-    "@relaymessenger/sdk": "0.3.7-staging.7"
+    "@relaymessenger/sdk": "0.3.7-staging.12"
   },
   "devDependencies": {
     "@types/node": "^26.6.2",

package/src/inbound.ts

@@ -80,9 +80,8 @@ export function buildRelayInboundFacts(
   const selection = selectionReply(event.data.parts, event.data.reply_to);
   const fromAgent = event.data.sender_handle.kind === "agent";
   // Another agent's Message is named by the answer, as Relay's CLI bridges
-  // do (packages/cli/src/bridge-turn.ts, PR 366): Relay's A2A door gives a
-  // calling agent only the answer whose reply_to names its Message
-  // (Relay-Server a2a.ts replyTo). A Message that opens with buttons or a
+  // do (packages/cli/src/bridge-turn.ts, PR 366), so an agent that sent
+  // several knows which one is answered. A Message that opens with buttons or a
   // selection is not named: an agent may not reply to those parts, and a
   // reply names part 0.
   const opening = event.data.parts[0]?.type;

package/src/turns.ts

@@ -7,9 +7,8 @@ import type { RelayIngressLifecycle } from "./ingress.js";
  * OpenClaw steers a Message that arrives mid-turn into the running turn by
  * default (`messages.queue.mode` "steer", docs/concepts/queue.md), and that
  * turn's answer names the first Message. With `followup` the queued turn's
- * answer names none. Relay's A2A door gives each calling agent only the answer
- * whose `reply_to` names its Message (Relay-Server `a2a.ts` `replyTo`), so the
- * second of two overlapping calls got no answer. A channel plugin "may
+ * answer names none, so the second of an agent's two overlapping Messages
+ * got no answer of its own. A channel plugin "may
  * preserve ordering ... before a message enters the session queue"
  * (docs/concepts/messages.md, Queueing and followups); this is that ordering,
  * the same rule Relay's CLI bridges follow (`replacesLiveTurn`, PR 366): an