feat(testing): End-to-End on-device smoke test harness & live P2P bridge verifier

[hungify]

What to build

Build an end-to-end on-device smoke test harness to verify live P2P communication between the Android phone app and Huawei Watch GT5. Deploy both apps, send mock navigation sequences (turns, distances, arrival), and verify watch screen rendering, connection indicator, and haptic feedback.

Acceptance criteria

• Script / test tool to trigger mock navigation message sequence from phone to watch over active Wear Engine P2P bridge.
• Verifies watch displays updated arrow icon, distance in meters, and street name.
• Verifies arrival state transitions and vibration triggers.
• Captures ping latency and logs communication result codes for diagnostics.

Blocked by

• feat(dev-tools): Device pre-flight diagnostics & ADB connection health-check #34: feat(dev-tools): Device pre-flight diagnostics & ADB connection health-check
• feat(watch-app): HAP packaging verification & DevEco sideload automation script #35: feat(watch-app): HAP packaging verification & DevEco sideload automation script

[hungify]

Scope note: the pipeline this ticket verifies end-to-end is changing per the v1.4 architecture pivot (docs/PRD.md Section 13) — the phone side now relays a parsed Google Maps notification (#61/#62) instead of its own GPS/Directions-based route. The on-device smoke test's coverage of the phone→watch P2P path stays relevant; the part that exercised GPS/Directions-driven updates should be re-scoped to exercise the notification relay instead.