Order Play permission and listing setup

android/play-store/location-and-fgs-declaration.md

@@ -230,9 +230,14 @@ were removed. Production readiness remained healthy. This file is final local
 evidence, but it is not considered submitted until an unlisted hosted URL is
 entered and saved in Play Console.
 
-The remaining Play policy references were last checked on 2026-08-03; refresh
+The remaining Play policy references were rechecked on 2026-08-10. The current
-them again immediately before submitting the declaration because the Help
+Play Help still requires a video demonstration for the declared permission and
-Center pages can change independently of the Android platform documentation:
+accepts a YouTube link (preferred) or a cloud-hosted common video file. It also
+states that an unresolved declaration for an active bundle can prevent
+publishing other changes, including Store Presence. Refresh the pages again
+immediately before submitting because Play Help can change independently of
+the Android platform documentation:
 
 - https://support.google.com/googleplay/android-developer/answer/9799150
 - https://support.google.com/googleplay/android-developer/answer/16909972
+- https://support.google.com/googleplay/android-developer/answer/9214102

android/play-store/release-checklist.md

@@ -78,6 +78,11 @@
 
 ## Store presence
 
+Complete the mandatory foreground-service declaration under **App content**
+before attempting to publish Store Presence changes. The current Play Help
+states that an unresolved permissions declaration for an active bundle can
+block publishing changes, including Store Listing, Pricing, and Distribution.
+
 - [x] 512×512 Play icon prepared.
 - [x] 1024×500 24-bit PNG feature graphic prepared.
 - [x] Four current 1080×1920 physical-phone screenshots captured and reviewed.

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

@@ -74,12 +74,18 @@ queue, or automated test.
 
 1. Recheck the current Console fields and policy warnings read-only.
 2. Verify the production policy/support URLs and monitored email.
-3. Save category, tags, contact email, and website.
+3. Host the verified foreground-location demonstration as an unlisted video,
-4. Create the default English (United States) listing with prepared text,
+   then complete and save the mandatory foreground-service declaration. Reopen
+   **App content** and verify that the permission alert is cleared before
+   changing Store Presence. Google documents that an unresolved permissions
+   declaration for an active bundle can block publishing changes, including
+   store-listing changes.
+4. Save category, tags, contact email, and website.
+5. Create the default English (United States) listing with prepared text,
    images, and alt text.
-5. Add Ukrainian and Russian localizations from their prepared files.
+6. Add Ukrainian and Russian localizations from their prepared files.
-6. Reopen the Dashboard and verify both setup tasks are marked complete.
+7. Reopen the Dashboard and verify both setup tasks are marked complete.
-7. Recheck App content; do not start Closed or Production rollout as part of
+8. Recheck App content; do not start Closed or Production rollout as part of
    store-presence setup.
 
 Official references rechecked on 2026-08-10:
@@ -87,3 +93,4 @@ Official references rechecked on 2026-08-10:
 - https://support.google.com/googleplay/android-developer/answer/9859454
 - https://support.google.com/googleplay/android-developer/answer/14747720
 - https://support.google.com/googleplay/android-developer/answer/9878809
+- https://support.google.com/googleplay/android-developer/answer/9214102