Roll the economy back to 02:14, after a dry run

A dupe exploit goes around Discord at 01:50. By 02:40 eleven hundred players hold gold that never existed, and the auction house is pricing itself against them.

The economy lives in a KV table on hoody-sqlite, and the table keeps history. You call POST /kv/rollback?to_timestamp=…&dry_run=true with the timestamp of the exploit's first known trade. The response lists every key that would change: wallets, listings, guild banks: without touching one. You skim it, spot the two legitimate whales caught inside the window, note their keys for a manual credit, and re-issue the call with confirm=yes. The keys rewrite atomically. kv/diff?from=&to= is the postmortem.

On a hot database this is a restore-from-backup, a maintenance window, and an apology post. Here it is a query with a preview step.

Rollback is a table operation, not a disaster recovery plan.