backup-restorelisted

<!-- Generated from `.claude/skills/backup-restore/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> # Backup Restore Three jobs, in increasing weight: prove a backup is intact, prove it actually restores, and bring one back. All three are driven by one tool, and none of them will ever overwrite the live vault: a restore always goes to a fresh folder the user chooses, to inspect and move into place themselves. ## Test mode (the one to suggest routinely) ```bash python3 core/backup/restore_vault.py test ``` This checks the newest set's fingerprints, verifies the version-history bundle with git's own verifier, extracts the whole archive into a throwaway temporary folder, counts what came out, and deletes the extraction. It proves a restore works without touching anything. Suggest running it once after setup and occasionally after that; a backup that has never been test-restored is a hope, not a backup. ## Verify only (quick integrity check) ```bash python3 core/backup/restore_vault.py verify ``` Fingerprint and history checks only, no extraction. Add `--set <stamp>` for a specific older set, or `--source /path` for a folder other than the configured destination. ## Restore for real First ask which set they want (default is the newest) and where the restored copy should go. The target must be a new or empty folder. ```bash python3 core/backup/restore_vault.py restore --to /path/to/fresh-folder ``` Then be explicit about three things: 1. **The live v