Document the native aarch64-pc-windows-msvc build

CHANGELOG.md

@@ -23,6 +23,14 @@ that may never merge. They are not releases and are not listed here.
   the same `k1=v1&k2=v2` shape as a URL's own query string — for an API
   parameter this CLI's specs don't declare a flag for.
 
+- A native `aarch64-pc-windows-msvc` build. Windows on Arm ran the x64 build
+  under emulation before this — including inside a VM on Apple Silicon, the
+  larger of the two populations this serves — which `install.ps1` already
+  said out loud and now no longer has reason to. `install.ps1` already asked
+  the manifest for this target before falling back to the x64 one, and
+  `.cargo/config.toml` already named it, so publishing the artifact was the
+  whole client-side change.
+
 - `install.sh`/`install.ps1` now document a convention for `MAPBOX_CLI_INSTALL_SOURCE`
   when a coding agent invokes the installer on someone's behalf: `agent-<name>`
   (`agent-claude-code`, `agent-cursor`), so an access-log query can tell those

README.md

@@ -86,9 +86,10 @@ not allowed where you work, the archives are ordinary HTTP downloads, and
 curl -fsSL https://cli.mapbox.com/latest/manifest.json
 ```
 
-Five targets are published: `aarch64-apple-darwin`, `x86_64-apple-darwin`,
-`aarch64-unknown-linux-musl`, `x86_64-unknown-linux-musl` and
-`x86_64-pc-windows-msvc`. Pick yours, check it, then extract:
+Six targets are published: `aarch64-apple-darwin`, `x86_64-apple-darwin`,
+`aarch64-unknown-linux-musl`, `x86_64-unknown-linux-musl`,
+`x86_64-pc-windows-msvc` and `aarch64-pc-windows-msvc`. Pick yours, check it,
+then extract:
 
 ```sh
 version=v0.2.1