Subject: Codex Micro (fw v0.4.1) — BLE identity not persisted across power cycles; reconnection impossible without re-pairing (measured evidence included)

Hi Work Louder team,

I'm hitting a reproducible BLE reconnection bug on the Codex Micro and I have detailed measurements that may help you pinpoint it.

**Environment**
- Codex Micro, firmware v0.4.1 (device reports it via `device.status`)
- Windows 11 Pro (build 10.0.26200), paired over BLE
- Repro rate: every power cycle of the board

**Symptom**
After powering the board off and back on, Windows never re-establishes a working HID session. The board itself boots fine (its lighting preset shows), but the paired host cannot talk to it anymore. The ONLY reliable user fix is: forget the device in Windows + re-pair from scratch.

**Evidence measured on my machine**
1. **The board's BLE address changes between pairings**: two pairings on the same day yielded `FB:02:B1:DD:2A:7E`, then `E8:54:66:01:D2:B8` (both static-random). This suggests the firmware regenerates its identity address instead of persisting it — so the host's existing bond can never resolve the board after a power cycle.
2. After a power cycle, Windows shows a **half-established state**: the BTHLE device node reports `IsConnected = True`, the HID child instances get re-created (new container instance ID), and a WinRT **GATT service discovery succeeds** (`GetGattServicesAsync(Uncached)` → Success, all services enumerated). Yet the **HID layer is completely dead**: output reports are written without any error but never reach the board, and no input reports ever arrive. I observed this state persisting for 17+ minutes.
3. **What un-wedges it** (any of these): a short tap on the board's comms button (board re-initiates the connection); host-side WinRT `GattSession.MaintainConnection = true` + an Uncached service discovery (HID layer comes back within ~90 s); a full re-pair.
4. Your public Creator Micro 2 changelog shows this exact class of fixes ("Improved BLE reconnect and pairing behavior", several v0.4.0 RCs, up to v0.6.0-rc "pairing, reconnection, host switching, sleep recovery"). The Codex Micro firmware line doesn't seem to have received the equivalent yet.

**Requests**
1. Is a Codex Micro firmware update with the CM2-class BLE reconnect fixes planned? (v0.4.1 appears to predate them.)
2. Unrelated but important: Input 0.17.2 has **no firmware repository mapped for the Codex Micro**, yet the manual flash screen can offer firmwares of other boards — a user already bricked a Codex Micro this way (see the July 22 feedback post). A guard matching firmware ↔ device type would prevent this.

Happy to provide logs, run test builds, or capture Wireshark/BTP traces if useful.

Thanks!