Repository navigation
make/publish-app: document the public-review submission flow - #5
Merged
Merged
Conversation
Portable generator for the chatgpt-app-submission.v1.json the ChatGPT App directory portal wants, plus the schema + end-to-end process learned shipping Content Rabbit (per-tool annotations+justifications, domain challenge, dev-mode vs public, verified-identity gate, 10KB icon).
Add a 'Submitting for public review' section: publish is permanent, set modules visible, the review form needs an API-docs link + one successful-run scenario per module + one error scenario (built manually — the Scenarios API can't make them meaningfully pass), plus logo/contact/terms. Note which code requirements the script already satisfies so the review won't bounce on them.
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 a 'Submitting for public review' section to the README: publish is permanent, set every module visible, the review form needs an API-docs link + one successful-run scenario per module + one deliberate error scenario (all built manually — the Scenarios API can create empties but can't make them meaningfully pass, and modules have side effects), plus logo/contact/terms. Lists which code requirements the script already satisfies so the review won't bounce on them. Makes the full build→submit path clear for anyone reusing the tool.