fix(plh): downgrade cross-plugin command-name overlap to low ambiguity
Commands are namespaced (/name:command), so a command name shared by two differently-named plugins keeps both reachable — it is ambiguity, not a hard conflict. The check now mirrors COL's plugin-vs-plugin skill finding: severity LOW (was HIGH), category plugin-hygiene, COL-shaped details.namespaces, and a group-first shape (one finding per command name listing every namespace, not pairwise). It keys on the declared namespace (was folder basename) and fires only across 2+ distinct namespaces — when plugins share a declared name, the namespace-collision finding (medium) is the right signal, so this stays silent. Removes the inaccurate "only one wins" humanizer entry. Adds fixtures (duplicate-command-name; a shared command in duplicate-plugin-name's colliding namespace) and 4 tests. Suite 932->936. self-audit A 97 / A 100, scanners 13.
This commit is contained in:
parent
c6c5f17752
commit
0874188fe4
13 changed files with 160 additions and 27 deletions
1
tests/fixtures/duplicate-command-name/two/.claude-plugin/plugin.json
vendored
Normal file
1
tests/fixtures/duplicate-command-name/two/.claude-plugin/plugin.json
vendored
Normal file
|
|
@ -0,0 +1 @@
|
|||
{ "name": "plugin-two", "description": "Declares namespace plugin-two", "version": "1.0.0" }
|
||||
Loading…
Add table
Add a link
Reference in a new issue