fix(docs): remove pre-fill config requirement and irrelevant static-IP note

Menu collects all values interactively at boot -- no pre-configuration
needed before building. Static IP note on boot page was about future
node deployment requirements, not Beacon WinPE network bootstrap.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013AZySkzowyq4Ne2hrSRRAL

Author: kristopherjturner

README.md

@@ -50,17 +50,10 @@ For non-Dell hardware, supply your own drivers:
 
 ## Quick start
 
-### 1. Populate config
+!!! tip "No pre-configuration required"
+    All environment values (DC IPs, DNS, gateway, domain FQDN) are collected interactively by the Beacon menu at boot. Just build the ISO and boot it.
 
-Copy `src/config/validation-config.example.json` to `src/config/validation-config.json` and fill in your deployment values (DNS, AD domain, node IPs, gateway).
-
-Regenerate the Azure endpoint list if needed:
-
-```powershell
-.\src\Convert-EndpointsToJson.ps1
-```
-
-### 2. Build
+### 1. Build
 
 ```powershell
 # Minimal — downloads PS7, no drivers

docs/getting-started/boot.md

@@ -24,15 +24,15 @@ Set the node's one-time boot order to the USB device.
 ## What happens at boot
 
 ```
-wpeinit                   ← WinPE network stack init
-Start-AzlBeacon.ps1       ← Menu orchestrator
-  Start-NetworkBootstrap  ← DHCP detect / static IP prompt
-  Main menu               ← Choose: AD / Local Identity / Network+Firewall / Full sweep
+wpeinit                   <- WinPE network stack init
+Start-AzlBeacon.ps1       <- Menu orchestrator
+  Start-NetworkBootstrap  <- DHCP detect / static IP prompt
+  Main menu               <- Choose: AD / Local Identity / Network+Firewall / Full sweep
 ```
 
 ## Network bootstrap
 
-On boot, Beacon waits **15 seconds** for a DHCP lease. If none is detected, you are prompted for:
+On boot, Beacon waits **15 seconds** for a DHCP lease on the management NIC. If none is detected, you are prompted for:
 
 | Prompt | Example |
 |---|---|
@@ -41,9 +41,7 @@ On boot, Beacon waits **15 seconds** for a DHCP lease. If none is detected, you
 | Default gateway | `10.10.0.1` |
 | Primary DNS | `10.10.0.10` |
 
-!!! note "Local Identity deployments require static IPs"
-    Microsoft requires static IP addresses for all cluster nodes in a Local Identity (AD-less) deployment.
-    DHCP is not supported for node NICs in this mode.
+This gives Beacon connectivity to run the validation — it has nothing to do with how the eventual Azure Local cluster nodes will be addressed.
 
 ## Results
 

docs/getting-started/prerequisites.md

@@ -2,8 +2,8 @@
 
 ## Build machine
 
-!!! note "Build once, boot anywhere"
-    You build the ISO once on a Windows machine, then boot it on any node (or on a separate machine on the management network).
+!!! note "Build once, boot on any Dell AX node"
+    You build the ISO once on a Windows machine with ADK installed, then mount it via iDRAC virtual media on each Dell AX node.
 
 | Requirement | Details |
 |---|---|
@@ -17,7 +17,7 @@
 
 ## Dell AX NIC drivers
 
-NIC drivers for Dell AX 16G nodes are **bundled in the repo** under `drivers/dell-ax/` (extracted from Dell SBE bundle `5.0.2603.1641`). No separate download required.
+NIC drivers for Dell AX 16G nodes are **bundled in the repo** under `drivers/dell-ax/` (extracted from Dell SBE bundle `5.0.2603.1641`). No separate download required — the build script picks them up automatically.
 
 | Driver | File | Version |
 |---|---|---|
@@ -29,20 +29,10 @@ NIC drivers for Dell AX 16G nodes are **bundled in the repo** under `drivers/del
 
 ## Network requirements
 
-The Beacon image needs to reach Azure endpoints to run the full endpoint sweep. Ensure:
+The Beacon image needs outbound access to Azure endpoints to run the endpoint sweep. Ensure the management VLAN where Beacon will boot has:
 
-- Management VLAN access from the machine where Beacon boots
 - Outbound HTTPS (443) to Azure endpoints (see [Endpoint List](../reference/endpoints.md))
-- DNS resolution (UDP/TCP 53) — can be tested interactively if DNS is in question
+- DNS resolution (UDP/TCP 53)
 
-## Validation config
-
-Copy `src/config/validation-config.example.json` to `src/config/validation-config.json` before building and fill in your environment's values (DC IPs, gateway, DNS, node IPs, etc.).
-
-```powershell title="Create your validation config"
-Copy-Item src\config\validation-config.example.json src\config\validation-config.json
-# Edit src\config\validation-config.json with your values
-```
-
-!!! warning
-    `validation-config.json` is gitignored. Never commit it — it contains environment-specific IPs.
+!!! tip "No pre-configuration required"
+    All environment values (DC IPs, DNS servers, gateway, domain FQDN) are collected interactively by the Beacon menu at boot. Nothing needs to be filled in before building the ISO.