[physicsdolphin]

What this changes

One FAQ entry. The Windows question currently names a single port; this adds the second maintained one, so Windows users landing here don't have to re-derive the ecosystem from issue threads.

What nv-uefi-unlocker is (for triage)

• Pre-driver UEFI app booted from USB (one-shot), chainloads the OS loader read-only afterwards. No resident boot entry, no NVRAM writes, no installer - deliberately the opposite of the "installers floating around" the FAQ warns about.
• Transaction core is a 1:1 port of this project's unlock_610 semantics; the firmware pipeline pins the same 610.43.03 inputs with SHA-256 checks and never redistributes blobs (same discipline as this repo's build).
• Real-machine evidence matrix across Turing / Ampere / Ada (27 device IDs with logs (a lot more in downstream community and social media comments), docs/compatibility.md), multi-GPU order unlocking, and a Turing GSP-firmware gate so 20-series users can't run it in a mode that TDRs.
• Active maintenance (v2.1.9-rc as of this week), zh+en docs, community reports triaged into the matrix.

Why here

This repo is the OG source both Windows ports credit. The FAQ is where Windows-bound traffic already lands; naming both maintained ports (and keeping the installer warning) is strictly more information for the reader. Happy to adjust wording - it's your README.