Add BUILD_ID console log + network-first SW for index.html

Tells us at a glance whether the latest deployed JS is actually running --

main.js logs [Aadhat] BUILD <id> on startup and exposes window.__AADHAT_BUILD__

so the user can paste it back to us.

Also fixes the root cause of stale-cache reports: the SW used cache-first

for index.html, so on the first reload after a deploy the user got a stale

index.html that still referenced the old main.js?v=YYYYMMDD URL --

guaranteeing they saw the old code regardless of cache version bumps. SW

now uses network-first for navigation requests; static assets remain

cache-first with background refresh.

Bumps cache-buster query strings (v=20260606b) and SW cache (aadhat-v5)

as well so any current stale cache is invalidated. 123/123 tests still pass.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: hiteshkrmsft

www/index.html

@@ -11,7 +11,7 @@
     <!-- Favicon -->
     <link rel="icon" type="image/svg+xml" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><rect fill='%23667eea' width='100' height='100' rx='20'/><text x='50' y='68' font-size='50' text-anchor='middle' fill='white' font-family='Arial,sans-serif' font-weight='bold'>A</text></svg>">
 
-    <link rel="stylesheet" href="styles.css?v=20260107">
+    <link rel="stylesheet" href="styles.css?v=20260606b">
 
     <!-- Firebase SDK -->
     <script src="https://www.gstatic.com/firebasejs/10.7.1/firebase-app-compat.js"></script>
@@ -42,7 +42,7 @@
     </script>
 
     <!-- ES6 Modular Architecture (loads and injects all templates) -->
-    <script type="module" src="js/main.js?v=20260107"></script>
+    <script type="module" src="js/main.js?v=20260606b"></script>
 
 </body>
 </html>

www/js/main.js

@@ -30,6 +30,19 @@ import { AdminManager } from './modules/admin.js';
 import { TemplateLoader } from './utils/template-loader.js';
 import { Helpers } from './utils/helpers.js';
 
+// Build stamp — bumped on every deploy that ships new JS so you can verify
+// in the browser console whether the latest code is actually running. If
+// your console shows an OLDER BUILD_ID after a deploy + reload, the service
+// worker / browser is still serving stale assets (reload twice, or hard
+// refresh / unregister the service worker).
+const BUILD_ID = '20260606-negstock-rate-fix';
+console.log(
+    `%c[Aadhat] BUILD ${BUILD_ID}`,
+    'color:#fff;background:#0a7;font-weight:bold;padding:2px 6px;border-radius:3px'
+);
+// Expose on window so the user can copy/paste it back to us when debugging.
+window.__AADHAT_BUILD__ = BUILD_ID;
+
 // Load and inject HTML templates from separate .html files
 async function injectTemplates() {
     const templates = await TemplateLoader.loadAllTemplates();

www/service-worker.js

@@ -3,7 +3,7 @@
  * Provides offline functionality and caching
  */
 
-const CACHE_NAME = 'aadhat-v4';
+const CACHE_NAME = 'aadhat-v5';
 const STATIC_ASSETS = [
     '/',
     '/index.html',
@@ -114,7 +114,14 @@ self.addEventListener('activate', (event) => {
 
 /**
  * Fetch event - serve from cache, fallback to network
- * Network-first for API calls, cache-first for static assets
+ * Strategy:
+ *   - index.html (the navigation document) is fetched NETWORK-FIRST so the
+ *     latest cache-buster query strings in <script> / <link> tags reach the
+ *     browser on first reload after a deploy. Without this, the user has to
+ *     reload twice to see new code (the SW serves a stale index.html on the
+ *     first reload, which references the stale main.js URL).
+ *   - All other static assets are cache-first with background refresh.
+ *   - Firebase/external API calls bypass the SW entirely.
  */
 self.addEventListener('fetch', (event) => {
     const url = new URL(event.request.url);
@@ -130,6 +137,26 @@ self.addEventListener('fetch', (event) => {
         url.hostname.includes('gstatic')) {
         return;
     }
+
+    // Treat navigation requests and explicit index.html requests as
+    // network-first so post-deploy cache-busters take effect immediately.
+    const isNavigation = event.request.mode === 'navigate'
+        || url.pathname === '/'
+        || url.pathname === '/index.html';
+    if (isNavigation) {
+        event.respondWith(
+            fetch(event.request)
+                .then((response) => {
+                    if (response && response.ok) {
+                        const clone = response.clone();
+                        caches.open(CACHE_NAME).then((cache) => cache.put(event.request, clone)).catch(() => {});
+                    }
+                    return response;
+                })
+                .catch(() => caches.match(event.request).then((cached) => cached || caches.match('/index.html')))
+        );
+        return;
+    }
 
     // For static assets - cache first, then network
     event.respondWith(