Record current Play closed-test readiness

android/play-store/closed-test.md

@@ -27,7 +27,8 @@ eligibility and the date on which production access can be requested.
    `contact@whoneedhelp.com`; phone and website were empty.
 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 2026-08-25 the Internal release is active. The existing **Closed
+   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.
 

android/play-store/internal-release-v4.md

@@ -34,7 +34,8 @@ build, and a new operator record.
 
 ## Publication evidence
 
-A read-only authenticated Play Console inspection on 2026-08-25 showed:
+A read-only authenticated Play Console inspection on 2026-08-25, repeated on
+2026-08-26, showed:
 
 1. **Internal testing** is active;
 2. the latest release is `0.1.3 Reliable notifications` with one version code;

docs/verification.md

@@ -4079,3 +4079,27 @@ promoted.
   one database notification and removed the mode-`0600` local state file. The
   existing Chrome tab remained at `/notifications?section=settings`, so a
   human click on the operating-system surface still is not claimed.
+
+# 2026-08-26 Google Play closed-test readiness recheck
+
+- Read-only inspection of the authenticated Play Console showed Internal
+  testing active with release `0.1.3 Reliable notifications` and version code
+  `4` available to internal testers.
+- The existing Closed testing Alpha track remained inactive with zero of four
+  setup tasks complete. Countries and testers were not selected, the track
+  contained no release, and its review action was locked behind those setup
+  tasks.
+- The Child safety standards declaration remained incomplete. The standards
+  URL and contact selection were blank, both attestations were unchecked, and
+  the Save action was disabled. The public `/child-safety` page returning `200`
+  does not replace the monitored-contact and legal-attestation decisions.
+- The retained AAB checksum still matched
+  `5147404e91aee6ef87014e19db93403fdb18a15e91b749737c494c372ea87371`.
+  The connected physical phone passed the strict Play-delivery verifier again
+  for `org.whoneedhelp.mobile` version `0.1.3 (4)`: Google Play installer,
+  protected Play App Signing identity, verified production App Link, and
+  `MainActivity` resolution all matched. The browser-only Google OAuth callback
+  was not claimed by Android.
+- 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.