zenture 1.0.1__tar.gz

zenture-1.0.1/.gitignore

@@ -0,0 +1,11 @@
+.coverage
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.venv/
+__pycache__/
+*.py[cod]
+dist/
+build/
+*.egg-info/
+scratch/

zenture-1.0.1/AGENTS.md

@@ -0,0 +1,173 @@
+# AGENTS.md
+
+Purpose: onboard contributors and coding agents to the official Python client
+for the zenture REST API and hosted MCP endpoint.
+
+## Repository Purpose
+
+`zenture-client` is the official server-side Python REST client and the
+implementation home for hosted MCP peers and explicit native authentication.
+The default installation includes REST, MCP, native auth, and the `zenture`
+command; no extra is required. API tokens are REST-only, account OAuth is
+MCP-only, and Backend/Engine retain authorization, execution, billing, and
+tenant authority. The package provides no local MCP server. It is intended
+for backend services, workers, automation jobs, CI, evaluation pipelines, controlled
+notebooks and governed MCP-consuming clients. It is not for browsers, mobile
+apps, or frontend bundles.
+
+Package names:
+
+- Distribution: `zenture`
+- Import package: `zenture`
+- Sync client: `ZentureClient`
+- Async client: `AsyncZentureClient`
+
+Public product references:
+
+- Users create API tokens at `https://ai.zenture.app/profile?tab=api-tokens`.
+- Human-facing API documentation lives at
+  `https://www.zenture.app/developers`.
+- The committed `openapi/zenture-public-api-v1.openapi.json` file remains the
+  SDK-local contract source of truth for implementation and drift tests.
+
+## Architecture Map
+
+- `src/zenture/client.py` and `src/zenture/async_client.py`: public clients.
+- `src/zenture/_resources/`: private resource implementation classes backing
+  public `client.<resource>` attributes for operations, chat, input wizard,
+  evaluations, models, billing, usage, limits, and helloworld.
+- `src/zenture/_transport/`: private sync/async `httpx` transport layer.
+- `src/zenture/auth/`: public explicit login (`login`, `login_async`) and the
+  auth errors; implementation in private `src/zenture/_auth/`.
+- `src/zenture/mcp/`: public `McpClient` / `AsyncMcpClient`; implementation in
+  private `src/zenture/_mcp/` (transport ports, official Streamable HTTP binding,
+  typed Run adapter). It owns no Backend, Engine or persistence authority.
+- `src/zenture/cli.py`: the `zenture auth login|status|clear` command.
+- `src/zenture/_contract/`: internal OpenAPI-derived Pydantic models.
+- `src/zenture/errors.py`: typed SDK exceptions.
+- `src/zenture/polling.py`: polling policy primitives.
+- `src/zenture/retries.py`: retry decision policy.
+- `src/zenture/idempotency.py`: idempotency-key helpers.
+- `src/zenture/redaction.py`: secret redaction helpers.
+
+## Public vs Internal Surface
+
+Only `ZentureClient`, `AsyncZentureClient`, and `__version__` are top-level
+public exports.
+Do not export internal `_contract` models from `zenture.__init__`.
+
+Public MCP/auth surface: `zenture.auth` (`login`, `login_async`, `AuthSession`,
+`AuthorizationRequired`, `AuthUnavailable`, `SecureStoreUnavailable`,
+`PermissionDenied`, `LoginCancelled`), `zenture.mcp` (`McpClient`,
+`AsyncMcpClient`) and the `zenture` command. `_auth`, `_mcp` and similar
+underscore namespaces are implementation details.
+
+Resource methods such as `client.chat.run(...)`, `client.models.list(...)`, and
+`client.operations.wait(...)` are the ergonomic public API. `_transport`,
+`_resources`, and `_contract` are implementation namespaces even when tests
+import them.
+
+## Contract drift
+
+The OpenAPI artifact in `openapi/zenture-public-api-v1.openapi.json` is the
+local contract source of truth. Contract tests under
+`tests/integration/contract/` verify operation statuses, error codes, bounded
+operation result shapes, idempotency header constraints, and excluded
+user-session routes.
+
+Use `https://www.zenture.app/developers` for human-facing API context,
+but do not implement SDK behavior from website prose unless the local OpenAPI
+artifact and drift tests agree.
+
+When adding or changing a resource:
+
+- Confirm the route exists in OpenAPI.
+- Add or update internal Pydantic contract models.
+- Add contract drift tests where the schema meaning matters.
+- Add sync and async resource tests using `httpx.MockTransport`.
+- Keep examples and docs aligned with the public surface.
+
+When a new Engine capability is intended for client consumption, extend this
+repository's canonical contract models and both peer surfaces: the API
+resource and the hosted MCP peers. Add sync/async parity and cross-channel
+acceptance tests here before release promotion; do not create a workspace-only client duplicate or move Engine/business authority into the
+SDK.
+
+## Using zenture as an agent
+
+Contracts: [`README.md`](./README.md) (quickstart, errors, exit codes),
+[`docs/authentication.md`](./docs/authentication.md),
+[`docs/mcp-client.md`](./docs/mcp-client.md), and
+[`docs/migration.md`](./docs/migration.md) (uninstall-first upgrade and published
+return baseline).
+
+- Check the connection with `zenture auth status` (exit code 0 means connected).
+  Only a human at a terminal should run `zenture auth login`; explain what is
+  needed and stop instead of logging in on the user's behalf.
+- no implicit login: call `McpClient.connect()` / `AsyncMcpClient.connect()` with
+  the stored authorization and handle `AuthorizationRequired` by reporting
+  "run `zenture auth login`".
+- no private imports: use `zenture`, `zenture.auth`, `zenture.mcp` only, never
+  underscore modules of the package.
+- never print, log, store or paste tokens, refresh credentials, codes or
+  authorization URLs. Session objects are safe to print; do not try to extract
+  credentials from them.
+- Sync `McpClient` must not run inside a running event loop; use `AsyncMcpClient`.
+- Do not use `zenture auth clear` to revoke access; it is local only. Revocation
+  happens in zenture under Zugriff & Sicherheit -> Verbindungen.
+- Save a caller-owned `run(idempotency_key=...)` key before dispatch when a Run
+  must survive interruption or restart. Reuse that key and the same request for
+  deliberate recovery; never switch to a new key after an uncertain outcome.
+  Read `run.idempotency_key` or `ZentureMCPError.idempotency_key` separately from
+  model serialization; do not log keys or treat receipts as effect evidence.
+
+## Required Commands
+
+```bash
+python3 -m ruff format --check .
+python3 -m ruff check .
+python3 -m mypy
+python3 -m pyright
+python3 -m pytest
+python3 -m coverage run -m pytest
+python3 -m coverage report
+python3 -m build
+python3 -m twine check dist/*
+```
+
+Remove local artifacts after verification: `.coverage`, `.pytest_cache`,
+`.ruff_cache`, `.mypy_cache`, `dist/`, and `__pycache__/`.
+
+## Security Red Lines
+
+- no token logging
+- no token literals in examples, docs, tests, or issue text
+- no arbitrary base URL origins
+- no API-token-management SDK resource
+- no public helper for agentic chat mode in Public V1
+- no internal `_contract` top-level exports
+- no request or response body logging by default
+- no private infrastructure details in public docs
+
+## Contribution Expectations
+
+New resources must include typed sync and async behavior, idempotency safety for
+mutating calls, no real network tests, and public-safe docs/examples when the
+usage surface changes.
+
+Examples must use `ZentureClient.from_env()` or `AsyncZentureClient.from_env()` for REST
+and the documented auth/MCP public APIs (`zenture.auth`, `zenture.mcp`) for sign-in and MCP.
+Mutating examples must pass explicit stable idempotency keys, preferably built with the
+SDK helper. Do not create tracked `.env` files.
+
+## Pull Request Rules
+
+Use one primary PR type: `type: fix`, `type: feat`, `type: docs`,
+`type: test`, `type: chore`, `type: refactor`, or `type: security`.
+
+Every PR must keep public docs production-relevant, avoid internal routes, avoid
+real token patterns, and preserve the private/public package boundary. Public
+API changes require matching tests, README/docs updates, and changelog coverage.
+
+Required review posture: small focused PRs, `Development CI` green, CODEOWNERS
+review once branch protection is available, and squash merge only.

zenture-1.0.1/CHANGELOG.md

@@ -0,0 +1,114 @@
+# Changelog
+
+All notable changes to `zenture` will be documented in this file.
+
+The project follows semantic versioning once public releases begin. Prerelease
+versions may change while the Public API contract is still in release-candidate
+state.
+
+## 1.0.1 - 2026-10-10
+
+- Documentation leads with Runs; the classic API resources are documented as secondary.
+
+- MCP peers keep authorization failures (`AuthorizationRequired`,
+  `PermissionDenied`, including inside an `ExceptionGroup`) classified and
+  do not retry them in `wait_run` or discovery; only unknown transport failures
+  are wrapped as retryable `mcp_transport_unavailable`.
+
+- MCP result-contract errors no longer chain the Pydantic validation error, so
+  submitted values do not appear in tracebacks.
+
+- The MCP run review example uses `wait_run` under one caller budget that also
+  covers the final full read; a late completion raises `ZenturePollingTimeoutError`.
+
+- The end-to-end example reports a billed total only when every component is
+  known, and names the operations included in each total.
+
+- Documented `wait_run` on both MCP peers and clarified that MCP `run()` only
+  starts a Run. Documented in-process `login(session_only=True)`; the CLI
+  `--session-only` option is verification only. PyPI publication requires
+  Trusted Publishing without a long-lived token fallback.
+
+- Examples print identifiers and status by default; evaluation results and the
+  optimized prompt require `--show-result` / `--show-prompt`.
+
+- Added immutable typed validation `issues` on REST and MCP errors, bounded by
+  public field schemas, and content-free local Run `ValidationError` summaries.
+  Sync/async REST Run and artifact requests automatically negotiate safe details
+  with `X-Zenture-Error-Details: issues`; older servers remain supported.
+
+- Added sync/async `get_tool_catalog()` and public `zenture.mcp.McpToolDefinition`
+  for detached registered schemas, descriptions and annotations, with bounded
+  complete pagination. Existing name-only `list_tools()` behavior is preserved.
+
+- MCP Run peers now allocate or accept a strict caller-owned idempotency key and
+  expose validated Run-only success/error receipts for deliberate recovery.
+  Save an explicit key before interruption; default model serialization and
+  REST models retain their existing shape.
+
+- Rename the repository to `zenture-client`, the distribution to `zenture`, and
+  public API classes to `ZentureClient` / `AsyncZentureClient` without aliases.
+- Preserve API-token resource behavior and caller-provided bearer MCP support;
+  Public package publication remains outside this source cutover.
+- Added native authorization for the hosted MCP endpoint: explicit browser
+  (PKCE, loopback) and headless device login through `zenture.auth.login` /
+  `login_async`, secure credential storage (macOS Keychain proven; Windows
+  Credential Manager and Linux Secret Service implemented, not yet verified)
+  with a session-only mode, and safe refresh that requires a new login after an
+  interrupted refresh.
+- Added the `zenture` command: `zenture auth login [--device] [--session-only]`,
+  `zenture auth status` and `zenture auth clear` with documented exit codes.
+- Added the public `zenture.mcp` module with `McpClient` and `AsyncMcpClient`
+  exposing the six Run tools; the former `zenture._mcp` path is internal and no
+  alias exists (hard cutover).
+- Declared CPython 3.14 support and configured the CI matrix for 3.11 to 3.14
+  across Linux, macOS and Windows (configured, not yet run).
+
+- Added nullable `deadline_at` Run response fields, additive response tolerance,
+  and finite sync/async Run waits with deadline-aware timeout context.
+- Added an opt-in, internal MCP client peer adapter with sync/async transport
+  ports, official Streamable HTTP integration, typed Run mappings, bounded safe
+  errors and local cross-channel composition tests. The API-only installation
+  remains unchanged; public `zenture-client` promotion is deferred.
+
+## 1.0.0rc3 - 2026-06-28
+
+- Clarified external vs. internal evaluation flows across SDK docs.
+- Added local SDK validation for internal evaluation target payloads.
+- Updated evaluation error handling docs for local `ValidationError` and API
+  `ZentureValidationError`.
+
+## 1.0.0rc2 - 2026-06-27
+
+- Updated the README logo to use the public production-hosted zenture logo so
+  PyPI renders the project description correctly.
+
+## 1.0.0rc1 - 2026-06-27
+
+- Added `client.wallet.get()` and `await client.wallet.get()` for the public
+  `GET /v1/wallet` account projection with `wallet:read` scope.
+- Removed the unpublished `client.billing.get()` mapping and `/v1/billing`
+  SDK surface in favor of wallet terminology before public release.
+- Added optional `chat.run(..., include_content=True)` and
+  `evaluations.run(..., include_detail=True)` attachments for common
+  chat-then-evaluate application flows.
+- Added an end-to-end chat evaluation smoke example with wallet, model
+  discovery, input wizard, chat, evaluation, and billed-amount summary output.
+- Synced the Public API OpenAPI artifact with pagination parameters for chats,
+  chat messages, and evaluations.
+- Added `limit` and `cursor` support plus sync/async iterator helpers for chat
+  summaries, chat messages, and evaluations.
+- Added pagination documentation and an executable pagination example.
+- Updated operation-error contract handling to match the current OpenAPI
+  `PublicOperationError` schema.
+
+## 0.1.0b1 - 2026-06-15
+
+- Added SDK architecture and implementation plan.
+- Added repository governance bootstrap documents.
+- Added public sync/async clients, private httpx transport, strict contract
+  models, model discovery, single-/multi-model chat, evaluation creation,
+  operation reads, billing, usage, limits, idempotency, retry, timeout and
+  polling primitives.
+
+- Add sync/async MCP `wait_run` with finite deadlines, same-Run summary observation, safe read retries and official per-call read budgets.

zenture-1.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,14 @@
+# Code of Conduct
+
+zenture SDK contributors are expected to participate professionally, respectfully,
+and constructively.
+
+Unacceptable behavior includes harassment, abusive comments, intimidation,
+disruptive conduct, publishing private information without permission, or any
+behavior that makes the project unsafe for maintainers or contributors.
+
+Maintainers may remove comments, reject contributions, restrict participation, or
+take other action needed to protect the project.
+
+Security issues must be reported through the private process described in
+`SECURITY.md`, not through public issues or pull requests.

zenture-1.0.1/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing
+
+`zenture-client` provides the public `zenture` Python SDK for the zenture Public API. The current
+repository contains the runtime SDK, typed contract layer, public docs,
+examples, and packaging configuration used for prerelease validation.
+
+## Development Standards
+
+- Keep public APIs typed and exposed through `ZentureClient`, `AsyncZentureClient`, and
+  resource attributes such as `client.chat`.
+- Keep `_transport`, `_resources`, and `_contract` as implementation
+  namespaces.
+- Use Pydantic models for request, response, and configuration validation.
+- Use `httpx` for sync and async HTTP transport.
+- Do not log secrets, prompts, raw request bodies, or raw response bodies.
+- Add deterministic tests for behavior changes.
+- Keep README, docs, examples, and `AGENTS.md` aligned when public behavior
+  changes.
+- Maintainers may run controlled non-production checks using the private
+  environment runbook. Do not commit non-production hostnames, local port
+  conventions, tokens, payloads, or logs.
+
+## Pull Requests
+
+All changes should go through a pull request into `main`. Keep pull requests
+small and reviewable: one topic per PR, no unrelated formatting churn, and no
+mixed feature/security/release work.
+
+Pull requests should include:
+
+- a concise description of the change
+- tests or a clear reason tests are not applicable
+- documentation updates when behavior, public API, security posture, examples,
+  or release process changes
+- confirmation that no real zenture API tokens or customer data were added
+
+Use one primary PR type:
+
+- `type: fix` - bug fix or incorrect SDK behavior
+- `type: feat` - new public SDK capability
+- `type: docs` - README, examples, AGENTS, changelog, or prose docs
+- `type: test` - tests only
+- `type: chore` - CI, packaging, metadata, dependency upkeep
+- `type: refactor` - internal change with no public behavior change
+- `type: security` - security hardening or vulnerability fix
+
+Public-surface changes require extra care. Any change to `ZentureClient`,
+`AsyncZentureClient`, public resources, public errors, return types, examples, or
+OpenAPI-derived contract behavior must update tests and docs in the same PR.
+Breaking changes are not allowed in V1 without an explicit release decision,
+migration note, and changelog entry.
+
+Before merge:
+
+- `Development CI` must pass.
+- CODEOWNERS review must be satisfied once branch protection is available.
+- Security, docs, and artifact checklist items in the PR template must be
+  answered truthfully.
+- Use squash merge only; the PR title becomes the commit title.
+- Delete the branch after merge.
+
+## Local Checks
+
+Run the full local gate before handing off SDK changes:
+
+```bash
+python3 -m ruff format --check .
+python3 -m ruff check .
+python3 -m mypy
+python3 -m pyright
+python3 -m pytest
+python3 -m coverage run -m pytest
+python3 -m coverage report
+python3 -m build
+python3 -m twine check dist/*
+```
+
+Tests must not hit the real zenture API. Use `httpx.MockTransport` or static
+checks for docs and examples.
+
+## Release Process
+
+Public PyPI releases are blocked until the SDK reviewer gate passes. Publishing
+must use PyPI Trusted Publishing through GitHub Actions OIDC, not long-lived
+package tokens.

zenture-1.0.1/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 2026 zenture UG (haftungsbeschraenkt)
+
+   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.

zenture-1.0.1/NOTICE

@@ -0,0 +1,7 @@
+zenture SDK
+Copyright 2026 zenture UG (haftungsbeschraenkt)
+
+This product includes software developed by zenture UG (haftungsbeschraenkt).
+
+Third-party dependency license information is documented in
+THIRD_PARTY_NOTICES.md.