[Fix] Automation scans post status messages before results are ready - #924
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
[Fix] Automation scans post status messages before results are ready#924roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
Author
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
Scheduled automation scans now carry an explicit runtime flag that prevents them from calling channel-posting tools. Their result-submission tools remain available, and late-bound execution tasks can still send their required final closeout.
The worker tests cover all chat reply purposes, standalone channel posts, the OpenCode hook integration, and the allowed suggestion-submission path.
Why this change was made
Scheduled scans could post agent-authored status updates before their normal automation report was ready, creating noisy and misleading channel messages.
Impact
Automation channels stay quiet while scheduled scans are running and receive output only through the established reporting path. Follow-up execution task closeouts are unchanged.