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

What we have tested

Current published release: Frame Control v0.4.52, 28 October 2026. Rows identify the last direct check of each feature; an older row does not mean the latest installer was retested on that hardware. “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. 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 and ZIP hashes/architectures verified; clean DMG app installed and launched. Native UI, preferences across restart, update discovery of 0.4.40, offline OBS Start/Stop and 116-entry Decky store checked. Actual Open at Login menu toggled on, persisted across Quit/relaunch, then restored off. A 54-byte relay upload/readback/delete passed under coordinator/headset locks	No	Ordinary browser quarantine, right-click Open and Open Anyway remain unverified; the synthetic quarantine probe was inconclusive. Actual login startup untested. Direct frame.local had no route and app SSH trust failed; relay transfer is not native Mac transfer acceptance. Real OBS/Framey VR unverified. Earlier shutdown race fix #284 shipped in v0.4.40, whose Intel installer was not tested here	26 Oct, official v0.4.39 tag fd0b0a9: repeat Intel acceptance evidence; earlier release test
Core title smoke test	A Linux host ran the v0.4.52 versioned source candidate, whose tree matches the tagged release commit, against the real Frame under a unique lock: 12 steps passed, one optional x86_64 launch was skipped, zero failed; a separate locked cleanup audit passed	No	The headset was in standby and unworn. Steam Linux Runtime 4 was absent, so the x86_64 test executable did not launch. Worn rendering and physical-controller input were not checked	28 Oct, v0.4.52 tag v0.4.52, Frame OS 0.5.6 build 20261022.6153909: release verification, 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; official v0.4.39 on the physical Intel Air toggled the actual native menu on, retained its checkmark after Quit/relaunch and restored it off. Linux autostart file previously toggled on a physical Linux host with an isolated config directory	No	A full OS login session and physical Windows host login remain untested	26 Oct, v0.4.39: native Intel toggle evidence; Linux 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	Earlier real Frame checks passed opt-in ARM64 user-service install/status/update/remove and managed ProtonDB install/update/remove. The current exact-version catalog records six scoped works: Notebook default drawing, Volume Mixer and Mixer silent per-app volume, Volume Boost muted sink controls, DeckySpy metrics, and Simple Timer silent in-panel timers	No	v0.4.52 classifies 116 exact-version plugins as 6 works / 54 partial / 45 broken / 11 N/A. “Works” applies only to each documented behavior, never worn VR. Network Sentinel and Battery Tracker are partial; their managed real-Frame ARM64 behavior is unverified. Most other backends, audible output, physical-controller use and wearer-visible official panels remain unverified	28 Oct, v0.4.52: exact-version table, release verification, DeckySpy evidence, Simple Timer evidence, audio evidence
Experimental Framey VR plugin panels and store	An unattended Frame OS 0.5.6 exercise showed the repository sample panel in stereo compositor and mirror captures. Synthetic OpenVR clicks changed a live sample setting, read its Decky backend file, and confirmed it after a fresh iframe reopen; temporary services were removed and original power settings restored	No	This was the repository sample, not an official store plugin. Physical controllers, native scrolling, VR keyboard, wearer comfort and legibility remain unverified. Fake-Frame install/remove and local Chromium plugin initialization do not prove an official plugin is visible or usable in worn VR	28 Oct, v0.4.52 catalog with earlier 25–26 Oct VR evidence: unattended sample evidence, compatibility table, 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.