Declare eden and ragnarok in tofu (ADR-0076's scope), and settle how ragnarok's isolation proof survives it #1443

Finding

ADR-0076's scope names "#421's attack VM and targets". Two guests are built outside the pipeline, so tofu can't rebuild either:

• eden (BloodHound, VMID 141 on Saruman) is a hand qm clone 901 141 (build-the-bloodhound-guest.md:71);
• ragnarok (the attack VM, VMID 130 on gandalf) comes from scripts/make-attack-vm.sh.

Decided

Declare both in tofu (owner's choice on audit finding #18, over superseding ADR-0076).

What has to be settled first: why this is an issue and not yet a PR

1. A second provider. phoenix.env and gandalf.env export the same names (PROXMOX_URL, PROXMOX_TOKEN_ID, PROXMOX_TOKEN_SECRET), and make-attack-vm.sh refuses to run unless PROXMOX_URL is gandalf's. A provider "proxmox" { alias = "gandalf" } needs its own variables (for example TF_VAR_gandalf_endpoint and a token), with gandalf's CA trusted on phoenix (already true, per build-the-lab-templates.md §5), and an ACL so phoenix@pve on gandalf can create VMID 130.

2. ragnarok is more than a clone. make-attack-vm.sh also:

   • sets net1 on vmbr1 with no gateway (172.30.30.10/24);
   • writes 99-no-forward.conf;
   • proves §8 check three (forwarding off, no NAT) over SSH, against a host key read through the guest agent (ADR-0085).

   tofu can make the VM and its NICs. The no-forward sysctl and the proof are not tofu's job. Either make-attack-vm.sh keeps them as a post-apply --verify-only, or that moves into the module's cloud-init plus a separate proof script. ADR-0017 says the range is "rebuilt, not repaired" by that script, so this probably wants a short ADR that amends 0017 and 0076.

3. Identities. Both MACs go in tofu/identities.auto.tfvars (tofu/guests.tf publishes 15 full guest MACs and 6 SMBIOS UUIDs, against security.md's do-not-publish list #1420's file); ragnarok has no reservation today (net0 is DHCP from the pool).

4. Import, then plan. Import both, and require a plan of No changes before any apply. eden holds the BloodHound graph, and a replace would lose it.

Steps once 1 and 2 are decided

tofu/ gets the gandalf provider, then the eden and ragnarok entries, then import blocks. phoenix runs plan (it must say No changes) and then make-attack-vm.sh --verify-only. Then the runbooks (build-the-bloodhound-guest.md, build-the-playground.md §5) switch to the pipeline.

Source: Phase 1 audit, finding #18.