@remit/api-http-client 0.0.13 → 0.0.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-http-client",
-  "version": "0.0.13",
+  "version": "0.0.14",
   "type": "module",
   "exports": {
     ".": "./index.ts",

package/types.gen.ts

@@ -687,11 +687,11 @@ export type RemitImapCreateFilterInput = {
      */
     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: RemitImapFilterScope;
     /**
-     * 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;
     /**
@@ -999,11 +999,11 @@ export type RemitImapFilterResponse = {
      */
     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: RemitImapFilterScope;
     /**
-     * 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;
     /**
@@ -2222,13 +2222,33 @@ export type RemitImapUpdateAddressInput = {
 };
 
 /**
- * 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 type RemitImapUpdateFilterInput = {
     /**
      * 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?: RemitImapFilterScope;
+    /**
+     * 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.
      */
@@ -2483,11 +2503,11 @@ export type RemitImapFilterResponseWritable = {
      */
     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: RemitImapFilterScope;
     /**
-     * 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;
     /**