A cognitive protocol for safely managing and auditing OpenClaw application upgrades. Analyzes configuration-level risks (schema, defaults) and runtime-level...
This protocol is designed to be conservative. It's better to flag a false positive than miss a silent breaking change.
Runtime risks are often harder to detect than config risks. Pay extra attention to behavioral keywords like "improve", "fix", "refactor" in areas you actively use (sessions, routing, streaming).
When in doubt, ask the operator about their workflow patterns before deeming a risk "Low" priority.
