feat(k1): stabilize LAB bridge and isolate onboard device integration

plugins/xgrids-k1/README.md

@@ -14,6 +14,23 @@ This manifest currently exposes only `xgrids.lixelkity-k1`, and the transitional
 runtime still owns one active model/session at a time. Concurrent model/session
 routing remains a later supervisor milestone.
 
+The onboard sensor views and Bridge enrollment controller are also plugin-owned
+under `frontend/src/sensors`. The shared sensor workspace consumes optional
+`SensorUiContribution` renderers through `@mission-core/sensor-sdk`; the main
+frontend registers these on `DeviceUiPlugin.sensorUi`, and the Node frontend
+selects its installed contribution explicitly. An absent or ambiguous renderer
+does not fall through into another device's detail controls. The current single
+enrollment provider is explicit; a multi-provider enrollment picker is not yet
+implemented.
+
+`connection_attempt.py` owns the pure join of network journal, owned control
+bootstrap, recovery verification and current control authority. LAB keeps the
+full public attempt; Node exports a compact allowlisted projection without
+timeline payloads or diagnostic bundles. The Node observer submits once and
+follows the same operation across response loss and bootstrap completion.
+These are read-model and presentation boundaries, not a new command scheduler
+or a claim of independently installable backend/process isolation.
+
 The plugin owns:
 
 - the exact firmware/topology compatibility profiles under