@hunt-labs/bytekit-sdk 0.11.8 → 0.11.9

package/CHANGELOG.md

@@ -10,6 +10,17 @@ today, see [README.md](./README.md), which remains the authoritative usage guide
 
 ## [Unreleased]
 
+## [0.11.9] - 2026-10-02
+
+### Changed
+
+- **Terms-version doc comments describe the new onboarding contract (#5055).** Bootstrap no
+  longer records Terms acceptance: the internal `POST /v1/account/bootstrap` `terms_version` body
+  is now documented as a version guard, with acceptance recorded by
+  `POST /v1/account/accept-terms`. The account `terms_version` description now says an empty
+  string means the account has not accepted the Terms yet. Regenerated `src/generated/api.d.ts`;
+  description text only, no type or SDK method signature moves.
+
 ## [0.11.8] - 2026-09-30
 
 ### Changed

package/dist/generated/api.d.ts

@@ -644,9 +644,6 @@ export interface paths {
          *     endpoint factor (a 100 KiB estimate is pre-charged, then reconciled). The
          *     bandwidth is still billed when the scrape succeeds but extraction later
          *     fails; both axes are refunded only when the scrape itself never runs.
-         *
-         *     Availability is gated by a server-side feature flag; when disabled the
-         *     endpoint returns `404`.
          */
         post: operations["createSchemaExtraction"];
         delete?: never;
@@ -2730,7 +2727,7 @@ export interface components {
                 /** @description Whether the account admin wants an email when bandwidth reaches 100 % of the plan limit. */
                 bandwidth_100_enabled: boolean;
             };
-            /** @description The Terms of Service version this account has accepted. An empty string means the account predates clickwrap acceptance (issue #1025). The dashboard diffs this against the published current version to decide whether to show the re-acceptance prompt. */
+            /** @description The Terms of Service version this account has accepted. An empty string means the account has not accepted the Terms yet; acceptance is recorded only by `POST /v1/account/accept-terms`, never by bootstrap (issue #5055). The dashboard diffs this against the published current version to decide whether to show the re-acceptance prompt. */
             terms_version: string;
             /** Format: date-time */
             created_at: string;
@@ -2768,7 +2765,7 @@ export interface components {
                 /** @description Whether the account admin wants an email when bandwidth reaches 100 % of the plan limit. */
                 bandwidth_100_enabled: boolean;
             };
-            /** @description The Terms of Service version this account has accepted. An empty string means the account predates clickwrap acceptance (issue #1025). The dashboard diffs this against the published current version to decide whether to show the re-acceptance prompt. */
+            /** @description The Terms of Service version this account has accepted. An empty string means the account has not accepted the Terms yet; acceptance is recorded only by `POST /v1/account/accept-terms`, never by bootstrap (issue #5055). The dashboard diffs this against the published current version to decide whether to show the re-acceptance prompt. */
             terms_version: string;
             /** @description True when the account has a Stripe subscription, keyed on the same `stripe_subscription_id` column that GET /v1/billing/change-plan's `no_subscription` guard tests. */
             has_subscription: boolean;
@@ -5920,15 +5917,6 @@ export interface operations {
                 };
             };
             402: components["responses"]["PaymentRequired"];
-            /** @description Endpoint not available (feature flag disabled). */
-            404: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    "application/json": components["schemas"]["Error"];
-                };
-            };
             /** @description Validation error (`validation_error`) or non-normalizable schema (`schema_incompatible`). */
             422: {
                 headers: {
@@ -7110,11 +7098,11 @@ export interface operations {
             path?: never;
             cookie?: never;
         };
-        /** @description Optional clickwrap acceptance signal (issue #1025). When present, terms_version MUST equal the published current version or the request is rejected with 400 terms_version_mismatch. When absent, the server stamps the current version server-side (back-compatible). */
+        /** @description Optional Terms version guard (issue #1025). When present, terms_version MUST equal the published current version or the request is rejected with 400 terms_version_mismatch. It is never recorded as acceptance: a new account starts with an empty terms_version, and acceptance is recorded only by POST /v1/account/accept-terms. When absent, the guard is skipped (back-compatible). */
         requestBody?: {
             content: {
                 "application/json": {
-                    /** @description The Terms of Service version the user is accepting. */
+                    /** @description The Terms of Service version the client was built against. Checked against the current version, never recorded as acceptance. */
                     terms_version?: string;
                 };
             };
@@ -7138,7 +7126,7 @@ export interface operations {
                     "application/json": components["schemas"]["Account"];
                 };
             };
-            /** @description terms_version does not match the published current version. */
+            /** @description terms_version does not match the published current version (version guard only; acceptance is recorded by POST /v1/account/accept-terms). */
             400: {
                 headers: {
                     [name: string]: unknown;

package/dist/version.d.ts

@@ -5,4 +5,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export declare const SDK_VERSION = "0.11.8";
+export declare const SDK_VERSION = "0.11.9";

package/dist/version.js

@@ -9,4 +9,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export const SDK_VERSION = '0.11.8';
+export const SDK_VERSION = '0.11.9';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hunt-labs/bytekit-sdk",
-  "version": "0.11.8",
+  "version": "0.11.9",
   "description": "Official TypeScript SDK for the ByteKit API",
   "license": "MIT",
   "type": "module",