Add payload-free tool cycle disposition events - #2187
Draft
Aaronontheweb wants to merge 2 commits into
Draft
Aaronontheweb wants to merge 2 commits into
Aaronontheweb wants to merge 2 commits into
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
This change adds one shared, payload-free disposition event for each evaluated tool batch candidate.
The event reports these fields:
The event applies to parent and child actors.
Executemeans entry into the execution pipeline. It does not prove successful tool execution.CorrectandStopnever dispatch. Approval redrive emits no second candidate event.The exact cycle guard and the 60 and 30 iteration caps stay unchanged. The events are process-level diagnostics, not per-session correlation entries. The operations skill version also changed.
Verification
This pull request is draft.