fix: deliver Stop movement commands

[enaboapps]

Closes #117

Summary

• send every mouse.repeat.stop command in acknowledged mode accepted by Switchify PC
• clear local repeat state once, then prioritize PC delivery before Android bridge deactivation
• preserve serialized stop/start ordering across the button, other controls, physical switches, cleanup, and session replacement

Validation

• npm run validate
  • 49 test suites passed
  • 396 tests passed
  • Expo Doctor 21/21 checks passed
• Physical Windows, macOS, Android, and iOS repeat-stop checks remain to be completed

No PC, protocol schema, BLE identifier, storage, dependency, permission, or native configuration changes.

[enaboapps]

Latest-head update (9b4ac32):\n\n- Resolved the independent review finding by reserving the stop and clearing the local repeat state synchronously at the stopRepeat() call boundary.\n- Preserved serialized ordering: repeat start completes, the acknowledged PC stop is attempted, then Android bridge deactivation runs.\n- Added regression coverage for a stop requested while bridge activation is pending, including a duplicate stop.\n- Full local validation:
pm run validate — 49 suites / 397 tests passed; Expo Doctor 21/21.\n- Focused validation: 3 suites / 75 tests passed.\n- git diff --check passed.\n- Independent re-review of exact head 9b4ac32: no actionable findings.\n\nPhysical Android/iOS and Windows/macOS hardware checks remain for manual verification.

[enaboapps]

Latest-head CI is green for 9b4ac32:\n\n- validate: passed\n- native-projects (Android): passed\n- native-projects (iOS): passed\n\nImplementation remains in draft and unmerged pending explicit approval.