backup-setuplisted

<!-- Generated from `.claude/skills/backup-setup/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> # Backup Setup Set up (or change) automatic backups of the whole vault: notes, projects, people, tasks, settings, and the vault's own version history. Runs on a schedule in the background, keeps a sensible ladder of older copies, and tells you loudly if it ever stops working. ## What a backup contains Every run writes a **set** of three files, stamped with the date and time: | File | What it is | |------|-----------| | `dex-vault-<stamp>.tar.gz` | The whole vault as one compressed archive | | `dex-vault-<stamp>.bundle` | The vault's version history, individually verified so a restore is provable rather than hoped for | | `dex-vault-<stamp>.sha256` | Fingerprints of both, so damage in storage is detectable | Secrets are deliberately left out: the `.env` file holding AI keys, generated tool configuration that can reference credentials, saved sign-in tokens (`*token.json`), the `System/credentials` folder, any `.key` or `.pem` file, virtual environments, and caches. Never store those in a synced folder. Keys live in the system keychain or get re-entered on restore. See `docs/backup-restore.md` for what a full rebuild needs beyond these files. ## Step 1: Where should backups go? Ask which destination suits them, in plain terms: 1. **A synced folder** (default, simplest): OneDrive, iCloud Drive, Dropbox, Google Drive, or a plugged-in external disk. Anything