Use GitHub-hosted Windows for the temporary Tauri ARM64 test job because the Blacksmith Windows Build Tools image does not expose the ARM64 MSVC linker/libs we need. The hosted Windows images already include LLVM and VC.Tools.ARM64, so we can drop the custom installer and linker hacks.
Rename the temporary ARM64 linker-path local so the PowerShell step stops colliding with the built-in read-only variable before it rewrites LIB and the target linker.
Pin the Windows ARM64 test build to the HostX64 ARM64 linker and overwrite LIB with only ARM64 SDK and MSVC paths so Tauri stops resolving x64 runtimes during cross-link.
Invoke the Visual Studio installer directly so the Build Tools install path with spaces stays intact. The previous Start-Process call split the path and caused setup.exe to target instead of the actual VS instance.
Use the documented Visual Studio installer entrypoint for modify operations and remove the unsupported wait flag that was returning exit code 87 on the Blacksmith Windows runner.
Install the Visual Studio ARM64 toolchain and switch the temporary Windows ARM64 test build into the amd64_arm64 developer environment so the Tauri linker stops pulling x64 SDK libraries.
Install clang with Chocolatey on the temporary Windows ARM64 test workflow because the Blacksmith Windows image does not expose LLVM through the Visual Studio path lookup.
Run the temporary Windows ARM64 workflow from the PR head branch without release credentials. Disable Tauri updater artifacts so the build can run without signing secrets.
