feat: atomically enqueue Workshop replies - #856
Merged
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
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.
Summary
Atomic contract
One transaction now owns:
message.createdeventdelivery.requestedeventdelivery_outboxrowAny binding-resolution, append, projection, outbox-insert, or commit failure rolls the whole unit back.
The caller supplies only the canonical inbound message, response body, and occurrence time. The service derives the agent, channel, and exactly one canonical Telegram binding; it accepts no Telegram chat ID or binding ID from the caller.
Failure and idempotency coverage
Production impact
None.
record_outbound_message_with_deliveryhas no production caller. The Workshop worker remains unregistered, and existing direct Telegram delivery remains authoritative.Validation
make checkmake typecheck