## Summary
The browser-facing build targets WebGL via index.html. WebGL rendering
introduces frame pacing risks that are absent in headless engine testing.
A validation checklist and automated checks are needed before any
rendering-dependent build is considered safe for accessibility-sensitive users.
## Acceptance Criteria
- [ ] Document maximum acceptable frame delta for game-state transitions
- [ ] Identify all engine events that trigger visual state changes (aura application, Veiled transition, capture, turn change)
- [ ] For each event: confirm no frame spike above threshold occurs in WebGL target
- [ ] Validate that Safe Mode suppresses all non-essential visual events at the render layer
- [ ] Add checklist to docs/ as WEBGL_SAFETY_CHECKLIST.md
- [ ] Checklist is referenced from CONTRIBUTING.md so all rendering contributors see it
## Reference
- docs/ENGINE_ACCESSIBILITY_A11Y_PARADOX.md
- index.html (browser build entry point)
- ARCHITECTURE_OVERVIEW.md — Headless testability