A daily puzzle should survive a train tunnel. Check what still works before you rely on it.
Networks fail in the places where daily puzzles are played: trains, basements, old buildings, phone plans with narrow data caps. A ten-minute game that requires a perfect connection will lose those sessions, and those are exactly the sessions the habit needs.
The good news is that a small browser game can be built so the first load is enough. Once the puzzle payload and the code are cached, the round is decided locally, and a tunnel does not change the answer. The bad news is that many web games still phone home on every guess or load assets late, and those fail at the first tunnel.
It is worth checking how your game behaves before you depend on it. Load the daily, put the phone in airplane mode, and play the whole round. If it works, the game is safe to use on a commute. If the board freezes on the first guess, the game needs a network for something it should compute locally.
The second useful check is the cold start. Clear the cache, put the phone in airplane mode, and open the game. A well-built static puzzle fails here, and that is acceptable; the fix is to load the game once while on a good network, before the tunnel, not to expect the tunnel to be magic.
The tunnel check is worth repeating after any update to a game you play daily, because caching behaviour is easy to break accidentally.
These checks are also a fair way to judge a small game. A daily puzzle that works offline after one load is a different product from one that needs a signal every time, and the difference is invisible until the day it matters.
The habit to build is boring: load the game before you leave, then play wherever you end up. When you are back online, another practice round is available and nothing was lost by waiting.