docs(k1): record connection mode acceptance

plugins/xgrids-k1/README.md

@@ -19,7 +19,8 @@ The plugin owns:
 - the exact firmware/topology compatibility profiles under
   [`profiles/`](profiles/), with strict evidence flags and a fail-closed loader;
 - BLE discovery hints and K1 GATT metadata;
-- the reviewed firmware-3 Wi-Fi provisioning profile;
+- Bridge and Direct Connect through the reviewed firmware-3 BLE Wi-Fi
+  provisioning frame, plus a one-shot macOS CoreWLAN Quick Connect adapter;
 - K1 LAN status and private-address validation;
 - subscribe-only data MQTT transport plus a separately bounded canonical
   application-control transport;
@@ -74,7 +75,8 @@ in-process and its health is lifecycle-only; process isolation, crash/restart
 containment and signed deployment remain later supervisor gates.
 
 The compatibility profile is descriptive and cannot itself authorize a vendor
-write. The UI selects the exact firmware `3.0.2` / direct-LAN profile; the
+write. The UI selects the exact firmware `3.0.2` local-network profile and an
+exact topology for Bridge, Quick Connect or Direct Connect; the
 canonical bootstrap then requires a correlated live `DeviceInfo` match for
 model `LixelKity K1`, platform type `A4`, activation and firmware before START.
 Validate the current exact-match profile without device I/O with:
@@ -83,7 +85,18 @@ Validate the current exact-match profile without device I/O with:
 uv run python plugins/xgrids-k1/profile_loader.py
 ```
 
-Plugin v0.5.0 installs that reviewed transport behind explicit plugin actions.
+Plugin v0.6.0 retains the physically accepted v0.5.0 control transport and adds
+the connection matrix behind the existing explicit `network.provision` action.
+Bridge remains the default. Direct Connect sends the same single reviewed
+99-byte frame with credentials for an already-running controller hotspot. Quick
+Connect sends no BLE write: a short-lived Swift/CoreWLAN helper receives the
+operator-entered K1 AP credentials only over stdin, performs at most one scan
+and one association, and never receives an automatic retry. Mission Core then
+uses the observed K1 AP data-plane address. Automatic extraction of AP
+credentials from undocumented BLE data is deliberately not implemented.
+
+Plugin v0.5.0 installed the reviewed application-control transport behind
+explicit plugin actions.
 The normal UI accepts the project name and one explicit launch confirmation.
 It then performs operations 1–6, operation 7 and operations 8–10 only after the
 previous response barrier succeeds, prepares local reception, and emits one