cluebase-backend-sdk 0.0.1__tar.gz

cluebase_backend_sdk-0.0.1/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: cluebase-backend-sdk
+Version: 0.0.1
+Summary: Cluebase Backend SDK (Python) — OTel-based observation-source event capture for Django, FastAPI, Celery, SQLAlchemy, LangChain, LlamaIndex, CrewAI, MCP, and AI providers.
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: opentelemetry-api<2.0,>=1.41.1
+Requires-Dist: opentelemetry-sdk<2.0,>=1.41.1
+Requires-Dist: rfc8785<0.2,>=0.1.4
+Provides-Extra: mutation
+Requires-Dist: mutmut<4.0,>=3.2; extra == "mutation"
+Provides-Extra: instrumentation-requests
+Requires-Dist: opentelemetry-instrumentation-requests<1.0,>=0.63b1; extra == "instrumentation-requests"
+Provides-Extra: instrumentation-httpx
+Requires-Dist: opentelemetry-instrumentation-httpx<1.0,>=0.63b1; extra == "instrumentation-httpx"
+Provides-Extra: instrumentation-fastapi
+Requires-Dist: fastapi<1.0,>=0.100; extra == "instrumentation-fastapi"
+Requires-Dist: opentelemetry-instrumentation-fastapi<1.0,>=0.63b1; extra == "instrumentation-fastapi"
+Provides-Extra: instrumentation-asgi
+Requires-Dist: opentelemetry-instrumentation-asgi<1.0,>=0.63b1; extra == "instrumentation-asgi"
+Provides-Extra: instrumentation-sqlalchemy
+Requires-Dist: opentelemetry-instrumentation-sqlalchemy<1.0,>=0.63b1; extra == "instrumentation-sqlalchemy"
+Provides-Extra: instrumentation-django
+Requires-Dist: opentelemetry-instrumentation-django<1.0,>=0.63b1; extra == "instrumentation-django"
+Provides-Extra: instrumentation-celery
+Requires-Dist: opentelemetry-instrumentation-celery<1.0,>=0.63b1; extra == "instrumentation-celery"
+Provides-Extra: test
+Requires-Dist: pytest<9.0,>=8.0; extra == "test"
+Requires-Dist: pytest-cov<7.0,>=5.0; extra == "test"
+Requires-Dist: pyright<1.2,>=1.1.411; extra == "test"
+Requires-Dist: build<2.0,>=1.2; extra == "test"
+Requires-Dist: packaging<26,>=25; extra == "test"
+Requires-Dist: twine<7.0,>=6.1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-requests<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-httpx<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-fastapi<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-asgi<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-sqlalchemy<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-django<1.0,>=0.63b1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-celery<1.0,>=0.63b1; extra == "test"
+Requires-Dist: requests>=2.31; extra == "test"
+Requires-Dist: httpx>=0.26; extra == "test"
+Requires-Dist: sqlalchemy>=2.0; extra == "test"
+Requires-Dist: django<6.0,>=5.0; extra == "test"
+Requires-Dist: fastapi<1.0,>=0.100; extra == "test"
+Requires-Dist: celery<6.0,>=5.0; extra == "test"
+Requires-Dist: langchain-core<1.0,>=0.3; extra == "test"
+Requires-Dist: llama-index-core<1.0,>=0.12; extra == "test"
+Requires-Dist: crewai<1.16,>=1.15.1; extra == "test"
+Requires-Dist: openai==2.45.0; extra == "test"
+Requires-Dist: anthropic==0.116.0; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-openai==0.62.1; extra == "test"
+Requires-Dist: opentelemetry-instrumentation-anthropic==0.62.1; extra == "test"
+Requires-Dist: aiosqlite==0.21.0; extra == "test"
+Requires-Dist: setuptools<83,>=68; extra == "test"
+Dynamic: requires-python
+
+# cluebase-backend-sdk
+
+Shared Python backend core for Cluebase SDK wrappers (Django, FastAPI,
+Celery). Events flow through an OTel `TracerProvider` + `ConsentSpanProcessor` +
+`ObservationSourceEventExporter` and the shared delivery queue to
+`/api/v1/ingest/backend`.
+
+## Minimal integration
+
+The SDK exposes a single ``cluebase`` namespace with eight methods (``init`` /
+``identify`` / ``group`` / ``reset`` / ``track`` / ``set_consent`` /
+``flush`` / ``close``). This mirrors the cross-SDK contract documented in
+``docs/contracts/sdk/public-api.md`` §1.6.
+
+```python
+import asyncio
+from cluebase_backend_sdk import cluebase
+
+cluebase.init({
+    "endpoint": "https://api.example.com",
+    "project_key": "...",
+    "api_key": "...",
+    "service_key": "backend-api",
+})
+
+cluebase.identify("user_42", {"name": "Alice", "email": "alice@example.com"})
+cluebase.group("organization", "org_7", {"name": "Acme Inc"})
+cluebase.track("order_placed", {"product_name": "shirt", "amount": 100})
+cluebase.set_consent("granted")
+
+# Shutdown idiom — both are coroutines for cross-SDK parity.
+asyncio.run(cluebase.flush())
+asyncio.run(cluebase.close())
+```
+
+Do not pass ``environment`` or ``service_name`` in the MVP setup path.
+Cluebase derives dev/prod from the project key prefix, and ``service_key`` is the
+single literal customer-facing backend service label.
+
+``cluebase.track`` custom event names must match
+``^[A-Za-z0-9_.:-]{1,128}$``. Invalid names are ignored and do not emit
+a source-signal custom track intent. ``cluebase.set_consent`` only records local
+SDK state in the MVP backend SDK; it does not emit consent transition events.
+
+Framework wrappers and runtime helpers are imported from their owning modules.
+The package root is intentionally small: customer-facing lifecycle methods plus
+stable setup helpers. Direct event builders are not public extension
+points.
+
+## Architecture boundary
+
+The Python SDK is a thin language wrapper around OpenTelemetry and the Cluebase
+transport. Framework integrations create spans or annotate the current span,
+the exporter serializes those spans as ``sdk_source_signal_observed`` events,
+and the Cluebase backend ingest core performs classification, normalization,
+privacy projection, and raw-ingest shaping.
+
+```text
+Python framework / library hook
+  -> OTel span or Cluebase source-signal attributes
+  -> ObservationSourceEventExporter
+  -> /api/v1/ingest/backend
+  -> apps/api/src/modules/ingest core
+```
+
+Rules:
+
+- Keep framework code limited to raw facts, correlation context, and standard
+  OTel attributes.
+- Do not add Python-only classification, direct event builders, or custom
+  fallback behavior.
+- Add classifier behavior in the backend ingest core so Node.js, Python, and
+  future SDK wrappers receive the same behavior.
+- Preserve ``interaction_id``, ``request_span_id``, ``request_id``, and
+  ``trace_id`` whenever they are available. User-action linkage is an ingest
+  contract, not a display-only field.
+
+## Privacy and PII handling
+
+### 1. Hard-deny: PII / secrets are stripped before transport
+
+The SDK strips a built-in set of property keys **before** the event
+leaves the customer process. Caller-supplied `denied_keys` are added
+on top of `DEFAULT_DENIED_KEYS` — they cannot remove a default-denied
+key.
+
+Hard-deny categories (case- and separator-insensitive — `userEmail`,
+`user-email`, `USER_EMAIL`, `email_address` all match):
+
+- Auth credentials: `authorization`, `cookie`, `set-cookie`,
+  `password`, `passwd`, `secret`, `token`, `access_token`,
+  `refresh_token`, `session`, `session_token`, `api_key`, `apikey`,
+  `private_key`
+- PII categories: `email`, `phone`, `credit_card`, `ssn`
+
+This list is a strict superset of the server-side ingest hard-deny
+(`@cluebase/shared` `INGEST_HARD_DENY_KEYS`), enforced by the
+`tests/test_privacy_parity.py` cross-SDK parity test.
+
+### 2. HTTP request values
+
+This SDK does not read HTTP request or response bodies. The value surface it can
+observe is the request query, and its values are masked by default. A value is
+sent in plaintext only when the customer names that field on the Cluebase screen; the
+decision is delivered to the SDK and re-checked by ingest. Hard-denied keys such
+as `email` can never be released, whatever the screen says. See
+`docs/arch/sdk/backend-sdk.md` for the boundary and for what would be required to
+bring bodies into scope.
+
+### 3. Analysis projection and later registration
+
+Properties that pass the hard-deny gate are projected by default unless a
+cardinality, free-text, or complex-value guard keeps them out of the analysis
+index. Guarded non-private values remain available in
+`analysisProperties.raw_only` so they can be registered and promoted later.
+The map stores each original value as JSON so its type can be restored.
+Hard-denied values are dropped and never stored in `raw_only`. After a privacy
+review, use the project service allowlist to promote a guarded non-private
+property into the analysis projection.
+
+### 4. Identity traits stay privacy-safe
+
+`cluebase.identify(user_id, traits={...})` accepts profile traits such as
+`name`, `email`, and `avatarUrl`. Other customer-defined values remain generic
+subject traits instead of becoming fixed Cluebase profile fields. Use a stable opaque
+`user_id`; the SDK converts `email` into privacy-safe contact-derived
+fields before canonical identity events leave the process.
+
+## Build / test
+
+```sh
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e '.[test]'
+python -m pytest
+```

cluebase_backend_sdk-0.0.1/README.md

@@ -0,0 +1,136 @@
+# cluebase-backend-sdk
+
+Shared Python backend core for Cluebase SDK wrappers (Django, FastAPI,
+Celery). Events flow through an OTel `TracerProvider` + `ConsentSpanProcessor` +
+`ObservationSourceEventExporter` and the shared delivery queue to
+`/api/v1/ingest/backend`.
+
+## Minimal integration
+
+The SDK exposes a single ``cluebase`` namespace with eight methods (``init`` /
+``identify`` / ``group`` / ``reset`` / ``track`` / ``set_consent`` /
+``flush`` / ``close``). This mirrors the cross-SDK contract documented in
+``docs/contracts/sdk/public-api.md`` §1.6.
+
+```python
+import asyncio
+from cluebase_backend_sdk import cluebase
+
+cluebase.init({
+    "endpoint": "https://api.example.com",
+    "project_key": "...",
+    "api_key": "...",
+    "service_key": "backend-api",
+})
+
+cluebase.identify("user_42", {"name": "Alice", "email": "alice@example.com"})
+cluebase.group("organization", "org_7", {"name": "Acme Inc"})
+cluebase.track("order_placed", {"product_name": "shirt", "amount": 100})
+cluebase.set_consent("granted")
+
+# Shutdown idiom — both are coroutines for cross-SDK parity.
+asyncio.run(cluebase.flush())
+asyncio.run(cluebase.close())
+```
+
+Do not pass ``environment`` or ``service_name`` in the MVP setup path.
+Cluebase derives dev/prod from the project key prefix, and ``service_key`` is the
+single literal customer-facing backend service label.
+
+``cluebase.track`` custom event names must match
+``^[A-Za-z0-9_.:-]{1,128}$``. Invalid names are ignored and do not emit
+a source-signal custom track intent. ``cluebase.set_consent`` only records local
+SDK state in the MVP backend SDK; it does not emit consent transition events.
+
+Framework wrappers and runtime helpers are imported from their owning modules.
+The package root is intentionally small: customer-facing lifecycle methods plus
+stable setup helpers. Direct event builders are not public extension
+points.
+
+## Architecture boundary
+
+The Python SDK is a thin language wrapper around OpenTelemetry and the Cluebase
+transport. Framework integrations create spans or annotate the current span,
+the exporter serializes those spans as ``sdk_source_signal_observed`` events,
+and the Cluebase backend ingest core performs classification, normalization,
+privacy projection, and raw-ingest shaping.
+
+```text
+Python framework / library hook
+  -> OTel span or Cluebase source-signal attributes
+  -> ObservationSourceEventExporter
+  -> /api/v1/ingest/backend
+  -> apps/api/src/modules/ingest core
+```
+
+Rules:
+
+- Keep framework code limited to raw facts, correlation context, and standard
+  OTel attributes.
+- Do not add Python-only classification, direct event builders, or custom
+  fallback behavior.
+- Add classifier behavior in the backend ingest core so Node.js, Python, and
+  future SDK wrappers receive the same behavior.
+- Preserve ``interaction_id``, ``request_span_id``, ``request_id``, and
+  ``trace_id`` whenever they are available. User-action linkage is an ingest
+  contract, not a display-only field.
+
+## Privacy and PII handling
+
+### 1. Hard-deny: PII / secrets are stripped before transport
+
+The SDK strips a built-in set of property keys **before** the event
+leaves the customer process. Caller-supplied `denied_keys` are added
+on top of `DEFAULT_DENIED_KEYS` — they cannot remove a default-denied
+key.
+
+Hard-deny categories (case- and separator-insensitive — `userEmail`,
+`user-email`, `USER_EMAIL`, `email_address` all match):
+
+- Auth credentials: `authorization`, `cookie`, `set-cookie`,
+  `password`, `passwd`, `secret`, `token`, `access_token`,
+  `refresh_token`, `session`, `session_token`, `api_key`, `apikey`,
+  `private_key`
+- PII categories: `email`, `phone`, `credit_card`, `ssn`
+
+This list is a strict superset of the server-side ingest hard-deny
+(`@cluebase/shared` `INGEST_HARD_DENY_KEYS`), enforced by the
+`tests/test_privacy_parity.py` cross-SDK parity test.
+
+### 2. HTTP request values
+
+This SDK does not read HTTP request or response bodies. The value surface it can
+observe is the request query, and its values are masked by default. A value is
+sent in plaintext only when the customer names that field on the Cluebase screen; the
+decision is delivered to the SDK and re-checked by ingest. Hard-denied keys such
+as `email` can never be released, whatever the screen says. See
+`docs/arch/sdk/backend-sdk.md` for the boundary and for what would be required to
+bring bodies into scope.
+
+### 3. Analysis projection and later registration
+
+Properties that pass the hard-deny gate are projected by default unless a
+cardinality, free-text, or complex-value guard keeps them out of the analysis
+index. Guarded non-private values remain available in
+`analysisProperties.raw_only` so they can be registered and promoted later.
+The map stores each original value as JSON so its type can be restored.
+Hard-denied values are dropped and never stored in `raw_only`. After a privacy
+review, use the project service allowlist to promote a guarded non-private
+property into the analysis projection.
+
+### 4. Identity traits stay privacy-safe
+
+`cluebase.identify(user_id, traits={...})` accepts profile traits such as
+`name`, `email`, and `avatarUrl`. Other customer-defined values remain generic
+subject traits instead of becoming fixed Cluebase profile fields. Use a stable opaque
+`user_id`; the SDK converts `email` into privacy-safe contact-derived
+fields before canonical identity events leave the process.
+
+## Build / test
+
+```sh
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e '.[test]'
+python -m pytest
+```

cluebase_backend_sdk-0.0.1/pyproject.toml

@@ -0,0 +1,180 @@
+[project]
+name = "cluebase-backend-sdk"
+dynamic = ["version"]
+description = "Cluebase Backend SDK (Python) — OTel-based observation-source event capture for Django, FastAPI, Celery, SQLAlchemy, LangChain, LlamaIndex, CrewAI, MCP, and AI providers."
+readme = "README.md"
+requires-python = ">=3.10"
+# OTel SDK is required because the backend SDK emits through TracerProvider,
+# BatchSpanProcessor, and ObservationSourceEventExporter.
+dependencies = [
+	"opentelemetry-api>=1.41.1,<2.0",
+	"opentelemetry-sdk>=1.41.1,<2.0",
+	"rfc8785>=0.1.4,<0.2",
+]
+
+[project.optional-dependencies]
+# 断定の強さを測る道具（`[tool.mutmut]` が設定を持つ）。**`test` とは分けます。**
+# 変異試験だけを入れて走らせられる形にしないと、設定だけが在って 1 度も動かない
+# 状態になります（実測 2026-08-22: 設定は書かれているのに実行体が入っておらず、
+# CI からも呼ばれていませんでした）。
+mutation = ["mutmut>=3.2,<4.0"]
+# Auto-instrumentation packages are loaded lazily by each
+# ``instrument_*`` helper. Downstream consumers opt into the ones they need
+# via these extras; the helpers degrade to a no-op when the corresponding
+# instrumentation is not installed.
+instrumentation-requests = ["opentelemetry-instrumentation-requests>=0.63b1,<1.0"]
+instrumentation-httpx = ["opentelemetry-instrumentation-httpx>=0.63b1,<1.0"]
+instrumentation-fastapi = [
+	"fastapi>=0.100,<1.0",
+	"opentelemetry-instrumentation-fastapi>=0.63b1,<1.0",
+]
+instrumentation-asgi = ["opentelemetry-instrumentation-asgi>=0.63b1,<1.0"]
+instrumentation-sqlalchemy = ["opentelemetry-instrumentation-sqlalchemy>=0.63b1,<1.0"]
+instrumentation-django = ["opentelemetry-instrumentation-django>=0.63b1,<1.0"]
+instrumentation-celery = ["opentelemetry-instrumentation-celery>=0.63b1,<1.0"]
+test = [
+	"pytest>=8.0,<9.0",
+	"pytest-cov>=5.0,<7.0",
+	"pyright>=1.1.411,<1.2",
+	"build>=1.2,<2.0",
+	"packaging>=25,<26",
+	"twine>=6.1,<7.0",
+	"opentelemetry-instrumentation-requests>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-httpx>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-fastapi>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-asgi>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-sqlalchemy>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-django>=0.63b1,<1.0",
+	"opentelemetry-instrumentation-celery>=0.63b1,<1.0",
+	# The `instrument_*` helpers verify peer libraries before activating
+	# upstream instrumentors. These runtime peers are not transitive deps of
+	# the OTel instrumentors, so tests install them explicitly.
+	"requests>=2.31",
+	"httpx>=0.26",
+	"sqlalchemy>=2.0",
+	"django>=5.0,<6.0",
+	"fastapi>=0.100,<1.0",
+	"celery>=5.0,<6.0",
+	"langchain-core>=0.3,<1.0",
+	"llama-index-core>=0.12,<1.0",
+	"crewai>=1.15.1,<1.16",
+	"openai==2.45.0",
+	"anthropic==0.116.0",
+	"opentelemetry-instrumentation-openai==0.62.1",
+	"opentelemetry-instrumentation-anthropic==0.62.1",
+	"aiosqlite==0.21.0",
+	"setuptools>=68,<83",
+]
+
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+
+[tool.setuptools.dynamic]
+version = {attr = "cluebase_backend_sdk._version.__version__"}
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = [
+    "../../../tests/unit/backend-sdk-python",
+    "../../../tests/integration/backend-sdk-python",
+    "../../../tests/contract/backend-sdk-python",
+]
+# 実環境が要る試験を既定の実行から外します (`tests/README.md` §12.2)。
+# `testpaths` 配下の file には `--ignore-glob` が効かないため、live file は
+# 既定実行から明示的に外します。実環境のあるジョブは path を名指しして実行します。
+addopts = [
+	"--ignore=../../../tests/integration/backend-sdk-python/test_canonical_endpoint_live.py",
+	"--ignore=../../../tests/integration/backend-sdk-python/test_provider_content_privacy_live.py",
+]
+# The second entry lets cross-language conformance tests import the contract's
+# official fixture loader (python_loader / python_equality) in dev. This is the
+# dev-test path only; the published wheel never ships tests, so it does not
+# duplicate the copy-on-build of _conformance/ used by installed SDKs.
+pythonpath = [
+    ".",
+    "src",
+	"../../../tests/support/backend-sdk-python",
+	"../../../tests/unit/backend-sdk-python",
+	"../../../tests/integration/backend-sdk-python",
+	"../../../tests/contract/backend-sdk-python",
+]
+
+# tests/README.md §5 の判定器。変異させる記号は網羅の情報から自動で選ばれるので、
+# 手で宣言しません。
+[tool.mutmut]
+# mutmut はここに挙げた木を `mutants/` へ複製してから試験を回すので、範囲を
+# 1 file に絞ると import 先が複製されず collect が落ちます。木は package 全体を
+# 渡し、実際に壊す範囲は `mutmut run <glob>` の側で絞ります。
+source_paths = ["src/cluebase_backend_sdk/"]
+# 試験が package 直下から取り込む先。複製されないと collect が落ちます
+# （tests/ と pyproject.toml と uv.lock は mutmut が既定で複製します）。
+also_copy = ["scripts/", "setup.py"]
+# 下の 2 本を **変異の走行からだけ** 外します。素の束（`pytest`）では今までどおり
+# 走ります。理由は 2 本とも同じで、**mutmut が変異を source file 自体へ書き込む**
+# ためです（文字列は `XX...XX` の形、関数は `x_名前__mutmut_1` を同じ module へ
+# 足す）。原文の字面と名前の面が常に変わっているので、この 2 本は **どの変異でも
+# 必ず落ちます**。必ず落ちる試験があると全変異が「殺した」と記録され、**生き残りが
+# 隠れます**（tests/README.md §5.5 の裏返しで、測定が実際より良く見える向き）。
+#
+# 2 本が見ているのは実行時の振る舞いではなく構造なので、tests/README.md 上の担当は
+# §5（断定の強さ）ではなく §4（構造の不変条件）です。§5 から外すのが正しい配置で、
+# 緩めではありません。
+#
+# 複製先で実際に落ちることを 1 本ずつ確かめた上で外しています。**同じ探し方で
+# 引っかかった `tests/test_prepublish_gate.py` は、複製先でも 13 passed で通る
+# ので外していません**（読んでいるのが原文の中身ではなく file の一覧で、mutmut は
+# file を足さないため）。
+pytest_add_cli_args_test_selection = [
+    "tests/",
+    # 原文を読む: 全 .py を ast で読み、診断の記録が読める形で出るか確かめる
+    "--ignore=tests/test_internal_log_messages.py",
+    # 名前の面を数える: 輸出された名前が契約の宣言と一致するか確かめる
+    "--ignore=tests/test_mcp_observer_surface.py",
+]
+
+[tool.pyright]
+# Tests resolve the package via a runtime ``sys.path.insert`` to the
+# ``src/`` layout described by ``[tool.setuptools].package-dir``. Pyright
+# does not execute that snippet, so we mirror the search path here so
+# imports like ``from cluebase_backend_sdk.provider.bootstrap import ...``
+# resolve in editors without requiring an editable install.
+include = ["src", "tests"]
+extraPaths = [".", "src"]
+
+# Production code in ``src/`` is held to strict type-correctness, but
+# tests freely use ``JsonValue`` union subscripts and assertX helpers
+# that Pyright cannot narrow without per-call casts. Tests are gated
+# by ``pytest`` at runtime, so demote Pyright's general type issues
+# under ``tests/`` to warnings instead of errors.
+[[tool.pyright.executionEnvironments]]
+root = "tests"
+reportGeneralTypeIssues = "warning"
+reportOptionalSubscript = "warning"
+reportOptionalMemberAccess = "warning"
+
+[tool.coverage.run]
+branch = true
+source = ["cluebase_backend_sdk"]
+
+[tool.coverage.report]
+# Regression floor: keep combined statement and branch coverage high enough to
+# block large untested modules without failing on small coverage noise.
+fail_under = 80
+precision = 2
+exclude_lines = [
+	"pragma: no cover",
+	"raise NotImplementedError",
+	"if TYPE_CHECKING:",
+	# Defensive ImportError handlers for optional peer dependencies
+	# (sqlalchemy, django, celery, opentelemetry-instrumentation-*). The
+	# module degrades to a no-op when the framework is absent; that branch
+	# is exercised in test environments where the framework happens to be
+	# installed but not in unit tests.
+	"except ImportError",
+]

cluebase_backend_sdk-0.0.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

cluebase_backend_sdk-0.0.1/setup.py

@@ -0,0 +1,20 @@
+from __future__ import annotations
+
+import runpy
+from pathlib import Path
+
+from setuptools import find_packages, setup
+
+
+_VERSION_FILE = Path(__file__).parent / "src" / "cluebase_backend_sdk" / "_version.py"
+_VERSION = runpy.run_path(str(_VERSION_FILE))["__version__"]
+
+
+setup(
+	name="cluebase-backend-sdk",
+	version=_VERSION,
+	description="Cluebase Backend SDK (Python) — OTel-based observation source event capture",
+	python_requires=">=3.10",
+	package_dir={"": "src"},
+	packages=find_packages("src"),
+)