delegate-connector-telegram 0.1.0__tar.gz

delegate_connector_telegram-0.1.0/.env.example

@@ -0,0 +1,20 @@
+# Copyright 2026 Terrene Foundation
+# SPDX-License-Identifier: Apache-2.0
+#
+# Telegram connector configuration. Copy to .env and fill in real values.
+# NEVER commit a populated .env (root .gitignore excludes .env).
+# All credentials are read from the environment — never hardcoded.
+
+# --- Bot API (outbound sendMessage + inbound getUpdates) ---
+# TELEGRAM_BOT_TOKEN is the single auth credential. It is part of the request
+# URL (.../bot${TELEGRAM_BOT_TOKEN}/sendMessage), so the transport logs the
+# method + chat, NEVER the URL or token. Leave blank in the template.
+TELEGRAM_BOT_TOKEN=
+
+# Bot API base URL. Public Telegram is https://api.telegram.org. For local
+# Tier-2/3 tests, point at the hermetic local Bot API service (see
+# docker-compose.yml), e.g. http://localhost:8081.
+TELEGRAM_API_BASE=https://api.telegram.org
+
+# Integer chat_id the integration tests send to. Leave blank in the template.
+TELEGRAM_TEST_CHAT_ID=

delegate_connector_telegram-0.1.0/.gitignore

@@ -0,0 +1,74 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+!.claude/hooks/lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Virtual environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+.python-version
+
+# IDE specific files
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+.jbeval/
+output.txt
+
+# Testing
+.coverage
+htmlcov/
+.pytest_cache/
+.mypy_cache/
+
+# Secrets
+*.pem
+*.key
+secrets/
+
+# Workspace session notes (per-session, not versioned)
+**/.session-notes
+
+# Per-project learning data (generated at runtime)
+.claude/learning/
+.claude/rules/learned-instincts.md
+
+# Runtime telemetry logs (generated by hooks at runtime)
+.claude/logs/
+
+# Internal docs (not for distribution)
+/docs/01-kailash-vibe-cc-internals/
+
+# Generated script outputs (sdk-users examples)
+**/scripts/data/
+**/scripts/outputs/
+**/scripts/*.log
+
+# Journal-hook runtime bookkeeping (per-clone skip log; not source)
+**/.journal-skipped.log

delegate_connector_telegram-0.1.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 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 Support. 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 support.
+
+   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 Terrene Foundation
+
+   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.

delegate_connector_telegram-0.1.0/PKG-INFO

@@ -0,0 +1,120 @@
+Metadata-Version: 2.4
+Name: delegate-connector-telegram
+Version: 0.1.0
+Summary: OSS Telegram connector for the Terrene Delegate substrate (kailash.delegate).
+Project-URL: Homepage, https://github.com/terrene-foundation/delegate-connectors
+Project-URL: Changelog, https://github.com/terrene-foundation/delegate-connectors/blob/main/CHANGELOG.md
+Author: Terrene Foundation
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: bot-api,connector,delegate,kailash,telegram
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Communications :: Chat
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: cryptography>=42.0
+Requires-Dist: httpx>=0.27
+Requires-Dist: kailash>=2.28.0
+Provides-Extra: test
+Requires-Dist: pytest-asyncio>=0.23; extra == 'test'
+Requires-Dist: pytest>=8.0; extra == 'test'
+Requires-Dist: python-dotenv>=1.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+<!--
+Copyright 2026 Terrene Foundation
+SPDX-License-Identifier: Apache-2.0
+-->
+
+# delegate-connector-telegram
+
+An OSS Python connector for the Terrene Delegate substrate. Implements the
+shipped `kailash.delegate.Connector` ABC (kailash 2.26.2) for Telegram via the
+Bot API. It mirrors the email connector's shape and differs only in transport
+(HTTP-only Bot API) and identity model (integer `user_id` / `chat_id`).
+
+The connector contract (the shipped ABC — `authenticate / read / write / invoke`
+plus the `auth_verifier / ledger / revocation` trust properties) is:
+
+- **`write`** — `action` is a thunk wrapping a Bot API `sendMessage` POST,
+  executed under audit, returning a real `SignedActionEnvelope`. The send is the
+  auditable external side-effect.
+- **`read`** — `query` is a thunk wrapping a Bot API `getUpdates` long-poll fetch,
+  executed under audit, returning `(updates, AttestedReadReceipt)`.
+- **`authenticate`** — resolves the dispatch identity's `delegate_id` to a
+  `Principal` against a dual-keyed resolver (by stringified integer `user_id`
+  and `chat_id`). An unknown identity resolves to `Reject` (fail-closed); a
+  `@username` handle is never a resolution key (ref-unsafe and mutable).
+- **`invoke`** — single-method dispatch entry: authenticate FIRST (fail-closed,
+  before any Bot API call), then dispatch a send, returning a
+  `ConnectorInvocationResult(external_side_effect=True)`.
+- Trust properties — `auth_verifier` returns the wired `Ed25519Verifier`;
+  `ledger` / `revocation` return shipped concretes (framework-first; no custom
+  trust primitives).
+
+It subclasses `Connector` **directly** (ADR-1) — NOT `LegacyInvokeConnector`,
+whose proxied `read` / `write` emit empty, unverifiable receipts. There is no
+stale `connect() / identify() / normalize()` surface; those methods do not exist
+in the shipped ABC.
+
+## Components
+
+- **`transport.py`** — the `httpx`-backed Bot API transport (`sendMessage`
+  outbound + `getUpdates` inbound long-poll). A Bot API `429` raises a typed
+  `RateLimitedError` carrying `retry_after`; the caller decides backoff.
+- **`connector.py`** — the `TelegramConnector` itself (the four ABC members + the
+  three trust properties) plus the `verify_action_envelope` /
+  `verify_read_receipt` helpers that re-derive identity-bound signing bytes.
+- **`directory.py`** — the dual-keyed principal resolver + the closed-enum
+  `UnknownSenderDisposition` (unknown sender → `Reject`).
+- **`validation.py`** — pure message-content validation (control-character
+  reject, `text` ≤ 4096 UTF-16 code units, `chat_id` shape), invoked at the
+  `OutboundMessage` construction boundary so every send route is covered.
+- **`compose.py`** — `build_telegram_runtime`, which composes a real
+  `DelegateRuntime` around the connector with the shipped trust / audit /
+  verifier concretes (no mocks).
+
+## Install
+
+```bash
+pip install -e connectors/telegram
+```
+
+## Configure
+
+All credentials come from the environment (see `.env.example`):
+`TELEGRAM_BOT_TOKEN` and `TELEGRAM_API_BASE`. Nothing is hardcoded; nothing is
+logged. The token is part of the request URL, so the transport logs the method +
+chat, never the URL.
+
+## Test
+
+```bash
+pip install -e "connectors/telegram[test]"
+# Tier 1 (unit)
+python -m pytest connectors/telegram/tests/unit -q
+# Tier 2/3 (integration — REAL TelegramTransport over a REAL httpx.AsyncClient
+# whose byte stream terminates at an in-process protocol-faithful Bot API
+# double; NO mock at the connector boundary, so these RUN in CI)
+python -m pytest connectors/telegram/tests/integration -q
+# Conformance (canonical conformance vector set)
+python -m pytest connectors/telegram/tests/conformance -q
+# Regression (behavioral security-property guards; NEVER deleted)
+python -m pytest connectors/telegram/tests/regression -q
+```
+
+The opt-in Tier-3 live test (`test_live_telegram`) skips with a clear "cannot
+execute" reason unless real `TELEGRAM_*` credentials are present — it never falls
+back to a mock. The end-to-end `runtime.execute()` outcome assertions are
+strict-`xfail` gated on an SDK fix (kailash-py#1182); the connector's own
+read / write receipts verify today.
+
+## License
+
+Apache 2.0. All open-source IP is owned by the Terrene Foundation.

delegate_connector_telegram-0.1.0/README.md

@@ -0,0 +1,91 @@
+<!--
+Copyright 2026 Terrene Foundation
+SPDX-License-Identifier: Apache-2.0
+-->
+
+# delegate-connector-telegram
+
+An OSS Python connector for the Terrene Delegate substrate. Implements the
+shipped `kailash.delegate.Connector` ABC (kailash 2.26.2) for Telegram via the
+Bot API. It mirrors the email connector's shape and differs only in transport
+(HTTP-only Bot API) and identity model (integer `user_id` / `chat_id`).
+
+The connector contract (the shipped ABC — `authenticate / read / write / invoke`
+plus the `auth_verifier / ledger / revocation` trust properties) is:
+
+- **`write`** — `action` is a thunk wrapping a Bot API `sendMessage` POST,
+  executed under audit, returning a real `SignedActionEnvelope`. The send is the
+  auditable external side-effect.
+- **`read`** — `query` is a thunk wrapping a Bot API `getUpdates` long-poll fetch,
+  executed under audit, returning `(updates, AttestedReadReceipt)`.
+- **`authenticate`** — resolves the dispatch identity's `delegate_id` to a
+  `Principal` against a dual-keyed resolver (by stringified integer `user_id`
+  and `chat_id`). An unknown identity resolves to `Reject` (fail-closed); a
+  `@username` handle is never a resolution key (ref-unsafe and mutable).
+- **`invoke`** — single-method dispatch entry: authenticate FIRST (fail-closed,
+  before any Bot API call), then dispatch a send, returning a
+  `ConnectorInvocationResult(external_side_effect=True)`.
+- Trust properties — `auth_verifier` returns the wired `Ed25519Verifier`;
+  `ledger` / `revocation` return shipped concretes (framework-first; no custom
+  trust primitives).
+
+It subclasses `Connector` **directly** (ADR-1) — NOT `LegacyInvokeConnector`,
+whose proxied `read` / `write` emit empty, unverifiable receipts. There is no
+stale `connect() / identify() / normalize()` surface; those methods do not exist
+in the shipped ABC.
+
+## Components
+
+- **`transport.py`** — the `httpx`-backed Bot API transport (`sendMessage`
+  outbound + `getUpdates` inbound long-poll). A Bot API `429` raises a typed
+  `RateLimitedError` carrying `retry_after`; the caller decides backoff.
+- **`connector.py`** — the `TelegramConnector` itself (the four ABC members + the
+  three trust properties) plus the `verify_action_envelope` /
+  `verify_read_receipt` helpers that re-derive identity-bound signing bytes.
+- **`directory.py`** — the dual-keyed principal resolver + the closed-enum
+  `UnknownSenderDisposition` (unknown sender → `Reject`).
+- **`validation.py`** — pure message-content validation (control-character
+  reject, `text` ≤ 4096 UTF-16 code units, `chat_id` shape), invoked at the
+  `OutboundMessage` construction boundary so every send route is covered.
+- **`compose.py`** — `build_telegram_runtime`, which composes a real
+  `DelegateRuntime` around the connector with the shipped trust / audit /
+  verifier concretes (no mocks).
+
+## Install
+
+```bash
+pip install -e connectors/telegram
+```
+
+## Configure
+
+All credentials come from the environment (see `.env.example`):
+`TELEGRAM_BOT_TOKEN` and `TELEGRAM_API_BASE`. Nothing is hardcoded; nothing is
+logged. The token is part of the request URL, so the transport logs the method +
+chat, never the URL.
+
+## Test
+
+```bash
+pip install -e "connectors/telegram[test]"
+# Tier 1 (unit)
+python -m pytest connectors/telegram/tests/unit -q
+# Tier 2/3 (integration — REAL TelegramTransport over a REAL httpx.AsyncClient
+# whose byte stream terminates at an in-process protocol-faithful Bot API
+# double; NO mock at the connector boundary, so these RUN in CI)
+python -m pytest connectors/telegram/tests/integration -q
+# Conformance (canonical conformance vector set)
+python -m pytest connectors/telegram/tests/conformance -q
+# Regression (behavioral security-property guards; NEVER deleted)
+python -m pytest connectors/telegram/tests/regression -q
+```
+
+The opt-in Tier-3 live test (`test_live_telegram`) skips with a clear "cannot
+execute" reason unless real `TELEGRAM_*` credentials are present — it never falls
+back to a mock. The end-to-end `runtime.execute()` outcome assertions are
+strict-`xfail` gated on an SDK fix (kailash-py#1182); the connector's own
+read / write receipts verify today.
+
+## License
+
+Apache 2.0. All open-source IP is owned by the Terrene Foundation.

delegate_connector_telegram-0.1.0/docker-compose.yml

@@ -0,0 +1,30 @@
+# Copyright 2026 Terrene Foundation
+# SPDX-License-Identifier: Apache-2.0
+#
+# One service, real infrastructure (no mock at the boundary):
+#
+#   * botapi — a local Bot API HTTP server (the OSS telegram-bot-api daemon).
+#              Speaks the real Bot API protocol over a real socket + JSON cycle,
+#              so the connector's httpx sendMessage/getUpdates paths exercise the
+#              same request-response shape they hit against api.telegram.org.
+#              Backs the Tier-2/3 outbound-arrival + inbound round-trip tests
+#              (wired in todo 07). TELEGRAM_API_BASE points at this service.
+#
+# TELEGRAM_API_ID / TELEGRAM_API_HASH come from the environment (the local Bot
+# API daemon requires Telegram app credentials to start). They are read from the
+# shell / .env — never hardcoded here (rules/security.md). No Postgres, no PACT
+# (the shipped kailash.delegate runtime audit is in-memory).
+services:
+  botapi:
+    image: aiogram/telegram-bot-api:latest
+    container_name: delegate-telegram-botapi
+    restart: unless-stopped
+    environment:
+      # Telegram app credentials (https://my.telegram.org). Supplied via the
+      # environment; the template .env leaves them blank. The daemon refuses to
+      # start without them — that is the intended fail-closed behavior.
+      TELEGRAM_API_ID: ${TELEGRAM_API_ID:-}
+      TELEGRAM_API_HASH: ${TELEGRAM_API_HASH:-}
+      TELEGRAM_LOCAL: "true"
+    ports:
+      - "8081:8081" # Bot API HTTP

delegate_connector_telegram-0.1.0/pyproject.toml

@@ -0,0 +1,66 @@
+# Copyright 2026 Terrene Foundation
+# SPDX-License-Identifier: Apache-2.0
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "delegate-connector-telegram"
+dynamic = ["version"]
+description = "OSS Telegram connector for the Terrene Delegate substrate (kailash.delegate)."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Terrene Foundation" }]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Communications :: Chat",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+keywords = ["kailash", "delegate", "connector", "telegram", "bot-api"]
+dependencies = [
+    # Connector ABC (write/read/authenticate) + Principal/SignedActionEnvelope
+    # landed in kailash 2.26.1; 2.24.0-2.25.2 ImportError on Principal. Floor 2.28.0:
+    # kailash-py#1182 (runtime audit-emit signature bug) fixed at <=2.28.1; dev/CI pin 2.28.1.
+    "kailash>=2.28.0",
+    # Ed25519Verifier requires the cryptography lib (kailash [trust] extra
+    # ships it; declared here because this connector composes a real
+    # Ed25519Verifier directly).
+    "cryptography>=42.0",
+    # async HTTP transport for the Bot API (sendMessage + getUpdates).
+    "httpx>=0.27",
+]
+
+[project.optional-dependencies]
+test = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.23",
+    "python-dotenv>=1.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/terrene-foundation/delegate-connectors"
+Changelog = "https://github.com/terrene-foundation/delegate-connectors/blob/main/CHANGELOG.md"
+
+[tool.hatch.version]
+path = "src/delegate_connectors/telegram/__init__.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/delegate_connectors"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+asyncio_default_fixture_loop_scope = "function"
+testpaths = ["tests"]
+markers = [
+    "integration: real-infra Tier-2/3 tests (require a running local Bot API service)",
+    "regression: regression tests guarding a specific fixed bug (NEVER deleted)",
+    "conformance: canonical conformance vector tests",
+]

delegate_connector_telegram-0.1.0/src/delegate_connectors/telegram/__init__.py

@@ -0,0 +1,52 @@
+# Copyright 2026 Terrene Foundation
+# SPDX-License-Identifier: Apache-2.0
+"""Telegram connector for the Terrene Delegate substrate.
+
+Implements the shipped ``kailash.delegate.Connector`` ABC (kailash 2.26.2) for
+Telegram via the Bot API: ``sendMessage`` outbound (``write``) and ``getUpdates``
+long-poll inbound (``read``), authenticated against a dual-keyed principal
+resolver. See the package README + ``specs/`` in the monorepo root for the full
+contract.
+
+The full surface has shipped: the pure-logic foundation — principal resolution
+(:mod:`delegate_connectors.telegram.directory`) and message-content validation
+(:mod:`delegate_connectors.telegram.validation`) — alongside the ``httpx``-backed
+Bot API transport (:mod:`delegate_connectors.telegram.transport`), the
+``TelegramConnector`` itself (:mod:`delegate_connectors.telegram.connector`), and
+the runtime composition (:mod:`delegate_connectors.telegram.compose`).
+
+``__all__`` re-exports only the pure, always-importable primitives (directory +
+validation) so importing the package root never forces an ``httpx`` import for
+callers that only need the resolver / validators. The ``httpx``-dependent
+modules are imported from their own submodules directly (e.g.
+``from delegate_connectors.telegram.transport import TelegramTransport``).
+"""
+
+__version__ = "0.1.0"
+
+from delegate_connectors.telegram.directory import (
+    ResolutionOutcome,
+    TelegramPrincipalResolver,
+    UnknownSenderDisposition,
+)
+from delegate_connectors.telegram.validation import (
+    MAX_TEXT_UTF16_UNITS,
+    MessageValidationError,
+    text_utf16_units,
+    validate_chat_id,
+    validate_text,
+)
+
+__all__ = [
+    "__version__",
+    # Principal resolution (directory.py).
+    "TelegramPrincipalResolver",
+    "UnknownSenderDisposition",
+    "ResolutionOutcome",
+    # Message-content validation (validation.py — pure, no transport).
+    "MessageValidationError",
+    "validate_text",
+    "validate_chat_id",
+    "text_utf16_units",
+    "MAX_TEXT_UTF16_UNITS",
+]