docs: record Mission Core K1 architecture milestone

docs/01_IMPLEMENTATION_PLAN.md

@@ -15,12 +15,14 @@ Each gate produces evidence and an explicit GO, PAUSE or BLOCKED result.
 | Stage 4 artifacts/flows | GO — bounded capture, hashes and negative control |
 | Stage 5 point cloud | GO — raw-LZ4 protobuf, 1,140 live frames decoded |
 | Stage 5 pose | GO — 1,215 live frames decoded and motion-correlated |
-| Stage 5 camera | PAUSE — no independent frame/video stream observed |
+| Stage 5 camera | GO (discovery) — left/right RTSP/H.264 preview observed; runtime adapter pending |
 | Stage 6 live viewer | GO — React console, Foxglove cloud/path and Mac latency metrics |
 
 USB project copying remains optional ground truth rather than a blocker for the
-now-verified network path. MQTT control publishing remains deliberately deferred
-because the physical button is a known-safe start/stop mechanism.
+now-verified network path. Owner-operated LixelGO traffic verifies the MQTT
+start/stop mapping and RTSP camera transport. MQTT control publishing remains
+deliberately deferred because complete request/save/rollback semantics are not
+yet modeled and the physical button remains a known-safe fallback.
 
 The Stage 6 alpha uses a bounded raw-first bridge: loss in the visualization
 queue cannot discard MQTT evidence. Acceptance is replay of the full captured