Field incident from the first production run of this runbook (wy-7lmdp,
2026-07-18): all local writers were fenced, but a peer machine's scheduled
bridge-sync job was never stopped. One tick after the clean force-push it
pulled the new baseline, cross-merged it into its old chain, and pushed the
entire old history back to the freshly replaced remote.
Step 1 now tells the operator that writers include scheduled sync jobs on
every machine that syncs the database, to enumerate and verify them by
name, and why one live peer undoes the procedure. Step 5 orders re-enabling
per machine after its re-clone; the top warning says 'on every machine'.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>