feat(k1): wire canonical control session to UI

README.md

@@ -133,9 +133,9 @@ BLE Wi-Fi provisioning write, read-only MQTT live capture, native `.k1mqtt` and
 reviewed-TSV replay, raw-first evidence storage, device-reported scan
 time/distance/speed and measured preview metrics. Its frontend contribution now
 also owns an optional spatial-scene control block, including acquisition phase,
-telemetry and the stop action. On the active laboratory profile that stop action
-finalizes local reception only; physical K1 scanning is still started and
-stopped by the verified double-click.
+telemetry and the stop action. Operator-manual acquisition still finalizes only
+local reception; plugin-commanded v0.5.0 acquisition uses the separately gated
+canonical K1 START/STOP dialogue.
 
 The exact recovered `ModelingRequest` start/stop encoder, response correlator
 and device-status state machine are implemented as inert protocol components.
@@ -147,16 +147,18 @@ as one private application-level value in the observed client, not a manual
 per-scanner profile. The whole pre-START order and START/STOP payloads are
 byte-matched offline. A fixed macOS Keychain loader now supplies the exact
 application authority without env/file/browser fallback, and a five-batch
-orchestrator passes all retained response barriers. The installed publisher
-boundary is structurally write-disabled and cannot call its sink. Plugin v0.4.0
-wires a dormant coordinator into the facade: explicit shadow arm holds authority
+orchestrator passes all retained response barriers. The legacy shadow publisher
+boundary remains structurally write-disabled and cannot call its sink. Its
+dormant coordinator can hold authority
 for at most 300 seconds and expiry/disarm/reprovision/acquisition/shutdown revoke
-it together with the orchestrator. A separate, uninstalled physical-acceptance
-transport now reproduces MQTT 3.1.1 `clean_session=false`, keepalive 60, exact
+it together with the orchestrator. Plugin v0.5.0 installs a separate
+physical-acceptance transport reproducing MQTT 3.1.1 `clean_session=false`,
+keepalive 60, exact
 response subscriptions, QoS2 completion and the five response-gated batches.
 It consumes operation keys before publish and poisons unknown outcomes without
-retry. Neither component is wired to facade/UI; `vendor_writes_enabled` remains
-false. The first operator-present physical attempt on 2026-07-18 emitted only
+retry. One background owner services that socket between separate connection,
+workspace, project, START, STOP and steady-green UI actions; navigation cannot
+emit a command. The first operator-present physical attempt on 2026-07-18 emitted only
 the first six bootstrap requests, then failed closed while correlating the third
 response batch; START was not emitted. A second one-shot attempt correlated all
 ten pre-START requests and the START acknowledgement, but incorrectly collapsed