fix: suppress stale-counts for cursor-plugin type to unblock D-1#16
Merged
TMHSDigital merged 1 commit intomainfrom Apr 25, 2026
Merged
Conversation
The cursor-plugin tool repos use narrative aggregate descriptions in AGENTS.md and CLAUDE.md (e.g., "the skills/ directory contains 9 SKILL.md files"). These are intentional documentation, not stale data. The stale-counts check flags them as warnings, which now fails CI per the rc=1 propagation fix shipped in v1.7.4. Suppresses stale-counts at the cursor-plugin type level to match the existing mcp-server pattern (which already skips this check). This is a type-level suppression, not global; the meta-repo and any future repo types retain stale-counts. Interim decision; the underlying policy question (can stale-counts be made smarter to distinguish narrative from truth-bearing aggregates?) is tracked in #12 and remains open. Required to proceed with Phase 2 Session D D-1 rollout. See #1 Phase 2 Session D. Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com Made-with: Cursor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This was referenced Apr 25, 2026
Closed
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
Adds
stale-countstotypes.cursor-plugin.skip_checksinstandards/drift-checker.config.json, matching the existingmcp-servertype pattern. Type-level suppression only;globals.skip_checksis untouched so the meta-repo's own surface keeps the check.Why now
D-1 canary on CFX surfaced 2 pre-existing
stale-countswarnings inAGENTS.md(9 SKILL.md files,6 tools). Per the rc=1 propagation fix in v1.7.4, warnings now fail CI — so the new tool-repodrift-checkjob would go red on day one across all 8 plugin repos because each carries similar narrative aggregates. This was always the policy tension captured in #12.Interim decision: aggregate truth claims belong in CFX/Unity-style
validate-countschecks againstREADME.md. Agent files (AGENTS.md,CLAUDE.md) carry the same numbers as descriptive prose, not as truth-bearing data —stale-countsis too noisy to enforce on them today.Verification
CFX (with bumped signals in working tree) is clean. Steam shows only the expected
version-signalerrors that D-1 will resolve; nostale-countswarnings remain.Full test suite: 160 passed, 1 skipped (integration test, gated).
Test plan
pytest tests/passesVERSION
1.7.4→1.7.5(PATCH; policy refinement, no behavior change for any other check or any tool repo).Follow-up
After merge, force-update the
v1.7floating tag tov1.7.5so tool-repo composite-action consumers pick up the new config.Related