Record v0.4.50 candidate gates and smoke limit

docs/evidence/v0450-candidate-2026-10-27.md

@@ -0,0 +1,33 @@
+# v0.4.50 candidate gate, 27 October 2026
+
+The version bump at `a160043` follows the merged Windows panel-response repair
+[#356](https://github.com/saphid/frame-control/pull/356) and the Framey changes
+[#353](https://github.com/saphid/frame-control/pull/353),
+[#354](https://github.com/saphid/frame-control/pull/354),
+[#355](https://github.com/saphid/frame-control/pull/355),
+[#357](https://github.com/saphid/frame-control/pull/357),
+[#358](https://github.com/saphid/frame-control/pull/358), and
+[#359](https://github.com/saphid/frame-control/pull/359).
+The exact DeckyFileServer catalog entry is **partial**; the shared Toggle fix
+does not promote any plugin status. Worn VR and physical controller behavior
+remain unverified.
+
+## Locked real Frame smoke
+
+The first `scripts/frame-smoke.sh` attempt from the version-bumped candidate
+exited **2** before any headset status read or test action: it could not acquire
+`/tmp/frame-test.lock` or reach the headset to acquire it. The runner left the
+existing lock untouched. This attempt supplies **no real Frame smoke result**.
+Retry on a later interval; record activity, proximity, battery, exact passed,
+skipped and failed counts, owned cleanup, and a separate locked cleanup audit
+before this candidate can merge or be released.
+
+## Remaining release gates
+
+The candidate needs green exact-head PR CI, e2e, native amd64/ARM64 Decky
+runtime checks and all four installer previews. After the candidate merges,
+its exact main commit needs green CI and e2e. The tagged release then needs
+every installer build, ten assets, matching checksums, release verification,
+independent package checks, publisher dry run and a successful locked real
+Frame smoke. A failed, cancelled, skipped, pending or unverified release gate
+holds publication. The current published release remains v0.4.49.