docs(k1): record successful onboard Bluetooth discovery
This commit is contained in:
@@ -92,6 +92,14 @@ binding; it reports fresh/available/idle and permits scan-ble. No hardware
|
||||
discovery is inferred from these readiness facts. The owner was asked to clear
|
||||
Chrome cache again and repeat Find K1 through the Core Fleet modal.
|
||||
|
||||
The subsequent real onboard scan completed: Fleet reported discovery generation
|
||||
1, one K1 candidate and RSSI -62 dBm, with the new runtime still available.
|
||||
The agent issued no hardware command; this was observed after asking the owner
|
||||
to use the UI. This confirms actual onboard Bluetooth discovery. Separate
|
||||
explicit confirmation of the fresh-cache procedure, Wi-Fi provisioning,
|
||||
camera/LiDAR and recovery acceptance remains open. Raw device identifiers stay
|
||||
in the private acceptance material.
|
||||
|
||||
Git publication remains pending explicit owner authorization after automatic
|
||||
approval review rejected the preceding installation report `2fdf1d3` due to
|
||||
internal deployment metadata and its destination. No push workaround was used.
|
||||
|
||||
Reference in New Issue
Block a user