Kjell Tore Guttormsen
0874188fe4
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.
7 lines
154 B
Markdown
7 lines
154 B
Markdown
---
|
|
name: shared-cmd
|
|
description: A command whose name is shared across two differently-named plugins
|
|
model: sonnet
|
|
allowed-tools: Read
|
|
---
|
|
Do the thing.
|