The windows-2022 doc-tests matrix entry in test.yml is commented out with the note "30+ doc-test snippets COMPILE_FAIL on the Windows runner with perry exit 1 (mix of platform-banner gaps and #463-unimplemented node:* surface)... macOS doc-tests still gate the release." Those 30+ failures are real doc/feature drift on Windows that is currently invisible — every documented snippet that fails to compile on Windows is either a missing platform banner in the docs or a genuine Windows gap. Found in the 2026-07-18 Windows audit (main @ 58e555e).
Evidence
Suggested fix
Triage the ~30 failures into (a) snippets that need // targets: platform banners and (b) genuine Windows gaps (file those individually), then re-enable the job so Windows doc drift gates like macOS does.
The windows-2022 doc-tests matrix entry in
test.ymlis commented out with the note "30+ doc-test snippets COMPILE_FAIL on the Windows runner with perry exit 1 (mix of platform-banner gaps and #463-unimplemented node:* surface)... macOS doc-tests still gate the release." Those 30+ failures are real doc/feature drift on Windows that is currently invisible — every documented snippet that fails to compile on Windows is either a missing platform banner in the docs or a genuine Windows gap. Found in the 2026-07-18 Windows audit (main @ 58e555e).Evidence
.github/workflows/test.yml:1811-1824— commented-outwindows-2022/perry-ui-windowsdoc-tests matrix entry with the 30+-COMPILE_FAIL note.whoamicrate'sGetUserNameExWlink fails on every doc-test (missingsecur32import lib) #220 (earlier Windows doc-test link failure, fixed).Suggested fix
Triage the ~30 failures into (a) snippets that need
// targets:platform banners and (b) genuine Windows gaps (file those individually), then re-enable the job so Windows doc drift gates like macOS does.