@curviate/sdk 0.24.2 → 0.25.0

package/CHANGELOG.md

@@ -7,7 +7,130 @@ Versioning: semantic. Minor for additive changes, patch for bug fixes; no stabil
 
 ---
 
-## [Unreleased]
+## [0.25.0] - 2026-09-05
+
+**BREAKING** for a consumer that pinned the old type declarations: `quotas[]`
+on `GET /v1/accounts/{account_id}` is a different array, and `message_id` on
+`startChat`, `sendMessage`, `sendInMail` and the company chat reply is now
+`string | string[] | null` where it was `string`. Both are detailed under
+"Regenerated types" below. Pre-1.0 a breaking change ships as a minor, so a
+caret range on `0.24.x` will not pick this up.
+
+### Added
+
+- **`BUDGET_EXHAUSTED`, the account-safety refusal, and its payload.** A `429`
+  that is Curviate's own ceiling rather than a request-rate limit: nothing
+  reached LinkedIn and nothing was spent. `CurviateError` gains `budgetRow`
+  (wire `row`), `resetAt` (`reset_at`, and `null` in the two cases no clock
+  frees: the `pending_invites` gauge and an InMail credit exhaustion),
+  `safetyHint` (`hint`, the settable parameter
+  on `PATCH /v1/{account_id}/safety-policy`), `safetyReason` (`reason`:
+  `ceiling` or `activity_window`) and `blocked`. All six ride `toJSON()`.
+  The code is deliberately NOT retryable: a monthly row's reset can be weeks
+  out, so a backoff loop burns retries against a wall that will not move.
+  On a successful response the same payload arrives under `safety_warning`
+  with `blocked: false`, typed on the generated response types.
+- **`budgetRow` and `retryAfterSeconds` on a paused-row `PLATFORM_RATE_LIMIT`.**
+  Same wire `row`, different meaning: LinkedIn refused a recent call on that
+  row, so the next one is refused locally until the pause lifts. The pause is
+  scoped to `(account, row)`, so the recovery is to switch work rather than
+  back off across the account. `retry_after` is deliberately NOT folded into
+  `retryAfterMs`, which everything sleeps.
+- **A response carrying `row` is never auto-retried, on any method.**
+- **`LINKEDIN_SESSION_EVICTED`.** A 401 split from `LINKEDIN_AUTH_FAILED`
+  because the remedies differ: reconnecting does nothing while the other
+  session is open. Not retryable.
+
+### Changed
+
+- **Fixture regenerated against the deployed production document**
+  (`https://api.curviate.com`, `git_sha 33b42521...`), and the generated
+  types with it. Two shape changes are BREAKING for a consumer that pinned
+  the old declarations, and one enum widened. See "Regenerated types" below.
+
+### Regenerated types
+
+- **BREAKING - `quotas[]` on `GET /v1/accounts/{account_id}` is a different
+  array.** `quota_name`, `remaining`, `total`, `reset_time` and
+  `recommended_throttle_hint` are gone. Each row now carries `budget_row`,
+  `kind` (`debit` / `tally` / `gauge`), `window`, `window_start`, `resets_at`,
+  `used`, `ceiling`, `effective_ceiling`, `band`, `posture`, `over_default`,
+  `halt` and, on the gauge, `observed_at`. **Compare `used` against
+  `effective_ceiling`**, which is `ceiling` with the account's warm-up ramp
+  applied; on a new account the two differ by roughly a factor of seven.
+  `used` is `null` only on the gauge, and only before anything has observed
+  it. The per-minute REQUEST ceiling is deliberately not in this array.
+- **BREAKING - `message_id` is `string | string[] | null`** on `startChat`,
+  `sendMessage`, `sendInMail` and the company chat reply, where it was
+  `string`. `null` when no message was actually sent, an array when the
+  message was delivered as several, one per attachment. Confirm a send with
+  `chat_id`, which is always present.
+- Chat-search results: `type` gains `channel`. The generated comment used to
+  say search results are never channels; that is no longer true, so an
+  exhaustive `switch` over `type` needs a third arm.
+- Additive: `GET`/`PATCH /v1/{account_id}/safety-policy`,
+  `GET /v1/{account_id}/safety-events`, the four retained-event operations
+  under `/v1/{account_id}/events`, a `SafetyWarning` component reachable as
+  `safety_warning` on 149 success responses, six new optional fields on the
+  shared `Error` component, `coverage` on chat search, `mode` and `max_age`
+  query params on the store-served reads, `account_states[]` on the account
+  resource, and `observed_at` / `source` / `withdrawn` becoming REQUIRED on
+  four entity reads (a response gaining guarantees, not losing them).
+
+- **`postpublish` now notices a stale CLI pin.** After every `npm publish`,
+  `scripts/check-cli-notice.mjs` compares the version just published
+  against what `@curviate/cli` actually declares for `@curviate/sdk` on the
+  registry (never a dist-tag lookup, since `npm view @curviate/sdk version`
+  returns `latest` and this package's own RC/0.x releases route to `--tag
+  next`). Exits non-zero, loudly, when the CLI has not picked up the
+  release yet. It cannot undo the publish and does not try to; it replaces
+  the prior manual runbook step, which could not fail by construction
+  (the SDK-CLI drift-notice defect).
+- `check:clean` now flags a committed npm auth token (`npm_`-prefixed
+  shape), and `.npmrc`/`*.tgz` are gitignored. Same gap as the sibling
+  `cli` package's copy of this scanner (security-auditor F3).
+
+## [0.24.3] - 2026-08-27
+
+Fixture regenerated against the deployed production document
+(`https://api.curviate.com`, `git_sha cf4fc77e...`). Patch: no `ErrorCode`
+change, no runtime change.
+
+These are corrections, not changes. The wire has always sent these shapes;
+the previous declarations described them wrongly, so consumer code that
+type-checked against the old declaration was already failing at runtime.
+Upgrading may turn a consumer's `tsc` red where it was previously green
+against a declaration that did not match reality. That red is the bug
+becoming visible, not a new one.
+
+### Sales Navigator response corrections
+
+- `founded_on`: was an open object, is a `number`
+  (`sales-navigator/search/companies` and `sales-navigator/account-lists`).
+- `websites`, `addresses`: were arrays of open objects, are `string[]`.
+- `contact_info.phones`, `contact_info.emails`: were arrays of open objects,
+  are `string[]`.
+- `specialties`: was `unknown`, is `string[]` on
+  `sales-navigator/search/companies`.
+- Nested `school`, `company` and `organization` references on `education`,
+  `work_experience` and `volunteering` are now declared, each with a
+  nullable `id`.
+- `job_title` and `role` are now required (non-optional) on
+  `work_experience` and `volunteering`.
+
+### Also reflected from production, first fixtured here
+
+- `expand` removed from `GET /v1/{account_id}/chats/search`. The parameter
+  was inert: that endpoint's response is a strict subset that emits no user
+  object, so the expansion had nowhere to land. Its `notices` block goes
+  with it. Removed server-side before this release; every other
+  `expand`-accepting endpoint is unaffected.
+- `quoted` on a message is now declared recursively as a `Message`, so a
+  quoted message carries the full message shape and may itself carry a
+  `quoted`.
+- Wording only: "Provider-enriched detail about the sender" is now
+  "Platform-enriched detail about the sender" (5 occurrences).
+
 
 ## [0.24.2] - 2026-08-24
 

package/README.md

@@ -109,6 +109,16 @@ try {
       // err.retryAfterMs tells you exactly how long to wait
       await sleep(err.retryAfterMs ?? 5_000);
       break;
+    case "BUDGET_EXHAUSTED":
+      // 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.
+      // 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"}`);
+      console.warn(`change ${err.safetyHint?.parameter} to lift it`);
+      break;
     case "ACCOUNT_NOT_FOUND":
       console.error("Account does not exist for this tenant.");
       break;