registry: install azure-cli from the official Windows zip

registry/azure.toml

@@ -4,6 +4,31 @@ test = { cmd = "az --version", expected = "azure-cli                         {{v
 version_order = "semver"
 
 bins = ["az"]
+
+# Windows: the official ZIP release. It bundles its own python.exe and its
+# `bin/az.cmd` locates it relatively, so it works wherever mise unpacks it.
+# The PyPI package cannot: it ships `az.bat` as a plain script rather than a
+# console_scripts entry point, and that script resolves python next to itself
+# (`%~dp0\python.exe`), which is only true inside the venv's Scripts directory
+# — not in the bin directory uv/pipx copy it to.
+[[backends]]
+full = "github:Azure/azure-cli"
+platforms = ["windows"]
+
+[backends.options]
+version_prefix = "azure-cli-"
+
+# ARM64 gets the same x64 ZIP: Microsoft publishes no ARM64 asset, the launcher
+# defect above is not architecture-specific, and Windows 11 ARM runs x64 user-mode
+# code transparently. Verified on a `windows-11-arm` runner — `az --version` works
+# through `mise exec` and through the shim, and the bundled `python.exe` is an x64
+# binary. Same reasoning as `codeql`, which points macos-arm64 at the osx64 asset.
+[backends.options.platforms.windows-arm64]
+asset_pattern = "azure-cli-{{ version }}-x64.zip"
+
+# Everywhere else: PyPI. There is no Linux release asset, and the macOS tarball
+# does not bundle python — outside a Homebrew Cask path its launcher requires
+# AZ_PYTHON to be set.
 [[backends]]
 full = "pipx:azure-cli"