Repository navigation
feat(submission): prepare MCP-only ChatGPT plugin candidate - #28
Draft
lukas-bekr wants to merge 2 commits into
Draft
lukas-bekr wants to merge 2 commits into
lukas-bekr 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 a separate MCP-only Apify package for the planned ChatGPT submission while preserving the existing
apify/developer distribution. The candidate uses 29 individually named tools on the existing root MCP endpoint, includes Web Search/Web Fetch, and packages exactly the portable plugin manifest, generated MCP configuration, and PNG logo. An explicit archive allowlist prevents skills, hooks, private bindings, and review notes from entering the ZIP.The package includes five positive and three negative review cases, a thirteen-Actor/private-development test matrix, and explicit readiness gaps. It is not ready to submit: the server aliases are not deployed, curated builds are unapproved, live review cases and OAuth remain untested, and a fresh demo, commerce/legal review, and written OpenAI clearance are still required. The publisher selected all portal-supported countries, encoded as an explicit empty country restriction list; verify its import in the portal. The repository metadata retains the current verified URL until an administrator performs the rename.
The manual developer-release workflow now accepts the old/new repository names only for the same immutable repository ID. Coordinate the upstream sync guard first, then rename the existing repository rather than creating a replacement. No rename, release, portal upload, or submission is performed by this PR.
Validation: nine packaging tests pass, including symlink/tampered-archive and accidental skill/hook exclusion cases. The deterministic ZIP was built and inspected; its 29 selectors match the MCP server candidate. Local structure checks do not establish portal acceptance or runtime behavior.
AI assistance: Codex implemented and tested the candidate. Submitted from a fork because the connected account has read-only access to the upstream repository.