Publish 0.3.0 download and upgrade guidance

Author: johndoe

README.md

@@ -11,7 +11,7 @@
 
 ![Muse, beyond the chat: an open-source Android runtime, illustrated with phone, tablet and TV layouts](docs/social-preview.png)
 
-*Phone, tablet and TV layouts from the 0.3 development UI; see [device validation](#what-is-verified) for tested hardware. The latest published APK is **0.2.0**; the features and interface below require a 0.3 [source build](docs/BUILD.md) or development CI artifact until 0.3 is released.*
+*Phone, tablet and TV layouts from 0.3.0; see [device validation](#what-is-verified) for tested hardware. [Download 0.3.0](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0) to try this interface. Published APKs use development signing; production signing remains planned.*
 
 ## Build an Android endpoint, keep the SDK upstream
 
@@ -42,7 +42,7 @@ The app uses the **unmodified upstream Muse Gadget SDK** for pairing and cloud c
 
 ## Quick start
 
-**For the current 0.3 experience:** [build and install the APK](docs/BUILD.md), or get a development artifact from a successful [CI run](https://github.com/hypery11/muse-gadget-everywhere/actions/workflows/ci.yml). **For the published 0.2 release:** [download `app-debug.apk`](https://github.com/hypery11/muse-gadget-everywhere/releases/download/v0.2.0/app-debug.apk); it has the earlier pairing/TV controls and UI. Published 0.2 is a development-signed APK.
+**Download 0.3.0:** [Universal APK — including Chromecast](https://github.com/hypery11/muse-gadget-everywhere/releases/download/v0.3.0/muse-gadget-0.3.0-universal-debug.apk) · [Modern APK — 64-bit / 16 KiB](https://github.com/hypery11/muse-gadget-everywhere/releases/download/v0.3.0/muse-gadget-0.3.0-modern-debug.apk) · [Release notes and checksums](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0). These development-signed APKs use the same signing certificate as the published 0.2 APK. Use `adb install -r` to update without uninstalling; see [upgrade instructions](docs/GETTING_STARTED.md#install). You can also [build from source](docs/BUILD.md).
 
 1. **Install on your Android device.** Android 7.0+ is the minimum. Use the universal build for Chromecast; devices with 16 KiB pages need the modern build. [Choose a build and connect ADB →](docs/GETTING_STARTED.md)
 2. **Try it locally.** Open the app → **Start service → Try a card → Show card**. A visible message is your first success; no Muse account is needed for this step.

README.zh-TW.md

@@ -6,7 +6,7 @@
 
 ![Muse，走出聊天室：Android 開源執行環境與手機、平板、TV 介面](docs/social-preview.png)
 
-> 圖片展示 **0.3 開發中原始碼**的手機、平板與 TV 版型，已測硬體請見下方驗證範圍。目前公開 APK 仍是 **0.2.0**，使用舊版介面，主要提供配對與 TV 控制。要體驗新版，請依[建置指南](docs/BUILD.md)自行編譯，或下載成功 CI run 的開發版產物。
+> 圖片展示 **0.3.0** 的手機、平板與 TV 版型，已測硬體請見下方驗證範圍。[下載 Universal APK（含 Chromecast）](https://github.com/hypery11/muse-gadget-everywhere/releases/download/v0.3.0/muse-gadget-0.3.0-universal-debug.apk) · [Modern APK（64 位元／16 KiB）](https://github.com/hypery11/muse-gadget-everywhere/releases/download/v0.3.0/muse-gadget-0.3.0-modern-debug.apk) · [版本說明與 SHA256](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0)。APK 使用開發簽章，與公開 0.2 版憑證相同；正式產品簽章仍待建立。
 
 ## 給開源開發者的入口
 
@@ -22,7 +22,7 @@ cd muse-gadget-everywhere
 
 ## 先讓它做一件有用的事
 
-1. 安裝 APK：Chromecast 請用 **universal**；需要 16 KiB 記憶體頁面的 ARM64/x86_64 裝置請用 **modern**。最低 Android 7.0，硬體能力另有差異。
+1. 下載上方 APK：Chromecast 請用 **universal**；需要 16 KiB 記憶體頁面的 ARM64/x86_64 裝置請用 **modern**。最低 Android 7.0，硬體能力另有差異。從公開 0.2 版升級時，使用 `adb install -r muse-gadget-0.3.0-universal-debug.apk` 保留資料，不必先移除 App；自行編譯或 CI 產物可能使用不同簽章，請見[升級說明](docs/GETTING_STARTED.md#install)。
 2. 開啟 App → **Start service → Try a card → Show card**。先看到訊息出現在螢幕上；這一步不必配對 Muse。
 3. 要遠端控制時，回首頁選 **Pair with Muse**。從 [gadgets.muse.ai](https://gadgets.muse.ai/settings/sdk-tokens) 取得 SDK token，儲存後開啟配對視窗。
 4. Muse 手機 App → Settings → Devices → Add Device，完成配對後選 **Start service & open controls**。

docs/BUILD.md

@@ -41,13 +41,15 @@ use the same output path: copy an APK before building another variant.
 `-PsplitApks=true` also creates ABI APKs; Python asset archives limit how much
 ordinary Android ABI splits can reduce size.
 
-Release builds stay unsigned unless all four private environment variables are
+The **Gradle release build type** stays unsigned unless all four private environment variables are
 provided: `MUSE_RELEASE_STORE`, `MUSE_RELEASE_STORE_PASSWORD`,
 `MUSE_RELEASE_KEY_ALIAS`, `MUSE_RELEASE_KEY_PASSWORD`.
 Run `./gradlew :app:assembleRelease` after configuring them in your secret store.
 Never commit the keystore or passwords. An unsigned release build is useful for
 packaging checks and is not an installable published release.
 
+GitHub Release [0.3.0](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0) distributes installable **debug build type** APKs, built with the same persistent development signing key used for the published 0.2 APK. Both universal and modern downloads include checksums. They are not production-signed; the signing key stays outside the repository. Ordinary CI artifacts below use separate, temporary keys and are not interchangeable updates.
+
 
 For development checks, see [CONTRIBUTING](../CONTRIBUTING.md).
 

docs/COMPATIBILITY.md

@@ -52,5 +52,7 @@ is not a supported setup procedure and is not counted as fresh 0.3 pairing.
   the old external import file is optional and is deleted after successful import.
 - No 72-hour soak result is claimed. Android 16/17 behavior and a target-SDK
   upgrade are not validated by the API-35 run. Newer emulator images do exist.
-- Release APKs remain unsigned unless private release-signing variables are
-  supplied. No store submission or new public release is implied by these tests.
+- The Gradle release build type remains unsigned unless private release-signing
+  variables are supplied. Published [0.3.0 downloads](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0)
+  use the debug build type and the same development certificate as published 0.2.
+  No store submission or production signing is claimed.

docs/GETTING_STARTED.md

@@ -2,7 +2,7 @@
 
 [Project](../README.md) · [Build](BUILD.md) · [繁體中文](../README.zh-TW.md)
 
-This guide describes **0.3 development source/CI builds**. The published 0.2 APK has the earlier Probe/Pair interface; it does not contain the new local control dashboard.
+This guide describes **0.3.0**, available as installable APKs from [GitHub Releases](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0), or as a [source build](BUILD.md).
 
 ## Choose a build
 
@@ -16,16 +16,20 @@ If unsure, connect ADB and run `adb shell getconf PAGE_SIZE` (4096 or 16384) and
 
 ## Install
 
+Download `muse-gadget-0.3.0-universal-debug.apk` or `muse-gadget-0.3.0-modern-debug.apk` from the release above. `SHA256SUMS` is provided alongside the APKs. Published 0.3.0 APKs use the same development signing certificate as the published 0.2 APK.
+
 On a phone/tablet, enable Developer options and USB debugging, connect USB and accept the Android authorization prompt. On Chromecast with Google TV, open Settings → System → About and tap the Android TV OS build entry seven times. Enable the debugging option offered by that device.
 
 For network ADB, use the address/port shown by Android. If the device offers wireless pairing, run `adb pair HOST:PAIR_PORT`, then `adb connect HOST:CONNECT_PORT`. Older TV builds may offer debugging on port 5555 without a separate pairing-code flow. Ports and menu labels vary by Android version; do not assume the pairing port is the connection port.
 
 ```sh
 adb devices
-adb install -r app/build/outputs/apk/debug/app-debug.apk
+adb install -r muse-gadget-0.3.0-universal-debug.apk
 ```
 
-An incompatible signing key blocks an in-place update. Do not uninstall reflexively: uninstalling erases pairing and local settings. Keep the original signing key for updates.
+Use the modern filename instead if that is your selected build; source builds are at `app/build/outputs/apk/debug/app-debug.apk`. The `-r` option updates in place and preserves app data. Open the app and start the service after updating.
+
+An incompatible signing key blocks an in-place update, including some local builds and CI artifacts. Do not uninstall reflexively: uninstalling erases pairing and local settings. Keep the original signing key for updates. Production signing is not established yet; these APKs remain development-signed.
 
 ## Try local controls
 

docs/ROADMAP.md

@@ -2,7 +2,7 @@
 
 [Project](../README.md) · [Contributing](../CONTRIBUTING.md)
 
-This is a prioritized direction, not a delivery-date promise. The current public release is 0.2; 0.3 is under development.
+This is a prioritized direction, not a delivery-date promise. The current public release is [0.3.0](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0), with universal and modern APKs using development signing.
 
 ## Make the first success easy
 
@@ -24,7 +24,7 @@ This is a prioritized direction, not a delivery-date promise. The current public
 
 - Complete native dependency remediation and review build provenance.
 - Establish production signing and documented update continuity.
-- Ship clearly named universal/modern artifacts with checksums and release notes.
+- Preserve clearly named universal/modern artifacts, checksums and release notes for each version.
 - Keep release screenshots and feature descriptions aligned with the downloadable version.
 
 ## Grow useful examples

docs/VALIDATION-RESULTS.md

@@ -1,6 +1,6 @@
-# Validation summary — 0.3 development
+# Validation summary — 0.3.0
 
-Results were collected on 2026-10-04, with a copy/artwork build check on 2026-10-05. This is a maintainer-reported summary. CI provides independently inspectable build results; private account sessions and raw device captures are not distributed. [Reproduce the checks](VALIDATION.md) · [Compatibility](COMPATIBILITY.md) · [Security limits](SECURITY.md).
+Results were collected on 2026-10-04, with copy/artwork and release-package checks on 2026-10-05. This is a maintainer-reported summary. CI provides independently inspectable build results; private account sessions and raw device captures are not distributed. [Reproduce the checks](VALIDATION.md) · [Compatibility](COMPATIBILITY.md) · [Security limits](SECURITY.md).
 
 | Check | Result and scope |
 | --- | --- |
@@ -13,7 +13,10 @@ Results were collected on 2026-10-04, with a copy/artwork build check on 2026-10
 | Real Chromecast with Google TV, API 31 | BLE pairing, Muse commands, cards, TTS, Cast play/pause/resume/stop and reboot reconnection verified separately from cloud-isolated regression |
 | Adaptive layout | TV D-pad navigation, phone layout, 1.3× font scaling and tablet-sized emulator layout inspected |
 | Branding follow-up, 2026-10-05 | Universal debug build and lint passed after the device-neutral Home copy and launcher banner update; no new physical-device run |
+| Published 0.3.0 packages, 2026-10-05 | Universal and modern rebuilt and linted; both signatures match published 0.2. Universal updated a clean API 35 fixture from the actual 0.2 download using `adb install -r`, preserving synthetic app data. Packaged runtime/UI regression passed on API 35 with 4 KiB (universal) and 16 KiB (modern): 3 executed, 2 opt-in tests skipped per build. Modern's 146 native libraries and ZIP packaging passed 16 KiB checks. |
 
 The UI regression verifies navigation, draft retention and rejection of an invalid scene ID before dispatch. Runtime checks cover native media, OCR/barcode fixtures, local scenes and lifecycle. A passing local test does not prove cloud transport, hardware camera quality or a physical phone/tablet installation.
 
+Release-package checks used fresh fixtures without Muse account credentials. The upgrade test establishes installer/data continuity, not a new cloud pairing or refresh-token migration test. Both installable APKs and `SHA256SUMS` are attached to [0.3.0](https://github.com/hypery11/muse-gadget-everywhere/releases/tag/v0.3.0); CI artifacts have different signing keys.
+
 Still open: physical phone/tablet reports, real Home Assistant/MQTT installations, a 72-hour soak, production signing and the dependency advisories documented in [SECURITY.md](SECURITY.md). Tablet layouts are emulator fixtures. No blanket compatibility, security or long-term stability claim is made.