@kusinta/iot-schema 0.2.0-beta.11 → 0.2.0-beta.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kusinta/iot-schema",
-  "version": "0.2.0-beta.11",
+  "version": "0.2.0-beta.12",
   "type": "module",
   "license": "MIT",
   "files": ["src"],

package/src/kusinta/iot/common/v1/pairing_pb.d.ts

@@ -192,6 +192,22 @@ export enum PairingError {
    * @generated from enum value: PAIRING_ERROR_INTERNAL = 7;
    */
   INTERNAL = 7,
+
+  /**
+   * The request named no connector. Pairing always targets exactly one connector,
+   * chosen from the connector enumeration; an untargeted "pair anything" is refused
+   * rather than fanned out across every hub. Permanent for the request as sent —
+   * naming a connector and asking again is the fix, retrying identically is not —
+   * which is why this is not CONNECTOR_UNAVAILABLE, whose retry is reasonable.
+   *
+   * The gateway is the enforcer: connector_id is a message field, so proto cannot
+   * mark it required, and the check lives where the fan-out used to. A client whose
+   * schema predates this reads it as UNSPECIFIED and offers a retry, which is
+   * harmless — an app built against the enumeration always names a connector anyway.
+   *
+   * @generated from enum value: PAIRING_ERROR_CONNECTOR_REQUIRED = 8;
+   */
+  CONNECTOR_REQUIRED = 8,
 }
 
 /**

package/src/kusinta/iot/common/v1/pairing_pb.js

@@ -8,7 +8,7 @@ import { enumDesc, fileDesc, messageDesc, tsEnum } from "@bufbuild/protobuf/code
  * Describes the file kusinta/iot/common/v1/pairing.proto.
  */
 export const file_kusinta_iot_common_v1_pairing = /*@__PURE__*/
-  fileDesc("CiNrdXNpbnRhL2lvdC9jb21tb24vdjEvcGFpcmluZy5wcm90bxIVa3VzaW50YS5pb3QuY29tbW9uLnYxIlgKElBhaXJpbmdFcnJvckRldGFpbBIxCgRjb2RlGAEgASgOMiMua3VzaW50YS5pb3QuY29tbW9uLnYxLlBhaXJpbmdFcnJvchIPCgdtZXNzYWdlGAIgASgJIoIBCg1QYWlyaW5nV2luZG93Eh0KEGR1cmF0aW9uX3NlY29uZHMYASABKA1IAIgBARITCgtkZXZpY2VfaGludBgCIAEoCRIYCgttYXhfZGV2aWNlcxgDIAEoDUgBiAEBQhMKEV9kdXJhdGlvbl9zZWNvbmRzQg4KDF9tYXhfZGV2aWNlcyqiAgoMUGFpcmluZ0Vycm9yEh0KGVBBSVJJTkdfRVJST1JfVU5TUEVDSUZJRUQQABIeChpQQUlSSU5HX0VSUk9SX05PVF9FTlRJVExFRBABEiUKIVBBSVJJTkdfRVJST1JfQUxSRUFEWV9JTl9QUk9HUkVTUxACEicKI1BBSVJJTkdfRVJST1JfQ09OTkVDVE9SX1VOQVZBSUxBQkxFEAMSJAogUEFJUklOR19FUlJPUl9OT19ERVZJQ0VfQVBQRUFSRUQQBBIhCh1QQUlSSU5HX0VSUk9SX0RFVklDRV9VTlVTQUJMRRAFEh4KGlBBSVJJTkdfRVJST1JfV1JPTkdfREVWSUNFEAYSGgoWUEFJUklOR19FUlJPUl9JTlRFUk5BTBAHQgJIAWIGcHJvdG8z");
+  fileDesc("CiNrdXNpbnRhL2lvdC9jb21tb24vdjEvcGFpcmluZy5wcm90bxIVa3VzaW50YS5pb3QuY29tbW9uLnYxIlgKElBhaXJpbmdFcnJvckRldGFpbBIxCgRjb2RlGAEgASgOMiMua3VzaW50YS5pb3QuY29tbW9uLnYxLlBhaXJpbmdFcnJvchIPCgdtZXNzYWdlGAIgASgJIoIBCg1QYWlyaW5nV2luZG93Eh0KEGR1cmF0aW9uX3NlY29uZHMYASABKA1IAIgBARITCgtkZXZpY2VfaGludBgCIAEoCRIYCgttYXhfZGV2aWNlcxgDIAEoDUgBiAEBQhMKEV9kdXJhdGlvbl9zZWNvbmRzQg4KDF9tYXhfZGV2aWNlcyrIAgoMUGFpcmluZ0Vycm9yEh0KGVBBSVJJTkdfRVJST1JfVU5TUEVDSUZJRUQQABIeChpQQUlSSU5HX0VSUk9SX05PVF9FTlRJVExFRBABEiUKIVBBSVJJTkdfRVJST1JfQUxSRUFEWV9JTl9QUk9HUkVTUxACEicKI1BBSVJJTkdfRVJST1JfQ09OTkVDVE9SX1VOQVZBSUxBQkxFEAMSJAogUEFJUklOR19FUlJPUl9OT19ERVZJQ0VfQVBQRUFSRUQQBBIhCh1QQUlSSU5HX0VSUk9SX0RFVklDRV9VTlVTQUJMRRAFEh4KGlBBSVJJTkdfRVJST1JfV1JPTkdfREVWSUNFEAYSGgoWUEFJUklOR19FUlJPUl9JTlRFUk5BTBAHEiQKIFBBSVJJTkdfRVJST1JfQ09OTkVDVE9SX1JFUVVJUkVEEAhCAkgBYgZwcm90bzM");
 
 /**
  * Describes the message kusinta.iot.common.v1.PairingErrorDetail.

package/src/kusinta/iot/webrtc/v1/envelope_pb.d.ts

@@ -342,8 +342,9 @@ export declare const ManagementResultSchema: GenMessage<ManagementResult>;
  *
  * A payload case of its own rather than a ManagementRequest. Those are gated on a target —
  * a space, a device — and that is the justification for keeping them behind one wrapper.
- * This one names no target: connector_id is optional, and unset means every connector, so
- * it is authorized against the caller's role and nothing else.
+ * A connector is not a target the caller must reach the way a space is, so this is
+ * authorized against the caller's role and nothing else — but it must still name the
+ * connector to open (see connector_id), never every connector at once.
  *
  * Answered twice, and the two answers say different things at different times.
  * PairingStarted reports whether the window opened; PairingFinished reports what came of
@@ -354,13 +355,13 @@ export declare const ManagementResultSchema: GenMessage<ManagementResult>;
  */
 export declare type StartPairing = Message<"kusinta.iot.webrtc.v1.StartPairing"> & {
   /**
-   * Which connector to open. Unset means every connector the gateway holds, which is the
-   * sensible default: a device picks its hub by radio range, and asking a user to choose is
-   * asking them to guess at something they cannot observe.
-   *
-   * Name one where the answer is not a guess — a device that will be linked to devices on a
-   * particular hub has to join that hub, because links are held by the hub that brokered
-   * them.
+   * Which connector to open. Required: pairing always targets exactly one connector,
+   * picked from the connector enumeration (see ConnectorsAnnounced and
+   * ConnectorInfo.supports_pairing). An untargeted request is refused with
+   * PairingError.CONNECTOR_REQUIRED, never fanned out across every hub — so that no
+   * client can open every radio at once, and so a device is paired onto the specific hub
+   * that will broker its links. The field is a message, so proto cannot mark it required;
+   * the gateway enforces it.
    *
    * @generated from field: kusinta.iot.identity.v1.ConnectorId connector_id = 1;
    */