diff --git a/apps/web/public/manifest.webmanifest b/apps/web/public/manifest.webmanifest
index eb6bb37..7bbf628 100644
--- a/apps/web/public/manifest.webmanifest
+++ b/apps/web/public/manifest.webmanifest
@@ -6,6 +6,9 @@
   "scope": "/",
   "display": "standalone",
   "orientation": "portrait-primary",
+  "launch_handler": {
+    "client_mode": ["navigate-existing", "auto"]
+  },
   "background_color": "#fbfaf8",
   "theme_color": "#b4552d",
   "categories": ["news", "productivity", "utilities"],
diff --git a/apps/web/public/sw.js b/apps/web/public/sw.js
index cafa4b9..1059567 100644
--- a/apps/web/public/sw.js
+++ b/apps/web/public/sw.js
@@ -29,7 +29,15 @@
 // now, so the shell is one URL shorter. Without the bump an install that
 // precached the pair under v5 would hold the retired file forever, since
 // nothing requests it any more and only the version sweep can evict it.
-const VERSION = 'v6';
+//
+// v7 is a manifest bump: the manifest gained a launch_handler and it is one of
+// the shell URLs, so the copy taken at install is now out of date. Nothing
+// serves that copy today — the fetch handler below lets .webmanifest fall
+// through to the network — but the shell is meant to hold what the site
+// currently ships, and the version sweep is the only thing that can replace
+// it. The browser reads launch_handler over the network either way, so this
+// bump is hygiene rather than the fix.
+const VERSION = 'v7';
 const SHELL = `shell-${VERSION}`;
 const ASSETS = `assets-${VERSION}`;