The game worked, but the iframe was clipped
Claim: A playable embedded game should remain visible and inside its frame on phone-sized screens after interaction.
Bug: Hot Path completed its two-player interaction in every viewport, but the embedded game surface was visibly clipped on phone and tablet.
Why normal checks missed it: The saved game used overflow hidden, so document scroll width stayed clean. A simple page overflow check would have passed.
Why this sells Riddle Proof: This is the kind of issue a product team can miss when automated checks only ask “did the route load?” Riddle Proof turns the browser screenshot into a reviewable receipt.
Reusable profile seed: For embedded apps: run post-interaction screenshots, iframe bounds checks, and visible-canvas assertions across phone/tablet/desktop.
What the browser run checked
- Opened the player in a real browser at responsive viewports.
- Drove the two-player interaction far enough to prove the game was active.
- Captured screenshots after interaction instead of only at first load.
- Compared visible element bounds against the viewport and iframe frame.
Proof lesson
Element bounds and screenshots catch user-visible clipping that scalar scroll-width checks miss.
The human-readable artifact: it shows the game active, but clipped in the viewport.
Records the browser run timestamp, duration, worker, and whether the proof script itself errored.
Preserves browser console output so visual findings can be read alongside runtime errors or warnings.
