E2E scenario diagnose-fix-path-prepends-with-apostrophe-intact fails on Windows Strix Halo CI lane (pre-existing since #691) #700

Current behavior
The Windows Strix Halo self-hosted E2E lane (E2E tests (Strix Halo, Windows)) fails the scenario diagnose-fix-path-prepends-with-apostrophe-intact (tests/e2e-cucumber/features/diagnose.feature, @requires-os:windows). The cucumber reconciliation step reports it as an unexpected regression:

Reconciliation: 3 xfail (failed as expected), 0 XPASS (0 flaky, 0 stale), 1 unexpected failure(s).
FAIL: 'diagnose-fix-path-prepends-with-apostrophe-intact' was expected to pass on this host but FAILED — a regression.

Expected behavior
Fixing a missing PATH entry via rocm fix (the fix-6-path recipe on Windows, run_path_export_windows in crates/rocm-core/src/fix.rs) should prepend the HIP SDK bin dir to the real Windows User PATH while leaving an apostrophe already present on that PATH intact, per the scenario's own assertion.

Steps to reproduce
Not reproducible outside the self-hosted Strix Halo Windows runner (needs a real Windows host with the fixture's User PATH state). Observed failing on two separate PRs' CI runs for the same job:

• fix(rocm-core): stop fix-6-path from wiping Windows User PATH on a failed read (ROCMAI-449) #691 (the PR that introduced this scenario) — its own E2E tests (Strix Halo, Windows) check failed with the identical message before merge: https://github.com/ROCm/rocm-cli/actions/runs/38712635607/job/116847390742
• ROCMAI-151: extract config/automation/service_record/binary_paths from rocm-core lib.rs #666, which does not touch fix.rs/diagnose.rs/e2e-cucumber at all — same failure on the same job: https://github.com/ROCm/rocm-cli/actions/runs/38727805978/job/116737460717

Possible solution
Not investigated beyond confirming the regression predates and is independent of #666.

Your environment

• rocm-cli channel: n/a (CI only)
• Platform: Windows (self-hosted Strix Halo runner)

Relevant log output

Reconciliation: 3 xfail (failed as expected), 0 XPASS (0 flaky, 0 stale), 1 unexpected failure(s).
FAIL: 'diagnose-fix-path-prepends-with-apostrophe-intact' was expected to pass on this host but FAILED — a regression.

Additional context
Surfaced while reviewing #666 (ROCMAI-151). The scenario and the fix-6-path code it exercises are untouched by that PR, so this has been failing on main since #691 merged with the check already red — no tracking issue existed for it before this one.