saphid--frame-control/docs/current-support-matrix.md

What we have tested

Release baseline: Frame Control v0.4.40, 26 October 2026. Rows also identify verified post-release main changes explicitly. “Real Frame + physical PC” means an actual headset and a non-virtual computer. “VM only” means a Windows virtual machine, sometimes connected to the real Frame. A CI test or a simulated device is not a physical hardware test. The date/version column is the last relevant check, not a promise that every new release was retested on that platform. See each link for the exact procedure and limits.

Feature	Real Frame + physical PC tested	VM only	Untested or limited	Last check and proof
Mac desktop release — tested on a real Mac	Physical MacBook Air (MacBookAir9,1), Intel Core i3, macOS 15.7.7 (24G720): official v0.4.39 x64 DMG verified, installed and launched. Native UI, preference persistence across restart (original file restored), bundled Python logs, update check, offline OBS Start/Stop and 116-entry Decky store checked. A 40-byte relay upload/readback/delete passed under coordinator/headset locks	No	No quarantined Safari/Chrome download or Gatekeeper override test; native Open at Login/menu automation unavailable. Direct frame.local had no route and the app refused a stale SSH identity. Relay transfer is not native Mac transfer acceptance. Real OBS/Framey VR unverified. Quit exposed a server cleanup race; fix #284 shipped in v0.4.40 with physical-Mac source regression coverage, but the tagged Intel installer was not launched on physical Intel hardware	26 Oct, official v0.4.39 tag fd0b0a9: Intel release evidence; earlier ARM64 failure
Core title smoke test	Linux lxso2 ran the exact v0.4.40 tagged source against the real Frame; all 13 reserved native/Proton title steps passed and cleanup completed	No	The headset was unworn; visible rendering and controller input were not checked. Other feature paths retain their separate limits below	26 Oct, exact v0.4.40 tag a4d8073, Frame OS 0.5.6 build 20261022.6153909: tagged release evidence; earlier candidate smoke
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, PC guide
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, Steam helper PR #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
OBS headset source on Linux	Real Frame to OBS 30.0.2 on a Linux host: 187.367 s, 720p30 H.264/AAC stereo, 5,621 frames, no encoder skips; room passthrough appeared in the recording	No	Synthetic tone was measured, not real game audio or audible listening. Default audio led by about 0.43 s in this setup; a measured +480 ms OBS offset removed residual skew at test resolution. Source-image latency was 1.431 s in one trial; other hosts and long sessions are unverified	25 Oct, v0.4.30 package plus PR #219 runtime: validation
OBS headset source on Windows	No physical Windows PC test	Windows 11 VM helper fixture passed, but a native bridge to the real Frame sent no packets	In-app OBS controls remain hidden; native Windows OBS and firewall path are unverified	25 Oct, PR #219: validation, OBS guide
OBS headset source on macOS	Physical Intel Air: official v0.4.39 native Start/Stop returned to idle offline	No	Real headset stream, OBS receiver and audio/video remain unverified; the app rejected its stale SSH identity	26 Oct, v0.4.39: Mac evidence, OBS guide
OBS headset source on a SteamOS / Steam Machine PC	No SteamOS PC or Flatpak OBS runtime test	No SteamOS host VM test	v0.4.27 AppImage launched on Ubuntu x86_64 under Xvfb; the helper sent H.264/AAC from a real Frame to a local UDP receiver. SteamOS read-only root, desktop UI and Flatpak OBS remain unverified	25 Oct, v0.4.27: host test, OBS guide
Wired connection doctor	No physical PC/Frame cable test of the doctor	No	Synthetic route/SSH tests; a separate Mac USB-C address observation does not test the doctor or game stream	25 Oct, v0.4.23: PR #178, wired guide
Windows Wireless Adapter doctor	No physical Steam Wireless Adapter/dropout test	Windows 11 VM ran read-only checks without the adapter or WLAN	Adapter identification, dropouts and recovery on hardware	24–25 Oct, v0.4.20–0.4.25: VM log, doctor guide, comparison PR #184
Linux Wireless Adapter doctor	No Steam Wireless Adapter hardware test	No	Read-only Linux host checks and mocked adapter states; no adapter-specific hardware observation	24 Oct, v0.4.20: PR #165, doctor guide
Switch PC windows	No physical Windows PC test	No real VM-to-Frame Alt+Tab check recorded	Explicit chord is covered by tests; actual window focus, keyboard layouts and controller interaction are unverified	25 Oct, v0.4.24: PR #181, PC guide
Keyboard and trackpad from Frame Control	A Linux PC sent a click and ASCII keys to a temporary focused window on the real Frame	No	Worn-headset interaction, Unicode delivery and pixel-accurate pointing	24 Oct, v0.4.19: received-event log, PR #66
Backup and restore after reset	Same-headset backup, no-op save restore and Return to Game Mode checks	No	Restore after a factory reset, replacement restore and Android data restore have not been tested on a headset. No headset reset was done	24 Oct, v0.4.17: backup guide, Return to Game Mode log
Android game backup import	F-Droid Basic APK with synthetic main and patch OBBs installed, transferred and read back on a real Frame	No	v0.4.30 restricted split-APK backup route has generated-fixture and existing merger tests only; no real split game or RE4 gameplay test	20 Oct OBB headset check; 25 Oct, v0.4.30 split fixtures: OBB device evidence, split PR #206, guide
Passthrough in recordings	Real room pixels in OBS and a production MP4 after safe SteamVR wake	No	Yes for the checked 0.5.6 mirror. Raw cameras are not opened. Other games/modes and Steam clips may differ	25 Oct: validation, recording guide
Open at login	No Frame needed; Linux autostart file toggled on a physical Linux host with an isolated config directory	No	A full login session and physical Windows/macOS host login have not been checked; OS API calls were unit tested	25 Oct, v0.4.26: PR #189
Local Frame Control extensions	Example panel displayed live Frame status in a browser preview; the real Frame served a read-only example in the experimental headset panel	No	No wearer-visible extension view; third-party extensions and physical Windows/macOS extension folders untested	25 Oct, v0.4.29: PR #194, PR #201, extension guide
Experimental Frame Control SteamVR panel	Frame OS 0.5.6 registered and served the opt-in overlay. A later unattended check safely woke SteamVR and found the panel in stereo compositor and mirror captures; it removed its temporary service and restored power settings	No	No person wore the headset for that check. Physical controller input, scrolling, VR keyboard, comfort and legibility remain unverified. The large status view has browser and packaging checks, not a wearer review	26 Oct, v0.4.29–0.4.40: panel PR #201, unattended evidence, post-#292 unworn sample exercise, earlier standby-gated exercise, worn checklist
Experimental Decky Loader manager	Frame OS 0.5.6 ARM64 user-service install/status/update/remove and managed ProtonDB install/update/remove passed earlier. A private Decky 3.3.0 service returned read-only ProtonDB and Steam Status setting RPCs; a later locked check verified the official Notebook default drawing/save/reopen flow and Simple Timer backend events in local Chromium	No	The loader remains opt-in. Installs/updates reject an archive whose Decky name collides with another installed plugin before download and under the headset transaction lock; this safety path has host/fake Frame tests, not a new real-headset collision test. v0.4.40 classifies the 116 exact-version plugins as 1 works (Notebook default flow only), 49 partial, 55 broken and 11 not applicable. Post-tag PR #289 changes TabMaster to partial, giving 1/50/54/11 on current main; #293 audio evidence is still in CI. Deck Shelves moved to partial after its exact chunked frontend rendered settings in local Chromium; its backend and Steam Home shelves remain unverified. Steamback, PlayTime and Deck Settings became partial after detached read-only library/user snapshots and isolated amd64 backend checks; their official ARM64 backends, automatic behavior and VR panels remain unverified. A read-only Steam bridge returned the Frame country, install folders and system information; IsThereAnyDeal selected that country in local Chromium, but its deployed HTTP endpoint and deal lookup remain unverified. An isolated ARM64 LocalSend core answered its info endpoint, but the official x86-only plugin archive and file transfers remain blocked. Three official audio plugins had local real-backend controls and independent virtual-audio readbacks, but their ARM64 Frame audio sessions and physical output remain unverified. Most official backends and VR controls remain unverified. Physical controller use and wearer-visible official panels remain unverified	26 Oct, v0.4.31–0.4.40: managed store PR #208, name-collision PR #269, catalog PR #266, backend event evidence, Steam read PR #274, LocalSend evidence PR #275, local audio evidence, post-release library evidence, compatibility table
Experimental Framey VR plugin panels and store	Unattended Frame OS 0.5.6 runs showed the Framey sample panel in stereo compositor and mirror captures. The latest standby-gated exercise restored the original power settings and released its shared lock. Synthetic OpenVR clicks changed a live sample setting, read its Decky backend file and confirmed it after a fresh iframe reopen	No	This was the repository sample, not an official store plugin. Physical controllers, native scrolling, VR keyboard, wearer comfort and legibility remain unverified. CSS Loader and SteamGridDB exact archives passed fake Frame install/remove and panel packing; this does not establish theme or artwork controls in VR. Panel-local backend events and React toasts have local/real-backend checks, but no wearer review. Pause Games and Tailscale Control settings render in local Chromium; their live actions are unverified. The 116-plugin catalog had 60 fake installs/removals and 56 expected blocks; v0.4.40 recorded 101 local Chromium initializers ready and 15 failed, up from 98/18 in v0.4.39. Notebook is marked works only for its default drawing/save/reopen flow	26 Oct, v0.4.38–0.4.40: post-#294 unworn sample and scroll evidence, backend event PR #270, settings/cache PR #271, post-release sample exercise, worn checklist

Release notes must preserve these limits until a newer recorded check changes them. When a feature is retested, add its date, exact app/Frame version, host type and proof here. The older v0.3.1 matrix is a historical snapshot and does not describe current coverage.