@remit/api-openapi-types 0.0.20 → 0.0.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-types",
-  "version": "0.0.20",
+  "version": "0.0.21",
   "type": "module",
   "main": "types.d.ts",
   "types": "types.d.ts",

package/types.d.ts

@@ -1466,9 +1466,13 @@ data through `byAccountAndState`.
        */
       hasAnchor: boolean;
       /**
-       * Epoch seconds, written only when the predicate (literalClauses, hasAnchor) or the action (actionLabelId, actionMailboxId) changes — never on a cosmetic rename. Backs most-recently-changed-filter-wins precedence for the exclusive move action (RFC 034 Decision 3.2). Distinct from ElectroDB's own updatedAt, which bumps on any write.
+       * Epoch seconds, written whenever the predicate, the action, the scope, or the expiry changes (reader #266) — never on a cosmetic rename. This is the broad "the user asserted something new about this rule" signal the settings UI uses to decide whether to re-offer a lapsed filter's back-application. It is deliberately NOT the precedence signal for the exclusive move action — see actionChangedAt for that (RFC 034 Decision 3.2, reader #384). Distinct from ElectroDB's own updatedAt, which bumps on any write.
        */
       ruleChangedAt: number;
+      /**
+       * Epoch seconds, written only when the predicate (literalClauses, hasAnchor) or the action (actionLabelId, actionMailboxId) changes — never on scope, expiresAt, or a cosmetic rename. Backs most-recently-changed-filter-wins precedence for the exclusive move action (RFC 034 Decision 3.2). Split out from ruleChangedAt (reader #384): extending a filter's expiry or flipping its scope changes its lifecycle, not what it matches or does, so it must not promote the filter to move-winner.
+       */
+      actionChangedAt: number;
       /**
        * How literalClauses combine. Meaningless when literalClauses is empty.
        */
@@ -1482,7 +1486,7 @@ data through `byAccountAndState`.
        */
       actionLabelId: string;
       /**
-       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest ruleChangedAt wins. `"None"` means no move action.
+       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest actionChangedAt wins. `"None"` means no move action.
        */
       actionMailboxId: string;
       createdAt: number;
@@ -1534,9 +1538,13 @@ data through `byAccountAndState`.
        */
       hasAnchor: boolean;
       /**
-       * Epoch seconds, written only when the predicate (literalClauses, hasAnchor) or the action (actionLabelId, actionMailboxId) changes — never on a cosmetic rename. Backs most-recently-changed-filter-wins precedence for the exclusive move action (RFC 034 Decision 3.2). Distinct from ElectroDB's own updatedAt, which bumps on any write.
+       * Epoch seconds, written whenever the predicate, the action, the scope, or the expiry changes (reader #266) — never on a cosmetic rename. This is the broad "the user asserted something new about this rule" signal the settings UI uses to decide whether to re-offer a lapsed filter's back-application. It is deliberately NOT the precedence signal for the exclusive move action — see actionChangedAt for that (RFC 034 Decision 3.2, reader #384). Distinct from ElectroDB's own updatedAt, which bumps on any write.
        */
       ruleChangedAt: number;
+      /**
+       * Epoch seconds, written only when the predicate (literalClauses, hasAnchor) or the action (actionLabelId, actionMailboxId) changes — never on scope, expiresAt, or a cosmetic rename. Backs most-recently-changed-filter-wins precedence for the exclusive move action (RFC 034 Decision 3.2). Split out from ruleChangedAt (reader #384): extending a filter's expiry or flipping its scope changes its lifecycle, not what it matches or does, so it must not promote the filter to move-winner.
+       */
+      actionChangedAt: number;
       /**
        * How literalClauses combine. Meaningless when literalClauses is empty.
        */
@@ -1550,7 +1558,7 @@ data through `byAccountAndState`.
        */
       actionLabelId: string;
       /**
-       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest ruleChangedAt wins. `"None"` means no move action.
+       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest actionChangedAt wins. `"None"` means no move action.
        */
       actionMailboxId: string;
       createdAt: number;
@@ -1592,7 +1600,7 @@ sets `hasAnchor`. Absent for a purely-literal filter.
        */
       actionLabelId: string;
       /**
-       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest ruleChangedAt wins. `"None"` means no move action.
+       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest actionChangedAt wins. `"None"` means no move action.
        */
       actionMailboxId: string;
       /**
@@ -1604,10 +1612,13 @@ sets `hasAnchor`. Absent for a purely-literal filter.
      * Input for updating a filter (RFC 034, reader #266). The name, predicate,
 action, scope, and expiresAt are all updatable; `ttl` is always
 server-derived from `scope`/`expiresAt`, never client-supplied, and
-`state`/`hasAnchor`/`ruleChangedAt`/`filterId` are server-derived too. A
-patch touching the predicate, the action, `scope`, or `expiresAt` bumps
-`ruleChangedAt`; a name-only rename never does (RFC 034 Decision 3.2, reader
-#266).
+`state`/`hasAnchor`/`ruleChangedAt`/`actionChangedAt`/`filterId` are
+server-derived too. A patch touching the predicate, the action, `scope`, or
+`expiresAt` bumps `ruleChangedAt`; a name-only rename never does (RFC 034
+Decision 3.2, reader #266). Only a patch touching the predicate or the
+action bumps `actionChangedAt`, the narrower signal exclusive-move
+precedence reads (reader #384) — a scope/expiresAt-only edit leaves it
+untouched.
 
 The semantic anchor has no field here at all — it is set once, from
 `anchorMessageId`, only on `CreateFilterInput`. Repointing an anchor would
@@ -1641,7 +1652,7 @@ anchor change through this body (reader #266).
        */
       actionLabelId: string;
       /**
-       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest ruleChangedAt wins. `"None"` means no move action.
+       * Mailbox matched messages are moved into — exclusive action, since a message lives in exactly one mailbox (RFC 034 Decision 3.1). On conflict between filters, the one with the latest actionChangedAt wins. `"None"` means no move action.
        */
       actionMailboxId: string;
     }