Commit Graph

2 Commits

Author SHA1 Message Date
2c50d1e79e feat: 0.4.3 - precise conflict detection (read actual config ids, not package names)
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.
2026-11-17 14:53:13 +08:00
4c96f28f53 docs: 0.4.2 - add COMMENTS-FAQ.md, a line-by-line answer to the comment section
Eleven comments from the video, each marked resolved / partially resolved /
cannot be resolved, with a pointer to the file that handles it.

Honest status:
- 9 resolved (install, verify, purge conflict, "second fork", missing binaries,
  model gets dumber, not-working)
- 1 partially resolved (safety refusal: host permission fixed, model layer
  fixed, server-side moderation improved by provider switch + layer 6 but not
  removable)
- 1 cannot be resolved (the one about bypassing limits on minors - out of scope)
2026-11-17 14:47:42 +08:00