Repository navigation
Place shared request policy in the headless application - #190
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
The SDK and reserved-run worker currently import request validation from a module named for the MCP transport, obscuring which layer owns the safety gate. This moves that policy into the headless application, points application callers at it, and keeps
mcp_policyas a compatibility import for existing hosts. The policy behavior is unchanged. A drift-guard test now forces its intended import failure instead of depending on whether this development environment hasvllminstalled.Validation: focused SDK/MCP/contract/packaging tests passed; the full local suite now passes, and strict SPEC coverage/freshness passes, and an installed-wheel smoke confirms the legacy and application policy imports resolve to the same callables. An environment-sensitive drift-guard test was made deterministic after the same failure was reproduced on unchanged main. CI validates the complete branch.