Repository navigation
ci: run shadercheck in CI #360
Description
What
npm run shadercheck compiles every screensaver's shaders in headless Chrome and checks the pixels. It is the only gate that catches:
- a shader the driver rejects (the registry's fallback to the DVD logo hides that from everything else);
- a shader that compiles but renders wrong (fix: repair washed-out raymarch fractal #140);
- a structure regression (test: pixel-sanity checks cannot see a double-encode or a flat sim #156).
Neither ci.yml nor release.yml runs it. A shader regression merges and releases unless someone runs it locally.
Context
It forces SwiftShader on purpose, so it needs no GPU. That makes it possible on a hosted runner (ubuntu-latest with Chrome, or macos-latest). The CLAUDE.md note on structure baselines applies: they are resolution- and rasteriser-dependent, so CI must render at the same size the baselines were taken at.
Fix
A CI job that runs npm run shadercheck on PRs touching src/renderer/screensavers/**, scripts/shader-check.mjs or the baselines.
Found while reconstructing the Electron app's decisions as ADRs for the egui port (#346, docs/adr/open-questions.md). Line numbers are from main at 787375b (v3.4.1).
Activity