Стабилизация переключения Bridge и Quick Connect
Безопасно восстанавливает управляющее подключение и локальные checkpoint без повторных команд сканеру. Добавляет PCAP/Bridge guardrails и регрессионные проверки одношагового переподключения. Известный дефект: после второго подключения интерфейс не присоединяется к новой генерации preview правой камеры. В живой Quick Connect-сессии STOP был принят, но READY не подтвердился до таймаута; автоматический повтор STOP запрещён.
This commit is contained in:
@@ -96,6 +96,15 @@ Core Quick Connect intent emits one AP-enable frame even when the baseline mode
|
||||
already says `WIFI_AP`, then polls for the byte-51 ready flag for at most 15
|
||||
seconds. It never retries the device write automatically.
|
||||
|
||||
For that exact explicit intent, a completed write-with-response followed by
|
||||
the same canonical `WIFI_AP / 192.168.56.1 / ready` observation is an
|
||||
idempotent ensure-target success: the K1 AP was already ready, and the host may
|
||||
continue into the bounded exact-SSID CoreWLAN association. This exception
|
||||
requires the durable ledger to record `write_confirmed=true`. An unconfirmed
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
@@ -163,6 +163,13 @@ contract coverage but remains a distinct physical acceptance gate; it must not
|
||||
be reported as field-accepted until one redacted live run records both sides of
|
||||
the transition.
|
||||
|
||||
Quick Connect Apply is an exact idempotent ensure-target operation when the
|
||||
selected K1 already reports the canonical AP-ready state. Mission Core accepts
|
||||
that unchanged state only after the one reviewed write-with-response is
|
||||
durably confirmed, then performs the normal exact device-SSID host association.
|
||||
An unconfirmed or merely read-only unchanged observation remains fail-closed;
|
||||
this rule neither retries the BLE write nor weakens Bridge admission.
|
||||
|
||||
The corrected host boundary derives a non-secret, device-scoped profile ID from
|
||||
the selected SSID. The reviewed client contains per-device `WiFiAP_SSID` and
|
||||
`WiFiAP_Password` fields, but the 2026-07-20 review of the exact official K1
|
||||
|
||||
Reference in New Issue
Block a user