Recover from developer disasters. Use when someone force-pushed to main, leaked credentials in git, ran out of disk space, killed the wrong process, corrupted a database, broke a deploy, locked themselves out of SSH, lost commits after a bad rebase, or hit any other "oh no" moment that needs immediate, calm, step-by-step recovery.
Initial release — step-by-step recovery for git disasters, credential leaks, disk full, process emergencies, database failures, deploy rollbacks, access lockouts, and network failures