@clawrent/openclaw-channel 0.7.0 → 0.8.0

package/README.md

@@ -141,6 +141,28 @@ See [guardrails.example.md](guardrails.example.md) for a full example. Recommend
 2. 在 `~/.openclaw/openclaw.json` 配置两块：`plugins.entries.clawrent.config`（plugin 运行时读）+ `channels.clawrent`（channel 实例检测），见上方示例；token 放 `~/.clawrent/config.json`。
 3. 重启 Gateway → plugin 走 **channel 触发式加载**（`onStartup:false`）→ gateway 经 `startAccount` 自启账户 → provider WS 上线 → 自动接单。配了 `channels.clawrent` 后，provider 由 **gateway 托管**：health-monitor 判其健康（无误判 restart），且终态死亡 / 启动失败时自动恢复。
 
+> **OpenClaw 2026.9+ (capability consent):** after installing or upgrading, the plugin sits in an
+> unauthorized state and the gateway log reports `requires capability consent`. Run:
+>
+> ```bash
+> openclaw plugins enable clawrent --accept-capabilities
+> openclaw gateway restart
+> ```
+>
+> Afterwards `openclaw channels status` should show `clawrent ... running`.
+> 2026.7.x/8.x hosts have no such mechanism — skip this step.
+>
+> **OpenClaw 2026.9+（capability consent）：** 安装或升级后插件处于未授权状态，
+> gateway 日志会报 `requires capability consent`。执行：
+>
+> ```bash
+> openclaw plugins enable clawrent --accept-capabilities
+> openclaw gateway restart
+> ```
+>
+> 之后 `openclaw channels status` 应显示 `clawrent ... running`。
+> 2026.7.x/8.x 宿主无此机制，跳过本步。
+
 > ⚠️ **Do NOT add `plugins.allow: ["clawrent"]`.** In testing, adding `allow` switches the load path to strict mode and actually *blocks* `registerFull` from executing (hit in 0.3.1). Staying in auto-load (no `allow`) is the config that works in 0.3.2.
 >
 > ⚠️ **不要加 `plugins.allow: ["clawrent"]`**。实测加 `allow` 会把加载路径切到严格模式，反而阻止 `registerFull` 执行（0.3.1 撞过）。保持 auto-load（无 allow）是 0.3.2 跑通的配置。
@@ -196,9 +218,27 @@ openclaw plugins install @clawrent/openclaw-channel@<version>
 openclaw gateway restart
 ```
 
-> ⚠️ **`openclaw plugins uninstall --force` removes the `channels.clawrent` config block** from `~/.openclaw/openclaw.json` (including `agentId` / `autoApproveSessions` / `guardrailsFile` — **not the token**: the token always stays in `~/.clawrent/config.json`, credentials are unaffected). The subsequent `install` **does not recreate** that block. After upgrading, **verify `channels.clawrent` is still present**; if it was removed, restore it from the pre-uninstall backup (`openclaw.json.bak.*`) or re-fill it per the [Configuration](#configuration--配置) section (`agentId` can be left empty to auto-resolve from the token). Missing the block does not affect the provider coming online, but `autoApproveSessions` / `guardrailsFile` fall back to their defaults. This behavior stems from the OpenClaw CLI's `uninstall` design (reported upstream); the plugin cannot intercept it.
+After the upgrade completes (OpenClaw 2026.9+ hosts):
+
+```bash
+openclaw plugins update clawrent --accept-capabilities   # or enable --accept-capabilities after install
+openclaw gateway restart
+```
+
+When the capability surface (declared channels / tools / hooks, etc.) changes, 9.x forces re-authorization — this is expected behavior.
+
+升级完成后（OpenClaw 2026.9+ 宿主）：
+
+```bash
+openclaw plugins update clawrent --accept-capabilities   # 或 install 后 enable --accept-capabilities
+openclaw gateway restart
+```
+
+能力面（channels/tools/hooks 等声明）有增减时，9.x 会强制重新授权，属预期行为。
+
+> ⚠️ **`openclaw plugins uninstall --force` removes the `channels.clawrent` config block** from `~/.openclaw/openclaw.json` (including `agentId` / `autoApproveSessions` / `guardrailsFile` — **not the token**: the token always stays in `~/.clawrent/config.json`, credentials are unaffected). The subsequent `install` **does not recreate** that block. After upgrading, **verify `channels.clawrent` is still present**; if it was removed, restore it from the pre-uninstall backup (`openclaw.json.bak.*`) or re-fill it per the [Configuration](#configuration--配置) section (`agentId` can be left empty to auto-resolve from the token). As of plugin 0.7.0 (gateway-managed lifecycle), the `channels.clawrent` block is **required**: when missing, the plugin falls back to legacy `registerFull` start, which fires on every registerFull call → multiple provider instances → `system.roster` storms the session every few seconds (roster spam). The gateway-managed `startAccount` path (single instance, stable, health-monitor-friendly) only activates when `channels.clawrent` is present. **After `uninstall`, you MUST add back `channels: { clawrent: {} }` (or restore from backup) before restarting the gateway.** This behavior stems from the OpenClaw CLI's `uninstall` design (reported upstream); the plugin cannot intercept it.
 >
-> ⚠️ **`openclaw plugins uninstall --force` 会删除 `channels.clawrent` 配置块**（含 `agentId` / `autoApproveSessions` / `guardrailsFile`，**不含 token** —— token 始终在 `~/.clawrent/config.json`，凭据不受影响），随后的 `install` **不会重建**该块。升级后**请检查 `channels.clawrent` 是否还在**；若被删，从卸载前的备份（`openclaw.json.bak.*`）恢复，或按[配置](#configuration--配置)章节重新填写（`agentId` 可留空由 token 自动解析）。缺失该块不影响 provider 上线，但 `autoApproveSessions` / `guardrailsFile` 会回退默认值。此行为源自 OpenClaw CLI 的 uninstall 设计（已向上游反馈），插件侧无法干预。
+> ⚠️ **`openclaw plugins uninstall --force` 会删除 `channels.clawrent` 配置块**（含 `agentId` / `autoApproveSessions` / `guardrailsFile`，**不含 token** —— token 始终在 `~/.clawrent/config.json`，凭据不受影响），随后的 `install` **不会重建**该块。升级后**请检查 `channels.clawrent` 是否还在**；若被删，从卸载前的备份（`openclaw.json.bak.*`）恢复，或按[配置](#configuration--配置)章节重新填写（`agentId` 可留空由 token 自动解析）。plugin 0.7.0 起（gateway 托管生命周期）`channels.clawrent` 块**必需**：缺失时 plugin 退回 legacy `registerFull` 启动，每次 registerFull 都启动 → 多 provider 实例 → `system.roster` 每隔几秒刷屏（roster spam）。gateway 托管的 `startAccount` 路径（单实例、稳定、health-monitor 友好）只有在 `channels.clawrent` 存在时才激活。**`uninstall` 后、重启 gateway 前务必加回 `channels: { clawrent: {} }`（或从备份恢复）。**此行为源自 OpenClaw CLI 的 uninstall 设计（已向上游反馈），插件侧无法干预。
 
 ## Design notes / 设计要点
 

package/dist/index.js

@@ -39,6 +39,12 @@ const setupAdapter = {
 };
 const base = createChannelPluginBase({
     id: CHANNEL_ID,
+    meta: {
+        label: "ClawRent",
+        selectionLabel: "ClawRent (rental sessions)",
+        docsPath: "https://clawrent.cloud/docs/openclaw",
+        blurb: "ClawRent rental sessions as native OpenClaw conversations, answered by your local provider agent.",
+    },
     setup: setupAdapter,
     config: {
         listAccountIds: () => ["clawrent-provider"],

package/dist/provider.d.ts

@@ -37,4 +37,28 @@ export interface StartProviderOptions {
 export interface ProviderHandle {
     stop: () => Promise<void> | void;
 }
+/**
+ * D2 上下文 → OpenClaw ChannelStructuredContext entries（2026.9 channel contract）。
+ * 旧字段名 UntrustedStructuredContext 的移除窗口 2026-09-08 已过；9.3 运行时只认
+ * entries 数组形状。7.1 宿主不认识新字段 → 退化为 BodyForAgent preamble 通道，
+ * 与 9.3 修复前状态一致（两个宿主时代行为对齐，见 plan Task 6 差异表）。
+ */
+export interface ClawRentSessionContext {
+    addressedToMe: boolean;
+    sender: {
+        participantId?: string;
+        side?: string;
+        agentId?: string;
+        consumerUserId?: string;
+    };
+    mentions: unknown[];
+    gist?: string;
+    participantId?: string;
+}
+export declare function buildStructuredContextEntries(untrusted: ClawRentSessionContext): {
+    label: string;
+    source: string;
+    type: string;
+    payload: ClawRentSessionContext;
+}[];
 export declare function startProvider(opts: StartProviderOptions): Promise<ProviderHandle>;

package/dist/provider.js

@@ -31,6 +31,16 @@ function extractDialogue(message) {
         "";
     return { type, content: String(content ?? "") };
 }
+export function buildStructuredContextEntries(untrusted) {
+    return [
+        {
+            label: "ClawRent session context",
+            source: "clawrent",
+            type: "clawrent-session-context",
+            payload: untrusted,
+        },
+    ];
+}
 export async function startProvider(opts) {
     const log = (m) => (opts.onLog ? opts.onLog(m) : console.log(`[clawrent:provider] ${m}`));
     // 动态 import,避免插件在未安装 @clawrent/provider 时整体加载失败。
@@ -156,7 +166,7 @@ export async function startProvider(opts) {
                 return;
             }
             // D1: @-gate removed — agent self-decides whether to reply (prompt-based).
-            // @ is now CONTEXT (addressedToMe), threaded to the agent via UntrustedStructuredContext (D2).
+            // @ is now CONTEXT (addressedToMe), threaded to the agent via ChannelStructuredContext (D2).
             const addressedToMe = isAddressedToMe(session?.participantId, message);
             // D2 prefilter (D3: gated by triagePrefilter, default on) — silent-drop garbage.
             if (opts.triagePrefilter !== false) {
@@ -191,7 +201,7 @@ export async function startProvider(opts) {
             // Windows 文件名不允许冒号, storePath 需做安全转义。
             const storePath = routeSessionKey.replace(/[:]/g, "_");
             const consumerId = session?.consumerUserId ?? "consumer";
-            // D2: UntrustedStructuredContext — sender / mentions / gist / @-addressing. With the
+            // D2: ChannelStructuredContext — sender / mentions / gist / @-addressing. With the
             // @-gate gone (D1), this is what lets the agent self-decide whether + how to reply.
             const mentions = Array.isArray(message.mentions) ? message.mentions : [];
             const untrusted = {
@@ -207,7 +217,7 @@ export async function startProvider(opts) {
                 participantId: session?.participantId,
             };
             // Inject the context as a preamble in the agent-facing text so the model literally
-            // sees it (also available structured on ctxPayload.UntrustedStructuredContext).
+            // sees it (also available structured on ctxPayload.ChannelStructuredContext).
             const textForAgentContent = `[被@: ${addressedToMe ? "是" : "否"}] ` +
                 `[发送方: ${untrusted.sender.side ?? "unknown"}] ` +
                 `[会话: ${untrusted.gist ?? ""}] ` +
@@ -219,7 +229,7 @@ export async function startProvider(opts) {
                 BodyForAgent: textForAgentContent,
                 channel: CHANNEL,
                 SessionKey: routeSessionKey,
-                UntrustedStructuredContext: untrusted,
+                ChannelStructuredContext: buildStructuredContextEntries(untrusted),
             };
             const raw = { sessionId, consumerId, content, message, textForAgent: textForAgentContent };
             try {

package/docs/openclaw-sdk-notes.md

@@ -6,6 +6,19 @@
 
 ---
 
+## 0. 7.1 vs 9.3 已知差异表（0.8.0 维护的地板=2026.7.1，2026-09-10 审计）
+
+| 面 | 2026.7.1 | 2026.9.3 | 我们的策略 |
+|---|---|---|---|
+| 结构化上下文字段 | `UntrustedStructuredContext`，resolver 同样只收 entries 数组（对象形状在任何宿主上都从未生效） | `ChannelStructuredContext`（entries 数组），旧名已过移除窗口 | 只写新字段；0.8.0 是结构化上下文首次真正生效的版本（9.3），7.1 宿主仍走 BodyForAgent preamble |
+| capability consent | 无 | install/enable/升级需 `--accept-capabilities`（第三方插件，能力面变化触发） | README 引导；manifest 面保持最小 |
+| `plugins.installs` 落盘 | plugin 管理命令可能写入（legacy 残留） | 写盘自动剥除；strict schema 拒绝该 key | 宿主侧问题，见 memory `openclaw-8-2-installs-key-fix` |
+| channel meta | 不要求 | label/selectionLabel/docsPath/blurb 缺失时 gateway 兜底并告警 | 0.8.0 显式提供 |
+| Node 运行时 | 无硬性要求 | 宿主要求 Node ≥24.16（宿主侧约束，非插件约束） | 文档提示，不在 engines 强制 |
+| update rehearsal | 无 | 宿主升级排练会核对插件兼容声明+channel readiness | 声明准确（Task 2），readiness 快速返回 |
+
+---
+
 ## 1. 已确认的 OpenClaw Channel Plugin SDK 事实（2026.6.11）
 
 | 项 | 文档说法 | 实际实现（dist 验证） |

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "clawrent",
   "name": "ClawRent Channel",
   "description": "OpenClaw channel plugin that turns ClawRent rental sessions into native OpenClaw conversations, so a local ClawRent provider agent can answer tenants autonomously with its own model and identity. / OpenClaw 频道插件：把 ClawRent 租赁会话桥接成 OpenClaw 原生对话，让本地 ClawRent provider 智能体用自有模型与身份自动应答租户。",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "channels": [
     "clawrent"
   ],
@@ -187,5 +187,13 @@
       }
     },
     "required": []
+  },
+  "configContracts": {
+    "dangerousFlags": [
+      {
+        "path": "autoApproveSessions",
+        "equals": true
+      }
+    ]
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clawrent/openclaw-channel",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "OpenClaw channel plugin that turns ClawRent rental sessions into native OpenClaw conversations, so a local ClawRent provider agent can answer tenants autonomously with its own model and identity. / OpenClaw 频道插件：把 ClawRent 租赁会话桥接成 OpenClaw 原生对话，让本地 ClawRent provider 智能体用自有模型与身份自动应答租户。",
   "license": "ISC",
   "type": "module",
@@ -35,6 +35,7 @@
     ],
     "install": {
       "clawhubSpec": "clawhub:@clawrent/openclaw-channel",
+      "npmSpec": "@clawrent/openclaw-channel",
       "defaultChoice": "clawhub",
       "minHostVersion": ">=2026.7.1"
     },
@@ -42,7 +43,7 @@
       "pluginApi": ">=2026.7.1"
     },
     "build": {
-      "openclawVersion": "2026.7.1"
+      "openclawVersion": "2026.9.3"
     },
     "release": {
       "publishToClawHub": true
@@ -51,6 +52,9 @@
   "scripts": {
     "build": "tsc -p tsconfig.build.json",
     "typecheck": "tsc -p tsconfig.json --noEmit",
+    "verify:compat:floor": "npm install --no-save openclaw@2026.7.1 && npm run typecheck",
+    "verify:compat:current": "npm install && npm run typecheck && npm test",
+    "verify:compat": "npm run verify:compat:floor && npm run verify:compat:current",
     "test": "vitest run",
     "prepublishOnly": "npm run build"
   },
@@ -58,7 +62,7 @@
     "@clawrent/provider": "^0.4.0"
   },
   "peerDependencies": {
-    "openclaw": ">=2026.6.11"
+    "openclaw": ">=2026.7.1"
   },
   "peerDependenciesMeta": {
     "openclaw": {
@@ -66,8 +70,8 @@
     }
   },
   "devDependencies": {
-    "openclaw": "2026.7.1",
-    "@types/node": "^20",
+    "openclaw": "2026.9.3",
+    "@types/node": "^24",
     "typescript": "*",
     "vitest": "^3.0.0"
   }