Repository navigation
Add reviewed certificate metadata changes - #236
Merged
Merged
Conversation
chen21019
force-pushed
the
feature/webmcp-certificate-metadata-release
branch
2 times, most recently
from
October 30, 2026 04:28
75fcbc7 to
746a0b7
Compare
chen21019
force-pushed
the
feature/webmcp-certificate-metadata-release
branch
from
October 30, 2026 04:29
746a0b7 to
3350a56
Compare
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.
Certificate changes currently require the manual form. Add name/description edits through the existing query, preview, human confirmation and apply workflow, with opaque resource references and the original role, Key, ownership and CAS checks. PEM, private keys and chains remain in the human UI.
Package Web Console 1.6.202 / bridge 0.2.4 and enroll the new regression in official CI and the bridge source archive. Twelve public tools remain. Requires the matching Engine certificate and audit integration.
Validation: four focused certificate cases, two checker cases and the real paired wire contract passed. Independent scoped source review found no blocker. Required full producer and CodeQL checks are pending; runtime and complete frontend acceptance are not claimed.