feat: support installation as a DeepSeek Harness (DSH) plugin #670

What problem are you trying to solve?

Understand Anything currently ships as a plugin for Claude Code (.claude-plugin/), Cursor (.cursor-plugin/), and Copilot (.copilot-plugin/), each with a platform-specific plugin.json manifest plus skills/ and agents/ directories. However, it is not installable as a DeepSeek Harness (DSH) plugin, so users who run their agent tooling inside DSH cannot use /understand and the rest of the skill set through dsh.

Concretely, DSH installs out-of-tree plugins as npm packages into a profile's node_modules, where a package that declares dsh.bundle (a manifest field) joins the profile's dsh.profile.bundles layer stack and provides a cordis.patch.yml patch layer. Understand Anything has no such bundle manifest or patch layer today, so dsh plugin --profile <name> pnpm add <understand-anything> does not activate anything.

Proposed solution

Add first-class DeepSeek Harness plugin support alongside the existing Claude/Cursor/Copilot plugin manifests:

• Add a dsh.bundle declaration (with a patch field) to the plugin's package.json so DSH recognizes it as a bundle and joins the profile's layer stack.
• Ship a cordis.patch.yml patch layer that registers the /understand skills (and related /understand-* skills) and any agents so they load inside a DSH profile.
• Document the install steps in the README, e.g.:

  dsh plugin --profile <name> pnpm add <package-name>
  

• Mirror the existing versioning convention (the same version field kept in sync across all plugin manifests) for the new DSH manifest.

This keeps the project's "one source of truth, multiple agent platforms" model and lets DSH users get the same codebase-understanding experience as Claude Code / Cursor / Copilot users.

Alternatives you've considered

• Manual/manual-command usage only: Users could invoke the underlying analysis scripts directly without a DSH plugin, but they lose the /understand skill UX, agent pipeline, and dashboard integration that the other platforms get.
• Vendor a separate DSH-only package: A dedicated wrapper package that depends on the core engine and just adds the DSH patch layer. This works but adds a second package to maintain and version in sync.
• Do nothing: DSH users simply cannot install it as a plugin and must use another agent platform or run the tool standalone.

Which part of the project?

skill (the /understand skill set and skills/ definitions), plus the plugin packaging/manifests (understand-anything-plugin/package.json, and the plugin manifest/versioning convention shared across .claude-plugin/, .cursor-plugin/, .copilot-plugin/).