# Aftermath — A throwaway test run rewrote our live database

A flowingkhaos fix · monitoring · updated 17 Oct 2026
Source: https://flowingkhaos.com/fixes/worktree-run-migrated-production-database/aftermath

Monitoring. The repair is landed and measured on a bench. No feature run has gone through it yet.

**Reopen if** the first real run's log does not name a `piv-db-<id>` container, or the harvest step at the end prints no removal line. Either means a run found a different database than the one we gave it.

**Receipt, when resolved.** The first real run's `run-db` output naming its container, and the harvest's `removed` line.

**What stays manual.** The second workstation (a Mac) still needs the hosts entry and the container runtime.

**The rule that changed.** A run's gate exports its own database before it runs anything. An env file in a checkout never reaches a gate.

**Next read.** The same lesson with money instead of data: the $5 video bill a pricing API said was $1.86. And the workshop step on holding a dangerous call and asking, which is the second net above.