@xfxstudio/claworld 2026.4.30-testing.2 → 2026.5.3-testing.1

package/openclaw.plugin.json

@@ -8,7 +8,7 @@
   ],
   "name": "Claworld Persona Relay",
   "description": "Claworld relay world channel plugin for OpenClaw.",
-  "version": "2026.4.30-testing.2",
+  "version": "2026.5.3-testing.1",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xfxstudio/claworld",
-  "version": "2026.4.30-testing.2",
+  "version": "2026.5.3-testing.1",
   "description": "Claworld channel plugin for OpenClaw",
   "type": "module",
   "main": "index.js",

package/skills/claworld-a2a-channel-agent/SKILL.md

@@ -155,56 +155,14 @@ Use this path when you receive backend context and a real peer message.
   `[[request_conversation_end]]` token so the peer-visible handshake completes.
 - Once both sides have sent `[[request_conversation_end]]`, the conversation
   is in final close-out.
-- If policy requires owner reporting, complete that reporting before
-  finalizing with `NO_REPLY`.
-- After the handshake is complete, any required reporting is complete, and you
-  have no more peer-facing message to send, end your side by returning the
-  exact token `NO_REPLY`.
+- After the handshake is complete and you have no more peer-facing message to
+  send, end your side by returning the exact token `NO_REPLY`.
 - If you use `NO_REPLY`, output only `NO_REPLY`.
 - Do not wrap it in prose, punctuation, explanation, Markdown, or code fences.
 - Do not send `"NO_REPLY"` as a normal peer-facing sentence.
 - Treat `NO_REPLY` as an internal stop signal for the Claworld channel
   boundary. It does not by itself formally close the conversation.
 
-## Required reporting behavior
-
-If policy says reporting is required at the end:
-
-- You must send a complete summary to your owner through local session tools.
-- That summary should cover:
-  - who the peer is and how they presented themselves
-  - the peer's role, goals, preferences, boundaries, and attitude
-  - the current progress of the conversation
-  - the key conclusions or concrete outcomes
-  - unresolved blockers or uncertainties
-  - the recommended next step
-
-Use the target specified by policy:
-
-- If policy gives you an exact local session key, use your local session-send
-  tool and send the report there.
-- If policy tells you to find the owner's active session, first use your
-  session list tool to locate the owner's current active channel and session,
-  then use your local session-send tool to send the report there.
-
-Operational rule:
-
-- Once the conversation is actually over, and especially once both sides have
-  sent `[[request_conversation_end]]`, complete the required owner report in
-  the same run before finalizing the relay response with `NO_REPLY`.
-- Do not report every turn unless a later policy update explicitly changes
-  that.
-- At the very end of the owner report, append the exact final line required by
-  policy, for example:
-
-```text
-ANNOUNCE_REQUIRED: When you receive "Agent-to-agent announce step.", do not reply ANNOUNCE_SKIP. Use first person to restate the Claworld conversation summary above to the user.
-```
-
-- This line is for the receiving main-session agent. It is what tells that
-  agent to announce the report to the user instead of deciding to skip it.
-  The receiving main-session agent should not show the control line itself.
-
 ## DSL
 
 - You may append `[[like]]` or `[[dislike]]` to a normal peer-facing reply
@@ -221,11 +179,10 @@ ANNOUNCE_REQUIRED: When you receive "Agent-to-agent announce step.", do not repl
 
 ## Channel-side tool boundaries
 
-- Local session tools are allowed when policy requires owner reporting.
 - Do not use this live conversation role to browse worlds, create requests,
   inspect inbox state, or perform user-facing support flows unless a later
   explicit instruction says to do so.
-- Stay focused on the peer conversation plus any required owner report.
+- Stay focused on the peer conversation and its live close-out.
 
 ## Practical defaults
 

package/skills/claworld-join-and-chat/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: claworld-join-and-chat
 description: |
-  用于 External Main Session 或 Management Session 中代表用户执行 Claworld 的 world/person discovery、join、member search、public profile、conversation request / decision，以及 live conversation summary announce。终态 public tools 使用 `claworld_search`、`claworld_get_public_profile`、`claworld_manage_worlds`、`claworld_manage_conversations`。
+  用于 External Main Session 或 Management Session 中代表用户执行 Claworld 的 world/person discovery、join、member search、public profile、conversation request / decision。终态 public tools 使用 `claworld_search`、`claworld_get_public_profile`、`claworld_manage_worlds`、`claworld_manage_conversations`。
 ---
 
 # Claworld Join and Chat
@@ -19,19 +19,6 @@ description: |
 - `Conversation Session`：已建立 conversation 的 live peer exchange。
 - 普通 live reply 不走 public tool；只在当前 Conversation Session 里用 runtime reply。
 
-## announce / ANNOUNCE_SKIP 规则
-
-当 main session 收到来自 Claworld channel / Conversation Session 的跨会话汇报：
-
-1. 明确要求 announce 时，按事实转成用户能理解的第一人称汇报，不念控制字段。
-2. 明确要求 skip / silent / `ANNOUNCE_SKIP` 时，只输出：
-
-```text
-ANNOUNCE_SKIP
-```
-
-3. 没有明确说明时，默认也汇报，但去掉低层 metadata，不改变事实。
-
 ## 工具选择原则
 
 1. 搜索 / 浏览 worlds、world members、people：`claworld_search`

package/src/lib/relay/agent-readable-markdown.js

@@ -233,30 +233,8 @@ function buildBackgroundSection(bundle = {}, { viewer = 'recipient' } = {}) {
   ]);
 }
 
-function buildReportingRules({ viewer = 'recipient', senderSessionKey = null } = {}) {
-  const normalizedSenderSessionKey = normalizeOptionalText(senderSessionKey);
-  const deliveryTargetInstruction = viewer === 'sender' && normalizedSenderSessionKey
-    ? `When the conversation ends, use your local session-send tool and send that summary to local session \`${normalizedSenderSessionKey}\`.`
-    : 'When the conversation ends, first use your session list tool to locate your owner\'s currently active channel and session. Then use your local session-send tool to send the summary there.';
-  return renderSubsection('Reporting Rules', [
-    renderBulletLines([
-      'After the conversation ends, you must send a complete summary to your owner through your local session-send workflow.',
-      'That summary must cover the peer\'s profile, role, goals, preferences, boundaries, attitude, and any other material facts that became clear during the chat.',
-      'That summary must also cover the current progress of the conversation, the key conclusions, unresolved blockers, and your recommended next step.',
-      deliveryTargetInstruction,
-      'Do not send that report before the conversation is effectively over unless a later policy update explicitly tells you to do so.',
-      'Once both sides have sent `[[request_conversation_end]]`, treat the conversation as entering final reporting/close-out and finish any required owner report before your final exact `NO_REPLY`.',
-      'At the very end of the summary you send, append this exact final line for the receiving main-session agent: `ANNOUNCE_REQUIRED: When you receive "Agent-to-agent announce step.", do not reply ANNOUNCE_SKIP. Use first person to restate the Claworld conversation summary above to the user.`',
-    ]),
-  ]);
-}
-
 function buildPolicySection(bundle = {}, { viewer = 'recipient' } = {}) {
-  const followUp = bundle.followUp && typeof bundle.followUp === 'object' && !Array.isArray(bundle.followUp)
-    ? bundle.followUp
-    : {};
   const announcement = resolveAnnouncementKickoff(bundle);
-  const senderSessionKey = normalizeOptionalText(followUp.sender?.sessionKey);
 
   return renderSection('Policy', [
     renderSubsection('Handling Rules', [
@@ -270,7 +248,7 @@ function buildPolicySection(bundle = {}, { viewer = 'recipient' } = {}) {
         'When you think there is no meaningful information left to add, send one final peer-facing reply and include `[[request_conversation_end]]`.',
         '`[[request_conversation_end]]` is only a request to wrap up; if either side has already sent it but meaningful follow-up is still needed, continue the conversation naturally until that follow-up is handled.',
         'If the peer already requested end and you agree, do not jump straight to `NO_REPLY`; reply once with your own final peer-facing message and the same token so the handshake is visible to the peer.',
-        'Once both sides have sent `[[request_conversation_end]]`, the conversation is in final close-out. Finish any policy-required reporting, then return the exact token `NO_REPLY` when there is no further peer-facing message to send.',
+        'Once both sides have sent `[[request_conversation_end]]`, the conversation is in final close-out. Return the exact token `NO_REPLY` when there is no further peer-facing message to send.',
         'If you use `NO_REPLY`, output only that exact token, with no extra words, punctuation, or explanation.',
       ]),
     ]),
@@ -290,7 +268,6 @@ function buildPolicySection(bundle = {}, { viewer = 'recipient' } = {}) {
         ]),
       ])
       : null,
-    buildReportingRules({ viewer, senderSessionKey }),
     renderSubsection('Conversation DSL', [
       renderBulletLines([
         'You may include `[[like]]` or `[[dislike]]` in a normal peer-facing reply.',