Halloween Dev Horror: 5 micro stories with protective charms

Happy Halloween. Scarier than ghost stories: 5 micro horror stories that could actually happen. Three sentences each.
Night 1, "The Window": Two terminals open — staging and production. You hit Enter. Then you read the window title. Charm: color-code production; double-confirm dangerous commands.
Night 2, "The Space": You meant to delete ./build. You typed rm -rf . /build. Charm: ls first to see what you're deleting; protect and back up key directories.
Night 3, "The Backup": Every night, the backup said "success". Then you needed to restore. The files were empty. Charm: a backup only counts if you can restore it — practice. In 2017 GitLab accidentally deleted a production database, several backup methods failed, and about 6 hours of data was lost; their public post-mortem is still required reading.
Night 4, "The Key": 3 a.m., a cloud billing alert with extra zeros. You remember the config file you pushed to a public repo yesterday. Charm: scan commits for secrets; if leaked, revoke and regenerate immediately.
Night 5, "Friday": 5 p.m. Friday. "It's one line, quick deploy." Charm: …just don't.
3 everyday guardrails: preview before you run anything dangerous; actually restore a backup now and then; keep keys out of repos.
When AI can run commands for you, install guardrails first: BFBT Code's Hooks can require checks before risky steps, and DTworkeasy lets you stop things from your phone.
Which story gave you chills? Got one of your own?