services.hermesVm -> services.hermenix throughout. setup.sh and
migrate-docker-hermes.sh are replaced by nu/hermenix.nu (setup + migrate
subcommands), packaged as a flake output (packages.${system}.hermenix,
pkgs.writers.writeNuBin) so it's installable without cloning conventions
beyond the repo itself. Both subcommands verified end-to-end against a
sandboxed dry run (stubbed disk/cache tools, a local ssh stand-in for the
migrate path) before landing.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Agent Instructions
MANDATORY FIRST ACTION: Read GUIDELINES.md in full before
doing anything in this repository. It is the single source of truth for agent
behavior here.
Key non-negotiable rules from that file:
- Always present a plan first and wait for user approval before making any changes — no matter how small the task.
- Never run builds or disk-writing steps (
nix build,hermenix setup's disk creation/image-write steps,ddto any disk image,nixos-rebuild switchon any consuming host) — zero exceptions, even if asked. - Never run
hermes-vm rollbackorhermes-ctl reseedwithout explicit, freshly-given confirmation — both destroy live guest state. - Never edit
guest/hardware.nix's disk labels without the operator having confirmedlsblk -foutput first. - Never commit live secrets (
.envvalues, API keys, tokens) toguest/hermes/home— it's a template seed, not where real credentials go. - When migrating existing data from elsewhere, copy — never move or delete — the source, until the operator confirms the migration is verified.
- Never commit or push changes unless explicitly asked.