Repository navigation
fix(agent): revalidate OpenAPI after public policy contradictions - #38
Merged
nkavian merged 1 commit intoOct 17, 2026
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
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
Re-fetch OpenAPI when a validated AEP challenge contradicts a public operation policy. Keep metadata retrieval anonymous and continue the existing authentication flow if refresh fails. Cancellation still stops the request.
Distinguish public policies from unsupported mappings internally without adding a public API or a document cache.
Verification
make verifymake conformance interoperabilityThis does not add resource retries or automatic enrollment.