docs: record 1.7.12 lazy notification bell

AGENTS.md

@@ -2255,9 +2255,9 @@ Node 22 + npm 10 · Bun 1.3 · Java 21 · Android SDK at `~/Android/Sdk` · `ngi
   and no longer fetch at startup; Shops/Gear/Tours pass `enabled` too. ③
   `queryPersister`'s allow-list now matches the real keys (`skate-crews`,
   `skate-tour`/`skate-tours`, `shop-directory`, `newsletter-issues`, …), so
-  cold starts rehydrate those datasets. Next targets: the notification bell's
-  5+ source queries on every cold start (split trigger/panel or one summary
-  query), paginate the map's 2000-spot payload, a no-vendor service worker for
+  cold starts rehydrate those datasets. The bell is now code-split/deferred (1.7.12) and its feeds load after first
+  paint. Next targets: fold the bell's feeds into one summary query or open-only
+  fetch, paginate the map's 2000-spot payload, a no-vendor service worker for
   hashed assets/app shell, and the translation model (617 MB M2M100 is the
   biggest latency cost; use a smaller model or native ONNX).
 
@@ -2426,6 +2426,11 @@ Rules:
       query persistence allow-list aligned with real keys (crews, tours, shops,
       newsletter). No analytics/vendor/server shortcut. APK sha256 `a5d99ab9…`,
       versionCode 10711. Web forced live at `c903a51`.
+    - **1.7.12 (2026-10-28):** the notification bell is code-split into
+      `NotificationBellLazy` (idle-mounted or loaded on tap) so its five data
+      sources no longer compete with the map/route queries on first paint. The
+      bell button is a lightweight placeholder until then. APK sha256
+      `34195aa3…`, versionCode 10712. Web forced live at `e75a50c`.
 
 ### Relay archive (dataset backup)
 - **Transfer content between keys (`scripts/transfer-content.mjs`, 2026-10-04):**