Repository navigation
fix: reject blank semantic tokens and padded identities - #32
Merged
Merged
Conversation
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
semantic_rules[].tokenswhile preserving meaningful spaces inside code tokens.id,plugin_id, andtopicfields.Why
A whitespace-only token can match ordinary source lines and produce misleading
pattern_observed_control_flow_unverifiedevidence. Padded identity fields can also silently fail exact matching against plugin IDs and clause/rule references.Boundaries
Validation
Python 3.10–3.13, MCP stdio E2E and Sample Project Advisory.