Summary

OpenClaw updates consistently cause the gateway service to enter a crash loop when plugin validation rules change between versions. The service cannot start because the existing config becomes invalid, but openclaw doctor --fix is not automatically executed during updates.

Environment

• Host: Raspberry Pi (arm64)
• OS: Linux 6.12.62+rpt-rpi-v8
• Node: v22.22.0
• OpenClaw: 2.21 (2026.1.29)

Steps to Reproduce

1. Have OpenClaw running via systemd (openclaw-gateway.service)
2. Update OpenClaw (npm update -g openclaw or auto-update)
3. Service restarts → crash loop begins

Error Logs

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - plugins: plugin: extension entry escapes package directory: ./index.ts (x31)
  - plugins.entries.telegram: plugin not found: telegram
  - plugins.entries.slack: plugin not found: slack
  - plugins.entries.voice-call: plugin not found: voice-call
  - plugins.slots.memory: plugin not found: memory-core

Run: openclaw doctor --fix

Service then crash-looped 3320 times before manual intervention.

Expected Behavior

The update process should:

1. Run openclaw doctor --fix automatically before restarting, OR
2. Run it as part of the systemd ExecStartPre, OR
3. Auto-migrate configs when validation rules change

Current Workaround

Reinstall OpenClaw entirely (npm install -g openclaw), which regenerates a fresh config.

Impact

Every update requires manual reinstall to recover from crash loop. Users running headless (Pi, VPS) may lose access until they SSH in and fix manually.