thrustlab 0.4.0__tar.gz

thrustlab-0.4.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+dist/
+build/
+*.egg-info/
+.venv/
+.tox/

thrustlab-0.4.0/CHANGELOG.md

@@ -0,0 +1,385 @@
+# Changelog
+
+All notable changes to the `thrustlab` Python SDK are documented here. The
+project follows [semantic versioning](https://semver.org/) independent of the
+ThrustLab API version (which is permanently `/v1/`).
+
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+## [0.4.0] - 2026-08-27
+
+Contract refresh for the production `/v1/` API. This release adds the current
+multi-rotor, battery-topology, geometry, entitlement, and native Rust solver
+response models. It also removes generated models for an endpoint that is not
+part of the public API.
+
+### Breaking
+
+- Paid accounts now represent unlimited monthly simulation usage explicitly:
+  `CreditBalanceResource.total` and `CreditUsageEventResource.balance_after`
+  may be `None`, and `CreditBalanceResource.unlimited` states whether the
+  account has no monthly usage allowance. Concurrency and HTTP rate limits are
+  still enforced separately.
+- Removed `PreviewRequest` and `GeometryPreviewResponse`. The corresponding
+  `/v1/geometry/preview` operation was not a public live endpoint; use
+  `client.geometry.generate(...)` or `client.geometry.analyze(...)` instead.
+- The generated sweep-point payload is now typed as `SweepPointInputs` with a
+  nested `SweepPointComponentSelection`, replacing the unstructured
+  `SweepPointResourceInputs` model.
+- Generated dynamic schedule enum names now include the nullable-union suffix:
+  `SegmentGroupCommandInThrottleRampType0` and
+  `SegmentGroupCommandInTiltRampType0` replace their unsuffixed counterparts.
+
+### Added
+
+- Single-point, sweep, and dynamic requests accept an ordered `rotors` list.
+  Each rotor can carry its rotation sense and coaxial stack/position metadata;
+  legacy grouped inputs remain accepted for compatibility. Rotor-group counts
+  now support up to 40 rotors.
+- Structured `PackTopologyIn` battery definitions with series, parallel, and
+  leaf nodes. Simulation and dynamic resources return the stored topology.
+- Simulation, sweep, and dynamic resources expose `solver_engine`; dynamic
+  resources also expose `snapshot_version`.
+- Dynamic rotor groups expose the full ESC contract: type, timing, PWM
+  frequency, resistance, motor-wire resistance, and synchronous rectification.
+- Geometry design/generation accepts explicit radial station arrays, hub ratio,
+  airfoil layout, and one to 16 blades. Analysis responses expose validation
+  envelope status/limiting factor and `Ct_raw`, `Cp_raw`, `thrust_raw`,
+  `torque_raw`, and `power_raw`.
+- Entitlements expose `max_concurrent_runs` and `fmi_export`. User resources
+  expose first/last name and required-tier gate metadata.
+
+### Changed
+
+- The published contract and generated models now identify native Rust solver
+  results via the `solver_engine` response field (`prom-rs/0.2.1` in this
+  release).
+- Hobbyist and Pro usage is unlimited. `max_concurrent_runs` communicates the
+  account-wide queue width (one for Hobbyist and five for Pro); request rate
+  limiting remains independent of simulation concurrency.
+- **Physical inputs that were silently accepted out of range are now rejected
+  with a `422` naming the field.** The intervals below were already enforced one
+  layer inside the API, but they were absent from the request schema — so a
+  request carrying one of these values either returned an unhelpful `500` or, for
+  the pinned motor temperatures, was accepted and run. Nothing in range changes:
+  every previously-valid request is still valid and returns the same numbers.
+
+  | Field | Accepted range |
+  | --- | --- |
+  | `density_kg_m3` (simulation, sweep, dynamic, dynamic estimate) | `0 < x <= 2.0` kg/m³ |
+  | `airspeed_m_s` (simulation, sweep) | `0 – 100` m/s |
+  | `airspeed_target` (dynamic schedule segment and CSV row) | `0 – 100` m/s |
+  | `throttle_pct` (rotor group) | `0 – 100` % |
+  | `esc_resistance_mohm`, `esc_motor_wire_resistance_mohm` (rotor group) | `0 – 10000` mΩ |
+  | `battery_esc_wire_resistance_mohm` (simulation, sweep) | `0 – 10000` mΩ |
+  | `motor_t_w`, `motor_t_mag` (rotor group) | `-60 – 250` °C |
+
+  The motor-temperature pins are the ones worth checking in existing code: they
+  are **degrees Celsius**, and a value in kelvin (e.g. `293.15`) used to be
+  accepted and quietly changed the winding resistance and torque constant. It is
+  now a `422`.
+
+  Every one of these bounds also appears in the OpenAPI spec now, so a
+  spec-generated client can see them.
+
+- **`esc_type` now defaults to `six_step` instead of `foc`** on `RotorGroupIn`
+  and `SweepRotorGroupIn` (ESC-7). This is a BEHAVIOUR change for any caller that
+  omits the field: `esc_type` selects the commutation convention — K_volt
+  (1/sqrt(3) vs sqrt(3)/pi), copper and iron multipliers, the six-step advance
+  physics, and the throttle→duty map. Measured on a 400 kV / 14-pole / 50 mOhm
+  motor at 22.2 V: RPM −4.56% at full throttle (−2.56% at 75%, −2.84% at 50%,
+  −3.71% at 25%), thrust −8.91% at full throttle to −5.06% at 75%.
+
+  Why: the API defaulted to `foc` while the web app has always sent `six_step`,
+  so the same powertrain returned different numbers depending on which surface
+  submitted it. Six-step is the researched default — catalog Kv is measured under
+  trapezoidal drive and real hobby ESCs are 120° block commutation — so aligning
+  the API to it makes the two agree without moving the web app.
+
+  **To keep the previous behaviour, send `esc_type="foc"` explicitly.** Stored
+  simulations are unaffected: the column default changed with no backfill, so a
+  run recorded as FOC still re-runs as FOC.
+
+### Fixed
+
+- The source archive now uses an explicit public-package manifest, excluding
+  monorepo-only release tooling while retaining the SDK, tests, examples,
+  changelog, and legal files.
+
+## [0.3.2] - 2026-07-16
+
+Bug-fix release: a docs-vs-code audit found several SDK surfaces that
+silently did nothing (the server ignores unknown query params) or targeted
+endpoints that don't exist. No new API surface beyond the fixes below.
+
+### Fixed
+
+- **`list(project_id=...)` on `simulations`, `sweeps`, and
+  `dynamic_simulations` now actually filters.** The SDK sent a `project_id`
+  query key but the endpoints read `project` — the filter was silently
+  ignored and every listing returned ALL of the caller's runs. The kwarg
+  name is unchanged; the SDK now sends the right param.
+- **`projects.list`, `submissions.list`, `webhook_endpoints.list`,
+  `list_events`, and `list_deliveries` pagination kwarg renamed
+  `starting_after=` → `cursor=`.** The endpoints read `cursor`;
+  `starting_after` was silently ignored (same defect the 0.3.0 changelog
+  fixed for sims/sweeps — these five were missed).
+- **BREAKING — `client.starred_components` rewritten against the real API.**
+  The previous resource targeted `GET/POST /v1/projects/{pid}/starred-components`,
+  which does not exist under `/v1/` — every call 404'd. Stars are flat,
+  first-class resources:
+  - `list(project_id=..., component_type=..., cursor=...)` →
+    `GET /v1/starred_components`;
+  - `add(project_id=..., component_id=..., component_type=...)` →
+    `POST /v1/starred_components` (component_type is required; duplicate
+    star raises `ConflictError` 409 `already_starred`);
+  - `remove(star_id)` → `DELETE /v1/starred_components/{star_id}` — keys on
+    the star's own `star_<ksuid>` id (from `list()`/`add()`), not the
+    component id.
+- **`APIError.request_id` is now populated.** It is read from the error
+  envelope's `request_id` (with the `X-Request-ID` response header as a
+  fallback); previously the SDK only read the header, which the server did
+  not send, so `request_id` was always `None`.
+
+### Added
+
+- `simulations.list(status=...)` — filter by `queued` / `running` /
+  `completed` / `failed` / `canceled`.
+- `submissions.list(status=...)` — filter by moderation status.
+- `submissions.update(id, ...)` / `submissions.withdraw(id)` — edit or
+  withdraw a submission while it is still `submitted`.
+- `webhook_endpoints.list_deliveries(..., event_type=..., created_at_gte=...)`
+  — the endpoint's remaining filters, previously unreachable from the SDK.
+
+## [0.3.1] - 2026-07-16
+
+Packaging-metadata fix, no code changes:
+
+- The `Repository` project URL shipped in 0.3.0 carried a literal
+  `<owner>` placeholder; it now points to the public SDK repo,
+  `https://github.com/kbedrich/thrustlab-sdk`.
+- README links corrected to the same repo.
+
+## [0.3.0] - 2026-07-15
+
+The ThrustLab public API was refocused to a **product-only** surface: account,
+billing, subscription, API-key and geometry-calibration management are no
+longer part of the public `/v1/` contract. This SDK release realigns the
+client to that surface.
+
+> **0.2.0 was built but never published to PyPI.** 0.3.0 is the first release
+> after 0.1.2, and it **consolidates the unpublished 0.2.0 changes** (canonical
+> `snake_case` result keys, the `dynamic_simulations` resource, the sims/sweeps
+> `cursor` fix) together with the API-refocus breaking changes below. If you are
+> upgrading from `0.1.x`, read this whole entry — it is the full delta.
+
+### Removed
+
+- **BREAKING — `client.subscriptions` and `client.api_keys` resources are gone.**
+  Subscription/billing-portal and API-key management are not part of the public
+  product SDK. `client.subscriptions` / `client.api_keys` now raise
+  `AttributeError`. (Create and manage API keys from the ThrustLab dashboard.)
+
+### Changed
+
+- **BREAKING — `client.credits` renamed to `client.compute_units`.** The public
+  credits surface was renamed to *compute units*:
+  - accessor `client.credits` → `client.compute_units`;
+  - method `usage(...)` → `transactions(...)`;
+  - endpoints `/v1/credits/balance` → `/v1/compute-units/balance` and
+    `/v1/credits/usage` → `/v1/compute-units/transactions`;
+  - the pager keyword `starting_after=` → `cursor=` (the endpoint reads `cursor`;
+    this matches the 0.2.0 sims/sweeps fix — a `starting_after=` kwarg was
+    silently ignored). The `credit_type=` filter keyword is unchanged.
+- **BREAKING (from the unpublished 0.2.0) — result payloads are canonical
+  `snake_case` across single-point, sweep, AND dynamic endpoints**, each with a
+  sibling `display_labels` map (`{snake_key: "Human Label"}`). Consumers that
+  parsed the old display-label result keys on sweep points (`"Thrust (N)"`,
+  `"RPM"`, …) must read the snake keys (`thrust_n`, `rpm`, …) and use
+  `display_labels` to recover a human string.
+- **BREAKING — simulation / sweep / dynamic create bodies drop the first-party
+  fields `solver`, `input_snapshot`, and `design_cl`.** These were never part of
+  the public product contract; passing them is no longer accepted. (They remain
+  present in *response* payloads where the server legitimately echoes them.)
+- **BREAKING — rotor-group count is capped at 16 total rotors (Σ ≤ 16)** across
+  all groups on a create request; larger configurations are rejected by the API.
+
+### Added
+
+- **`client.components.create(...)`** — create a private custom component
+  (`POST /v1/components`) without dropping to the raw transport. Takes
+  `type`, `name`, `spec_json`, and an optional `idempotency_key`.
+- Component create/update responses may carry a non-blocking `warnings` list
+  (`code` / `param` / `message`) when a spec value looks physically
+  implausible — e.g. a motor `R` far outside the expected range for its `kv`
+  and `weight` (milliohm/ohm mix-up, or a per-phase value where phase-to-phase
+  is expected). The write always succeeds.
+- **`client.compute_units.summary()`** — usage-meter read for the current
+  metering window (`GET /v1/compute-units/summary`).
+- **`client.dynamic_simulations` resource** (`create` / `retrieve` / `wait` /
+  `list` / `cancel` / `estimate`) mirroring `client.sweeps`, plus a runnable
+  dynamic example (`examples/dynamic/run_and_poll.py`).
+- Runnable end-to-end examples for all three simulation types
+  (single-point / sweep / dynamic) reading canonical `snake_case` result keys,
+  and a corrected README quickstart using the real create body
+  (`rotor_groups=[…]` + `battery_component_id`).
+
+### Fixed
+
+- **`cursor` pagination** — an explicit `starting_after=` kwarg on
+  `simulations.list`, `sweeps.list`, and `sweeps.list_points` was silently
+  ignored (the backend reads `cursor`). The keyword argument is now `cursor=`.
+  Automatic multi-page iteration was unaffected.
+
+### Migration from 0.1.x / 0.2.0
+
+```python
+# --- credits -> compute_units ---------------------------------------------
+# before (<= 0.2.0)
+balance = client.credits.balance()
+for ev in client.credits.usage(credit_type="simulation", starting_after=cur):
+    ...
+
+# after (0.3.0)
+balance = client.compute_units.balance()
+for ev in client.compute_units.transactions(credit_type="simulation", cursor=cur):
+    ...
+
+# --- removed resources ----------------------------------------------------
+# client.subscriptions.* and client.api_keys.* no longer exist — manage
+# subscriptions and API keys from the ThrustLab dashboard.
+
+# --- sweep result keys are snake_case (from 0.2.0) ------------------------
+# before: point["rotors"]["1"]["Thrust (N)"]
+# after:  point["rotors"]["1"]["thrust_n"]   # display_labels["thrust_n"] -> "Thrust (N)"
+```
+
+## [0.2.0] - 2026-07-09
+
+### Changed
+
+- **BREAKING — result payloads are now canonical `snake_case` across
+  single-point, sweep, AND dynamic endpoints, each with a sibling
+  `display_labels` map (`{snake_key: "Human Label"}`).** Single-point results
+  were already snake_case; this release aligns **sweep points** and **dynamic
+  samples** to the same contract. Consumers that parsed the old display-label
+  result keys on sweep points (`"Thrust (N)"`, `"RPM"`, `"Current (A)"`, …)
+  must now read the snake keys (`thrust_n`, `rpm`, `current_a`, …). Use the
+  sibling `display_labels` map to recover a human string for any key.
+
+  Migration:
+
+  ```python
+  # before (0.1.x) — sweep point rotor keys were display labels
+  thrust = point["rotors"]["1"]["Thrust (N)"]
+
+  # after (0.2.0) — canonical snake_case, with display_labels for UI
+  thrust = point["rotors"]["1"]["thrust_n"]
+  label  = sweep["display_labels"]["thrust_n"]   # -> "Thrust (N)"
+  ```
+
+### Added
+
+- **`client.dynamic_simulations` resource** (`create` / `retrieve` / `wait` /
+  `list` / `cancel` / `estimate`) mirroring `client.sweeps`, plus a runnable
+  dynamic example (`examples/dynamic/run_and_poll.py`).
+- Runnable end-to-end examples for all three simulation types
+  (single-point / sweep / dynamic) reading canonical snake_case result keys,
+  and a corrected README quickstart that uses the real create body
+  (`rotor_groups=[…]` + `battery_component_id`, not the phantom
+  `motor=/propeller=/battery=/throttle=` kwargs).
+
+### Fixed
+
+- **`cursor` pagination** — an explicit `starting_after=` kwarg on
+  `simulations.list`, `sweeps.list`, and `sweeps.list_points` was silently
+  ignored (the backend reads `cursor`). The keyword argument is now `cursor=`.
+  Automatic multi-page iteration was unaffected.
+
+### Corrected (documentation record)
+
+- The 0.1.0 changelog listed a `geometry` resource module and terminal states
+  `succeeded`/`cancelled` that never matched the shipped library. The SDK has
+  **no** `geometry` resource, and the canonical terminal states are
+  `completed` / `failed` / `canceled` (one-L wire spelling), with a
+  `timed_out` client-side sentinel from `wait()`.
+
+## [0.1.2] - 2026-07-08
+
+### Fixed
+
+- **`wait()` now recognizes the canonical terminal states
+  `completed`/`failed`/`canceled`** (one-L `canceled` wire spelling). The
+  previous set omitted `canceled`, so `wait()` polled forever on a canceled
+  run until it hit the timeout sentinel.
+
+## [0.1.1] - 2026-04-28
+
+### Changed
+
+- **License relicensed from MIT to Apache-2.0.** The Apache-2.0 license
+  includes an explicit patent grant scoped to the SDK plus a defensive
+  termination clause (anyone who sues ThrustLab for patent infringement
+  loses the patent grant). MIT had no explicit patent terms. ThrustLab
+  reserves all rights to the underlying simulation methodology that this
+  SDK calls; the license here applies only to this client library.
+- Added `NOTICE` file alongside `LICENSE` per Apache convention.
+
+### Migration from 0.1.0
+
+If you pinned `thrustlab==0.1.0`, upgrade to `thrustlab==0.1.1`. No code
+changes — only the license text differs. Version 0.1.0 has been yanked
+from PyPI.
+
+## [0.1.0] - 2026-04-27
+
+Initial public beta release of the official ThrustLab Python SDK.
+
+### Added
+
+- Full coverage of the `/v1/` API surface across **12 resource modules**:
+  `api_keys`, `users`, `projects`, `simulations`, `sweeps`, `components`,
+  `submissions`, `starred_components`, `geometry`, `credits`,
+  `subscriptions`, `webhook_endpoints`.
+- Sync transport (`httpx.Client`) with bearer-token authentication.
+- Auto-generated `Idempotency-Key` header on every mutating request (override
+  via `idempotency_key=` keyword argument).
+- Exponential backoff + jitter retry on 429, 5xx, and transient network
+  errors (`max_retries=3` default, configurable per client instance).
+- `CursorPager[T]` lazy iterator for cursor-paginated list endpoints;
+  transparent multi-page iteration.
+- `wait()` helpers on `simulations` and `sweeps` for polling async resources
+  to terminal state (`succeeded` / `failed` / `cancelled` / `timed_out`).
+- `Webhook.verify()` for HMAC SHA256 webhook signature verification with
+  configurable timestamp tolerance (default 300 s).
+- Stripe-style typed exception hierarchy:
+  `ThrustlabError` → `APIError` → `AuthenticationError`, `PermissionError`,
+  `NotFoundError`, `ValidationError`, `ConflictError`, `RateLimitError`,
+  `APIServerError`; plus `NetworkError`, `SignatureVerificationError`,
+  `ConfigurationError`.
+- Pydantic v2 models generated from `openapi.json` via
+  `openapi-python-client`; used internally for request/response shaping.
+- Configuration via constructor kwargs (`api_key`, `base_url`, `timeout`,
+  `max_retries`) or env vars (`THRUSTLAB_API_KEY`, `THRUSTLAB_BASE_URL`).
+- 103 unit + integration tests (pytest).
+
+### Out of scope (deferred)
+
+- Async transport (`httpx.AsyncClient`). Planned for v0.2.
+- Streaming response support.
+- Python 3.9 compatibility.
+- CLI tool (`thrustlab` command).
+- SDKs in other languages.
+
+## Pre-release rehearsal procedure
+
+Before tagging v0.1.0, rehearse with:
+
+1. Create a short-lived release-rehearsal branch from master.
+2. Tag `sdk-py-v0.0.1-rc1` and push it.
+3. The CI workflow runs build + TestPyPI publish only (gate step enforces
+   ancestry before either publish step fires).
+4. Delete the rehearsal tag + branch after validation.
+5. Tag `sdk-py-v0.1.0` from the actual master-merge commit for production publish.

thrustlab-0.4.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

thrustlab-0.4.0/NOTICE

@@ -0,0 +1,8 @@
+ThrustLab Python SDK
+Copyright (c) 2026 ThrustLab
+
+This product includes software developed by ThrustLab.
+Licensed under the Apache License, Version 2.0 (the "License").
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0