Expand WebMCP to the full standard Skin V1 surface catalogue - #2052
Merged
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
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.
Refs #2030.
This is the infrastructure/capture pass for the Human-approved WebMCP surface registry. It intentionally does not auto-close #2030 because Human visual approval and baseline locking remain explicit.
What changes:
The existing core WebMCP visual-conformance audit remains in place; the expanded catalogue runs in the same startup/Architecture Verification path and uses the same manifest/locking convention.
Merge only when exact-head Architecture Verification is green. After merge, run WebMCP locally and visually review the 12 candidates before the final #2030 closeout.