Repository navigation
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.
Adds one plugin resource for Velox-XR/trifit-partner-api-example. Its public manifest is plugins/velox-trifit/plugin.json. The package supplies developer guidance and the remote virtual try-on MCP server at https://studio.v3lox.com/partner/trifit/mcp. Public API and SDK documentation is anonymous. Account and limited guest try-on tools require OAuth and user consent.
The existing main-branch package was installed in an isolated GitHub Copilot CLI profile. The native configuration reported the unified HTTPS URL and enabled version 1.2.1. This submission describes that plugin. GitHub MCP Registry curation for the standalone server follows its existing request separately.
The registered source and generated row are the only two file changes. The reviewed output adds exactly one resource to the upstream catalog. The generator also accepted it against a separate snapshot of the live registry. No server action, OAuth grant or image generation was used for validation.