@epilot/entity-client 7.2.0 → 7.2.1

package/dist/openapi.d.ts

@@ -524,18 +524,35 @@ declare namespace Components {
              */
             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?: /**
@@ -727,18 +744,35 @@ declare namespace Components {
              */
             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?: /**
@@ -947,18 +981,35 @@ declare namespace Components {
              */
             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";
         }
@@ -1182,18 +1233,35 @@ declare namespace Components {
              */
             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;
             };
         }
         /**
@@ -1453,18 +1521,35 @@ declare namespace Components {
              */
             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 +1572,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)
              */
@@ -1741,18 +1828,35 @@ declare namespace Components {
              */
             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;
@@ -1927,18 +2031,35 @@ declare namespace Components {
              */
             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;
@@ -2106,18 +2227,35 @@ declare namespace Components {
              */
             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";
         }
@@ -2283,18 +2421,35 @@ declare namespace Components {
              */
             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;
@@ -2470,18 +2625,35 @@ declare namespace Components {
              */
             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 +2694,36 @@ declare namespace Components {
             cluster?: string;
         }
         /**
-         * Configuration for non-direct edit modes on an entity attribute.
+         * 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
@@ -2697,18 +2887,35 @@ declare namespace Components {
              */
             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";
         }
@@ -5216,18 +5423,35 @@ declare namespace Components {
              */
             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 +5478,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 +5509,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.
              */
@@ -6048,18 +6298,35 @@ declare namespace Components {
              */
             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";
         }
@@ -6225,18 +6492,35 @@ declare namespace Components {
              */
             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";
         }
@@ -6402,18 +6686,35 @@ declare namespace Components {
              */
             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";
         }
@@ -6587,18 +6888,35 @@ declare namespace Components {
              */
             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 +6929,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.
          *
          */
@@ -6780,18 +7101,35 @@ declare namespace Components {
              */
             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;
@@ -6960,18 +7298,35 @@ declare namespace Components {
              */
             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";
             /**
@@ -7244,18 +7599,35 @@ declare namespace Components {
              */
             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";
             /**
@@ -7430,18 +7802,35 @@ declare namespace Components {
              */
             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";
         }
@@ -7607,18 +7996,35 @@ declare namespace Components {
              */
             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";
         }
@@ -7784,18 +8190,35 @@ declare namespace Components {
              */
             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";
         }
@@ -7961,18 +8384,35 @@ declare namespace Components {
              */
             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";
         }
@@ -8138,18 +8578,35 @@ declare namespace Components {
              */
             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";
         }
@@ -8315,18 +8772,35 @@ declare namespace Components {
              */
             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";
         }
@@ -8492,18 +8966,35 @@ declare namespace Components {
              */
             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";
         }
@@ -8669,18 +9160,35 @@ declare namespace Components {
              */
             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";
         }
@@ -8846,18 +9354,35 @@ declare namespace Components {
              */
             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";
         }
@@ -9038,18 +9563,35 @@ declare namespace Components {
              */
             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";
@@ -9437,18 +9979,35 @@ declare namespace Components {
              */
             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;
             };
         }
         /**
@@ -10018,18 +10577,35 @@ declare namespace Components {
              */
             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?: ({
@@ -10203,18 +10779,35 @@ declare namespace Components {
              */
             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";
             /**
@@ -10397,18 +10990,35 @@ declare namespace Components {
              */
             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) | {
@@ -10670,18 +11280,35 @@ declare namespace Components {
              */
             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";
             /**
@@ -10903,18 +11530,35 @@ declare namespace Components {
              */
             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[];
@@ -11282,18 +11926,35 @@ declare namespace Components {
              */
             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;
@@ -11472,18 +12133,35 @@ declare namespace Components {
              */
             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;