[WIP] Fix automated tests failure during OpenClaw 2026.3.22 upgrade

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>⚠️ OpenClaw 2026.3.22 upgrade failed automated tests</issue_title>
<issue_description>## Automated Upgrade Failed: 2026.3.11 → 2026.3.22

Failed stage: Docker smoke tests
Workflow run: https://github.com/vhrahulkumar/openclaw-appplatform/actions/runs/23457918301

Test Output

=== OpenClaw Upgrade Verification ===

Waiting for container openclaw-upgrade-test to be ready...
✓ Container is responsive (waiting for init to complete...)
✓ s6 init complete (crond up)
✓ Version: 2026.3.22
✓ Config is valid JSON
✓ tools.profile: coding
✓ Config owned by openclaw
✓ Auth mode: token
✓ Gateway process running
✓ Tailscale binary present
Waiting for gateway HTTP...
FAIL: Gateway HTTP not responding (code: 503)
✓ Config writable by openclaw user
✓ Channel plugins loaded: discord,signal,telegram,whatsapp
✓ Backup config (backup.yaml) is valid
✓ pnpm store excluded from backups
SKIP: Telegram channel probe (TELEGRAM_BOT_TOKEN not set)
✓ openclaw doctor completes

=== Upgrade Verification Results ===
  Passed:   12
  Failed:   1
  Warnings: 0

=== UPGRADE VERIFICATION FAILED (1 failures) ===

Known Regressions

• vhrahulkumar/openclaw-appplatform#53096: [Bug]: Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.
• vhrahulkumar/openclaw-appplatform#52925: Control UI assets missing from npm package (2026.3.22)
• vhrahulkumar/openclaw-appplatform#52269: [Bug]: 最新的源码在安装飞书消息渠道时报错
• vhrahulkumar/openclaw-appplatform#52848: [Bug]: Control UI assets missing in NPM release 2026.3.22
• vhrahulkumar/openclaw-appplatform#52904: [Bug]: openclaw 2026.3.22 whatsapp plugin broke and cannot be downloaded

Release Notes

openclaw 2026.3.22

Breaking

• Plugins/install: bare openclaw plugins install <package> now prefers ClawHub before npm for npm-safe names, and only falls back to npm when ClawHub does not have that package or version. Docs: https://docs.openclaw.ai/tools/clawhub
• Browser/Chrome MCP: remove the legacy Chrome extension relay path, bundled extension assets, driver: "extension", and browser.relayBindHost. Run openclaw doctor --fix to migrate host-local browser config to existing-session / user; Docker, headless, sandbox, and remote browser flows still use raw CDP. Docs: https://docs.openclaw.ai/gateway/doctor and https://docs.openclaw.ai/tools/browser (#47893) Thanks @vincentkoc.
• Tools/image generation: standardize the stock image create/edit path on the core image_generate tool. The old nano-banana-pro docs/examples are gone; if you previously copied that sample-skill config, switch to agents.defaults.imageGenerationModel for built-in image generation or install a separate third-party skill explicitly.
• Skills/image generation: remove the bundled nano-banana-pro skill wrapper. Use agents.defaults.imageGenerationModel.primary: "google/gemini-3-pro-image-preview" for the native Nano Banana-style path instead.
• Plugins/SDK: the new public plugin SDK surface is openclaw/plugin-sdk/*; openclaw/extension-api is removed with no compatibility shim. Bundled plugins must use injected runtime for host-side operations (for example api.runtime.agent.runEmbeddedPiAgent) and any remaining direct imports must come from narrow openclaw/plugin-sdk/* subpaths instead of the monolithic SDK root. Docs: https://docs.openclaw.ai/plugins/sdk-migration and https://docs.openclaw.ai/plugins/sdk-overview
• Plugins/message discovery: require ChannelMessageActionAdapter.describeMessageTool(...) for shared message tool discovery. The legacy listActions, getCapabilities, and getToolSchema adapter methods are removed. Plugin authors should migrate message discovery to describeMessageTool(...) and keep channel-specific action runtime code inside the owning plugin package. Thanks @gumadeiras.
• Plugins/Matrix: add a new Matrix plugin backed by the official matrix-js-sdk. If you are upgrading from the previous public Matrix plugin, follow the migration guide: https://docs.openclaw.ai/install/migrating-matrix Thanks @gumadeiras.
• Config/env: remove legacy CLAWDBOT_* and MOLTBOT_* compatibility env names across runtime, installers, and test tooling. Use the matching OPENCLAW_* env names instead.
• Config/state: remove legacy .moltbot state-dir and moltbot.json auto-detection/migration fallback. If you still keep state under ~/.moltbot, move it to ~/.openclaw or set OPENCLAW_STATE_DIR / OPENCLAW_CONFIG_PATH explicitly. Docs: https://docs.openclaw.ai/install/migrating and https://docs.openclaw.ai/start/getting-started
• Exec/env sandbox: block build-tool JVM injection (MAVEN_OPTS, SBT_OPTS, GRADLE_OPTS, ANT_OPTS), glibc tunable exploitation (GLIBC_TUNABLES), and .NET dependency resolution hijack (DOTNET_ADDITIONAL_DEPS...

• Fixes vhrahulkumar/openclaw-appplatform#15

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.