Repository navigation
fix(project): require owner request for Worker reports - #64
Merged
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.
Why
Worker discussions can still be open when the agent sends a final report to the coordinator. This change requires the project owner to request that report in the current Worker group.
What changed
requestId.Scope
finalandescalationreports.Blast Radius
Worker reports that do not have a current explicit owner request now fail before coordinator delivery. Existing local discussion and native event handling remain covered by the project runtime tests.
Verification
npm testpassed with 719 tests.npm run check,npm run build, andgit diff --checkpassed.