EDGE-04: Wear OS local lightweight runtime, offline mode and optional phone relay #5

New issue

Open

opened 2026-09-23 05:58:23 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-09-23 05:58:23 +00:00

(Migrated from github.com)

Scope

Share the Android library and Common Lisp behavior; keep watch platform APIs thin. Build a watch-local lightweight profile with bounded state, durable local queue, explicit sensor capabilities, battery/thermal and charging policies, and optional phone relay. Local mode must not silently become phone execution. Product UI and branding may remain in downstream Wear OS/Zara clients.

Wear OS is the first target. ABCL is the selected Android Lisp target, but real watch ART execution is a required proof, not an assumption. Do not claim Apple Watch or other closed watch-platform coverage.

Acceptance

Watch library/APK builds reproducibly and consumes pinned shared runtime.
Actual Common Lisp API execution passes on watch ART.
Core diagnostic/local function works with phone disconnected and no cloud account.
Standalone manifest declaration matches actual independence, including setup/auth.
Process death, offline restart, capability/permission revocation and bounded queue tests.
Battery/thermal/charging behavior measured on hardware; no always-on daemon assumption.
Optional phone relay, reconnection and local-vs-relay status are explicit and tested.
Downstream consumer uses the upstream library rather than a copied runtime.

Current WatchHost.kt is a forwarding facade only; JVM tests do not establish a working watch runtime.

Primary reference checked 2026-09-23: https://developer.android.com/training/wearables/apps/standalone-apps

Canonical watch runtime source belongs in this repository. Foundation #1; shared Android/Common Lisp backend #3. This is a first-class runtime target, not merely a notification mirror or the existing phone-side watch configuration companion. ## Scope Share the Android library and Common Lisp behavior; keep watch platform APIs thin. Build a watch-local lightweight profile with bounded state, durable local queue, explicit sensor capabilities, battery/thermal and charging policies, and optional phone relay. Local mode must not silently become phone execution. Product UI and branding may remain in downstream Wear OS/Zara clients. Wear OS is the first target. ABCL is the selected Android Lisp target, but real watch ART execution is a required proof, not an assumption. Do not claim Apple Watch or other closed watch-platform coverage. ## Acceptance - [ ] Watch library/APK builds reproducibly and consumes pinned shared runtime. - [ ] Actual Common Lisp API execution passes on watch ART. - [ ] Core diagnostic/local function works with phone disconnected and no cloud account. - [ ] Standalone manifest declaration matches actual independence, including setup/auth. - [ ] Process death, offline restart, capability/permission revocation and bounded queue tests. - [ ] Battery/thermal/charging behavior measured on hardware; no always-on daemon assumption. - [ ] Optional phone relay, reconnection and local-vs-relay status are explicit and tested. - [ ] Downstream consumer uses the upstream library rather than a copied runtime. Current `WatchHost.kt` is a forwarding facade only; JVM tests do not establish a working watch runtime. Primary reference checked 2026-09-23: https://developer.android.com/training/wearables/apps/standalone-apps