Description

openclaw doctor --fix detects stale plugin entries in plugins.allow but doesn't auto-remove them. The gateway then refuses to start because v2026.3.22 validates plugins.allow strictly.

Steps to Reproduce

1. Install a plugin (e.g. acpx)
2. Remove/uninstall the plugin
3. Leave the entry in plugins.allow and plugins.entries in openclaw.json
4. Upgrade to v2026.3.22
5. Gateway fails to start: Invalid config: plugins.allow: plugin not found: acpx
6. Run openclaw doctor --fix — it detects the stale entry but does not remove it

Expected Behaviour

openclaw doctor --fix should remove stale plugin entries from both plugins.allow and plugins.entries when the referenced plugin is not installed.

Actual Behaviour

Doctor reports the warning but leaves the config unchanged. The gateway remains broken until you manually edit openclaw.json.

Workaround

Manually remove the stale plugin from plugins.allow and plugins.entries in ~/.openclaw/openclaw.json, then openclaw gateway restart.

Environment

• OpenClaw v2026.3.22
• Ubuntu 24.04 (arm64)
• Affected 3 of 5 agents in our fleet (all had acpx previously installed then removed)

Impact

This is a fleet-wide issue — any agent that previously had a plugin installed and removed will break on upgrade to v2026.3.22+ since the stricter config validation was introduced. The fix is trivial (a JSON edit) but the failure mode is opaque for users who don't know to check plugins.allow.