Android BLE GATT Server

Step 1: Define the local GATT server contract

1. DEFINE local service database | characteristic/descriptor read | immediate write | prepared/execute write | CCCD subscription | notification/indication | multiple centrals | connection/MTU | service update | shutdown.
2. IDENTIFY min/compile/target SDK, device/OEM/client matrix, peripheral and GATT-server roles, logical schema/version, UUID/instance identity, properties/permissions/security, per-central state, value encoding/limits, response status mapping, prepared-write budget, CCCD policy, notification queue, callback confinement, advertising owner, server lifetime, and process-death recovery.
3. READ current BluetoothManager, BluetoothGattServer, and BluetoothGattServerCallback symbol pages for every used API.
4. READ references/api-contracts.md for server/client boundaries, unsupported profile queries, API 33 value methods, and API 37.2 availability.
5. ROUTE scanning/advertising/background/permission lifecycle to android-ble, remote BluetoothGatt client operations to android-ble-gatt-queue, logical schema/profile design to ble-protocol-stack, and sockets to android-bluetooth-sockets.

Completion: database, every ATT callback/response, per-central state, transaction/notification ordering, lifecycle owner, and SDK/device matrix are explicit.

Step 2: Inspect the Android project

RUN from the Android project root:

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