Document final Play foreground service evidence

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

@@ -95,7 +95,11 @@ and frozen-test readiness endpoints returned `ready`.
 
 The long evidence take is not the submission video: Android's recorder reached
 its time limit before the Stop action was captured even though Stop and server
-cleanup were verified immediately afterward. Record a concise, complete take
+cleanup were verified immediately afterward. A separate 21.379802-second take
-from this same Play-delivered version before entering a video URL in Play
+from this same Play-delivered version now includes the trigger, disclosure,
-Console. Do not replace the Internal candidate until that recording and the
+permission prompt, minimized persistent notification, notification Stop action,
-foreground-service declaration are complete.
+and stopped state. Its path and SHA-256 are recorded in
+`location-and-fgs-declaration.md`. It remains local evidence until it is hosted
+as an unlisted video and its URL is saved with the foreground-service
+declaration. Do not replace the Internal candidate before that declaration is
+complete.

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

@@ -83,10 +83,16 @@ resolution verifier. A production-fixture replay also verified user-initiated
 foreground location, minimized notification operation, notification Stop, 41
 samples, zero retained raw positions after Stop, and exact fixture cleanup.
 
+The final 21.379802-second foreground-location declaration video was recorded
+from this Play-delivered candidate and verified locally and server-side. Its
+path and SHA-256 are recorded in
+`android/play-store/location-and-fgs-declaration.md`. It has not yet been
+uploaded or entered in Play Console.
+
 The remaining gates are:
 
-1. create a concise final foreground-location declaration video from the
+1. host the verified final video as an unlisted video and enter its URL in the
-   Play-delivered candidate;
+   Play Console foreground-service/location form;
 2. complete and verify the Play Console foreground-service/location form;
 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

docs/verification.md

@@ -2723,9 +2723,14 @@ promoted.
   assignment, tracking session, and synthetic requester were then deleted.
 - The retained 177.864689-second source take is not the final Play declaration
   video because Android screen recording stopped before the Stop tap and
-  stopped state were captured. A concise complete take of 30 seconds or less,
+  stopped state were captured. A separate 21.379802-second final take from the
-  the Play foreground-service declaration, and Closed testing remain open
+  same Play-delivered build includes the trigger, disclosure, permission prompt,
-  gates. No Production Play rollout has been started.
+  minimized persistent notification, notification Stop action, and stopped
+  state. Its SHA-256 is
+  `3c5f52019bf8a42ff42e1d9232afc126b62627390d74eed75084d82ecb33ac56`.
+  Hosting that take as an unlisted video, 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