Android BLE GATT Queue

Step 1: Define the serialization contract

1. DEFINE overlapping operations | wrong callback | timeout/hang | caller cancellation | disconnect/reconnect | subscription race | queue backpressure | migration.
2. IDENTIFY connection owner/epoch, callback executor/thread, supported GATT operations, submission return contract, expected callback type/target/result, per-operation timeout, caller cancellation semantics, queue capacity, reconnect policy, and unsolicited event consumers.
3. READ the official BluetoothGatt and BluetoothGattCallback methods for every queued operation/API branch.
4. READ references/article-audit.md before reusing the supplied article's sample; its loop does not wait for callbacks and several callback/signature/value assumptions are incorrect.
5. ROUTE connection/status failures to android-ble-gatt-status, local BluetoothGattServer callbacks to android-ble-gatt-server, connection/scan/background/permission ownership to android-ble, logical GATT procedure/schema to ble-protocol-stack, throughput to ble-throughput, and generic structured-concurrency choices to kotlin-coroutines.

Completion: each operation has one submission, one matching completion callback, one timeout/reset policy, and one caller result type.

Step 2: Inspect queue candidates

RUN from the Android project root:

python3 scripts/inspect-project.py --root . --json