@capybara-hq/plugin-telegram 0.0.0-stage → 0.1.0-rc.1

package/.capybara-plugin/plugin.json

@@ -0,0 +1,63 @@
+{
+  "schemaVersion": 1,
+  "name": "telegram",
+  "version": "0.1.0-rc.1",
+  "publisher": "Capybara",
+  "description": {
+    "en": "Telegram (channel@1 bot over the Bot API: long polling or webhook, inline keyboard cards)",
+    "zh": "Telegram 机器人渠道（channel@1，Bot API：长轮询或 webhook，内联键盘卡片）"
+  },
+  "displayName": {
+    "zh": "Telegram",
+    "en": "Telegram"
+  },
+  "icon": "./icon.svg",
+  "homepage": "https://github.com/capybara-hq/plugins/tree/main/plugins/telegram#readme",
+  "extension": {
+    "entry": "./dist/index.mjs",
+    "manifest": {
+      "name": "telegram",
+      "version": "0.1.0-rc.1",
+      "sdk": "^0.1.0-rc.4",
+      "provides": [
+        "channel@1"
+      ],
+      "requires": [],
+      "optional": [],
+      "permissions": {
+        "network": [
+          "api.telegram.org"
+        ]
+      },
+      "config": {
+        "deployment": [
+          {
+            "path": "apiUrl",
+            "secret": false,
+            "hot": false
+          }
+        ],
+        "org": []
+      }
+    },
+    "configSchemas": {
+      "deployment": {
+        "type": "object",
+        "properties": {
+          "apiUrl": {
+            "default": "https://api.telegram.org",
+            "type": "string",
+            "format": "uri",
+            "x-ui": {
+              "label": {
+                "zh": "API 地址",
+                "en": "API URL"
+              }
+            },
+            "title": "API URL"
+          }
+        }
+      }
+    }
+  }
+}

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.

package/NOTICE

@@ -0,0 +1,2 @@
+Capybara
+Copyright 2026 Meta-1 (Tianjin Yuanyilian Technology Co., Ltd.)

package/README.md

@@ -1,3 +1,181 @@
-# Temporary Holding Version
+# @capybara-hq/plugin-telegram
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The official Telegram plugin. It provides one capability:
+
+- `channel@1` (bot): talk to Capybara agents in a private chat with a Telegram bot, or by mentioning the bot in a group.
+  Messages arrive by long polling (`getUpdates`, the default, no public URL needed) or by webhook (optional),
+  replies are sent with `sendMessage` and streamed by editing, and approval / question / connection / binding
+  cards are rendered as inline keyboards.
+
+It does not provide login (`identity-source@1`) or a directory (`directory@1`); see [Out of scope](#out-of-scope).
+
+Identity: `identities.source` = `telegram:global`, `external_id` = the Telegram user id (decimal). Telegram user ids are
+global (one person has the same id for every bot), so one person is one identity across every Telegram bot of a deployment.
+
+The Telegram docs cited here are the [Bot API reference](https://core.telegram.org/bots/api) (Bot API 10.3), consulted on 2026-11-08.
+
+Verified live on 2026-11-08 against a real bot: verify, send, edit, a 5000-character split send and a card with an inline callback keyboard, in a private chat and in a basic group. Not covered live: a person clicking a card button, webhook mode and forum supergroups.
+
+## Create the bot
+
+1. In Telegram, open [@BotFather](https://t.me/BotFather) and send `/newbot`. Pick a display name and a username
+   (it must end in `bot`). BotFather replies with the bot token, such as `123456:ABC-DEF…`
+   ([Bot API: authorizing your bot](https://core.telegram.org/bots/api#authorizing-your-bot)). Treat it like a password.
+2. **Privacy mode** (`/setprivacy`): leave it **enabled** (the default). With it on, a bot in a group receives only
+   commands, mentions of the bot and replies to the bot's own messages, which is exactly what this plugin forwards
+   ([Bot API: `getMe`, `can_read_all_group_messages`](https://core.telegram.org/bots/api#getme)).
+   If you turn it off the bot receives every group message; the plugin still forwards only mentions and replies to
+   the bot, and `verify` logs a warning. Telegram applies a privacy change to a group only after the bot is removed from the group and added again.
+3. **Groups** (`/setjoingroups`): enable it if people should add the bot to groups, disable it for a private-only bot.
+4. **Topics in private chats**: leave the bot's topic mode off. It is not supported (see [Behavior](#behavior)); `verify` warns when it is on.
+5. In the Capybara org settings, enable the `telegram` plugin, then **create a new channel connection** under Channels:
+   pick Telegram as the plugin, fill in the bot token (`botToken`) and bind an agent. The token is stored in the secret
+   store and the API only returns "set".
+6. In Telegram, open the bot and press **Start** (see [Binding](#binding)). The first message gets a binding card; open its link to confirm the binding on the web page.
+
+## Binding
+
+A person must bind their Telegram user to a Capybara account before the agent answers. The kernel sends the binding card
+in the private chat only.
+
+- **Press Start once.** A bot cannot message a user who never started it: Telegram answers 403 ("Forbidden: bot can't initiate conversation with a user"),
+  which the plugin maps to `target_gone`. So the first step for everyone is to open the bot and press **Start** (or send any message).
+- **Start is a message.** Pressing Start sends `/start`, and the plugin forwards it like any other text: that is what gives a new
+  user the binding card. A user who is already bound and presses Start again (for example after clearing the chat) sends `/start` to the agent.
+- **In a group**, an unbound person who mentions the bot gets a "bind in a private chat" reply instead of a card: open the bot, press Start, and bind there.
+- **The `anonymous` unbound policy has no effect on Telegram.** A Telegram bot is reachable by anyone who finds it, so
+  anonymous guests would let the whole internet use an org's agent and model budget (maintainer decision). Every Telegram user is *external*
+  to the connection: `verify` returns the tenant `bot<bot id>` while every inbound sender's tenant is `global`, and the kernel never lets an external sender be an anonymous guest.
+  A connection set to `anonymous` therefore gives an unbound person the binding reply, not an agent run.
+
+## Channel connection config
+
+Shown in the form with zh / en labels and help.
+
+| Field | Label | Description |
+|---|---|---|
+| `botToken` | Bot token / 机器人令牌 | `<bot id>:<secret>` from @BotFather (secret) |
+| `webhookSecret` | Webhook secret / Webhook 密钥 | Secret, 1-256 characters of `A-Z a-z 0-9 _ -`; only needed in [webhook mode](#webhook-mode-optional) (the `secret_token` you give `setWebhook`), leave empty for long polling |
+
+## Deployment-level config
+
+| Field | Default | Description |
+|---|---|---|
+| `apiUrl` | `https://api.telegram.org` | Bot API root URL; change it only in tests or when going through a reverse proxy |
+
+The deployment-level config lives under the kernel config `extensionConfig.telegram`. There is no org-level config.
+
+## Behavior
+
+- **Private chats**: every text message goes to the kernel (`chatType: "dm"`, one conversation per user). Topic mode in
+  private chats (`has_topics_enabled`) is **not supported**: the kernel keys a private chat as one thread per user. `verify` warns when it is on; keep it off.
+- **Groups and supergroups**: only messages that mention the bot (`@<username>`, a text mention, or a command addressed to the bot such as `/cmd@botname`)
+  and replies to one of the bot's messages (a reply to the bot counts as a mention, since people address a bot by replying to it). Other group messages are dropped.
+- **Threads**: each mention that is not a reply starts its own conversation, and replies continue it. Telegram replies only point to their direct parent,
+  so the plugin records the thread of every message it sends into a group and of every inbound group message it forwards (kv, 30 days). A reply to a bot message older than that, or to an unknown message, starts a new conversation.
+  Replies are sent as replies to the thread's root message.
+- **Forum supergroups behave like groups.** A forum topic is only where the messages live, never the conversation key (otherwise a topic would become one ever-growing conversation):
+  each mention starts a conversation and replies continue it. The plugin remembers the topic (`message_thread_id`, kv, 30 days) so replies land in the right topic. `/new` works only in private chats.
+- **Ignored**: edited messages, channel posts, messages from bots, service messages (a group becoming a supergroup is logged; the old conversations in it then stop receiving replies), messages without text or caption.
+  A caption on media is taken as the text; the media itself is ignored.
+- **Text**: the bot mention is removed, a leading `/` is kept exactly where the person typed it (`/cmd@botname` becomes `/cmd`; commands are the kernel's), and mentions of other people become readable `@name`.
+  The speaker's display name is first + last name from the update itself; there is no avatar (getting one needs two more calls and exposes a file URL that carries the token).
+- **ids**: message id = `<chat id>:<message id>` (the chat id may be negative); the card-click `eventId` = the `callback_query.id`.
+  Messages with `message_id` 0 (ephemeral or scheduled) send no event: they have no stable id.
+- **Format**: the model reply's Markdown is converted to Telegram HTML (`parse_mode: "HTML"`); everything else is escaped.
+  Link previews are off. Links are limited to http(s): `tg://` and other schemes stay plain text, so model text cannot produce `tg://user?id=…` mentions.
+  A raw `@username` in model text would notify people, so the converter puts a U+2060 WORD JOINER after the `@` outside code and links, and Telegram no longer parses it as a mention.
+- **Limit and splitting**: one message holds at most 4096 characters after entity parsing
+  ([`sendMessage`, `text`](https://core.telegram.org/bots/api#sendmessage)); longer text is split into several messages and the last id is returned.
+  An edit that would need several messages reports `too_large` and the kernel sends a new message instead.
+- **Streaming edits**: replies are sent and then edited ([`editMessageText`](https://core.telegram.org/bots/api#editmessagetext)); `minEditIntervalMs = 3000`.
+  Telegram's limit for a group is about 20 messages per minute ([Broadcasting to users, FAQ](https://core.telegram.org/bots/faq))
+  and edits count; a 429 is honored through `retry_after`. "message is not modified" on an edit counts as success.
+  [`sendMessageDraft`](https://core.telegram.org/bots/api#sendmessagedraft) is not used: it exists only in private chats, is a 30-second preview that must be followed by a real
+  `sendMessage`, and does not fit the kernel's send-then-edit model.
+- **Idempotency**: the Bot API has no idempotent send, so `idempotencyKey` is ignored. A send whose response is lost and is retried can show the message twice; the alternative (never retrying) would lose messages.
+- **Permission manifest**: `network: ["api.telegram.org"]`, shown only and not enforced.
+
+## Cards
+
+Approval, question, connection and binding cards are the message text plus an **inline keyboard** ([`InlineKeyboardMarkup`](https://core.telegram.org/bots/api#inlinekeyboardmarkup)),
+with button labels in the org's language. Link buttons are used only for http(s) URLs.
+
+- **One message per card.** The kernel sends a card with a short line of text ("Your input is needed") and later updates it the same way, so
+  the text leads the card's own message (left out when it repeats the card's title) and the update edits that one message. A card message is
+  never split: over 4096 characters the text is cut first, then the card, each ending in "…". Text without a card is split as described above.
+- **Rejected link buttons.** Telegram refuses some link-button URLs that work as links in text, such as `http://localhost:3000/...`
+  ("Wrong HTTP URL"; `127.0.0.1` and LAN addresses are accepted). When a send or edit is refused for that reason, the plugin sends it once more
+  without link buttons and puts the link into the card text; callback buttons stay.
+
+- `callback_data` is limited to 64 bytes ([`InlineKeyboardButton`](https://core.telegram.org/bots/api#inlinekeyboardbutton)), too small for a card id, action, scope and answer.
+  Each button carries `cb:` plus a random 16-character token; the payload lives in kv for **30 days**, and any replica can decode it. A click whose token is missing, expired or malformed is answered and ignored.
+  After 30 days a card's buttons stop working; use the card's "open on web" link.
+- A question card with a single single-choice field of at most 5 options shows one button per option. Any other question (several fields, a multi-select field, a field that allows "other", a non-enum field, or more than 5 options) is answered on the web: its card carries only the link.
+- A decided or expired card is edited to its new state without its action buttons; only the "Open on web" link button stays.
+- Every click is answered with `answerCallbackQuery` (no text) so the client's progress indicator stops. In long polling this happens after the kernel accepted the click.
+
+## Errors
+
+| Telegram | `ChannelSendError` |
+|---|---|
+| 429 | retryable, waits `retry_after` |
+| 5xx, network error, timeout | retryable |
+| 401 Unauthorized | `auth` (not retryable) |
+| 403 (bot blocked, kicked, can't initiate conversation) | `target_gone` |
+| 400 chat not found, or the group migrated to a supergroup | `target_gone` |
+| 400 message too long | `too_large` |
+| other 400 | `rejected` |
+
+The Bot API puts the token in the URL path (`/bot<token>/<method>`), so error messages and logs carry only the method, Telegram's `error_code` and its short description, never the URL.
+
+## Long polling (default)
+
+`connect` calls `getUpdates` in a loop (25-second long poll, `allowed_updates=["message","callback_query"]`), held by one `gateway` replica per connection.
+
+- The offset is confirmed only **after the kernel accepted** the update (`onEvent` resolved, or the update was ignored). If `onEvent` rejects, the loop backs off and fetches the same update again; Telegram keeps updates for 24 hours.
+  The confirmed offset is also kept in kv (7 days), so the replica that takes over after a failover resumes where the last one stopped (a repeat is safe: the kernel dedupes by message id).
+- `connect` never changes webhook state behind your back. If a webhook is set for the bot, it fails with "A webhook is set for this Telegram bot; switch the connection to webhook mode or call deleteWebhook"
+  (check with [`getWebhookInfo`](https://core.telegram.org/bots/api#getwebhookinfo)).
+- **409 Conflict** means another client is polling the same bot (another deployment, a script, a second connection with the same token). The connection fails with "another client is polling this bot" and the kernel records `last_error`. A 401 fails with "bot token rejected".
+- Network errors back off exponentially with jitter (cap 30 seconds); 5 failures in a row end `connect` with an error, and the kernel records `last_error` and takes over.
+
+## Webhook mode (optional)
+
+A connection can instead receive updates over HTTPS, when the deployment exposes a gateway replica and sets `channels.webhookBaseUrl` (see
+[Deploying: webhook](https://github.com/capybara-hq/core/blob/main/docs/deploy/README.md#webhook-optional)). Switch the connection to webhook mode in the web app
+(Channels → connection → Overview → Inbound mode); the connection page then shows its webhook URL. The plugin never calls `setWebhook` itself; you do, once:
+
+1. Choose a secret (1-256 characters of `A-Z a-z 0-9 _ -`) and put it into the connection's `webhookSecret`. Every request is checked against it
+   (the `X-Telegram-Bot-Api-Secret-Token` header, compared in constant time); without it every webhook request is refused with 401.
+2. Register the webhook ([`setWebhook`](https://core.telegram.org/bots/api#setwebhook)), with the `url` from the connection page:
+
+   ```bash
+   curl "https://api.telegram.org/bot<botToken>/setWebhook" \
+     --data-urlencode "url=<webhook URL from the connection page>" \
+     --data-urlencode "secret_token=<webhookSecret>" \
+     --data-urlencode 'allowed_updates=["message","callback_query"]'
+   ```
+
+3. To go back to long polling, call [`deleteWebhook`](https://core.telegram.org/bots/api#deletewebhook) (long polling refuses to start while a webhook is set) and switch the connection back to long polling.
+
+Both modes parse updates the same way (same message and click ids), so the kernel's dedupe drops a redelivery that arrives across a mode switch. The kernel acks (200) only after it accepted the update; a non-2xx makes Telegram retry.
+
+Trade-off: the webhook contract gives the plugin no hook after the kernel accepted the update, so a card click is answered with `answerCallbackQuery` **before** the event is handed over.
+If the kernel then answers non-2xx and Telegram redelivers, the spinner has already stopped; the click itself is not lost and the redelivery is deduped.
+
+## Out of scope
+
+- **Login (`identity-source@1`)**: Telegram login gives no email and its widget does not fit the kernel's redirect / callback flow; binding through the bot already links a Telegram user to an account (maintainer decision).
+- **Directory (`directory@1`)**: the Bot API cannot list group members and Telegram has no organization concept (maintainer decision).
+- **Media**: attachments, voice, stickers, polls, inline mode, business accounts and broadcast channels are not handled; media without a caption sends no event.
+- **Proxy**: no proxy support for networks where `api.telegram.org` is unreachable (maintainer decision); `apiUrl` can point at a reverse proxy you run.
+
+## Icon
+
+`icon.svg`: the Telegram logo (owner: Telegram), downloaded on 2026-11-09 from
+https://telegram.org/tour/screenshots ("Download Telegram Logos", file `Logo.svg`). Telegram lets
+its logos be used as long as people understand you're not representing Telegram officially. It is a
+trademark of its owner, used only to identify the service this plugin connects to; the plugin is
+not affiliated with or endorsed by the owner. The artwork is unchanged except for removing editor
+metadata.