marqov 0.2.0__tar.gz

marqov-0.2.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Report a bug in the Marqov SDK
+labels: bug
+---
+
+**Describe the bug**
+A clear description of what the bug is.
+
+**To reproduce**
+Minimal code example that reproduces the issue:
+
+```python
+from marqov.circuits import Circuit
+from marqov.executors.local import LocalExecutor
+# ...
+```
+
+**Expected behavior**
+What you expected to happen.
+
+**Actual behavior**
+What actually happened, including any error messages or tracebacks.
+
+**Environment**
+- marqov version: (run `pip show marqov`)
+- Python version: (run `python --version`)
+- OS:
+- Provider/executor:

marqov-0.2.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest a new feature or improvement
+labels: enhancement
+---
+
+**What problem does this solve?**
+Describe the use case or limitation you're running into.
+
+**Proposed solution**
+Describe what you'd like to see added or changed.
+
+**Alternatives considered**
+Any alternative solutions or workarounds you've considered.
+
+**Additional context**
+Links to provider documentation, related issues, or examples.

marqov-0.2.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## Summary
+
+Brief description of what this PR does.
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New executor
+- [ ] Circuit format converter
+- [ ] Documentation
+- [ ] Other (describe):
+
+## Testing
+
+- [ ] I ran `pytest tests/ -v` and tests pass
+- [ ] For new executors: tested against local simulator or QVM (describe below)
+- [ ] For circuit converters: roundtrip test passes with known-correct reference circuit
+
+**Test details:**
+
+## Checklist
+
+- [ ] No hardcoded credentials or API keys
+- [ ] Handles the canonical gate set from `CONTRIBUTING.md §1` (if adding a circuit converter)
+
+**For new executors only:**
+- [ ] Registered in `ExecutorFactory` per `CONTRIBUTING.md §3`
+- [ ] `get_status()` returns device-level availability (`"online"/"offline"/"maintenance"`), not job-level status

marqov-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,24 @@
+name: CI
+on:
+  push:
+    branches: ["**"]
+  pull_request:
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - name: Install uv
+        run: pip install uv
+      # Install the [all] backend extras (qiskit/cirq/pennylane/pytket/quantinuum/
+      # pyquil): the circuit-interop / device / executor tests import these at
+      # module load and HARD-FAIL (ModuleNotFoundError) rather than skip when
+      # absent. Installing them is what makes the full suite green.
+      - name: Install (with all backend extras + dev)
+        run: uv pip install --system -e ".[all,dev]"
+      - name: No-URL-deps guard
+        run: python tools/check_no_url_deps.py
+      - name: Test suite
+        run: pytest tests/ -q

marqov-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,46 @@
+name: release
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:        # manual TestPyPI dry-run
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install uv && uv build
+      - name: Assert built version matches the tag (tag pushes only)
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          test -f "dist/marqov-${TAG}-py3-none-any.whl" \
+            || { echo "FAIL: built wheel is not version ${TAG} (check pyproject version)"; ls dist/; exit 1; }
+          echo "version OK: ${TAG}"
+      - uses: actions/upload-artifact@v4
+        with: { name: dist, path: dist/ }
+
+  publish-testpypi:
+    needs: build
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions: { id-token: write }
+    steps:
+      - uses: actions/download-artifact@v4
+        with: { name: dist, path: dist/ }
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  publish-pypi:
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions: { id-token: write }
+    steps:
+      - uses: actions/download-artifact@v4
+        with: { name: dist, path: dist/ }
+      - uses: pypa/gh-action-pypi-publish@release/v1

marqov-0.2.0/.gitignore

@@ -0,0 +1,19 @@
+.venv/
+.venv-gate/
+# Any virtualenv (e.g. .verify-venv) — excluded so the hatchling sdist build does
+# not try to bundle venv symlinks.
+*-venv/
+.*-venv/
+# Claude Code local tooling / worktrees — never ship in the sdist.
+.claude/
+__pycache__/
+*.pyc
+*.pyo
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+.env
+.env.local

marqov-0.2.0/CHANGELOG.md

@@ -0,0 +1,34 @@
+# Changelog
+
+All notable changes to the `marqov` SDK are documented here. This project follows
+[Semantic Versioning](https://semver.org/). While on `0.x`, the public API may
+still change between minor versions; `1.0.0` is reserved for the first API-stable
+release.
+
+## [0.2.0] — 2026-06-29
+
+First public release on PyPI.
+
+### Added
+- Public release of the `marqov` SDK: build quantum circuits and run them across
+  multiple hardware backends (AWS Braket, IBM Quantum, Azure Quantum, IonQ,
+  Rigetti, Quantinuum, and local simulation) behind one API.
+- Circuit interop helpers (import/export with Qiskit, Cirq, PennyLane, pytket,
+  and pyQuil) and workflow/task decorators for composing multi-step programs.
+
+### Changed
+- The circuit IR / transpilation dependency is now the published
+  [`marqov-quantumflow`](https://pypi.org/project/marqov-quantumflow/) package
+  instead of a git URL, which is what makes `pip install marqov` possible.
+- The package version is single-sourced from `marqov/__init__.py` (`__version__`)
+  via hatchling, so the distribution metadata, `marqov.__version__`, and
+  `marqov --version` always agree.
+
+### Known limitations
+- `@task`/`@workflow` serialize the decorated function with `cloudpickle` at
+  decoration time. When the function is a local/closure (not module-level) and a
+  large set of heavy backends is imported in the same process, this can overflow
+  into a `RecursionError`. Module-level task functions are unaffected. A fix that
+  defers/removes the function serialization is planned.
+
+[0.2.0]: https://pypi.org/project/marqov/0.2.0/

marqov-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,54 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders at ops@marqov.ai. All complaints will be
+reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

marqov-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,204 @@
+# Contributing to Marqov SDK
+
+Thank you for contributing. This guide covers everything you need to add a new
+executor, circuit converter, or other contribution to the Marqov SDK.
+
+## Development Setup
+
+```bash
+git clone https://github.com/marqov-dev/marqov-sdk
+cd marqov-sdk
+python3.12 -m venv .venv
+source .venv/bin/activate  # Windows: .venv\Scripts\activate
+pip install -e ".[all,dev]"
+pytest tests/ -v
+```
+
+## §1 — Canonical Gate Set
+
+All executor and circuit converter contributions must support the following
+gates and raise `NotImplementedError` for anything outside this set. This list
+is derived from `marqov/circuits.py` (`_QISKIT_GATE_MAP`) and represents what
+the SDK can round-trip today.
+
+| Category      | Gates                        |
+|---------------|------------------------------|
+| Single-qubit  | H, X, Y, Z, S, T            |
+| Rotation      | Rx(θ), Ry(θ), Rz(θ)         |
+| Two-qubit     | CNOT/CX, CZ, SWAP            |
+
+## §2 — Executor Interface
+
+All executors inherit from `BaseExecutor` in `marqov/executors/base.py`.
+
+### Required methods
+
+**`async execute(circuit: Circuit, shots: int = 1000, **kwargs) -> ExecutionResult`**
+
+Submit the circuit to the backend and return results. `ExecutionResult` fields
+you must populate:
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `counts` | `dict[str, int]` | Yes | Measurement outcomes e.g. `{"00": 512, "11": 488}` |
+| `backend` | `str` | Yes | Name or identifier of the backend |
+| `execution_time_ms` | `float` | Yes | Wall time in milliseconds |
+| `shots` | `int` | Yes | Number of shots executed |
+| `raw_result` | `Any` | No | Provider-specific result object, for debugging |
+| `metadata` | `dict` | No | Additional provider metadata |
+
+**`async cancel(job_id: str) -> bool`**
+
+Cancel a running job. Return `True` if successful, `False` otherwise. If the
+provider does not support cancellation, the default `BaseExecutor` implementation
+returns `False` — do not override it unless the provider supports cancellation.
+
+`job_id` is the provider's job or task identifier. Callers obtain it from
+`ExecutionResult.metadata` (e.g. `result.metadata["task_arn"]` for Braket).
+Executors that support cancellation should store the active job ID as instance
+state (e.g. `self._current_job_id`) and include it in `ExecutionResult.metadata`
+under a documented key. Job polling (queued → running → completed) happens
+internally inside `execute()` and is not related to this method.
+
+**`async get_status() -> DeviceStatus`**
+
+Return the QPU's **operational availability** — whether the device is currently
+accepting new job submissions. This is **device-level status**, not job-level
+status. Job polling (queued → running → completed) is handled internally inside
+`execute()` and is not exposed via `get_status()`.
+
+`DeviceStatus` fields:
+
+| Field | Type | Values |
+|-------|------|--------|
+| `status` | `str` | `"online"`, `"offline"`, `"maintenance"` |
+| `queue_depth` | `int \| None` | Number of queued tasks, or `None` if unknown |
+| `queue_time_seconds` | `int \| None` | Estimated queue wait, or `None` if unknown |
+
+The default `BaseExecutor.get_status()` returns `DeviceStatus.always_online()`.
+Cloud backends should override this to query the provider's device status endpoint.
+
+## §3 — Adding a New Executor
+
+1. Create `marqov/executors/<name>.py` with a config dataclass and executor class:
+
+```python
+from dataclasses import dataclass
+from typing import Any
+from marqov.executors.base import BaseExecutor, DeviceStatus, ExecutionResult
+from marqov.circuits import Circuit
+
+@dataclass
+class MyProviderExecutorConfig:
+    api_key: str
+    device_name: str
+    shots: int = 1000
+
+class MyProviderExecutor(BaseExecutor):
+    def __init__(self, config: MyProviderExecutorConfig) -> None:
+        self.config = config
+
+    async def execute(self, circuit: Circuit, shots: int = 1000, **kwargs: Any) -> ExecutionResult:
+        # convert circuit, submit, poll, return ExecutionResult
+        ...
+
+    async def get_status(self) -> DeviceStatus:
+        # query provider device status endpoint
+        ...
+```
+
+2. Register in `marqov/executors/factory.py`:
+   - Add import at top: `from marqov.executors.<name> import MyProviderExecutor, MyProviderExecutorConfig`
+   - Add branch in `create_executor()`:
+     ```python
+     if provider == "My Provider":
+         return cls._create_myprovider_executor(backend_slug, backend_config)
+     ```
+   - Add `_create_myprovider_executor()` classmethod following the pattern of `_create_ibm_executor()`
+   - Add `"My Provider"` to the list in `get_supported_providers()`
+
+3. Add the provider package to `pyproject.toml` as an optional dependency:
+   ```toml
+   [project.optional-dependencies]
+   myprovider = ["my-provider-sdk>=1.0.0"]
+   ```
+
+4. Export from `marqov/executors/__init__.py`.
+
+## §4 — Local QVM Setup (Rigetti executor development)
+
+The Rigetti QCS executor tests run against a local QVM instance. QVM requires
+`quilc` running alongside it.
+
+```bash
+docker pull rigetti/quilc
+docker pull rigetti/qvm
+docker run -d -p 5555:5555 rigetti/quilc -server
+docker run -d -p 5000:5000 rigetti/qvm -server
+```
+
+Verify:
+```bash
+python -c "from pyquil import get_qc; qc = get_qc('2q-qvm'); print(qc)"
+```
+
+Expected output: `<QVM 2q-qvm>` or similar. If you see a connection error,
+check both containers are running with `docker ps`.
+
+## §5 — Running Benchmarks
+
+`benchmarks/suite.py` runs a fixed set of reference circuits — Bell, 3-qubit
+GHZ, and a deterministic depth-5 random circuit — against any configured
+executor and prints a comparison table. It works out of the box with
+`LocalExecutor`, so no credentials are required:
+
+```bash
+python benchmarks/suite.py --executor local --shots 1000 --seed 1234
+```
+
+Output format — one row per (backend × circuit) combination:
+
+| backend | circuit   | shots | exec_time_ms | top_3_outcomes                       |
+|---------|-----------|-------|--------------|--------------------------------------|
+| local   | bell      | 1000  | 0.4          | {"11": 502, "00": 498}               |
+| local   | ghz       | 1000  | 0.4          | {"111": 524, "000": 476}             |
+| local   | random_d5 | 1000  | 0.4          | {"010": 262, "100": 254, "110": 243} |
+
+Columns:
+- `backend`: executor name
+- `circuit`: circuit name (`bell`, `ghz`, `random_d5`)
+- `shots`: number of shots
+- `exec_time_ms`: wall time in milliseconds (varies per run and machine)
+- `top_3_outcomes`: counts of the 3 most frequent measurement outcomes, ordered
+  by count descending
+
+The measurement outcomes above are reproducible for a fixed `--seed` (it seeds
+both the random circuit and the local sampler); `exec_time_ms` is wall time and
+will differ on your machine.
+
+**Scope.** The suite compares execution time and outcome distribution only.
+Shot-fidelity and queue-overhead metrics are out of scope for this harness;
+device-level queue status is available separately via `BaseExecutor.get_status()`.
+
+**Error handling.** If a backend errors on any circuit, the suite skips that
+*entire* backend (it emits no partial rows for it), logs the backend and the
+failing circuit to stderr, and continues with the next backend — it never
+aborts. If every backend fails the command exits non-zero, so CI can flag a
+fully broken run.
+
+**Benchmarking other backends.** The CLI only constructs the zero-credential
+`local` executor, but `run_suite()` is executor-agnostic — pass a mapping of
+name → `BaseExecutor` to benchmark cloud backends programmatically:
+
+```python
+import asyncio
+from benchmarks.suite import run_suite, format_table
+from marqov.executors import ExecutorFactory, LocalExecutor
+
+executors = {
+    "local": LocalExecutor(),
+    "sv1": ExecutorFactory.create_executor("sv1", braket_config),
+}
+rows = asyncio.run(run_suite(executors, shots=1000))
+print(format_table(rows))
+```

marqov-0.2.0/LICENSE

@@ -0,0 +1,184 @@
+                                 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 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, as submitted to the 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 designated in writing by the copyright owner as "Not a
+      Contribution."
+
+      "Contributor" shall mean Licensor and any Legal Entity on behalf of
+      whom a Contribution has been received by the Licensor and included
+      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 the 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 any
+      Contributor's Contribution(s) constitutes direct or contributory
+      patent infringement, then any patent rights 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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 in addition 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Contribution, either on an unrestrictive basis or under the terms of
+      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 reproducing 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 exemplary 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 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 offer such
+      obligations 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
+
+   Copyright 2026 Marqov
+
+   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.