@remit/api-openapi-spec 0.0.6 → 0.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/openapi.json +3 -4
  2. package/package.json +1 -1
package/openapi.json CHANGED
@@ -4921,18 +4921,17 @@
4921
4921
  "RemitImap.QuarantineFailureCode": {
4922
4922
  "type": "string",
4923
4923
  "enum": [
4924
- "UnterminatedMultipartBoundary",
4925
4924
  "UnknownCharset",
4926
- "TruncatedBody"
4925
+ "UnreadableBody"
4927
4926
  ],
4928
- "description": "The specific defect within a stage.\n\nClosed rather than free text: this is the one diagnostic that is interpolated\ninto the title of an issue filed under the user's own GitHub account, so its\npublishability has to be a property of the type instead of a claim about the\nwriter. Grows with the same narrowing that grows QuarantineFailureStage."
4927
+ "description": "The specific defect within a stage.\n\nClosed rather than free text: this is the one diagnostic that is interpolated\ninto the title of an issue filed under the user's own GitHub account, so its\npublishability has to be a property of the type instead of a claim about the\nwriter.\n\nThe vocabulary is total — every quarantine write picks a member, and a defect\nthe writer cannot name is `UnreadableBody` rather than an invented code. It\nis deliberately small: the body parser reports its refusals as free text with\nno stable type or code, so a member exists only where the writer can identify\nthe defect without reading parser prose. `UnterminatedMultipartBoundary` and\n`TruncatedBody` were provisional members carried by Phase 2 and are gone —\nnothing on the narrowed sync path could produce either, and a member no\nwriter can reach is a vocabulary that lies about what the field means.\n`MissingEnvelope` is absent for the same reason: see QuarantineFailureStage."
4929
4928
  },
4930
4929
  "RemitImap.QuarantineFailureStage": {
4931
4930
  "type": "string",
4932
4931
  "enum": [
4933
4932
  "BodyParse"
4934
4933
  ],
4935
- "description": "The pipeline step that refused a quarantined message.\n\nOne member. No catch site on the sync path can currently tell a parse failure\nfrom an infrastructure failure: the per-message frame in `body-sync.ts` wraps\nthe S3 body write, the parsed-body cache write, the body-part upserts, the\nplacement move and the label and counter writes alongside the `simpleParser`\ncall, and filters only connection drops out of it. A stage is added when a\ntry block is narrowed far enough to attribute it, never ahead of that an\nenum member that reached stored rows cannot be walked back."
4934
+ "description": "The pipeline step that refused a quarantined message.\n\nOne member, and it is behind a real narrowing rather than a promise of one:\nthe body parse has its own try block around the parse call and nothing else,\nso an error out of it can only be the message. S3, queue and database\nfailures propagate and never become a record here quarantining one would\nset a message aside for an outage, tell the user it was unreadable, and\ninvite a public GitHub issue about it.\n\nA message that arrives with no ENVELOPE is deliberately NOT a member. Nothing\ncan tell that apart from the FETCH row glitching (#408), and the IMAP client\nis far more often the cause than the message; the sync path holds its cursor\nand retries instead, so a transient glitch heals and a persistent one trips\nthe stalled-cursor alert."
4936
4935
  },
4937
4936
  "RemitImap.QuarantineListResponse": {
4938
4937
  "type": "object",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/api-openapi-spec",
3
- "version": "0.0.6",
3
+ "version": "0.0.7",
4
4
  "description": "Remit API OpenAPI 3 document, generated from TypeSpec.",
5
5
  "exports": {
6
6
  ".": "./openapi.json",