@zhin.js/adapter-telegram 1.1.0 → 1.1.3

package/commands/{endpoint/add/[id].js → telegram/endpoint/add/[id]/index.js}

@@ -1,3 +1,3 @@
 // Generated by build-plugin-runtime-entries.mjs. Do not edit.
-import { telegramEndpointCommands } from "../../../lib/telegram-endpoint-commands.js";
+import { telegramEndpointCommands } from '../../definition.js';
 export default telegramEndpointCommands.add;

package/commands/telegram/endpoint/add/[id]/index.ts

@@ -0,0 +1,3 @@
+import { telegramEndpointCommands } from '../../definition.js';
+
+export default telegramEndpointCommands.add;

package/{lib/telegram-endpoint-commands.js → commands/telegram/endpoint/definition.js}

@@ -1,10 +1,11 @@
+// Generated by build-plugin-runtime-entries.mjs. Do not edit.
 /**
- * `telegram.endpoint` 命令族：由 @zhin.js/adapter 的 createEndpointCommands 套件生成。
- * commands/endpoint/ 下的 list / add / remove 直接默认导出这三项。
+ * `telegram endpoint` 命令族：由 @zhin.js/adapter 的 createEndpointCommands 套件生成。
+ * commands/telegram/endpoint/ 下的 list / add / remove 直接默认导出这三项。
  */
 import { createEndpointCommands } from 'zhin.js/adapter';
 import { defineCommand } from 'zhin.js/command';
-import { telegramRuntimeStateToken } from './telegram-runtime-state.js';
+import { telegramRuntimeStateToken } from "../../../lib/telegram-runtime-state.js";
 export const telegramEndpointCommands = createEndpointCommands({
     adapterKey: 'telegram',
     adapterDisplayName: 'Telegram',

package/{src/telegram-endpoint-commands.ts → commands/telegram/endpoint/definition.ts}

@@ -1,10 +1,10 @@
 /**
- * `telegram.endpoint` 命令族：由 @zhin.js/adapter 的 createEndpointCommands 套件生成。
- * commands/endpoint/ 下的 list / add / remove 直接默认导出这三项。
+ * `telegram endpoint` 命令族：由 @zhin.js/adapter 的 createEndpointCommands 套件生成。
+ * commands/telegram/endpoint/ 下的 list / add / remove 直接默认导出这三项。
  */
 import { createEndpointCommands } from 'zhin.js/adapter';
 import { defineCommand } from 'zhin.js/command';
-import { telegramRuntimeStateToken } from './telegram-runtime-state.js';
+import { telegramRuntimeStateToken } from '../../../src/telegram-runtime-state.js';
 
 export const telegramEndpointCommands = createEndpointCommands({
   adapterKey: 'telegram',

package/commands/{endpoint/list.js → telegram/endpoint/list/index.js}

@@ -1,3 +1,3 @@
 // Generated by build-plugin-runtime-entries.mjs. Do not edit.
-import { telegramEndpointCommands } from "../../lib/telegram-endpoint-commands.js";
+import { telegramEndpointCommands } from '../definition.js';
 export default telegramEndpointCommands.list;

package/commands/telegram/endpoint/list/index.ts

@@ -0,0 +1,3 @@
+import { telegramEndpointCommands } from '../definition.js';
+
+export default telegramEndpointCommands.list;

package/commands/{endpoint/remove/[id].js → telegram/endpoint/remove/[id]/index.js}

@@ -1,3 +1,3 @@
 // Generated by build-plugin-runtime-entries.mjs. Do not edit.
-import { telegramEndpointCommands } from "../../../lib/telegram-endpoint-commands.js";
+import { telegramEndpointCommands } from '../../definition.js';
 export default telegramEndpointCommands.remove;

package/commands/telegram/endpoint/remove/[id]/index.ts

@@ -0,0 +1,3 @@
+import { telegramEndpointCommands } from '../../definition.js';
+
+export default telegramEndpointCommands.remove;

package/lib/index.d.ts

@@ -1,4 +1,4 @@
 export { TelegramClient, TelegramEndpoint, type TelegramClientApi, type TelegramEndpointOptions, type TelegramFetch, } from './endpoint.js';
-export { botApiUrl, formatCallbackContent, formatInboundContent, formatOutboundActions, formatOutboundPlan, normalizeWebhookPath, resolveTelegramConfig, senderDisplayName, type ResolvedTelegramConfig, type TelegramAdapterConfig, type TelegramCallbackQuery, type TelegramChat, type TelegramChatMember, type TelegramMessage, type TelegramOutboundAction, type TelegramOutboundPlan, type TelegramOutboundUpload, type TelegramUpdate, type TelegramUser, type TelegramWireSegment, } from './protocol.js';
+export { botApiUrl, formatCallbackContent, formatInboundContent, formatOutboundActions, formatOutboundPlan, normalizeWebhookPath, resolveTelegramConfig, senderDisplayName, type ResolvedTelegramConfig, type TelegramEndpointConfig, type TelegramCallbackQuery, type TelegramChat, type TelegramChatMember, type TelegramMessage, type TelegramOutboundAction, type TelegramOutboundPlan, type TelegramOutboundUpload, type TelegramUpdate, type TelegramUser, type TelegramWireSegment, } from './protocol.js';
 export { telegramClient, type TelegramClientEventMap } from './client.js';
 export { checkTelegramPlatformPermit, normalizeTelegramChatMember, platformPermit, telegramGroupPermitResolver, } from './platform-permit.js';

package/lib/protocol.d.ts

@@ -3,12 +3,12 @@
  * Canonicalization is owned by gateway/core before endpoint.send.
  */
 import type { IncomingMessage } from 'node:http';
+import { type ConversationKind, type ConversationRef } from '@zhin.js/im-contract';
 import type { Segment } from '@zhin.js/core/runtime';
-import type { ConversationKind, ConversationRef } from '@zhin.js/im-contract';
-/** Plugin Runtime owner config (`plugins.<instanceKey>` / schema.json). */
-export interface TelegramAdapterConfig {
-    readonly id?: string;
-    readonly token?: string;
+/** One endpoint config after AdapterIndex expands `plugins.<instanceKey>.endpoints`. */
+export interface TelegramEndpointConfig {
+    readonly id: string;
+    readonly token: string;
     /** Default true. `false` selects webhook mode (requires httpHostToken). */
     readonly polling?: boolean;
     readonly webhook?: {
@@ -18,14 +18,6 @@ export interface TelegramAdapterConfig {
     };
     readonly allowedUpdates?: readonly string[];
     readonly apiBaseUrl?: string;
-    /** Transitional: legacy root `endpoints[]` with `context: telegram`. */
-    readonly endpoints?: ReadonlyArray<Partial<ResolvedTelegramConfig> & {
-        readonly context?: string;
-        readonly polling?: boolean;
-        readonly webhook?: TelegramAdapterConfig['webhook'];
-        readonly allowedUpdates?: readonly string[];
-        readonly apiBaseUrl?: string;
-    }>;
 }
 export interface ResolvedTelegramConfig {
     readonly context: 'telegram';
@@ -236,7 +228,7 @@ export type TelegramOutboundAction = {
         };
     };
 };
-export declare function resolveTelegramConfig(config?: TelegramAdapterConfig): ResolvedTelegramConfig;
+export declare function resolveTelegramConfig(config: TelegramEndpointConfig): ResolvedTelegramConfig;
 export declare function normalizeWebhookPath(path: string): string;
 export declare function buildWebhookUrl(webhook: NonNullable<ResolvedTelegramConfig['webhook']>): string;
 export declare function readTextBody(request: IncomingMessage, options?: {

package/lib/protocol.js

@@ -2,40 +2,23 @@
  * Telegram Bot API protocol helpers — no legacy Adapter/Endpoint / segment-mapper.
  * Canonicalization is owned by gateway/core before endpoint.send.
  */
-import { isMediaRef } from '@zhin.js/core';
+import { isMediaRef } from '@zhin.js/im-contract';
 import { formatCompact, getLogger } from '@zhin.js/logger';
 import { escapeTelegramHtml, markdownToTelegramHtml } from './markdown-to-html.js';
 const logger = getLogger('telegram');
-export function resolveTelegramConfig(config = {}) {
-    const entry = config.endpoints?.find((item) => item.context === 'telegram');
-    const token = config.token
-        ?? entry?.token
-        ?? process.env.TELEGRAM_TOKEN
-        ?? process.env.TELEGRAM_BOT_TOKEN;
-    if (!token) {
-        throw new TypeError('Telegram adapter requires token (plugins.<key>.token or endpoints with context: telegram)');
-    }
-    const id = (typeof config.id === 'string' && config.id)
-        || (typeof entry?.id === 'string' && entry.id)
-        || process.env.TELEGRAM_BOT_NAME
-        || 'telegram-bot';
-    const polling = config.polling ?? entry?.polling;
-    const webhookSource = config.webhook ?? entry?.webhook;
-    // Match legacy: polling defaults true; webhook only when polling === false.
+export function resolveTelegramConfig(config) {
+    const id = requiredEndpointField(config.id, 'id');
+    const token = requiredEndpointField(config.token, 'token');
+    const polling = config.polling;
+    const webhookSource = config.webhook;
     const mode = polling === false ? 'webhook' : 'polling';
-    const apiBaseUrl = (config.apiBaseUrl
-        ?? entry?.apiBaseUrl
-        ?? 'https://api.telegram.org').replace(/\/$/, '');
-    const allowedUpdates = config.allowedUpdates
-        ?? entry?.allowedUpdates
-        ?? ['message', 'callback_query'];
+    const apiBaseUrl = (config.apiBaseUrl ?? 'https://api.telegram.org').replace(/\/$/, '');
+    const allowedUpdates = config.allowedUpdates ?? ['message', 'callback_query'];
     const webhook = mode === 'webhook'
         ? {
             domain: webhookSource?.domain ?? '',
             path: normalizeWebhookPath(webhookSource?.path ?? '/telegram/webhook'),
-            secretToken: webhookSource?.secretToken
-                ?? process.env.TELEGRAM_WEBHOOK_SECRET
-                ?? undefined,
+            secretToken: webhookSource?.secretToken,
         }
         : undefined;
     return {
@@ -48,6 +31,12 @@ export function resolveTelegramConfig(config = {}) {
         webhook,
     };
 }
+function requiredEndpointField(value, field) {
+    if (typeof value !== 'string' || !value.trim()) {
+        throw new TypeError(`Telegram endpoint requires a non-empty ${field}`);
+    }
+    return value.trim();
+}
 export function normalizeWebhookPath(path) {
     const trimmed = path.trim() || '/telegram/webhook';
     return trimmed.startsWith('/') ? trimmed : `/${trimmed}`;

package/lib/telegram-runtime-state.js

@@ -1,6 +1,6 @@
 /**
  * Telegram 插件实例的运行时状态：adapter create() 注册的 endpoint 列表。
- * 由 plugin.ts setup() provide，adapter create 与 `telegram.endpoint` 命令共享（同一 owner generation）。
+ * 由 plugin.ts setup() provide，adapter create 与 `telegram endpoint` 命令共享（同一 owner generation）。
  */
 import { defineEndpointRuntimeStateToken } from 'zhin.js/adapter';
 export const telegramRuntimeStateToken = defineEndpointRuntimeStateToken('telegram');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zhin.js/adapter-telegram",
-  "version": "1.1.0",
+  "version": "1.1.3",
   "description": "Zhin.js Telegram Bot API adapter for Plugin Runtime (long-poll getUpdates)",
   "type": "module",
   "main": "./lib/index.js",
@@ -32,26 +32,25 @@
     "directory": "plugins/adapters/telegram"
   },
   "dependencies": {
-    "@zhin.js/adapter": "1.1.12",
-    "@zhin.js/core": "1.1.35",
-    "@zhin.js/feature-kit": "1.1.0",
-    "@zhin.js/host-http": "1.1.0",
-    "@zhin.js/im-contract": "1.1.0",
-    "@zhin.js/logger": "1.1.0"
+    "@zhin.js/adapter": "1.1.15",
+    "@zhin.js/agent-feature": "1.1.2",
+    "@zhin.js/core": "1.1.38",
+    "@zhin.js/feature-kit": "1.1.2",
+    "@zhin.js/host-http": "1.1.2",
+    "@zhin.js/im-contract": "1.1.2",
+    "@zhin.js/logger": "1.1.1",
+    "@zhin.js/skill": "1.1.2",
+    "@zhin.js/tool": "1.1.2"
   },
   "peerDependencies": {
     "zod": "^4.0.0",
-    "@zhin.js/adapter": "^1.1.12",
-    "@zhin.js/agent": "^1.1.23",
-    "@zhin.js/command": "^1.1.0",
-    "@zhin.js/core": "^1.1.35",
-    "@zhin.js/permission": "^1.1.0",
-    "zhin.js": "^1.1.0"
+    "@zhin.js/adapter": "^1.1.15",
+    "@zhin.js/command": "^1.1.2",
+    "@zhin.js/core": "^1.1.38",
+    "@zhin.js/permission": "^1.1.2",
+    "zhin.js": "^1.1.3"
   },
   "peerDependenciesMeta": {
-    "@zhin.js/agent": {
-      "optional": true
-    },
     "@zhin.js/command": {
       "optional": true
     },
@@ -67,9 +66,8 @@
     "typescript": "^6.0.3",
     "vitest": "^4.1.10",
     "zod": "^4.4.3",
-    "@zhin.js/agent": "1.1.23",
-    "@zhin.js/host-http": "1.1.0",
-    "zhin.js": "1.1.0"
+    "@zhin.js/host-http": "1.1.2",
+    "zhin.js": "1.1.3"
   },
   "files": [
     "adapters",
@@ -78,9 +76,11 @@
     "schema.json",
     "src",
     "lib",
-    "agent",
+    "tools",
+    "agents",
     "README.md",
-    "CHANGELOG.md"
+    "CHANGELOG.md",
+    "PERMITS.md"
   ],
   "publishConfig": {
     "access": "public",
@@ -103,6 +103,18 @@
       {
         "package": "@zhin.js/command",
         "api": "^1.0.0"
+      },
+      {
+        "package": "@zhin.js/tool",
+        "api": "^1.0.0"
+      },
+      {
+        "package": "@zhin.js/skill",
+        "api": "^1.0.0"
+      },
+      {
+        "package": "@zhin.js/agent-feature",
+        "api": "^1.0.0"
       }
     ],
     "plugins": []

package/schema.json

@@ -60,10 +60,11 @@
     },
     "endpoints": {
       "type": "array",
+      "minItems": 1,
       "description": "多账号：一个插件实例挂多个 endpoint。每项与顶层字段同构（id 必填，其余覆盖顶层）",
       "items": {
         "type": "object",
-        "additionalProperties": true,
+        "additionalProperties": false,
         "properties": {
           "master": {
             "type": [
@@ -87,6 +88,36 @@
             "type": "string",
             "description": "Telegram bot token"
           },
+          "polling": {
+            "type": "boolean"
+          },
+          "webhook": {
+            "type": "object",
+            "additionalProperties": false,
+            "properties": {
+              "domain": {
+                "type": "string"
+              },
+              "path": {
+                "type": "string"
+              },
+              "secretToken": {
+                "type": "string"
+              }
+            }
+          },
+          "allowedUpdates": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "apiBaseUrl": {
+            "type": "string"
+          },
+          "commandPrefix": {
+            "type": "string"
+          },
           "id": {
             "type": "string",
             "description": "Telegram bot name"

package/src/index.ts

@@ -16,7 +16,7 @@ export {
   resolveTelegramConfig,
   senderDisplayName,
   type ResolvedTelegramConfig,
-  type TelegramAdapterConfig,
+  type TelegramEndpointConfig,
   type TelegramCallbackQuery,
   type TelegramChat,
   type TelegramChatMember,

package/src/protocol.ts

@@ -4,18 +4,17 @@
  */
 
 import type { IncomingMessage } from 'node:http';
-import { isMediaRef } from '@zhin.js/core';
+import { isMediaRef, type ConversationKind, type ConversationRef } from '@zhin.js/im-contract';
 import type { Segment } from '@zhin.js/core/runtime';
-import type { ConversationKind, ConversationRef } from '@zhin.js/im-contract';
 import { formatCompact, getLogger } from '@zhin.js/logger';
 import { escapeTelegramHtml, markdownToTelegramHtml } from './markdown-to-html.js';
 
 const logger = getLogger('telegram');
 
-/** Plugin Runtime owner config (`plugins.<instanceKey>` / schema.json). */
-export interface TelegramAdapterConfig {
-  readonly id?: string;
-  readonly token?: string;
+/** One endpoint config after AdapterIndex expands `plugins.<instanceKey>.endpoints`. */
+export interface TelegramEndpointConfig {
+  readonly id: string;
+  readonly token: string;
   /** Default true. `false` selects webhook mode (requires httpHostToken). */
   readonly polling?: boolean;
   readonly webhook?: {
@@ -25,14 +24,6 @@ export interface TelegramAdapterConfig {
   };
   readonly allowedUpdates?: readonly string[];
   readonly apiBaseUrl?: string;
-  /** Transitional: legacy root `endpoints[]` with `context: telegram`. */
-  readonly endpoints?: ReadonlyArray<Partial<ResolvedTelegramConfig> & {
-    readonly context?: string;
-    readonly polling?: boolean;
-    readonly webhook?: TelegramAdapterConfig['webhook'];
-    readonly allowedUpdates?: readonly string[];
-    readonly apiBaseUrl?: string;
-  }>;
 }
 
 export interface ResolvedTelegramConfig {
@@ -246,40 +237,19 @@ export type TelegramOutboundAction =
     };
   };
 
-export function resolveTelegramConfig(config: TelegramAdapterConfig = {}): ResolvedTelegramConfig {
-  const entry = config.endpoints?.find((item) => item.context === 'telegram');
-  const token = config.token
-    ?? entry?.token
-    ?? process.env.TELEGRAM_TOKEN
-    ?? process.env.TELEGRAM_BOT_TOKEN;
-  if (!token) {
-    throw new TypeError(
-      'Telegram adapter requires token (plugins.<key>.token or endpoints with context: telegram)',
-    );
-  }
-  const id = (typeof config.id === 'string' && config.id)
-    || (typeof entry?.id === 'string' && entry.id)
-    || process.env.TELEGRAM_BOT_NAME
-    || 'telegram-bot';
-  const polling = config.polling ?? entry?.polling;
-  const webhookSource = config.webhook ?? entry?.webhook;
-  // Match legacy: polling defaults true; webhook only when polling === false.
+export function resolveTelegramConfig(config: TelegramEndpointConfig): ResolvedTelegramConfig {
+  const id = requiredEndpointField(config.id, 'id');
+  const token = requiredEndpointField(config.token, 'token');
+  const polling = config.polling;
+  const webhookSource = config.webhook;
   const mode: 'polling' | 'webhook' = polling === false ? 'webhook' : 'polling';
-  const apiBaseUrl = (
-    config.apiBaseUrl
-    ?? entry?.apiBaseUrl
-    ?? 'https://api.telegram.org'
-  ).replace(/\/$/, '');
-  const allowedUpdates = config.allowedUpdates
-    ?? entry?.allowedUpdates
-    ?? ['message', 'callback_query'];
+  const apiBaseUrl = (config.apiBaseUrl ?? 'https://api.telegram.org').replace(/\/$/, '');
+  const allowedUpdates = config.allowedUpdates ?? ['message', 'callback_query'];
   const webhook = mode === 'webhook'
     ? {
       domain: webhookSource?.domain ?? '',
       path: normalizeWebhookPath(webhookSource?.path ?? '/telegram/webhook'),
-      secretToken: webhookSource?.secretToken
-        ?? process.env.TELEGRAM_WEBHOOK_SECRET
-        ?? undefined,
+      secretToken: webhookSource?.secretToken,
     }
     : undefined;
   return {
@@ -293,6 +263,13 @@ export function resolveTelegramConfig(config: TelegramAdapterConfig = {}): Resol
   };
 }
 
+function requiredEndpointField(value: unknown, field: 'id' | 'token'): string {
+  if (typeof value !== 'string' || !value.trim()) {
+    throw new TypeError(`Telegram endpoint requires a non-empty ${field}`);
+  }
+  return value.trim();
+}
+
 export function normalizeWebhookPath(path: string): string {
   const trimmed = path.trim() || '/telegram/webhook';
   return trimmed.startsWith('/') ? trimmed : `/${trimmed}`;

package/src/telegram-runtime-state.ts

@@ -1,6 +1,6 @@
 /**
  * Telegram 插件实例的运行时状态：adapter create() 注册的 endpoint 列表。
- * 由 plugin.ts setup() provide，adapter create 与 `telegram.endpoint` 命令共享（同一 owner generation）。
+ * 由 plugin.ts setup() provide，adapter create 与 `telegram endpoint` 命令共享（同一 owner generation）。
  */
 import { defineEndpointRuntimeStateToken } from 'zhin.js/adapter';
 

package/agent/skills/telegram.md

@@ -1,103 +0,0 @@
----
-name: telegram
-platforms:
-  - telegram
-description: >-
-  Telegram 群组全功能管理。当用户在 Telegram 群中请求群管（踢人、封禁、解封、禁言、
-  设管理员、改群名/描述）、消息管理（置顶/取消置顶）、社交互动（投票、表情反应、贴纸）、
-  或群权限设置时使用。即使用户没有提到 Telegram，只要上下文是 Telegram 群组场景
-  且涉及上述操作，就应触发。仅有用户名时必须先查成员列表获取 user_id。
-keywords:
-  - telegram
-  - tg
-  - adapter:telegram
-  - 群管理
-  - 置顶
-  - 投票
-  - 反应
-  - 贴纸
-  - 权限
-  - 封禁
-  - 禁言
-  - list_members
-tags:
-  - group
-  - management
-  - im
-tools:
-  - telegram_pin_message
-  - telegram_unpin_message
-  - telegram_list_admins
-  - telegram_member_count
-  - telegram_create_invite
-  - telegram_send_poll
-  - telegram_react
-  - telegram_send_sticker
-  - telegram_set_permissions
-  - telegram_set_description
-  - telegram_kick_member
-  - telegram_unban_member
-  - telegram_mute_member
-  - telegram_set_admin
-  - telegram_set_group_name
-  - telegram_get_group_info
----
-
-# Telegram 群组管理技能
-
-Telegram 的群组管理模型与 QQ 不同：没有「群名片」概念，有封禁（ban）/解封（unban）机制，权限体系更细粒度。
-
-## 核心原则
-
-### 先查后操作
-
-Telegram 的 user_id 是纯数字，用户通常只知道用户名（@xxx）。操作具体成员前，用 `telegram_list_admins` 或从消息上下文获取 user_id。
-
-### Telegram 权限模型
-
-Telegram 的权限不是简单的 owner/admin/member 三级，而是细粒度的权限集合。通过 `telegram_set_permissions` 可以控制：发消息、发媒体、发投票、添加成员、置顶消息等。
-
-## 工具分类
-
-### 群管基础
-
-| 工具 | 用途 | 说明 |
-|------|------|------|
-| `telegram_kick_member` | 踢出成员 | 踢出后用户仍可重新加入 |
-| `telegram_unban_member` | 解除封禁 | 被 ban 的用户无法加入群组 |
-| `telegram_mute_member` | 禁言 | duration 单位秒，**0=永久限制** |
-| `telegram_set_admin` | 设/取消管理员 | — |
-| `telegram_set_group_name` | 改群名 | — |
-| `telegram_set_description` | 设群描述 | — |
-| `telegram_set_permissions` | 设群权限 | 影响所有普通成员，管理员不受限 |
-| `telegram_get_group_info` | 群信息 | — |
-| `telegram_list_admins` | 管理员列表 | — |
-| `telegram_member_count` | 成员数量 | — |
-
-### 消息与社交
-
-| 工具 | 用途 | 说明 |
-|------|------|------|
-| `telegram_pin_message` | 置顶消息 | 需管理员权限 |
-| `telegram_unpin_message` | 取消置顶 | — |
-| `telegram_create_invite` | 创建邀请链接 | 需管理员权限 |
-| `telegram_send_poll` | 发起投票 | 支持匿名 + 多选 |
-| `telegram_react` | 表情反应 | 对消息贴 emoji |
-| `telegram_send_sticker` | 发贴纸 | — |
-
-## 与 QQ 群管的关键差异
-
-| 概念 | QQ（OneBot11） | Telegram |
-|------|---------------|----------|
-| 禁言 duration=0 | **解禁** | **永久限制** |
-| 踢出 | 踢出 = 移除 | 踢出 ≠ 封禁，可重新加入 |
-| 封禁 | 无独立概念 | `ban` 阻止加入 |
-| 群名片 | 支持 | 不支持 |
-| 群权限 | admin/member 二分 | 细粒度权限集 |
-
-## 易错点
-
-1. **禁言 duration=0 在 Telegram 是永久限制**，与 QQ 的「解禁」含义相反。
-2. **踢人不等于封禁**：`kick_member` 移除但不阻止重新加入；要永久禁止需要 ban。
-3. **投票支持匿名和多选**：用户说「发个投票」时确认是否需要匿名/多选。
-4. **权限设置影响全体普通成员**，不是针对个人。管理员不受影响。

package/commands/endpoint/add/[id].ts

@@ -1,3 +0,0 @@
-import { telegramEndpointCommands } from '../../../src/telegram-endpoint-commands.js';
-
-export default telegramEndpointCommands.add;

package/commands/endpoint/list.ts

@@ -1,3 +0,0 @@
-import { telegramEndpointCommands } from '../../src/telegram-endpoint-commands.js';
-
-export default telegramEndpointCommands.list;

package/commands/endpoint/remove/[id].ts

@@ -1,3 +0,0 @@
-import { telegramEndpointCommands } from '../../../src/telegram-endpoint-commands.js';
-
-export default telegramEndpointCommands.remove;

package/lib/telegram-endpoint-commands.d.ts

@@ -1 +0,0 @@
-export declare const telegramEndpointCommands: import("@zhin.js/adapter").EndpointCommands<Readonly<import("@zhin.js/command").CommandDefinition<unknown, unknown, import("@zhin.js/command").CommandMessage, string | undefined>>>;