release: Build and validate the Windows ARM64 beta package

[zackees]

Fixes #629. Refs #635 and #627.

Changes

• Build Windows ARM64 using the existing Windows toolchain, install aarch64-pc-windows-msvc, collect its actual target-specific zip, and require that asset before any release publication.
• Add verify_only manual dispatch to the existing release workflow. It runs the same production builds, packaging, and full gate for a candidate ref while refusing both normal and continuous publication; existing master/date/repair guards remain in normal mode.
• Pass rust_libobs: true explicitly to called AppImage builds. A manual parent dispatch previously inherited workflow_dispatch without this input and could silently build a C-only AppImage.
• Run the exact ARM64 zip on a native Windows ARM64 runner, verify the frontend PE machine, and reload a saved profile containing screen, camera, and microphone sources. Authenticate to the live websocket, check registered capture kinds and selected profile/scene/source items, obtain PNG and JPEG screenshots with matching MIME/image signatures, and close only the owned frontend cleanly.
• Remove the real packaged win-dshow.dll and require startup validation to fail specifically for missing dshow_input, then accept that expected failure explicitly in the Actions PowerShell wrapper. Publication requires the native job to succeed.
• Refuse any existing config and any fixture path other than the frontend's actual platform config path; always clean the owned fixture after the child exits.

Hosted runners have no physical camera/microphone devices. The runtime test proves plugin registration, package loading, saved-profile state, rendering/codecs, and clean startup/shutdown; it does not claim captured physical camera/microphone frames.

RED → GREEN

• 9799b8af0: four failures for the missing ARM64 matrix, collector and required asset.

• 290139593: missing Rust ARM64 standard-library provisioning.

• 8d0e2a0e2: nonpublishing verification absent (one failure, three errors).

• e5c045a4f: two failures for manual called AppImage Rust selection.

• 005db2526: missing native saved-profile gate.

• 160003400: wrong config roots accepted (missing validator).
  The corresponding GREEN commits pass the focused suite. The native mutation is part of the release workflow, not simulated by a fixture-only unit test.

• f1bd4cc57: two failures executing the actual package action argument builder with PowerShell 7.6.5: x64 splats --run into characters; cross-built ARM64 supplies --expect-version without --run. 60f244fa2 fixes both; ARM64 runtime version checking runs on the native ARM runner.

• Actual production candidate run 38492393948 compiled all four desktop targets, then failed the Windows argument builder and macOS DMG volume-reader checks. db70a2bbc fixes the latter using a regular plist file while retaining the VolumeName assertion. A new candidate run is required.

Validation

145 CI Python tests pass (one environment skip); focused real PowerShell regression and integration review are clean. Mandatory lint/unit pass: OFF/ON CTest each reports zero failures out of 192 (environment skips retained), with 1766 identical exports. Fresh attestation passed all four lanes in 397 seconds at 737edb6aad1d (tree fd3951b26af2) after rebasing onto master 0a50b7cf3 and resolving #666's overlapping verifier changes. The stamped head is pushed unchanged.

The exact published head passed complete production verification in 38500142290. All desktop packages, the full platform gate, and the AppImage tests on Arch/Debian/Fedora/Ubuntu pass. Native Windows ARM64 job 115654578226 verifies the PE machine/version, reloads the saved screen/camera/microphone profile, validates PNG/JPEG screenshots and clean shutdown, then rejects the same package after deleting its real win-dshow.dll. The run completed SUCCESS; verification publishes no release. All PR checks are terminal with no failures.

The separate absent-AppImage-input regression found in merged #670 is being transferred to its own PR, with actual GitHub-engine RED/GREEN already committed locally. It is not included in this validated platform head. The primary checkout has been rebased after later master merges.

The direct MIME include prerequisite landed in #660 with obs-rust/obs-websocket#10. This PR now targets master. #660's known Windows Tier 2 allocation-count failure remains tracked in #663; it is not being treated as a successful gate.

[zackees]

The exact stamped head d99adec is now running the existing production release workflow with verify_only=true: https://github.com/obs-rust/obs-studio/actions/runs/38492393948 . This run cannot publish normal or continuous releases. Native ARM64 saved-profile startup and the real removed-camera-module negative test remain pending. The Windows allocation-count failure tracked in #663 is also a known release-gate risk; it will not be waived if reproduced.

[zackees]

First actual verification run38492393948 is terminal FAILED, with concrete verifier regressions exposed after compilation/package success. Mac arm64 and Intel fail because PlistBuddy cannot parse the /dev/stdin pipe (jobs115620499528/629); the regular-file reader fix is prepared. Windows x64 fails with unrecognized arguments - - r u n (job115620499557): PowerShell unrolls the one-element array emitted by if, so splatting the scalar string splits it into characters. Windows ARM64 fails --expect-version needs --run (job115620499521): the x64 build host cannot execute that package, so version verification must happen in the native ARM64 job. These native failures are RED evidence; the next candidate will keep all validation requirements and fix their execution paths.

[zackees]

Replaced head d99adec with stamped 99ce02d, rebased onto master db559d9 after #660 and #658 merged. Fresh ./lint, ./unittest and all four attestation lanes pass (454 seconds, tree2555ce25ebed; OFF/ON zero failures out of192, 1766 identical exports).

The actual failed package run38492393948 exposed the Windows argument and macOS volume-reader errors. Real PowerShell RED4f8eebb7b has two failing target cases; GREEN1ca800202 builds a proper argument array and moves ARM64 runtime version validation to the native ARM runner. The DMG reader now uses a regular plist file with the original strict VolumeName check. Native smoke runs despite an unrelated matrix failure, while publication still requires all platform builds and native validation.

Dispatching a fresh verify_only production package run at this exact repaired head. PR remains draft until actual native evidence is recorded. #663 is a separate known Windows Tier2 startup race, with #667 now open; its failure is not waived.

[zackees]

Replaced head 99ce02d with stamped 737edb6 after rebasing onto master 0a50b7c (#666/#654). The overlap preserves the real-tested argument array, static ARM cross checks plus native runtime version checks, and the regular-file DMG reader. The new pattern test caught only the explanatory comment; rewording it gives focused RED 1 → GREEN 12 without changing the command.

Fresh ./lint, ./unittest and all four attestation lanes pass (397 seconds, tree fd3951b26af2). The complete CI Python suite passes 145 tests with one environment skip; review is clean. The older immutable native run 38497908870 remains live; both macOS collection jobs passed and Apple Silicon printed the correct Rust beta version. Those results are historical evidence, not validation of this rebased head. Native Windows startup and new-head package verification remain required; this stays draft.