Repository navigation
Conversation
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
1 participant
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.
Organisers can message selected guest response groups with text and attachments, view delivery history in the Mini App, and request deletion from guest chats. Recipient selections update in place, the composer uses Telegram's reply keyboard, and sending restores the main menu.
The delivery queue retries brief database lock contention, drains successive batches, and prioritises organiser confirmations. Shared media supports direct Telegram links and optional QR codes; organiser menus, guest totals, event cancellation and update timestamps are clearer.
Validation: 460 unit tests, complete Worker integration checks and static asset imports passed locally. Integration covers simulated delivery contention, duplicate prevention, authorisation, snapshot safeguards, multipart QR delivery and message deletion. Mobile messaging and gallery layouts checked during development. No schema migration or database refresh is required. Existing invitation links, responses, payments and production environment configuration are preserved.