chore: prepare v1.0.0-rc.6

[enaboapps]

Prepare the v1.0.0-rc.6 prerelease containing the Controls and Cursor appearance settings labels from #707. Synchronize the application, startup launcher, lockfiles, browser sample version, and configuration assertion.

Closes #708

Validation on Node.js 24.13.0 and Rust 1.97.1:

• npm run lint, npm test, and npm run build passed. 108 UI/API tests and 5 update-feed tests passed.
• cargo fmt --manifest-path src-tauri/Cargo.toml --check and cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings passed.
• cargo test --manifest-path src-tauri/Cargo.toml passed with 270 tests. Independent agent review of c7fdee1 found no actionable issues. Required CI must pass before merging.

After merge, push an annotated v1.0.0-rc.6 tag to run the existing signed release workflow, then verify the prerelease assets and dedicated updater feed.

[greptile-apps]

Greptile Summary

This change promotes Switchify PC from 1.0.0-rc.5 to 1.0.0-rc.6 across the npm package, Tauri application, Windows startup launcher, browser sample state, lockfiles, and configuration assertion.

The release-version consistency hypothesis was disproved: a production frontend build completed successfully, the browser sample-state test passed, both locked Cargo manifests resolved successfully, and the built frontend plus all nine version-bearing sources consistently reported 1.0.0-rc.6 with no remaining rc.5 version string.

No defects were found. Safe to merge.

Confidence Score: 5/5

The release metadata is consistent across the application manifests, launcher, configuration, browser state, lockfiles, and production frontend output.

No publishable findings remain after exercising the release build, browser-visible version path, and locked Rust package metadata.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• Built the baseline and updated frontend artifacts, exercised the browser sample-state test, and parsed the locked Cargo metadata for the main application and startup launcher, while preparing a reproducible metadata and artifact validator.
• Validated that the baseline state reported 1.0.0-rc.5 and the changed revision reported 1.0.0-rc.6 across nine metadata/runtime sources and four built browser files, with rc.5 no longer present in the production frontend artifact.
• Uploaded the reproducible release-version validation script source and captured its execution results for review.
• Release-version validation logs show the after-change state reports 1.0.0-rc.6 and the validation completed with a pass.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore: prepare v1.0.0-rc.6" | Re-trigger Greptile}