Repository navigation
release: Telegram live activity in 0.20.1 - #32
Merged
Merged
Conversation
morningstarnasser
changed the title
morningstarnasser
marked this pull request as ready for review
November 11, 2026 10:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ship Telegram live activity as stable maintenance release 0.20.1. The display shows reading/running/thinking phases, fixed tool labels, measured outcomes and an honest wait hint. The existing five-second status tick supplies optional dots; approval waits stay quiet. Reply completion remains separate from background-job completion.
Includes the refreshed renderer-based Telegram demonstration, public documentation and website version/capability copy. No permission, model or dependency changes.
Qualification: two consecutive Telegram regression runs (94 passed each); full platform, signed clean-install/0.20.0 upgrade/rollback, real-model E2E, OSV and public-hygiene gates must all pass before merge. This replaces the earlier post-Stable hold: the operator explicitly requested immediate publication after 0.20.0 was completed.