OpenClaw 2026.3.13 regression causes false unreachable status reports

Diagnostic regression in OpenClaw 2026.3.13

A regression in OpenClaw version 2026.3.13 causes false negative status reports while the underlying gateway connectivity remains functional. The issue appears to be in the diagnostic/probe path rather than actual authentication or configuration problems.

Specific symptoms observed

On a Debian 13 host with identical configuration between versions:

• openclaw gateway status reports RPC probe OK
• openclaw status --all falsely reports "unreachable (missing scope: operator.read)"
• openclaw security audit --deep reports "gateway.probe_failed"

Rolling back to version 2026.3.12 immediately resolves the issue:

• openclaw status --all returns healthy status
• All warnings clear from the security audit

Impact and workaround

This regression affects monitoring and alerting systems that rely on openclaw status --all output. The gateway functionality itself appears unaffected - RPC probes continue to work correctly. The issue is specific to version 2026.3.13 and rolling back to 2026.3.12 provides an immediate workaround while maintaining full gateway functionality.

For developers using OpenClaw in production environments, this regression highlights the importance of testing status and monitoring commands after upgrades, even when core functionality appears to be working correctly.