This file is a fragment: tools/harness.sh resume appends everything from the marker below to index.html, serves the folder over http (IndexedDB does not work from file:// in headless Chrome), drives it in real time over the DevTools protocol (tools/harness-cdp.py) and runs it WITHOUT autoplay allowed. It seeds the library with one station and one rendered track and resumes the station with no user gesture, the way an installed app comes back to a station link. Expected: the track is loaded but autoplay is refused, so the player waits with the cover saying TAP TO PLAY, and the next track cooks behind it. The other half — the tap starting it — needs a real user activation, which headless Chrome cannot fake; it is documented in ARCHITECTURE.md, not asserted here.