@epilot/entity-client 7.2.0 → 7.2.1-rc1

package/dist/openapi.d.ts

@@ -516,26 +516,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "address";
             default_address_fields?: /**
@@ -719,26 +734,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "relation_address";
             default_address_fields?: /**
@@ -939,26 +969,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "automation";
         }
@@ -1174,26 +1219,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
         }
         /**
@@ -1279,8 +1339,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -1445,26 +1509,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "boolean";
             display_type?: "switch" | "checkbox";
@@ -1487,17 +1566,19 @@ declare namespace Components {
             created_at: string; // date-time
             created_by?: /* Identifies the actor that created the changeset. */ ChangesetCreator;
             /**
-             * The edit mode that triggered this changeset
+             * The edit mode that triggered this changeset.
+             * - `external`: auto-cleared by a matching `?direct=true` write (see `match_strategy`).
+             * - `approval`: resolved only via explicit `:apply` / `:dismiss` endpoints; never auto-clears.
+             *
              */
             edit_mode: "external" | "approval";
-            match_strategy?: /**
-             * Strategy for auto-clearing the changeset when an external update is received.
-             * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-             * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
-             * - `any`: Any update to the attribute clears the changeset, regardless of value.
+            /**
+             * Match strategy copied from the attribute's `edit_mode_config` at changeset
+             * creation time. Only consulted when `edit_mode` is `external`; ignored for
+             * `approval` (which never auto-clears).
              *
              */
-            MatchStrategy;
+            match_strategy?: "exact" | "fuzzy" | "any";
             /**
              * Optional label indicating where the change originated (e.g. end_customer_portal, installer_portal, journey, automation)
              */
@@ -1733,26 +1814,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "computed";
             computed?: boolean;
@@ -1919,26 +2015,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "consent";
             topic: string;
@@ -2098,26 +2209,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "country";
         }
@@ -2275,26 +2401,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "currency";
             currency_selector_only?: boolean;
@@ -2462,26 +2603,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "date" | "datetime";
         }
@@ -2522,18 +2678,49 @@ declare namespace Components {
             cluster?: string;
         }
         /**
-         * Configuration for non-direct edit modes on an entity attribute.
+         * Controls whether a write goes through immediately or is held as a pending entry
+         * on the parent entity's `_changesets` map.
+         *
+         * - `direct`: write applied immediately. No changeset created.
+         * - `external`: write held as a pending changeset; auto-cleared on a matching direct/ERP write.
+         * - `approval`: write held as a pending changeset; requires explicit human apply/dismiss.
+         *
+         * Used at two levels: per-attribute (entity-attribute changesets) and per-capability
+         * (currently the `meter_readings` capability on the Meter schema, gating reading submissions).
+         *
+         */
+        export type EditMode = "direct" | "external" | "approval";
+        /**
+         * Configuration for `edit_mode: external` auto-clear matching.
+         * Fields here (`match_strategy`, `fuzzy_config`) only take effect when
+         * `edit_mode` is `external`. They are ignored for `edit_mode: approval`,
+         * which never auto-clears and is resolved exclusively via the
+         * `:apply` / `:dismiss` changeset endpoints.
+         *
          */
         export interface EditModeConfig {
             match_strategy?: /**
-             * Strategy for auto-clearing the changeset when an external update is received.
+             * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+             * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+             * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+             * exclusively via the `:apply` / `:dismiss` changeset endpoints.
              * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-             * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+             * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
              * - `any`: Any update to the attribute clears the changeset, regardless of value.
              *
              */
             MatchStrategy;
-            fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+            fuzzy_config?: /**
+             * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+             * Not used for `edit_mode: approval`.
+             *
+             * Type compatibility with attribute shape is enforced at schema save time:
+             * - scalar string attributes: `suffix`, `digits_only`, `regex`
+             * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+             * - relation attributes: `relation_set`
+             *
+             */
+            FuzzyConfig;
         }
         /**
          * Email address
@@ -2689,26 +2876,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "email";
         }
@@ -2795,8 +2997,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -3299,8 +3505,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -3590,8 +3800,12 @@ declare namespace Components {
                 _manifest?: string /* uuid */[] | null;
                 /**
                  * Pending attribute changesets for attributes configured with external or approval edit mode.
-                 * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-                 * Use the changeset management endpoints to apply or dismiss changesets.
+                 *
+                 * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+                 * and is what `:apply` / `:dismiss` operate on.
+                 *
+                 * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+                 * from request bodies. Use the changeset management endpoints to mutate this field.
                  *
                  */
                 _changesets?: {
@@ -3683,8 +3897,12 @@ declare namespace Components {
                     _manifest?: string /* uuid */[] | null;
                     /**
                      * Pending attribute changesets for attributes configured with external or approval edit mode.
-                     * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-                     * Use the changeset management endpoints to apply or dismiss changesets.
+                     *
+                     * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+                     * and is what `:apply` / `:dismiss` operate on.
+                     *
+                     * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+                     * from request bodies. Use the changeset management endpoints to mutate this field.
                      *
                      */
                     _changesets?: {
@@ -3775,8 +3993,12 @@ declare namespace Components {
                     _manifest?: string /* uuid */[] | null;
                     /**
                      * Pending attribute changesets for attributes configured with external or approval edit mode.
-                     * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-                     * Use the changeset management endpoints to apply or dismiss changesets.
+                     *
+                     * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+                     * and is what `:apply` / `:dismiss` operate on.
+                     *
+                     * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+                     * from request bodies. Use the changeset management endpoints to mutate this field.
                      *
                      */
                     _changesets?: {
@@ -3867,8 +4089,12 @@ declare namespace Components {
                     _manifest?: string /* uuid */[] | null;
                     /**
                      * Pending attribute changesets for attributes configured with external or approval edit mode.
-                     * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-                     * Use the changeset management endpoints to apply or dismiss changesets.
+                     *
+                     * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+                     * and is what `:apply` / `:dismiss` operate on.
+                     *
+                     * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+                     * from request bodies. Use the changeset management endpoints to mutate this field.
                      *
                      */
                     _changesets?: {
@@ -5208,26 +5434,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "image" | "file";
             multiple?: boolean;
@@ -5254,19 +5495,26 @@ declare namespace Components {
             file_size_bytes?: number;
         }
         /**
-         * Configuration for fuzzy match strategies on changeset auto-clearing.
+         * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+         * Not used for `edit_mode: approval`.
+         *
+         * Type compatibility with attribute shape is enforced at schema save time:
+         * - scalar string attributes: `suffix`, `digits_only`, `regex`
+         * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+         * - relation attributes: `relation_set`
+         *
          */
         export interface FuzzyConfig {
             /**
              * Which fuzzy algorithm to apply.
              */
-            type: "suffix" | "digits_only" | "normalize_phone" | "ignore_fields" | "contains_entry" | "regex";
+            type: "suffix" | "digits_only" | "normalize_phone" | "ignore_fields" | "set_equivalent" | "entry_match" | "relation_set" | "regex";
             /**
              * For type=suffix: number of characters to compare from end of string.
              */
             suffix_length?: number;
             /**
-             * For type=ignore_fields: field names to exclude when comparing array entries.
+             * For type=ignore_fields and type=set_equivalent: field names to exclude when comparing array entries. `_id` is always stripped by the platform regardless of this config.
              */
             fields_to_ignore?: string[];
             /**
@@ -5278,9 +5526,28 @@ declare namespace Components {
              */
             country_code?: string;
             /**
-             * For type=normalize_phone and type=contains_entry: attribute key(s) within array entries to compare on.
+             * For type=normalize_phone: attribute key within array entries to compare on (e.g. 'phone_number').
              */
             match_on?: string;
+            /**
+             * For type=entry_match: business key(s) within each entry used to match proposed entries against incoming entries.
+             */
+            key?: /* For type=entry_match: business key(s) within each entry used to match proposed entries against incoming entries. */ string | string[];
+            /**
+             * For type=entry_match and type=set_equivalent: how strict the comparison is.
+             * - `subset` (default for entry_match): every proposed entry must exist in incoming; extra incoming entries are allowed.
+             * - `exact_set` (default for set_equivalent): the two sides must contain the same entries (order-insensitive, multiset semantics).
+             *
+             */
+            mode?: "subset" | "exact_set";
+            /**
+             * For type=relation_set: when true, relation order is significant. Defaults to false (order-insensitive).
+             */
+            ordered?: boolean;
+            /**
+             * For type=relation_set: when true, each relation item's `_tags` must match on both sides (order-insensitive). Defaults to false — `_tags` are stripped before compare.
+             */
+            require_tags_match?: boolean;
             /**
              * For type=regex: regular expression pattern to test the incoming value against.
              */
@@ -5875,8 +6142,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -6040,26 +6311,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "internal";
         }
@@ -6217,26 +6503,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "internal_user";
         }
@@ -6394,26 +6695,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "invitation_email";
         }
@@ -6579,26 +6895,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "link";
         }
@@ -6611,9 +6942,12 @@ declare namespace Components {
             results?: /* A saved entity view */ SavedViewItem[];
         }
         /**
-         * Strategy for auto-clearing the changeset when an external update is received.
+         * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+         * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+         * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+         * exclusively via the `:apply` / `:dismiss` changeset endpoints.
          * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-         * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+         * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
          * - `any`: Any update to the attribute clears the changeset, regardless of value.
          *
          */
@@ -6772,32 +7106,131 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "message_email_address";
             address?: string;
             send_status?: string;
             email_type?: string;
         }
+        /**
+         * A meter readings changeset entry — service-managed by metering-api.
+         * Stored on `Meter._meter_readings_changeset` array attribute. Each entry mirrors a
+         * ClickHouse meter reading row plus a changeset metadata overlay.
+         *
+         * Note: `org_id` is NOT stored on the entry. The entries live on the Meter entity,
+         * which is already org-scoped (`_org`). Round-tripping it would only invite drift;
+         * downstream consumers receive the org from the meter / handler context.
+         *
+         */
+        export interface MeterReadingChangesetEntry {
+            value: number;
+            direction?: "feed-in" | "feed-out";
+            timestamp?: string; // date-time
+            meter_id: string; // uuid
+            counter_id: string; // uuid
+            source?: string;
+            reason?: string;
+            read_by?: string;
+            status?: "valid" | "in-validation" | "implausible";
+            external_id?: string;
+            remark?: string;
+            metadata?: {
+                [name: string]: string;
+            };
+            /**
+             * Unique changeset identifier (UUID v4).
+             */
+            changeset_id: string;
+            edit_mode: "external" | "approval";
+            match_strategy?: "exact" | "fuzzy";
+            /**
+             * Slack on `reading.timestamp` when metering-api auto-clear matches an
+             * incoming reading against this pending changeset.
+             *
+             * Variants:
+             * - `'exact'`: strict millisecond equality.
+             * - `{ type: 'same-day', timezone? }`: strip the time component and
+             *   compare year-month-day. Optional `timezone` is an IANA name
+             *   (e.g. `'Europe/Berlin'`); the day is bucketed in that zone.
+             *   Defaults to UTC when omitted.
+             * - `{ type: 'within-seconds', seconds }`: symmetric ±N-second window.
+             *
+             */
+            timestamp_tolerance?: /**
+             * Slack on `reading.timestamp` when metering-api auto-clear matches an
+             * incoming reading against this pending changeset.
+             *
+             * Variants:
+             * - `'exact'`: strict millisecond equality.
+             * - `{ type: 'same-day', timezone? }`: strip the time component and
+             *   compare year-month-day. Optional `timezone` is an IANA name
+             *   (e.g. `'Europe/Berlin'`); the day is bucketed in that zone.
+             *   Defaults to UTC when omitted.
+             * - `{ type: 'within-seconds', seconds }`: symmetric ±N-second window.
+             *
+             */
+            ("exact") | {
+                type: "same-day";
+                /**
+                 * IANA timezone identifier (e.g. `'Europe/Berlin'`, `'UTC'`).
+                 * When omitted, the day is bucketed in UTC.
+                 *
+                 */
+                timezone?: string;
+            } | {
+                type: "within-seconds";
+                /**
+                 * Tolerance in seconds. e.g. 60 = ±1 minute, 3600 = ±1 hour.
+                 */
+                seconds: number;
+            };
+            fuzzy_config?: {
+                percentage_threshold?: number;
+                absolute_threshold?: number;
+            };
+            created_at: string; // date-time
+            created_by?: /* Identifies the actor that created the changeset. */ ChangesetCreator;
+            previous?: {
+                value?: number;
+                direction?: "feed-in" | "feed-out";
+                timestamp?: string; // date-time
+            };
+        }
         /**
          * Multi Choice Selection
          */
@@ -6952,26 +7385,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "multiselect" | "checkbox";
             /**
@@ -7074,8 +7522,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -7236,26 +7688,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "number";
             /**
@@ -7422,26 +7889,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "ordered_list";
         }
@@ -7599,26 +8081,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "partner_organisation";
         }
@@ -7776,26 +8273,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "partner_status";
         }
@@ -7953,26 +8465,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "payment";
         }
@@ -8130,26 +8657,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "relation_payment_method";
         }
@@ -8307,26 +8849,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "phone";
         }
@@ -8484,26 +9041,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "portal_access";
         }
@@ -8661,26 +9233,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "price_component";
         }
@@ -8838,26 +9425,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "purpose";
         }
@@ -9030,26 +9632,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval" | "list-view";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "relation";
             relation_type?: "has_many" | "has_one";
@@ -9247,8 +9864,12 @@ declare namespace Components {
             _manifest?: string /* uuid */[] | null;
             /**
              * Pending attribute changesets for attributes configured with external or approval edit mode.
-             * Read-only via normal entity PATCH/PUT operations — cannot be set directly.
-             * Use the changeset management endpoints to apply or dismiss changesets.
+             *
+             * The value shape is `Changeset` (`proposed_value`, `created_at`, `edit_mode`, ...)
+             * and is what `:apply` / `:dismiss` operate on.
+             *
+             * Read-only via normal entity PATCH/PUT operations — those handlers strip `_changesets`
+             * from request bodies. Use the changeset management endpoints to mutate this field.
              *
              */
             _changesets?: {
@@ -9429,26 +10050,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
         }
         /**
@@ -10010,26 +10646,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "select" | "radio";
             options?: ({
@@ -10195,26 +10846,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "sequence";
             /**
@@ -10389,26 +11055,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "status";
             options?: ((string | null) | {
@@ -10662,26 +11343,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "table";
             /**
@@ -10895,26 +11591,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "tags";
             options?: string[];
@@ -11274,26 +11985,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "string";
             multiline?: boolean;
@@ -11464,26 +12190,41 @@ declare namespace Components {
             repeatable?: boolean;
             has_primary?: boolean;
             /**
-             * Controls how updates to this attribute are handled.
-             * - `direct` (default): update is applied immediately. No changeset created.
-             * - `external`: update creates a changeset, auto-cleared on matching external update (e.g. ERP inbound sync via ?direct=true).
-             * - `approval`: update creates a changeset, requires explicit human approval.
+             * Controls how updates to this attribute are handled. See the `EditMode`
+             * schema for the per-mode semantics. Defaults to `direct`.
              *
              */
             edit_mode?: "direct" | "external" | "approval";
             /**
-             * Configuration for non-direct edit modes. Required when edit_mode is external or approval with fuzzy match strategy.
+             * Configuration for auto-clear matching on `edit_mode: external` attributes.
+             * `match_strategy` and `fuzzy_config` are only consulted for `external` mode —
+             * they are ignored for `approval` mode, which resolves via explicit
+             * `:apply` / `:dismiss` endpoints and never auto-clears.
+             *
              */
             edit_mode_config?: {
                 match_strategy?: /**
-                 * Strategy for auto-clearing the changeset when an external update is received.
+                 * Strategy for auto-clearing a changeset on an `edit_mode: external` attribute
+                 * when a direct write (`?direct=true`) arrives — typically an ERP inbound sync.
+                 * Ignored for `edit_mode: approval`, which does not auto-clear and is resolved
+                 * exclusively via the `:apply` / `:dismiss` changeset endpoints.
                  * - `exact`: The inbound value must exactly match the proposed value (deep equality).
-                 * - `fuzzy`: The inbound value is compared using the configured fuzzy algorithm.
+                 * - `fuzzy`: The inbound value is compared using the configured `fuzzy_config` algorithm.
                  * - `any`: Any update to the attribute clears the changeset, regardless of value.
                  *
                  */
                 MatchStrategy;
-                fuzzy_config?: /* Configuration for fuzzy match strategies on changeset auto-clearing. */ FuzzyConfig;
+                fuzzy_config?: /**
+                 * Configuration for fuzzy auto-clear matching on `edit_mode: external` attributes.
+                 * Not used for `edit_mode: approval`.
+                 *
+                 * Type compatibility with attribute shape is enforced at schema save time:
+                 * - scalar string attributes: `suffix`, `digits_only`, `regex`
+                 * - repeatable attributes: `set_equivalent`, `entry_match`, `ignore_fields`, `normalize_phone`
+                 * - relation attributes: `relation_set`
+                 *
+                 */
+                FuzzyConfig;
             };
             type: "relation_user";
             multiple?: boolean;
@@ -17691,6 +18432,7 @@ export type CurrencyAttribute = Components.Schemas.CurrencyAttribute;
 export type DateAttribute = Components.Schemas.DateAttribute;
 export type DefaultAddressFields = Components.Schemas.DefaultAddressFields;
 export type ESClusterAssignment = Components.Schemas.ESClusterAssignment;
+export type EditMode = Components.Schemas.EditMode;
 export type EditModeConfig = Components.Schemas.EditModeConfig;
 export type EmailAttribute = Components.Schemas.EmailAttribute;
 export type Entity = Components.Schemas.Entity;
@@ -17756,6 +18498,7 @@ export type LinkAttribute = Components.Schemas.LinkAttribute;
 export type ListSavedViewsResults = Components.Schemas.ListSavedViewsResults;
 export type MatchStrategy = Components.Schemas.MatchStrategy;
 export type MessageEmailAddressAttribute = Components.Schemas.MessageEmailAddressAttribute;
+export type MeterReadingChangesetEntry = Components.Schemas.MeterReadingChangesetEntry;
 export type MultiSelectAttribute = Components.Schemas.MultiSelectAttribute;
 export type NullableEntity = Components.Schemas.NullableEntity;
 export type NumberAttribute = Components.Schemas.NumberAttribute;