General: Add the Play Console declarations and their demo recorder

[d4rken]

What changed

No user-facing behavior change in the app.

The store listing no longer lists supported manufacturers and ROM versions. That list goes stale with every OEM system update and can't promise anything reliable — Amply already determines support on the device at runtime, so the listing now says Pixels generally have good support, that everywhere else depends on the specific phone, and that installing and opening the app is how you find out.

The privacy policy now covers the opt-in charging history, which landed after the policy was last written and wasn't described by it.

Technical Context

Play requires, per declared foreground service type, a functionality description, a statement of user impact if the task is deferred or interrupted, and a link to a demo video. None of that existed and it gates review, including for closed testing.

fastlane/play-declarations/ is the copy-paste source for the Console forms (specialUse FGS, app access, data safety) plus the tooling that regenerates the video — label-based UI driving over adb, screenrecord capture, and an ffmpeg pass for title card, timed captions and end card. Butler's play-declarations/ layout, adapted. Scripts are committed; the .mp4 is written to /tmp and is not.

Review guidance:

• The video demonstrates the unplug stop condition, not the 100% one. It's the condition that cannot work without a running foreground service — Android doesn't deliver the disconnect to a dormant app — which is exactly the argument the declaration makes. It also needs no simulated charge progression, so nothing on screen is faked beyond the disconnect. An earlier take that simulated the level to 100% ended on "Policy not verified", because a simulated battery blocks the hardware verification path; the unplug take ends on "80% limit active — Confirmed by Android's charging hardware".
• The recorder refuses a bad take. It aborts if the device doesn't start at the 80% limit, and fails the run unless it observed charge_optimization_mode go 1 → 0 → 1 across the take.
• Privacy hygiene is part of the recorder, not a manual step. The finished video goes to Google; the shade and QS strip would otherwise carry other apps' notifications and the Wi-Fi SSID. It clears the shade, enables DND and disables Wi-Fi for the take, restoring all three via an exit trap.
• The declaration text and the manifest's PROPERTY_SPECIAL_USE_FGS_SUBTYPE describe the same four functions; they have to be changed together.

Verified alongside this: bundleGplayRelease builds under R8 and is signed with the Play upload key at the path Fastfile expects (this was never exercised before — every artifact so far has been a FOSS APK).