@xfxstudio/claworld 2026.5.14-testing.1 → 2026.5.25-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.14-testing.1",
+  "version": "2026.5.25-testing.1",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

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

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

@@ -69,6 +69,12 @@ 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

@@ -195,6 +195,7 @@ function buildClaworldManagementStartupPrompt(options = {}) {
     '',
     '## 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.',
     '- `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.',
@@ -204,6 +205,7 @@ function buildClaworldManagementStartupPrompt(options = {}) {
     '## Session Routing',
     '- Reports/approval requests: resolve the current owner-facing route at send time. Use explicit reportTargetSessionKey first. Otherwise treat sessions/index.json main.lastActiveSessionKey as a cache hint; if absent, stale, or uncertain, use the local session list tool to find the latest main/external direct session key.',
     '- Conversation details: prefer sessions/index.json chatRequestId -> artifacts. If missing/stale, search by localSessionKey, chatRequestId, and time window.',
+    '- `sessions_history` is a convenience lookup, not the authority. If it times out, fails, or returns incomplete data, do not conclude the transcript is unavailable. Read sessions/index.json first, locate sessionFile or transcriptPath by chatRequestId, localSessionKey, conversationKey, or time window, then read the local transcript file directly. If both paths fail, report the uncertainty instead of silently dropping the task.',
     '- If no safe Main route exists or session send fails, write a report artifact, journal the failure, and retry or surface it on the next Main route.',
     '',
     '## Write Rules',
@@ -222,6 +224,7 @@ function buildClaworldManagementStartupPrompt(options = {}) {
     '## Reporting',
     '- User-visible reports normally go through Main Session. State what happened, why it matters, evidence/uncertainty, what you did, file/report references when relevant, and the recommended next step or approval question.',
     '- Testing observability is intentionally high: any event related to the user\'s current goals, recent explicit instructions, or NOW.md Active Goals / Open Conversations / Watched People And Worlds / Pending Approvals should receive a concise Main Session report.',
+    '- For owner reports, send the user-visible message first, then write journal/NOW/report entries that say the owner was notified. If you need to record the plan before sending, mark it as pending. After a successful send, append the target Main Session, message id when available, timestamp, and short report summary.',
     '- Do not stay silent only because NOW.md or journal was updated. Use `NO_REPLY` only when the same event was already reported to Main, or when the event is clearly unrelated or low-value.',
     '- If the wake is only a self-echo, delivery ack, or report-ready confirmation for something already routed to Main, default to `NO_REPLY` unless it adds a new owner decision, a new user-facing delta, or a delivery failure that changes what Main should know.',
     '- Avoid duplicate or long Main noise by keeping related-event reports short and evidence-based.',