simpletest/who_need_help
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record current Play Console launch gates

Browse Source
This commit is contained in:
SimpleTest 2026-08-26 04:17:32 +03:00
parent 5a6f99b2aa
commit c91ce502cb
2 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
android/play-store/release-checklist.md
View File

@ -68,7 +68,10 @@
2026-08-25. The retained AAB SHA-256, Android source fingerprint, 2026-08-25. The retained AAB SHA-256, Android source fingerprint,
provenance limitation, and strict Play-delivered phone verification are provenance limitation, and strict Play-delivered phone verification are
recorded in `internal-release-v4.md`. No Closed or Production release was recorded in `internal-release-v4.md`. No Closed or Production release was
created by this verification. created by this verification. A fresh read-only Console inspection on
2026-08-26 again showed version code `4`, version name `0.1.3`, target SDK
37, and status **Available to internal testers** on the Internal testing
track.
## Production capability gate ## Production capability gate
@ -124,7 +127,12 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
observed on local revision `dafcdb36`. The frozen hackathon test remains observed on local revision `dafcdb36`. The frozen hackathon test remains
intentionally unchanged and returns `404`. The public page is only one intentionally unchanged and returns `404`. The public page is only one
gate: do not self-certify until the monitored contact and real escalation gate: do not self-certify until the monitored contact and real escalation
workflow are also verified. workflow are also verified. On 2026-08-26 the authenticated App content
overview showed exactly one item under **Need attention**: Child safety
standards. The declaration itself was still blank and its Save action was
disabled. A simultaneous public request returned `200` and displayed the
CSAE/CSAM standards and dedicated reporting path, but that technical
evidence does not authorise the separate legal-compliance attestation.
## App content ## App content

5
docs/public-launch-checklist.md
View File

@ -137,6 +137,11 @@ The following decisions are intentionally not generated by code:
incident queues have named owners and monitored contact paths. incident queues have named owners and monitored contact paths.
- [ ] Provider terms and capacity are approved for email, map tiles, Google - [ ] Provider terms and capacity are approved for email, map tiles, Google
identity, Web Push, Firebase/FCM, database hosting, backups, and monitoring. identity, Web Push, Firebase/FCM, database hosting, backups, and monitoring.
- [ ] The Google Play child-safety declaration has a named monitored contact,
an approved escalation/reporting procedure, and an owner-approved legal
attestation. On 2026-08-26 Play Console showed this as the only App content
item needing attention. The public standards page and reporting route are
live, but they do not by themselves prove the legal attestation.
- [ ] Google Analytics for Firebase remains disabled until the operator has - [ ] Google Analytics for Firebase remains disabled until the operator has
approved a purpose and event allow-list, updated the privacy notice, approved a purpose and event allow-list, updated the privacy notice,
implemented an explicit user analytics preference, and verified that the implemented an explicit user analytics preference, and verified that the