Evandro Fonseca Junior
d1d04001d0
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)
3.0 KiB
3.0 KiB
Documentation Index
Living index of project documentation in /docs.
public-api.md is the canonical entrypoint for stable extension surfaces. Focused documents exist only when a surface has enough runtime rules to need a dedicated standard.
Documents
- architecture.md — Overview of the Telegram bridge runtime, optional profile isolation, queueing model, native Rich Markdown delivery, UI/compat rendering, and interactive controls
- public-api.md — Stable public API map: package entrypoints, commands, config, assistant markup, extension APIs, smoke examples, and compatibility boundaries
- delivery.md — Target-aware companion delivery contract for operational views, logical message handles, target scopes, lifecycle fencing, and leader/follower transport
- activity.md — Normalized Pi lifecycle API for extension-owned reasoning, intermediate prose, tool activity, source identity, delivery contexts, and consumer policy examples
- ../.agents/skills/telegram-bot/SKILL.md — Agent-facing Telegram Bot API lookup skill backed by a local full Bot API reference
- ../.agents/skills/domain-dag/SKILL.md — Project-local Domain DAG architecture skill and validator guidance
- command-templates.md — Portable command-template standard core
- inbound.md — Local
pi-telegraminbound text/media handler bus, programmatic inbound handlers, registered STT provider fallbacks, legacyattachmentHandlerscompatibility, placeholders, and fallbacks - outbound.md — Local
pi-telegramoutbound-handler config, text/voice/button behavior, voice synthesis provider fallback priority, artifact outputs, and callback routing - callback-namespaces.md — Shared Telegram
callback_datanamespace standard for layered extensions - updates.md — Update classification and runtime handler registry that lets layered extensions observe and consume Telegram updates without owning their own polling connection
- multi-instance-bus.md — Optional multi-instance Telegram bus architecture: profile-scoped transport, leader/follower routing, thread targets, instance slots, manual follower registration, and recovery semantics
- sections.md — Telegram Extension Sections Standard: registration contract, context ports, callback routing, navigation hierarchy, and demo reference for pi extensions that want Telegram UI surfaces
- voice.md — Voice integration guide: detection, reply policy, STT/TTS provider registration, provider-owned conversion, and transparent interception
- locks.md — Shared
locks.jsonstandard for singleton extension ownership - ui-style.md — Inline UI style guide for buttons, toggles, tabs, option lists, cards, and dialogs