Repository navigation
Bind Responses verification results to issued tool calls - #69
Merged
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Runtime capabilities
Source commit: |
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.
Change contract
When: A Responses API client returns tool outputs to the local agent verification fixture.
Before: A session marker in a result for a missing or unrelated call ID can advance the allow/deny sequence. A result can also be accepted after a text-only response that never issued the call.
After: Results contribute evidence only when their call ID matches the issued phase call and that call was actually emitted. Valid conversation history remains accepted.
Boundaries preserved
Evidence
ab9083b68a24; report confirms 33 real-agent and three runtime cellsFailure and recovery
Uncorrelated results cannot advance the fixture trajectory and receive its existing rejection response. No retries or alternate evidence paths are added. Revert the fixture change and refresh native provenance to recover the previous implementation.
Remaining limits
The counterexamples concern the verification fixture's evidence admission. They do not demonstrate a production Controller bypass. Existing marker matching and result semantics for other model dialects remain outside this change.