Release v1.0.0-alpha.4

[enaboapps]

Summary

• synchronize the application, startup launcher, browser fallback, configuration test, and lockfiles to 1.0.0-alpha.4
• preserve updater-feed fixtures, documentation examples, identities, protocols, schemas, and signing configuration
• prepare the signed prerelease after the merged Windows modifier-overlay fix

Validation

pm run lint

pm test (57 passed)

pm run build

• cargo fmt --manifest-path src-tauri/Cargo.toml --check
• cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
• cargo test --manifest-path src-tauri/Cargo.toml (133 passed)
• verified no 1.0.0-alpha.3 remains in shipping source/configuration

Closes #570

[greptile-apps]

Greptile Summary

Promotes Switchify PC release metadata to 1.0.0-alpha.4 across the desktop bundle, startup launcher, JavaScript package metadata, and browser fallback. The executed release-version check confirmed that all nine release-facing values agree.

Confidence Score: 5/5

No blocking failure remains.

No accepted blocking findings remain after confirming the release-facing version values are synchronized.

T-Rex Logs

What T-Rex did

• Ran a self-contained release-version validator against the merge-base and the current branch.
• The merge-base reported 1.0.0-alpha.3 in all nine release-facing sources, while the current branch reported 1.0.0-alpha.4 in all nine sources, including the browser fallback.
• Attempted the changed telemetry test; compilation stopped before execution because the host lacks the gdk-3.0 development package.
• Before capture, all nine sources consistently reported 1.0.0-alpha.3 at merge base. After capture, all nine sources consistently reported 1.0.0-alpha.4 in the PR working tree.
• Telemetry execution blocker is environmental, not a test failure: pkg-config cannot locate required gdk-3.0 >= 3.22.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into codex/release-v..." | Re-trigger Greptile}