@llblab/pi-telegram 0.46.0 → 0.47.0

package/BACKLOG.md

@@ -37,5 +37,4 @@ _This file owns unresolved project work only. Completed behavior belongs in `CHA
   - [ ] Harden the implemented pre-queue `app::method` / strict-JSON bound-action route with revision capture for agent-mediated initial surfaces, profile/target authority, follower transport evidence, voice output delivery, and commit-unknown diagnostics while preserving generation-plus-revision stale-click rejection, fail-closed malformed/absent methods, ordinary model prompts, and native single-colon callbacks.
   - [ ] Harden the implemented cross-process transition lock, dead-owner recovery, expected-generation/revision comparison, repaired partial-tail/current-state recovery, transactional `init` reset, and output-only methods with process-birth proof, bounded lock diagnostics, more interruption points, and explicit commit-unknown evidence.
   - [ ] Complete the capability-owned Music Player adapter evidence beyond the successful real `ffplay` singleton install and no-model-turn bound `next`, `pause`, resume/`play`, and terminal `stop` Controls: exercise generated relative-volume controls over arbitrary absolute Actor percentages, `toggle`, `previous`, `status`, compatible singleton reuse, checkpoint restart, missing/terminal Run, unavailable backend, process timeout/cancellation/stream bounds, and redacted errors while keeping actor reality authoritative and rejecting generic remote-terminal methods.
-  - [ ] Extend the implemented new-message default plus opt-in `viewMode: "edit"` bound-action update into optional output-only `refresh` scheduling from `refreshAfterMs`, clamped to at least two seconds and serialized after prior completion; retain one latest logical view handle per app/profile/target, skip unchanged frame digests, honor Telegram retry/backoff, cancel on lifecycle replacement, stop and forget the handle on known deletion or message-not-found, and never recreate a deleted live view without a fresh user action.
   - [ ] Cover CML and JSON equivalence, both mutually exclusive Tool shapes, direct agent-authored app discovery, install/copy and existing-app `init`, scalar/object/no-argument methods, agent-side diagnostic invocation, bounded CLI adaptation, refresh coalescing/rate limits/backoff/deletion, identity/path traversal, duplicate/overlapping prefixes, state recovery, handler failure, stale clicks, session replacement, follower routing, and the invariant that bound actions perform no model turn. `tests/generative-apps.test.ts` now covers scalar/object/no-argument argument shapes, throwing-method failure containment (state and journal untouched), and bounded argument/output/state/module limits before durable mutation; the remaining items stay open.

package/CHANGELOG.md

@@ -4,6 +4,14 @@
 
 ## Unreleased
 
+## 0.47.0: Built runtime and live surfaces
+
+- `Startup`: npm installs now load a compiled JavaScript extension from a nested `dist/pi-telegram` entrypoint while source checkouts retain `index.ts`. Stable public subpath exports ship compiled JavaScript plus declarations, packaged Skills follow the distributive root, and validation checks the built extension import.
+- `Button authoring`: Native `telegram_button` fences now accept adjacent top-level JSON/CML objects without an outer array or commas as vertical singleton rows. Explicit outer matrices remain equivalent, nested arrays still own horizontal layout, and malformed sequences activate no controls.
+- `Activity`: Native typing remains continuously re-armed during agent/message work, pauses only for local UI prompts, resumes for unsettled agent or compaction work, and retargets queued turns without leaking keepalive ticks across Threads; transport and session fences still suppress stale actions.
+- `Live views`: Validated `refreshAfterMs` drives non-overlapping timers after hinted `telegram_bind` delivery. Refreshes and current-surface actions edit one generation-fenced Delivery handle through the Markdown/button planner across classic, leader, and follower targets; hints reschedule and omission closes. Retryable failures retain one frame; unavailable messages invalidate with a bounded diagnostic. Take, shutdown, and replacement fence late refreshes and cancel memory-only surfaces.
+- `Thread display`: Adds explicit `directory-snake` and `directory-title` profile modes with shared Unicode-aware path tokenization, uppercase-abbreviation preservation, live Settings previews, initial/reconciled title projection, and negotiated peer capability fencing. Their slot suffixes now follow authenticated concurrent live same-directory ownership and disappear after disconnect or confirmed-dead pruning; dormant bindings and sticky legacy metadata are ignored. Retained `directories` stays unchanged.
+
 ## 0.46.0: Session-aware Workspace Threads
 
 - `Session-aware Thread binding`: Workspace identity restored session-qualified bindings from Pi's stable public session identity, so reopening, resuming, or replacing a process reclaims the same Telegram Thread and letter while distinct sessions in one directory keep independent targets. Strict legacy cwd-only records remain inert and coexist safely; protocol v2 rejects mixed 0.45.x peers before provisioning, and exact-session cleanup, displacement, rename, promotion, and slot-pressure fences are preserved.

package/README.md

@@ -226,7 +226,7 @@ Voice notes, audio, images, PDFs, and other media can pass through configured in
 
 ### Buttons And Callbacks
 
-Assistant replies can place controls between paragraphs using standalone triple-backtick `telegram_button` blocks, or keep them in the footer using top-level hidden `telegram_button` comments. Both wrappers accept singleton cells and mixed JSON/CML matrices. Native in-body rows allow up to eight buttons; HTML compatibility moves these rows to the footer. In-body clicks acknowledge without recoloring the Rich body, while footer selection styles remain unchanged. Hidden comments accept a JSON object, adaptive JSON/CML matrix, or positional Compact Matrix Literal (CML). One adaptive matrix may mix named JSON objects with positional CML cells; separators are optional and one trailing comma is tolerated, including inside JSON objects. Top-level cells become full-width rows while nested rows group one or more buttons horizontally without an artificial parser-level width cap; generated surfaces default to five columns and use six to eight only for short position-bearing labels. CML uses `{value}`, `{label|prompt}`, `{|prompt}`, or the corresponding three-atom form with `selected_style` set to `primary`, `success`, or `danger`; omitting the first atom leaves the existing prompt-as-label fallback in charge, while the optional style still requires a non-empty prompt. A fourth atom adds disabled state: `{|Next||1}` or `{|Next||true}` disables, `0` or `false` enables (exact lowercase), and omission stays enabled; the third atom may be empty in this form. JSON uses boolean `disabled`. Disabled controls require no prompt or selected style: `{Next|||1}` shows only a label, while `{|||1}` is a blank disabled cell. Disabled controls remain visible without registering callbacks or invoking prompts/app methods. It trims atom boundaries, preserves non-structural text literally, and decodes only `\|`, `\}`, and `\\`. Prefer one matrix comment for multiple buttons. Buttons use `label` plus `prompt`, or the compact `value` key when both are identical. The bridge strips every assistant-authored HTML comment from Telegram previews and final replies regardless of Markdown position or owning extension, while only recognized top-level comments activate buttons or voice; comment-only output sends no text message and the Pi terminal transcript remains unchanged. It renders valid inline buttons and routes callbacks back into Pi as queued prompts or extension-owned callback actions. Button-only replies receive the standard `☑️ **Choose an option:**` heading as automatic visible fallback text. Once a generated prompt button is accepted, only that exact button switches to its optional `selected_style` (`primary` blue by default, `success` green, or `danger` red) without altering its agent-authored label or emoji; every style still queues the selected prompt.
+Assistant replies can place controls between paragraphs using standalone triple-backtick `telegram_button` blocks, or keep them in the footer using top-level hidden `telegram_button` comments. Both wrappers accept singleton cells and mixed JSON/CML matrices. Native in-body rows allow up to eight buttons; HTML compatibility moves these rows to the footer. In-body clicks acknowledge without recoloring the Rich body, while footer selection styles remain unchanged. Hidden comments accept a JSON object, adaptive JSON/CML matrix, or positional Compact Matrix Literal (CML). One adaptive matrix may mix named JSON objects with positional CML cells; separators are optional and one trailing comma is tolerated, including inside JSON objects. Top-level cells become full-width rows while nested rows group one or more buttons horizontally without an artificial parser-level width cap; inside a fenced block, adjacent top-level JSON/CML objects may omit the outer array and commas. Generated surfaces default to five columns and use six to eight only for short position-bearing labels. CML uses `{value}`, `{label|prompt}`, `{|prompt}`, or the corresponding three-atom form with `selected_style` set to `primary`, `success`, or `danger`; omitting the first atom leaves the existing prompt-as-label fallback in charge, while the optional style still requires a non-empty prompt. A fourth atom adds disabled state: `{|Next||1}` or `{|Next||true}` disables, `0` or `false` enables (exact lowercase), and omission stays enabled; the third atom may be empty in this form. JSON uses boolean `disabled`. Disabled controls require no prompt or selected style: `{Next|||1}` shows only a label, while `{|||1}` is a blank disabled cell. Disabled controls remain visible without registering callbacks or invoking prompts/app methods. It trims atom boundaries, preserves non-structural text literally, and decodes only `\|`, `\}`, and `\\`. Prefer one matrix comment for multiple buttons. Buttons use `label` plus `prompt`, or the compact `value` key when both are identical. The bridge strips every assistant-authored HTML comment from Telegram previews and final replies regardless of Markdown position or owning extension, while only recognized top-level comments activate buttons or voice; comment-only output sends no text message and the Pi terminal transcript remains unchanged. It renders valid inline buttons and routes callbacks back into Pi as queued prompts or extension-owned callback actions. Button-only replies receive the standard `☑️ **Choose an option:**` heading as automatic visible fallback text. Once a generated prompt button is accepted, only that exact button switches to its optional `selected_style` (`primary` blue by default, `success` green, or `danger` red) without altering its agent-authored label or emoji; every style still queues the selected prompt.
 
 ### Threaded Mode And Multi-Instance Bus
 
@@ -240,7 +240,7 @@ Classic private DM mode is the base product mode. When Telegram private-chat Thr
 - Unknown threads are preserved and offered explicit reroute/restore choices.
 - Telegram never launches hidden Pi processes.
 
-In Threaded Mode, open Settings → **🧵 Thread display** to choose **Letters** (default), **Names**, or **Directories** for this bot profile. Fresh tabs are created with the active mode's title instead of being visibly renamed afterward. Telegram tab titles, Pi terminal status, live Thread choosers/notices, prompt attribution, and named `telegram_message` targeting use the same acknowledged display name; target IDs and live registrations still own routing. Names shows the generated dictionary name chosen for the slot, such as `Anchor` for slot `A`. Directory mode adds persistent global-letter suffixes when a Workspace has multiple instances, such as `extensions_a` and `extensions_c`. `/name` sets a manual Thread display name; **Reset to automatic** restores the selected automatic projection. Switching preserves Thread IDs, slots, generated recovery identity, and queue ownership. Partial application reports an error and can be retried without recreating Threads.
+In Threaded Mode, open Settings → **🧵 Thread display** to choose **Letters** (default), **Names**, **directory-snake**, or **directory-title** for this bot profile; a retained **directories** value remains available as an unchanged legacy presentation. The Settings detail shows a bounded live preview computed from current Workspace bindings. Fresh tabs are created with the active mode's title instead of being visibly renamed afterward. Telegram tab titles, Pi terminal status, live Thread choosers/notices, prompt attribution, and named `telegram_message` targeting use the same acknowledged display name; target IDs and live registrations still own routing. Names shows the generated dictionary name chosen for the slot, such as `Anchor` for slot `A`; the directory formats produce `api_tools` or `Api Tools` and append `_a` or ` · A` only while two or more authenticated live instances share that exact directory. Dormant retained bindings do not keep those suffixes visible. `/name` sets a manual Thread display name; **Reset to automatic** restores the selected automatic projection. Switching preserves Thread IDs, slots, generated recovery identity, and queue ownership. Partial application reports an error and can be retried without recreating Threads.
 
 | Mode | Best for | Runtime shape |
 | --- | --- | --- |

package/dist/api/activity.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram activity API
+ * Zones: package boundary, pi agent lifecycle, extension interop
+ * Exposes normalized non-blocking activity registration while keeping lifecycle wiring and dispatch internals package-private
+ */
+export { registerTelegramActivityHandler, type TelegramActivityContext, type TelegramActivityEnvelope, type TelegramActivityEvent, type TelegramActivityHandlerRegistration, type TelegramActivitySource, type TelegramActivityTarget, } from "../lib/activity.ts";

package/dist/api/activity.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram activity API
+ * Zones: package boundary, pi agent lifecycle, extension interop
+ * Exposes normalized non-blocking activity registration while keeping lifecycle wiring and dispatch internals package-private
+ */
+export { registerTelegramActivityHandler, } from "../lib/activity.js";

package/dist/api/commands.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram commands API
+ * Zones: package boundary, extension interop
+ * Exposes the stable Telegram slash-command registration surface while keeping registry internals package-private
+ */
+export { registerTelegramCommand, type TelegramExtensionCommandContext, type TelegramExtensionCommandRegistration, } from "../lib/commands.ts";

package/dist/api/commands.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram commands API
+ * Zones: package boundary, extension interop
+ * Exposes the stable Telegram slash-command registration surface while keeping registry internals package-private
+ */
+export { registerTelegramCommand, } from "../lib/commands.js";

package/dist/api/delivery.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram delivery API
+ * Zones: package boundary, telegram delivery, extension interop
+ * Exposes target-aware operational view delivery while keeping transport and runtime binding internals package-private
+ */
+export { deleteTelegramView, editTelegramView, sendTelegramChatAction, sendTelegramView, type SendTelegramViewOptions, type TelegramDeliveryChatAction, type TelegramDeliveryFailureReason, type TelegramDeliveryHandle, type TelegramDeliveryParseMode, type TelegramDeliveryResult, type TelegramDeliveryScope, type TelegramDeliveryTarget, type TelegramDeliveryView, } from "../lib/delivery.ts";

package/dist/api/delivery.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram delivery API
+ * Zones: package boundary, telegram delivery, extension interop
+ * Exposes target-aware operational view delivery while keeping transport and runtime binding internals package-private
+ */
+export { deleteTelegramView, editTelegramView, sendTelegramChatAction, sendTelegramView, } from "../lib/delivery.js";

package/dist/api/inbound.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram inbound API
+ * Zones: package boundary, extension interop
+ * Exposes the stable programmatic inbound handler surface while keeping handler runtime internals package-private
+ */
+export { registerTelegramInboundHandler, type TelegramInboundHandlerFile, type TelegramInboundHandlerOutput, type TelegramInboundProgrammaticHandler, type TelegramInboundProgrammaticHandlerInput, type TelegramInboundProgrammaticHandlerResult, } from "../lib/inbound.ts";

package/dist/api/inbound.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram inbound API
+ * Zones: package boundary, extension interop
+ * Exposes the stable programmatic inbound handler surface while keeping handler runtime internals package-private
+ */
+export { registerTelegramInboundHandler, } from "../lib/inbound.js";

package/dist/api/keyboard.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram keyboard API
+ * Zones: package boundary, extension interop
+ * Exposes shared inline-keyboard structural types without runtime exports
+ */
+export type { TelegramInlineKeyboardButton, TelegramInlineKeyboardButtonStyle, TelegramInlineKeyboardMarkup, } from "../lib/keyboard.ts";

package/dist/api/keyboard.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram keyboard API
+ * Zones: package boundary, extension interop
+ * Exposes shared inline-keyboard structural types without runtime exports
+ */
+export {};

package/dist/api/outbound.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram outbound API
+ * Zones: package boundary, extension interop
+ * Exposes stable outbound handler and diagnostics surfaces while keeping delivery internals package-private
+ */
+export { recordTelegramRuntimeEvent, registerTelegramOutboundHandler, type TelegramOutboundProgrammaticHandler, } from "../lib/outbound.ts";

package/dist/api/outbound.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram outbound API
+ * Zones: package boundary, extension interop
+ * Exposes stable outbound handler and diagnostics surfaces while keeping delivery internals package-private
+ */
+export { recordTelegramRuntimeEvent, registerTelegramOutboundHandler, } from "../lib/outbound.js";

package/dist/api/sections.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Public Telegram sections API
+ * Zones: package boundary, extension interop
+ * Exposes the stable managed Telegram menu-section surface while keeping registry internals package-private
+ */
+export type { TelegramInputRichBlock, TelegramInputRichMessage, TelegramRichText } from "../lib/telegram-api.ts";
+export { getTelegramSectionDiagnostics, registerTelegramSection, type TelegramSectionCallbackContext, type TelegramSectionCallbackResult, type TelegramSectionContext, type TelegramSectionDiagnostic, type TelegramSectionRegistration, type TelegramSectionSettingsRegistration, type TelegramSectionView, } from "../lib/sections.ts";

package/dist/api/sections.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram sections API
+ * Zones: package boundary, extension interop
+ * Exposes the stable managed Telegram menu-section surface while keeping registry internals package-private
+ */
+export { getTelegramSectionDiagnostics, registerTelegramSection, } from "../lib/sections.js";

package/dist/api/status.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram status API
+ * Zones: package boundary, extension interop
+ * Exposes compact status-menu line registration for extension consumers while keeping status rendering internals package-private
+ */
+export { registerTelegramStatusLineProvider, type TelegramStatusLineProvider, type TelegramStatusLineProviderContext, type TelegramStatusLineProviderResult, } from "../lib/status.ts";

package/dist/api/status.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram status API
+ * Zones: package boundary, extension interop
+ * Exposes compact status-menu line registration for extension consumers while keeping status rendering internals package-private
+ */
+export { registerTelegramStatusLineProvider, } from "../lib/status.js";

package/dist/api/updates.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram updates API
+ * Zones: package boundary, extension interop
+ * Exposes the stable raw-update handler surface while keeping update routing internals package-private
+ */
+export { assertTelegramUpdateExecutionCurrent, carryTelegramUpdateExecutionFence, createTelegramUpdateExecutionFenceGuard, getTelegramUpdateExecutionFence, registerTelegramUpdateHandler, type TelegramUpdateExecutionFence, type TelegramUpdateHandler, type TelegramUpdateHandlerVerdict, } from "../lib/updates.ts";

package/dist/api/updates.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram updates API
+ * Zones: package boundary, extension interop
+ * Exposes the stable raw-update handler surface while keeping update routing internals package-private
+ */
+export { assertTelegramUpdateExecutionCurrent, carryTelegramUpdateExecutionFence, createTelegramUpdateExecutionFenceGuard, getTelegramUpdateExecutionFence, registerTelegramUpdateHandler, } from "../lib/updates.js";

package/dist/api/voice.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram voice API
+ * Zones: package boundary, extension interop
+ * Exposes the stable STT/TTS provider surface and voice policy helpers
+ */
+export { TELEGRAM_VOICE_REPLY_MODES, computeVoicePromptContribution, computeVoiceTurnFlags, getTelegramVoiceReplyMode, isVoiceTurn, registerTelegramVoiceSynthesisProvider, registerTelegramVoiceTranscriptionProvider, shouldSuppressPreviewForVoice, type TelegramVoiceReplyMode, type TelegramVoiceSynthesisProvider, type TelegramVoiceSynthesisProviderResult, type TelegramVoiceTranscriptionFile, type TelegramVoiceTranscriptionProvider, type TelegramVoiceTranscriptionProviderResult, type TelegramVoiceTurnView, } from "../lib/voice.ts";

package/dist/api/voice.js

@@ -0,0 +1,6 @@
+/**
+ * Public Telegram voice API
+ * Zones: package boundary, extension interop
+ * Exposes the stable STT/TTS provider surface and voice policy helpers
+ */
+export { TELEGRAM_VOICE_REPLY_MODES, computeVoicePromptContribution, computeVoiceTurnFlags, getTelegramVoiceReplyMode, isVoiceTurn, registerTelegramVoiceSynthesisProvider, registerTelegramVoiceTranscriptionProvider, shouldSuppressPreviewForVoice, } from "../lib/voice.js";

package/dist/index.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Telegram package entrypoint
+ * Zones: telegram, pi agent, public API
+ * Re-exports the extension composition root without owning runtime wiring.
+ */
+export { default } from "./lib/extension.ts";

package/dist/index.js

@@ -0,0 +1,6 @@
+/**
+ * Telegram package entrypoint
+ * Zones: telegram, pi agent, public API
+ * Re-exports the extension composition root without owning runtime wiring.
+ */
+export { default } from "./lib/extension.js";

package/dist/lib/activity-verbosity.d.ts

@@ -0,0 +1,52 @@
+/**
+ * Bridge-owned Telegram activity verbosity projection
+ * Zones: telegram activity, rich rendering, operational delivery
+ * Owns persistent bounded thinking and tool disclosures; excludes activity normalization, assistant answer rendering, and transport authority policy
+ */
+import type { TelegramActivityEvent, TelegramActivityPublicationRuntime } from "./activity.ts";
+import type { TelegramEditMessageTextBody, TelegramInputRichMessage, TelegramSendMessageBody, TelegramSendRichMessageBody, TelegramSentMessage } from "./telegram-api.ts";
+import type { TelegramTarget } from "./target.ts";
+export declare const TELEGRAM_ACTIVITY_DETAIL_MAX_CHARS = 1200;
+export declare const TELEGRAM_ACTIVITY_MESSAGE_MAX_CHARS = 3900;
+export declare const TELEGRAM_ACTIVITY_MESSAGE_MAX_TOOLS = 6;
+export declare const TELEGRAM_REASONING_MESSAGE_MAX_FRAMES = 24;
+export declare const TELEGRAM_REASONING_BUFFER_MAX_CHARS = 1200;
+export declare const TELEGRAM_REASONING_MIN_INTERVAL_MS = 1200;
+export declare const TELEGRAM_TOOL_UPDATE_MAX_ENTRIES = 4;
+interface ToolActivity {
+    id: string;
+    name: string;
+    args: string;
+    updates: string[];
+    droppedUpdates: number;
+    result?: string;
+    isError?: boolean;
+    complete: boolean;
+}
+export declare function renderTelegramToolActivityHtml(tools: readonly ToolActivity[]): string;
+export declare function renderTelegramToolActivityRichMessage(tools: readonly ToolActivity[]): TelegramInputRichMessage;
+export declare function renderTelegramThinkingActivityHtml(text: string): string;
+export interface TelegramActivityVerbosityRuntime {
+    accept: (event: TelegramActivityEvent) => void;
+    reset: () => void;
+    stop: () => void;
+    waitForIdle: () => Promise<void>;
+}
+export interface TelegramActivityVerbosityBinding extends TelegramActivityVerbosityRuntime {
+    bind: (runtime: TelegramActivityVerbosityRuntime) => void;
+}
+export declare function createTelegramActivityVerbosityBinding(): TelegramActivityVerbosityBinding;
+export declare function createTelegramActivityVerbosityRuntime<TAuthority>(deps: {
+    enqueue?: TelegramActivityPublicationRuntime["enqueue"];
+    getActivityMode: () => "quiet" | "thinking" | "tools" | "verbose";
+    refreshActivityMode?: () => Promise<void>;
+    getNowMs?: () => number;
+    resolveTarget: (event: TelegramActivityEvent) => TelegramTarget | undefined;
+    captureAuthority: () => TAuthority;
+    isAuthorityActive: (authority: TAuthority) => boolean;
+    sendMessage: (body: TelegramSendMessageBody) => Promise<TelegramSentMessage>;
+    sendRichMessage: (body: TelegramSendRichMessageBody) => Promise<TelegramSentMessage>;
+    editMessageText: (body: TelegramEditMessageTextBody) => Promise<"edited" | "unchanged">;
+    recordFailure?: (operation: "config-refresh" | "reasoning-send" | "reasoning-edit" | "tool-send" | "tool-edit", event: TelegramActivityEvent, error: unknown) => void;
+}): TelegramActivityVerbosityRuntime;
+export {};