Skip to content

fix(telegram): fallback blank rich final sends#1099

Open
artemgetmann wants to merge 2 commits into
mainfrom
codex/telegram-rich-final-transport-20260706
Open

fix(telegram): fallback blank rich final sends#1099
artemgetmann wants to merge 2 commits into
mainfrom
codex/telegram-rich-final-transport-20260706

Conversation

@artemgetmann

@artemgetmann artemgetmann commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • detect Telegram rich final sends that return a message id but render blank visible text
  • fall back to the legacy HTML/plain send path when that blank rich response is detected
  • add regression coverage for final paragraphs falling back without losing paragraph spacing

Validation

  • pnpm exec vitest run extensions/telegram/src/bot/delivery.test.ts extensions/telegram/src/send.test.ts extensions/telegram/src/bot-message-dispatch.test.ts
  • GitHub checks: green on head 7cbd04a8aa9b0dd25fec3fe8b20e83892d8d9b16

Proof Gaps

  • No live tester-bot proof was run for this PR. This is intentionally a transport fallback PR with terminal regression coverage.

Codex added 2 commits July 7, 2026 13:43
- What: validate rich-message request/response visibility before treating rich text sends as delivered.
- Why: final answers can now use rich transport while explicit blank rich responses fall back to legacy Telegram HTML.
- Risk: low; scoped to Telegram text rich-send fallback and preserves existing HTML/plain fallback chain.
- What: add a regression test for three-paragraph final text when rich delivery reports explicit blank text.

- Why: the observed failure was blank visible final text with paragraph-sensitive final content, so fallback must prove readable paragraph preservation.

- Risk: none; test-only coverage for the existing Telegram rich-to-HTML fallback behavior.
@artemgetmann artemgetmann force-pushed the codex/telegram-rich-final-transport-20260706 branch from e543b36 to 7cbd04a Compare July 7, 2026 05:44
@artemgetmann artemgetmann marked this pull request as ready for review July 7, 2026 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant