Play 'Live' only when the public store page proves it: play status checks https://play.google.com/store/apps/details?id=<pkg> (no auth, 4 s timeout, cached 5 min; publicPage in the JSON), a completed production release with a 404 page is 'Sent to Google (in review or not yet published)', 200 is live for the first release or when the page shows the versionName, otherwise 'Released to production (Google may still be reviewing)', offline is unknown; new phases sent / released in the desktop Releases tab, Portfolio, release status | plan; versions matched across the stores without trailing .0 parts (App Store 1.0 and Play 1.0.0 are one row and one train, each side shows its own string); tests/play-public-version-match.test.ts, desktop boot check release-state cases (page 404 and 200) (pitfall 56)

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## Unreleased
+
+- **Play "Live" only when the store page proves it.** The Play Developer API has no review state: a production release
+  reads `completed` while Google still reviews it. `play status` now checks the public store page (no auth, fast
+  timeout, cached 5 minutes) and adds `publicPage` to its JSON: page 404 = "Sent to Google (in review or not yet
+  published)", 200 = live for the first release, an update is "Released to production (Google may still be
+  reviewing)" unless the page shows its versionName, offline = unknown. New release phases `sent` and `released` in
+  the desktop Releases tab, Portfolio, `release status | plan` and the CLI JSON. Pitfall 56.
+- **One row per release across the stores.** Versions are matched without trailing .0 parts (App Store "1.0" and Play
+  "1.0.0" are one row and one timeline); each side still shows the store's own string.
+
+
 ## 0.8.1 · 2026-10-13
 
 `apple build` exports each build into its own folder and fails loudly on any export error; `apple upload` refuses a