docs: add stale OpenAI cooldown recovery runbook

[EdgeClaws]

Summary

• document how to distinguish stale OpenAI/Codex cooldown state from a real provider limit
• require schema verification and a consistent SQLite backup before mutation
• clear only explicitly confirmed profile markers and preserve unrelated auth state
• verify database integrity plus a fresh OpenClaw provider attempt
• define when a gateway reload is actually warranted

Validation

• git diff --check
• exercised the documented JSON mutation against a disposable SQLite fixture
• confirmed selected stale fields were removed while unrelated OpenAI and Anthropic entries remained unchanged
• PRAGMA integrity_check returned ok

No account identifiers, credentials, tokens, or host-specific paths are included.