Merge pull request #305 from saphid/docs/framey-running-postmerge-vr

Document post-merge Framey running panel check

docs/evidence/framey-running-context-2026-10-26.md

@@ -76,3 +76,26 @@ missing/stale receipts are rejected before CEF after plugin replacement, and a
 reopened panel can poll and close with the new receipt. Rejected stale closes
 retain the tested finite-lease cleanup. This authorization-only follow-up did
 not repeat the device checks above; their recorded hardware scope is unchanged.
+
+## Post-merge unworn panel exercise
+
+On merged main `daee952873255b86018cce1d2a4d3bd070ec4341`,
+`scripts/framey-vr-check.py --exercise --output /tmp/framey-post304-exercise`
+acquired its own `/tmp/frame-test.lock` before any headset read. At 05:54 UTC,
+preflight found SteamVR activity 3 (standby), proximity 6.25 and battery 99%.
+The temporary sample panel passed the real Decky setting save and fresh-iframe
+reopen, a trusted synthetic OpenVR pointer, quick action, slider value 50 and
+CDP text entry after OpenVR focus. Stereo compositor SHA-256 changed from
+`50fcab1ee25e6d9398106cc0c24ec6616e07bcf4573b52be1774c715b756060b`
+to `98241806fb1f775e7f4c5ef0b0564bfd3c552ee896ff225b4d0cb5b7b53f70d1`;
+the `/dev/video99` mirror capture hash was
+`c284c05f86b60362168c1d1f58fe775974b70ac54bbfd57834802b892eb4509e`.
+The command exited 0 with `passed=true`. The original power values (`false` and
+`5.000000`) were read back, battery remained 99%, the recovery timer was removed,
+cleanup errors were empty and the run released only its own lock. The private
+full report is `/tmp/framey-post304-exercise/result.json` on the test host.
+
+This exercise covered the sample panel path after the running-context merge. It
+did not observe a nonempty running-game list, a game lifetime callback, Discord
+activity, a worn display or physical controller input. Synthetic native scroll
+again did not move (`scrollTop=0`, no wheel event).

docs/evidence/v0442-release-2026-10-26.md

@@ -1,62 +0,0 @@
-# v0.4.42 tagged release, 26 October 2026
-
-The annotated `v0.4.42` tag dereferences to main merge commit
-`98909cb54374a7bd7ec1f665f50eda20fa196f32` from PR #302. The app and
-lockfile both report 0.4.42. The [tagged release workflow](https://github.com/saphid/frame-control/actions/runs/40276685171)
-passed its draft, Linux, Windows, Apple Silicon Mac, Intel Mac and checksum jobs.
-The Linux job launched its built AppImage under isolated Xvfb. CI does not prove
-a physical Windows or Mac launch.
-
-## Real Frame, exact tag
-
-From an exact tag checkout, `scripts/frame-smoke.sh` acquired its own unique
-owner in `/tmp/frame-test.lock` before reading the headset. Preflight found
-SteamVR activity 3 (standby), proximity 6.25 and battery 100%. On Frame OS 0.5.6
-build `20261022.6153909`, it recorded **12 passed / 1 skipped / 0 failed** and
-exited 0. ARM64 and Proton test executables launched. The x86_64 title was
-installed and removed, but its launch was skipped because optional Steam Linux
-Runtime 4 was absent. Test title/process cleanup passed and only the run's lock
-was released. The private result is
-`tests/smoke/results/2026-10-26T055940Z-20261022.6153909.json` in the exact tag
-checkout.
-
-The separate [unworn Framey candidate exercise](v0442-candidate-2026-10-26.md)
-passed real sample setting save/reopen, synthetic OpenVR pointer delivery and
-stereo compositor change, with power restored and cleanup complete. It was run
-on the release branch's code before the evidence-only final commit. No person
-wore the Frame. Neither run verifies official plugin VR panels, physical
-controller usability, native scrolling, VR keyboard or optical comfort. The
-hourly worn check remains enabled.
-
-## Installer, checksum and updater checks
-
-The draft held ten installers plus `SHA256SUMS`, each with a GitHub SHA-256
-digest. `scripts/publish-release.sh --dry-run v0.4.42` checked the exact remote
-tag and every installer digest, regenerated the checksum list from those
-metadata digests, and matched the uploaded `SHA256SUMS` digest. A fresh
-checksum-list download independently matched
-`e5c85f5a46d789dccafae5259bd00b9b048dd10ca4f2a6cdc52d1f432a6db989`.
-
-A fresh Linux x86_64 AppImage download matched
-`16fc9fbe448bccbe59aa4206bc171c6bfc741973d2b4da0a79652a5c11d837b3`.
-`scripts/check-appimage-launch.py` launched those exact bytes under isolated
-Xvfb: the bundled server answered HTTP 200 with `FrameControl/1` and then
-stopped. Fresh Mac ZIP downloads matched GitHub digests: arm64
-`394d6088e732a19289b7b92366dd247f14f7293a345d57ed5c4e9c83a50abad3`
-and x64 `66d4606e38210d02af59dc87e4d1216282ad9e968056d7096f247fcc51e72395`.
-Both bundles report version 0.4.42; their main Mach-O CPU types are arm64 and
-x86_64 respectively. Neither tagged Mac ZIP was launched on a physical Mac.
-
-`scripts/publish-release.sh v0.4.42` published
-[v0.4.42](https://github.com/saphid/frame-control/releases/tag/v0.4.42) at
-2026-10-26 06:02:20 UTC. GitHub's latest-release API read back `draft=false`,
-`prerelease=false`, the expected tag, ten installers, `SHA256SUMS` and
-`update.json`. A fresh public latest-download of `update.json` parsed as
-version 0.4.42 with the stable release page and ten SHA-256 installer digests.
-The tag contains #299, #300, #301 and #303 through #302's release merge.
-#304 merged after the tag and is not in this release.
-
-The exact-version official Decky table for v0.4.42 is **3 works / 48 partial /
-54 broken / 11 N/A**. The two additional works labels are restricted to tested
-per-app silent-stream volume control. Audible playback and official-plugin
-worn VR remain unverified.