Fix portable WinUI startup and prepare 3.0.0-beta.2

[neko-no-otoko]

What changed

• regenerate the registration-free WinUI activation manifest immediately before every single-file publish
• fail release verification when the extracted-runtime loadFrom mappings are absent
• add an extracted single-file GUI smoke launch alongside the dark/light folder smoke tests
• keep portable data beside the original EXE rather than under the .NET extraction cache
• fix JSON serialization for scan, history, and service collections
• report the beta 2 version consistently and identify new WUA operations as PSWindowsUpdateGUI/3
• map malformed WUA criteria to the documented validation exit code and a useful structured error

Why

The beta 1 release could reuse a stale folder-build manifest during publish. That manifest lacked the loadFrom mappings required after bundled Windows App SDK files were extracted, causing WinUI activation failures (0x80040111) before the first window appeared.

User impact

The portable single EXE now starts without installing the Windows App Runtime, preserves settings beside the downloaded executable, and returns usable JSON from the read-only CLI commands.

Validation

• Release x64 build: 0 warnings, 0 errors
• Unit tests: 27 passed
• dotnet format --verify-no-changes
• folder GUI smoke: light Updates and dark History & Status
• extracted single-file GUI smoke: dark History & Status
• production manifest verification
• live local WUA: status, history, registered services, software scan, and driver scan
• selected Intel driver install/hide previews by GUID and revision
• malformed criteria: HRESULT 0x80240032, CLI exit code 2