chore: add .cursor-plugin/plugin.json manifest#5
Merged
Conversation
PR #4 onboarded the repo to standards 1.10.0 but never added the plugin manifest, so the ecosystem drift checker still classified the repo as 'unknown' (_detect_repo_type keys off .cursor-plugin/plugin.json). That left stale.yml and the @v1.15 refs present but unenforced, and mismatched the registry's "cursor-plugin" type. - Add .cursor-plugin/plugin.json per the scaffold standard (name, displayName, description, version, author, license, keywords, and the 12 skill + 6 rule component paths). _detect_repo_type now returns cursor-plugin. - AGENTS.md: the overview asserted "no .cursor-plugin/plugin.json" as a fact; updated to state the manifest now ships and why (drift-checker classification). Verified locally with the meta-repo drift checker against this tree: repo_type=cursor-plugin, 0 errors / 0 warnings, required-workflows and required-refs both evaluated and passing. Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>
github-actions
Bot
added
the
documentation
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
1 participant
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.
Summary
Follow-up to #4. That PR re-stamped standards to
1.10.0, bumped workflow refs to@v1.15, and addedstale.yml— but never added.cursor-plugin/plugin.json. The ecosystem drift checker's_detect_repo_typekeys off that manifest, so the repo still classified as unknown, which meansrequired-workflowsandrequired-refswere silently skipped (the newstale.ymland current refs were present but unenforced) and the type disagreed with the registry'scursor-plugin.Changes
.cursor-plugin/plugin.jsonper the scaffold standard (the manifest CFX/Unity/Docker carry):name,displayName,description,version,author,license,keywords, and the 12 skill + 6 rule component paths._detect_repo_typenow returnscursor-plugin..cursor-plugin/plugin.json" as a fact about the repo. Updated to state the manifest now ships and why (drift-checker classification).keywordsuseblenderrather than the scaffold's stockmcpsince this repo has no MCP server.The real test (run locally against this tree with the meta-repo drift checker)
With the type now coherent,
required-workflowsevaluates and passes (validate/release/stale/drift-check all present) andrequired-refsevaluates and passes (empty requirement set for cursor-plugin) — not merely version-signal staying green.Test plan
plugin.jsonvalid JSON; all 12+6 component paths resolve to real files.repo_type=cursor-plugin, 0 errors / 0 warnings.validate.ymldoes not inspectplugin.json(additive, stays green).