Merge pull request #332 from saphid/release/v0.4.47

Prepare Frame Control v0.4.47 candidate

app/package-lock.json

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

app/package.json

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

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

@@ -0,0 +1,46 @@
+# v0.4.47 candidate gate, 26 October 2026
+
+This candidate contains Game Theme Music's locally rendered Settings view
+(#330) and a digest-scoped Python import module for the official Shotty 0.1.0
+archive (#331). The 116-plugin table is **4 works / 52 partial / 49 broken /
+11 N/A**. Game Theme Music is partial for its local Settings view; its
+backend, network and playback were denied in that audit. Shotty is partial
+for its local frontend and synthetic screenshot copy in isolated Python;
+actual ARM64 Decky startup and live screenshot rescue are unverified.
+
+## Locked Frame candidate smoke
+
+At 14:18 UTC, source commit `1f5b37a7552880b40868617ef22398fcd39b3f5d`
+ran `scripts/frame-smoke.sh` on the real Frame. The script acquired its unique
+owner in `/tmp/frame-test.lock` before reading status. Locked preflight found
+SteamVR activity **3** (standby), proximity raw **3.0625**, and battery
+**100%** on Frame OS 0.5.6 build `20261022.6153909`. Owned ARM64 and
+Windows/Proton test titles installed, launched, and were removed. The
+optional x86_64 title installed and was removed; launch was **skipped**
+because Steam Linux Runtime 4 was absent. The result was **12 passed /
+1 skipped / 0 failed**. Cleanup passed and the command exited 0, including
+release of its owned lock. Detailed results stay private in
+`tests/smoke/results/2026-10-26T141812Z-20261022.6153909.json`.
+
+No wearer was confirmed. The interactive worn-check script was not run;
+the smoke did not wake the headset or test the Framey panel. Game Theme
+Music playback, Shotty live rescue, wearer-visible official-plugin UI,
+physical controllers, keyboard and optical comfort remain unverified.
+The hourly shared-lock worn check remains enabled.
+
+## Publication boundary
+
+At 14:23 UTC, the exact version-bumped candidate commit
+`e07fa155928d1609304e317d15e0c4ef4a977579` ran the same token-locked
+`scripts/frame-smoke.sh`.
+Preflight again found activity **3** (standby), proximity raw **3.0625** and
+battery **100%**. The result was **12 passed / 1 optional x86 launch skipped /
+0 failed**. Owned cleanup passed and the command exited 0 after releasing its
+lock. Its private result is
+`tests/smoke/results/2026-10-26T142321Z-20261022.6153909.json`.
+This paragraph is the only change after that smoke.
+
+PR #331's combined-head CI, green release-PR and post-merge CI, tagged
+installer builds, all ten installer digests with `SHA256SUMS`, independent
+package checks, publisher dry run, and public `update.json` readback remain
+required.