By: ananjiani <ananjiani@noreply.codeberg.org>
feat(framework13): add remote deployment (#337) ## Summary ```diff + reserve 192.168.1.63 for the Framework 13 Wi-Fi MAC + resolve framework13 over LAN and Tailscale from Aragorn + pin the Framework SSH host key for both names and addresses + deploy .#framework13: NixOS first, Home Manager second ``` ## Evidence - **Before:** Framework used a dynamic DHCP address and had no deploy-rs node. **After:** Nix evaluation shows both aliases on `192.168.1.63` and `100.64.0.6`, with ordered system/home profiles. - `nix flake check --no-build` — passed. - `tofu validate` — passed with existing provider deprecation warnings. - Targeted `tofu plan` — `1 to add, 0 to change, 0 to destroy`. - Full plan also found unrelated existing Mullvad drift. This PR does not apply Terraform. ## Merge Danger **Door:** two-way The code can be reverted. The DHCP reservation remains inactive until a separate `tofu apply`. **Blast Radius:** Framework/Aragorn Aragorn gains the deploy target and dual-address lookup. Hosts using the shared LAN map learn the Framework LAN address. Co-authored-by: Ammar Nanjiani <ammar.nanjiani@gmail.com> Reviewed-on: https://codeberg.org/ananjiani/infra/pulls/337