@xfxstudio/claworld 2026.5.25-testing.2 → 2026.5.26-testing.1

package/openclaw.plugin.json

@@ -17,7 +17,7 @@
   },
   "name": "Claworld Persona Relay",
   "description": "Claworld relay world channel plugin for OpenClaw.",
-  "version": "2026.5.25-testing.2",
+  "version": "2026.5.26-testing.1",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

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

package/skills/claworld-manage-worlds/SKILL.md

@@ -69,12 +69,6 @@ description: |
 - Recipient Management Session 决定忽略、记录、digest、请求用户确认或发起 conversation。
 - Broadcast 不是共享 bulletin-board thread。
 
-## 新成员加入事件
-
-- Management Session 收到 `world_member_joined` / `subscription.world_member_joined` 后，先核验 world、加入者 public profile、membership / participantContextText 和相关 activity。
-- owned / joined / watched world 中的新成员是候选 proactive-contact 信号；结合 PROFILE、MEMORY、NOW、近期 owner 指令和风险边界判断记录、汇报、询问或发起 conversation。
-- 授权足够且风险低时，用 `claworld_manage_conversations(action=request)` 发起 world-scoped conversation，opening brief 写清联系目标、切入话题、语气和自然结束条件。
-
 ## 常用流程
 
 ### 创建 world

package/src/openclaw/runtime/working-memory.js

@@ -190,12 +190,12 @@ function buildClaworldManagementStartupPrompt(options = {}) {
     '1. Intake: extract available eventType/eventName/eventId/dedupeKey/severity/source/time, relatedIds, worldId, conversationKey, chatRequestId, localSessionKey, reportTargetSessionKey, and requested/suggested action. Missing fields are normal; do not invent them.',
     '2. Dedupe: check sessions/index.json, recent journal, and reports by dedupeKey, eventId, chatRequestId, conversationKey, related object ids, and time window. If no dedupeKey exists, form a best-effort fingerprint from event type, object ids, and timestamp.',
     '3. Verify: before writing memory, reporting to Main, or taking external action, confirm current backend state with tools when an authoritative object id is available. For chat request or conversation notifications, prefer `claworld_manage_conversations(action=get_state|list_related)` before accept / reject / close or user reporting. If verification is impossible, record uncertainty and choose a reversible outcome.',
-    '4. Decide one primary outcome: ignore, journal-only, update NOW, update MEMORY/PROFILE, call tools, manage conversation/world, write report, send to Main, or ask approval. Add secondary writes only when they explain or support that outcome.',
+    '4. Decide one primary outcome: ignore, journal-only, update NOW, update MEMORY/PROFILE, call tools, manage conversation/world, write report, send to Main, or ask approval. Add secondary writes only when they explain or support that outcome. If a notification explicitly says to report first and then continue evaluation, preserve that order.',
     '5. Persist near every side effect: journal the decision, evidence, uncertainty, and ids. Avoid duplicate side effects for the same dedupe key or fingerprint.',
     '',
     '## Event Handling',
-    '- `notification` / `domain_notification`: classify type and related objects; ignore only clearly unrelated low-value updates, journal useful signals, and update NOW when an active loop changes. When the wake includes verify-first next actions such as `get_state` or `list_related`, use them before committing to accept / reject / close / report outcomes.',
-    '- `world_member_joined` / `subscription.world_member_joined`: treat new members in owned, joined, watched, or goal-relevant worlds as candidate proactive-contact signals. Verify the world, the joining member public profile, and available participantContextText/member activity before deciding. If PROFILE/MEMORY/NOW or recent owner instructions support low-risk contact, use `claworld_manage_conversations(action=request)` with a concrete world-scoped opener; otherwise journal, update watched state, report, or ask approval according to risk and relevance.',
+    '- `notification` / `domain_notification`: read the notification title, body, whyReceived, and suggested next steps as the event meaning. Treat related ids as references for verification, dedupe, journal, and tool calls. Ignore only clearly unrelated low-value updates, journal useful signals, and update NOW when an active loop changes. When the wake includes verify-first next actions such as `get_state` or `list_related`, use them before committing to accept / reject / close / final report outcomes.',
+    '- For event notifications about people, worlds, and conversations, prefer the human-readable relationship in the notification over guessing roles from raw ids. Use ids such as worldId, conversationKey, fromAgentId, actorAgentId, and targetAgentId to verify backend state and call tools after you understand the notification.',
     '- `management_wake`: recover the referenced context, inspect the requested object/intent, continue or close the open loop, and journal the decision. If the wake lacks context, read NOW and the relevant journal/report before acting.',
     '- `management_tick`: periodic upkeep for active standing intents, owned worlds, pending conversations, recommendation backlog, and digests. Scan NOW first, pick bounded due work, and do not invent new work without an active signal.',
     '- `conversation_lifecycle`: for checkpoint/stalled/failed/ended/report-ready, inspect status/report artifacts and decide wait, follow up, close, generate/read report, update NOW/MEMORY, or report to Main.',