fix(docs): correct stale category numbers and NIC driver instructions

- README: 7→6 categories, fix NIC driver section (bundled in repo,
  not export-from-node), fix boot step (menu launches, not auto-run)
- network-firewall.md: AD ports = Category 3 not 4
- environment-checker.md: EnvChecker = Cat-5, Arc = Cat-6 (not 6/7)
- results-schema.md: example shows Cat-3-AD not Cat-4-AD
- build.md: air-gap note references Category 5 not 6

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

Author: kristopherjturner

README.md

@@ -9,7 +9,7 @@ Boot it on bare metal before you touch the deployment wizard. Know your environm
 
 ## What it does
 
-On boot, `Start-AzlValidation.ps1` runs 7 validation categories grounded in Microsoft and Dell source documents:
+On boot, `Start-AzlBeacon.ps1` presents an interactive menu. Choose your deployment path — it calls `Start-AzlValidation.ps1` to run the applicable categories from these 6, all grounded in Microsoft and Dell source documents:
 
 | # | Category | What it checks |
 |---|---|---|
@@ -36,16 +36,16 @@ Results land at `X:\results\` on the WinPE RAM drive in JSON format. Copy off be
 | Administrator rights | DISM mount requires elevation |
 | Internet access | For PS7 download + `Save-Module` (skippable — see air-gap build) |
 
-### NIC drivers (recommended)
+### NIC drivers
 
-Inject 25 GbE NIC drivers so ports come up on first boot. Export from a provisioned node:
+Dell AX 16G NIC drivers are **bundled in the repo** at `drivers/dell-ax/` (extracted from Dell SBE bundle `5.0.2603.1641`). The build script picks them up automatically — no separate download or driver export required.
+
+For non-Dell hardware, supply your own drivers:
 
 ```powershell
-Export-WindowsDriver -Online -Destination C:\drivers
+.\src\Build-WinPEImage.ps1 -DriverPath C:\my-drivers
 ```
 
-Or download the full driver pack for your hardware and point `-DriverPath` at the extracted folder.
-
 ---
 
 ## Quick start
@@ -88,7 +88,7 @@ Output: `src/output/azl-validate-<yyyyMMdd>.iso`
 2. Open **Virtual Console → Virtual Media → Connect Virtual Media**.
 3. Under **Map CD/DVD**, select the ISO and click **Map Device**.
 4. Reboot: power menu → one-time boot (F11) → **Virtual CD/DVD**.
-5. WinPE loads, `startnet.cmd` runs, validation starts automatically.
+5. WinPE loads, `startnet.cmd` runs, the Beacon menu appears.
 
 To preserve results before reboot:
 

docs/getting-started/build.md

@@ -29,7 +29,7 @@ If your build machine has limited or no internet access, pre-download the PS7 LT
 ```
 
 !!! warning "Module not included in air-gapped builds"
-    Without `AzStackHci.EnvironmentChecker`, Category 6 (environment checker) is skipped.
+    Without `AzStackHci.EnvironmentChecker`, Category 5 (environment checker) is skipped.
     Pre-stage the module at `<WorkspacePath>\mount\Tools\Modules` before the unmount step, or
     run the module-based tests from a staging server post-OS.
 

docs/reference/environment-checker.md

@@ -12,9 +12,9 @@ AzL Beacon bundles and calls the Microsoft `AzStackHci.EnvironmentChecker` Power
 
 | Validator | Cmdlet | When called |
 |---|---|---|
-| Connectivity | `Invoke-AzStackHciConnectivityValidation` | Category 6, all paths |
-| Network | `Invoke-AzStackHciNetworkValidation` | Category 6, all paths |
-| Arc integration | `Invoke-AzStackHciArcIntegrationValidation` | Category 7 — optional, requires Azure sign-in |
+| Connectivity | `Invoke-AzStackHciConnectivityValidation` | Category 5, all paths |
+| Network | `Invoke-AzStackHciNetworkValidation` | Category 5, all paths |
+| Arc integration | `Invoke-AzStackHciArcIntegrationValidation` | Category 6 — optional, requires Azure sign-in |
 
 ## WinPE limitations
 

docs/reference/results-schema.md

@@ -28,7 +28,7 @@ Beacon saves results to `X:\results\validation-<timestamp>.json`.
       "DurationMs": 38
     },
     {
-      "Category": "Cat-4-AD",
+      "Category": "Cat-3-AD",
       "Name": "AD-LDAP-10.10.0.10",
       "Target": "10.10.0.10:389",
       "Status": "Fail",

docs/validation/network-firewall.md

@@ -4,7 +4,7 @@ Select **option 3** from the Beacon main menu to run a focused networking and fi
 
 ## What it covers
 
-This path runs everything except the AD port tests (Category 4). It's ideal for:
+This path runs everything except the AD port tests (Category 3). It's ideal for:
 
 - Verifying firewall policy before any identity configuration
 - Checking endpoint reachability from the management VLAN