Add cross-SDK allow-disposition conformance test (SAN-765)#85
Merged
Conversation
Drives an allowed (can_execute) action through the HTTP and subprocess interceptors in enforce mode and asserts the emitted receipt matches the shared protocol fixture (allow_disposition_vectors), including assurance=partial per spec Section 7.3. Companion to the escalate-disposition conformance suite and the Section 7.3 verifier enforcement; both SDKs now assert the same allowed-path vector. action_hash is not pinned (the executed action's output hash is environment-dependent).
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.
Summary
Adds the allowed-path half of the cross-SDK disposition conformance suite (SAN-765). It drives an
allowed (can_execute) action through the HTTP and subprocess interceptors in enforce mode and
asserts the emitted receipt matches the shared protocol fixture
(spec/fixtures/multi-surface-vectors.json -> allow_disposition_vectors), including
assurance=partial per spec Section 7.3.
This is the allowed-path companion to the existing escalate-disposition conformance suite and to
the Section 7.3 verifier enforcement. Both SDKs now assert the same allowed-path vector, closing
the cross-SDK loop on the prior TypeScript 'full'-for-allowed divergence. action_hash is not pinned
in the fixture (the executed action's output hash is environment-dependent); the consumer honors
the fixture's not_pinned list.
Test plan