Add catalog-sourced GPU display driver scrapers (Intel/NVIDIA/AMD)

[jm2]

Summary

Extends the driver scrapers to GPU display drivers, kept single-source from the Microsoft Update Catalog — verified that NVIDIA (consumer GeForce and RTX/Quadro pro), AMD (Radeon RX and Radeon Pro), and Intel are all HWID-indexed, complete, and WHQL-signed on the catalog. So this needs no vendor-direct backend, no 7-Zip, no new dependency, and no engine change: each vendor is a new .psd1 + a thin shim feeding the existing Invoke-DriverScrape, exactly like the Wi-Fi scrapers.

What's added

Data tables (catalogscrape/)

• intel-gfx.psd1 (Intel_Display) — unified DCH; one device, multi-HWID dedup (Arc A/B, Iris Xe, recent iGPU) → one download.
• nvidia-gfx.psd1 (NVIDIA_Display) — GeForce consumer (unified across Ampere/Ada/Blackwell) + RTX/Quadro pro; HWID targeting auto-resolves the pro production branch (a distinct, newer package).
• amd-gfx.psd1 (AMD_Display) — Radeon RX + Radeon Pro, one device per family (RDNA4/3/2 + W7000/W6000) to avoid the current/legacy branch mis-pick.

Shims (repo root) — Get-{Intel,Nvidia,Amd}GraphicsDrivers.ps1, post-boot-convenience scope documented. Run standalone on a live box (-Install → pnputil).

build_win11pxe.ps1

• -GraphicsDrivers Intel|AMD|NVIDIA|All (ValidateSet), excluded from the -Drivers glob, mapped to shims, fed into the same DISM /Add-Driver.
• Scraper Wait-Job timeout scales to 60 min when graphics are included (noted as a shared global budget).
• Comment at $nicDriverDefs: GPU drivers are deliberately not boot-promoted (a GPU is on neither the boot nor the iSCSI data path).

Test-CatalogScrape.ps1 — three tables added to $expectKeys (so the universal Key/Label/Queries schema check covers them) + targeted assertions (Intel-unified / NVIDIA consumer-vs-pro / AMD Radeon-Pro).

README.md — scraper table rows + -GraphicsDrivers documentation.

Scope decisions (deliberate)

• Userspace utilities out of scope. A bare INF install (offline DISM or live pnputil) yields a fully accelerated driver incl. the OpenGL/Vulkan/OpenCL/D3D ICDs and the CUDA/NVENC runtime; only the Microsoft Store control-panel apps (NVIDIA App, AMD Adrenalin, Intel Graphics Software) are absent. Radeon Pro cards get the base WHQL driver, not the ISV-certified PRO Edition.
• x64 only. Discrete GPUs have no ARM64 Windows driver; Qualcomm Adreno is ACPI-enumerated and not on the catalog by any query shape, so no ARM64 GPU table is shipped (the arch plumbing already supports -Architecture arm64 if that changes).
• Accepted limitation: newest-WHQL-on-catalog, not day-0 Game Ready, and no GRD/Studio/branch pinning — consistent with the existing scrapers' bar.

Verification

• All touched/new .ps1 files AST-parse clean; the three .psd1 load with expected device counts (1/2/5).
• Test-CatalogScrape.ps1: 81 passed, 0 failed (+9 new).
• Invoke-ScriptAnalyzer not run locally (PSScriptAnalyzer not installed in the dev env); additions use full cmdlet names and mirror existing patterns — CI will cover it.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request adds support for scraping and injecting GPU display drivers (Intel, AMD, and NVIDIA) from the Microsoft Update Catalog. It introduces new scraper scripts, configuration files, and updates build_win11pxe.ps1 with a -GraphicsDrivers parameter to handle these large, post-boot-only drivers. The review feedback suggests two improvements in build_win11pxe.ps1: wrapping the Wait-Job call in a conditional block to prevent crashes when no scrapers are run, and using -LiteralPath with Test-Path and Get-Item to avoid wildcard expansion issues in paths.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If no scraper scripts are found or executed (for example, if -GraphicsDrivers is specified but the corresponding scraper script is missing, and -Drivers is not set), $scraperJobs will be empty or $null. Piping an empty or $null collection to Wait-Job will throw a terminating error under $ErrorActionPreference = 'Stop', which aborts the entire VHDX build process after a lengthy image application. Wrapping the Wait-Job call in an if ($scraperJobs) block safely avoids this crash.

        if ($scraperJobs) {
            Write-Host "    -> Waiting for $($scraperJobs.Count) scrapers to complete (max $([int]($scraperTimeoutSec / 60)) min)..."
            $scraperJobs | Wait-Job -Timeout $scraperTimeoutSec | Out-Null
        }

[gemini-code-assist]

Using the default -Path parameter for Test-Path and Get-Item can cause failures if the repository is cloned into a directory path containing wildcard characters (such as [ or ]). Using -LiteralPath ensures that the path is treated as a literal string, preventing wildcard expansion issues.

                $gpuPath = Join-Path $PSScriptRoot $gpuName
                if (Test-Path -LiteralPath $gpuPath) { $driverScripts += Get-Item -LiteralPath $gpuPath }