brightdata-hotdata-bridge 0.1.1__tar.gz

brightdata_hotdata_bridge-0.1.1/.env.example

@@ -0,0 +1,35 @@
+# Copy to .env and fill in. Both the `bdh` CLI and the Python library read these.
+# Never commit the real .env file.
+
+# --- Required ------------------------------------------------------------
+BRIGHTDATA_API_KEY=
+HOTDATA_API_KEY=
+HOTDATA_WORKSPACE_ID=
+
+# --- Optional (defaults shown) -------------------------------------------
+# Target database. When neither is set, the workspace's only database is used;
+# if the workspace has several, set one of these (`bdh databases` lists them).
+# HOTDATA_DATABASE_ID=
+# HOTDATA_DATABASE_NAME=
+# Schema that tables are published into. Defaults to the database's default schema,
+# or `public` when the database has none.
+# HOTDATA_SCHEMA=
+# Override only when targeting a non-production Hotdata environment.
+# HOTDATA_HOST=https://api.hotdata.dev
+
+# Seconds between Bright Data progress checks, and the overall wait limit.
+# BDH_POLL_INTERVAL_SECONDS=10
+# BDH_POLL_TIMEOUT_SECONDS=3600
+
+# Seconds to wait for a background Hotdata load job to finish.
+# BDH_LOAD_TIMEOUT_SECONDS=1800
+
+# Timeout for a single HTTP request.
+# BDH_HTTP_TIMEOUT_SECONDS=60
+
+# Where run records, downloaded snapshots and the scraper catalog cache live.
+# BDH_STATE_DIR=.bdh
+
+# Scraper catalog source and how long the cached copy stays fresh.
+# BDH_CATALOG_URL=https://docs.brightdata.com/scrapers-full.json
+# BDH_CATALOG_TTL_HOURS=24

brightdata_hotdata_bridge-0.1.1/.gitignore

@@ -0,0 +1,38 @@
+# Secrets: never commit credentials
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+
+# Pipeline working state (downloaded snapshots, run records, catalog cache)
+.bdh/
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+
+# Tooling caches
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+coverage.xml
+htmlcov/
+
+# Editors / OS
+.idea/
+.vscode/
+.DS_Store
+
+# Internal working documents (kept locally, not published)
+BrightData_Hotdata_Functional_Specification_Document.docx.md
+Technical Specification_ Bright Data → Hotdata Integration.md
+audit.md
+dataset_id.json
+.cursorrules

brightdata_hotdata_bridge-0.1.1/CHANGELOG.md

@@ -0,0 +1,39 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.1.1]
+
+### Fixed
+
+- Release workflow reads `__version__` from `__about__.py`, so the tag check matches the package version.
+
+## [0.1.0]
+
+### Added
+
+- `NOTICE` file for the Apache-2.0 license, shipped in the wheel and sdist.
+- Individual Contributor License Agreement (`CLA.md`), signed with a GitHub login through
+  CLA assistant and checked on every pull request.
+- `PushResult.row_count`: rows loaded by the run (the same as `rows_published`).
+- `docs/` with setup, configuration, usage, troubleshooting and architecture pages.
+- `examples/push_with_library.py`: end-to-end library use with handling for each failure.
+- `SECURITY.md` (private vulnerability reporting), `CODE_OF_CONDUCT.md` (Contributor
+  Covenant 2.1), and issue and pull request templates.
+- End-to-end pipeline: trigger a Bright Data collection, poll until ready, stream the
+  snapshot, validate it, upload it to Hotdata object storage and load it into a table.
+- Support for any scraper in Bright Data's catalog, with CSV inputs validated against
+  the selected collection method (`collect_by_url` and `discover_by_*`).
+- Output validation against the scraper's output schema, with error records set aside
+  and a JSON report on mismatch.
+- Resumable run records, `bdh replay` for failed writes, and `replace`, `append`,
+  `upsert`, `update` and `delete` load modes.
+- Target database looked up from the Hotdata workspace when `HOTDATA_DATABASE_ID` is not
+  set (the only database, or one chosen by `HOTDATA_DATABASE_NAME`), recorded per run so
+  replays publish to the same database. The schema defaults to the database's own.
+- `bdh` CLI: `push`, `trigger`, `status`, `replay`, `runs`, `databases`,
+  `scrapers list|show`.

brightdata_hotdata_bridge-0.1.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

brightdata_hotdata_bridge-0.1.1/NOTICE

@@ -0,0 +1,4 @@
+brightdata-hotdata-bridge
+Copyright 2026 Adom Hamza
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

brightdata_hotdata_bridge-0.1.1/PKG-INFO

@@ -0,0 +1,258 @@
+Metadata-Version: 2.5
+Name: brightdata-hotdata-bridge
+Version: 0.1.1
+Summary: Trigger Bright Data scraper collections and publish the results into Hotdata tables.
+Project-URL: Documentation, https://github.com/adomhamza/brightdata-hotdata-bridge#readme
+Project-URL: Source, https://github.com/adomhamza/brightdata-hotdata-bridge
+Project-URL: Issues, https://github.com/adomhamza/brightdata-hotdata-bridge/issues
+Author: Adom Hamza
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: brightdata,data-pipeline,etl,hotdata,web-scraping
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Database
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: hotdata<1,>=0.11
+Requires-Dist: httpx<1,>=0.27
+Requires-Dist: pydantic-settings<3,>=2.3
+Requires-Dist: pydantic<3,>=2.7
+Requires-Dist: typer<1,>=0.12
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest-cov>=5; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# brightdata-hotdata-bridge
+
+Collect web data with [Bright Data](https://brightdata.com) scrapers and publish it into
+[Hotdata](https://www.hotdata.dev) tables, from Python or the `bdh` command line.
+
+Give it a scraper's dataset id and a CSV of URLs (or keywords, usernames, and so on).
+It triggers the collection, waits for it, validates the records, and loads them into a
+Hotdata table.
+
+```text
+inputs.csv ─► Bright Data trigger ─► poll until ready ─► download NDJSON
+           ─► validate against the scraper schema ─► Hotdata upload ─► table load
+```
+
+Full documentation is in [`docs/`](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/README.md): [setup](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/setup.md),
+[configuration](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/configuration.md), [usage](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/usage.md),
+[troubleshooting](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/troubleshooting.md) and [architecture](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/docs/architecture.md).
+
+## Features
+
+- **Any Bright Data scraper.** Dataset ids and their inputs are checked against Bright
+  Data's published [scraper catalog](https://docs.brightdata.com/scrapers-full.json)
+  (1,200+ scrapers, cached locally), so a bad CSV is rejected before a paid collection
+  starts.
+- **Collect and discover.** Supports `collect_by_url` and every `discover_by_*` method
+  (keyword, category, user name, and more).
+- **Validated before writing.** Records are type-checked against the scraper's output
+  schema. A mismatch pauses ingestion and writes a report. Records Bright Data flags
+  as errors are set aside rather than loaded.
+- **Large snapshots.** The snapshot is streamed to disk and uploaded straight to Hotdata
+  object storage, using multipart for big files. Loads run as background jobs.
+- **Resumable and replayable.** Every stage is saved to a local run record. A timeout,
+  a failed write or a fixed schema problem is resumed with `bdh replay`, and a run is
+  never loaded twice.
+- **Polite to the APIs.** Honours `Retry-After` with exponential backoff, and only
+  retries a Bright Data trigger when it provably never reached the server.
+
+## Install
+
+```bash
+pip install brightdata-hotdata-bridge        # library + CLI
+pipx install brightdata-hotdata-bridge       # CLI only, isolated environment
+```
+
+Requires Python 3.10+.
+
+## Configure
+
+Copy `.env.example` to `.env` (or export the variables):
+
+```bash
+BRIGHTDATA_API_KEY=...
+HOTDATA_API_KEY=...
+HOTDATA_WORKSPACE_ID=...
+```
+
+The target database is looked up from the workspace before anything is triggered. If the
+workspace has exactly one database it is used automatically; if it has several, set
+`HOTDATA_DATABASE_ID` or `HOTDATA_DATABASE_NAME` (run `bdh databases` to list them). Each
+run records the database it used, so `bdh replay` always publishes to the same place.
+
+Optional settings (schema, polling interval and timeout, state directory, catalog
+source) are documented in [`.env.example`](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/.env.example). The library and the CLI read
+the same configuration.
+
+## CLI
+
+Find a scraper and the CSV columns it needs:
+
+```bash
+bdh scrapers list --search amazon
+bdh scrapers show gd_l7q7dkf244hwjntr0
+```
+
+Collect and publish in one step:
+
+```bash
+# urls.csv has a header row:  url
+bdh push --dataset-id gd_l7q7dkf244hwjntr0 --input-file urls.csv --table amazon_products
+
+# A single required input can be passed inline
+bdh push -d gd_l7q7dkf244hwjntr0 -q "https://www.amazon.com/dp/B0CRMZHDG8" -t amazon_products
+
+# Discovery methods take their own inputs (keywords.csv header: keyword)
+bdh push -d gd_l7q7dkf244hwjntr0 -m discover_by_keyword -i keywords.csv \
+  --limit-per-input 50 -t amazon_search --mode append
+```
+
+Publish a snapshot that already exists, or start a collection and finish it later:
+
+```bash
+bdh push --snapshot-id sd_m1a2b3c4d5e6f7g8h --table amazon_products
+bdh trigger -d gd_l7q7dkf244hwjntr0 -i urls.csv -t amazon_products   # prints snapshot id
+bdh replay sd_m1a2b3c4d5e6f7g8h
+```
+
+Operate:
+
+```bash
+bdh status sd_m1a2b3c4d5e6f7g8h      # Bright Data status + local stage + last error
+bdh runs                              # all local runs
+bdh databases                         # Hotdata databases, and which one push will use
+bdh replay sd_m1a2b3c4d5e6f7g8h       # resume after a timeout or failed write
+```
+
+Add `--json` to `push`, `replay`, `status`, `runs` and `trigger` for machine-readable
+output, and `--log-json` for JSON logs.
+
+### Load modes
+
+| Mode      | Effect                                                    |
+| --------- | --------------------------------------------------------- |
+| `replace` | The snapshot becomes the table's contents (default).      |
+| `append`  | Rows are added to the existing table.                     |
+| `upsert`  | Rows matching `--key` columns are replaced, others added. |
+| `update`  | Rows matching `--key` columns are replaced.               |
+| `delete`  | Rows matching `--key` columns are removed.                |
+
+> **`replace` is the default and discards every existing row.** Pushing to a table that
+> already holds data without `--mode` leaves only the new snapshot's rows. To keep earlier
+> data, use `--mode append`, or `--mode upsert --key <column>` to keep one up-to-date row
+> per record (for example `--key id` for LinkedIn profiles).
+
+The first load into a new table is always `replace`, as Hotdata requires. If you ask
+for another mode on a table that does not exist yet, `replace` is used automatically.
+Every load is atomic: readers see the old contents or the new ones, never a mix, and a
+failed load leaves the table unchanged.
+
+### Validation options
+
+- `--require-field name` (repeatable): the field must be present and non-null.
+- `--strict-fields`: fail on fields that are not in the scraper's output schema
+  (by default they are allowed and listed as schema drift in the report).
+- `--stringify-nested`: store nested objects and arrays as JSON text.
+
+### Exit codes
+
+| Code | Meaning                                    |
+| ---- | ------------------------------------------ |
+| 0    | Success                                    |
+| 2    | Configuration or usage error               |
+| 3    | Unknown dataset / method, or invalid input |
+| 4    | Bright Data API error                      |
+| 5    | Collection failed or was canceled          |
+| 6    | Snapshot not ready in time (resumable)     |
+| 7    | Schema mismatch or no publishable records  |
+| 8    | Hotdata write failed (replayable)          |
+| 9    | Local run record missing or unusable       |
+
+## Library
+
+```python
+from brightdata_hotdata_bridge import push_snapshot_to_hotdata
+
+result = push_snapshot_to_hotdata(
+    dataset_id="gd_l7q7dkf244hwjntr0",
+    input_file="urls.csv",
+    table_name="amazon_products",
+)
+print(f"Loaded {result.row_count} rows; the table now has {result.table_row_count}")
+```
+
+[`examples/push_with_library.py`](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/examples/push_with_library.py) shows how to handle each
+failure.
+
+Async code (FastAPI, notebooks, orchestrators) should use the async API:
+
+```python
+from brightdata_hotdata_bridge import (
+    PushRequest,
+    TableTarget,
+    arun_pipeline,
+    build_collection_request,
+    get_settings,
+)
+
+settings = get_settings()
+collection = await build_collection_request(
+    dataset_id="gd_l7q7dkf244hwjntr0",
+    queries=["https://www.amazon.com/dp/B0CRMZHDG8"],
+    settings=settings,
+)
+result = await arun_pipeline(
+    PushRequest(collection=collection, target=TableTarget(table="amazon_products")),
+    settings,
+)
+```
+
+Every error derives from `BridgeError`. Catch `HotdataWriteError` to schedule a
+`replay_run(snapshot_id)`, or `SchemaMismatchError` to inspect `exc.report_path`.
+
+## How failures are handled
+
+| Situation                         | Behaviour                                                                 |
+| --------------------------------- | ------------------------------------------------------------------------- |
+| Collection `failed` / `canceled`  | Logged with the snapshot id; nothing is written to Hotdata.               |
+| Snapshot not ready before timeout | Run is saved; `bdh push --snapshot-id` or `bdh replay` resumes polling.   |
+| Schema or type mismatch           | Ingestion pauses; `report.json` lists every issue; nothing is written.    |
+| Hotdata upload or load fails      | Logged with Hotdata's trace id; `bdh replay` retries from that stage.     |
+| Bright Data / Hotdata rate limits | `Retry-After` honoured, exponential backoff (2, 4, 8, 16, 32 s).          |
+
+Run state lives in `.bdh/runs/<snapshot_id>/`: `run.json` (stage, target, upload id,
+last error), the raw and validated NDJSON, the rejected records, and the validation
+report.
+
+## Development
+
+```bash
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+ruff check . && ruff format --check .
+mypy
+pytest --cov
+```
+
+See [CONTRIBUTING.md](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/CODE_OF_CONDUCT.md). Report
+security problems privately as described in [SECURITY.md](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/SECURITY.md). Contributors sign the
+[Contributor License Agreement](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/CLA.md) on their first pull request. Licensed under
+[Apache-2.0](https://github.com/adomhamza/brightdata-hotdata-bridge/blob/main/LICENSE).