USR369 reported not seeing the new tab, despite it being verified byte-exact on the live server via direct fetch. Root cause: service-worker.js used a cache-first strategy for index.html with a static CACHE_NAME ('doughcalc-v1') that never changed across any of today's deploys. Browsers only re-check a service worker file for updates when ITS OWN bytes change -- since I only ever edited index.html (never service-worker.js itself), the browser had no signal to reinstall the service worker or refresh its cache, so the installed PWA kept serving whatever index.html was cached at install time indefinitely, regardless of how many real server-side deploys happened. This likely means some or all of today's earlier DoughCalc fixes may not have been visible either if USR369 was testing via the installed home-screen app rather than a fresh browser tab. FIX: switched the fetch handler from cache-first to network-first (always try the live network fetch first, update the cache with the fresh copy, only fall back to the cached copy if the fetch fails -- i.e. genuinely offline, which is what this caching exists for) and bumped CACHE_NAME to v2 to force an immediate refresh of the currently-stuck stale cache. This is a permanent fix, not a one-time patch -- future index.html edits will now show up on next load without needing another service-worker version bump.