fix: auto-dispatch incident code workers#7
Merged
Conversation
Dispatch incident_new and incident_regressed events directly through CallCodeWorkerTool instead of relying on the leader LLM to decide whether to call the tool. Persist observable activity log entries for incident dispatch, prevent duplicate in-progress code worker calls for the same incident, and keep worker/reviewer aggregate output visible when a chat_response is also present. Sanitize worker job path segments so incident thread ids such as incident::fingerprint work on Windows and Linux. Add deterministic incident auto-dispatch coverage verifying leader-task bundles, full traceback propagation, ecommerce repo targeting, duplicate-dispatch prevention, and platform-aware worker runtime assertions.
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.
Dispatch incident_new and incident_regressed events directly through CallCodeWorkerTool instead of relying on the leader LLM to decide whether to call the tool.
Persist observable activity log entries for incident dispatch, prevent duplicate in-progress code worker calls for the same incident, and keep worker/reviewer aggregate output visible when a chat_response is also present.
Sanitize worker job path segments so incident thread ids such as incident::fingerprint work on Windows and Linux.
Add deterministic incident auto-dispatch coverage verifying leader-task bundles, full traceback propagation, ecommerce repo targeting, duplicate-dispatch prevention, and platform-aware worker runtime assertions.