C1.5: Build the Android companion BLE and durable-sync foundation

[Tinnci]

Goal

Create a real minimal Android companion that associates, connects and runs the shared protocol durably.

Scope

Modern Gradle/Kotlin project, Companion Device Manager association, appropriate CompanionDeviceService/presence lifecycle, permissions, GATT client, protocol transport, durable queue/cursors, minimal status/config/diagnostic UI and Kotlin golden vectors.

Non-goals

Large UI, fixed periodic scanning, broad notification mirror, cloud account framework or simulated-only companion.

Dependencies

Depends on #31 and #32.

Acceptance criteria

• Clean Android build and JVM tests succeed with the pinned local toolchain.
• Kotlin agrees with all C++ golden vectors.
• Association, reconnect and process restart state machines are explicit.
• Permissions and background behavior follow supported Android APIs.
• Durable state is persisted before ACK ownership is reported.

Automated evidence

JVM unit tests cover codec, queue, lifecycle state, duplicate and reconnect. Instrumentation tests run where an Android target permits.

Hardware evidence

A real Android device must pair, reconnect, survive process/background scenarios and exchange durable state before closure.

Closure condition

Keep open until both automated evidence and available real-device evidence are attached.

[Tinnci]

Automated foundation checkpoint is pushed on 95d2063; this Issue remains OPEN for its required real-Android evidence.

Verified now:

• Real Android application module, minSdk 26 / targetSdk 37, built-in Kotlin, minimal Activity and CompanionDeviceService.
• Companion Device Manager association request filters for Zectrix Note4; no periodic scan loop is used.
• Kotlin Protocol 1.0 encoder/decoder matches the C++ golden frame byte-for-byte and rejects every single-byte mutation.
• File-backed durable queue persists before reporting enqueue/ACK success and rejects corrupt records.
• Ordered association/connect/discovery/negotiation/reconnect state-machine tests pass.
• :app:testDebugUnitTest and :app:assembleDebug pass with no compiler warning.
• Debug APK SHA-256 from this build: 3d29ea764a2c0a5e5e87b4be42e3433f0e21df44d6f6af2c2c5dc56dd28127bc.

Still required before closure:

• real Android association and GATT connection;
• background/presence and process restart behavior;
• durable exchange with real Note4;
• explicit unpair/re-pair;
• instrumentation where a device becomes available.

adb devices -l currently has no Android target, so none of these physical results is claimed.

[Tinnci]

Production Android/GATT checkpoint (7bfaaca, corrected by 1213643)

Implemented and pushed:

• Companion Device association and presence-driven background reconnect; no fixed periodic scan loop.
• Production connectGatt() client with explicit discovery, CCCD subscription, pairing, secure-link verification, MTU setup and Hello/HelloAck states.
• Serialized bounded GATT writes, fragmentation, stale-callback rejection and process-owned connection lifecycle.
• Material 3 Expressive UI and the Android 12 Companion Device Manager crash fix.
• Matching HelloAck now requires message class/type, response flag, request ID, sequence and empty payload. A wrong sequence cannot enter Android READY.

Automated evidence:

• Android JVM tests and assembleDebug: PASS.
• Shared protocol tests and architecture/SDK checks: PASS.
• ESP-IDF v5.5.2 firmware build: PASS; application size 0x12af10, 61% partition free.

This Issue remains OPEN. Real-device evidence is still required for fresh association/pair, Hello/HelloAck, background/process restart, Note4 reboot reconnect, durable exchange and unpair/re-pair. Peer authorization is also not implemented; Android READY currently means secure transport plus observed protocol negotiation, not full product readiness.

[Tinnci]

G1.1 delivery review — 2026-09-10

Android now implements NFC enrollment intake and stored peer authorization, hardened durable replay, the controlled resource gateway, reading-position resume and authorized time calibration. The older comment that peer authorization is unimplemented no longer describes current code.

Evidence: 33478d8, f76a84b, 3cfd529, bcf84b0 and d68b43f. The latest recorded S1.3 Android validation includes 29 JVM tests and the debug build; current firmware Host regression passes all 34 targets.

Keep open for real association/pairing, background/presence and process restart, Note4 reboot reconnect, durable exchange and unpair/re-pair. This governance run does not add Android device evidence.