diff --git a/docs/public-launch-checklist.md b/docs/public-launch-checklist.md
index 0af18f3..4c64975 100644
--- a/docs/public-launch-checklist.md
+++ b/docs/public-launch-checklist.md
@@ -210,7 +210,10 @@ as forward-only rather than receiving an invented database rollback.
       reopened the same link, and observed the invalid/expired notice together
       with the signed-in account email in the replacement-link form.
 - [x] The Web Push provider accepts a production notification for a real active
-      browser subscription without disabling the device.
+      browser subscription without disabling the device. On 2026-08-26 the
+      workstation subscription was explicitly renewed from the production
+      delivery-settings page, and a guarded browser-only smoke completed on its
+      first attempt with exact job and notification cleanup.
 - [ ] A person has observed the resulting operating-system browser notification
       and its navigation target on the subscribed workstation.
 - [x] The production Android build signs in, opens verified App Links, receives
diff --git a/docs/verification.md b/docs/verification.md
index c2c827c..e1420ad 100644
--- a/docs/verification.md
+++ b/docs/verification.md
@@ -3781,6 +3781,23 @@ promoted.
   `0.1.3 (4)` installed by `com.android.vending`. No package, permission, Play
   track, production service, frozen hackathon test deployment, shared Caddy
   configuration, or public Git remote was changed by this recheck.
+- The previously recorded browser notification subscription was no longer
+  active. A first guarded production smoke stopped before creating a
+  notification or job because no active browser device existed; its local
+  state and remote temporary script were then removed after exact inspection
+  confirmed that no run-scoped manifest or database records existed.
+- The existing authenticated production Chrome session granted notification
+  permission only to `https://whoneedhelp.com` and used the product's visible
+  device-enablement action. Browser inspection then reported
+  `permission=granted` and a real service-worker subscription, while the
+  delivery-settings page listed a new `Linux x86_64` browser device and
+  retained the independent Android FCM device.
+- A second guarded smoke created one browser-only notification and Oban job for
+  that renewed subscription. Provider delivery completed on attempt one, the
+  device remained active, no email or Android FCM delivery was enqueued, and
+  exact cleanup deleted one job and one notification plus the run-scoped
+  manifest and temporary script. Visible operating-system presentation and
+  click navigation remain a separate human-observation gate.
 
 # 2026-08-25 anonymous production support verification and cleanup