chore: prepare beta.24 internal release

[enaboapps]

Closes #158

Summary

• Prepare 1.0.0-beta.24 with shared Android/iOS build ordinal 26; marketing version remains 1.0.0.
• Depends on chore: align Expo SDK 57 patch dependencies #156 and feat: support negotiated Linux read replies #157, which must merge first. Includes the optional Linux read-v1 phone transport; PC work remains on linux-support.
• Internal Play/TestFlight prerelease only. Physical Linux pairing/input qualification remains outstanding.

Validation

• npm run validate: lint, types, 580 tests, version checks and Expo Doctor 21/21 passed.
• Independent latest-head release review and CI required before merge and publication.

[enaboapps]

Independent latest-head release review completed at 2057d57: no actionable findings. Reviewer verified the three-file beta.24/build 26 bump, unchanged marketing/native identity/signing configuration, version/history validation and 21 versioning tests. Local full validation passed (580 tests, Expo Doctor 21/21). Merge remains gated on green CI and prerequisite merges #156 then #157; publish only an internal prerelease from the merged main commit.

[greptile-apps]

Greptile Summary

Summary

• Adds negotiated BLE read-v1 response handling for compatible Linux peers while retaining notification responses for existing peers.
• Adds bounded serial response polling with validation, readiness, cancellation, and reconnect-required failure handling.
• Updates release metadata and Expo SDK patch dependency alignment for the beta release.

Confidence Score: 5/5

Safe to merge: the negotiated response path establishes readiness after an empty read, delivers later frames, and does not register the legacy notification transport.

No issues were found. The focused transport flow and repository transport tests completed successfully.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• Compared the transport behavior before and after the change using the same negotiated Linux read-v1 peer harness.
• In the updated revision, the harness connected, subscribed, achieved readiness after an empty read, delivered a later response frame, and confirmed that legacy transmit monitoring was not used.
• The focused repository transport suites completed with 74 passing tests across 3 suites.
• Before baseline, the exact harness passed on bde491b, proving the pre-PR transport selected the legacy notification route.
• After PR, the exact harness and focused transport suites passed, proving read-v1 readiness after an empty read and non-empty response delivery without transmit monitoring.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore: prepare beta.24 internal release" | Re-trigger Greptile}

[enaboapps]

All checks now pass at reviewed head 2057d57: full validation, Android build, iOS build and Greptile review. Independent agent review had no actionable findings. Dependencies #156 and #157 have merged and been pulled; local main-to-release diff is exactly the three version files. Proceeding with the user-authorized internal prerelease.

[enaboapps]

Release completed: https://github.com/switchifyapp/switchify-remote/releases/tag/v1.0.0-beta.24

Published prerelease from main merge commit 2fed7e1; local main pulled and clean. Version 1.0.0-beta.24, shared build 26.

Both internal-store workflows succeeded:

• Play internal: https://github.com/switchifyapp/switchify-remote/actions/runs/34643054374
• TestFlight internal (upload and App Store Connect validation passed): https://github.com/switchifyapp/switchify-remote/actions/runs/34643054447

PC stack remains unmerged on linux-support. Supervised Linux physical pairing/input validation remains outstanding.