clusteraudiencekit 7.3.0__tar.gz → 7.3.1__tar.gz

clusteraudiencekit-7.3.1/.github/pull_request_template.md

@@ -0,0 +1,20 @@
+## What does this change do, and why?
+
+<!-- Link an issue if there is one. -->
+
+## How was this tested?
+
+<!--
+This project's real test paths (see CONTRIBUTING.md):
+- Rust: `cargo test --release` (works on Linux/CI; currently does not run
+  standalone on macOS — see docs/ROADMAP_HONEST.md)
+- Python, end-to-end through the compiled extension (works on macOS too):
+  `maturin develop --release && pytest tests/`
+-->
+
+- [ ] Added/updated a Rust `#[cfg(test)]` unit test in the module you changed
+- [ ] Added/updated a Python-level test in `tests/` exercising the real PyO3 binding
+- [ ] `cargo fmt --all -- --check` passes
+- [ ] `pytest tests/` passes
+
+## Anything reviewers should pay extra attention to?

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/.github/workflows/ci.yml

@@ -52,3 +52,27 @@ jobs:
 
       - name: Run pytest
         run: if [ -d "tests" ]; then pytest tests/ -v --tb=short; else echo "No Python tests found"; fi
+
+  security-audit:
+    # New job (2026-09-20 OSS-standardization pass). Not previously present
+    # anywhere in this repo's CI. Could not be verified from the sandbox
+    # this was added in (`cargo audit`'s advisory-db fetch over git needs
+    # outbound network access this sandbox didn't have), but GitHub-hosted
+    # runners have full internet access, so this should run for real here.
+    # See docs/ROADMAP_HONEST.md.
+    name: Cargo Security Audit
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: dtolnay/rust-toolchain@stable
+
+      - uses: Swatinem/rust-cache@v2
+        with:
+          workspaces: .
+
+      - name: Install cargo-audit
+        run: cargo install cargo-audit --locked
+
+      - name: Run cargo audit
+        run: cargo audit

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/.github/workflows/tests.yml

@@ -8,7 +8,7 @@ jobs:
         python-version: ["3.10", "3.11", "3.12"]
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
       - name: Install
@@ -24,4 +24,13 @@ jobs:
         # have been silently swallowed rather than turning CI red.
         run: pytest
       - name: Lint
-        run: ruff check . 2>/dev/null || true
+        # Previously `ruff check . 2>/dev/null || true`, which discarded
+        # ruff's stderr AND always exited 0 - silently hiding findings
+        # entirely, the same "always green" anti-pattern already fixed once
+        # in the Test step above. Then briefly `continue-on-error: true`
+        # (2026-09-20) because `ruff check .` had 33 real, pre-existing
+        # findings and a hard gate would've turned CI red on unrelated debt.
+        # Those 33 findings were fixed for real in the 2026-09-21 quick-fix
+        # pass (see docs/ROADMAP_HONEST.md) - `ruff check .` is clean now,
+        # so this is a real, blocking gate again.
+        run: ruff check .

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/.gitignore

@@ -26,6 +26,18 @@ __pycache__/
 dist/
 build/
 .pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+.hypothesis/
+
+# pytest-benchmark output (declared dev dependency in pyproject.toml).
+# .deepeval/ is unrelated local tooling output seen in this checkout, not a
+# declared project dependency, but shouldn't be committed either way.
+.benchmarks/
+.deepeval/
 
 # Compiled extension module (built in-place by `maturin develop` into
 # clusteraudiencekit/) and maturin/wheel build output

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/CHANGELOG.md

@@ -2,6 +2,121 @@
 
 All notable changes to ClusterAudienceKit are documented here.
 
+## [Unreleased]
+
+## [7.3.1] - 2026-09-22
+
+Two passes, no version bump until this release. 2026-09-20 was documentation/CI-hygiene only
+(full detail in `docs/ROADMAP_HONEST.md`'s "Documentation and structural
+issues found (2026-09-20)"). 2026-09-21 is a quick-fix pass with real,
+verified code changes (full detail in that file's "Quick-fix pass
+(2026-09-21)" section): all 33 `ruff` findings, a clippy-blocking compile
+error, dead code, a non-snake-case rename, and the macOS `cargo test` crash.
+
+### Fixed (2026-09-21 quick-fix pass)
+- `.github/workflows/tests.yml`'s `Lint` step (`ruff check .`) is a real,
+  blocking gate again — the 33 pre-existing `ruff` findings it was
+  `continue-on-error`'d around (see `### Changed` below) are all fixed.
+  Narrowed 5 `pytest.raises(Exception)`/bare-`except` blocks in
+  `tests/test_clustering.py`, `tests/test_wired_modules.py`,
+  `tests/test_sql_export.py`, and `examples/sql_export_example.py` to the
+  actual exception type each PyO3 binding raises (`RuntimeError` for
+  `kmeans`, `ValueError` for the streaming/lifecycle/SQL-export parsers —
+  confirmed by reading the `PyErr::new::<...>` call sites in
+  `src/python.rs`, not guessed); added explicit `tzinfo=timezone.utc` to
+  3 naive `datetime.datetime(...)` calls (`DTZ001`) in
+  `examples/basic_segmentation.py`/`tests/test_basic.py`/
+  `tests/test_performance.py` (safe — the values are only ever consumed via
+  `.strftime(...)`); `ClassVar` annotations on 2 mutable class-attribute
+  defaults; 3 unused unpacked variables prefixed with `_`; 2 unused
+  variables and 1 bare `except:` cleaned up in
+  `examples/sql_export_example.py`; that file's shebang made executable;
+  10 further findings (import sorting, `__all__` order, a redundant
+  f-string prefix) auto-fixed via `ruff check . --fix` with a verified
+  no-semantic-change diff. `python -m pytest tests/ -q`: 229 passed, 0
+  failed (unchanged pass count from before, modulo the 2 environment-only
+  sklearn skips noted in `docs/ROADMAP_HONEST.md`).
+- `cargo clippy --workspace --all-targets` had silently stopped completing
+  at all (new toolchain drift turned `clippy::approx_constant`, deny by
+  default, into a hard compile error on a hand-written `0.693_147` literal
+  in `segment_intelligence.rs` that approximates `LN_2`). Fixed with
+  `std::f64::consts::LN_2` (same value to ~1e-7, no behavior change).
+- Deleted the dead/duplicate `src/engine/metrics.rs` (predated and
+  duplicated `src/engine/quality_metrics.rs`, the module actually wired to
+  Python; confirmed unreferenced anywhere else before deleting) and its
+  `pub mod metrics;` declaration, removing 3 clippy warnings.
+- Renamed the non-snake-case `X` parameter (leftover ML-paper notation) to
+  `inputs` across `neural_networks.rs`'s four `train`/`anomaly_scores`/
+  `extract_patterns` methods and their tests, removing 17 clippy warnings.
+  `cargo clippy --workspace --all-targets`: 37 → 30 warnings, all still in
+  already-documented deferred/unwired modules (see `docs/ROADMAP_HONEST.md`).
+- **`cargo test` on macOS.** `Cargo.toml`'s `pyo3` dependency no longer
+  hardcodes the `extension-module` feature; it's now behind a `default`-on
+  crate feature of the same name. Every existing build path (`cargo build`,
+  `cargo bench`, `cargo clippy`, `maturin develop`, and CI's
+  `--all-features` invocations) still gets it automatically — verified
+  unaffected (same clippy warning count, `cargo fmt --check` still clean,
+  same `pytest` pass count against the `maturin develop`-built wheel;
+  `Cargo.lock` unchanged). New working path:
+  `cargo test --release --no-default-features --lib` (needs a Python with
+  a linkable `libpython`, e.g. via `PYO3_PYTHON` — see `CONTRIBUTING.md`).
+  Verified: 435 passed, 0 failed.
+
+### Changed (2026-09-20 doc/CI-hygiene pass)
+- Archived 15 stale/fabricated docs to `docs/archive/` (with an index
+  explaining each): five previously banner-flagged docs describing a
+  fictional `AudienceSegmenter(method=...)` API and fabricated benchmarks
+  (`api-reference.md`, `getting-started-simple.md`, `comparison.md`,
+  `performance-comparison.md`, `press-release.md`); four more with the same
+  problem that were never flagged before (`WORKFLOW_INTEGRATION.md` —
+  documented a CLI and REST server that don't exist anywhere in this
+  codebase; `troubleshooting.md`; `error-catalog.json`, unused by any code);
+  two independently-stale architecture docs, including root `ARCHITECTURE.md`,
+  which described integration with four other products via code samples
+  referencing crates this project has no dependency on; a superseded
+  `docs/ROADMAP.md`; a `docs/CONTRIBUTING.md` that was actually mislabeled
+  `CLAUDE.md`-style content; a stale duplicate `docs/SECURITY.md`; a `v1.5.0`
+  `docs/PYPI_UPLOAD.md`; and an unfilled `.github/CI_ERRORS.md` template with
+  dead links.
+- Replaced the two archived architecture docs with a new
+  `docs/architecture/README.md`, checked directly against `src/` (real
+  module list, PyO3 boundary, Mermaid data-flow diagram).
+- Rewrote `examples/streaming_updates.py`, previously an unimplemented stub
+  ("TODO: Implement... once core functionality is ready") despite
+  `StreamingSegmentationEngine` being real and Python-wired since 7.2.0.
+  Verified to run.
+- `CONTRIBUTING.md`: added a Rust/PyO3 build section (macOS `RUSTFLAGS`
+  workaround, and a newly-found `cargo test` macOS bug — see Fixed below);
+  fixed a stale "proprietary license" contributor-agreement line (repo is
+  Apache-2.0); replaced a fabricated `.fit_predict()` test example with a
+  real, verified one; replaced an unmeasurable ">90% coverage" instruction;
+  removed an unverifiable "review within 7 days" promise.
+- `SECURITY.md`: removed an unverifiable "acknowledge within 24 hours" SLA
+  promise.
+- `.github/workflows/tests.yml`: `Lint` step (`ruff check . 2>/dev/null ||
+  true`) always exited 0 regardless of findings — the same "always green"
+  anti-pattern already fixed once in this same file's `Test` step (see
+  `[7.2.0]` below), reintroduced here. Changed to `continue-on-error: true`
+  (visible-but-non-blocking) rather than a hard gate, since `ruff check .`
+  currently reports 33 real, pre-existing findings in `tests/` that this
+  pass didn't fix. Bumped `actions/setup-python@v4` to `@v5`.
+- `.gitignore`: added `.coverage`, `htmlcov/`, `.mypy_cache/`, `.ruff_cache/`,
+  `.hypothesis/`, `.benchmarks/`, `.deepeval/`.
+
+### Added (2026-09-20 doc/CI-hygiene pass)
+- `.github/workflows/ci.yml`: new `security-audit` job running `cargo
+  audit` (unverified from the sandbox this was added in — see
+  `docs/ROADMAP_HONEST.md`).
+
+### Found this pass, documented, code-fixed the next day (2026-09-20 → 2026-09-21)
+- `cargo test` cannot run at all on macOS (`dyld: symbol not found
+  '_PyBaseObject_Type'`, SIGABRT) because `pyo3`'s `extension-module`
+  feature is unconditionally enabled in `Cargo.toml` rather than
+  feature-gated for test builds. `maturin develop --release && pytest
+  tests/` was the verified-working alternative (227 passed, 2 skipped,
+  2026-09-20) at the time this was found. **Fixed the next day** — see the
+  `### Fixed (2026-09-21 quick-fix pass)` section above.
+
 ## [7.3.0] - 2026-08-30
 
 ### Fixed

clusteraudiencekit-7.3.1/CONTRIBUTING.md

@@ -0,0 +1,211 @@
+# Contributing to ClusterAudienceKit
+
+Thank you for your interest in contributing to ClusterAudienceKit!
+
+## Code of Conduct
+
+Be respectful and constructive in all interactions. We're committed to providing a welcoming and inclusive environment.
+
+## Getting Started
+
+### Fork and Clone
+
+```bash
+git clone https://github.com/YOUR_USERNAME/clusteraudiencekit.git
+cd clusteraudiencekit
+```
+
+### Set Up Development Environment
+
+ClusterAudienceKit is a Rust core (`src/`) with PyO3 Python bindings — you
+need a Rust toolchain (see `rust-toolchain.toml`, currently `stable`) as well
+as Python 3.8+.
+
+Install in editable mode, which builds the Rust extension via `maturin` and
+installs the Python package:
+
+```bash
+pip install -e ".[dev]"
+```
+
+**macOS linker note:** a bare `cargo build`/`cargo test` (not going through
+`maturin`) needs this linker flag, because the crate's PyO3 dependency uses
+the `extension-module` feature (which deliberately doesn't link against
+`libpython`, since normally a Python interpreter provides those symbols at
+import time):
+
+```bash
+export RUSTFLAGS="-C link-args=-undefined -C link-args=dynamic_lookup"
+cargo build --release
+```
+
+**`cargo test` on macOS:** pyo3's `extension-module` feature (on by default,
+so plain `cargo build`/`cargo bench`/`cargo clippy`/`maturin develop` all
+behave as before) deliberately omits linking against `libpython`, since a
+real Python interpreter provides those symbols via `dlopen` at import time.
+A standalone `cargo test` binary is never loaded by a Python process, so it
+SIGABRTs immediately (`dyld: symbol not found in flat namespace
+'_PyBaseObject_Type'`) if built with that feature on. Build tests **without**
+it instead:
+
+```bash
+cargo test --release --no-default-features --lib
+```
+
+This links the test binary normally against `libpython`, which requires a
+Python installation with an actual linkable `libpython*.dylib` (a Homebrew,
+pyenv `--enable-shared`, or python.org install; the Xcode Command Line
+Tools' bundled Python does **not** ship one). If `python3` on your `PATH`
+doesn't have one, point pyo3 at one that does:
+
+```bash
+export PYO3_PYTHON=/opt/homebrew/bin/python3.11   # or your equivalent
+cargo test --release --no-default-features --lib   # verified: 435 passed
+```
+
+If you don't have a suitable Python installed, validate Rust logic on macOS
+via the Python test suite instead, which builds the extension through
+`maturin` and exercises it from a real Python process — verified working:
+
+```bash
+maturin develop --release
+pytest tests/ -v          # 229 passed, last verified 2026-09-21
+```
+
+Rust-only checks that do work directly on macOS:
+
+```bash
+cargo fmt --all -- --check   # verified clean
+cargo clippy --workspace --all-targets   # NOT clean repo-wide — see
+                                          # docs/ROADMAP_HONEST.md for the
+                                          # current count and which modules
+cargo bench --bench benchmarks
+```
+
+## Development Workflow
+
+### 1. Create a Feature Branch
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+### 2. Make Your Changes
+
+- Follow [PEP 8](https://www.python.org/dev/peps/pep-0008/) for Python code
+- Use type hints on all public functions
+- Use Black for formatting and Ruff for linting
+
+```bash
+black .
+ruff check .
+mypy .
+```
+
+### 3. Write Tests
+
+- Add Rust unit tests (`#[cfg(test)]`) in the module you changed under
+  `src/engine/`, and a Python-level test in `tests/` exercising the same
+  change through the actual PyO3 binding (not a mock).
+- There's no coverage tooling wired up for the Rust side (no tarpaulin/
+  grcov/similar), and `pytest --cov` only measures
+  `clusteraudiencekit/__init__.py` (a 24-line re-export shim, already at
+  100%) — Python's `coverage.py` can't instrument the compiled Rust
+  extension, so a "% coverage" number for this project wouldn't mean much.
+  Judge test adequacy by whether the new/changed logic has a real test that
+  would fail if the logic were wrong, not by a coverage percentage.
+
+```bash
+pytest tests/
+```
+
+### 4. Update Documentation
+
+- Update docstrings for any changed public API
+- Update README.md if the user-facing API changes
+- Add examples in `examples/`
+
+### 5. Commit and Push
+
+```bash
+git add .
+git commit -m "feat: add streaming drift detection"
+git push origin feature/your-feature-name
+```
+
+Follow [conventional commits](https://www.conventionalcommits.org/):
+- `feat:` New feature
+- `fix:` Bug fix
+- `docs:` Documentation only
+- `test:` Test changes
+- `perf:` Performance improvement
+- `refactor:` Code refactoring
+- `chore:` Build or dependency changes
+
+### 6. Open a Pull Request
+
+Create a pull request with a clear description of:
+- What the change does
+- Why it's needed
+- How it was tested
+
+## Pull Request Guidelines
+
+- Keep PRs focused on a single feature or fix
+- Include tests for all new functionality
+- Ensure all tests pass before requesting review
+- This is currently maintained by one person (see `docs/CONTRIBUTORS.md`);
+  there's no guaranteed review turnaround time
+
+## Testing
+
+### Python Integration Tests
+
+The real constructor is `AudienceSegmenter(n_clusters, n_jobs=None)`, and it
+takes a numeric feature matrix (`list[list[float]]`), not a DataFrame; there
+is no `fit_predict()` — call `fit()` then `predict()` separately:
+
+```python
+import pytest
+from clusteraudiencekit import AudienceSegmenter
+
+def test_fit_predict_pipeline():
+    features = [[10.0, 2.0], [12.0, 1.0], [200.0, 40.0], [190.0, 38.0]]
+    segmenter = AudienceSegmenter(2)
+    segmenter.fit(features)
+    segments = segmenter.predict(features)
+    assert len(segments) == len(features)
+    assert min(segments) >= 0
+    assert max(segments) < 2
+```
+
+## Documentation
+
+- Update docstrings for all changed public APIs
+- Include usage examples in docstrings
+- Update README.md for user-facing changes
+- Add or update examples in `examples/`
+
+## Reporting Issues
+
+Use the [GitHub issue tracker](https://github.com/Mullassery/clusteraudiencekit/issues):
+
+1. Check existing issues first
+2. Include:
+   - Clear description of the issue
+   - Steps to reproduce
+   - Expected vs actual behaviour
+   - Environment (OS, Python version, ClusterAudienceKit version)
+
+## Suggesting Features
+
+- Open an issue with the "Feature Request" label
+- Describe the feature and the use case it addresses
+- Link to similar features in other libraries if applicable
+
+## License
+
+By contributing, you agree your contributions will be licensed under the
+project's Apache License 2.0 (see [`LICENSE`](LICENSE)).
+
+Thank you for contributing to ClusterAudienceKit!

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/Cargo.lock

@@ -461,7 +461,7 @@ checksum = "c8d4a3bb8b1e0c1050499d1815f5ab16d04f0959b233085fb31653fbfc9d98f9"
 
 [[package]]
 name = "clusteraudiencekit"
-version = "7.3.0"
+version = "7.3.1"
 dependencies = [
  "arrow",
  "bincode",

{clusteraudiencekit-7.3.0 → clusteraudiencekit-7.3.1}/Cargo.toml

@@ -1,8 +1,9 @@
 [package]
 name = "clusteraudiencekit"
-version = "7.3.0"
+version = "7.3.1"
 edition = "2021"
 authors = ["Georgi Mammen Mullassery <mullassery@gmail.com>"]
+license = "Apache-2.0"
 description = "High-performance audience segmentation engine with Python bindings"
 repository = "https://github.com/Mullassery/clusteraudiencekit"
 readme = "README.md"
@@ -12,7 +13,7 @@ categories = ["algorithms", "data-structures"]
 [dependencies]
 ndarray = "0.16"
 ndarray-stats = "0.5"
-pyo3 = { version = "0.22", features = ["extension-module"] }
+pyo3 = { version = "0.22" }
 numpy = "0.22"
 arrow = "55.0"
 parquet = "55.0"
@@ -28,6 +29,20 @@ log = "0.4"
 criterion = { version = "0.5", features = ["html_reports"] }
 proptest = "1.4"
 
+# `extension-module` is on by default so `cargo build`/`cargo bench`/`cargo
+# clippy`/`maturin develop` all behave exactly as before this feature-gating
+# was introduced. It deliberately omits linking against libpython (a real
+# Python interpreter provides those symbols via dlopen at import time), which
+# is fine for the real extension module but means a standalone `cargo test`
+# binary (never loaded by a Python process) SIGABRTs on macOS with "symbol
+# not found in flat namespace '_PyBaseObject_Type'" -- run
+# `cargo test --no-default-features` to build tests without it, which links
+# normally against libpython instead. See docs/ROADMAP_HONEST.md and
+# CONTRIBUTING.md.
+[features]
+default = ["extension-module"]
+extension-module = ["pyo3/extension-module"]
+
 [[bench]]
 name = "benchmarks"
 harness = false

clusteraudiencekit-7.3.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 2026 Georgi Mullassery
+
+   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.
+