Refresh Google Play launch gates

android/play-store/release-checklist.md

@@ -92,7 +92,10 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
       before Console entry. On 2026-08-10 the repository validator passed all
       three localized text limits, the 512×512 icon, the 1024×500 RGB feature
       graphic, and all four 1080×1920 RGB phone screenshots.
-- [ ] Enter the prepared alt text when the assets are uploaded in Play Console.
+- [ ] Enter the prepared alt text if the current asset editor exposes that
+      field. The read-only Dashboard summary does not expose saved per-asset
+      alt text, so this detail remains unknown even though the overall Store
+      listing task is complete.
 - [x] Choose category in the current Console options. **Social** was saved;
       tags were deliberately left empty rather than adding an inaccurate tag.
 - [ ] Complete **Select an app category and provide contact details** in Play
@@ -103,9 +106,9 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
       address, so inbound delivery has not been demonstrated. Configure and
       test that mailbox/forwarder, or deliberately choose another monitored
       public support address, before saving the field.
-- [ ] Complete **Set up your store listing** in Play Console using the prepared
-      localized copy and assets. The same Dashboard inspection showed overall
-      app setup at 9 of 11 tasks.
+- [x] Complete **Set up your store listing** in Play Console using the prepared
+      copy and assets. A read-only Dashboard inspection on 2026-08-14 showed
+      overall app setup at 10 of 11 tasks and marked this task complete.
 - [ ] If the truthful category remains **Social**, publish and verify the
       `/child-safety` standards, select a monitored child-safety point of
       contact, verify that contact can access the urgent queue, and complete
@@ -197,9 +200,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-10 Play Console showed Closed testing locked until the two remaining
-app-setup tasks are complete and reported `0 testers currently opted-in`. No
-Closed or Production release was created during this inspection.
+On 2026-08-14 Play Console showed Closed testing locked until the one remaining
+app-setup task, public contact details, is complete and reported `0 testers
+currently opted-in`. No Closed or Production release was created during this
+inspection.
 
 ## Publishing
 

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

@@ -22,6 +22,20 @@ does not authorize saving fields in Play Console or publishing a release.
   before any later release; this runbook does not treat a saved form as Google
   approval.
 
+## Read-only recheck on 2026-08-14
+
+- The Dashboard now reports **10 of 11 complete**.
+- **Set up your store listing** is marked complete.
+- **Select an app category and provide contact details** is the only remaining
+  setup task. The category remains **Social**, while public email, phone and
+  website are still empty.
+- Closed testing remains locked and reports `0 testers currently opted-in`.
+- The foreground-service form still contains **User-initiated location
+  sharing**, the final unlisted video URL, and the saved-change confirmation.
+
+This was a read-only observation. No Console value, track, release, production
+deployment, frozen test deployment, or public Git remote was 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/google-play-release-candidate-2026-08-09-v3.md

@@ -92,13 +92,13 @@ authenticated Play Console foreground-service form was saved with
 **User-initiated location sharing** and this URL. This does not claim Google
 approval.
 
-The remaining gates are:
+The remaining gates, rechecked read-only on 2026-08-14, are:
 
 1. recheck the saved foreground-service declaration before submitting a new
    bundle or release and respond to any Play policy feedback;
-2. complete the Play Console public contact task and Store listing; read-only
-   Dashboard inspection on 2026-08-10 showed app setup at 9 of 11 tasks and
-   Closed testing locked;
+2. complete the Play Console public contact task; the Store listing is now
+   marked complete, the Dashboard reports 10 of 11 tasks complete, and Closed
+   testing remains locked;
 3. recruit the required tester cohort only after Closed testing is unlocked;
    the Dashboard currently reports `0 testers currently opted-in`;
 4. keep Closed and Production tracks untouched until their separate gates are