CNA-VGAP-026: The Windows renderer families have no automatic native Windows execution: DIRECTX9 has no CI job and the DIRECTX11 lane is manual

CNA snapshot c1c316b9  ·  Known Issues › Verification gaps  ·  source links pinned to c1c316b9

The Direct3D Windows workflow (DIRECTX11) runs only on manual dispatch, no workflow selects DIRECTX9, the SDL3-on-Windows platform job is manual too, and DXGI device removal is only simulated.

Identifier

CNA-VGAP-026

Category

Verification gap

Subsystem

Testing & evidence

Status

Open

Verified against

CNA c1c316b9 (c1c316b9c7a846ce8002809c151fcd1af14942c9)

Evidence basis

Source-verified: read at TARGET, not executed

Tests touching this area

Yes: see Current tests

Affected contract

DIRECTX9 and DIRECTX11 renderer identities on native Windows

Expected behaviour

Renderers whose home platform is Windows need at least one automatic native run.

Actual behaviour at TARGET

d3d-windows-ci.yml (matrix DIRECTX11) triggers only on workflow_dispatch; no workflow selects DIRECTX9. platform-ci.yml's sdl3-windows job (SDL3 on native MSVC: the platform module's suite and the HWND check) also runs only on manual dispatch. Device removal on the DXGI renderer is exercised only through debug simulation hooks. The Wine/DXVK cross-build lanes are local evidence, not native Windows. CNA records one manual dispatch of each workflow on GitHub's windows-latest runners (plan_platform.md, PLAT-142: the DIRECTX11 job passed 300 of 300 ctest entries, its hardware smoke skipped for want of a GPU); that is a recorded run, not continuous integration.

Source locations

• .github/workflows/d3d-windows-ci.yml — on: workflow_dispatch; renderer matrix DIRECTX11
• .github/workflows/platform-ci.yml — sdl3-windows job: workflow_dispatch only
• plans/plan_platform.md — PLAT-142: the recorded manual windows-latest runs

Evidence

Checked by reading the named sources at c1c316b9; nothing was built or executed for this entry.

Independently reported as CNA-VGAP-043 (folded into this entry by the adversarial audit): Every engine-level Windows workflow is manual: neither the Direct3D 11 lane nor the SDL3-on-Windows platform job has a push or schedule trigger.

Focused reproduction

No focused reproduction is known. Nothing has been invented here; the evidence above is what exists.

Current tests

Cross-built parity fixtures run under Wine locally; the manual workflows exist but have no schedule or push trigger.

Regression test

Push or scheduled triggers for the Windows lane and a DIRECTX9 job.

Blast radius

All Windows-native rendering, presentation (including PresentInterval pacing and tearing), DPI and device-loss behaviour.

Workaround

No workaround is known.