docs: clarify core vs optional workflows and add MCP-server variations to ci-cd.md#61
Merged
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
8 tasks
…s to ci-cd.md Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.com>
The MCP-server Variations section opened with "follow the same core requirement as cursor-plugin repos," implying validate.yml was required. It is not. All validate.yml checks assume plugin.json; mcp-server repos have no plugin.json. Rewrites the section to state the three required workflows explicitly (drift-check.yml, stale.yml, publish.yml) and explains why validate.yml is absent. Also updates the doc intro to distinguish cursor-plugin (four required) from mcp-server (three required). This brings the prose into exact agreement with the machine-readable config in standards/drift-checker.config.json. Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com> Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.com>
TMHSDigital
force-pushed
the
docs/clarify-workflow-standard
branch
from
7f39642 to
9966ab9
Compare
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
pages.ymlfrom the required core workflow list; it is generated by the scaffold by default but is not required for every repo type.drift-check.ymlas the third required core workflow (alongsidevalidate.yml,release.yml, andstale.yml), matching what all nine tool repos already have.pages.ymlandlabel-sync.ymlto the optional workflows table with explicit notes that the scaffold generates them by default.## MCP-server Variationssection documenting that MCP-server repos substitutepublish.ymlforrelease.yml, may omitpages.yml, may omit plugin-manifest validation checks invalidate.yml(noplugin.json), and still requiredrift-check.ymlandstale.yml.Motivation
The prior drift audit found that
ci-cd.md, the scaffold output, and the drift checker disagreed about which workflows are required. The scaffold generateslabel-sync.ymlandpages.ymlby default, but neither the standard nor the checker treated them as required.drift-check.ymlis present in all nine tool repos but was not listed inci-cd.mdat all. This PR makes the standard authoritative.Version note
This is a
docs:commit; CI does not require aVERSIONbump. However, this change settles a surface-level ambiguity in the standards and is exactly the kind of clarification thatstandards/versioning.mddescribes as warranting a MINOR bump and a re-alignment rollout. Deferring that decision to the maintainer. If you decide a MINOR bump is warranted, bumpVERSIONin a follow-upchore:commit on this branch before merging, or open a separate PR after this lands.Test plan
python scripts/sync_from_registry.py --checkexits 0Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com