Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After updating to OpenClaw 2026.4.22 (00bd2cf), Telegram channel startup repeatedly fails with:
Cannot find package 'openclaw' imported from .../.openclaw/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/...
It appears to resolve a stale runtime hash (4eca...) although the installed build is 00bd2cf.

Steps to reproduce

1. Install/update to [email protected] (global npm install).
2. Start gateway as non-root user.
3. Observe startup logs for Telegram provider

Expected behavior

Telegram provider should load runtime deps from the currently installed build and start normally.

Actual behavior

Telegram provider exits and auto-restarts in a loop with:
Cannot find package 'openclaw' imported from ...openclaw-2026.4.22-4eca.../dist/extensions/telegram/monitor-polling.runtime-...js

OpenClaw version

2026.4.22 (00bd2cf)

Operating system

Linux (Debian/Ubuntu-like)

Install method

Global npm install (/usr/lib/node_modules/openclaw)

Model

openai/gpt-5.2 (agent model in gateway logs)

Provider / routing chain

OpenRouter (via OpenClaw gateway)

Additional provider/model setup details

No unusual model/provider customization relevant to this issue.
Problem occurs during Telegram plugin/channel startup.

Logs, screenshots, and evidence

- `[plugins] telegram installed bundled runtime deps: @grammyjs/runner..., grammy...`
- `[telegram] [default] starting provider (...)`
- `[telegram] [default] channel exited: Cannot find package 'openclaw' imported from /home/.../.openclaw/plugin-runtime-deps/openclaw-2026.4.22-4eca.../dist/extensions/telegram/monitor-polling.runtime-...js`
- auto-restart repeats

Troubleshooting already done:
- cleared `~/.openclaw/plugin-runtime-deps`, `~/.openclaw/cache`, npm cache
- reinstalled `[email protected]`
- verified old `4eca...` dirs no longer present on disk
- issue persists at runtime

Workaround:
- downgrade to `2026.4.20` restores functionality.

Impact and severity

High for affected installs:
Telegram channel is unusable (crash/restart loop), blocks messaging workflows.

Additional information

Potentially related to previous bundled runtime dependency issues:

• v2026.3.31 npm package appears to miss runtime deps for bundled plugins (Telegram/Bedrock load failures) #58701
• Telegram plugin fails after update: grammy peer deps not auto-installed #60263
• v4.1 update: bundled plugin deps not installed (Telegram/Discord broken after update) #59286
• Telegram plugin crashes CLI: grammy not in package dependencies, lost on every update #59867
• openclaw doctor fails on 2026.4.20 with missing @whiskeysockets/baileys in WhatsApp bundled runtime after successful npm rebuild #69842

This report may be a variant specifically involving stale runtime hash resolution in 2026.4.22.