[green] publish consistent Android open-testing availability

Replace obsolete invited internal-testing claims across README, homepage, app installation, tutorial setup and search/social metadata. Keep the official Google Play URL and QR payload, preserve historical artifact provenance, and refresh the affected sitemap entries.

Validation: npm run check (346 tests, both builds, zero audit findings); 42 publication tests; Markdown links; no-leak; SPDX; git diff --check.
Signed-off-by: Viwat Vchirawongkwin <viwat.v@chula.ac.th>

Author: yyods

README.md

@@ -21,7 +21,8 @@ telemetry.
 - Official example collection: [PyBLE-dev/examples](https://github.com/PyBLE-dev/examples)
 - iPad external beta:
   [join with TestFlight](https://testflight.apple.com/join/yU4e8s6d)
-- Android invited testing: [see the app page](https://pyble.dev/app)
+- Android 0.2.0 published for open testing:
+  [get PyBLE on Google Play](https://play.google.com/store/apps/details?id=dev.pyble.pyble)
 - License: [MIT](LICENSE)
 
 <p align="center">
@@ -75,13 +76,20 @@ and asks separately before overwriting existing files. Import never creates a
 remote folder hierarchy, opens an editor document, or runs downloaded code.
 
 The current App source version is `0.2.0+8`; App and firmware versions are
-independent. iPad testing uses TestFlight, and Android distribution follows
-the testing access shown on the [App page](https://pyble.dev/app). The
+independent. The published Android version is `0.2.0`, available through
+[Google Play open testing](https://play.google.com/store/apps/details?id=dev.pyble.pyble).
+iPad testing continues through TestFlight. The
+[App page](https://pyble.dev/app) provides both installation links and QR codes.
+Google Play determines account, country, device, and testing availability;
+open testing is a beta channel, not a production-track release.
+
+The [publication review](docs/testing/website/android-open-testing-2026-09-25.md)
+records the current Android availability. The earlier
 [Google Play build-8 handoff](docs/testing/google-play/0.2.0-build-8.md)
-records prepared artifacts and their exact source; preparation does not
-establish a live store release or mean those earlier artifacts contain later
-connection-lifecycle fixes. Both platforms share the same Flutter source and
-app test gates. The iOS/iPadOS project minimum is 15.
+records prepared artifacts and their exact source. The store's public version
+does not establish its installed build/source identity or mean those earlier
+artifacts contain later connection-lifecycle fixes. Both platforms share the
+same Flutter source and app test gates. The iOS/iPadOS project minimum is 15.
 
 ### Firmware
 
@@ -168,9 +176,12 @@ shared conformance corpus, documentation, and CI atomically.
 
 ## Try PyBLE
 
-1. Install the iPad beta from
-   [TestFlight](https://testflight.apple.com/join/yU4e8s6d), or build the
-   Flutter app locally.
+1. Install PyBLE 0.2.0 for Android open testing from
+   [Google Play](https://play.google.com/store/apps/details?id=dev.pyble.pyble),
+   or install the iPad external beta from
+   [TestFlight](https://testflight.apple.com/join/yU4e8s6d). The
+   [App page](https://pyble.dev/app) has links and QR codes for both platforms.
+   You can also build the Flutter app locally.
 2. Open [pyble.dev/flash](https://pyble.dev/flash) in a supported desktop
    Chromium browser. Confirm that the published v0.6.1 release is selected,
    then choose only the exact profile matching the board and memory topology.

docs/ROADMAP.md

@@ -11,14 +11,19 @@ v0.7.0 remains non-normative and requires separate maintainer approval.
 ## Available now
 
 - iPad external beta through TestFlight
+- Android PyBLE 0.2.0 published for
+  [Google Play open testing](https://play.google.com/store/apps/details?id=dev.pyble.pyble),
+  subject to Play's account, country, device, and testing availability
 - PBLE/1 editing, run/stop, console, and file workflows over BLE
 - Offline Blockly with beginner GPIO and NeoPixel examples
 - The published firmware v0.6.1 covers five exact profiles: four ESP
   Web Serial installers and the verified Pico 2 W UF2/manual-BOOTSEL path.
   Publication follows the owner's qualification confirmation, recorded in the
   [owner confirmation](https://pyble.dev/firmware-v0.6.1-owner-confirmation.md).
   Incomplete automated evidence is preserved unchanged; the qualified v0.6.0
-  release remains a separate historical baseline.
+  release remains a separate historical baseline. The original qualification
+  tracker [#24](https://github.com/PyBLE-dev/PyBLE/issues/24) was closed as
+  superseded on 2026-09-13; its incomplete checklist is not marked completed.
 - Guided [tutorials](https://pyble.dev/learn) with reviewed Lenovo captures,
   the [firmware functional reference](https://pyble.dev/features), and the
   separate [official example collection](https://github.com/PyBLE-dev/examples)
@@ -27,14 +32,15 @@ v0.7.0 remains non-normative and requires separate maintainer approval.
 ## Near term
 
 - Continue the app 0.2.0 beta train; source is currently `0.2.0+8`. The
-  [prepared build-8 handoff](testing/google-play/0.2.0-build-8.md) is not proof
-  of store publication or validation of subsequent source changes.
-- Reconcile the original automated qualification tracker
-  [#24](https://github.com/PyBLE-dev/PyBLE/issues/24) with the recorded
-  owner-confirmed v0.6.1 publication without inventing missing measurements.
+  [Android publication review](testing/website/android-open-testing-2026-09-25.md)
+  records live open-testing availability. The
+  [prepared build-8 handoff](testing/google-play/0.2.0-build-8.md) remains a
+  source-specific historical record, not validation of subsequent source
+  changes in the installed store app.
 - Review the proposed v0.7.0 Reliable Projects scope before implementation.
 - Expand user-facing setup, recovery, and board-specific wiring guidance
-- Open and document the Android beta distribution path
+- Gather Android open-testing feedback and improve installation and recovery
+  guidance
 - Convert remaining pre-public planning references into focused GitHub issues
 - Improve automated app-to-board integration coverage
 

docs/specifications/google-play-release.md

@@ -2,18 +2,40 @@
 
 # Google Play open-testing preparation
 
-Status: candidate preparation, 10 September 2026. This contract supplements
+Status: historical candidate preparation, 10 September 2026; publication status
+updated 25 September 2026. This contract supplements
 the [app distribution requirements](App/specs.md#9-build-versioning--distribution--bld)
 and [ADR-0044](../decisions/0044-start-app-v020-beta-train-at-build-5.md).
 
-The owner has reported that open testing is available for the existing Play
-application. Preparation does not imply a submitted or approved release.
+At preparation time, the owner reported that the open-testing track was
+available for the existing Play application. That preparation alone did not
+establish a submitted or approved release.
+
+## Published status — 25 September 2026
+
+The owner confirms that PyBLE **0.2.0** is now published on Google Play for
+Android **open testing**. The official
+[listing](https://play.google.com/store/apps/details?id=dev.pyble.pyble)
+identifies SciLabPro and describes open testing for this version. The
+[publication review](../testing/website/android-open-testing-2026-09-25.md)
+records the primary-source check.
+
+Current README and website copy MUST reflect this live open-testing status,
+as specified by [website §3.1](website.md#31-app-beta-distribution). Google Play
+determines account, country, device, and testing availability. Do not infer a
+production-track release, worldwide availability, or the installed artifact's
+exact version code/source from the public version alone. Keep the official
+listing as the public link; no signed-in opt-in workflow is asserted verified.
+
+The preparation, artifact identities, and remaining historical checklists
+below retain their original scope. Publication does not retroactively certify
+unrecorded Console decisions, hardware evidence, or later source changes.
 
 ## Candidate identity
 
-The next candidate is **0.2.0 (8)**, owned by `app/pubspec.yaml`, for production
-package `dev.pyble.pyble`. Build 5 remains a historical handoff; retained local
-builds 6 and 7 must not be relabelled or replaced. The automated app-version
+The 10 September candidate is **0.2.0 (8)**, owned by `app/pubspec.yaml`, for
+production package `dev.pyble.pyble`. Build 5 remains a historical handoff;
+retained local builds 6 and 7 must not be relabelled or replaced. The automated app-version
 contract must bind build 8 to base version 0.2.0, PBLE/1 HELLO, and the existing
 GitHub User-Agent. If Play Console has already consumed code 8 or higher,
 increase this declaration and the version contract before rebuilding.
@@ -58,10 +80,12 @@ any stale golden requiring a reviewed update. Physical release-candidate BLE
 checks and iOS distribution parity remain separate release gates; an emulator
 or historical engineering report does not close them.
 
-Keep the public website's existing testing status until open testing is
-actually available. Console declarations, reviewer arrangements, upload,
-review submission and rollout remain explicit handoff steps. This preparation
-does not authorize sending tester messages or publishing a production release.
+At the preparation handoff, the public website's testing status was to remain
+unchanged until open testing became available. The dated publication status
+above now governs current public copy. Console declarations, reviewer
+arrangements, upload, review submission and rollout remain explicit handoff
+steps. This preparation does not authorize sending tester messages or
+publishing a production release.
 
 ## Official references
 

docs/specifications/website.md

@@ -125,7 +125,7 @@ Compatibility copy MUST distinguish platform scope from current support:
 It MUST NOT imply that Bluetooth hardware or stock MicroPython alone is enough,
 or promise that every eligible board has a firmware image today.
 
-### 3.1 App distribution
+### 3.1 App beta distribution
 
 The current app channels, verified on 2026-09-25, are:
 

docs/testing/website/android-open-testing-2026-09-25.md

@@ -0,0 +1,53 @@
+<!-- SPDX-License-Identifier: MIT -->
+<!-- Part of PyBLE (https://pyble.dev) — see /LICENSE. -->
+
+# Android open-testing publication review — 2026-09-25
+
+## Observed status
+
+The project owner confirms that PyBLE is published on Google Play. Current
+first-party README and website copy still described an invited Android
+internal test, while the public store listing described open testing.
+
+The official [Google Play listing](https://play.google.com/store/apps/details?id=dev.pyble.pyble)
+was retrieved over HTTPS on 2026-09-25 with English/US presentation parameters
+(`hl=en&gl=US`). It returned HTTP 200 and identified **SciLabPro**, app version
+**0.2.0**, and release notes stating **“Open testing for PyBLE 0.2.0.”** The
+package is `dev.pyble.pyble`. This primary-source result supports the
+owner-confirmed publication and supersedes the invited internal-testing copy.
+
+The [AppAgg entry](https://appagg.com/android/education/pyble-micropython-ide-44135975.html?hl=en)
+also lists version 0.2.0 and the same open-testing release notes, with a
+2026-09-16 listing date. It is corroborating third-party indexing, not proof of
+the exact rollout date or Play Console configuration.
+
+## Current publication contract
+
+- Describe Android as **PyBLE 0.2.0 published on Google Play for open testing**.
+- Keep iPad described as the external TestFlight beta.
+- Link directly to the existing official Google Play listing and encode the
+  same destination in the neutral `/google-play/pyble-google-play-qr.svg` asset.
+- Keep README, home, `/app`, metadata, setup guidance, and current distribution
+  documentation consistent. Remove the invitation requirement from current
+  Android installation guidance.
+- Google Play determines account, country, device, and testing availability.
+  Open testing does not establish a production-track release or universal
+  availability.
+
+The candidate opt-in endpoint redirected to Google sign-in. No signed-in
+enrollment or on-device installation was verified in this review. The public
+listing remains the link; no inferred opt-in destination is introduced.
+
+## Source and evidence boundaries
+
+The repository's App source version remains `0.2.0+8`. The public app version
+`0.2.0` does not establish the installed store artifact's version code, source
+commit, or inclusion of later connection-lifecycle fixes. The
+[build-8 handoff](../google-play/0.2.0-build-8.md) and original submission
+materials remain historical preparation records. Firmware versions and
+qualification evidence remain independent of the app distribution channel.
+
+This record documents availability and the coordinated content contract. It
+does not attest a deployment, signed-in Play Console state, installed app
+binary, or hardware-validation result. Search engines control when indexed
+snippets refresh after updated pages are published.

tests/publication/test_public_claims.py

@@ -182,7 +182,8 @@ def test_current_public_surfaces_agree_on_v061_publication(self) -> None:
             "v0.7.0",
             near_term,
         )
-        self.assertIn("automated qualification", near_term)
+        self.assertIn("closed as superseded on 2026-09-13", available)
+        self.assertIn("incomplete checklist is not marked completed", available)
 
     def test_readme_distinguishes_app_source_from_store_availability(self) -> None:
         firmware = markdown_section(self.readme, "What works")

tools/web/DEPLOYMENT.md

@@ -39,9 +39,11 @@ Review at least:
 - home at phone, portrait-tablet, landscape-tablet, and desktop widths;
 - home and metadata clearly separate the capability-defined MicroPython + BLE
   platform vision from the targets validated by the current release;
-- `/app`, including the current iPad external-beta and Android internal-test
-  destinations, scannable local QR images, visible fallback addresses,
-  invited-account restriction, and links to firmware and support;
+- home, `/app`, and setup guidance identify the iPad external beta and published
+  Android PyBLE 0.2.0 Google Play open test consistently, including page and
+  social descriptions; verify the official `dev.pyble.pyble` listing link,
+  scannable local QR images, visible fallback addresses, Play availability
+  guidance, and links to firmware and support;
 - `/privacy`, including the effective date and public contact address;
 - `/support`, including the public contact address;
 - `/flash`, confirming the install button is still disabled unless the

tools/web/README.md

@@ -34,13 +34,20 @@ introduce a second page source or an application backend.
 | Route       | Purpose                                                                     |
 | ----------- | --------------------------------------------------------------------------- |
 | `/`         | Product story, verified capabilities, platform vision, and current targets  |
-| `/app`      | Stable app landing page for iPad and Android testing channels               |
+| `/app`      | iPad TestFlight beta and published Android Google Play open-testing links   |
 | `/privacy`  | Separate app and website privacy disclosures                                |
 | `/support`  | Beta quick start, troubleshooting, and report checklist                     |
 | `/flash`    | Fail-closed Web Serial installer, exact profiles, and recovery              |
 | `/features` | Release-bound firmware architecture, operations, profiles, limits, evidence |
 | `/learn`    | Ordered tutorial hub, compatibility legend, and learning tracks             |
 
+Android PyBLE 0.2.0 is published for Google Play open testing. Home, `/app`,
+their metadata, and setup guidance share this status; iPad remains an external
+TestFlight beta. The official Android listing uses package `dev.pyble.pyble`.
+Both the direct link and local `/google-play/pyble-google-play-qr.svg` QR code
+use `https://play.google.com/store/apps/details?id=dev.pyble.pyble`. Play
+determines account, country, device, and testing availability.
+
 The ten statically authored tutorials are `/learn/setup`,
 `/learn/first-program`, `/learn/files`, `/learn/github-import`,
 `/learn/blocks`, `/learn/examples`, `/learn/hardware`,

…y/pyble-google-play-internal-test-qr.svg …lic/google-play/pyble-google-play-qr.svgtools/web/public/google-play/pyble-google-play-internal-test-qr.svg renamed to tools/web/public/google-play/pyble-google-play-qr.svg tools/web/public/google-play/pyble-google-play-internal-test-qr.svg renamed to tools/web/public/google-play/pyble-google-play-qr.svg

@@ -1,7 +1,7 @@
 {
   "name": "PyBLE — Python over Bluetooth Low Energy",
   "short_name": "PyBLE",
-  "description": "A free, open-source, tablet-first IDE for MicroPython boards with compatible Bluetooth Low Energy agent firmware.",
+  "description": "PyBLE is a free, open-source MicroPython IDE over Bluetooth Low Energy. Available on Google Play open testing for Android and TestFlight for iPad.",
   "start_url": "/",
   "display": "standalone",
   "background_color": "#F4F7FF",