Describe the bug

The core logger module (dist/logger-*.js) imports tslog directly:

import { Logger } from "tslog";

However, tslog is not bundled within the core package. It relies on the plugin runtime deps installer (bundled-runtime-deps.ts) to create a plugin-runtime-deps/openclaw-<version>-<hash>/package.json with tslog as its only dependency, then runs npm install to materialize it.

When this deps folder is rebuilt or partially missing, the logger module crashes with Cannot find module 'tslog', taking down the entire gateway.

This is not caused by a plugin failing -- it's the core logger module itself that requires tslog, so it should be a bundled dependency or have explicit handling, not rely on the plugin runtime deps bootstrap process.

Reproduction

1. Delete or corrupt the tslog install:

   rm -rf ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.24-*/node_modules/tslog

2. Start the gateway:

   openclaw gateway

3. Result: channels fail to load with:

   Cannot find package 'tslog' imported from /Users/.../plugin-runtime-deps/openclaw-2026.4.24-<hash>/dist/logger-<hash>.js

   The gateway enters auto-restart loop and eventually gets EADDRINUSE.

Environment

• OpenClaw version: 2026.4.24
• Node.js: 22+ (Apple Silicon M1)
• Install method: Homebrew
• OS: macOS

Root cause analysis

The dependency graph has a gap:

1. package.json lists tslog: ^4.10.2 as a top-level dependency, installed in /opt/homebrew/lib/node_modules/openclaw/node_modules/tslog
2. During runtime, the loader copies core modules to plugin-runtime-deps/openclaw-<hash>/dist/
3. The plugin runtime deps resolver creates a minimal package.json with tslog as the dependency and runs npm install
4. If the deps install is interrupted, skipped, or the sentinel checks fail to recognize that tslog is needed, the logger module in the deps folder fails to find tslog

The plugin runtime deps sentinel system (isInstalledDependencyVersionSatisfied, hasDependencySentinel) may be failing to verify tslog is present before the first startup, allowing the gateway to start and then crash when the logger is actually imported.

Expected behavior

tslog should always be available when the core logger module runs. Two options:

1. Include tslog as a bundled dependency that gets copied along with the core modules
2. Make the bootstrap process block until tslog is verified installed, with a clear error message instead of a silent crash

Current workaround

Manually install tslog in the runtime deps folder:

cd ~/.openclaw/plugin-runtime-deps/openclaw-*/
npm install tslog