From 3acc2d91e60b10b3f955e25b72a8782f7d62a6c1 Mon Sep 17 00:00:00 2001 From: SAPHID Date: Sun, 25 Oct 2026 23:08:07 +0000 Subject: [PATCH] Record v0.4.36 real Frame release smoke --- docs/current-support-matrix.md | 2 +- .../v0436-release-smoke-2026-10-25.md | 24 +++++++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 docs/evidence/v0436-release-smoke-2026-10-25.md diff --git a/docs/current-support-matrix.md b/docs/current-support-matrix.md index 6f7315e..a10bd20 100644 --- a/docs/current-support-matrix.md +++ b/docs/current-support-matrix.md @@ -4,7 +4,7 @@ Current for Frame Control **v0.4.36**, 25 October 2026. “Real Frame + physical | Feature | Real Frame + physical PC tested | VM only | Untested or limited | Last check and proof | |---|---|---|---|---| -| Core title smoke test | Linux lxso2 installed, launched and removed reserved native/Proton titles on the real Frame; all 13 steps passed | No | Unworn headset; visible rendering and controller input not checked. Other feature paths retain their separate limits below | 25 Oct, v0.4.31 candidate source `1255ef2`, Frame OS 0.5.6 build `20261022.6153909`: [sanitized results](evidence/round2-smoke-2026-10-25.json) | +| Core title smoke test | Linux lxso2 installed, launched and removed reserved native/Proton titles on the real Frame; all 13 steps passed | No | Unworn headset; visible rendering and controller input not checked. Other feature paths retain their separate limits below | 25 Oct, v0.4.36 tag `1701e62`, Frame OS 0.5.6 build `20261022.6153909`: [release smoke evidence](evidence/v0436-release-smoke-2026-10-25.md); [earlier detailed results](evidence/round2-smoke-2026-10-25.json) | | Windows desktop in the headset | No physical Windows PC test | Windows 11 VM sent a whole desktop to a real Frame; this used an intermediate fix, not the final native DLL | Physical GPU, capture and controller input; individual windows unavailable in bundled DXGI build | 24 Oct, v0.4.10 installer + candidate fix: [VM log](evidence/windows-vm-2026-10-24.md), [PC guide](pc-in-headset.md) | | Linux desktop in the headset | No | No | Native Linux PC capture is disabled; lxso2 lacked a desktop portal and PipeWire session. The separate Steam `-pipewire` helper is not Frame Control's PC capture | 24 Oct, v0.4.17: [host audit](evidence/linux-pc-host-lxso2-2026-10-24.md), [Steam helper PR #163](https://github.com/saphid/frame-control/pull/163) | | Mac desktop in the headset | A physical Mac sent its screen/window to a real Frame | No | Current v0.4.26 Mac installer and worn-headset controller input have not been repeated | 28 Sep, pre-v0.4 / Frame OS 0.4.1: [Mac guide and measurement](streaming.md#b-show-the-macs-desktop-inside-the-frame) | diff --git a/docs/evidence/v0436-release-smoke-2026-10-25.md b/docs/evidence/v0436-release-smoke-2026-10-25.md new file mode 100644 index 0000000..2474545 --- /dev/null +++ b/docs/evidence/v0436-release-smoke-2026-10-25.md @@ -0,0 +1,24 @@ +# v0.4.36 release smoke on a real Frame + +On 25 October 2026 at 22:59 UTC, the release branch ran +`scripts/frame-smoke.sh` from a physical Linux host against a real Steam Frame. +The script and its Python implementation were byte-identical to the +`v0.4.36` tag `1701e622dc1f9888560412a058fe816b19ca7e79`. +The headset reported Frame OS 0.5.6, build `20261022.6153909`. + +The test acquired `/tmp/frame-test.lock` with a unique owner marker before +reading device status or changing test titles. Its first read showed SteamVR +activity level 3 (standby), proximity raw 6.3125, and battery 99%. The test +ran only while that lock was owned. It released only its own marker and lock +after the final cleanup. + +All **13 of 13** smoke steps passed: cleanup of reserved leftovers, devkit +service read, status read, install/launch/remove for reserved ARM64, x86_64 +and Windows test titles, and final cleanup. The test did not pair a key. The +test output was saved locally under `/tmp/frame-v0436-smoke-results/`; this +summary omits the headset identifier and private device status fields. + +The headset was in standby. This test does not show wearer-visible game or +Framey pixels, controller input, live Decky settings, or plugin actions. +See [release v0.4.36](https://github.com/saphid/frame-control/releases/tag/v0.4.36) +for the tagged installer and checksum checks.