Skip to content

fix: support Telegram callbacks and long polling - #262

Merged
deepessh merged 2 commits into
mainfrom
fix/261-telegram-callback-polling
Aug 7, 2026
Merged

deepessh merged 2 commits into
mainfrom
fix/261-telegram-callback-polling

Conversation

@deepessh

@deepessh deepessh commented Aug 7, 2026 •

Copy link
Copy Markdown
Owner

Closes #261

Summary

  • encode delivery-bound Telegram callback data within the 64-byte Bot API limit and strictly decode it inbound
  • add local staff-only Telegram long polling with offset, retry, shutdown, and webhook mutual-exclusion behavior
  • route polling through the existing authorization, replay, and evidence path; update PRD F6 and runtime configuration
  • format reviews with Telegram-native HTML hierarchy and quoted answer panels
  • edit answered messages in place with durable correct/keep-going feedback, preserving unanswered buttons in multi-question batches

Verification

  • corepack pnpm test
  • corepack pnpm lint
  • corepack pnpm build
  • ADR, architecture, and problem-document validation
  • live staff-only Telegram proof: one real review delivered, one button callback consumed via long polling, delivery finalized with one persisted attempt

No credentials, chat identifiers, or learner data are included.

@deepessh
deepessh merged commit 482bd8f into main Aug 7, 2026
2 of 3 checks passed
@deepessh
deepessh deleted the fix/261-telegram-callback-polling branch August 7, 2026 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix Telegram inline callback payloads exceeding Bot API limit

1 participant