cendor-sdk 1.0.0__tar.gz

cendor_sdk-1.0.0/.claude/skills/namespace-guard/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: namespace-guard
+description: Verify the cendor PEP 420 namespace packaging is correct — there must be no src/cendor/__init__.py. Use before committing, building, or releasing, or whenever cross-package imports break.
+---
+# Namespace guard
+
+`cendor-sdk` is one distribution contributing to the shared PEP 420 `cendor` namespace. It must own
+`src/cendor/sdk/` **only** and never ship `src/cendor/__init__.py` — the #1 way multi-repo namespace
+packages break.
+
+```bash
+# Must print NOTHING:
+find src -path '*/cendor/__init__.py' -print
+```
+
+- If it prints any path → **delete that file.** A top-level `cendor/__init__.py` turns the implicit
+  namespace into a regular package and silently breaks every other `cendor.<tool>` import.
+- `src/cendor/sdk/__init__.py` SHOULD exist — only the `src/cendor/__init__.py` *level* is forbidden.
+- The same check runs in CI (`.github/workflows/ci.yml`).
+
+If it passes, report "namespace-guard: OK".

cendor_sdk-1.0.0/.gitattributes

@@ -0,0 +1,4 @@
+# Normalize line endings: store LF in git; check out LF everywhere (ruff/CI stay consistent).
+* text=auto eol=lf
+*.png binary
+*.jpg binary

cendor_sdk-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,55 @@
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# Cancel superseded runs for the same ref (PR pushes); never cancel a main-branch build.
+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]   # development happens on Windows — test it too
+    runs-on: ${{ matrix.os }}
+    defaults:
+      run:
+        shell: bash   # Git Bash on the Windows runner, so `find`/heredocs work cross-platform
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          repository: cendorhq/Cendor
+          path: Cendor           # the dev source override in pyproject resolves ../Cendor/packages/*
+      - uses: actions/checkout@v5
+        with:
+          path: cendor-sdk
+      - uses: astral-sh/setup-uv@v3
+      - name: sync
+        working-directory: cendor-sdk
+        run: uv sync
+      - name: ruff lint
+        working-directory: cendor-sdk
+        run: uv run ruff check .
+      - name: ruff format check
+        working-directory: cendor-sdk
+        run: uv run ruff format --check .
+      - name: namespace guard (no top-level cendor/__init__.py)
+        working-directory: cendor-sdk
+        run: |
+          if find src -path '*/cendor/__init__.py' | grep . ; then
+            echo "ERROR: a top-level cendor/__init__.py exists — it breaks the PEP 420 namespace"; exit 1
+          fi
+          echo "namespace-guard: OK"
+      - name: type-check
+        working-directory: cendor-sdk
+        run: uv run mypy -p cendor.sdk
+      - name: tests
+        working-directory: cendor-sdk
+        run: uv run pytest -q
+      - name: import check
+        working-directory: cendor-sdk
+        run: uv run python -c "import cendor.sdk; print('import cendor.sdk OK', cendor.sdk.__version__)"

cendor_sdk-1.0.0/.github/workflows/release.yml

@@ -0,0 +1,50 @@
+name: release
+on:
+  push:
+    tags:
+      - 'v*.*.*'          # e.g. v1.0.0 — publishing is tag-triggered
+
+# PyPI **trusted publishing** (OIDC) — no stored API token. Configure a trusted publisher for the
+# `cendor-sdk` project on PyPI with:
+#   Owner: cendorhq · Repository: cendor-sdk · Workflow: release.yml · Environment: sdk
+# The GitHub OIDC identity of this workflow authenticates the upload; the (repo, workflow, env)
+# triple must match the publisher exactly.
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: sdk
+    permissions:
+      id-token: write      # OIDC trusted publishing
+      contents: write      # checkout (read) + create the GitHub Release (write)
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Assert tag version matches pyproject version
+        run: |
+          VERSION="${GITHUB_REF_NAME#v}"
+          PYPROJECT="$(grep -m1 -E '^version[[:space:]]*=' pyproject.toml | sed -E 's/.*"([^"]+)".*/\1/')"
+          echo "tag=$VERSION  pyproject=$PYPROJECT"
+          if [ "$VERSION" != "$PYPROJECT" ]; then
+            echo "::error::tag $GITHUB_REF_NAME says v$VERSION but pyproject.toml is $PYPROJECT — fix one and re-tag"
+            exit 1
+          fi
+      - name: Build sdist + wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build       # backend-only (hatchling); ignores the dev [tool.uv.sources] override
+      - uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Create GitHub Release (notes from CHANGELOG)
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          VERSION="${GITHUB_REF_NAME#v}"
+          awk -v hdr="## [$VERSION]" '
+            index($0, hdr)==1 {p=1; next}
+            p && index($0, "## [")==1 {exit}
+            p {print}
+          ' CHANGELOG.md > /tmp/notes.md
+          [ -s /tmp/notes.md ] || echo "cendor-sdk $VERSION" > /tmp/notes.md
+          gh release create "$GITHUB_REF_NAME" --title "cendor-sdk $VERSION" --notes-file /tmp/notes.md

cendor_sdk-1.0.0/.gitignore

@@ -0,0 +1,27 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+.uv/
+uv.lock
+.ruff_cache/
+.pytest_cache/
+.mypy_cache/
+.coverage
+coverage.json
+htmlcov/
+.smoke/
+.idea/
+.vscode/
+.DS_Store
+*.log
+
+# Local scratch / audit artifacts produced by examples & tests
+audit.jsonl
+*.audit.jsonl
+checkpoints/
+
+# Planning docs — kept local, not tracked
+plan/

cendor_sdk-1.0.0/CHANGELOG.md

@@ -0,0 +1,190 @@
+# Changelog
+
+All notable changes to `cendor-sdk` are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project adheres to
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] — 2026-07-05
+
+First public release on PyPI — the governed agent loop, multi-agent orchestration, ecosystem
+interop, and production hardening + governed eval, consolidated with the gap-analysis remediation,
+retrieval (RAG), and rolling memory. Requires `cendor-core>=1.3` (Hugging Face detection).
+
+### Fixed
+- **Tool calling on Gemini & Bedrock** (P0) — `build_kwargs` dropped assistant `tool_calls` and all
+  `tool` results, so multi-turn tool loops silently broke on those providers. Added
+  `_canonical_to_gemini` / `_canonical_to_bedrock` (functionCall/functionResponse; toolUse/toolResult),
+  mirroring the Anthropic translator, with round-trip tests.
+
+### Added — gap-analysis remediation (see `plan/SDK_FIT_GAP_ANALYSIS.md`)
+- **Provider param passthrough** — `Agent.extra` merges arbitrary request kwargs (`tool_choice`,
+  `reasoning_effort`, `top_p`, `stop`, `seed`, `response_format`, `extra_body`, …) into every call.
+- **o-series temperature guard** — the OpenAI provider omits `temperature` for `o1`/`o3`/`o4` models
+  (which reject it) instead of erroring.
+- **Robust structured output** — an `output_type` now derives a JSON Schema used via each provider's
+  native structured-output feature: OpenAI `json_schema`, Ollama `format`, Gemini `response_schema`;
+  Anthropic/Bedrock/Responses embed the schema in the JSON nudge. Dataclass / Pydantic / dict.
+- **Streaming** — `run.stream(agent, input)` / `run.astream(...)` yield `TextDelta` / `ToolCallEvent`
+  / `ToolResultEvent` and a terminal `RunComplete(result)`. Native reassembly for the OpenAI family +
+  Ollama (tool-call deltas included); whole-response fallback for the rest. Single-agent.
+- **Multimodal input** — message `content` may be a parts list (`text` + `image_url`); OpenAI-family
+  passes it through, Anthropic/Gemini translate to image blocks (base64/url), Bedrock keeps the text.
+- **Unpriced-model cost governance** — `register_model_price(model, input=…, output=…)` registers a
+  rate so cost/USD budgets bind on HF/Azure-deployment/Foundry-Local/custom ids; `configure`
+  (`on_unpriced="raise"`) re-exported.
+- **Embeddings** — `embed(model, inputs)` / `aembed(...)` return vectors and emit a governed
+  `LLMCall` (tokens/cost/audit captured) for OpenAI-family providers — RAG calls become first-class.
+- **RAG seam** — `VectorIndex` (a dependency-free in-memory cosine index over `embed()`) +
+  `Agent(retriever=…)`, which injects retrieved context as a system message before the call
+  ("always-on" RAG). Bring your own embedder via `embedder=`, or plug a real vector DB as a
+  retriever. The SDK governs retrieval; it does not store your vectors.
+- **Summarizing memory** — `SummarizingSession(model=… | summarizer=…, max_messages=…,
+  keep_recent=…)` folds old turns into a durable summary note when a conversation grows, keeping
+  recent turns verbatim so memory stays bounded but the gist persists (beyond `context_budget`
+  trimming). `llm_summarizer(model)` builds a governed summarizer; pass any callable for offline
+  summaries.
+- **Multi-agent checkpointing** — `run([...], checkpoint=…)` persists the trajectory per turn/segment
+  and resumes a crashed team run.
+- **MCP prompts** — `load_mcp_prompts(session)` + `get_mcp_prompt(session, name, args)` (renders to
+  canonical messages); `load_mcp_resources` now exported too.
+- **Concurrent tool execution** — a turn's multiple tool calls run via `asyncio.gather` in async runs.
+- **`max_turns` signal** — `Result.incomplete` is `True` when a run ends with no final answer.
+- **Nested tool params** — tool schema generation expands nested dataclass / Pydantic parameters.
+- **Richer OTel spans** — `span_tree` now records latency, finish reason, reasoning tokens, and tool
+  argument names.
+- **Eval judge** — `EvalCase.judge` adds a pluggable semantic / LLM-judge scorer.
+
+### Added
+- **Hugging Face provider** (`provider="huggingface"` / `"hf"`, extra `[huggingface]`) — wraps
+  `huggingface_hub.InferenceClient.chat_completion` (OpenAI-shaped response, so request formatting
+  and normalization are reused). Token via `api_key=` or `HF_TOKEN`/`HUGGINGFACEHUB_API_TOKEN`;
+  `base_url=` targets a dedicated Inference Endpoint; `HF_PROVIDER` routes through a specific
+  inference provider. `cendor-core`'s `instrument` now detects `chat_completion` structurally and
+  attributes the `LLMCall` to `huggingface`, so budgets/guard/audit apply.
+- **Azure AI Foundry provider** (`provider="azure"` / `"azure_openai"` / `"foundry"`, extra
+  `[azure]`) — connects to Foundry deployments via the **standard `openai` SDK** on the
+  `/openai/v1/` endpoint, per Microsoft's current guidance (the `AzureOpenAI` client and
+  `azure-ai-inference` are being retired). `model` is the Foundry **deployment name**; `base_url`
+  (or `AZURE_OPENAI_ENDPOINT`) is normalized to the v1 route; `api_key` falls back to
+  `AZURE_OPENAI_API_KEY`/`AZURE_INFERENCE_CREDENTIAL`. Entra ID via a bearer-token `api_key` or a
+  bring-your-own `client=`. See `docs/sdk.md` → *Connecting to Hugging Face & Azure AI Foundry*.
+- **Azure Foundry Responses API** (`provider="azure_responses"` / `"foundry_responses"`) — drives
+  the OpenAI Responses API over a Foundry endpoint for OpenAI-family deployments; same Foundry-aware
+  construction as `provider="azure"` (Chat Completions).
+- **Foundry Local provider** (`provider="foundry_local"` / `"foundry-local"`, extra
+  `[foundry-local]`) — Microsoft's on-device runtime over its local OpenAI-compatible REST server
+  (the local counterpart to Ollama). Endpoint via `base_url=` or `FOUNDRY_LOCAL_ENDPOINT` (e.g.
+  `foundry_local.FoundryLocalManager(alias).endpoint`); no key required. `model` is the resolved
+  Foundry Local model id.
+- **Examples**: `examples/foundry_agent.py` (Azure Foundry + Foundry Local) and
+  `examples/huggingface_agent.py`, both offline.
+
+### Consolidation & docs (Phases 1–4)
+
+Consolidates Phases 1–4 into a stable, documented release (plan §12): the governed agent loop,
+multi-agent orchestration, ecosystem interop, and production hardening + governed eval — complete,
+provider-agnostic, local-first, and tested offline.
+
+- Full docs pass: `docs/index.md` links every page and lists the public API surface; the two-door
+  framing (libraries primary, SDK secondary) is consistent across the README and docs.
+- Marked `Development Status :: 5 - Production/Stable`.
+- Verification: `uv run pytest` green (91 tests, no network), `ruff check`/`ruff format` clean,
+  mypy clean, namespace-guard clean, `import cendor.sdk` works.
+
+## [0.4.0] — Phase 4: Production hardening & governed eval
+
+The "safe for real workloads" layer plus the testing wedge fully realized.
+
+### Added
+- **Retries & backoff** — `RetryPolicy` retries transient model-call failures (timeouts,
+  connection errors, rate limits, 5xx) with exponential backoff; governance decisions
+  (`BudgetExceeded`/`PolicyViolation`) are never retried. `run(..., retry=RetryPolicy(...))`.
+- **Checkpointed / resumable runs** — `run(..., checkpoint="run.ckpt.json")` persists the
+  conversation after each turn; re-running with the same checkpoint resumes without re-executing
+  completed tools. Backed by `Checkpointer` (atomic local JSON).
+- **Durable memory** — `SQLiteSessionStore` persists many named conversations locally (no server);
+  `Session.save`/`Session.load` for JSON.
+- **Governed eval / regression harness** — `evaluate(agent, [EvalCase(...)])` replays recorded
+  cassettes as tests and asserts output, tool sequence, and cost/token ceilings; cost/tokens are
+  real on replay. `EvalReport.assert_ok()` fails CI on a behaviour *or* spend regression.
+- **Docs/examples**: `docs/hardening.md`, `docs/eval.md`; `examples/eval_suite.py`.
+- **Tests** (+9): transient failure recovers, retry gives up / doesn't retry non-transient, a
+  checkpointed run resumes after a simulated crash, SQLite durable memory round-trips, and an eval
+  suite catches a cost regression + a tool-sequence change.
+
+## [0.3.0] — Phase 3: Ecosystem & interop
+
+Governed `cendor-sdk` agents become first-class citizens elsewhere — all optional and local-first.
+
+### Added
+- **MCP client** (`[mcp]` extra) — `load_mcp_tools(session)` turns an MCP server's tools into
+  governed `Tool`s (duck-typed against `mcp.ClientSession`; async, use with `run.aio`).
+  `load_mcp_resources(session)` reads resources.
+- **A2A** — `A2AServer` serves an agent over the Agent-to-Agent protocol (JSON-RPC `message/send` +
+  agent card); `A2AClient` calls it **in-process**; `a2a.serve(...)` is an optional stdlib HTTP
+  server. Replies carry governance metadata (trace id, cost).
+- **Foundry / Copilot** — `FoundryAdapter` publishes an agent as a Microsoft 365 / Foundry
+  custom-engine agent over the Bot Framework Activity protocol (`on_activity`, `manifest`).
+- **OpenTelemetry span tree** (`[otel]` extra) — `span_tree(result)` emits a `gen_ai.*` span tree
+  (root `agent.run` → per-agent → per model call / tool) mirroring the correlated `Result`; a
+  no-op when OTel isn't installed.
+- **Human-in-the-loop** — `require_approval(tool, approver=…)` gates a tool behind approval and
+  records the verdict via `decision.human_oversight(...)` on the run's audit chain; rejection blocks
+  the tool. The runner now exposes the active audit `decision` via a contextvar for this wiring.
+- **Docs/examples**: `docs/interop.md`; `examples/mcp_agent.py`.
+- **Tests** (+7): MCP round-trip (mocked session), A2A serve+call (in-proc), Foundry adapter, OTel
+  span-tree assertions (in-memory exporter), HITL approval + rejection recorded in a verified chain.
+
+## [0.2.0] — Phase 2: Multi-agent orchestration
+
+Orchestration patterns land, with the correlation that was impossible beneath frameworks: a whole
+multi-agent trajectory is one governed, correlated tree on one verifiable audit chain.
+
+### Added
+- **Handoff** — an agent transfers control to a named peer via a synthetic `transfer_to_<peer>`
+  tool; the canonical conversation carries across the switch, so **handoff works across providers**.
+- **Supervisor / router** — `supervisor(coordinator, [sub_agents], ...)`; a coordinator routes to
+  sub-agents by handoff. `run([entry, *peers], input)` is the handoff-team shortcut.
+- **Sequential & parallel** — `sequential([...])` pipes each agent's output into the next;
+  `parallel([...])` / `parallel_async([...])` fan out over the same input (`{agent: output}`).
+- **Nested trace correlation** — one parent `run_id`; each agent segment runs under a child trace
+  id (`{run_id}:{agent}#i`), so every `Step` carries its agent name and a `trace_id` that starts
+  with the parent — one correlated tree.
+- **Per-agent governance** — each segment is wrapped in `track(agent=…)` (spend attribution) and,
+  when the agent sets `max_usd`, a per-agent `budget(...)`; each segment opens its own audit
+  `decision()` on a shared `AuditLog` — one verifiable chain, distinct agents distinguishable.
+- **Session persistence** — `Session.save(path)` / `Session.load(path)` (local JSON), resumable.
+- **Refactor** — the per-agent loop is extracted (`run_agent_sync`/`run_agent_async`) so the
+  single-agent `Runner` and the orchestrator share exactly one loop.
+- **Docs/examples**: `docs/multi-agent.md`; `examples/handoff.py`, `examples/supervisor.py`.
+- **Tests**: supervisor + 2 sub-agents with a correlated audit trail; per-agent budgets enforced;
+  handoff across OpenAI↔Anthropic; sequential/parallel pipelines; session persistence.
+
+## [0.1.0] — Phase 1: Governed single agent
+
+The wedge lands: a governed single agent runs on OpenAI **and** Anthropic, with budgets, audit,
+redaction, and deterministic replay — provider-agnostic, local-first, no network in tests.
+
+### Added
+- **`Agent`** — a small, opinionated agent bound to any core-supported provider id, with tools,
+  instructions, structured output, and a bounded ReAct loop.
+- **`tool` / `Tool`** — decorator that generates a JSON Schema from a function's type hints +
+  docstring, and formats it per provider (OpenAI functions, Anthropic tools, Gemini function
+  declarations, Bedrock toolConfig). Sync **and** async tools; every call emits a `ToolCall`.
+- **`run` / `Runner`** — the single-agent loop, **sync (`run`) and async (`run.aio`)**: assemble →
+  format → call (inside `trace(run_id)`) → normalize → tools → repeat → finalize.
+- **Provider response normalization** (`providers.py`) — extract assistant content + tool calls +
+  finish reason for OpenAI (Chat Completions + Responses), Anthropic, Gemini, Bedrock, and Ollama.
+- **Structured output** — `output_type` as a dataclass or JSON-schema dict, parsed from the final
+  message.
+- **In-memory `Session`** — conversation memory across `run()` calls.
+- **`Result` / `Run` / `Step`** — the data model; steps are the actual bus `LLMCall`/`ToolCall`
+  records, correlated by one `trace_id`, with aggregate `usage` and Decimal `cost`.
+- **Governance re-exports** — `budget`, `track`, `report` (tokenguard); `AuditLog`, `Policy`,
+  `guard` (acttrace, with `guard` wrapped as a context manager); all composing through core's seams
+  with zero SDK glue. An ungoverned `run()` still works on `cendor-core` alone.
+- **Docs**: `README.md` (two doors + killer metric), `docs/index.md`, `docs/sdk.md`;
+  `examples/single_agent.py`.
+- **Tests**: governed single-agent runs across OpenAI and Anthropic (respx-mocked, no network);
+  usage/cost/reasoning captured, budget blocks, guard redacts, audit chain `verify()`s, `trace_id`
+  correlates, and cassette replay is deterministic.

cendor_sdk-1.0.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 2026 Raghav Mishra (PowerAI Labs)
+
+   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.