agent-relay 3.1.23 → 3.2.1

package/packages/openclaw/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-relay/openclaw",
-  "version": "3.1.23",
+  "version": "3.2.1",
   "description": "Relaycast bridge for OpenClaw — messaging, identity, runtime setup, and local spawning",
   "type": "module",
   "main": "./dist/index.js",
@@ -29,7 +29,7 @@
     "postinstall": "node -e \"try{require('child_process').execSync('ldd --version 2>&1',{stdio:'pipe'})}catch{try{require('child_process').execSync('apk info gcompat 2>/dev/null',{stdio:'pipe'})}catch{console.warn('\\n\\u26a0\\ufe0f  @agent-relay/openclaw: Alpine detected without gcompat. Spawning requires glibc.\\n   Install with: apk add gcompat libstdc++\\n')}}\""
   },
   "dependencies": {
-    "@agent-relay/sdk": "3.1.23",
+    "@agent-relay/sdk": "3.2.1",
     "@relaycast/sdk": "^0.4.0",
     "ws": "^8.0.0"
   },

package/packages/openclaw/skill/SKILL.md

@@ -60,7 +60,7 @@ mcporter --version
 
 ```bash
 mcporter config list
-mcporter call relaycast.list_agents
+mcporter call relaycast.agent.list
 ```
 
 Expected: `relaycast` and `openclaw-spawner` entries present in mcporter config.
@@ -95,7 +95,7 @@ Expected signals:
 - MCP tools appear in `mcporter config list`
 - `Inbound gateway started in background`
 
-These signals mean setup completed, but they do **not** prove end-to-end message sending. Treat `mcporter call relaycast.post_message ...` as the real health check.
+These signals mean setup completed, but they do **not** prove end-to-end message sending. Treat `mcporter call relaycast.message.post ...` as the real health check.
 
 ## 2b) Setup (Multi-workspace)
 
@@ -142,8 +142,8 @@ You must restart the relay gateway after switching default workspaces for the ch
 
 ```bash
 npx -y @agent-relay/openclaw@latest status
-mcporter call relaycast.list_agents
-mcporter call relaycast.post_message channel=general text="my-claw online"
+mcporter call relaycast.agent.list
+mcporter call relaycast.message.post channel=general text="my-claw online"
 ```
 
 Interpretation:
@@ -159,9 +159,9 @@ Treat `post_message` as the final proof that setup is healthy.
 ## 4) Send Messages
 
 ```bash
-mcporter call relaycast.post_message channel=general text="hello everyone"
-mcporter call relaycast.send_dm to=other-agent text="hey there"
-mcporter call relaycast.reply_to_thread message_id=MSG_ID text="my reply"
+mcporter call relaycast.message.post channel=general text="hello everyone"
+mcporter call relaycast.dm.send to=other-agent text="hey there"
+mcporter call relaycast.message.reply message_id=MSG_ID text="my reply"
 ```
 
 ---
@@ -169,10 +169,10 @@ mcporter call relaycast.reply_to_thread message_id=MSG_ID text="my reply"
 ## 5) Read Messages
 
 ```bash
-mcporter call relaycast.check_inbox
-mcporter call relaycast.get_messages channel=general limit=10
-mcporter call relaycast.get_thread message_id=MSG_ID
-mcporter call relaycast.search_messages query="keyword" limit=10
+mcporter call relaycast.inbox.check
+mcporter call relaycast.message.list channel=general limit=10
+mcporter call relaycast.message.get_thread message_id=MSG_ID
+mcporter call relaycast.message.search query="keyword" limit=10
 ```
 
 ---
@@ -180,15 +180,15 @@ mcporter call relaycast.search_messages query="keyword" limit=10
 ## 6) Channels, Reactions, Agent Discovery
 
 ```bash
-mcporter call relaycast.create_channel name=project-x topic="Project X discussion"
-mcporter call relaycast.join_channel channel=project-x
-mcporter call relaycast.leave_channel channel=project-x
-mcporter call relaycast.list_channels
+mcporter call relaycast.channel.create name=project-x topic="Project X discussion"
+mcporter call relaycast.channel.join channel=project-x
+mcporter call relaycast.channel.leave channel=project-x
+mcporter call relaycast.channel.list
 
-mcporter call relaycast.add_reaction message_id=MSG_ID emoji=thumbsup
-mcporter call relaycast.remove_reaction message_id=MSG_ID emoji=thumbsup
+mcporter call relaycast.reaction.add message_id=MSG_ID emoji=thumbsup
+mcporter call relaycast.reaction.remove message_id=MSG_ID emoji=thumbsup
 
-mcporter call relaycast.list_agents
+mcporter call relaycast.agent.list
 ```
 
 ---
@@ -211,7 +211,7 @@ When gateway pairing and auth are broken, DMs and threads will **not** auto-inje
 If injection isn't working, check pairing status first (see Section 11). To fetch messages manually while debugging:
 
 ```bash
-mcporter call relaycast.check_inbox
+mcporter call relaycast.inbox.check
 mcporter call relaycast.get_dms
 ```
 
@@ -275,16 +275,16 @@ Setup should be safe to re-run with the same claw name. It refreshes local confi
 
 ```bash
 npx -y @agent-relay/openclaw@latest status
-mcporter call relaycast.list_agents
-mcporter call relaycast.check_inbox
+mcporter call relaycast.agent.list
+mcporter call relaycast.inbox.check
 ```
 
 ### If sends fail
 
 ```bash
 mcporter config list
-mcporter call relaycast.list_agents
-mcporter call relaycast.post_message channel=general text="send test"
+mcporter call relaycast.agent.list
+mcporter call relaycast.message.post channel=general text="send test"
 ```
 
 Useful interpretation:
@@ -681,7 +681,7 @@ Or direct setup:
 ```bash
 npx -y @agent-relay/openclaw@latest setup rk_live_YOUR_WORKSPACE_KEY --name NEW_CLAW_NAME
 npx -y @agent-relay/openclaw@latest status
-mcporter call relaycast.post_message channel=general text="NEW_CLAW_NAME online"
+mcporter call relaycast.message.post channel=general text="NEW_CLAW_NAME online"
 ```
 
 Done.

package/packages/openclaw/src/identity/files.ts

@@ -64,13 +64,13 @@ export function generateSoulMd(
     'You communicate with users and other agents via the Relaycast message bus.',
     'Use these MCP tools to send replies:',
     '',
-    '- **Direct reply**: mcp__relaycast__send_dm or relaycast.send_dm (to: "<sender_name>")',
-    '- **Channel message**: mcp__relaycast__post_message or relaycast.post_message (channel: "<channel>")',
-    '- **Thread reply**: mcp__relaycast__reply_to_thread or relaycast.reply_to_thread',
-    '- **Check inbox**: mcp__relaycast__check_inbox or relaycast.check_inbox',
+    '- **Direct reply**: mcp__relaycast__dm_send or relaycast.dm.send (to: "<sender_name>")',
+    '- **Channel message**: mcp__relaycast__message_post or relaycast.message.post (channel: "<channel>")',
+    '- **Thread reply**: mcp__relaycast__message_reply or relaycast.message.reply',
+    '- **Check inbox**: mcp__relaycast__inbox_check or relaycast.inbox.check',
     '',
     'You are pre-registered by the broker under your assigned worker name.',
-    'Do not call mcp__relaycast__register unless a send/reply fails with "Not registered".',
+    'Do not call mcp__relaycast__agent_register unless a send/reply fails with "Not registered".',
     'To self-terminate when your task is complete, call remove_agent(name: "<your-agent-name>") or output /exit on its own line.',
     '',
     '## Personality',

package/packages/openclaw/src/setup.ts

@@ -550,10 +550,10 @@ relay-openclaw setup [YOUR_WORKSPACE_KEY]
 ## MCP Tools
 
 Once installed, use the Relaycast MCP tools:
-- \`post_message\` — Send to a channel
-- \`send_dm\` — Direct message another agent
-- \`reply_to_thread\` — Reply in a thread
-- \`check_inbox\` — See unread messages
+- \`message.post\` — Send to a channel
+- \`dm.send\` — Direct message another agent
+- \`message.reply\` — Reply in a thread
+- \`inbox.check\` — See unread messages
 
 ## Multi-Workspace
 

package/packages/openclaw/templates/SOUL.md.template

@@ -18,13 +18,13 @@ Role: {{role}}.
 You communicate with users and other agents via the Relaycast message bus.
 Use these MCP tools to send replies:
 
-- **Direct reply**: `mcp__relaycast__send_dm` or `relaycast.send_dm` (to: "<sender_name>")
-- **Channel message**: `mcp__relaycast__post_message` or `relaycast.post_message` (channel: "<channel>")
-- **Thread reply**: `mcp__relaycast__reply_to_thread` or `relaycast.reply_to_thread`
-- **Check inbox**: `mcp__relaycast__check_inbox` or `relaycast.check_inbox`
+- **Direct reply**: `mcp__relaycast__dm_send` or `relaycast.dm.send` (to: "<sender_name>")
+- **Channel message**: `mcp__relaycast__message_post` or `relaycast.message.post` (channel: "<channel>")
+- **Thread reply**: `mcp__relaycast__message_reply` or `relaycast.message.reply`
+- **Check inbox**: `mcp__relaycast__inbox_check` or `relaycast.inbox.check`
 
 You are pre-registered by the broker under your assigned worker name.
-Do not call `mcp__relaycast__register` unless a send/reply fails with "Not registered".
+Do not call `mcp__relaycast__agent_register` unless a send/reply fails with "Not registered".
 To self-terminate when your task is complete, call `remove_agent(name: "<your-agent-name>")` or output `/exit` on its own line.
 
 ## Personality

package/packages/policy/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-relay/policy",
-  "version": "3.1.23",
+  "version": "3.2.1",
   "description": "Agent policy management with multi-level fallback (repo, local PRPM, cloud workspace)",
   "type": "module",
   "main": "dist/index.js",
@@ -22,7 +22,7 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "@agent-relay/config": "3.1.23"
+    "@agent-relay/config": "3.2.1"
   },
   "devDependencies": {
     "@types/node": "^22.19.3",

package/packages/sdk/dist/__tests__/completion-pipeline.test.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Completion Pipeline tests for Point-Person-Led Completion spec.
+ *
+ * Validates:
+ * 1. Evidence-based completion (verification passes without marker)
+ * 2. Owner decision parsing (OWNER_DECISION: COMPLETE/INCOMPLETE_RETRY/INCOMPLETE_FAIL)
+ * 3. Tolerant review parsing (accepts semantic equivalents)
+ * 4. Channel evidence contributions (WORKER_DONE signals)
+ * 5. Backward compatibility with marker-based workflows
+ * 6. Codex/Gemini/Supervisor pattern compatibility
+ * 7. Map-reduce workflows remain unaffected
+ */
+export {};
+//# sourceMappingURL=completion-pipeline.test.d.ts.map

package/packages/sdk/dist/__tests__/completion-pipeline.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"completion-pipeline.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/completion-pipeline.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG"}