Add hermenix setup --clean for a fully fresh start

Encodes the "start over" runbook from tonight's incident as a flag:
stops hermes-vm.service, deletes system.raw/state.raw/OVMF_VARS.fd,
then continues through the normal setup flow. Leaves the btrfs
subvolumes and any snapshots untouched - only the files inside them.
Gated behind a confirm-word ("clean") since it's destructive.

Verified in a sandbox: confirms it stops the VM and removes exactly
the three targeted files (nothing else), that declining the
confirm-word aborts without touching anything, and that it correctly
falls through into the normal disk-creation flow afterward.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
ariandClaude Sonnet 5 committed 2026-09-16 10:42:41 -04:00
1 parent ff752cb803
commit 3c491b1624
2 files changed
+22

No files matched your search

+9
View File
@@ -636,6 +636,15 @@ fresh image to the system disk, and leave the state disk alone — Hermes comes
back with its identity, memories, workspace and NixOS config intact. That is
the intended repair, not a last resort.
### Starting completely fresh
`hermenix setup --clean` stops the VM and deletes the existing
`system.raw`/`state.raw`/UEFI vars before walking through setup again — for
when you want a genuinely clean first boot rather than the disk-exists,
skip-ahead path. It leaves the btrfs subvolumes and any snapshots alone
(only the files inside them), and asks you to type `clean` to confirm before
touching anything.
---
## Nix flavour