Make the Cursor listing overlay conform again - #35
Merged
Conversation
PR #33 grew the Cursor manifest with homepage, repository, license, keywords, and logo, and bumped it to 1.0.0. The conformance validator only accepted the thin manifest and the packer requires every host to share the root release version, so main has been red since. Accept the listing manifest shape explicitly, pin the version back to the shared release version, and update the README tool count to 30.
ericjuta
added a commit
that referenced
this pull request
Sep 3, 2026
#35 restored the Cursor overlay so the listing shape would conform. Keep the overlay deleted: Cursor is a root host. Keep listing version 1.0.0, take the public-boundary README wording, and drop the duplicate overlay validator.
5 tasks
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.
main CI has been red since #33 landed: the Cursor manifest gained homepage, repository, license, keywords, and logo and moved to 1.0.0, but the conformance validator only accepted the thin manifest and the packer requires every host manifest to carry the root release version.
Proof on this head: bun run check, bun run test (135), bun run check:target-conformance (160/160), bun run verify:artifacts all pass.