Prepare v1.0.0-alpha.1 release

[enaboapps]

Closes #554.

What changed

• synchronizes the application, startup launcher, browser fallback, configuration assertion, and lockfile versions to 1.0.0-alpha.1
• leaves generic beta updater-feed fixtures and release documentation examples unchanged
• prepares the exact source version required by tag v1.0.0-alpha.1

There are no public API, protocol, persisted-schema, application-identity, or updater-feed format changes.

Validation

• npm run lint
• npm test — 45 frontend tests and 4 release-feed tests passed
• 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 native unit tests and 2 configuration tests passed

Validated with Node.js 24.13.0 and Rust 1.97.1.

[greptile-apps]

Greptile Summary

Synchronizes the release version to 1.0.0-alpha.1 across the frontend package and lockfile, native application and lockfile, startup launcher and lockfile, Tauri configuration, browser fallback state, and configuration assertion.

An executable consistency check exercised all ten release-version surfaces and confirmed that each reports 1.0.0-alpha.1 with no retained 1.0.0-beta.1 value. The frontend and update-feed test suite passed with 49 tests. This disproves the release-metadata mismatch hypothesis.

T-Rex validation blocked

The native configuration test could not compile because the environment is missing the gdk-3.0 system development package and its pkg-config metadata (gdk-3.0.pc).

Confidence Score: 5/5

No release-version defect was found in the modified application metadata, and the tested frontend behavior remains healthy.

The focused validator checked every changed release-version surface against the intended alpha version, including manifests, lockfiles, Tauri configuration, browser fallback state, and the Rust configuration assertion. It passed at the proposed revision, while the equivalent parent revision failed the alpha-version expectation. The frontend and update-feed test suite also passed.

Files Needing Attention: No changed file requires follow-up. Native configuration execution remains unavailable in this environment until the gdk-3.0 development package is installed.

T-Rex Logs

What T-Rex did

• Ran the release-version-consistency validator against the archived parent revision and the PR head; it showed the parent retained the beta version and failed the alpha-release expectation, while the PR head passed all ten metadata checks.
• Validated frontend health by running npm test -- --run and confirmed all 49 tests passed under 1.0.0-alpha.1.
• Attempted cargo test --manifest-path src-tauri/Cargo.toml --test config; compilation halted due to missing gdk-3.0.pc in the environment.
• Environment limitation blocks native configuration validation because the system lacks the gdk-3.0 development package and its pkg-config metadata.

_{Ran code and verified through T-Rex}

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