[Fix] Automation runs post Slack preambles before results - #2648
Open
roomote-roomote[bot] wants to merge 1 commit into
Open
roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 13, 2026 23:29
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.
What changed
Automation-started worker tasks now carry a dedicated state flag that blocks acknowledgement and progress replies, channel posts, thread replies, and reactions until a closeout or clarification is ready. The flag is shared by scheduled scans, automation work-item executions, and custom automation tasks without requiring routine no-result runs to post a terminal message.
Why this change was made
The original premature-reply gate reused the flag that also forced a terminal closeout. When that closeout requirement was intentionally removed so routine automation runs could remain silent, the delivery gate was disabled as a side effect and automation preambles could reach Slack again.
Impact
Scheduled automation work stays silent while in flight, while final results, blockers, and required input remain deliverable. Human-authored turn acknowledgement behavior is unchanged, and Fast chat platform events retain their existing independent closeout-or-clarification runtime gate. Focused worker tests cover all automation launch classifications, blocked non-terminal delivery paths, and allowed terminal delivery; worker lint, type checks, and the repository pre-push checks pass.