Repository navigation
Prepare production OAuth plugin distribution - #12
Draft
hiOpenmart wants to merge 2 commits into
Draft
hiOpenmart wants to merge 2 commits into
hiOpenmart wants to merge 2 commits into
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.
Prepare production plugin artifacts so distribution no longer depends on a developer's manually edited Codex cache. The packager creates separate portal and Codex marketplace ZIPs against https://api.openmart.ai/mcp, takes an explicit public OAuth client ID, and copies only the five skills, logo and manifests. No credentials or internal docs are packaged.
Add deterministic archive checksums, review test-case drafts and Beta installation/acceptance instructions. The README separates the hosted OAuth plugin from the legacy API-key MCP server. This PR does not ship the old Node plugin prototype or change the existing npm runtime.
Validation: production packaging tests verify repeatable checksums, artifact layout, production URL, no private/staging content, and rejection of forbidden credential text. The portal accepted the initial 0.2.1 draft and all five skill checks passed. New-account installation, portal OAuth/domain verification, executed review cases and a video remain release gates; no public-directory approval or customer release is claimed.