@zhin.js/adapter-telegram 1.1.17 → 1.1.19

package/CHANGELOG.md

@@ -1,5 +1,70 @@
 # Changelog
 
+## 1.1.19
+
+### Patch Changes
+
+- 2c3610a: Move account lifecycle ownership into the generic Adapter base and let native Endpoints retain their SDK Client inheritance. Infer platform-specific operation Sessions from a single adapter registry while preserving command parameter, option, configuration and factory inference.
+
+  Bind message replies, management ports, login challenges and Agent cancellation to the captured account incarnation. Persist runtime account intent with encrypted, revision-checked Host storage; keep account management independent of Root process restarts. Require explicit operator confirmation before importing existing accounts, and give replacement accounts a new identity without inheriting previous Sessions.
+
+  Expose account save, start, stop, update and replacement through the existing adapter Console, with exact account ownership, truthful pending/unknown outcomes and no startup configuration or environment-file rewrites.
+
+  Complete the target migration across every adapter, the public authoring API, generators, examples and Console. This intentionally removes the old create factory, inheritable Endpoint/ClientEndpoint classes, Client descriptors and file-rewrite account management; plugin authors must use createAdapter, native Client inheritance and the single AdapterRegistry. Satori and OneBot12 require explicit platform/userId selection, and WeCom requires a separate agentId.
+
+  Verify opaque credential changes before the same configuration snapshot is committed. Drain admitted native callbacks across close/rollback, cancel target work on stop, and keep raw transport parsing, platform ACK timing and SDK native methods under their existing owners. Account metadata conceals credentials carried in URLs.
+
+- a9f4e48: PATCH COMPATIBILITY CUTOVER: this batch intentionally changes plugin APIs. The maintainer explicitly chose patch releases with declared version boundaries. Upgrade the complete tested dependency set; patch numbering does not promise compatibility with the removed interfaces.
+
+  The first planned floors are zhin.js 1.1.19, Core 1.1.54, Adapter 1.1.26, FeatureKit 1.1.10, Plugin Runtime 1.1.18, Runtime/Isolate 1.1.16 and Agent 1.1.45. Keep old-interface plugins with the earlier locked stack until they are migrated. Adapter's independent Feature API changes from 1.0.0 to 2.0.0; official consumers declare ^2.0.0. Existing Feature API admission rejects explicitly incompatible ranges; omitted API metadata keeps its existing behavior and does not certify compatibility. Runtime engine and patch-only release gates remain unchanged.
+
+  Use the native-Client Adapter target contract, canonical FeatureKit AdapterRegistry augmentation and named Endpoint control/management requests. Route message controls from canonical message/conversation refs; retain exact source authority and propagate caller/account/explicit-Root-stop cancellation. Replace removed Agent activity feedback exports with source-bound feedback. HMR pause/resume belongs to concrete plugin instances; plugins choose accepted-work policy without changing Controller commit/rollback authority. Cooperative worker/process control cancellation does not kill an isolate or reopen retired business admission.
+
+  Provide authenticated historical-data preview, exact selected binding, transactional application, authoritative inspection and explicit resumption, including active games. Preserve before-images and journals; never replay an unconfirmed effect, infer an account from an alias, or reuse historical permission grants. Owner V2 approvals remain inactive legacy data, while new writes use V3. Rollback requires matching software, lockfile and verified data; installing old code alone cannot read a new V3 approval file. Conflicting after-images are never overwritten.
+
+  See docs/plans/adapter-operation-version-boundaries.md and the Chinese/English upgrade guide for the complete version inventory, custom-plugin changes, acceptance and recovery sequence. These code and metadata changes do not authorize merging, publication, deployment, login, production migration or removal of installed workspace patches.
+
+- Updated dependencies [2c3610a]
+- Updated dependencies [a9f4e48]
+- Updated dependencies [f8505b0]
+- Updated dependencies [2c3610a]
+  - @zhin.js/adapter@1.1.26
+  - @zhin.js/feature-kit@1.1.10
+  - @zhin.js/core@1.1.54
+  - @zhin.js/host-http@1.1.12
+  - @zhin.js/client@1.1.22
+  - @zhin.js/page@1.1.11
+  - @zhin.js/agent-feature@1.1.11
+  - @zhin.js/skill@1.1.11
+  - @zhin.js/tool@1.1.13
+
+## 1.1.18
+
+### Patch Changes
+
+- 6345a38: feat(adapters): add per-adapter Console pages
+
+  Every platform adapter now ships a `pages/index` Console page backed by a shared
+  `createAdapterConsolePage` component and `createAdapterConsoleRpc` server helper:
+
+  - See running endpoints, test connectivity, and manage
+    `plugins.<adapter>.endpoints` (add/remove writes `.env` references) from the
+    Console instead of chat commands.
+  - Surface LoginAssist pending tasks (QR / slider / SMS / device) so ICQQ login no
+    longer requires the terminal.
+  - QQ moves its QR binding flow (`qq endpoint add`) into Console actions with
+    public/private selection.
+  - Pages are permission-gated by `<adapter>:read`; writes need `<adapter>:write`.
+
+- Updated dependencies [6345a38]
+- Updated dependencies [ff3efe7]
+- Updated dependencies [c58c589]
+  - @zhin.js/adapter@1.1.25
+  - @zhin.js/client@1.1.21
+  - @zhin.js/core@1.1.53
+  - @zhin.js/im-contract@1.1.9
+  - @zhin.js/tool@1.1.12
+
 ## 1.1.17
 
 ### Patch Changes

package/README.md

@@ -32,12 +32,13 @@ pnpm add @zhin.js/adapter-telegram
 ## Plugin Runtime
 
 - `@zhin.js/adapter` — 约定式 `adapters/telegram/index.ts`（`defineAdapter`）
-- `@zhin.js/core` — `Endpoint.emit(...)` 入站、`outboundMessageToken` 出站
+- `@zhin.js/core` — `endpoint[endpointSpec].events` 入站、`outboundMessageToken` 出站
 - `zhin.js` — `plugin.ts`（`definePlugin`）
 - 配置经插件 `schema.json` 落到顶层 `<instanceKey>`
 - **无需** `@zhin.js/host-http`（polling 路径）
 
-入站：`gateway.receive({ conversation, message, content, sender, metadata })`（`conversation` 为 ConversationRef，由 `telegramInboundConversation` 归一化）  
+入站：`endpoint[endpointSpec].events.emit('message.receive', { conversation, message, content, sender, metadata })`（`conversation` 为 ConversationRef，由 `telegramInboundConversation` 归一化）
+
 出站：`send({ conversation, payload })` → Telegram Bot API
 
 ### 平台权限（platform permit）
@@ -134,6 +135,22 @@ Webhook 接收确认不等于业务处理完成；需要幂等性的业务应自
 | Platform tools (10) | `tools/`（invite / pin / admins / sticker / poll 等） |
 | Skill doc | `agents/telegram/skills/telegram-chat-admin/SKILL.md`, `agents/telegram/skills/telegram-messages/SKILL.md` |
 
+## Console 页面
+
+启动后打开 Console 的「Telegram」页（地址 `/telegram`），可以：
+
+- 查看运行中的连接、点「测试连接」做连通性诊断；
+- 在账号库保存、修改、启动、停止、替换或删除该 Adapter 的账号；新增仅保存，不创建 SDK Client，需手动启动；
+- 如果适配器要求登录，页面会显示 LoginAssist 的扫码 / 滑块 / 设备确认待办；
+
+读取需要 `telegram:read`，写操作需要 `telegram:write`；管理员 full token 不受限。页面里的「添加 endpoint」等价于原来的 `telegram endpoint add`。
+
+首次修改启动配置里的既有账号前，管理员必须核对清单并确认一次迁移。原 canonical 身份与历史保留，完整账号配置加密进入 Host 数据库；此后账号管理只写数据库，不修改启动文件或 `.env`，不重启进程。没有持久化账号端口的环境可使用静态配置连接，动态写操作明确不可用。
+
+启停意图在进程重启后恢复。停止或删除会取消并关闭目标账号的在途操作，其他账号继续运行；删除保留历史。已启动账号的连接配置更新先关闭旧 incarnation，再仅重连该账号；平台身份变化按替换处理，分配新内部身份、保留旧历史，新账号不继承旧 Session、个人设置或启动意图。提交结果未知时先刷新核实，不自动重复 CAS 或平台操作。
+
+Telegram 的 token / apiBaseUrl 更新通过只读 `getMe` 核验真实 bot ID。核验失败或操作取消时不提交配置、不改正在运行的 Client；身份变化由统一 Adapter 账号替换流程保存为未启动的新身份。
+
 ## 故障排查
 
 | 现象 | 排查 |

package/adapters/telegram/index.js

@@ -3,10 +3,8 @@
  * Convention entry: discover `adapters/telegram/index.ts` → defineAdapter.
  */
 import { defineAdapter } from 'zhin.js/adapter';
-import { httpHostToken } from '@zhin.js/host-http';
-import { TelegramEndpoint } from "../../lib/endpoint.js";
-import { resolveTelegramConfig, } from "../../lib/protocol.js";
-import { telegramRuntimeStateToken } from "../../lib/telegram-runtime-state.js";
+import { TelegramAdapter } from "../../lib/adapter.js";
+import {} from "../../lib/protocol.js";
 export { TelegramEndpoint } from "../../lib/endpoint.js";
 export default defineAdapter({
     capabilities: ['inbound', 'outbound'],
@@ -18,17 +16,5 @@ export default defineAdapter({
         interactive: 'native',
         markdown: 'native',
     },
-    create(context) {
-        const config = resolveTelegramConfig(context.config);
-        // 注册到插件运行时状态（telegram endpoint list 的"运行中"数据源）
-        context.use(telegramRuntimeStateToken).endpoints.set(config.id, {
-            id: config.id,
-            mode: config.mode,
-        });
-        return new TelegramEndpoint({
-            id: context.id,
-            config,
-            http: config.mode === 'webhook' ? context.use(httpHostToken) : undefined,
-        });
-    },
+    createAdapter: context => new TelegramAdapter(context),
 });

package/adapters/telegram/index.ts

@@ -2,13 +2,10 @@
  * Convention entry: discover `adapters/telegram/index.ts` → defineAdapter.
  */
 import { defineAdapter } from 'zhin.js/adapter';
-import { httpHostToken } from '@zhin.js/host-http';
-import { TelegramEndpoint } from '../../src/endpoint.js';
+import { TelegramAdapter } from '../../src/adapter.js';
 import {
-  resolveTelegramConfig,
   type TelegramEndpointConfig,
 } from '../../src/protocol.js';
-import { telegramRuntimeStateToken } from '../../src/telegram-runtime-state.js';
 
 export { TelegramEndpoint } from '../../src/endpoint.js';
 export type { TelegramEndpointOptions, TelegramFetch } from '../../src/endpoint.js';
@@ -23,17 +20,5 @@ export default defineAdapter<TelegramEndpointConfig>({
     interactive: 'native',
     markdown: 'native',
   },
-  create(context) {
-    const config = resolveTelegramConfig(context.config);
-    // 注册到插件运行时状态（telegram endpoint list 的"运行中"数据源）
-    context.use(telegramRuntimeStateToken).endpoints.set(config.id, {
-      id: config.id,
-      mode: config.mode,
-    });
-    return new TelegramEndpoint({
-      id: context.id,
-      config,
-      http: config.mode === 'webhook' ? context.use(httpHostToken) : undefined,
-    });
-  },
+  createAdapter: context => new TelegramAdapter(context),
 });

package/agents/telegram/skills/telegram-messages/tools/send_poll/index.js

@@ -25,7 +25,8 @@ export default defineAgentTool({
         if (!Array.isArray(optList) || optList.length < 2) {
             return { success: false, message: t(context.locale, 'pollOptionCount') };
         }
-        const result = await endpoint.sendPoll(Number(chat_id), question, optList, is_anonymous ?? true, allows_multiple ?? false);
+        const result = await endpoint.sendPoll({ chatId: Number(chat_id), question, options: optList,
+            isAnonymous: is_anonymous ?? true, allowsMultipleAnswers: allows_multiple ?? false });
         return { success: true, message_id: result.message_id, message: t(context.locale, 'pollSent') };
     },
 });

package/agents/telegram/skills/telegram-messages/tools/send_poll/index.ts

@@ -24,10 +24,8 @@ export default defineAgentTool<{ chat_id: string; question: string; options: str
     if (!Array.isArray(optList) || optList.length < 2) {
       return { success: false, message: t(context.locale, 'pollOptionCount') };
     }
-    const result = await endpoint.sendPoll(
-      Number(chat_id), question, optList,
-      is_anonymous ?? true, allows_multiple ?? false,
-    );
+    const result = await endpoint.sendPoll({ chatId: Number(chat_id), question, options: optList,
+      isAnonymous: is_anonymous ?? true, allowsMultipleAnswers: allows_multiple ?? false });
     return { success: true, message_id: result.message_id, message: t(context.locale, 'pollSent') };
   },
 });

package/commands/telegram/endpoint/definition.js

@@ -5,13 +5,11 @@
  */
 import { createEndpointCommands } from 'zhin.js/adapter';
 import { defineCommand } from 'zhin.js/command';
-import { telegramRuntimeStateToken } from "../../../lib/telegram-runtime-state.js";
 export const telegramEndpointCommands = createEndpointCommands({
     adapterKey: 'telegram',
     adapterDisplayName: 'Telegram',
     fields: [
         { key: 'token', required: true, env: true, description: 'Telegram bot token' },
     ],
-    running: (use) => use(telegramRuntimeStateToken).endpoints.values(),
     describeEntry: (entry) => `token: ${String(entry.token)}`,
 }, defineCommand);

package/commands/telegram/endpoint/definition.ts

@@ -4,7 +4,6 @@
  */
 import { createEndpointCommands } from 'zhin.js/adapter';
 import { defineCommand } from 'zhin.js/command';
-import { telegramRuntimeStateToken } from '../../../src/telegram-runtime-state.js';
 
 export const telegramEndpointCommands = createEndpointCommands({
   adapterKey: 'telegram',
@@ -12,6 +11,5 @@ export const telegramEndpointCommands = createEndpointCommands({
   fields: [
     { key: 'token', required: true, env: true, description: 'Telegram bot token' },
   ],
-  running: (use) => use(telegramRuntimeStateToken).endpoints.values(),
   describeEntry: (entry) => `token: ${String(entry.token)}`,
 }, defineCommand);

package/lib/adapter.d.ts

@@ -0,0 +1,15 @@
+import { Adapter, type AdapterContext, type EndpointCreationContext } from 'zhin.js/adapter';
+import { TelegramEndpoint, type TelegramEndpointOptions } from './endpoint.js';
+import { type TelegramEndpointConfig } from './protocol.js';
+import type { TelegramClientEventMap } from './client.js';
+export declare class TelegramAdapter extends Adapter<TelegramEndpoint, TelegramEndpointConfig, TelegramClientEventMap> {
+    private readonly context;
+    private readonly transport;
+    constructor(context: AdapterContext<TelegramEndpointConfig>, transport?: Pick<TelegramEndpointOptions, 'fetch' | 'requestTimeoutMs'>);
+    get configurationIdentityFields(): readonly string[];
+    get configurationIdentityProbeFields(): readonly string[];
+    get configurationUpdateFields(): readonly string[];
+    protected validateConfiguration(config: TelegramEndpointConfig): void;
+    protected identifyConfiguration(input: TelegramEndpointConfig, signal: AbortSignal): Promise<string>;
+    protected createEndpoint(input: TelegramEndpointConfig, execution: EndpointCreationContext): TelegramEndpoint;
+}

package/lib/adapter.js

@@ -0,0 +1,33 @@
+import { Adapter } from 'zhin.js/adapter';
+import { httpHostToken } from '@zhin.js/host-http';
+import { TelegramEndpoint } from './endpoint.js';
+import { TelegramClient } from './telegram-client.js';
+import { resolveTelegramConfig } from './protocol.js';
+export class TelegramAdapter extends Adapter {
+    context;
+    transport;
+    constructor(context, transport = {}) {
+        super();
+        this.context = context;
+        this.transport = transport;
+    }
+    get configurationIdentityFields() { return ['id']; }
+    get configurationIdentityProbeFields() { return ['token', 'apiBaseUrl']; }
+    get configurationUpdateFields() {
+        return ['token', 'polling', 'webhook',
+            'webhook.domain', 'webhook.path', 'webhook.secretToken', 'allowedUpdates', 'apiBaseUrl'];
+    }
+    validateConfiguration(config) { resolveTelegramConfig(config); }
+    async identifyConfiguration(input, signal) {
+        const client = new TelegramClient({ config: resolveTelegramConfig(input), ...this.transport });
+        const me = await client.callApi('getMe', {}, signal);
+        if (typeof me?.id !== 'number' || !Number.isFinite(me.id))
+            throw new Error('Telegram identity response is incomplete');
+        return JSON.stringify(['telegram', String(me.id)]);
+    }
+    createEndpoint(input, execution) {
+        const config = resolveTelegramConfig(input);
+        return new TelegramEndpoint({ id: execution.canonicalId, config, ...this.transport,
+            ...(config.mode === 'webhook' ? { http: this.context.use(httpHostToken) } : {}) });
+    }
+}

package/lib/client.d.ts

@@ -1,12 +1,8 @@
-import type { TelegramClient } from './endpoint.js';
+import type { TelegramAdapter } from './adapter.js';
 import type { TelegramUpdate } from './protocol.js';
 export type TelegramClientEventMap = Record<string, TelegramUpdate>;
 declare module '@zhin.js/feature-kit' {
-    interface AdapterClientRegistry {
-        readonly telegram: {
-            readonly client: TelegramClient;
-            readonly events: TelegramClientEventMap;
-        };
+    interface AdapterRegistry {
+        readonly telegram: TelegramAdapter;
     }
 }
-export declare const telegramClient: import("@zhin.js/adapter").EndpointClientToken<TelegramClient, TelegramClientEventMap>;

package/lib/client.js

@@ -1,2 +1 @@
-import { defineEndpointClient } from 'zhin.js/adapter';
-export const telegramClient = defineEndpointClient('telegram');
+export {};

package/lib/console-spec.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Telegram Console 页面元数据（浏览器与服务端共享；不要在这里 import 服务端代码）。
+ */
+import type { AdapterConsoleField } from 'zhin.js/adapter';
+export declare const telegramConsoleSpec: {
+    readonly adapterKey: "telegram";
+    readonly adapterDisplayName: "Telegram";
+    readonly fields: readonly AdapterConsoleField[];
+    readonly docsUrl: "https://zhin.js.org/adapters/telegram";
+    readonly readPermission: "telegram:read";
+    readonly writePermission: "telegram:write";
+};

package/lib/console-spec.js

@@ -0,0 +1,15 @@
+export const telegramConsoleSpec = {
+    adapterKey: 'telegram',
+    adapterDisplayName: 'Telegram',
+    fields: [
+        { key: 'token', required: true, env: true, description: 'Telegram bot token' },
+        { key: 'apiBaseUrl', description: 'Telegram Bot API URL' },
+        { key: 'polling', type: 'boolean', description: 'Use long polling; false selects webhook mode' },
+        { key: 'webhook.domain', description: 'Public webhook origin' },
+        { key: 'webhook.path', description: 'Local webhook route' },
+        { key: 'webhook.secretToken', env: true, description: 'Webhook secret token' },
+    ],
+    docsUrl: 'https://zhin.js.org/adapters/telegram',
+    readPermission: 'telegram:read',
+    writePermission: 'telegram:write',
+};

package/lib/console.d.ts

@@ -0,0 +1,2 @@
+import type { PluginConsoleRpc } from 'zhin.js';
+export declare function createTelegramConsoleRpc(getConfig: () => unknown): PluginConsoleRpc;

package/lib/console.js

@@ -0,0 +1,13 @@
+/**
+ * Telegram Console RPC：运行状态 + endpoint 增删（原 `telegram endpoint` 聊天命令）。
+ *
+ * 页面绑定 `pages/index`，读取 / 写入分别要求 `<adapter>:read` / `<adapter>:write`。
+ */
+import { createAdapterConsoleRpc } from 'zhin.js/adapter';
+import { telegramConsoleSpec } from './console-spec.js';
+export function createTelegramConsoleRpc(getConfig) {
+    return createAdapterConsoleRpc({
+        ...telegramConsoleSpec,
+        getConfig,
+    });
+}

package/lib/endpoint.d.ts

@@ -1,24 +1,10 @@
-import { Endpoint, type EndpointContentPort, type EndpointControl, type EndpointSendRequest, type EndpointTransportState } from 'zhin.js/adapter';
+import { TelegramClient, type TelegramFetch } from './telegram-client.js';
+import { endpointSpec, type Endpoint, type EndpointSpecification } from 'zhin.js/adapter';
 import type { HttpHost } from '@zhin.js/host-http';
 import { type MessageRef } from '@zhin.js/im-contract';
 import type { CapabilityId } from 'zhin.js';
 export { TelegramApiError } from './api-error.js';
-import { type ResolvedTelegramConfig, type TelegramCallbackQuery, type TelegramChatMember, type TelegramMessage, type TelegramUpdate } from './protocol.js';
-export type TelegramFetch = (url: string, init?: {
-    readonly method?: string;
-    readonly headers?: Record<string, string>;
-    readonly body?: string | FormData;
-    readonly signal?: AbortSignal;
-}) => Promise<{
-    readonly ok: boolean;
-    readonly status: number;
-    text(): Promise<string>;
-    json(): Promise<unknown>;
-    arrayBuffer?(): Promise<ArrayBuffer>;
-    readonly headers?: {
-        get(name: string): string | null;
-    };
-}>;
+import { type ResolvedTelegramConfig, type TelegramCallbackQuery, type TelegramMessage, type TelegramUpdate } from './protocol.js';
 export interface TelegramEndpointOptions {
     readonly id: CapabilityId;
     readonly config: ResolvedTelegramConfig;
@@ -27,91 +13,28 @@ export interface TelegramEndpointOptions {
     /** Internal transport deadline override; long polling always allows its server timeout. */
     readonly requestTimeoutMs?: number;
 }
-export interface TelegramClientApi {
-    callApi<T = unknown>(method: string, params?: Record<string, unknown>, signal?: AbortSignal): Promise<T>;
-    callApiForm<T = unknown>(method: string, form: FormData, signal?: AbortSignal): Promise<T>;
-    pinMessage(chatId: number, messageId: number): Promise<boolean>;
-    unpinMessage(chatId: number, messageId?: number): Promise<boolean>;
-    setChatDescription(chatId: number, description: string): Promise<boolean>;
-    setMessageReaction(chatId: number, messageId: number, reaction: string): Promise<boolean>;
-    getChatMemberCount(chatId: number): Promise<number>;
-    getChatAdmins(chatId: number): Promise<TelegramChatMember[]>;
-    sendStickerMessage(chatId: number, sticker: string): Promise<{
-        message_id: number;
-    }>;
-    setChatPermissionsAll(chatId: number, permissions: Record<string, boolean | undefined>): Promise<boolean>;
-    createInviteLink(chatId: number): Promise<string>;
-    sendPoll(chatId: number, question: string, options: string[], isAnonymous?: boolean, allowsMultipleAnswers?: boolean): Promise<{
-        message_id: number;
-    }>;
-}
-/** Telegram Bot API client carried by message, update and lifecycle events. */
-export declare class TelegramClient implements TelegramClientApi {
-    readonly api: TelegramClientApi;
-    constructor(api: TelegramClientApi);
-    callApi: <T = unknown>(method: string, params?: Record<string, unknown>, signal?: AbortSignal) => Promise<T>;
-    callApiForm: <T = unknown>(method: string, form: FormData, signal?: AbortSignal) => Promise<T>;
-    pinMessage: (chatId: number, messageId: number) => Promise<boolean>;
-    unpinMessage: (chatId: number, messageId?: number) => Promise<boolean>;
-    setChatDescription: (chatId: number, description: string) => Promise<boolean>;
-    setMessageReaction: (chatId: number, messageId: number, reaction: string) => Promise<boolean>;
-    getChatMemberCount: (chatId: number) => Promise<number>;
-    getChatAdmins: (chatId: number) => Promise<TelegramChatMember[]>;
-    sendStickerMessage: (chatId: number, sticker: string) => Promise<{
-        message_id: number;
-    }>;
-    setChatPermissionsAll: (chatId: number, permissions: Record<string, boolean | undefined>) => Promise<boolean>;
-    createInviteLink: (chatId: number) => Promise<string>;
-    sendPoll: (chatId: number, question: string, options: string[], anonymous?: boolean, multiple?: boolean) => Promise<{
-        message_id: number;
-    }>;
-}
+export { TelegramClient, type TelegramClientApi, type TelegramFetch } from './telegram-client.js';
 /**
  * Telegram Bot API 无列表类接口（无 getMyChats/getChatMembers），
  * 仅 getChat/getChatMember 按已知 id 单查，不构成列表能力；
  * 因此本 endpoint 不暴露 EndpointManagement（Console 社交面 RPC 对该平台保持未接线）。
  */
-export declare class TelegramEndpoint extends Endpoint<TelegramClient> {
+export declare class TelegramEndpoint extends TelegramClient implements Endpoint {
     #private;
-    readonly client: TelegramClient;
-    readonly control: EndpointControl;
-    readonly content: EndpointContentPort;
+    readonly [endpointSpec]: EndpointSpecification;
     constructor(options: TelegramEndpointOptions);
     /** Used by webhook handler. */
     get isOpen(): boolean;
-    get transportState(): EndpointTransportState;
     setPollingHealthy(healthy: boolean): void;
     get config(): ResolvedTelegramConfig;
     get allowedUpdates(): readonly string[];
     getUpdateOffset(): number;
     setUpdateOffset(offset: number): void;
-    start(): Promise<void>;
-    open(): void;
-    close(): void;
-    stop(): Promise<void>;
-    send({ conversation, payload }: EndpointSendRequest): Promise<string>;
-    recallMessage(message: MessageRef): Promise<void>;
+    recallMessage(message: MessageRef, signal?: AbortSignal): Promise<void>;
     /** Test / internal: admit a message when open. */
     admit(msg: TelegramMessage): void;
     /** Test / internal: admit a callback query when open. */
     admitCallback(query: TelegramCallbackQuery): void;
     /** Used by webhook / polling handlers. */
     handleUpdate(update: TelegramUpdate): Promise<void>;
-    callApi<T = unknown>(method: string, params?: Record<string, unknown>, signal?: AbortSignal): Promise<T>;
-    /** multipart/form-data 变体（attach:// 媒体上传；Content-Type 边界由 FormData 自带）。 */
-    callApiForm<T = unknown>(method: string, form: FormData, signal?: AbortSignal): Promise<T>;
-    pinMessage(chatId: number, messageId: number): Promise<boolean>;
-    unpinMessage(chatId: number, messageId?: number): Promise<boolean>;
-    setChatDescription(chatId: number, description: string): Promise<boolean>;
-    setMessageReaction(chatId: number, messageId: number, reaction: string): Promise<boolean>;
-    getChatMemberCount(chatId: number): Promise<number>;
-    getChatAdmins(chatId: number): Promise<TelegramChatMember[]>;
-    sendStickerMessage(chatId: number, sticker: string): Promise<{
-        message_id: number;
-    }>;
-    setChatPermissionsAll(chatId: number, permissions: Record<string, boolean | undefined>): Promise<boolean>;
-    createInviteLink(chatId: number): Promise<string>;
-    sendPoll(chatId: number, question: string, options: string[], isAnonymous?: boolean, allowsMultipleAnswers?: boolean): Promise<{
-        message_id: number;
-    }>;
 }