Prepare v1.0.0-alpha.3 release

[enaboapps]

Closes #566

Summary

• synchronize the application, launcher, browser fallback, configuration assertion, and lockfiles to 1.0.0-alpha.3
• retain the existing application identity, updater feed format, and prerelease behavior
• include the merged macOS updater cleanup repair from Fix macOS updater cleanup dispatch #565

Validation

• Node.js 24.13.0; Rust 1.97.1
• npm run lint
• npm test (55 frontend tests and 5 feed tests)
• npm 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 (129 unit tests and 2 configuration tests)

Release verification

After merge, publish annotated tag v1.0.0-alpha.3, verify both signed platform packages and the updater feed, exercise Windows Alpha 2 to Alpha 3 in-app installation, and manually bootstrap the notarized DMG on macOS because Alpha 1/2 cannot install this fix through their broken updater.

[greptile-apps]

Greptile Summary

Promotes the desktop release identity from 1.0.0-alpha.2 to 1.0.0-alpha.3 in npm metadata, the browser fallback, Tauri packaging configuration, and both Rust packages.

No defects were found. The potential version-mismatch failure was disproved by an executed consistency check: all nine release-version sources, including both Cargo lockfile package entries, report 1.0.0-alpha.3. The frontend API test passed, and Cargo metadata resolved the primary package at the promoted version.

T-Rex validation blocked

The Rust configuration integration test could not compile because the Linux environment is missing the gdk-3.0 system package required by the Tauri dependency chain. This prevented that test from starting; Cargo metadata still resolved the main crate successfully.

Confidence Score: 5/5

The version promotion is consistent across the application surfaces and package metadata checked, with no release-labeling defect found.

The executed validator verified every changed version-bearing source and matching lockfile entries, while the frontend API test and Cargo metadata check passed. The unavailable Linux GUI dependency prevented one Rust integration test from compiling but does not contradict the completed checks.

Files Needing Attention: No changed file needs corrective action. The Rust configuration test can be rerun on an environment with the gdk-3.0 system package installed.

T-Rex Logs

What T-Rex did

• Ran the self-contained release-version consistency validator against both the parent revision and the PR revision, and observed a version bump from 1.0.0-alpha.2 to 1.0.0-alpha.3 across nine sources including the Cargo lockfile.
• Executed Vitest tests for src/api.test.ts and all five tests passed.
• Fetched Cargo metadata for the Tauri crate and confirmed it resolved switchify-pc@1.0.0-alpha.3.
• Attempted cargo test --test config but the run could not proceed because gdk-3.0 is not installed in the Linux environment.
• Captured validator usage and before/after state evidence, noting that HEAD^ had nine sources at 1.0.0-alpha.2 and HEAD had nine sources at 1.0.0-alpha.3, with runtime/configuration evidence from frontend tests and metadata; the Rust integration-test attempt is retained for traceability.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Prepare v1.0.0-alpha.3 release" | Re-trigger Greptile}