Retire the PKJS feed behind a fallback flag #21

New issue

Open

opened 2026-08-31 17:14:42 +02:00 by robert · 0 comments

robert commented

2026-08-31 17:14:42 +02:00

(Migrated from git.butzei.de)

Goal

Once the companion app supplies position, PKJS becomes the fallback transport rather than the primary path.

Acceptance criteria

Companion app is the default source when installed and reachable
PKJS path retained behind a flag for the Spike A fallback scenario
Only one source is active at a time - no double-counted distance
Which path is active is visible somewhere in the UI for debugging

Files

watchapp/src/pkjs/index.js
watchapp/src/c/main.c

## Goal Once the companion app supplies position, PKJS becomes the fallback transport rather than the primary path. ## Acceptance criteria - [ ] Companion app is the default source when installed and reachable - [ ] PKJS path retained behind a flag for the Spike A fallback scenario - [ ] Only one source is active at a time - no double-counted distance - [ ] Which path is active is visible somewhere in the UI for debugging ## Files - `watchapp/src/pkjs/index.js` - `watchapp/src/c/main.c`