Repository navigation
feat(rules): add MCPCFG-003 unpinned MCP package launch - #198
Merged
Merged
Conversation
ivanpaghubasan
requested review from
ericksondelacruz,
jhumel-code and
sairenchristianbuerano
October 21, 2026 10:25
sairenchristianbuerano
approved these changes
Oct 21, 2026
ivanpaghubasan
marked this pull request as ready for review
October 23, 2026 10:23
…ned-mcp-launch # Conflicts: # manifest.yaml
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.
Summary
Adds MCPCFG-003 (high, 0.7, scope repo) to
agent_config/mcp_client_config.yamland bumps the manifest to schema 28. The second commit changes the MCPCFG-002
explanation to point to MCPCFG-003 for unpinned packages.
Schema version
28 is provisional (CSDK-115 / #197 holds 27). The later PR to merge renumbers.
Dependencies and order
Needs the engine PR (predicate
repo_mcp_config_launches_unpinned_package).Merge order: engine, rules, rulebook. Do not merge before the rationale-doc PR
is ready, since the strict gate fails on a shipped rule without a doc.
Notes
The rule file is byte-identical to the engine fixture copy.
attestations.json*and
badges/are untouched.