telegram-dev 0.4.0__tar.gz → 0.5.1__tar.gz

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/.claude-plugin/marketplace.json

@@ -1,17 +1,17 @@
 {
   "name": "telegram-dev-tools",
   "owner": {"name": "Kay0k1"},
-  "metadata": {"description": "Independent Telegram development tools with official documentation", "version": "0.4.0"},
+  "metadata": {"description": "Independent Telegram development tools with official documentation", "version": "0.5.1"},
   "plugins": [
     {
       "name": "telegram-dev",
       "source": "./",
-      "description": "Source-verified Telegram development with official documentation search",
-      "version": "0.4.0",
+      "description": "Source-verified Telegram and TON development with official documentation search",
+      "version": "0.5.1",
       "homepage": "https://github.com/Kay0k1/telegram-dev",
       "repository": "https://github.com/Kay0k1/telegram-dev",
       "license": "MIT",
-      "keywords": ["telegram", "documentation", "bot-api", "mini-apps", "mtproto", "tdlib"]
+      "keywords": ["telegram", "documentation", "bot-api", "mini-apps", "mtproto", "tdlib", "ton", "ton-connect"]
     }
   ]
 }

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "telegram-dev",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "displayName": "Telegram Dev",
-  "description": "Source-verified Telegram development across Bot API, Mini Apps, MTProto, TDLib, media and public releases. Independent project by Kay0k1.",
+  "description": "Source-verified Telegram and TON development across Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk and public releases. Independent project by Kay0k1.",
   "author": {
     "name": "Kay0k1",
     "url": "https://github.com/Kay0k1"
@@ -15,5 +15,5 @@
   "supportUrl": "https://github.com/Kay0k1/telegram-dev/issues",
   "privacyPolicyUrl": "https://github.com/Kay0k1/telegram-dev/blob/main/docs/privacy.md",
   "termsOfServiceUrl": "https://github.com/Kay0k1/telegram-dev/blob/main/docs/terms.md",
-  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "documentation"]
+  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "ton", "ton-connect", "documentation"]
 }

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "telegram-dev",
-  "version": "0.4.0",
-  "description": "Source-verified Telegram development across Bot API, Mini Apps, MTProto, TDLib and public release history",
+  "version": "0.5.1",
+  "description": "Source-verified Telegram and TON development across Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk and public release history",
   "author": {
     "name": "Kay0k1",
     "url": "https://github.com/Kay0k1"
@@ -9,7 +9,7 @@
   "homepage": "https://github.com/Kay0k1/telegram-dev",
   "repository": "https://github.com/Kay0k1/telegram-dev",
   "license": "MIT",
-  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "documentation"],
+  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "ton", "ton-connect", "documentation"],
   "skills": "./skills/",
   "mcpServers": {
     "telegram-knowledge": {
@@ -22,7 +22,7 @@
   "interface": {
     "displayName": "Telegram Dev",
     "shortDescription": "Telegram development knowledge",
-    "longDescription": "Develop Telegram bots, Mini Apps, clients and integrations using public official documentation. Telegram Dev helps identify the API surface, verify feature eligibility, inspect release changes and read current documentation before implementation. The bundled local MCP maintains a documentation cache; uv is required. This independent community project is maintained by Kay0k1 and is not affiliated with Telegram. It does not connect to Telegram accounts or operate on private chats.",
+    "longDescription": "Develop Telegram bots, Mini Apps, clients, integrations and TON features using public official Telegram and TON documentation. Telegram Dev helps identify the API surface, verify feature eligibility, inspect release changes and read current documentation before implementation. The bundled local MCP maintains a documentation cache; uv is required. This independent community project is maintained by Kay0k1 and is not affiliated with Telegram. It does not connect to Telegram accounts or operate on private chats.",
     "developerName": "Kay0k1",
     "category": "Developer Tools",
     "capabilities": ["Search Telegram documentation", "Read official sources", "Check documentation freshness"],

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/.cursor-plugin/plugin.json

@@ -1,12 +1,12 @@
 {
   "name": "telegram-dev",
-  "version": "0.4.0",
-  "description": "Source-verified Telegram development: Bot API, Mini Apps, MTProto, TDLib, media and public releases",
+  "version": "0.5.1",
+  "description": "Source-verified Telegram and TON development: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk and public releases",
   "author": {"name": "Kay0k1"},
   "license": "MIT",
   "repository": "https://github.com/Kay0k1/telegram-dev",
   "homepage": "https://github.com/Kay0k1/telegram-dev",
-  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "documentation"],
+  "keywords": ["telegram", "bot-api", "mini-apps", "mtproto", "tdlib", "ton", "ton-connect", "documentation"],
   "logo": "assets/logo.svg",
   "skills": "./skills/",
   "mcpServers": "./.mcp.json"

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/AGENTS.md

@@ -1,6 +1,6 @@
 # Telegram Dev — notes for coding agents
 
-MCP server + agent skill that give Claude Code, Codex and Cursor current official Telegram documentation. `CLAUDE.md` is a symlink to this file.
+MCP server + agent skill that give Claude Code, Codex and Cursor current official Telegram and TON documentation. TON pages are crawled from the Markdown twins listed in `https://docs.ton.org/llms.txt` and cited by their human URLs (`fetch_location()` maps between them). `CLAUDE.md` is a symlink to this file.
 
 ## Layout
 

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to this project. Versions follow [Semantic Versioning](https://semver.org/).
 
+## [0.5.1] - 2026-11-10
+
+### Fixed
+
+- `uv sync --frozen` on a machine without Python failed: uv picked Python 3.15, for which the locked pydantic-core and rpds-py had no wheels, and anyio does not yet start on 3.15. The project now requires Python `>=3.10,<3.15`, so uv installs 3.14, and the lock uses pydantic-core, rpds-py, anyio and MCP SDK dependencies with current wheels. This fixes Glama builds and the Claude Code plugin on such machines.
+- CI also runs the tests on the newest Python the project allows, installed by uv.
+
+## [0.5.0] - 2026-11-10
+
+### Added
+
+- TON documentation: every page listed in the docs.ton.org `llms.txt` index (TON Connect, payments, APIs, smart contracts, Tolk, TVM, blockchain foundations), the TEP standards, the TON node and Tolk changelogs, and Telegram's Blockchain Guidelines for Mini Apps. Pages are read as Markdown and cited by their docs.ton.org URLs.
+- Search areas `ton` and `ton-releases`; Russian aliases for wallets, contracts, jettons and NFTs.
+- Skill guide `ton-and-blockchain.md`: Telegram's rules first (TON and TON Connect only, Stars for digital goods), then TON Connect and `ton_proof`, payment confirmation, standards, testnet and key safety.
+- The daily source monitor covers the new TON sources (57 in total).
+
 ## [0.4.0] - 2026-11-10
 
 ### Added
@@ -35,6 +51,8 @@ All notable changes to this project. Versions follow [Semantic Versioning](https
 
 - First public release: documentation MCP server with an on-demand local cache, agent skill, project installer for Codex, Claude Code and Cursor, and a Claude Code plugin catalog.
 
+[0.5.1]: https://github.com/Kay0k1/telegram-dev/compare/v0.5.0...v0.5.1
+[0.5.0]: https://github.com/Kay0k1/telegram-dev/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/Kay0k1/telegram-dev/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/Kay0k1/telegram-dev/compare/v0.2.0...v0.3.0
 [0.2.0]: https://github.com/Kay0k1/telegram-dev/releases/tag/v0.2.0

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/MANIFEST.in

@@ -1,4 +1,4 @@
-include README.ru.md CHANGELOG.md AGENTS.md server.json uv.lock .mcp.json
+include README.ru.md CHANGELOG.md AGENTS.md server.json glama.json uv.lock .mcp.json
 include Dockerfile .dockerignore
 recursive-include docs *.md
 recursive-include deploy *.yml Caddyfile .env.example .gitkeep

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/NOTICE

@@ -1,6 +1,6 @@
 Telegram Dev is an independent community project, not an official Telegram product.
 The MIT license applies to this project's original code and authored instructions.
-Retrieved Telegram documentation, third-party source code, names and trademarks
+Retrieved Telegram and TON documentation, third-party source code, names and trademarks
 retain their original ownership and applicable terms. The public source package
 does not redistribute the previously downloaded documentation database. Each
 installation retrieves public sources directly and retains source URLs.

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/PKG-INFO

@@ -1,9 +1,9 @@
 Metadata-Version: 2.4
 Name: telegram-dev
-Version: 0.4.0
+Version: 0.5.1
 Summary: Source-grounded Telegram development skills and documentation MCP
 License-Expression: MIT
-Requires-Python: >=3.10
+Requires-Python: <3.15,>=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
@@ -22,9 +22,9 @@ Dynamic: license-file
 [![Docs monitor](https://github.com/Kay0k1/telegram-dev/actions/workflows/documentation.yml/badge.svg)](https://github.com/Kay0k1/telegram-dev/tree/docs-status)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-**Current official Telegram documentation for Claude Code, Codex and Cursor.**
+**Current official Telegram and TON documentation for Claude Code, Codex and Cursor.**
 
-Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes and searches the official docs (Bot API, Mini Apps, MTProto, TDLib, changelogs) and keeps them fresh. The skill teaches the agent to pick the right API, check eligibility and library support, and cite what it read.
+Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes and searches the official docs and keeps them fresh: Bot API, Mini Apps, MTProto, TDLib, and on the TON side docs.ton.org (TON Connect, Tolk, TVM, APIs), the TEP standards and the changelogs. The skill teaches the agent to pick the right API, follow Telegram's rules, check library support, and cite what it read.
 
 [Русская версия](README.ru.md)
 
@@ -34,6 +34,8 @@ Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes a
 
 Telegram ships a new Bot API version every month or two. A model's knowledge of it stops at its training cutoff, so agents confidently write code against fields that changed or never existed. They also mix up the Bot API, MTProto and TDLib, which have very different capabilities.
 
+TON moves just as fast. The current TON docs call the coin Gram, describe Telegram Money, the wallet built into Telegram, and treat Tolk as the main contract language with FunC as legacy. On top of that, Telegram has its own rules: blockchain features in Mini Apps must use TON and TON Connect, and digital goods are sold for Stars.
+
 With Telegram Dev the agent reads the current page before it writes code. A real Codex CLI run in a fresh project after `uvx telegram-dev install --agent codex` (tool calls trimmed):
 
 ```text
@@ -62,6 +64,26 @@ unstyled. Source: https://core.telegram.org/bots/api#inlinekeyboardbutton
    "style": "danger", "icon_custom_emoji_id": "YOUR_CUSTOM_EMOJI_ID"}]]}}
 ```
 
+The skill also knows when *not* to reach for a blockchain. Another real Codex run:
+
+```text
+> Use the telegram-dev skill. Our Telegram Mini App sells a premium in-game skin
+  for 2 TON. I want a Buy button that connects the user's wallet and charges them.
+
+  get_telegram_document {"url": "https://core.telegram.org/bots/payments-stars", "refresh": true}
+  search_telegram_docs {"query": "createInvoiceLink answerPreCheckoutQuery successful_payment XTR", "area": "bot-api"}
+  get_telegram_document {"url": "https://docs.ton.org/applications/ton-connect/overview", "refresh": true}
+  get_telegram_document {"url": "https://core.telegram.org/bots/webapps", "offset": 40310}
+
+Use Telegram Stars (XTR) through the Bot API. The skin is a digital good, so
+Telegram requires Stars and prohibits cryptocurrency payment for this purchase.
+For permitted wallet features, use the TON Connect SDK.
+1. Validate initData on the backend and bind the order to the user.
+2. createInvoiceLink with currency "XTR", open it with Telegram.WebApp.openInvoice.
+3. Answer pre_checkout_query, grant the skin once on successful_payment,
+   store telegram_payment_charge_id for refunds.
+```
+
 ## Install
 
 You need [uv](https://docs.astral.sh/uv/getting-started/installation/). No bot token, Telegram account or API key is needed: the server only reads public documentation.
@@ -121,11 +143,11 @@ The tools work without the skill, but the skill is what makes an agent use them
 
 | Tool | What it does |
 | --- | --- |
-| `search_telegram_docs` | Full-text search over indexed sections, optionally limited to one area: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `releases` and others |
+| `search_telegram_docs` | Full-text search over indexed sections, optionally limited to one area: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `ton`, `releases`, `ton-releases` and others |
 | `get_telegram_document` | Reads an official page in pages of up to 40,000 characters; fetches it if it is missing or older than 6 hours |
 | `telegram_corpus_status` | What is indexed, how fresh it is and which sources failed |
 | `telegram_document_history` | Revisions of a page captured by this installation |
-| `telegram_sources` | The 52 official entry points, grouped by API area |
+| `telegram_sources` | The 57 official entry points, grouped by API area |
 
 The cache starts empty. Pages are fetched the first time the agent reads them and indexed right away. To pre-fetch everything reachable from the configured sources:
 
@@ -146,7 +168,8 @@ uvx telegram-dev status
 | MTProto and TDLib | User vs bot authorization, schema and layers, TDLib versions |
 | Business and payments | Business connections, Stars, subscriptions, gifts, paid media |
 | Groups and channels | Admin rights, forums and topics, moderation |
-| Releases | Bot API changelog, API layers, TDLib changelog, official announcements |
+| TON | Telegram's blockchain rules for Mini Apps, Stars vs crypto, TON Connect and `ton_proof`, payment processing, jettons and NFTs (TEPs), Tolk contracts, testnet first, key safety |
+| Releases | Bot API changelog, API layers, TDLib changelog, TON node and Tolk changelogs, official announcements |
 
 The skill lives in [skills/telegram-dev](skills/telegram-dev/SKILL.md), with one reference file per area.
 
@@ -155,7 +178,7 @@ The skill lives in [skills/telegram-dev](skills/telegram-dev/SKILL.md), with one
 - Reading a page older than 6 hours re-fetches it. Search re-fetches up to six stale matching pages.
 - While the server runs, a background cycle checks up to 120 pages every 6 hours: entry points, newly found links, oldest pages.
 - If Telegram's site is unreachable, the cached text is kept and marked stale with the error, so the agent knows it is reading an old copy.
-- A daily GitHub Action checks all 52 official sources and publishes hashes and errors on the [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status) branch.
+- A daily GitHub Action checks all 57 official sources and publishes hashes and errors on the [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status) branch.
 
 Settings such as the cache path (`TELEGRAM_KNOWLEDGE_DB`) and refresh intervals are in [docs/runtime.md](docs/runtime.md).
 
@@ -170,8 +193,8 @@ uvx telegram-dev serve --transport streamable-http --port 8000
 ## Limits
 
 - Search is local full-text search (SQLite FTS5), not semantic search. Exact method names and English terms work best. A small set of Russian aliases is built in.
-- Coverage is what can be reached from the 52 official entry points. Page history starts when your installation first fetched the page.
-- The server does not log in to Telegram, send messages or touch chats. It only reads public pages.
+- Coverage is what can be reached from the 57 official entry points. TON pages come from the `llms.txt` index that docs.ton.org publishes for agents, so new TON pages are picked up automatically. Page history starts when your installation first fetched the page.
+- The server does not log in to Telegram, send messages, touch chats or hold wallet keys. It only reads public pages.
 - The skill improves how agents work. It does not guarantee a correct answer: check the code against Telegram before shipping.
 
 ## Development
@@ -187,4 +210,4 @@ CI runs the tests on Linux, macOS and Windows and checks the Docker image. [docs
 
 ## License
 
-[MIT](LICENSE) for the code and the skill. Fetched Telegram documentation remains Telegram's; the package does not bundle it ([NOTICE](NOTICE)). This is an independent project, not affiliated with Telegram.
+[MIT](LICENSE) for the code and the skill. Fetched Telegram and TON documentation remains with its owners; the package does not bundle it ([NOTICE](NOTICE)). This is an independent project, not affiliated with Telegram or the TON Foundation.

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/README.md

@@ -5,9 +5,9 @@
 [![Docs monitor](https://github.com/Kay0k1/telegram-dev/actions/workflows/documentation.yml/badge.svg)](https://github.com/Kay0k1/telegram-dev/tree/docs-status)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-**Current official Telegram documentation for Claude Code, Codex and Cursor.**
+**Current official Telegram and TON documentation for Claude Code, Codex and Cursor.**
 
-Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes and searches the official docs (Bot API, Mini Apps, MTProto, TDLib, changelogs) and keeps them fresh. The skill teaches the agent to pick the right API, check eligibility and library support, and cite what it read.
+Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes and searches the official docs and keeps them fresh: Bot API, Mini Apps, MTProto, TDLib, and on the TON side docs.ton.org (TON Connect, Tolk, TVM, APIs), the TEP standards and the changelogs. The skill teaches the agent to pick the right API, follow Telegram's rules, check library support, and cite what it read.
 
 [Русская версия](README.ru.md)
 
@@ -17,6 +17,8 @@ Telegram Dev is an MCP server plus an agent skill. The server fetches, indexes a
 
 Telegram ships a new Bot API version every month or two. A model's knowledge of it stops at its training cutoff, so agents confidently write code against fields that changed or never existed. They also mix up the Bot API, MTProto and TDLib, which have very different capabilities.
 
+TON moves just as fast. The current TON docs call the coin Gram, describe Telegram Money, the wallet built into Telegram, and treat Tolk as the main contract language with FunC as legacy. On top of that, Telegram has its own rules: blockchain features in Mini Apps must use TON and TON Connect, and digital goods are sold for Stars.
+
 With Telegram Dev the agent reads the current page before it writes code. A real Codex CLI run in a fresh project after `uvx telegram-dev install --agent codex` (tool calls trimmed):
 
 ```text
@@ -45,6 +47,26 @@ unstyled. Source: https://core.telegram.org/bots/api#inlinekeyboardbutton
    "style": "danger", "icon_custom_emoji_id": "YOUR_CUSTOM_EMOJI_ID"}]]}}
 ```
 
+The skill also knows when *not* to reach for a blockchain. Another real Codex run:
+
+```text
+> Use the telegram-dev skill. Our Telegram Mini App sells a premium in-game skin
+  for 2 TON. I want a Buy button that connects the user's wallet and charges them.
+
+  get_telegram_document {"url": "https://core.telegram.org/bots/payments-stars", "refresh": true}
+  search_telegram_docs {"query": "createInvoiceLink answerPreCheckoutQuery successful_payment XTR", "area": "bot-api"}
+  get_telegram_document {"url": "https://docs.ton.org/applications/ton-connect/overview", "refresh": true}
+  get_telegram_document {"url": "https://core.telegram.org/bots/webapps", "offset": 40310}
+
+Use Telegram Stars (XTR) through the Bot API. The skin is a digital good, so
+Telegram requires Stars and prohibits cryptocurrency payment for this purchase.
+For permitted wallet features, use the TON Connect SDK.
+1. Validate initData on the backend and bind the order to the user.
+2. createInvoiceLink with currency "XTR", open it with Telegram.WebApp.openInvoice.
+3. Answer pre_checkout_query, grant the skin once on successful_payment,
+   store telegram_payment_charge_id for refunds.
+```
+
 ## Install
 
 You need [uv](https://docs.astral.sh/uv/getting-started/installation/). No bot token, Telegram account or API key is needed: the server only reads public documentation.
@@ -104,11 +126,11 @@ The tools work without the skill, but the skill is what makes an agent use them
 
 | Tool | What it does |
 | --- | --- |
-| `search_telegram_docs` | Full-text search over indexed sections, optionally limited to one area: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `releases` and others |
+| `search_telegram_docs` | Full-text search over indexed sections, optionally limited to one area: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `ton`, `releases`, `ton-releases` and others |
 | `get_telegram_document` | Reads an official page in pages of up to 40,000 characters; fetches it if it is missing or older than 6 hours |
 | `telegram_corpus_status` | What is indexed, how fresh it is and which sources failed |
 | `telegram_document_history` | Revisions of a page captured by this installation |
-| `telegram_sources` | The 52 official entry points, grouped by API area |
+| `telegram_sources` | The 57 official entry points, grouped by API area |
 
 The cache starts empty. Pages are fetched the first time the agent reads them and indexed right away. To pre-fetch everything reachable from the configured sources:
 
@@ -129,7 +151,8 @@ uvx telegram-dev status
 | MTProto and TDLib | User vs bot authorization, schema and layers, TDLib versions |
 | Business and payments | Business connections, Stars, subscriptions, gifts, paid media |
 | Groups and channels | Admin rights, forums and topics, moderation |
-| Releases | Bot API changelog, API layers, TDLib changelog, official announcements |
+| TON | Telegram's blockchain rules for Mini Apps, Stars vs crypto, TON Connect and `ton_proof`, payment processing, jettons and NFTs (TEPs), Tolk contracts, testnet first, key safety |
+| Releases | Bot API changelog, API layers, TDLib changelog, TON node and Tolk changelogs, official announcements |
 
 The skill lives in [skills/telegram-dev](skills/telegram-dev/SKILL.md), with one reference file per area.
 
@@ -138,7 +161,7 @@ The skill lives in [skills/telegram-dev](skills/telegram-dev/SKILL.md), with one
 - Reading a page older than 6 hours re-fetches it. Search re-fetches up to six stale matching pages.
 - While the server runs, a background cycle checks up to 120 pages every 6 hours: entry points, newly found links, oldest pages.
 - If Telegram's site is unreachable, the cached text is kept and marked stale with the error, so the agent knows it is reading an old copy.
-- A daily GitHub Action checks all 52 official sources and publishes hashes and errors on the [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status) branch.
+- A daily GitHub Action checks all 57 official sources and publishes hashes and errors on the [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status) branch.
 
 Settings such as the cache path (`TELEGRAM_KNOWLEDGE_DB`) and refresh intervals are in [docs/runtime.md](docs/runtime.md).
 
@@ -153,8 +176,8 @@ uvx telegram-dev serve --transport streamable-http --port 8000
 ## Limits
 
 - Search is local full-text search (SQLite FTS5), not semantic search. Exact method names and English terms work best. A small set of Russian aliases is built in.
-- Coverage is what can be reached from the 52 official entry points. Page history starts when your installation first fetched the page.
-- The server does not log in to Telegram, send messages or touch chats. It only reads public pages.
+- Coverage is what can be reached from the 57 official entry points. TON pages come from the `llms.txt` index that docs.ton.org publishes for agents, so new TON pages are picked up automatically. Page history starts when your installation first fetched the page.
+- The server does not log in to Telegram, send messages, touch chats or hold wallet keys. It only reads public pages.
 - The skill improves how agents work. It does not guarantee a correct answer: check the code against Telegram before shipping.
 
 ## Development
@@ -170,4 +193,4 @@ CI runs the tests on Linux, macOS and Windows and checks the Docker image. [docs
 
 ## License
 
-[MIT](LICENSE) for the code and the skill. Fetched Telegram documentation remains Telegram's; the package does not bundle it ([NOTICE](NOTICE)). This is an independent project, not affiliated with Telegram.
+[MIT](LICENSE) for the code and the skill. Fetched Telegram and TON documentation remains with its owners; the package does not bundle it ([NOTICE](NOTICE)). This is an independent project, not affiliated with Telegram or the TON Foundation.

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/README.ru.md

@@ -5,9 +5,9 @@
 [![Docs monitor](https://github.com/Kay0k1/telegram-dev/actions/workflows/documentation.yml/badge.svg)](https://github.com/Kay0k1/telegram-dev/tree/docs-status)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-**Актуальная официальная документация Telegram для Claude Code, Codex и Cursor.**
+**Актуальная официальная документация Telegram и TON для Claude Code, Codex и Cursor.**
 
-Telegram Dev — это MCP-сервер и скилл для агента. Сервер загружает, индексирует и ищет официальную документацию (Bot API, Mini Apps, MTProto, TDLib, списки изменений) и следит, чтобы она не устаревала. Скилл учит агента выбирать нужный API, проверять, кому доступна функция и поддерживает ли её библиотека, и указывать, откуда взяты сведения.
+Telegram Dev — это MCP-сервер и скилл для агента. Сервер загружает, индексирует и ищет официальную документацию и следит, чтобы она не устаревала: Bot API, Mini Apps, MTProto, TDLib, а со стороны TON — docs.ton.org (TON Connect, Tolk, TVM, API), стандарты TEP и списки изменений. Скилл учит агента выбирать нужный API, соблюдать правила Telegram, проверять поддержку в библиотеке и указывать, откуда взяты сведения.
 
 [English](README.md)
 
@@ -15,6 +15,8 @@ Telegram Dev — это MCP-сервер и скилл для агента. Се
 
 Bot API выходит раз в месяц-два. Модель знает его только на дату своего обучения, поэтому агент уверенно пишет код с полями, которые уже изменились или которых никогда не было. Ещё агенты путают Bot API, MTProto и TDLib, а возможности у них сильно разные.
 
+TON меняется так же быстро. В текущей документации TON монета называется Gram, описан Telegram Money — кошелёк внутри Telegram, а основной язык контрактов — Tolk, FunC стал устаревшим. Сверху — правила самого Telegram: блокчейн в Mini Apps только на TON и через TON Connect, цифровые товары — за Stars.
+
 С Telegram Dev агент сначала читает актуальную страницу, потом пишет код. Настоящий прогон Codex CLI в новом проекте после `uvx telegram-dev install --agent codex` (вызовы сокращены):
 
 ```text
@@ -39,6 +41,26 @@ supergroup. PTB 22.7+ supports both fields. Older Telegram clients show the butt
 unstyled. Source: https://core.telegram.org/bots/api#inlinekeyboardbutton
 ```
 
+Скилл знает и когда блокчейн *не* нужен. Ещё один настоящий прогон Codex:
+
+```text
+> Use the telegram-dev skill. Our Telegram Mini App sells a premium in-game skin
+  for 2 TON. I want a Buy button that connects the user's wallet and charges them.
+
+  get_telegram_document {"url": "https://core.telegram.org/bots/payments-stars", "refresh": true}
+  search_telegram_docs {"query": "createInvoiceLink answerPreCheckoutQuery successful_payment XTR", "area": "bot-api"}
+  get_telegram_document {"url": "https://docs.ton.org/applications/ton-connect/overview", "refresh": true}
+  get_telegram_document {"url": "https://core.telegram.org/bots/webapps", "offset": 40310}
+
+Use Telegram Stars (XTR) through the Bot API. The skin is a digital good, so
+Telegram requires Stars and prohibits cryptocurrency payment for this purchase.
+For permitted wallet features, use the TON Connect SDK.
+1. Validate initData on the backend and bind the order to the user.
+2. createInvoiceLink with currency "XTR", open it with Telegram.WebApp.openInvoice.
+3. Answer pre_checkout_query, grant the skin once on successful_payment,
+   store telegram_payment_charge_id for refunds.
+```
+
 ## Установка
 
 Нужен [uv](https://docs.astral.sh/uv/getting-started/installation/). Токен бота, аккаунт Telegram и ключи API не нужны: сервер читает только публичную документацию.
@@ -98,11 +120,11 @@ Cursor: [![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](htt
 
 | Инструмент | Что делает |
 | --- | --- |
-| `search_telegram_docs` | Полнотекстовый поиск по разделам, можно ограничить областью: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `releases` и другими |
+| `search_telegram_docs` | Полнотекстовый поиск по разделам, можно ограничить областью: `bot-api`, `mini-apps`, `telegram-api`, `tdlib`, `ton`, `releases`, `ton-releases` и другими |
 | `get_telegram_document` | Читает официальную страницу частями до 40 000 символов; загружает её, если страницы нет или она старше 6 часов |
 | `telegram_corpus_status` | Что проиндексировано, насколько свежее и какие источники не загрузились |
 | `telegram_document_history` | Версии страницы, которые видела эта установка |
-| `telegram_sources` | 52 официальные точки входа по областям API |
+| `telegram_sources` | 57 официальных точек входа по областям API |
 
 Кэш сначала пустой. Страница загружается, когда агент впервые её читает, и сразу индексируется. Загрузить заранее всё, что достижимо из настроенных источников:
 
@@ -123,7 +145,8 @@ uvx telegram-dev status
 | MTProto и TDLib | Авторизация пользователя и бота, схема и слои, версии TDLib |
 | Бизнес и платежи | Бизнес-подключения, Stars, подписки, подарки, платный контент |
 | Группы и каналы | Права администраторов, форумы и темы, модерация |
-| Релизы | Changelog Bot API, слои API, changelog TDLib, официальные анонсы |
+| TON | Правила Telegram для блокчейна в Mini Apps, Stars или крипта, TON Connect и `ton_proof`, приём платежей, жетоны и NFT (TEP), контракты на Tolk, сначала testnet, безопасность ключей |
+| Релизы | Changelog Bot API, слои API, changelog TDLib, changelog узла TON и Tolk, официальные анонсы |
 
 Скилл лежит в [skills/telegram-dev](skills/telegram-dev/SKILL.md), по справочному файлу на каждую область.
 
@@ -132,7 +155,7 @@ uvx telegram-dev status
 - Страница старше 6 часов при чтении загружается заново. Поиск обновляет до шести устаревших совпадений.
 - Пока сервер работает, раз в 6 часов фоновый цикл проверяет до 120 страниц: точки входа, новые ссылки, самые старые страницы.
 - Если сайт Telegram недоступен, сохраняется прежний текст с пометкой об устаревании и ошибкой, и агент видит, что читает старую копию.
-- GitHub Action раз в сутки проверяет все 52 официальных источника и публикует хеши и ошибки в ветке [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status).
+- GitHub Action раз в сутки проверяет все 57 официальных источников и публикует хеши и ошибки в ветке [`docs-status`](https://github.com/Kay0k1/telegram-dev/tree/docs-status).
 
 Путь к кэшу (`TELEGRAM_KNOWLEDGE_DB`) и интервалы обновления — в [docs/runtime.md](docs/runtime.md).
 
@@ -147,8 +170,8 @@ uvx telegram-dev serve --transport streamable-http --port 8000
 ## Ограничения
 
 - Поиск локальный полнотекстовый (SQLite FTS5), не семантический. Лучше всего работают точные имена методов и английские термины. Есть небольшая таблица русских синонимов.
-- Охват — то, что достижимо из 52 официальных точек входа. История страницы начинается с её первой загрузки в вашей установке.
-- Сервер не входит в Telegram, не отправляет сообщения и не трогает чаты. Он читает только публичные страницы.
+- Охват — то, что достижимо из 57 официальных точек входа. Страницы TON берутся из оглавления `llms.txt`, которое docs.ton.org публикует для агентов, поэтому новые страницы подхватываются сами. История страницы начинается с её первой загрузки в вашей установке.
+- Сервер не входит в Telegram, не отправляет сообщения, не трогает чаты и не хранит ключи кошельков. Он читает только публичные страницы.
 - Скилл улучшает работу агента, но не гарантирует правильный ответ: проверяйте код в Telegram перед выкаткой.
 
 ## Разработка
@@ -164,4 +187,4 @@ CI запускает тесты на Linux, macOS и Windows и проверя
 
 ## Лицензия
 
-[MIT](LICENSE) для кода и скилла. Загруженная документация Telegram остаётся собственностью Telegram, пакет её не содержит ([NOTICE](NOTICE)). Независимый проект, не связан с Telegram.
+[MIT](LICENSE) для кода и скилла. Загруженная документация Telegram и TON остаётся у её владельцев, пакет её не содержит ([NOTICE](NOTICE)). Независимый проект, не связан с Telegram и TON Foundation.

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/docs/catalog-submissions.md

@@ -49,13 +49,13 @@ uv run --frozen python scripts/package_openai.py --skill-only
 1. Войдите своим аккаунтом в [OpenAI Plugins](https://platform.openai.com/plugins), выберите организацию и проект. Нужны права владельца или Apps Management Write. Завершите individual verification в [Organization settings](https://platform.openai.com/settings/organization/general); проверка личности выполняется издателем в кабинете.
 2. Сначала проверьте существующие drafts. Для новой заявки выберите **Upload new or existing plugin** / **Create plugin**, затем **Skills only**, свою проверенную Developer identity и файл `telegram-dev-skill-openai.zip`.
 3. В **Metadata & Skills** проверьте импортированные значения и дождитесь scans. Required safety/security scans каждого скилла должны пройти; они могут занять до двух часов. Для исправления package-managed полей загрузите исправленный ZIP.
-4. Выберите draft → **Submit for review**, заполните требуемые policy attestations. Сохраните URL/ID заявки, версию `0.4.0`, дату и подтверждённый Review status. После одобрения отдельно выберите **Publish plugin**.
+4. Выберите draft → **Submit for review**, заполните требуемые policy attestations. Сохраните URL/ID заявки, версию `0.5.0`, дату и подтверждённый Review status. После одобрения отдельно выберите **Publish plugin**.
 
 | Поле skills-only пакета | Подготовленное значение |
 | --- | --- |
 | Package name | `telegram-dev-skill` |
 | Display name | `Telegram Dev Skill` |
-| Version | `0.4.0` |
+| Version | `0.5.0` |
 | Category | `Developer Tools` |
 | Subtitle | `Telegram development knowledge` |
 | Русский subtitle | `Знания для разработки Telegram` |

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/docs/validation.md

@@ -1,5 +1,15 @@
 # Проверки / Validation
 
+## 0.5.0 — 2026-11-10 (Linux)
+
+| Check | Result |
+| --- | --- |
+| Repository tests | **55 passed**, including TON URL boundaries, Markdown fetching via the `llms.txt` twins, TEP link resolution and the `ton` / `ton-releases` areas |
+| TON crawl | Starting from the TON sources, 463 TON pages and 3 TON release pages were indexed. Three TON links failed because docs.ton.org itself returns 404 (`/languages/fift`, `/tvm`) or redirects off-site (`/contracts/acton`) |
+| TON search | Exact hits for TON Connect transactions, jetton transfers, Gram, Tolk structs, `ton_proof`, WalletTg and the Russian query «кошелек»; Telegram's Blockchain Guidelines rank next to TON Connect |
+| Source monitor | `scripts/check_sources.py` fetched all five new TON sources |
+| Real agent run | Codex CLI 0.167.0 with the 0.5.0 wheel installed: asked to sell a Mini App skin for 2 TON, it read the Stars and TON Connect pages over MCP and answered that digital goods must use Stars (`XTR`), with TON Connect only for permitted wallet features. This run is the second README example |
+
 ## 0.4.0 — 2026-11-10 (Linux)
 
 | Check | Result |

telegram_dev-0.5.1/glama.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://glama.ai/mcp/schemas/server.json",
+  "maintainers": ["Kay0k1"]
+}

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/pyproject.toml

@@ -4,10 +4,10 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "telegram-dev"
-version = "0.4.0"
+version = "0.5.1"
 description = "Source-grounded Telegram development skills and documentation MCP"
 readme = "README.md"
-requires-python = ">=3.10"
+requires-python = ">=3.10,<3.15"
 license = "MIT"
 dependencies = ["mcp>=1.30,<2", "httpx>=0.28,<1", "beautifulsoup4>=4.13,<5", "markdownify>=1,<2", "platformdirs>=4,<5", "tomlkit>=0.13,<1"]
 

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/server.json

@@ -2,18 +2,18 @@
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.Kay0k1/telegram-dev",
   "title": "Telegram Dev",
-  "description": "Search current official Telegram docs: Bot API, Mini Apps, MTProto, TDLib and changelogs",
+  "description": "Current official Telegram and TON docs: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk",
   "repository": {
     "url": "https://github.com/Kay0k1/telegram-dev",
     "source": "github"
   },
   "websiteUrl": "https://github.com/Kay0k1/telegram-dev",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "telegram-dev",
-      "version": "0.4.0",
+      "version": "0.5.1",
       "runtimeHint": "uvx",
       "transport": {
         "type": "stdio"

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/skills/telegram-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: telegram-dev
-description: Build, debug, migrate, and explain Telegram integrations using current official documentation and release history. Use for bots, Mini Apps, TDLib/MTProto clients, messaging and media, community administration, business, payments, account features, and Telegram web integrations. Does not itself access accounts or execute Telegram actions.
+description: Build, debug, migrate, and explain Telegram and TON integrations using current official documentation and release history. Use for bots, Mini Apps, TDLib/MTProto clients, messaging and media, community administration, business, payments, account features, Telegram web integrations, and TON wallets, TON Connect, jettons, NFTs and smart contracts. Does not itself access accounts or execute Telegram actions.
 ---
 
 # Telegram development
@@ -32,6 +32,7 @@ Read only the guide relevant to the requested behavior:
 | Business connections, Stars, invoices, subscriptions, gifts, stories | [Business and commerce](references/business-and-commerce.md) |
 | Mini Apps, website/mobile login, links, Gateway, Passport | [Mini Apps and web authentication](references/mini-apps-and-web.md) |
 | TDLib/MTProto clients, account auth, calls, secret chats, updates, export | [Client development](references/client-development.md) |
+| TON: wallets, TON Connect, crypto payments, jettons, NFTs, smart contracts (Tolk), blockchain features in Mini Apps | [TON and blockchain](references/ton-and-blockchain.md) |
 
 For an unfamiliar feature, browse the current API index and follow its related article, method, constructors and changelog. The routing table is intentionally open-ended: newly added features need evidence, not a new handwritten skill release before the agent can use them.
 

{telegram_dev-0.4.0 → telegram_dev-0.5.1}/skills/telegram-dev/references/surface-map.md

@@ -19,6 +19,7 @@
 | Passport | https://core.telegram.org/passport | Separate identity-document integration. |
 | Instant View | https://instantview.telegram.org/docs | Article templates; not Mini Apps. |
 | Themes | https://core.telegram.org/api/themes | Client themes; distinct from Mini App theme parameters. |
+| Blockchain in Mini Apps, wallets, crypto payments, tokens, smart contracts | https://core.telegram.org/bots/blockchain-guidelines ; https://docs.ton.org/llms.txt | Telegram's rules (TON only, TON Connect, Stars for digital goods) come before TON implementation docs. Read `ton-and-blockchain.md`. |
 
 ## Feature-family entrypoints