Automatic safety snapshots before big changes
Pekan now takes an automatic snapshot of your local database right before the handful of actions that can change or remove a lot of data at once, so there's always a recovery point if something goes wrong. Deleting a project (which cascades to every column, task, comment, and attachment inside it) always creates a snapshot first. Large bulk operations (updating, completing, or sending ten or more tasks to review in a single call, the kind of thing an AI agent might do) snapshot before they apply, too.
A snapshot is a complete, consistent copy of your board database, written to a managed folder on your machine. It's separate from the manual backups you can already save from Settings: these are app-managed recovery files that Pekan creates for you and prunes automatically, keeping the last ten, nothing older than a week, and staying under a size cap. If a project delete can't be snapshotted for some reason, Pekan blocks the delete rather than risk destroying data without a safety net.
You can see and manage your snapshots under Settings → Automatic snapshots. The list shows what each snapshot was for, when it was taken, and how large it is, with a button to reveal the folder in your file browser. To restore one, quit Pekan and swap your live database file for a snapshot copy: the folder view walks you through it. This feature is local-mode only.
If you drive coding agents from your board, this is a quiet but meaningful safety net: an agent that fires a large bulk change or an accidental project delete now leaves you a recoverable checkpoint automatically, with no setup required.