Стабилизация подключения K1 после сна и ожидания Bluetooth

docs/04_K1_WIFI_PROVISIONING_PROFILE.md

@@ -105,6 +105,13 @@ dispatch, a timeout, or an unchanged read-only observation without that exact
 confirmed write remains ambiguous and cannot authorize host association or an
 automatic retry.
 
+The reviewed 15-second limit applies to the byte-51 AP-ready observation after
+the one AP-enable write. It is not the CoreBluetooth connection timeout. The
+pre-write connection is one separate pending CoreBluetooth request with a
+bounded 30-second K1-appearance window. It performs no fallback discovery or
+retry; a timeout invalidates that exact captured handle with zero device writes
+and requires another explicit operator scan.
+
 Static review of the original client also established a lifecycle requirement:
 LixelGO keeps the same BLE manager connected after AP-ready and invokes native
 Wi-Fi association from that live session. Mission Core now retains the same