@relaymessenger/openclaw-plugin 0.4.8-staging.1 → 0.4.8-staging.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/contracts/relay-v1.lock.json +6 -6
- package/dist/src/inbound.js +2 -3
- package/package.json +2 -2
- package/src/inbound.ts +2 -3
- package/src/turns.ts +2 -3
package/README.md
CHANGED
|
@@ -24,7 +24,8 @@ New human reply text is literal `• ` + each selected source label joined with
|
|
|
24
24
|
`\n`, followed by `selection_response` metadata in source-option order. Dispatch
|
|
25
25
|
with `selected_values` and the explicit source target, never label parsing.
|
|
26
26
|
Exact legacy comma-joined text remains a server compatibility input. The person
|
|
27
|
-
checks any number of options
|
|
27
|
+
checks any number of options (exactly one when `multiple` is false) and submits
|
|
28
|
+
them once; checking sends nothing, and
|
|
28
29
|
a person answers a given selection once. iOS may draw a checkmark in place of
|
|
29
30
|
each bullet and repeat the prompt's title, as presentation only.
|
|
30
31
|
|
|
@@ -1,16 +1,16 @@
|
|
|
1
1
|
{
|
|
2
2
|
"relayServer": {
|
|
3
3
|
"repository": "RelayMessenger/Relay-Server",
|
|
4
|
-
"commit": "
|
|
4
|
+
"commit": "349431592ca866731a95407ab8836611989371d2",
|
|
5
5
|
"openapiPath": "contracts/developer/openapi.yaml",
|
|
6
|
-
"sha256": "
|
|
6
|
+
"sha256": "1721df340bf291aa1d5a12578fb4918209cba7525622dd5fb3af2ca68cbc77fc"
|
|
7
7
|
},
|
|
8
8
|
"relaySdk": {
|
|
9
9
|
"package": "@relaymessenger/sdk",
|
|
10
|
-
"version": "0.3.7-staging.
|
|
11
|
-
"integrity": "sha512-
|
|
12
|
-
"operationsSha256": "
|
|
13
|
-
"workspaceOpenapiSha256": "
|
|
10
|
+
"version": "0.3.7-staging.13",
|
|
11
|
+
"integrity": "sha512-uyAYGPsBxVREvW6E0ku2U2R/emT30rlZjN5Oj6agjaB3wPJrx45rG88jPsyfJcrerA9sk31Gc7JpYD71amaISw==",
|
|
12
|
+
"operationsSha256": "e094bf711e65ec5d37c2ca0203cf589be5747308aef8d590fd7cc5af0ac71564",
|
|
13
|
+
"workspaceOpenapiSha256": "1721df340bf291aa1d5a12578fb4918209cba7525622dd5fb3af2ca68cbc77fc",
|
|
14
14
|
"usedOperations": [
|
|
15
15
|
{
|
|
16
16
|
"method": "GET",
|
package/dist/src/inbound.js
CHANGED
|
@@ -58,9 +58,8 @@ export function buildRelayInboundFacts(event) {
|
|
|
58
58
|
const selection = selectionReply(event.data.parts, event.data.reply_to);
|
|
59
59
|
const fromAgent = event.data.sender_handle.kind === "agent";
|
|
60
60
|
// Another agent's Message is named by the answer, as Relay's CLI bridges
|
|
61
|
-
// do (packages/cli/src/bridge-turn.ts, PR 366)
|
|
62
|
-
//
|
|
63
|
-
// (Relay-Server a2a.ts replyTo). A Message that opens with buttons or a
|
|
61
|
+
// do (packages/cli/src/bridge-turn.ts, PR 366), so an agent that sent
|
|
62
|
+
// several knows which one is answered. A Message that opens with buttons or a
|
|
64
63
|
// selection is not named: an agent may not reply to those parts, and a
|
|
65
64
|
// reply names part 0.
|
|
66
65
|
const opening = event.data.parts[0]?.type;
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@relaymessenger/openclaw-plugin",
|
|
3
|
-
"version": "0.4.8-staging.
|
|
3
|
+
"version": "0.4.8-staging.10",
|
|
4
4
|
"description": "Native Relay channel plugin for OpenClaw",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -37,7 +37,7 @@
|
|
|
37
37
|
"prepack": "npm run build"
|
|
38
38
|
},
|
|
39
39
|
"dependencies": {
|
|
40
|
-
"@relaymessenger/sdk": "0.3.7-staging.
|
|
40
|
+
"@relaymessenger/sdk": "0.3.7-staging.13"
|
|
41
41
|
},
|
|
42
42
|
"devDependencies": {
|
|
43
43
|
"@types/node": "^26.6.2",
|
package/src/inbound.ts
CHANGED
|
@@ -80,9 +80,8 @@ export function buildRelayInboundFacts(
|
|
|
80
80
|
const selection = selectionReply(event.data.parts, event.data.reply_to);
|
|
81
81
|
const fromAgent = event.data.sender_handle.kind === "agent";
|
|
82
82
|
// Another agent's Message is named by the answer, as Relay's CLI bridges
|
|
83
|
-
// do (packages/cli/src/bridge-turn.ts, PR 366)
|
|
84
|
-
//
|
|
85
|
-
// (Relay-Server a2a.ts replyTo). A Message that opens with buttons or a
|
|
83
|
+
// do (packages/cli/src/bridge-turn.ts, PR 366), so an agent that sent
|
|
84
|
+
// several knows which one is answered. A Message that opens with buttons or a
|
|
86
85
|
// selection is not named: an agent may not reply to those parts, and a
|
|
87
86
|
// reply names part 0.
|
|
88
87
|
const opening = event.data.parts[0]?.type;
|
package/src/turns.ts
CHANGED
|
@@ -7,9 +7,8 @@ import type { RelayIngressLifecycle } from "./ingress.js";
|
|
|
7
7
|
* OpenClaw steers a Message that arrives mid-turn into the running turn by
|
|
8
8
|
* default (`messages.queue.mode` "steer", docs/concepts/queue.md), and that
|
|
9
9
|
* turn's answer names the first Message. With `followup` the queued turn's
|
|
10
|
-
* answer names none
|
|
11
|
-
*
|
|
12
|
-
* second of two overlapping calls got no answer. A channel plugin "may
|
|
10
|
+
* answer names none, so the second of an agent's two overlapping Messages
|
|
11
|
+
* got no answer of its own. A channel plugin "may
|
|
13
12
|
* preserve ordering ... before a message enters the session queue"
|
|
14
13
|
* (docs/concepts/messages.md, Queueing and followups); this is that ordering,
|
|
15
14
|
* the same rule Relay's CLI bridges follow (`replacesLiveTurn`, PR 366): an
|