[Bug]: native Windows lane never runs the control-plane suites the project hardened and fixed for Windows, so Windows-only regressions ship qualified #6638

What happens

LoopX ships native Windows support, and the native Windows qualification lane (windows-powershell in .github/workflows/python-tests.yml) is a required merge-gate job. That lane runs a curated list of TypeScript suites (6 of the 266 files in tests/control_plane_ts/). Every control-plane suite that carries behavior written or fixed specifically for native Windows is currently outside that list, so its Windows behavior is never exercised in CI:

The lane also installs no repository-root dependencies, so any suite that imports a package (for example the PostgreSQL provider's pg) cannot run there at all.

Impact

Windows-only runtime regressions keep shipping with green qualification:

• [Bug]: native Windows: runtime.checkpoint_artifacts capture and materialize always fail because the copied-file durability flush uses a read-only handle #6562: runtime.checkpoint_artifacts capture and materialize failed on every Windows host; only a user-side run of tests/control_plane_ts/checkpoint_artifacts.test.ts on Windows exposed it. The fix (fix(checkpoint): flush captured members through update handles on Windows #6566) is merged, and its own review named this follow-up: the checkpoint suite is not part of the windows-powershell lane, which is why this Windows-only regression escaped CI.
• fix(backup): flush state backup archives through writable handles on Windows #6258: loopx backup-state --execute failed on Windows because both durability flushes used read-only handles — the same defect class as [Bug]: native Windows: runtime.checkpoint_artifacts capture and materialize always fail because the copied-file durability flush uses a read-only handle #6562, in a different owner, with no Windows qualification either.
• [Bug]: native Windows: remaining 32 host-dependent control-plane TypeScript test failures after #6207 #6351 / test: guard remaining host-dependent control-plane assertions on native Windows #6356: ten control-plane suites needed native Windows hardening, which means their assertions differ by host; after hardening, CI still never runs them on Windows.

Root cause: the lane list is hand-curated and no contract keeps it aligned with the suites that encode native Windows behavior, so each Windows-only fix can land without adding the coverage that would catch the next one. #6562 is the demonstrated cost of that drift.

Expected

The windows-powershell lane qualifies every control-plane suite that carries native Windows behavior, and a contract test keeps it that way so the coverage cannot silently drop out again.

Environment

• Repository revision: dda6f7ef7 (main), verified on a native Windows 11 host with node v22.22.3 (the version the lane pins for its SQLite steps).
• The 11 listed suites run green on that host: 271 tests, 246 pass, 0 fail, 25 skipped (20 PostgreSQL-provider, 3 symlink-privilege, 2 POSIX-only), 48.1s (node --no-warnings --experimental-sqlite --experimental-strip-types --test <suites>).

_{Drafted with AI assistance at my request, under my direction and review.}