Repository navigation
feat(runtime): add owner-scoped extension presentation contributions - #29
Merged
Merged
Conversation
Codex Review Summary: ❌ FailedThis 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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
Implement the Runtime-owned semantic contribution path for extension panels and prompts. Extensions use owner-scoped contributions instead of publishing arbitrary UI snapshots directly to Backend.
Changes
label,text,list,tree,buttonandinputwidgets;valuehandling;core.ui:register_panel,update_panel,remove_panel,set_promptandclear_promptmethods backed by RuntimeUIModel.core.ui.publishis not exposed to extensions by default. A trusted host may explicitly opt in withallow_legacy_extension_ui_publish = truefor migration only; that path is outside the stable Extension Contract and must not be enabled for untrusted extensions.Spec traceability
Verification
Exact latest head
1b42779cfc3c78035fa182a7ca928d2d7e85809d:Capability boundary
This PR implements the Runtime-side semantic source and validator. It does not advertise
ui-presentation/1, render widgets, or claim Backend/Frontend conformance is complete. Interactive widget use remains unavailable until the corresponding Backend and Frontend implementations pass shared vectors and the capability is explicitly accepted in HELLO_ACK. The optionalcanvascapability remains separate.