@pidgeon-ai/sdk 1.4.0 → 1.8.0

package/CHANGELOG.md

@@ -9,6 +9,69 @@ call shapes, the result shape — not to the API behind it.
 
 ## Unreleased
 
+## 1.8.0 — wait for a message, and read the code out of it
+
+**`messagesAwait`** (`GET /v1/messages/await`) holds the request open until a
+message matching your filters arrives at an address — `from`, `subject_contains`,
+`has_code` — or `timeout` seconds pass, up to 280. It answers
+`{ message, timed_out, cursor }`; pass `cursor` back as `after` so a message
+arriving between two calls is never missed. One call where an agent waiting
+for a sign-up code used to write a polling loop.
+
+**Every `Message` carries `extracted`**: `codes` and `links`, most likely
+first, each with its kind. Candidates rather than one answer, because
+extraction is a heuristic — take the first, and when it fails the second is
+right there. Read from the new text, never the quoted history.
+
+## 1.7.0 — a pod's reputation you can see
+
+`GET /metrics` takes `pod_id`, and its window carries `pod` and `reputation`.
+1.6.0 claimed each pod had its own sending reputation and gave no way to
+check it; this is the check. `/metrics` also rejects an unknown query
+parameter instead of ignoring it, so a caller passing a misspelt filter is
+told rather than answered for the whole account.
+
+## 1.6.0 — a pod is a boundary now
+
+**No field changed.** What changed is what a pod means, and that is worth a
+release because 1.5.0's own description told you the opposite.
+
+**Each pod has its own sending reputation.** Bounces and complaints from one
+customer's mail are counted against that customer's pod and nothing else, so
+one bad tenant cannot degrade delivery for the rest. Mail from an address in
+a pod sends under that pod whichever domain it is on, so two pods sharing one
+domain are still separate.
+
+1.5.0 said _"a pod carries no sending reputation of its own"_, which was true
+and is not. Leaving it would be the worse kind of stale documentation — a
+caller reading it would decline to use something they already have.
+
+A pod is still **not** a key scope. A key is a list of address ids, which is
+what makes its reach checkable.
+
+## 1.5.0 — a container your customers live in
+
+**Additive.** Every account has exactly one pod already, every address is in
+it, and a caller who never mentions a pod cannot tell this release from the
+last one.
+
+**Added.** `podsList`, `podsCreate`, `podsGet`, `podsUpdate`, the `Pod` type,
+`pod_id` on an address, and `pod_id` as a filter on `identitiesList`.
+
+A **pod** holds addresses and domains: one of your customers, a client, or
+just test kept apart from production. It has a name and an optional
+`client_id` that is your own id for it, carried and never parsed.
+
+**It is organisational and not a boundary**, and the types say so because the
+risk in shipping the container before the isolation is a reader assuming the
+isolation. A pod carries no sending reputation of its own — one SES tenant
+per _account_, unchanged — and **a key is still a list of address ids**,
+never something scoped to a pod.
+
+**No delete.** The verb that destroys a container full of mailboxes is worth
+making somebody ask for, and nothing yet moves addresses between pods, so it
+would either refuse every non-empty pod or destroy mail.
+
 ## 1.4.0 — things the prose promised and the types did not have
 
 **Additive, and two corrections to descriptions that were wrong.**

package/dist/index.cjs

@@ -93,6 +93,7 @@ __export(index_exports, {
   mailboxesListFolder: () => mailboxesListFolder,
   meGet: () => meGet,
   messagesAct: () => messagesAct,
+  messagesAwait: () => messagesAwait,
   messagesForward: () => messagesForward,
   messagesGet: () => messagesGet,
   messagesListInThread: () => messagesListInThread,
@@ -105,6 +106,10 @@ __export(index_exports, {
   messagesUndo: () => messagesUndo,
   messagesUpdate: () => messagesUpdate,
   metricsQuery: () => metricsQuery,
+  podsCreate: () => podsCreate,
+  podsGet: () => podsGet,
+  podsList: () => podsList,
+  podsUpdate: () => podsUpdate,
   routingCreate: () => routingCreate,
   routingDelete: () => routingDelete,
   routingList: () => routingList,
@@ -1059,6 +1064,34 @@ var identitiesSuspendTenant = (options) => (options.client ?? client).post({
   url: "/tenants/{id}/suspend",
   ...options
 });
+var podsList = (options) => (options?.client ?? client).get({
+  security: [{ scheme: "bearer", type: "http" }],
+  url: "/pods",
+  ...options
+});
+var podsCreate = (options) => (options.client ?? client).post({
+  security: [{ scheme: "bearer", type: "http" }],
+  url: "/pods",
+  ...options,
+  headers: {
+    "Content-Type": "application/json",
+    ...options.headers
+  }
+});
+var podsGet = (options) => (options.client ?? client).get({
+  security: [{ scheme: "bearer", type: "http" }],
+  url: "/pods/{id}",
+  ...options
+});
+var podsUpdate = (options) => (options.client ?? client).patch({
+  security: [{ scheme: "bearer", type: "http" }],
+  url: "/pods/{id}",
+  ...options,
+  headers: {
+    "Content-Type": "application/json",
+    ...options.headers
+  }
+});
 var labelsList = (options) => (options.client ?? client).get({
   security: [{ scheme: "bearer", type: "http" }],
   url: "/labels",
@@ -1143,6 +1176,11 @@ var messagesUndo = (options) => (options.client ?? client).post({
     ...options.headers
   }
 });
+var messagesAwait = (options) => (options.client ?? client).get({
+  security: [{ scheme: "bearer", type: "http" }],
+  url: "/messages/await",
+  ...options
+});
 var messagesGet = (options) => (options.client ?? client).get({
   security: [{ scheme: "bearer", type: "http" }],
   url: "/messages/{id}",
@@ -1822,6 +1860,7 @@ function sleep(ms, signal) {
   mailboxesListFolder,
   meGet,
   messagesAct,
+  messagesAwait,
   messagesForward,
   messagesGet,
   messagesListInThread,
@@ -1834,6 +1873,10 @@ function sleep(ms, signal) {
   messagesUndo,
   messagesUpdate,
   metricsQuery,
+  podsCreate,
+  podsGet,
+  podsList,
+  podsUpdate,
   routingCreate,
   routingDelete,
   routingList,