Merge pull request #336 from saphid/release/v0.4.48

Prepare Frame Control v0.4.48 candidate

app/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "frame-control",
-  "version": "0.4.47",
+  "version": "0.4.48",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "frame-control",
-      "version": "0.4.47",
+      "version": "0.4.48",
       "license": "MIT",
       "devDependencies": {
         "electron": "^44.4.5",

app/package.json

@@ -1,7 +1,7 @@
 {
   "name": "frame-control",
   "productName": "Frame Control",
-  "version": "0.4.47",
+  "version": "0.4.48",
   "description": "Desktop app for managing a Valve Steam Frame over SSH",
   "private": true,
   "main": "main.js",

docs/evidence/v0448-candidate-2026-10-26.md

@@ -0,0 +1,50 @@
+# v0.4.48 candidate gate, 26 October 2026
+
+This candidate contains the exact-archive Music Control 1.1.7 Python call
+repair from [#335](https://github.com/saphid/frame-control/pull/335). All
+**11** hosted checks passed on its head
+`ff465accc508e40158c590eebffd4aec924503ac`, including fake-Frame e2e,
+Windows, macOS, Linux, ARM64 host libraries and iOS. The catalog remains
+**4 works / 52 partial / 49 broken / 11 N/A** out of 116. Music Control is
+partial: an isolated D-Bus command fixture proves dispatch after the repair;
+a live player and actual Decky ARM64 backend were not tested.
+
+## Locked real Frame smoke
+
+At 15:36 UTC, source head `ff465accc508e40158c590eebffd4aec924503ac`
+ran `scripts/frame-smoke.sh` on SteamOS 0.5.6 build `20261022.6153909`.
+The runner acquired its own unique `/tmp/frame-test.lock` owner before
+reading device status. Preflight found SteamVR activity **3** (standby),
+proximity raw **3.0625**, and battery **99%**. Owned ARM64 and Windows/Proton
+titles installed, launched and were removed. The optional x86_64 title
+installed and was removed; its launch was **skipped** because Steam Linux
+Runtime 4 was absent. The result was **12 passed / 1 skipped / 0 failed**.
+Owned cleanup passed and the command exited 0, including lock release.
+A separate fresh locked read found battery **100%**, activity **3** and no
+`fc_smoke_*` title directories; it released only its own lock. The private
+runner result is `2026-10-26T153655Z-20261022.6153909.json`.
+
+At 15:42 UTC, exact version-bumped commit
+`a31b4a426cf4204e45fe218e204a26328aa0b1c9` ran the same token-locked
+smoke. Preflight found activity **3**, proximity raw **3.0625** and battery
+**100%**. It passed **12 / 1 optional x86 launch skipped / 0 failed**.
+Cleanup passed and the command exited 0 after releasing its lock. The
+private runner result is `2026-10-26T154258Z-20261022.6153909.json`.
+A fresh separately locked read found battery **100%**, activity **3** and
+no test-title directories, then released that lock. Merging current main
+into the candidate created commit
+`a8bf01d660cd9abb8d2a724626a06a0e7e6c2a6a`; its tree before this
+evidence document was byte-identical to the tested version-bumped commit
+(`d45c2465ddfcf877fe2c8bc30420d4719da5035e`).
+
+No wearer was confirmed. Neither smoke woke the headset or ran the
+interactive worn-check script. Official-plugin wearer visibility, physical
+controllers, VR keyboard and optical comfort remain unverified. The hourly
+shared-lock worn check remains enabled.
+
+## Remaining publication gates
+
+The release PR's exact-head CI and installer previews, post-merge main CI,
+tagged builds with all ten installers and `SHA256SUMS`, independent package
+checks, publisher dry run and public `update.json` readback are required
+before publication.