Use browser or device controls to replay a fixed sequence: online for preparation, offline for two task attempts, intermittent connectivity, then stable reconnection. Seed fictional data only. Record available content, queued actions, state loss, duplicates, status wording, and the exact moment the interface admits that the network has gone sightseeing.
The acceptance hypothesis is explicit: previously available content remains legible, offline limits are named, safe changes queue once, and reconnection produces one understandable confirmation. Run the same script twice from a clean state and once after interruption to expose accidental success.
This protocol can verify a particular build under declared conditions; it cannot promise every railway, radio, or operating system will behave alike. Publish the build, cache state, network script, expected outcomes, and deviations so another tester can reproduce the tunnel without buying a ticket.
Offline is a place people visit, not an exceptional error.Review platform behavior