feat(k1): add physical acceptance transport

docs/lab/002_LIXELGO_IPHONE_LOCAL_PROTOCOL_20260716.redacted.md

@@ -65,6 +65,20 @@ Observed K1 transports:
 
 No LixelGO UDP flow was observed.
 
+The retained clean-cycle control connection was subsequently re-audited without
+capturing new traffic. MQTT CONNECT used protocol level 4 / MQTT 3.1.1,
+`clean_session=false` and keepalive 60. Control and point-cloud subscriptions
+used separate 19-byte client IDs; their values remain private. The control
+client issued three ordered subscription groups containing 9, 5 and 42 topics
+before issuing requests. The separate point-cloud client then issued groups of
+1 and 1 topic; their values are the already documented legacy/current point
+channels. The control group order, topic names and requested QoS values are now
+locked by public synthetic regression without exposing client IDs or payloads.
+The modeling acknowledgement topic is
+`lixel/application/response/modeling`; request QoS was 2 while the K1 delivered
+the observed application response PUBLISH packets at QoS 0. These redacted
+facts bound the acceptance transport but do not authorize it.
+
 ## Start and static initialization
 
 The application start transaction is now physical wire evidence rather than