feat(k1): recover exact application bootstrap

docs/06_K1_LIVE_VIEWER.md

@@ -143,14 +143,13 @@ per-message metadata and a hash summary. Repository-level
 the current writer. The connector subscribes to the fixed report-topic
 allowlist and does not publish an application request or modeling command.
 
-The recovered command substrate is intentionally inert. It can encode exact
-start/stop request bytes, correlate response identity/action/result and classify
-observed device states without importing MQTT or publishing anything. The header
-requires explicit ASCII `device_id` and OpenAPI key and derives the session ID
-exactly as `${device_id}:ModelingRequest`. Legitimate OpenAPI key
-provenance/provisioning and durable save completion after stop are unresolved,
-so `vendor_writes_enabled` is false and the physical-button workflow remains
-canonical.
+The recovered command substrate is intentionally inert. It byte-matches the ten
+observed pre-START requests plus START/STOP, correlates DeviceInfo and modeling
+responses, and classifies live device states without importing MQTT or
+publishing anything. One private application-level OpenAPI authority is kept
+separate from the transient vendor ID/serial returned by the BLE-selected K1.
+Secure authority loading and durable save completion after stop remain open, so
+`vendor_writes_enabled` is false and the physical-button workflow is canonical.
 
 ## Automatic Rerun source and lifecycle
 
@@ -332,8 +331,8 @@ listener and its process memory must be closed unconditionally.
   separate generic media path. Historical sessions predating that archive have
   no recoverable video.
 - Physical double-click remains the K1 scan start/stop control. Any MQTT command
-  publisher needs a separately reviewed state-changing profile with legitimate
-  OpenAPI key provisioning and a proven durable-save completion gate.
+  publisher needs reviewed private application-authority loading, response-gated
+  one-shot behavior and a proven durable-save completion gate.
 - No terrain map, elevation model, obstacle segmentation, localization fusion,
   mission planner or vehicle control is implemented by this viewer milestone.
 - Exact coordinate axes and the scanner-to-vehicle transform remain a mounting