Prove a publicly served game matches its release manifest
The practical problem
A green workflow is not evidence that visitors see the correct bytes; caching or a wrong document root can serve old files.
Implementation protocol
Include release ID, expected paths, digest values and commit SHA in a manifest. Verify each public URL externally and test interactive behavior in Chrome.
Worked scenario
Compare the served game's SHA against its release record and confirm a browser test marker appears in the rendered result.
What could go wrong
Checking only repository contents can miss a blocked cPanel transfer.
Acceptance criteria
Maintain per-file results with HTTP status and browser evidence.
Source material and evidence boundaries
For the topic Prove a publicly served game matches its release manifest, use the sources listed below to check relevant methods. Any worked figures illustrate a scenario, not measured MojPlayWin performance. Consult the shared evidence standards before applying the method.