@remit/api-openapi-spec 0.0.44 → 0.0.46

package/openapi.json

@@ -7072,7 +7072,7 @@
                 "$ref": "#/components/schemas/RemitImap.MessageCategory"
               }
             ],
-            "description": "Header-derived category for the message. Always present: `Message.category` is NOT NULL with an `uncategorized` default, and `uncategorized` names the not-yet-classified state rather than standing for absence (issue #45)."
+            "description": "Header-derived category for the message. Always present: `Message.category` is NOT NULL with an `uncategorized` default, and `uncategorized` is a named value — no category — rather than a stand-in for absence or for `personal` (issue #45)."
           },
           "senderTrust": {
             "allOf": [
@@ -7823,7 +7823,7 @@
           "transactional",
           "social"
         ],
-        "description": "Header-derived message category. Set by classifyByHeaders during body-sync. Defaults to `uncategorized` until the message is body-classified."
+        "description": "Header-derived message category. Set by classifyByHeaders during body-sync. Defaults to `uncategorized`, which covers both a message that has not been classified yet and one the classifier declined to categorize; `Message.classificationState` is what tells those apart."
       },
       "RemitImap.MessageReferenceResponse": {
         "type": "object",
@@ -7871,6 +7871,16 @@
         },
         "description": "Recorded when the user reported this message as spam via `POST /messages/report-spam`. Present means the report stands; absent means never reported, or reported and then undone via `POST /messages/not-spam` (which clears it). Backs the \"Reported as spam · Undo\" affordance independent of the message's current folder — the underlying move can settle, fail, or no-op (already in Junk) without changing whether the report itself is shown."
       },
+      "RemitImap.MessageStatus": {
+        "type": "string",
+        "enum": [
+          "active",
+          "deleting",
+          "deleted",
+          "moving"
+        ],
+        "description": "Message lifecycle status for move/delete operations"
+      },
       "RemitImap.MessageSummaryResponse": {
         "type": "object",
         "required": [
@@ -7878,7 +7888,9 @@
           "mailboxId",
           "uid",
           "rfc822Size",
-          "internalDate"
+          "internalDate",
+          "status",
+          "syncStatus"
         ],
         "properties": {
           "messageId": {
@@ -7924,6 +7936,26 @@
             "description": "Message-ID header value for quick reference",
             "readOnly": true
           },
+          "status": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/RemitImap.MessageStatus"
+              }
+            ],
+            "description": "Message lifecycle status for move/delete operations. Defaults to `active` (normal, visible).",
+            "default": "active",
+            "readOnly": true
+          },
+          "syncStatus": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/RemitImap.MessageSyncStatus"
+              }
+            ],
+            "description": "Sync status for move/delete operations. The `synced` column default only applies to a row written without the field: the repository always supplies one, and an ordinary inbound sync writes `pending`, which nothing later promotes. So `pending` here does not mean an outstanding move or delete — `status` names that, and `failed` marks a mutation that gave up.",
+            "default": "synced",
+            "readOnly": true
+          },
           "authenticity": {
             "allOf": [
               {
@@ -7959,6 +7991,15 @@
         },
         "description": "Core message metadata for API responses"
       },
+      "RemitImap.MessageSyncStatus": {
+        "type": "string",
+        "enum": [
+          "synced",
+          "pending",
+          "failed"
+        ],
+        "description": "Sync status for message move/delete operations"
+      },
       "RemitImap.MintOutboxAttachmentInput": {
         "type": "object",
         "required": [
@@ -9494,7 +9535,9 @@
           "updatedAt",
           "category",
           "senderTrust",
-          "muted"
+          "muted",
+          "status",
+          "syncStatus"
         ],
         "properties": {
           "threadMessageId": {
@@ -9618,7 +9661,7 @@
                 "$ref": "#/components/schemas/RemitImap.MessageCategory"
               }
             ],
-            "description": "Header-derived category for the message, served from the ThreadMessage row. Always present: the column is NOT NULL with an `uncategorized` default, and `uncategorized` is a named value for the not-yet-classified state, never a stand-in for `personal` (issue #45)."
+            "description": "Header-derived category for the message, served from the ThreadMessage row. Always present: the column is NOT NULL with an `uncategorized` default, and `uncategorized` is a named value — no category — never a stand-in for `personal` (issue #45)."
           },
           "senderTrust": {
             "allOf": [
@@ -9640,6 +9683,22 @@
             ],
             "description": "Structured sender-authenticity signal derived from DKIM headers at classification time (from the underlying Message). Absent for messages classified before this field was introduced — absence means no signal."
           },
+          "status": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/RemitImap.MessageStatus"
+              }
+            ],
+            "description": "Mutation lifecycle of the underlying Message, projected at read time — the ThreadMessage row has no column of its own. `active` means no move or delete is outstanding; `moving` or `deleting` means one is, and this row's folder is a local write the mail server has not confirmed."
+          },
+          "syncStatus": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/RemitImap.MessageSyncStatus"
+              }
+            ],
+            "description": "Sync status of the underlying Message, projected at read time. Read it WITH `status`, never alone: `message-move`, `message-delete` and `message-copy` all write `failed` on an ordinary transient attempt before a redelivery that usually succeeds, so `failed` by itself does not mean a mutation gave up. One pair does prove one: `active` + `failed`, written only by `abandonDelete` — a delete Remit refused to run and handed back. Nothing else here is decidable. A move that gave up leaves `moving` + `failed`, the same pair its first dropped connection leaves; a delete that exhausted its retries is repaired to `active` + `synced` and reads as settled; `flag-push` and `placement-move-push` never write either field."
+          },
           "accountId": {
             "allOf": [
               {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-spec",
-  "version": "0.0.44",
+  "version": "0.0.46",
   "description": "Remit API OpenAPI 3 document, generated from TypeSpec.",
   "exports": {
     ".": "./openapi.json",