Record current Google Play launch gates

android/play-store/closed-test.md

@@ -28,9 +28,9 @@ eligibility and the date on which production access can be requested.
 7. Finish the internal test on the owner’s device, complete the foreground-
    service declaration, then promote the verified build to the closed track.
    As of the read-only recheck on 2026-08-26 the Internal release is active.
-   The existing **Closed
-   testing - Alpha** track is inactive with zero of four setup tasks complete:
-   countries and testers are not selected, and the track has no release.
+   The 2026-08-28 Dashboard showed zero of five tasks complete: select countries
+   and regions, select testers, create a release, preview and confirm it, and
+   send it to Google for review.
 
 After installing from the internal-track opt-in link, verify the delivery
 boundary before testing authenticated flows:

android/play-store/release-checklist.md

@@ -220,10 +220,10 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
 - [ ] Tester feedback and fixes documented.
 - [ ] Production-access questionnaire completed from actual evidence.
 
-On 2026-08-25 the existing **Closed testing - Alpha** track was inactive with
-zero of four setup tasks complete. Countries and testers were not selected, and
-the track had no release. The current official requirement for this personal
-developer account was rechecked again on 2026-08-26 as at least 12 testers
+On 2026-08-28 the Dashboard showed zero of five Closed testing tasks complete:
+select countries and regions, select testers, create a release, preview and
+confirm it, and send it to Google for review. The current official requirement
+for this personal developer account was rechecked as at least 12 testers
 continuously opted in for at least 14 days before applying for Production
 access. No Closed or Production release was created during this inspection.
 

android/play-store/store-presence-runbook.md

@@ -68,6 +68,21 @@ frozen test environment, or public Git remote was changed.
 This recheck was read-only. No Console field, release, track, deployment,
 frozen test environment, or public Git remote was changed.
 
+## Read-only recheck on 2026-08-28
+
+- Internal testing remained active with release `0.1.3 Reliable
+  notifications`. Production remained inactive and the app remained a draft.
+- The Dashboard showed zero of five Closed testing tasks complete: select
+  countries and regions, select testers, create a release, preview and confirm
+  it, and send it to Google for review.
+- The current opted-in tester count was zero. Production access required at
+  least 12 opted-in testers for at least 14 days.
+- The Child safety declaration was empty. Its public standards URL and contact
+  were not selected, both attestations were unchecked, and Save was disabled.
+
+This recheck was read-only. No Console field, release, track, billing setting,
+Firebase setting, deployment, or public Git remote changed.
+
 These are direct observations from the authenticated Play Console session on
 that date. Recheck the Console before applying because its fields and policy
 requirements can change.

docs/verification.md

@@ -4103,3 +4103,37 @@ promoted.
 - No Play Console value was saved. The phone package was not installed,
   updated, cleared, or reconfigured. Production, the frozen hackathon test,
   shared Caddy, and the public Git remote were not changed.
+
+# 2026-08-28 Google Play launch-gate recheck
+
+- Read-only inspection showed Internal testing active with release
+  `0.1.3 Reliable notifications`. Production remained inactive and the app
+  remained a draft. Google still displayed the temporary internal-test name
+  `org.whoneedhelp.mobile (unreviewed)`.
+- The current Dashboard listed five incomplete Closed testing tasks: select
+  countries and regions, select testers, create a release, preview and confirm
+  the release, and send the release to Google for review. Production access
+  also required at least 12 opted-in testers for at least 14 days. The current
+  opted-in count was zero.
+- The Child safety standards declaration remained empty. The standards URL and
+  contact were not selected, both attestations were unchecked, and Save was
+  disabled. `https://whoneedhelp.com/child-safety` returned HTTP 200, while the
+  old hackathon test deployment returned 404 for the same path. The production
+  page satisfies the technical URL requirement, but it does not supply the
+  required monitored contact or approve the legal attestations.
+- No Play Console value, release, track, tester list, billing setting, Firebase
+  setting, deployment, or public Git reference changed during this check.
+
+# 2026-08-28 backup and external-monitor recheck
+
+- The production backup timer was loaded, enabled, and active. Its 28 August
+  run exited successfully after an encrypted off-site backup and isolated
+  restore drill. The next run was scheduled for 29 August at 00:00 EEST.
+- The independent host stored the resulting heartbeat with mode `0600`,
+  `restore_verified: true`, and snapshot
+  `800d5efbf902175a622d4b4eebd0432e81dbd39a25aa76b5fb3c33e6673950c2`.
+  The heartbeat was 4828 seconds old when inspected, below the selected
+  129600-second stale-backup threshold.
+- The external monitor timer was loaded, enabled, and active. Its latest check
+  returned `up` for public readiness, authenticated aggregate metrics, and
+  backup freshness. User lingering remained enabled on the monitor host.