@curviate/sdk 0.31.0 → 0.33.0

package/CHANGELOG.md

@@ -7,6 +7,102 @@ Versioning: semantic. Minor for additive changes, patch for bug fixes; no stabil
 
 ---
 
+## [0.33.0] - 2026-09-17
+
+The InMail subject on the message reads, now typed. Fixture and types
+regenerated against the deployed production document
+(`https://api.curviate.com`, 127 paths, server `a38f685e`); the exact source
+commit is recorded in `fixtures/PROVENANCE.json`.
+
+### Added
+
+- **`MessageDetail["specifics"]`** types as `{ subject?: string | null }`, on
+  `messaging.getMessage()` and each item of `messaging.listMessages()`. The
+  served object is narrowed to `subject` alone (`additionalProperties: false`).
+  `getChat()`, `listChats()` and `inboxes.listChats()` carry no `specifics` on
+  their embedded `last_message`.
+
+### Changed
+
+- **`recruiter.startChat()` `follow_up.subject` retention copy corrected.** It
+  previously read "Never stored and never logged, on any path", which is not
+  supportable: a Recruiter follow-up is an InMail, so once sent it lands in the
+  classic InMail inbox that the chat reads harvest. The served document now
+  states the conditional, and the regenerated types and fixture carry it.
+- **`messages.sendInmail()` `text`** and the `last_message` descriptions on the
+  chat reads carry the same corrected retention wording.
+
+### Documented
+
+- **`messaging.listMessages()` / `messaging.getMessage()`**: an InMail thread's
+  subject line arrives on a message as `specifics.subject`, set on the thread's
+  opening message. The chat object carries no subject at all, and `chat.name` is
+  the counterpart's display name, so the subject is read off the first message
+  and not off the chat. An ordinary message returns `specifics: {}`. The served
+  `specifics` object is narrowed to `subject` alone.
+- **`messaging.getChat()` / `listChats()` / `inboxes.listChats()`**: a chat read
+  carries no subject anywhere, its embedded `last_message` included. The preview
+  is deliberately narrower than a message read so that a chat read returns the
+  same fields whether it was answered live or from Curviate's stored copy. Read
+  the chat's messages to get a subject.
+
+### Fixture drift swept in by the refresh
+
+The refresh also picked up already-deployed drift the previous fixture lagged
+(it was captured from staging `c98d526`, 2026-09-15). All of it is real served
+state, verified against both `api.curviate.com` and `api.staging.curviate.com`:
+
+- Error-response `examples` blocks removed on **144** operations (343 response
+  slots), on status codes 409, 422, 503 and 504 only. This is server commit
+  `57afde5c5`, "error examples use only codes the API emits", which landed
+  immediately after the previous fixture's base. The earlier estimate of ~38
+  operations undercounted.
+- Prose corrections to a handful of already-served descriptions: the 503 on the
+  applicant-résumé read now names its code, the Sales Navigator chat 422 names
+  only the code it emits, the auth-intent 402 describes both codes it can
+  carry, and the safety-policy descriptions drop raw path templates and say
+  "tenant" rather than "workspace".
+
+---
+
+## [0.32.0] - 2026-09-15
+
+Seat discovery for connecting an account. Additive; nothing removed or renamed.
+
+Fixture and types regenerated against the deployed staging document
+(`https://api.staging.curviate.com`, 127 paths); the exact source commit is
+recorded in `fixtures/PROVENANCE.json`.
+
+### Added
+
+- **`accounts.listSeats()`** (`GET /v1/accounts/seats`). Returns
+  `{ object: "seat_list", items: { seat_id, occupied, account_id }[] }`: the
+  workspace's live seats, whether an account occupies each, and that account
+  (`null` when free). Not paginated. An empty seat is listed only when
+  connecting an account to it would be accepted right now, so an empty seat
+  that is provisional, cancelling, on an ended trial or blocked by billing is
+  left out, and `items` can be `[]` while the workspace still has seats. Any seat with `occupied: false` is a valid `seat_id` for connecting a new
+  account with `auth.intent`, so a connect no longer needs a seat id copied
+  from the dashboard. Carries no billing fields. The response type is
+  exported as `SeatList`.
+
+- **Types only: `GET` and `PATCH /v1/safety-policy`** (tenant-wide safety
+  defaults per limit profile and budget row). The generated `paths` type now
+  describes them; there is no resource method yet, so call them through your
+  own request if you need them today.
+
+### Changed
+
+- `auth.intent` documentation now points to `accounts.listSeats()` for finding
+  a free seat, matching the regenerated `seat_id` description.
+- Regenerated descriptions on `GET` and `PATCH /v1/{account_id}/safety-policy`:
+  an account's values now resolve from its own setting, then the tenant
+  default for its `limit_profile`, then the Curviate default, and `null` on the
+  account write restores the tenant default where one is set. Documentation
+  only; no type moved.
+
+---
+
 ## [0.31.0] - 2026-09-11
 
 Step two of the tier retirement, plus one billing refusal this SDK was about to

package/README.md

@@ -113,7 +113,8 @@ try {
       // Curviate's OWN account-safety ceiling, not a request-rate limit:
       // nothing reached LinkedIn and nothing was spent, so backing off is the
       // wrong move. Wait until err.resetAt, or raise the setting the hint
-      // names on PATCH /v1/{account_id}/safety-policy.
+      // names on PATCH /v1/{account_id}/safety-policy. The ceiling comes from the
+      // account's safety policy or the tenant default (GET/PATCH /v1/safety-policy).
       // resetAt is null in the two cases no clock frees: the pending_invites
       // backlog, and an InMail credit pool LinkedIn regrants on its own schedule.
       console.warn(`${err.budgetRow} is spent until ${err.resetAt ?? "no fixed time"}`);