Rollback still needs compatibility checks

A prompt about verifying that the previous release can run safely against current production state.

Rollback first is strongest when the previous version is known good, but compatibility is the detail that gets skipped. If data, queues, cache, flags, or third-party contracts changed after the deploy, the old build may not be safe anymore. What compatibility check belongs at the top of a rollback runbook?