Summary

Upgrading to openclaw@2026.5.2 breaks the Discord channel at boot. The bundled sidecar-paths manifest still lists dist/extensions/discord/runtime-api.js and dist/extensions/discord/runtime-setter-api.js, but the corresponding compiled files were removed from the published tarball. The npm fallback @openclaw/discord@2026.5.2 is also broken — it ships only TypeScript source, no compiled .js.

End result: Discord channel never starts after boot. mcp__openclaw__message returns Channel is unavailable: discord.

Evidence

In /opt/homebrew/lib/node_modules/openclaw/dist/runtime-sidecar-paths-Dx-JkZjB.js (2026.5.2):

```js
var bundled_runtime_sidecar_paths_default = [
...
"dist/extensions/discord/runtime-api.js",
"dist/extensions/discord/runtime-setter-api.js",
...
];
```

But the directory dist/extensions/discord/ does not exist in the 2026.5.2 tarball. (An orphaned compiled bundle dist/discord-Cv2PBeIv.js exists at the dist root but is not referenced.)

The fallback ~/.openclaw/npm/node_modules/@openclaw/discord/index.ts exists, but:

• The package is shipped as TypeScript source only (no compiled JS).
• It imports ./subagent-hooks-api.js etc., which the loader cannot resolve.

Reproduction

1. Have 2026.4.29 installed with Discord configured and working.
2. npm i -g openclaw@2026.5.2.
3. Restart the gateway.
4. No channels/discord log entries appear; mcp__openclaw__message ... target=discord fails with "Channel is unavailable".

Workaround

Downgrade: npm i -g openclaw@2026.4.29 (restores compiled dist/extensions/discord/).

Suggested fix

Either:

• Re-include dist/extensions/discord/ in the 2026.5.x tarball, or
• Publish @openclaw/discord@2026.5.2 with compiled JS so the npm fallback path works, and update the sidecar manifest to point at the npm package paths instead of dist/extensions/discord/.

Environment

• macOS Darwin 25.4.0 (Mac mini)
• openclaw 2026.5.2 (broken) → downgraded to 2026.4.29 (working)
• Node 25.9.0