bytekit-sdk 0.3.4__tar.gz → 0.3.6__tar.gz

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/CHANGELOG.md

@@ -3,6 +3,116 @@
 All notable changes to the ByteKit Python SDK are documented here.
 PyPI distribution: `bytekit-sdk`. Import name: `bytekit`.
 
+## 0.3.6
+
+### Documentation
+
+- No README change ships in 0.3.6. The README's Error handling documentation reached PyPI
+  inside the published 0.3.5 artifact (2026-08-10 publish rescue) and stays documented under
+  the 0.3.5 heading, which is the version whose wheel actually carries it.
+
+### Changed
+
+- Version-alignment release after the 2026-08-10 publish rescue: the published 0.3.5 artifact was built from the `main` promotion HEAD, which already contained every change documented under the 0.3.5 heading — but that commit postdates the one that introduced the 0.3.5 version string, so the `check-release-drift` gate (#2680) correctly reported shipped drift on every subsequent CI run (#2829). 0.3.6 realigns manifest ↔ registry ↔ version-introducing commit. **No consumer-visible change relative to the published 0.3.5.**
+
+## 0.3.5
+
+### Breaking
+
+- **`AuthenticatedClient` takes no positional arguments.** `token`, `prefix` and
+  `auth_header_name` are now keyword-only, joining `base_url`, `timeout`,
+  `raise_on_unexpected_status` and the rest — so `AuthenticatedClient(...)` accepts keywords
+  only. Before 0.3.0 the first positional argument was `base_url`, which made
+  `AuthenticatedClient("https://api-stg.bytekit.com", "sk_live_…")` a documented call. When
+  0.3.0 made `base_url` a defaulted keyword argument, that call stopped meaning what it said
+  and started **binding the URL to `token` and the API key to `prefix`** — sending
+  `Authorization: sk_live_… https://api-stg.bytekit.com` to the _default_ host,
+  `https://api.bytekit.com`, with nothing raised and nothing warned. It now raises
+  `TypeError`. Migration is mechanical:
+  `AuthenticatedClient(base_url="https://api-stg.bytekit.com", token="sk_live_…")`. Keyword
+  construction — the form the README, the docs site and every example already use — is
+  entirely unchanged, including `prefix=`/`auth_header_name=` overrides and the
+  `with_headers`/`with_cookies`/`with_timeout` helpers. The unauthenticated `Client` was
+  already keyword-only and is unaffected.
+
+### Fixed
+
+- **A schema-drifted response body no longer crashes with a bare `KeyError`.** A generated
+  model's `from_dict` trusts the `required` keys the OpenAPI spec declared when the client
+  was generated, so a server that renamed, dropped or retyped a field leaked the generator's
+  own internal exception straight to the caller — `KeyError: 'schema_version'` from
+  `create_scrape`, `KeyError: 'period_start'` from `get_usage`, `KeyError: 'data'` from
+  `list_monitors`, plus `TypeError`/`ValueError` for non-object and nested-drift bodies. It
+  happened on a **documented** status (a `200`/`202`), in **both** raise modes, and no row of
+  the documented error table covered it, so a caller who handled that table faithfully still
+  had no branch for it. Schema drift now takes exactly the same two arms as a non-JSON body:
+  `errors.UnexpectedStatus` (carrying `.status_code` and the raw `.content`, with the
+  original parse failure attached as `__cause__`) in the default mode, and `None` under
+  `raise_on_unexpected_status=False`. Deliberately **no new exception type** — a new class
+  would be one every existing `except errors.UnexpectedStatus` silently fails to catch, i.e.
+  the same untyped crash in a different costume. Bodies that match the documented schema
+  parse exactly as before, and a genuinely optional key that is absent still yields `UNSET`.
+- **`client.search()` never returns a silent `None`.** Its 200 body is parsed through the
+  same shared guard the generated operations use, which honors
+  `raise_on_unexpected_status` — so an opt-out client got `None` handed back from a non-JSON
+  200 or a schema-drifted one, contradicting both the method's non-`Optional` return
+  annotation and its own docstring. `search()` now raises `errors.UnexpectedStatus` in
+  **both** raise modes. `raise_on_unexpected_status` configures the generated two-tier
+  contract, whose signatures are `Optional[...]`; `search()` was never part of it — it
+  already raises on documented error statuses that the generated `create_search` returns as
+  a typed `Error` model. A well-formed 200 still returns the parsed
+  `CreateSearchResponse200` in either mode.
+- **A non-IANA HTTP status no longer crashes every operation with a bare `ValueError`.**
+  Each generated operation built its `Response` with
+  `status_code=HTTPStatus(response.status_code)` evaluated _before_ the response was
+  parsed, so any status outside Python's `http.HTTPStatus` — Cloudflare's `520`–`530`
+  family, nginx's `499` — raised `ValueError: 520 is not a valid HTTPStatus` from inside
+  the SDK. This happened in **both** raise modes: the default
+  `raise_on_unexpected_status=True` never got to raise its `errors.UnexpectedStatus`, and
+  `raise_on_unexpected_status=False`, which promises `None`, raised the `ValueError` too.
+  `api.bytekit.com` is served through Cloudflare, so this was exactly the edge/CDN failure
+  class the typed-error contract exists for. All 29 operations now behave as documented:
+  `errors.UnexpectedStatus` (carrying `.status_code` and the raw `.content`) in the default
+  mode, a `Response` with `.parsed is None` in the opt-out mode. The hand-written
+  `client.search()` wrapper was never affected and is unchanged.
+
+### Changed
+
+- **`Response.status_code` is a plain `int` for a status `http.HTTPStatus` does not know.**
+  This is the contract decision behind the fix above, recorded here because it is the one
+  observable difference in the typed surface. Concretely:
+  - Every status the stdlib enum **does** know — documented by the API or not, `200` as
+    much as `503` — still comes back as a real `http.HTTPStatus` member, so
+    `response.status_code.phrase`, `.name`, and identity comparisons such as
+    `response.status_code is HTTPStatus.OK` keep working exactly as before.
+  - A status the enum does **not** know (`499`, `520`, `521`, `522`, `530`, …) comes back
+    as the plain `int` the wire carried. `int` comparisons (`response.status_code == 520`,
+    `>= 500`) work; enum-only attributes (`.phrase`, `.name`) do not exist on it. The
+    alternatives were rejected deliberately: a synthetic `IntEnum` member would invent a
+    `.phrase`/`.name` no registry backs, and raising before the `Response` is constructed
+    is the bug itself — it is precisely what `raise_on_unexpected_status=False` promises
+    not to do.
+  - The **declared** annotation on `Response.status_code` is unchanged (`HTTPStatus`), so
+    this release adds no type errors to existing consumer code; widening it to
+    `Union[HTTPStatus, int]` would make `.phrase`/`.name` a type error on _every_ response,
+    including the IANA ones, which is a far larger break than the residual it would close.
+    Reach for `.phrase`/`.name` only after an `isinstance(..., HTTPStatus)` check if you
+    handle edge statuses off a non-raising client.
+
+  In the default (raising) mode this is largely invisible: a non-IANA status raises
+  `errors.UnexpectedStatus` before any `Response` is returned, and
+  `UnexpectedStatus.status_code` has always been a plain `int`.
+
+### Documentation
+
+- The "Error handling" example in the README now requests `formats=[…MARKDOWN]` explicitly.
+  Run literally, its success arm printed `<bytekit.types.Unset object at 0x…>`: the snippet
+  built `ScrapeRequest(url=...)` with no `formats`, so the server applied its `raw_html`
+  default and `result.formats.markdown` was legitimately unset. The same class of defect
+  0.3.3 fixed in the quick start, in the block directly beneath it. The README's error table
+  gains the schema-drift row, a note that `search()` is outside the two-tier contract, and a
+  migration note for the keyword-only constructor.
+
 ## 0.3.4
 
 ### Breaking
@@ -26,7 +136,33 @@ PyPI distribution: `bytekit-sdk`. Import name: `bytekit`.
   `create_bulk_body*` / `create_fetch_bulk_body_urls_item_type_1` models — no other generated
   model is affected.
 
-## 0.3.3
+- If you are upgrading from 0.3.2 or earlier, note that **0.3.3 also carried a breaking model
+  removal** that went undocumented at the time — see the "Breaking" entry under 0.3.3 below
+  (`CreateFetchBulkBodyMetadata` and `CreateScrapeBulkBodyItemsItemMetadata`).
+
+## 0.3.3 [NEVER PUBLISHED]
+
+> **Never published to PyPI.** This version was cut in-tree but no `bytekit-sdk` 0.3.3 artifact
+> exists — `pip install bytekit-sdk==0.3.3` fails. Everything below shipped to users in **0.3.4**,
+> which is the first published release containing it. Reconciled by issue #2680; the
+> `release-drift` CI gate now blocks a new phantom heading from being introduced.
+
+### Breaking
+
+- **`CreateFetchBulkBodyMetadata` and `CreateScrapeBulkBodyItemsItemMetadata` were removed;
+  both fields now use the shared `Metadata` model.** This landed with the default-stripping
+  traversal fix listed under "Fixed" below (issue #2592) and was not recorded at the time.
+  Once server defaults stopped being materialized into the request-direction schemas, the two
+  per-body `metadata` objects became structurally identical to the shared `Metadata`
+  component, and the code generator emits one model per distinct schema — so
+  `bytekit.models.create_fetch_bulk_body_metadata` and
+  `bytekit.models.create_scrape_bulk_body_items_item_metadata` no longer exist and importing
+  either raises `ModuleNotFoundError`. `CreateFetchBulkBody.metadata` and
+  `CreateScrapeBulkBodyItemsItem.metadata` are now typed `Union[Unset, Metadata]`. The wire
+  format is **unchanged** — the same JSON object is sent either way — so the migration is
+  purely at the import site: `from bytekit.models.metadata import Metadata`, then
+  `Metadata(...)` (or `Metadata.from_dict({...})`) wherever you constructed one of the two
+  removed classes.
 
 ### Security
 
@@ -125,7 +261,12 @@ PyPI distribution: `bytekit-sdk`. Import name: `bytekit`.
   real method in the class body that delegates to the same implementation: **runtime behavior,
   arguments, return type and raised errors are unchanged** — only the static surface is fixed.
 
-## 0.3.1
+## 0.3.1 [NEVER PUBLISHED]
+
+> **Never published to PyPI.** This version was cut in-tree but no `bytekit-sdk` 0.3.1 artifact
+> exists — `pip install bytekit-sdk==0.3.1` fails. Everything below shipped to users in **0.3.2**,
+> which is the first published release containing it. Reconciled by issue #2680; the
+> `release-drift` CI gate now blocks a new phantom heading from being introduced.
 
 ### Fixed
 

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: bytekit-sdk
-Version: 0.3.4
+Version: 0.3.6
 Summary: Official Python SDK for the ByteKit API
 Project-URL: Homepage, https://bytekit.com
 Project-URL: Repository, https://github.com/Hunt-Labs-Inc/ByteKit
@@ -72,13 +72,22 @@ See [Error handling](#error-handling) for what `result` can be when the request
 ### Error handling
 
 The SDK has a **two-tier** error contract. Both tiers are safe: an operation never raises
-a bare `json.JSONDecodeError`, even when a server returns an HTML error page.
-
-| Situation                                                                                                                   | What you get                                                                                                                                                                       |
-| --------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| A status the OpenAPI spec **documents** for that operation (e.g. a `422` or `500` on `create_scrape`), with a JSON body     | The typed `Error` model is **returned**, not raised. Check with `isinstance(result, Error)` and read `result.error.code` / `result.error.message`.                                 |
-| An **undocumented** status, or a **non-JSON body on a documented status** (HTML error page, load-balancer text, empty body) | `errors.UnexpectedStatus` is **raised**, carrying `.status_code` and the raw `.content`. When the body is the documented `Error` envelope, `.code` / `.message` are populated too. |
-| Either of the above, with `raise_on_unexpected_status=False`                                                                | Nothing is raised; the operation returns `None`.                                                                                                                                   |
+a bare `json.JSONDecodeError` or a bare `KeyError`, even when a server returns an HTML error
+page or a payload whose shape has drifted from the spec.
+
+| Situation                                                                                                                                       | What you get                                                                                                                                                                       |
+| ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| A status the OpenAPI spec **documents** for that operation (e.g. a `422` or `500` on `create_scrape`), with a JSON body of the documented shape | The typed `Error` model is **returned**, not raised. Check with `isinstance(result, Error)` and read `result.error.code` / `result.error.message`.                                 |
+| An **undocumented** status, or a **non-JSON body on a documented status** (HTML error page, load-balancer text, empty body)                     | `errors.UnexpectedStatus` is **raised**, carrying `.status_code` and the raw `.content`. When the body is the documented `Error` envelope, `.code` / `.message` are populated too. |
+| A **documented status whose JSON body does not match the documented schema** — a field the server renamed, dropped or retyped                   | `errors.UnexpectedStatus` is **raised**, same shape as the row above. The underlying parse failure (e.g. `KeyError: 'schema_version'`) is attached as `__cause__` for diagnosis.   |
+| Any of the above, with `raise_on_unexpected_status=False`                                                                                       | Nothing is raised; the operation returns `None`.                                                                                                                                   |
+
+The table describes the **generated operations** (`create_scrape.sync`, `get_usage.sync`, …),
+whose return types are `Optional[...]` accordingly. The hand-written
+`AuthenticatedClient.search(...)` convenience method is deliberately outside it: it returns a
+non-`Optional` `CreateSearchResponse200` and raises `errors.UnexpectedStatus` on anything else
+— including documented error statuses, and including a malformed `200` — **in both raise
+modes**. `raise_on_unexpected_status` does not apply to it.
 
 ```python
 from bytekit import AuthenticatedClient
@@ -86,12 +95,21 @@ from bytekit.api.scrape import create_scrape
 from bytekit.errors import UnexpectedStatus
 from bytekit.models.error import Error
 from bytekit.models.scrape_request import ScrapeRequest
+from bytekit.models.scrape_request_formats_item import ScrapeRequestFormatsItem
 from bytekit.models.scrape_success_envelope import ScrapeSuccessEnvelope
 
 client = AuthenticatedClient(token="sk_live_your_api_key_here")
 
 try:
-    result = create_scrape.sync(client=client, body=ScrapeRequest(url="https://example.com"))
+    result = create_scrape.sync(
+        client=client,
+        body=ScrapeRequest(
+            url="https://example.com",
+            # Ask for markdown explicitly — omit `formats` and the server returns raw HTML,
+            # leaving `formats.markdown` unset.
+            formats=[ScrapeRequestFormatsItem.MARKDOWN],
+        ),
+    )
 except UnexpectedStatus as err:
     # Undocumented status, or a non-JSON body on a documented one. Never a JSONDecodeError.
     print(f"request failed with status {err.status_code}: {err.code} {err.message}")
@@ -118,6 +136,22 @@ The client ships with production-ready defaults so `AuthenticatedClient(token=..
 
 Explicit constructor arguments always win over these defaults (explicit arg > default).
 
+#### Every constructor argument is keyword-only
+
+`AuthenticatedClient` accepts **no positional arguments**. `token`, `base_url`, `prefix`,
+`auth_header_name` and the rest are all passed by name:
+
+```python
+client = AuthenticatedClient(base_url="https://api.bytekit.com", token="sk_live_your_api_key_here")
+```
+
+**Migrating from a pre-0.3.0 positional call.** `base_url` used to be the first positional
+argument, so `AuthenticatedClient("https://…", "sk_live_…")` was a documented call. Once
+`base_url` became a defaulted keyword argument, that same call silently bound the **URL to
+`token`** and the **API key to `prefix`** — producing an `Authorization: sk_live_… https://…`
+header sent to the _default_ host, i.e. a wrong credential against production with nothing
+raised. Since 0.3.5 it raises `TypeError` instead. Add the keywords; nothing else changes.
+
 ## Async usage
 
 ```python

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/README.md

@@ -46,13 +46,22 @@ See [Error handling](#error-handling) for what `result` can be when the request
 ### Error handling
 
 The SDK has a **two-tier** error contract. Both tiers are safe: an operation never raises
-a bare `json.JSONDecodeError`, even when a server returns an HTML error page.
-
-| Situation                                                                                                                   | What you get                                                                                                                                                                       |
-| --------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| A status the OpenAPI spec **documents** for that operation (e.g. a `422` or `500` on `create_scrape`), with a JSON body     | The typed `Error` model is **returned**, not raised. Check with `isinstance(result, Error)` and read `result.error.code` / `result.error.message`.                                 |
-| An **undocumented** status, or a **non-JSON body on a documented status** (HTML error page, load-balancer text, empty body) | `errors.UnexpectedStatus` is **raised**, carrying `.status_code` and the raw `.content`. When the body is the documented `Error` envelope, `.code` / `.message` are populated too. |
-| Either of the above, with `raise_on_unexpected_status=False`                                                                | Nothing is raised; the operation returns `None`.                                                                                                                                   |
+a bare `json.JSONDecodeError` or a bare `KeyError`, even when a server returns an HTML error
+page or a payload whose shape has drifted from the spec.
+
+| Situation                                                                                                                                       | What you get                                                                                                                                                                       |
+| ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| A status the OpenAPI spec **documents** for that operation (e.g. a `422` or `500` on `create_scrape`), with a JSON body of the documented shape | The typed `Error` model is **returned**, not raised. Check with `isinstance(result, Error)` and read `result.error.code` / `result.error.message`.                                 |
+| An **undocumented** status, or a **non-JSON body on a documented status** (HTML error page, load-balancer text, empty body)                     | `errors.UnexpectedStatus` is **raised**, carrying `.status_code` and the raw `.content`. When the body is the documented `Error` envelope, `.code` / `.message` are populated too. |
+| A **documented status whose JSON body does not match the documented schema** — a field the server renamed, dropped or retyped                   | `errors.UnexpectedStatus` is **raised**, same shape as the row above. The underlying parse failure (e.g. `KeyError: 'schema_version'`) is attached as `__cause__` for diagnosis.   |
+| Any of the above, with `raise_on_unexpected_status=False`                                                                                       | Nothing is raised; the operation returns `None`.                                                                                                                                   |
+
+The table describes the **generated operations** (`create_scrape.sync`, `get_usage.sync`, …),
+whose return types are `Optional[...]` accordingly. The hand-written
+`AuthenticatedClient.search(...)` convenience method is deliberately outside it: it returns a
+non-`Optional` `CreateSearchResponse200` and raises `errors.UnexpectedStatus` on anything else
+— including documented error statuses, and including a malformed `200` — **in both raise
+modes**. `raise_on_unexpected_status` does not apply to it.
 
 ```python
 from bytekit import AuthenticatedClient
@@ -60,12 +69,21 @@ from bytekit.api.scrape import create_scrape
 from bytekit.errors import UnexpectedStatus
 from bytekit.models.error import Error
 from bytekit.models.scrape_request import ScrapeRequest
+from bytekit.models.scrape_request_formats_item import ScrapeRequestFormatsItem
 from bytekit.models.scrape_success_envelope import ScrapeSuccessEnvelope
 
 client = AuthenticatedClient(token="sk_live_your_api_key_here")
 
 try:
-    result = create_scrape.sync(client=client, body=ScrapeRequest(url="https://example.com"))
+    result = create_scrape.sync(
+        client=client,
+        body=ScrapeRequest(
+            url="https://example.com",
+            # Ask for markdown explicitly — omit `formats` and the server returns raw HTML,
+            # leaving `formats.markdown` unset.
+            formats=[ScrapeRequestFormatsItem.MARKDOWN],
+        ),
+    )
 except UnexpectedStatus as err:
     # Undocumented status, or a non-JSON body on a documented one. Never a JSONDecodeError.
     print(f"request failed with status {err.status_code}: {err.code} {err.message}")
@@ -92,6 +110,22 @@ The client ships with production-ready defaults so `AuthenticatedClient(token=..
 
 Explicit constructor arguments always win over these defaults (explicit arg > default).
 
+#### Every constructor argument is keyword-only
+
+`AuthenticatedClient` accepts **no positional arguments**. `token`, `base_url`, `prefix`,
+`auth_header_name` and the rest are all passed by name:
+
+```python
+client = AuthenticatedClient(base_url="https://api.bytekit.com", token="sk_live_your_api_key_here")
+```
+
+**Migrating from a pre-0.3.0 positional call.** `base_url` used to be the first positional
+argument, so `AuthenticatedClient("https://…", "sk_live_…")` was a documented call. Once
+`base_url` became a defaulted keyword argument, that same call silently bound the **URL to
+`token`** and the **API key to `prefix`** — producing an `Authorization: sk_live_… https://…`
+header sent to the _default_ host, i.e. a wrong credential against production with nothing
+raised. Since 0.3.5 it raises `TypeError` instead. Add the keywords; nothing else changes.
+
 ## Async usage
 
 ```python

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/pyproject.toml

@@ -7,7 +7,7 @@
 # `pip install bytekit-sdk` yields a working `import bytekit`. Mirrors the npm sibling
 # @hunt-labs/bytekit-sdk.
 name = "bytekit-sdk"
-version = "0.3.4"
+version = "0.3.6"
 description = "Official Python SDK for the ByteKit API"
 readme = "README.md"
 requires-python = ">=3.10"

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/account/get_account.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -59,7 +58,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, Union["AccountBearerResponse", "AccountSessionResponse"]]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/bulk/create_bulk.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -55,7 +54,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[CreateBulkResponse202, Error]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/bulk/delete_bulk.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 from urllib.parse import quote  # BYTEKIT-PATH-QUOTE
 
@@ -43,7 +42,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[DeleteBulkResponse200, Error]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/bulk/get_bulk.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 from urllib.parse import quote  # BYTEKIT-PATH-QUOTE
 
@@ -43,7 +42,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, GetBulkResponse200]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/bulk/list_bulk_screenshots.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 from urllib.parse import quote  # BYTEKIT-PATH-QUOTE
 
@@ -38,7 +37,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[ListBulkScreenshotsResponse200]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),
@@ -52,6 +51,18 @@ def sync_detailed(
 ) -> Response[ListBulkScreenshotsResponse200]:
     """List bulk job items
 
+     Returns the bulk job's items, discriminated by `type`.
+
+    **Downloading item artifacts.** `image_url` (`type: screenshot`) and both
+    `content_url` and `markdown_url` (`type: scrape`) are **pre-signed** URLs,
+    minted fresh on every read of this endpoint and valid for **600 seconds
+    (10 minutes)** —
+    the same signing lifetime as `content_url` on `GET /v1/fetch/bulk/{id}`.
+    The underlying objects are private, so an unsigned URL returns `401`:
+    download inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -81,6 +92,18 @@ def sync(
 ) -> Optional[ListBulkScreenshotsResponse200]:
     """List bulk job items
 
+     Returns the bulk job's items, discriminated by `type`.
+
+    **Downloading item artifacts.** `image_url` (`type: screenshot`) and both
+    `content_url` and `markdown_url` (`type: scrape`) are **pre-signed** URLs,
+    minted fresh on every read of this endpoint and valid for **600 seconds
+    (10 minutes)** —
+    the same signing lifetime as `content_url` on `GET /v1/fetch/bulk/{id}`.
+    The underlying objects are private, so an unsigned URL returns `401`:
+    download inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -105,6 +128,18 @@ async def asyncio_detailed(
 ) -> Response[ListBulkScreenshotsResponse200]:
     """List bulk job items
 
+     Returns the bulk job's items, discriminated by `type`.
+
+    **Downloading item artifacts.** `image_url` (`type: screenshot`) and both
+    `content_url` and `markdown_url` (`type: scrape`) are **pre-signed** URLs,
+    minted fresh on every read of this endpoint and valid for **600 seconds
+    (10 minutes)** —
+    the same signing lifetime as `content_url` on `GET /v1/fetch/bulk/{id}`.
+    The underlying objects are private, so an unsigned URL returns `401`:
+    download inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -132,6 +167,18 @@ async def asyncio(
 ) -> Optional[ListBulkScreenshotsResponse200]:
     """List bulk job items
 
+     Returns the bulk job's items, discriminated by `type`.
+
+    **Downloading item artifacts.** `image_url` (`type: screenshot`) and both
+    `content_url` and `markdown_url` (`type: scrape`) are **pre-signed** URLs,
+    minted fresh on every read of this endpoint and valid for **600 seconds
+    (10 minutes)** —
+    the same signing lifetime as `content_url` on `GET /v1/fetch/bulk/{id}`.
+    The underlying objects are private, so an unsigned URL returns `401`:
+    download inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/fetch/get_fetch.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -85,7 +84,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, str]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/fetch/post_fetch.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -61,7 +60,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, str]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/fetch_bulk/create_fetch_bulk.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -55,7 +54,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[CreateFetchBulkResponse202, Error]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/fetch_bulk/get_fetch_bulk.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 from urllib.parse import quote  # BYTEKIT-PATH-QUOTE
 
@@ -43,7 +42,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, GetFetchBulkResponse200]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),
@@ -57,6 +56,17 @@ def sync_detailed(
 ) -> Response[Union[Error, GetFetchBulkResponse200]]:
     """Get fetch bulk job status
 
+     Returns the job envelope plus its per-URL items.
+
+    **Downloading item content.** Each completed item's `content_url` is a
+    **pre-signed** URL, minted fresh on every read of this endpoint and valid
+    for **600 seconds (10 minutes)** — the same signing lifetime as the
+    `image_url` returned by `GET /v1/bulk/{id}/screenshots`. The underlying
+    objects are private, so an unsigned URL returns `401`: download the
+    content inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -86,6 +96,17 @@ def sync(
 ) -> Optional[Union[Error, GetFetchBulkResponse200]]:
     """Get fetch bulk job status
 
+     Returns the job envelope plus its per-URL items.
+
+    **Downloading item content.** Each completed item's `content_url` is a
+    **pre-signed** URL, minted fresh on every read of this endpoint and valid
+    for **600 seconds (10 minutes)** — the same signing lifetime as the
+    `image_url` returned by `GET /v1/bulk/{id}/screenshots`. The underlying
+    objects are private, so an unsigned URL returns `401`: download the
+    content inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -110,6 +131,17 @@ async def asyncio_detailed(
 ) -> Response[Union[Error, GetFetchBulkResponse200]]:
     """Get fetch bulk job status
 
+     Returns the job envelope plus its per-URL items.
+
+    **Downloading item content.** Each completed item's `content_url` is a
+    **pre-signed** URL, minted fresh on every read of this endpoint and valid
+    for **600 seconds (10 minutes)** — the same signing lifetime as the
+    `image_url` returned by `GET /v1/bulk/{id}/screenshots`. The underlying
+    objects are private, so an unsigned URL returns `401`: download the
+    content inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 
@@ -137,6 +169,17 @@ async def asyncio(
 ) -> Optional[Union[Error, GetFetchBulkResponse200]]:
     """Get fetch bulk job status
 
+     Returns the job envelope plus its per-URL items.
+
+    **Downloading item content.** Each completed item's `content_url` is a
+    **pre-signed** URL, minted fresh on every read of this endpoint and valid
+    for **600 seconds (10 minutes)** — the same signing lifetime as the
+    `image_url` returned by `GET /v1/bulk/{id}/screenshots`. The underlying
+    objects are private, so an unsigned URL returns `401`: download the
+    content inside that window, or re-poll this endpoint for a fresh
+    signature. Items that are not `completed`, and completed items with no
+    stored object, carry `null` or the unsigned stored URL instead.
+
     Args:
         id (str):
 

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/monitors/create_monitor.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union
 
 import httpx
@@ -59,7 +58,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Error, MonitorCreateResponse]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),

{bytekit_sdk-0.3.4 → bytekit_sdk-0.3.6}/src/bytekit/api/monitors/delete_monitor.py

@@ -1,4 +1,3 @@
-from http import HTTPStatus
 from typing import Any, Optional, Union, cast
 from urllib.parse import quote  # BYTEKIT-PATH-QUOTE
 
@@ -41,7 +40,7 @@ def _build_response(
     *, client: Union[AuthenticatedClient, Client], response: httpx.Response
 ) -> Response[Union[Any, Error]]:
     return Response(
-        status_code=HTTPStatus(response.status_code),
+        status_code=errors.bytekit_status_code(response.status_code),  # BYTEKIT-STATUS-COERCE
         content=response.content,
         headers=response.headers,
         parsed=_parse_response(client=client, response=response),