The old heuristic matched names like purge|ungate|jailbreak and reported
dsh-purge as a sibling. That was wrong: dsh-purge patches host source, it does
not touch approval/permission config ids at all.
Now the plugin reads every installed bundle's cordis.patch.yml, extracts the
config ids it actually rewrites, and intersects with its own set:
hardConflicts - other plugin rewrites approval/permission/sandbox-policy/...
-> last-applied wins, one silently stops working -> pick one
softOverlaps - other plugin only rewrites system-prompt (identity prefix)
-> negligible difference -> safe to coexist
Measured on this machine (22 bundles): scanned 19, hardConflicts [],
softOverlaps [{dsh-purge, system-prompt}]. So dsh-purge and this plugin do NOT
conflict.
Answers the issues raised in the comments:
1. "keeps triggering safety refusal" -> README now separates three layers:
host permission (this package fixes it), model willingness (prompt layer),
provider-side moderation (nothing can fix it). TROUBLESHOOTING gives a
decision tree with commands.
2. "how do I verify it worked" -> doctor.ps1 checks 11 items and prints
[OK]/[WARN]/[FAIL]. Verified locally: OK=11 WARN=2 FAIL=0.
3. "does it conflict with purge" -> documented: both target the same config
ids, last-applied wins. doctor warns when a user-layer override or a
conflicting plugin is detected.
4. "incomplete / missing stuff" -> documented that the 63 skills need their
external binaries (nuclei/fscan/IDA/jadx...), which the package does not ship.
5. "stronger armor makes the model dumber" -> confirmed in README as a real
trade-off with per-layer guidance on what to turn off.