Release 2.1.67 (2026-06-24)

Bug fixes

• handle volume-only boxes and report empty destroy-volume honestly (#1847) destroy_vm crashed on a box with a persistent volume but no VM (the steady state after a prior destroy preserved the volume): with no vm.tfstate the stored tfvars are absent and _run_tofu raised "no tofu vars supplied", breaking vrg-vm destroy and vrg-vm rebuild --destroy-first. destroy_vm is now a no-op when there is no vm.tfstate; the loud-failure guard still fires when the state exists but its tfvars are gone.

destroy-volume reported success even when tofu destroyed zero resources, masking a cloud disk orphaned under a different or legacy state dir. destroy_volume now returns whether the state managed a disk, and the command warns instead of claiming a phantom success.