Summary

The checks-windows CI job is consistently failing on PRs and on main due to a path-handling test failure in path-safety. The test expects Unix-style paths (~/file.txt) but runs on a Windows runner where paths use backslashes.

Reproduction

This failure is visible on multiple recent PRs and on main itself:

• docs: fix grammar "a OpenClaw" → "an OpenClaw" across 8 files #23753, docs: replace outdated legacy names and paths #23757, docs: fix broken URL, inconsistent casing, and hyphenation #23770 — all docs-only PRs, checks-windows fails
• Recent main branch CI runs also show repeated failures

Error

1 failed | 705 passed | 3 skipped (709)
1 failed | 5764 passed | 20 skipped (5785)

The single failing test is in the path-safety module, where expect(result).toBe(${fakeHome}/file.txt) fails because Windows uses backslash paths.

Expected behavior

Windows CI tests should pass, or the path-safety test should account for platform-specific path separators.