docs(milestone): record K1 control and archive acceptance

docs/06_K1_LIVE_VIEWER.md

@@ -134,8 +134,10 @@ directly and use their sibling metadata receive timestamps when present.
    from a browser timer or accumulated across a device counter reset.
 10. Choose **Остановить устройство и запись** in the scene. The
     plugin-commanded path emits one canonical STOP on the original socket,
-    waits for live unbound READY, and asks the operator to confirm the constant
-    green indicator before capture, camera archive and summaries are finalized.
+    waits for live unbound READY, then finalizes capture, camera archive and
+    summaries automatically. The UI does not ask for a redundant green-indicator
+    confirmation because READY plus cleared project binding is already the
+    scanner's protocol evidence.
 
 Each new live run creates a direct child below `MISSIONCORE_EVIDENCE_DIR`, or
 `.runtime/mission-core/evidence/sessions/` by default, with raw MQTT frames,
@@ -336,9 +338,10 @@ listener and its process memory must be closed unconditionally.
   left/right compressed RTSP preview and acquisition-owned fMP4 archive use a
   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
-  promotion needs reviewed Keychain item provisioning, operator-present use of
-  the uninstalled response-gated transport and durable-save proof.
+- Physical double-click remains the independently verified device-local fallback.
+  Mission Core also contains the installed response-gated operator-present
+  acceptance transport for the exact K1/A4/FW 3.0.2 profile; its full
+  START-to-STOP durable-save cycle was physically accepted on 2026-07-18/19.
 - 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