CNA-VGAP-023: No browser renderer path is executed automatically: WEBGL2 has no test registrations and no workflow runs a renderer in a browser

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

✓

Evidence basis: source-verified at the pinned commit; tests exist (not executed for this page). Claims on this page were checked by reading the CNA source at commit c1c316b9; unless a sentence says otherwise, nothing here was built or executed. Nothing on this page was executed unless the Evidence section says so.

WEBGL2 has no test registrations, and CI only links a WEBGL2+WEBGPU bundle without running it; no workflow runs any renderer in a browser.

Identifier: CNA-VGAP-023
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: WEBGL2 and WEBGPU renderer identities in Emscripten builds

Expected behaviour

A renderer identity published as supported should have at least one automated execution of its real target environment.

Actual behaviour at TARGET

CMakeLists.txt registers EasyGL tests only when NOT EMSCRIPTEN, so WEBGL2 has none. emscripten-multi-renderer-ci.yml links WEBGL2 and WEBGPU into one bundle and, per its header, does not run it in a browser (runtime behaviour in a page is left to CNA's own recorded runs); no workflow drives a browser.

Source locations

modules/renderers/easygl/examples/CMakeLists.txt — NOT EMSCRIPTEN registration guard
.github/workflows/emscripten-multi-renderer-ci.yml — links a WEBGL2+WEBGPU bundle and does not run it

Evidence

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

Independently reported as CNA-VGAP-045 (folded into this entry by the adversarial audit): No workflow runs a renderer in a browser: WEBGL2 and WEBGPU have no browser harness in CI, and the Emscripten multi-renderer job only links a WEBGL2+WEBGPU bundle.

Focused reproduction

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

Current tests

Build only: one Emscripten bundle linked, never run; any browser runs are manual.

Regression test

A headless-browser CI step per browser identity.

Blast radius

All WebGL 2 and browser WebGPU rendering, context loss and host-owned loop behaviour.

Workaround

No workaround is known.

The same subject is explained at several altitudes. These are the neighbouring pages at each one.

Deep dives: Web builds: renderer evidence
Known issues: Verification gap index