[Watch] 7 - Control Board Move

[KacperKozak]

What to build

Relay wrist hold/release intent to existing native iOS Board Move actions. The phone owns strength, link checks, firmware constraints and a dead-man timeout.

Source: docs/watchos.md and the approved watchOS parity plan. Execution: AFK, with integrated hardware validation in slice 8.

Likely files

• watch/wearos/src/main/java/app/vescape/wear/MoveScreen.kt — existing Wear OS behavior or wire-contract peer.
• watch/wearos/src/main/java/app/vescape/wear/WatchCommand.kt — existing Wear OS behavior or wire-contract peer.
• modules/vescape-core/android/src/main/java/expo/modules/vescapecore/watch/WatchMoveRelay.kt — existing Android phone-side parity peer.
• modules/vescape-core/ios/BoardMoveController.swift — existing native iOS integration or test starting point.
• modules/vescape-core/ios/BoardMoveControllerTests.swift — existing native iOS integration or test starting point.
• modules/vescape-core/ios/connection/BoardSessionController.swift — existing native iOS integration or test starting point.

Implementation hints

Read current Android code, not historical alert-forwarding docs. Keep native phone truth and actions in vescape-core; do not make live wrist behavior depend on JS. Add bidirectional @parity links for equivalent contracts/logic and document verified platform differences in docs/watchos.md. New durable watch source belongs under watch/watchos/, not generated ios/. The local planning document will be included in the draft watchOS feature PR; this issue includes its relevant requirements independently.

Acceptance criteria

• Match Android direction-only commands, 300 ms hold ticks and 900 ms phone-side timeout, with immediate stop on release.
• Lost release, app exit, watch death and connectivity loss stop movement through the phone-side timeout.
• Do not queue stale holds through deferred background transfer; stop supersedes pending holds and reconnect never resumes an old hold.
• Move is unavailable on stale/missing telemetry; phone-configured strength and existing Board Move safety gates remain authoritative.
• Test delayed/lost/reordered delivery and timeout using deterministic fixtures before any motor movement.

Blocked by

• [Watch] 2 - Adapt gauges and navigation #485
• [Watch] 3 - Mirror watch settings #486

Related

• [Watch] 1 - Set up watch app #484
• [Watch] 2 - Adapt gauges and navigation #485
• [Watch] 3 - Mirror watch settings #486
• [Watch] 4 - Mirror route navigation #487
• [Watch] 5 - Mirror weather and radar #488
• [Watch] 6 - Control Board lights #489
• [Watch] 8 - Complete diagnostics and ride validation #491
• [Watch] 9 - Prepare App Store shipping #493

[KacperKozak]

Implemented in a402b79 on watchos.

Not verified on hardware: no motor has been turned by this. Dead-man, lost/delayed/reordered delivery and the wire are pinned by deterministic fixtures only. Real wrist-to-board latency, an out-of-range walk mid-hold, the pager locks against a real cancelled drag, and the haptics are all slice 8's hardware validation.