@remit/api-openapi-types 0.0.14 → 0.0.16

package/package.json

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

package/types.d.ts

@@ -1360,6 +1360,10 @@ never from a raw content-type line — parameters carry `name=` and
        * Timestamp of the last successful message sync
        */
       lastMessageSyncAt: number;
+      /**
+       * Sync status for mailbox operations (create, rename, delete)
+       */
+      syncStatus?: MailboxSyncStatus;
       /**
        * Denormalized list of IMAP SPECIAL-USE designations (RFC 6154). Populated from the same `\Sent`, `\Drafts`, etc. attributes the server reports during LIST. Stored on the row to avoid an N+1 join when listing mailboxes.
        */
@@ -1438,11 +1442,11 @@ data through `byAccountAndState`.
        */
       name: String256;
       /**
-       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1).
+       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1). Mutable on update (reader #266): switching scope re-derives ttl and re-evaluates state from expiresAt, and bumps ruleChangedAt so a lapsed filter's back-application can be offered again. The semantic anchor stays immutable regardless — repointing it would silently change what a saved filter matches with nothing visible changing, which deserves a new filter instead.
        */
       scope: FilterScope;
       /**
-       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence.
+       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence. Mutable on update (reader #266), alongside scope — moving the date bumps ruleChangedAt the same way a scope change does.
        */
       expiresAt?: string;
       /**
@@ -1510,11 +1514,11 @@ data through `byAccountAndState`.
        */
       name: String256;
       /**
-       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1).
+       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1). Mutable on update (reader #266): switching scope re-derives ttl and re-evaluates state from expiresAt, and bumps ruleChangedAt so a lapsed filter's back-application can be offered again. The semantic anchor stays immutable regardless — repointing it would silently change what a saved filter matches with nothing visible changing, which deserves a new filter instead.
        */
       scope: FilterScope;
       /**
-       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence.
+       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence. Mutable on update (reader #266), alongside scope — moving the date bumps ruleChangedAt the same way a scope change does.
        */
       expiresAt?: string;
       /**
@@ -1564,11 +1568,11 @@ sets `hasAnchor`. Absent for a purely-literal filter.
        */
       name: String256;
       /**
-       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1).
+       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1). Mutable on update (reader #266): switching scope re-derives ttl and re-evaluates state from expiresAt, and bumps ruleChangedAt so a lapsed filter's back-application can be offered again. The semantic anchor stays immutable regardless — repointing it would silently change what a saved filter matches with nothing visible changing, which deserves a new filter instead.
        */
       scope: FilterScope;
       /**
-       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence.
+       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence. Mutable on update (reader #266), alongside scope — moving the date bumps ruleChangedAt the same way a scope change does.
        */
       expiresAt?: string;
       /**
@@ -1593,13 +1597,33 @@ sets `hasAnchor`. Absent for a purely-literal filter.
       anchorMessageId?: UUID;
     }
     /**
-     * Input for updating a filter (RFC 034). Only the mutable name/predicate/action fields are updatable — `scope`, `expiresAt`, and `ttl` are fixed at creation, and `state`/`hasAnchor`/`ruleChangedAt`/`filterId` are server-derived. A patch touching a predicate or action field bumps `ruleChangedAt`; a name-only rename never does (RFC 034 Decision 3.2).
+     * 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).
+
+The semantic anchor has no field here at all — it is set once, from
+`anchorMessageId`, only on `CreateFilterInput`. Repointing an anchor would
+silently change what a saved filter matches with nothing visible changing;
+that deserves a new filter, so the server rejects any attempt to smuggle an
+anchor change through this body (reader #266).
      */
     export interface UpdateFilterInput {
       /**
        * Plain-language name or editable label for this filter
        */
       name: String256;
+      /**
+       * Standing (permanent) or Temporary (expires). Governs whether expiresAt/ttl are present (RFC 034 Decision 1). Mutable on update (reader #266): switching scope re-derives ttl and re-evaluates state from expiresAt, and bumps ruleChangedAt so a lapsed filter's back-application can be offered again. The semantic anchor stays immutable regardless — repointing it would silently change what a saved filter matches with nothing visible changing, which deserves a new filter instead.
+       */
+      scope: FilterScope;
+      /**
+       * ISO 8601 date-time with zone offset, present only when scope is Temporary (RFC 034 Decision 1.1) — a business date, not an epoch instant. Every evaluation compares `now` against this value directly; it is the source of truth for whether a Temporary filter is still active, independent of `state` or row existence. Mutable on update (reader #266), alongside scope — moving the date bumps ruleChangedAt the same way a scope change does.
+       */
+      expiresAt?: string;
       /**
        * How literalClauses combine. Meaningless when literalClauses is empty.
        */