Release v1.0.0-alpha.5

[enaboapps]

Summary

• synchronize the application, launcher, browser fallback, configuration test, and lockfile versions at 1.0.0-alpha.5
• leave generic updater-feed fixtures and documentation examples unchanged
• prepare the signed Alpha 5 prerelease containing the Windows modifier-overlay repair

Closes #575

Validation

• Node.js v24.13.0
• Rust 1.97.1
• npm run lint
• npm test (57 frontend tests and 5 update-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 (133 unit tests and 2 configuration tests)

[greptile-apps]

Greptile Summary

This change promotes the application release to 1.0.0-alpha.5 across the npm package, browser fallback, Tauri application, startup launcher, lockfiles, and configuration assertion.

The release consistency check passed against both the prior release and this change. All ten checked version values, including package and Cargo lockfile entries and the browser fallback state, match their expected release value.

T-Rex validation blocked

The native Tauri configuration test could not compile because the Linux environment is missing the GDK 3 development package metadata (gdk-3.0.pc) required by the desktop dependency stack.

Confidence Score: 5/5

The release metadata is consistently synchronized and is safe to merge.

The executable release consistency check passed for the previous and promoted versions, with no defects found.

Files Needing Attention: No changed file requires follow-up. The native Tauri configuration test should be rerun in an environment with GDK 3 development libraries when available.

T-Rex Logs

What T-Rex did

• The release-version consistency checker was executed against HEAD^ 1.0.0-alpha.4 and HEAD 1.0.0-alpha.5; both runs exited with status 0, and the promoted-release validation passed all ten assertions.
• A native Tauri config test attempt was blocked by a missing GDK 3 development package (gdk-3.0.pc) in PKG_CONFIG_PATH on this Linux runner, so cargo test could not compile.
• A follow-up validation after the PR also passed all ten assertions.

_{Ran code and verified through T-Rex}

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