Skip to content

fix: report telegram ask provenance - #51

Merged
TerrifiedBug merged 1 commit into
masterfrom
fix/ask-result-provenance
Aug 14, 2026
Merged

fix: report telegram ask provenance#51
TerrifiedBug merged 1 commit into
masterfrom
fix/ask-result-provenance

Conversation

@TerrifiedBug

Copy link
Copy Markdown
Owner

Summary

  • prefix every telegram_ask result with machine-readable posted-surface and answer-origin provenance
  • preserve loud per-surface errors when Telegram posting fails but a terminal answer succeeds
  • track Telegram posting at the Bot API boundary without changing first-answer routing or cancellation semantics
  • document the result contract and pin terminal-only, both dual-surface answer origins, and partial-delivery failure

Verification

  • bun install
  • bun run check (273 tests pass)

Closes #50

@TerrifiedBug
TerrifiedBug merged commit 02dcfde into master Aug 14, 2026
1 check passed
@TerrifiedBug
TerrifiedBug deleted the fix/ask-result-provenance branch August 14, 2026 13:05
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.

telegram_ask result must report which surfaces the question was posted to and which surface answered

1 participant