Refresh Google Play closed-test runbook

android/play-store/closed-test.md

@@ -4,6 +4,10 @@ The developer account is a new personal account. Google currently requires at
 least 12 testers to remain opted in to the closed test for 14 continuous days
 before production access can be requested.
 
+This requirement was rechecked against the official Play Console Help article
+on 2026-08-09. The Console remains the source of truth for the account's actual
+eligibility and the date on which production access can be requested.
+
 ## Before inviting testers
 
 1. Complete Play developer identity and contact verification.
@@ -13,7 +17,10 @@ before production access can be requested.
    identities shown for quantum-ready hybrid signing when present. Add every
    applicable Play App Signing SHA-256 to production App Links and
    Google/Firebase configuration, then verify the production association files.
-5. Upload the source-bound production AAB.
+5. Upload the source-bound production AAB. The current prepared candidate is
+   `0.1.2 (3)` with SHA-256
+   `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.
 7. Start with an internal test on the owner’s device, then promote the verified
@@ -26,8 +33,8 @@ boundary before testing authenticated flows:
 ./scripts/verify-play-installed-android.sh \
   /secure/downloads/play-identities.json \
   DEVICE_SERIAL \
-  1 \
-  0.1.0
+  3 \
+  0.1.2
 ```
 
 The verifier is read-only. It requires the Google Play installer, one of the
@@ -43,6 +50,9 @@ look correct.
   14-day interval. If anyone opts out, replace them if needed and use the date
   shown by Play Console rather than assuming the original interval still
   qualifies.
+- Testers may join on different dates, but production access cannot be
+  requested until at least 12 currently opted-in testers have each satisfied
+  the continuous 14-day requirement shown by Play Console.
 - Do not publish tester email addresses in the repository.
 - Give every tester the Play opt-in link and state clearly that they must remain
   opted in for at least 14 continuous days.