Fork of upstream llblab/[email protected].0 (SHA afe09c5) repackaged as a drop-in extension for can1357/oh-my-pi (omp >= 16.5.2). Changes vs upstream: - Rename package: @llblab/pi-telegram -> @evandrodevbr/oh-my-pi-telegram - Bump version: 0.22.0 -> 0.22.0-evandro.1 - Update repository/homepage/bugs URLs to evandrodevbr - Add omp field in package.json (displayName + compatibleWith) - README: prepend 'Oh My Pi (omp) Compatibility' section with install commands, verified-components table, upstream lineage, and rationale - CHANGELOG: add '0.22.0-evandro.1' entry under Unreleased - docs/: rename @llblab/pi-telegram imports to @evandrodevbr/oh-my-pi-telegram - tests/public-api.test.ts: rename package import paths Gates re-run on the fork: - npm run typecheck -> tsc --noEmit (success) - npm test -> 1229 pass / 0 fail / 1 platform-only skip - npm run audit -> found 0 vulnerabilities - npm run pack:check -> evandrodevbr-oh-my-pi-telegram-0.22.0-evandro.1.tgz Verified: - omp install --link ./pi-telegram -> Linked OK - omp plugin list -> @evandrodevbr/[email protected].0-evandro.1 Upstream lineage: badlogic/pi-telegram -> llblab/pi-telegram (0.22.0) -> evandrodevbr/oh-my-pi-telegram (this fork)
22 lines
643 B
TypeScript
22 lines
643 B
TypeScript
/**
|
|
* 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";
|