Revert the forced Dev Drive VHD experiment after CI showed the explicit VHD path was viable but slower than using the runner-provided D: drive on windows-latest.
Co-authored-by: Codex <noreply@openai.com>
Prefer creating a ReFS Dev Drive VHD before falling back to the runner-provided D: drive so CI can measure whether the explicit Dev Drive path helps.
Co-authored-by: Codex <noreply@openai.com>
Incorporate the uv Dev Drive setup pattern by remounting newly-created Dev Drive VHDs after filter changes, using the configured temp directory for Bazel repo contents cache, and moving Cargo target output onto the selected fast Windows drive while preserving the default target path on other platforms.
Co-authored-by: Codex <noreply@openai.com>
Configure Windows Rust CI jobs and the shared Bazel CI setup to put temp, repository-cache, and output-root paths on the runner's fast work drive when available. Fall back to C: if no secondary drive or Dev Drive provisioning path is available.
Co-authored-by: Codex <noreply@openai.com>
