HTML5 build
A build produces locally executable browser assets with an unambiguous entry point.
Preparation
Pin dependencies and the SDK version, run tests and perform your bundler's production build. A simple project does not require a bundler: ES modules and resources may ship directly. Check filename case because Linux distinguishes Name.png from name.png.
Artifact checks
Run the built output, not a hot-reload development server. Disable external internet, verify relative paths and remove CDN requests. Do not add a service worker without an explicit cache-versioning design: a stale worker can replace game code after an update.
Readiness boundary
A working index.html in a normal browser does not prove production Runtime Host support. Projector launch, manifest delivery, audio, kiosk, process shutdown and package installation require separate acceptance. This SDK version is not evidence that those checks have already passed.