Record remaining Play setup gates

android/play-store/closed-test.md

@@ -22,11 +22,15 @@ eligibility and the date on which production access can be requested.
    `5f1b63d02467ce63af795d16459a75693e415426478e0788b83f0f6d35dff922`;
    its exact operator record is `internal-release-v3.md`.
 6. Complete the store listing, App content, privacy, Data Safety, content rating,
-   ads, target-audience, and access declarations.
+   ads, target-audience, and access declarations. Read-only Play Console
+   inspection on 2026-08-10 showed app setup at 9 of 11 tasks: the two
+   incomplete tasks were **Select an app category and provide contact details**
+   and **Set up your store listing**.
 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-10 the Internal release is active, but Closed testing has not
-   been started.
+   been started. The Dashboard showed Closed testing locked until app setup is
+   finished and `0 testers currently opted-in`.
 
 After installing from the internal-track opt-in link, verify the delivery
 boundary before testing authenticated flows:

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

@@ -73,6 +73,12 @@ under **Need attention**: the Foreground service permissions declaration. Its
 Location form had no saved task selection and the Save control was disabled.
 No incomplete declaration was saved or submitted during this inspection.
 
+The Dashboard separately showed overall app setup at 9 of 11 tasks. The two
+incomplete tasks were **Select an app category and provide contact details** and
+**Set up your store listing**. Closed testing remained locked until those tasks
+are complete and reported `0 testers currently opted-in`. No values were saved
+and no Closed or Production release was created during this inspection.
+
 The authorised physical phone then passed the strict installed-build verifier:
 Google Play installer, Play App Signing identity, exact `0.1.2 (3)` version,
 verified production App Link, and `MainActivity` resolution.

android/play-store/release-checklist.md

@@ -85,6 +85,12 @@
 - [x] Alt-text copy (≤140 characters) prepared in `store-assets/README.md`.
 - [ ] Enter the prepared alt text when the assets are uploaded in Play Console.
 - [ ] Choose category/tags in the current Console options.
+- [ ] Complete **Select an app category and provide contact details** in Play
+      Console. Read-only Dashboard inspection on 2026-08-10 showed this task
+      incomplete; no values were selected or saved during that inspection.
+- [ ] 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.
 
 ## App content
 
@@ -152,6 +158,10 @@
 - [ ] 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.
+
 ## Publishing
 
 - [ ] Managed publishing enabled if desired.

docs/google-play-release-candidate-2026-08-09-v3.md

@@ -88,5 +88,10 @@ The remaining gates are:
 1. create a concise final foreground-location declaration video from the
    Play-delivered candidate;
 2. complete and verify the Play Console foreground-service/location form;
-3. keep Closed and Production tracks untouched until their separate gates are
+3. complete the Play Console category/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;
+4. recruit the required tester cohort only after Closed testing is unlocked;
+   the Dashboard currently reports `0 testers currently opted-in`;
+5. keep Closed and Production tracks untouched until their separate gates are
    complete.

docs/verification.md

@@ -2726,3 +2726,8 @@ promoted.
   stopped state were captured. A concise complete take of 30 seconds or less,
   the Play foreground-service declaration, and Closed testing remain open
   gates. No Production Play rollout has been started.
+- Read-only Play Console Dashboard inspection showed app setup at 9 of 11
+  tasks. The remaining setup tasks were category/contact details and the Store
+  listing. Closed testing was locked pending those tasks and showed zero
+  opted-in testers. No Console values were saved and neither Closed nor
+  Production received a release during this inspection.