@hunt-labs/bytekit-sdk 0.9.3 → 0.10.0

package/dist/index.d.ts

@@ -8,7 +8,7 @@ export type { ScreenshotCreateRequest, ScreenshotCreateResponse, ScreenshotGetRe
 export type { FetchOpts, FetchGetOpts, FetchResult, FetchCacheStatus, FetchBulkCreateRequest, FetchBulkCreateResponse, FetchBulkGetResponse, } from './resources/fetch.js';
 export type { MonitorCreateRequest, MonitorCreateResponse, ListMonitorsParams, MonitorStatus, ListMonitorsResponse, MonitorResponse, MonitorUpdateRequest, UpdateMonitorResponse, ListMonitorCapturesResponse, } from './resources/monitors.js';
 export type { SitemapCreateRequest, SitemapCreateResponse, SitemapGetResponse, } from './resources/sitemap.js';
-export type { BulkCreateRequest, BulkCreateResponse, BulkGetResponse, BulkCancelResponse, ListBulkScreenshotsResponse, } from './resources/bulk.js';
+export type { BulkCreateRequest, BulkCreateResponse, BulkGetResponse, BulkCancelResponse, ListBulkScreenshotsResponse, BulkCompletedWebhook, } from './resources/bulk.js';
 export type { GetAccountResponse, ListApiKeysResponse, CreateApiKeyRequest, CreateApiKeyResponse, GetApiKeyResponse, UpdateApiKeyRequest, UpdateApiKeyResponse, RevealApiKeyResponse, } from './resources/account.js';
 export type { GetUsageResponse, GetUsageDailyParams, GetUsageDailyResponse, GetUsageByEndpointParams, GetUsageByEndpointResponse, } from './resources/usage.js';
 export type { ListWebhookDeliveriesParams, ListWebhookDeliveriesResponse, RetryWebhookDeliveryResponse, } from './resources/webhooks.js';

package/dist/resources/account.d.ts

@@ -69,8 +69,8 @@ declare class ApiKeysResource {
      * from — hence `Promise<void>`.
      *
      * `client.request()` short-circuits an empty body (204 or any empty response)
-     * to `undefined` before it would parse the body as JSON (#2450), so this
-     * method resolves cleanly on the gateway's empty 204 body.
+     * to `undefined` before it would parse the body as JSON, so this
+     * method resolves cleanly on an empty 204 body.
      */
     revoke(id: ApiKeyId, requestOptions?: RequestOptions): Promise<void>;
     /** POST /v1/account/api-keys/{id}/reveal — reveal the plaintext API key value */

package/dist/resources/account.js

@@ -50,8 +50,8 @@ class ApiKeysResource {
      * from — hence `Promise<void>`.
      *
      * `client.request()` short-circuits an empty body (204 or any empty response)
-     * to `undefined` before it would parse the body as JSON (#2450), so this
-     * method resolves cleanly on the gateway's empty 204 body.
+     * to `undefined` before it would parse the body as JSON, so this
+     * method resolves cleanly on an empty 204 body.
      */
     revoke(id, requestOptions) {
         return this.client.request('DELETE', buildPath('/v1/account/api-keys/{id}', { segments: { id } }), undefined, requestOptions);

package/dist/resources/bulk.d.ts

@@ -1,5 +1,5 @@
 import type { ByteKit, RequestOptions } from '../client.js';
-import type { operations } from '../generated/api.js';
+import type { components, operations } from '../generated/api.js';
 import type { BulkId } from '../types.js';
 /** Body of POST /v1/bulk. */
 export type BulkCreateRequest = operations['createBulk']['requestBody']['content']['application/json'];
@@ -11,6 +11,17 @@ export type BulkGetResponse = operations['getBulk']['responses'][200]['content']
 export type BulkCancelResponse = operations['deleteBulk']['responses'][200]['content']['application/json'];
 /** 200 payload of GET /v1/bulk/{id}/screenshots. */
 export type ListBulkScreenshotsResponse = operations['listBulkScreenshots']['responses'][200]['content']['application/json'];
+/**
+ * Body ByteKit POSTs to your webhook endpoint with `X-ByteKit-Event: bulk.completed`.
+ *
+ * #4340: indexed from `components` rather than `operations` because no operation
+ * `$ref`s this schema — it describes a request WE make to the customer's server,
+ * not a response they read from ours. It is still generated output: the alias
+ * below indexes `src/generated/api.d.ts`, so it cannot drift from the spec.
+ */
+export type BulkCompletedWebhook = components['schemas']['BulkCompletedWebhook'];
+/** Cursor, page-size, and item-status filters for mixed bulk recovery. */
+export type BulkPageParams = NonNullable<operations['listBulkScreenshots']['parameters']['query']>;
 export declare class BulkResource {
     private readonly client;
     readonly screenshots: BulkScreenshotsResource;
@@ -30,7 +41,8 @@ export declare class BulkResource {
 declare class BulkScreenshotsResource {
     private readonly client;
     constructor(client: ByteKit);
-    /** GET /v1/bulk/{id}/screenshots — list screenshots in a bulk job */
+    /** GET /v1/bulk/{id}/screenshots — list items in a mixed bulk job */
     list(id: BulkId, requestOptions?: RequestOptions): Promise<ListBulkScreenshotsResponse>;
+    list(id: BulkId, pageParams: BulkPageParams, requestOptions?: RequestOptions): Promise<ListBulkScreenshotsResponse>;
 }
 export {};

package/dist/resources/bulk.js

@@ -1,4 +1,5 @@
 import { buildPath } from '../client.js';
+import { toQueryString } from './query-string.js';
 export class BulkResource {
     client;
     screenshots;
@@ -29,8 +30,18 @@ class BulkScreenshotsResource {
     constructor(client) {
         this.client = client;
     }
-    /** GET /v1/bulk/{id}/screenshots — list screenshots in a bulk job */
-    list(id, requestOptions) {
-        return this.client.request('GET', buildPath('/v1/bulk/{id}/screenshots', { segments: { id } }), undefined, requestOptions);
+    list(id, pageParamsOrRequestOptions = {}, requestOptions) {
+        const hasPageParams = requestOptions !== undefined ||
+            'cursor' in pageParamsOrRequestOptions ||
+            'limit' in pageParamsOrRequestOptions ||
+            'status' in pageParamsOrRequestOptions;
+        const pageParams = hasPageParams ? pageParamsOrRequestOptions : {};
+        const resolvedRequestOptions = hasPageParams
+            ? requestOptions
+            : pageParamsOrRequestOptions;
+        return this.client.request('GET', buildPath('/v1/bulk/{id}/screenshots', {
+            segments: { id },
+            query: toQueryString(pageParams),
+        }), undefined, resolvedRequestOptions);
     }
 }

package/dist/resources/fetch.d.ts

@@ -7,6 +7,8 @@ export type FetchBulkCreateRequest = operations['createFetchBulk']['requestBody'
 export type FetchBulkCreateResponse = operations['createFetchBulk']['responses'][202]['content']['application/json'];
 /** 200 payload of GET /v1/fetch/bulk/{id}. */
 export type FetchBulkGetResponse = operations['getFetchBulk']['responses'][200]['content']['application/json'];
+/** Cursor, page-size, and item-status filters for fetch-bulk recovery. */
+export type FetchBulkPageParams = NonNullable<operations['getFetchBulk']['parameters']['query']>;
 /**
  * Options for fetch endpoints.
  *
@@ -108,7 +110,7 @@ export declare class FetchResource {
      * raw JSON string, not a parsed object.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
-     * optional caller `signal`. It matters most here: the gateway's own ceiling for a
+     * optional caller `signal`. It matters most here: ByteKit's own ceiling for a
      * fetch is 60 s, so without a per-call budget a slow upstream holds the caller for
      * the constructor default (2 minutes) rather than a duration the caller chose.
      */
@@ -126,7 +128,7 @@ export declare class FetchResource {
      * serialized.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
-     * optional caller `signal`. As on `create`, the gateway's own ceiling for a fetch is
+     * optional caller `signal`. As on `create`, ByteKit's own ceiling for a fetch is
      * 60 s, so a per-call budget is what keeps a slow upstream from holding the caller
      * for the constructor default.
      */
@@ -139,5 +141,6 @@ declare class FetchBulkResource {
     create(opts: FetchBulkCreateRequest, requestOptions?: RequestOptions): Promise<FetchBulkCreateResponse>;
     /** GET /v1/fetch/bulk/{id} — get a bulk fetch job */
     get(id: BulkId, requestOptions?: RequestOptions): Promise<FetchBulkGetResponse>;
+    get(id: BulkId, pageParams: FetchBulkPageParams, requestOptions?: RequestOptions): Promise<FetchBulkGetResponse>;
 }
 export {};

package/dist/resources/fetch.js

@@ -1,4 +1,5 @@
 import { buildPath } from '../client.js';
+import { toQueryString } from './query-string.js';
 /**
  * The query params `GET /v1/fetch` accepts, in serialization order.
  *
@@ -48,7 +49,7 @@ export class FetchResource {
      * raw JSON string, not a parsed object.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
-     * optional caller `signal`. It matters most here: the gateway's own ceiling for a
+     * optional caller `signal`. It matters most here: ByteKit's own ceiling for a
      * fetch is 60 s, so without a per-call budget a slow upstream holds the caller for
      * the constructor default (2 minutes) rather than a duration the caller chose.
      */
@@ -68,7 +69,7 @@ export class FetchResource {
      * serialized.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
-     * optional caller `signal`. As on `create`, the gateway's own ceiling for a fetch is
+     * optional caller `signal`. As on `create`, ByteKit's own ceiling for a fetch is
      * 60 s, so a per-call budget is what keeps a slow upstream from holding the caller
      * for the constructor default.
      */
@@ -91,8 +92,18 @@ class FetchBulkResource {
     create(opts, requestOptions) {
         return this.client.request('POST', '/v1/fetch/bulk', opts, requestOptions);
     }
-    /** GET /v1/fetch/bulk/{id} — get a bulk fetch job */
-    get(id, requestOptions) {
-        return this.client.request('GET', buildPath('/v1/fetch/bulk/{id}', { segments: { id } }), undefined, requestOptions);
+    get(id, pageParamsOrRequestOptions = {}, requestOptions) {
+        const hasPageParams = requestOptions !== undefined ||
+            'cursor' in pageParamsOrRequestOptions ||
+            'limit' in pageParamsOrRequestOptions ||
+            'status' in pageParamsOrRequestOptions;
+        const pageParams = hasPageParams ? pageParamsOrRequestOptions : {};
+        const resolvedRequestOptions = hasPageParams
+            ? requestOptions
+            : pageParamsOrRequestOptions;
+        return this.client.request('GET', buildPath('/v1/fetch/bulk/{id}', {
+            segments: { id },
+            query: toQueryString(pageParams),
+        }), undefined, resolvedRequestOptions);
     }
 }

package/dist/resources/monitors.d.ts

@@ -85,7 +85,7 @@ export declare class MonitorsResource {
      * Returns 204 No Content (`operations['deleteMonitor']['responses'][204]`
      * declares `content?: never`), so there is no JSON arm to derive a payload
      * from — hence `Promise<void>`. `client.request()` short-circuits the empty
-     * body to `undefined` before it would parse as JSON (#2450).
+     * body to `undefined` before it would parse as JSON.
      */
     delete(id: MonitorId, requestOptions?: RequestOptions): Promise<void>;
 }
@@ -95,7 +95,7 @@ declare class MonitorCapturesResource {
     /**
      * GET /v1/monitors/{id}/captures — list captures for a monitor.
      *
-     * `params` is optional and each key is omitted-when-absent (#2594), so `list(id)` with no
+     * `params` is optional and each key is omitted-when-absent, so `list(id)` with no
      * second argument serializes the bare `/v1/monitors/{id}/captures` URL unchanged — existing
      * zero-arg callers are unaffected (inverse case).
      */

package/dist/resources/monitors.js

@@ -37,7 +37,7 @@ export class MonitorsResource {
      * Returns 204 No Content (`operations['deleteMonitor']['responses'][204]`
      * declares `content?: never`), so there is no JSON arm to derive a payload
      * from — hence `Promise<void>`. `client.request()` short-circuits the empty
-     * body to `undefined` before it would parse as JSON (#2450).
+     * body to `undefined` before it would parse as JSON.
      */
     delete(id, requestOptions) {
         return this.client.request('DELETE', buildPath('/v1/monitors/{id}', { segments: { id } }), undefined, requestOptions);
@@ -51,7 +51,7 @@ class MonitorCapturesResource {
     /**
      * GET /v1/monitors/{id}/captures — list captures for a monitor.
      *
-     * `params` is optional and each key is omitted-when-absent (#2594), so `list(id)` with no
+     * `params` is optional and each key is omitted-when-absent, so `list(id)` with no
      * second argument serializes the bare `/v1/monitors/{id}/captures` URL unchanged — existing
      * zero-arg callers are unaffected (inverse case).
      */

package/dist/resources/scrape.d.ts

@@ -2,9 +2,29 @@ import type { ByteKit, RequestOptions } from '../client.js';
 import type { operations } from '../generated/api.js';
 import type { ScrapeId, BulkId } from '../types.js';
 /**
- * Response of POST /v1/scrape — a 200 sync success envelope or a 202 queued
- * envelope (`async: true`). Narrow on `status` (`'success' | 'queued'`) before
- * reading the result payload.
+ * Response of POST /v1/scrape — the WIRE union: a 200 terminal envelope or a 202
+ * queued receipt.
+ *
+ * What `scrape.create` RESOLVES to is narrower than this type: the `failed` member
+ * is delivered as a thrown `ByteKitError`, not as a value (#1870), so a resolved
+ * response is `success` or `queued`. The union stays honest about what the server
+ * sends — `requestRaw` and any hand-rolled transport still see the failure body.
+ *
+ * The shape follows from the request, in this order:
+ *
+ * 1. `async: true` → 202 receipt, immediately. Poll `scrape.get(id)`.
+ * 2. Otherwise a request that needs a full page render — today that is
+ *    `delay_ms > 0` — is held open until the render reaches a terminal state
+ *    and returns 200 with that state: the content envelope on success, or the
+ *    `failed` error envelope when the render itself failed. If the render is
+ *    still running when the server's hold window expires (28 s by default), it
+ *    returns the 202 receipt instead and the job continues in the background —
+ *    so a receipt can arrive without your ever asking for one.
+ * 3. Otherwise the fast HTTP path returns the 200 content envelope, typically
+ *    in under a second. A fetch that fails outright is a `failed` envelope on
+ *    that same 200, with `id: null`, because it ends before any job exists.
+ *
+ * So a 202 is never a surprise: you either asked for it, or the hold expired.
  */
 export type ScrapeCreateResponse = operations['createScrape']['responses'][200]['content']['application/json'] | operations['createScrape']['responses'][202]['content']['application/json'];
 /**
@@ -18,6 +38,8 @@ export type ScrapeBulkCreateRequest = operations['createScrapeBulk']['requestBod
 export type ScrapeBulkCreateResponse = operations['createScrapeBulk']['responses'][202]['content']['application/json'];
 /** Response of GET /v1/scrape/bulk/{id}. */
 export type ScrapeBulkGetResponse = operations['getScrapeBulk']['responses'][200]['content']['application/json'];
+/** Cursor, page-size, and item-status filters for scrape-bulk recovery. */
+export type ScrapeBulkPageParams = NonNullable<operations['getScrapeBulk']['parameters']['query']>;
 /** Markdown processing mode for the pipeline. */
 export type MarkdownMode = 'article' | 'raw' | 'llm';
 /** Link rendering style in the markdown output. */
@@ -32,7 +54,7 @@ export interface ScrapeOpts {
     formats?: Array<'raw' | 'markdown' | 'links' | 'images'>;
     country?: string;
     delay_ms?: number;
-    /** SERVER-side scrape budget in ms — how long the gateway may spend on the scrape itself. For the CLIENT-side abort budget (when this SDK gives up on the wire), see `RequestOptions.requestTimeoutMs`. */
+    /** SERVER-side scrape budget in ms — how long the server may spend on the scrape itself. For the CLIENT-side abort budget (when this SDK gives up on the wire), see `RequestOptions.requestTimeoutMs`. */
     timeout_ms?: number;
     async?: boolean;
     webhook_url?: string;
@@ -96,8 +118,22 @@ export declare class ScrapeResource {
     /**
      * POST /v1/scrape — create a scrape job.
      *
-     * Resolves to the 200 success envelope, or the 202 queued envelope when
-     * `async: true`. Narrow on `status` before reading the result.
+     * Resolves to the 200 `success` content envelope or the 202 queued receipt;
+     * narrow on `status` to tell them apart. A TERMINAL FAILURE THROWS: the server
+     * delivers it as a `failed` envelope on HTTP 200 (a definitive upstream outcome
+     * is a result, not a transport error), and this method converts it into the
+     * `ByteKitError` you already catch — `err.code`, `err.message`, and `err.status`
+     * 200. `scrape.get(id)` is unchanged and still returns `failed` as data.
+     *
+     * See {@link ScrapeCreateResponse} for the full precedence: `async: true` receipts
+     * immediately, a browser-path request without it is held open until the render
+     * reaches a terminal state (200) or the server's hold window expires (202 — a
+     * receipt you did not ask for), and everything else takes the fast path (200).
+     *
+     * A held request therefore occupies the connection for as long as the render
+     * takes, up to the server's hold window (28 s by default) — well inside this
+     * SDK's 120 s default `timeoutMs`, but worth raising `requestTimeoutMs` if you
+     * lowered it.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
      * optional caller `signal`; both override the constructor's `timeoutMs` default. They
@@ -121,5 +157,6 @@ declare class ScrapeBulkResource {
     create(opts: ScrapeBulkCreateRequest, requestOptions?: RequestOptions): Promise<ScrapeBulkCreateResponse>;
     /** GET /v1/scrape/bulk/{id} — get a bulk scrape job */
     get(id: BulkId, requestOptions?: RequestOptions): Promise<ScrapeBulkGetResponse>;
+    get(id: BulkId, pageParams: ScrapeBulkPageParams, requestOptions?: RequestOptions): Promise<ScrapeBulkGetResponse>;
 }
 export {};

package/dist/resources/scrape.js

@@ -1,4 +1,5 @@
 import { buildPath } from '../client.js';
+import { toQueryString } from './query-string.js';
 export class ScrapeResource {
     client;
     bulk;
@@ -9,8 +10,22 @@ export class ScrapeResource {
     /**
      * POST /v1/scrape — create a scrape job.
      *
-     * Resolves to the 200 success envelope, or the 202 queued envelope when
-     * `async: true`. Narrow on `status` before reading the result.
+     * Resolves to the 200 `success` content envelope or the 202 queued receipt;
+     * narrow on `status` to tell them apart. A TERMINAL FAILURE THROWS: the server
+     * delivers it as a `failed` envelope on HTTP 200 (a definitive upstream outcome
+     * is a result, not a transport error), and this method converts it into the
+     * `ByteKitError` you already catch — `err.code`, `err.message`, and `err.status`
+     * 200. `scrape.get(id)` is unchanged and still returns `failed` as data.
+     *
+     * See {@link ScrapeCreateResponse} for the full precedence: `async: true` receipts
+     * immediately, a browser-path request without it is held open until the render
+     * reaches a terminal state (200) or the server's hold window expires (202 — a
+     * receipt you did not ask for), and everything else takes the fast path (200).
+     *
+     * A held request therefore occupies the connection for as long as the render
+     * takes, up to the server's hold window (28 s by default) — well inside this
+     * SDK's 120 s default `timeoutMs`, but worth raising `requestTimeoutMs` if you
+     * lowered it.
      *
      * `requestOptions` carries the CLIENT-side abort budget (`requestTimeoutMs`) and an
      * optional caller `signal`; both override the constructor's `timeoutMs` default. They
@@ -40,8 +55,18 @@ class ScrapeBulkResource {
     create(opts, requestOptions) {
         return this.client.request('POST', '/v1/scrape/bulk', opts, requestOptions);
     }
-    /** GET /v1/scrape/bulk/{id} — get a bulk scrape job */
-    get(id, requestOptions) {
-        return this.client.request('GET', buildPath('/v1/scrape/bulk/{id}', { segments: { id } }), undefined, requestOptions);
+    get(id, pageParamsOrRequestOptions = {}, requestOptions) {
+        const hasPageParams = requestOptions !== undefined ||
+            'cursor' in pageParamsOrRequestOptions ||
+            'limit' in pageParamsOrRequestOptions ||
+            'status' in pageParamsOrRequestOptions;
+        const pageParams = hasPageParams ? pageParamsOrRequestOptions : {};
+        const resolvedRequestOptions = hasPageParams
+            ? requestOptions
+            : pageParamsOrRequestOptions;
+        return this.client.request('GET', buildPath('/v1/scrape/bulk/{id}', {
+            segments: { id },
+            query: toQueryString(pageParams),
+        }), undefined, resolvedRequestOptions);
     }
 }

package/dist/resources/screenshots.d.ts

@@ -30,7 +30,12 @@ type ScreenshotRequestSpec = operations['createScreenshot']['requestBody']['cont
 export type ScreenshotCreateRequest = Partial<ScreenshotRequestSpec> & Pick<ScreenshotRequestSpec, 'url'>;
 /**
  * Response of POST /v1/screenshots — 200 (captured synchronously) or 202
- * (queued, `async: true`). Both status codes carry the *same* `ScreenshotResponse`
+ * (pending). A 202 has TWO causes, not one: the caller passed `async: true`, so
+ * the capture was queued immediately; or the request ran synchronously and the
+ * gateway's bounded sync hold expired before the capture finished — that hold is
+ * sourced from `SYNC_HOLD_TIMEOUT_MS` (default 28s), so it is a configured bound
+ * rather than a fixed guarantee. A plain `create(opts)` call therefore reaches
+ * the pending arm too. Both status codes carry the *same* `ScreenshotResponse`
  * schema in the spec, so the type is a single derivation rather than a `200 | 202`
  * union (an identical-constituent union trips `no-duplicate-type-constituents`).
  * Narrow on `status` to tell a completed capture from a pending one.
@@ -66,12 +71,12 @@ export declare class ScreenshotsResource {
     /**
      * GET /v1/screenshots/{id} — poll a screenshot by ID.
      *
-     * A terminal-`failed` screenshot returns the `Error` envelope on a 200
-     * (issue #2027), so narrow the result before reading `image_url`.
+     * A terminal-`failed` screenshot returns the `Error` envelope on a 200,
+     * so narrow the result before reading `image_url`.
      */
     get(id: ScreenshotId, requestOptions?: RequestOptions): Promise<ScreenshotGetResponse>;
     /**
-     * POST /v1/screenshots, returning the header set alongside the body (#2547).
+     * POST /v1/screenshots, returning the header set alongside the body.
      *
      * Same request as `screenshots.create` — same method, path, body and
      * `RequestOptions` precedence — and `data` is exactly what `create()` resolves to.
@@ -86,10 +91,10 @@ export declare class ScreenshotsResource {
         async?: boolean;
     }, requestOptions?: RequestOptions): Promise<ApiResponse<ScreenshotCreateResponse>>;
     /**
-     * GET /v1/screenshots/{id}, returning the header set alongside the body (#2547).
+     * GET /v1/screenshots/{id}, returning the header set alongside the body.
      *
      * Same request as `screenshots.get`, and `data` is exactly what `get()`
-     * resolves to (including the #2027 failed-envelope arm). `get()`'s own return type is
+     * resolves to (including the failed-envelope arm). `get()`'s own return type is
      * UNCHANGED; this is an additive sibling.
      *
      * Call it for the typed body, NOT for header metadata: the spec declares
@@ -97,7 +102,7 @@ export declare class ScreenshotsResource {
      * none, so `headers` carries only the transport's own entries (`Content-Type`, …).
      * The `X-Screenshot-*` / `X-Raw-Bytes` / `X-Billable-Bytes` / `X-Billing-Multiplier`
      * family is emitted by `POST /v1/screenshots` — use `screenshots.createWithResponse`
-     * to read it (issue #2957). This matches `ByteKit.requestWithResponse` and the README,
+     * to read it. This matches `ByteKit.requestWithResponse` and the README,
      * which are the truth for what this endpoint emits.
      */
     getWithResponse(id: ScreenshotId, requestOptions?: RequestOptions): Promise<ApiResponse<ScreenshotGetResponse>>;

package/dist/resources/screenshots.js

@@ -23,14 +23,14 @@ export class ScreenshotsResource {
     /**
      * GET /v1/screenshots/{id} — poll a screenshot by ID.
      *
-     * A terminal-`failed` screenshot returns the `Error` envelope on a 200
-     * (issue #2027), so narrow the result before reading `image_url`.
+     * A terminal-`failed` screenshot returns the `Error` envelope on a 200,
+     * so narrow the result before reading `image_url`.
      */
     get(id, requestOptions) {
         return this.client.request('GET', buildPath('/v1/screenshots/{id}', { segments: { id } }), undefined, requestOptions);
     }
     /**
-     * POST /v1/screenshots, returning the header set alongside the body (#2547).
+     * POST /v1/screenshots, returning the header set alongside the body.
      *
      * Same request as `screenshots.create` — same method, path, body and
      * `RequestOptions` precedence — and `data` is exactly what `create()` resolves to.
@@ -46,10 +46,10 @@ export class ScreenshotsResource {
         return this.client.requestWithResponse('POST', buildPath('/v1/screenshots', { query: suffix }), opts, requestOptions);
     }
     /**
-     * GET /v1/screenshots/{id}, returning the header set alongside the body (#2547).
+     * GET /v1/screenshots/{id}, returning the header set alongside the body.
      *
      * Same request as `screenshots.get`, and `data` is exactly what `get()`
-     * resolves to (including the #2027 failed-envelope arm). `get()`'s own return type is
+     * resolves to (including the failed-envelope arm). `get()`'s own return type is
      * UNCHANGED; this is an additive sibling.
      *
      * Call it for the typed body, NOT for header metadata: the spec declares
@@ -57,7 +57,7 @@ export class ScreenshotsResource {
      * none, so `headers` carries only the transport's own entries (`Content-Type`, …).
      * The `X-Screenshot-*` / `X-Raw-Bytes` / `X-Billable-Bytes` / `X-Billing-Multiplier`
      * family is emitted by `POST /v1/screenshots` — use `screenshots.createWithResponse`
-     * to read it (issue #2957). This matches `ByteKit.requestWithResponse` and the README,
+     * to read it. This matches `ByteKit.requestWithResponse` and the README,
      * which are the truth for what this endpoint emits.
      */
     // NOTE (#2957): the doc block above deliberately spells sibling method names in plain

package/dist/resources/sitemap.d.ts

@@ -32,7 +32,7 @@ export declare class SitemapResource {
     /** GET /v1/sitemap/{id} — get a sitemap job by ID */
     get(id: SitemapId, requestOptions?: RequestOptions): Promise<SitemapGetResponse>;
     /**
-     * GET /v1/sitemap/{id}, returning the header set alongside the body (#2547).
+     * GET /v1/sitemap/{id}, returning the header set alongside the body.
      *
      * Same request as `sitemap.get` — same method, path and `RequestOptions`
      * precedence — and `data` is exactly what `get()` resolves to. `get()`'s own return type

package/dist/resources/sitemap.js

@@ -18,7 +18,7 @@ export class SitemapResource {
         return this.client.request('GET', buildPath('/v1/sitemap/{id}', { segments: { id } }), undefined, requestOptions);
     }
     /**
-     * GET /v1/sitemap/{id}, returning the header set alongside the body (#2547).
+     * GET /v1/sitemap/{id}, returning the header set alongside the body.
      *
      * Same request as `sitemap.get` — same method, path and `RequestOptions`
      * precedence — and `data` is exactly what `get()` resolves to. `get()`'s own return type

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.9.3";
+export declare const SDK_VERSION = "0.10.0";

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.9.3';
+export const SDK_VERSION = '0.10.0';

package/package.json

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