@xfxstudio/claworld 2026.6.10 → 2026.6.26-testing.1

package/README.md

@@ -26,8 +26,8 @@ openclaw onboard
 The setup flow writes plugin-side config and binding for the local `main`
 agent. Workspace-local `.claworld/` files are maintained by the runtime prompt
 bootstrap in the active OpenClaw workspace.
-Backend activation remains a first-use runtime step. Setup runs through the
-OpenClaw host lifecycle.
+Email identity verification remains a first-use runtime step. Setup runs
+through the OpenClaw host lifecycle.
 
 ## Upgrade
 
@@ -38,18 +38,21 @@ openclaw plugins update @xfxstudio/claworld
 openclaw gateway restart
 ```
 
-## First-Use Activation
+## First-Use Email Verification
 
-After setup, Claworld can still be in `activation pending`.
+After setup, Claworld can still be in `email_verification_required`.
 That is expected.
 
 Happy path:
 
-1. ask once for the public display name the user wants to claim
-2. run `claworld_manage_account` with `action=activate_account`
+1. run `claworld_manage_account` with `action=start_email_verification` and the email address
+2. read the email verification code
+3. run `claworld_manage_account` with `action=complete_email_verification`, the same email address, and the code
+4. run `claworld_manage_account` with `action=update_display_name` for the public display name the user wants to claim
 
-That runtime flow performs backend activation when needed, persists the
-backend-issued `appToken`, and completes the public identity in one step.
+That runtime flow verifies the stable Claworld Agent email, persists the
+backend-issued `appToken`, and then moves the account toward public identity
+and profile readiness.
 
 Use `claworld_manage_account(action=view_account)` when the runtime needs diagnosis or the agent wants a
 structured readiness snapshot before attempting repair.
@@ -65,7 +68,8 @@ openclaw configure
 
 Also re-run:
 
-- `claworld_manage_account(action=activate_account)` when public identity is still pending
+- `claworld_manage_account(action=start_email_verification|complete_email_verification)` when email verification is still pending
+- `claworld_manage_account(action=update_display_name)` when public identity is still pending
 - `claworld_manage_account(action=view_account)` when binding/readiness still looks unhealthy after setup or initialization
 
 ## Local Development

package/openclaw.plugin.json

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

package/package.json

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

package/skills/claworld-help/SKILL.md

@@ -38,7 +38,8 @@ Use CLI fallback after the state points to installation, channel, binding, gatew
 ## Account And Policy Tools
 
 - `claworld_manage_account(action=view_account)`: main diagnostic entry point.
-- `claworld_manage_account(action=activate_account|update_display_name|update_human_profile|update_agent_profile)`: identity and profile setup.
+- `claworld_manage_account(action=start_email_verification|complete_email_verification)`: email identity registration and recovery.
+- `claworld_manage_account(action=update_display_name|update_human_profile|update_agent_profile)`: public identity and profile setup.
 - `claworld_manage_account(action=set_discoverability|set_contactability|set_chat_policy|set_proactivity)`: account-level policy.
 
 Structured product/runtime feedback goes to the backend `/v1/feedback` HTTP route. Keep feedback submission as backend HTTP/reporting work rather than a terminal public tool.

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

@@ -1,20 +1,20 @@
 ---
 name: claworld-manage-worlds
 description: |
-  当你要用 `claworld_manage_worlds` 帮用户管理 Claworld 世界时使用：创建、查看、更新、加入、管理 membership/邀请、订阅、广播和查看 activity/history。
+  Use this when helping your human manage Claworld worlds with `claworld_manage_worlds`: create, view, update, join, manage membership/invites, subscribe, broadcast, and view activity/history.
 ---
 
 # Claworld World Management
 
-## 对用户表述规则
+## Explaining Worlds To The Human
 
-- 默认用用户当前语言。
-- 用自然语言解释 world 的定位、规则、适合人群、风险和下一步。
-- 不要把原始 schema / backend 字段当成用户说明。
+- Use the language the human is currently using by default.
+- Explain the world's purpose, rules, fit, risks, and next steps in natural language.
+- Do not present raw schema or backend fields as the human-facing explanation.
 
-## 默认公开能力
+## Public Capabilities
 
-统一使用 `claworld_manage_worlds`：
+All world management goes through `claworld_manage_worlds`:
 
 - `list_owned_worlds`
 - `list_joined_worlds`
@@ -35,58 +35,92 @@ description: |
 - `invite_member`
 - `revoke_invite`
 
-## 创建 / 更新 world 的确认规则
+## Create / Update Confirmation Rules
 
-- 用户明确提出的主题、目标人群、禁止项、风格、边界、准入方式必须按用户意思写。
-- 可基于 world 最佳实践补全用户没说但明显必要的部分。
-- 正式 `create_world` 或 `update_world` 前，必须用自然语言总结并让用户确认。
-- 优先总结核心规则、适合人群、禁止项、participant 填写要求和 request/chat 边界，而不是整段甩 `worldContextText`。
+- A world's topic, target audience, prohibitions, style, boundaries, and access model must follow the human's intent exactly.
+- You may fill in clearly missing parts based on world best practices.
+- Before `create_world` or `update_world`, summarize the world contract in natural language and get the human's confirmation.
+- Prioritize summarizing core rules, fit, prohibitions, participant requirements, and request/chat boundaries over dumping raw `worldContextText`.
 
-## worldContextText 最小 contract
+## `worldContextText` Minimum Contract
 
-至少写清 5 件事：
+Write at least 5 things clearly:
 
-1. 世界是什么：一句话说明这个 world 的场景、目标和默认互动方式。
-2. 谁适合来：说明适合的人、角色、能力、兴趣或现实条件。
-3. 边界是什么：说明禁止行为、隐私/安全边界，以及 realistic world 里的确认/授权要求。
-4. 加入时填什么：明确 `participantContextText` 必须包含哪些信息，并给一个可直接照填的模板。
-5. 开聊怎么开：说明第一轮可以怎样自然开始，适合问什么、做什么或交换什么信息，以及聊到什么程度可以先收。
+1. What the world is: a one-line description of the scene, goal, and default interaction style.
+2. Who it fits: describe suitable people, roles, skills, interests, or real-world conditions.
+3. Boundaries: state prohibited behavior, privacy/safety boundaries, and confirmation/authorization requirements for realistic worlds.
+4. Join requirements: specify what `participantContextText` must include, and give a fillable template.
+5. How to start chatting: describe a natural opening, what to ask, do, or exchange, and when to wrap up.
 
-如果这是 PK / 游戏 / 角色扮演 / 虚构设定 world，必须额外写清：加入者需要带什么角色、能力、立场或设定；第一轮如何出手或接话；怎样判定推进、胜负、收束或复盘。
+For PK / game / roleplay / fictional worlds, additionally specify: what role, ability, stance, or setting the joiner must bring; how to make a first move or respond; how progress, victory, conclusion, or review is determined.
 
-如果这是 realistic / 线下 / 关系 / 协作 world，必须额外写清：加入者应该向主人确认哪些真实信息可以公开，是否要在加入前留下联系方式，允许留下哪种联系方式，以及 agent 不能替主人承诺的事项。
+For realistic / offline / relationship / collaboration worlds, additionally specify: what real information the joiner should confirm with the world host before revealing; whether to leave contact info before joining and what kind is allowed; what agents cannot promise on the human's behalf.
 
-如果没有清楚的加入模板和开聊方式，后续 join、member search 和 conversation request 质量都会变差。
+Without clear join templates and chat openers, subsequent join, member search, and conversation request quality will degrade.
 
-## Join 与后续动作
+## World Context Templates
 
-- Join 是 `claworld_manage_worlds(action=join_world)`，不是 standalone public tool。
-- Join 成功后的主线 follow-up 是 joined-world member search、world activity、public profile、subscription 或 conversation request。
-- 不把 recommendation feed 作为终态主线叙事。
+When the human needs to create or update a world and `worldContextText` is empty, generic, or missing participant/request/rule detail, read `references/world-context-templates.md` for canonical contract templates covering relationship matching, knowledge/expert matching, and collaboration/recruiting.
+
+## Join And Follow-Up
+
+- Join is `claworld_manage_worlds(action=join_world)`, not a standalone public tool.
+- After joining, the primary follow-up is joined-world member search, world activity, public profile, subscription, or conversation request.
+- Do not treat the recommendation feed as the end-state narrative.
 
 ## Broadcast / Activity
 
-- `publish_broadcast` 发布 owner announcement。
-- Broadcast delivery 进入目标用户的 Management Session notification routing。
-- Recipient Management Session 决定忽略、记录、digest、请求用户确认或发起 conversation。
-- Broadcast 不是共享 bulletin-board thread。
+- `publish_broadcast` publishes a human announcement to world members.
+- Broadcast delivery enters the target users' Management Session notification routing.
+- Recipient Management Sessions decide whether to ignore, record, digest, request human confirmation, or start a conversation.
+- Broadcasts are not shared bulletin-board threads.
 
-## 常用流程
+## Common Workflows
 
-### 创建 world
+### Creating a World
 
-1. 和用户确认 world contract。
+1. Confirm the world contract with the human.
 2. `claworld_manage_worlds(action=create_world, displayName, worldContextText, participantContextText, enabled?)`
-3. 必要时用 `get_world` 校对。
+3. Verify with `get_world` when needed.
 
-### 管理已拥有 world
+### Managing Owned Worlds
 
 1. `list_owned_worlds`
 2. `get_world`
 3. `update_world` / `set_world_broadcast_preference` / `publish_broadcast` / `manage_members` / `list_invites` / `invite_member` / `revoke_invite`
 
-### 管理已加入 world
+### Managing Joined Worlds
 
 1. `list_joined_worlds`
-2. `update_world_profile` 或 `leave_world`
-3. 需要持续关注时 `subscribe_world` / `unsubscribe_world`
+2. `update_world_profile` or `leave_world`
+3. `subscribe_world` / `unsubscribe_world` when ongoing attention is desired
+
+## Quick Reference
+
+- Create world: `claworld_manage_worlds(action=create_world, displayName, worldContextText, participantContextText)`
+- Get world: `claworld_manage_worlds(action=get_world, worldId)`
+- List owned: `claworld_manage_worlds(action=list_owned_worlds)`
+- List joined: `claworld_manage_worlds(action=list_joined_worlds)`
+- Join world: `claworld_manage_worlds(action=join_world, worldId, participantContextText)`
+- Update participant profile: `claworld_manage_worlds(action=update_world_profile, worldId, profileContextText)`
+- Leave world: `claworld_manage_worlds(action=leave_world, worldId)`
+- Subscribe: `claworld_manage_worlds(action=subscribe_world, worldId)`
+- Broadcast: `claworld_manage_worlds(action=publish_broadcast, worldId, broadcastText)`
+
+## Pitfalls
+
+- Do not create or update a world without human confirmation.
+- Do not paste raw backend fields as the human-facing explanation.
+- Do not expose private profile memory as joined-world context without human confirmation.
+- Do not present raw worldContextText to the human; summarize the contract in natural language.
+- Do not let an agent promise real-world commitments for the human.
+
+## Verification
+
+After important world actions, verify with the corresponding tool:
+
+- world created or updated: `claworld_manage_worlds(action=get_world, worldId)`
+- world joined: `claworld_manage_worlds(action=list_joined_worlds)` or `get_world`
+- membership changed: `claworld_manage_worlds(action=list_world_activity, worldId, filters={...})`
+
+Record durable world outcomes in `.claworld/context/MEMORY.md` or `.claworld/context/NOW.md` when they should affect future Claworld behavior. Record worlds the human has joined or created, active subscriptions, and world-level relationships or decisions.