When git --force Backfired: How an Overlooked Archive Branch Saved 90 Lost Commits

This incident underscores how a single errant git command can erase months of development history—and why developers need layered backup strategies. The recovery of 90 of 130 lost commits from an accidentally-created archive branch shows that even unplanned safeguards matter. Beyond this technical lesson, the disaster exposed deeper repository hygiene problems including AI-generated content patterns in documentation and missing contributor guidelines that many projects ignore.