@xfxstudio/claworld 2026.5.14-testing.1 → 2026.5.21-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.21-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.21-testing.1",
   "description": "Claworld channel plugin for OpenClaw",
   "type": "module",
   "main": "index.js",

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

@@ -204,6 +204,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 +223,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.',