PLAN.md

@@ -956,6 +956,8 @@ deliberately so — no fetch can tell whether an APK runs. `checkFacts.mjs` asse
 still exist and that `minSdk` still says what "Android 10 or newer" claims, so the link is correct
 the moment a working build flips the boolean. The panel is not removed while the link is off: a page
 that omitted sideloading would read, to somebody who knows the APK exists, as a page hiding it.
+*(2026-10-31: the link is back on. Android `v0.7.0`'s APK was installed on an Android 16 emulator,
+connected to the public demo and read its Rust servers, so `serviceable` is `true`.)*
 
 **Three mechanisms this phase added that the plan did not anticipate.**
 

src/data/platform.json

@@ -120,17 +120,18 @@
     "",
     "`serviceable` is the one value here with no authority to check it against, and it is",
     "deliberately manual. It answers a question no API can: does the published build",
-    "actually work. The org lead reports v0.5.0's does not, so the download block renders a",
-    "'being replaced' state instead of a link, and flipping this to true is the single edit",
-    "that turns the link back on once a working build is released. A check cannot run an",
-    "APK; a person can, and this is where they record that they did."
+    "actually work. v0.5.0's did not, and while false the download block renders a 'being",
+    "replaced' state instead of a link. A check cannot run an APK; a person can, and this",
+    "is where they record that they did. v0.7.0's was installed on an Android 16 emulator",
+    "on 2026-10-31, connected to the public demo and read its Rust servers: true.",
+    "When `asset` moves to a new release, set this back to false until someone has run it."
   ],
   "androidApk": {
     "asset": "runic-gateway-0.7.0.apk",
     "checksums": "SHA256SUMS",
     "minSdk": 29,
     "minAndroid": "10",
-    "serviceable": false
+    "serviceable": true
   },
 
   "gitea": {