Repository navigation
feat(workbench): add authenticated HTTP checking policies - #140
Merged
Merged
Conversation
Negotiate an exact authenticated HTTP mapping and retain the selected Scheme plan through acceptance, worker claims and reconnection. Qualify boundaries, clients and actual provider workers with independent parent MCK fixtures; preserve frozen strict and native contracts.
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.
Authenticated HTTP executions can now offer the same explicit checking policies as standalone and desktop evaluation. The exact host
0.2.0-draft.2mapping captures the selected Scheme provider, policy, inputs and public boundary before acceptance. Real isolated workers claim that plan once, and the client validates returned plans and typed terminals against the captured selection.The connected Model Explorer enables policy controls only for a qualified offer. Frozen strict HTTP and native mappings retain their contracts. Rust connected v1 still advertises
executions:false; its actual authentication, Gleam compilation/generation and workspace behavior are qualified separately.Validation:
Beads:
morphir-etg2.16.6. The parent protocol schemas, normative HTML and independent fixtures ship in finos/morphir#1064. HTML plans and evidence stay in beads and ignored.dev/artifacts.