Update for jsonResult removal from openclaw/plugin-sdk

[nopresearcher]

The latest version of OpenClaw removed the jsonResult export from openclaw/plugin-sdk. This breaks all 22 tool files in DevClaw that import it, preventing the plugin from loading.

error TS2305: Module '"openclaw/plugin-sdk"' has no exported member 'jsonResult'.

Affected files

• All tools in lib/tools/admin/ (12 files)
• All tools in lib/tools/tasks/ (9 files)
• lib/tools/worker/work-finish.ts

Expected behavior

DevClaw should build and register successfully against the latest OpenClaw release.

[infraprodsh]

+1 — reproduced today on a fresh install.

Environment

• openclaw@2026.4.15 (npm -g)
• @laurentenhoor/devclaw@1.6.10
• Linux, Node v22.22.0
• Gateway restarted cleanly after install (confirmed via openclaw plugins doctor → DevClaw plugin registered (23 tools, …))

Repro
Any MCP tool call from the DevClaw surface returns:

(0 , _pluginSdk.jsonResult) is not a function

e.g. mcp__openclaw__tasks_status({ channelId: "-5293xxxxxxx" }) fails immediately.

Confirmed root cause: openclaw/plugin-sdk (root export) only exports 5 symbols (buildMemorySystemPromptAddition, delegateCompactionToRuntime, emptyPluginConfigSchema, onDiagnosticEvent, registerContextEngine). jsonResult was moved to openclaw/plugin-sdk/core, but DevClaw's bundle still does import { jsonResult } from "openclaw/plugin-sdk" at ~20 sites.

Same failure mode is visible in issue #520 (notify() → runtime.channel.telegram.sendMessageTelegram is undefined at runtime).

Workaround for other users hitting this today: downgrade openclaw to last 2026.3.x stable:

npm install -g openclaw@2026.3.31 && systemctl --user restart openclaw-gateway.service

DevClaw 1.6.10 runs cleanly on that baseline (peerDep ^2026.3.2).

Would be great to get a 1.6.11 patch that re-routes the imports to openclaw/plugin-sdk/core — happy to PR if useful.