dsh-plugin-boundary

The most underrated step in DSH plugin development is not the first line of code but a simple feasibility check: which data channels are officially supported, which are undocumented workarounds that happen to work, and which are architecturally impossible. That knowledge is scattered across source code, issue threads, and community experience with no single reliable reference at hand. This plugin packages those boundary conclusions into one loadable skill so you can run a quick sanity check before you start coding.

Registered via ctx.skills.registerProvider, the skill covers four core areas: the full landscape of client-to-host data channels, official API filesystem limits, lifecycle differences between dynamic and bundle plugins, and the hard rules that govern the install, effect, and debug phases. Structurally it is a SKILL.md (purpose, load timing, usage points) plus a set of rules/*.md files (the rule bodies), organized for quick, on-demand lookup.

If you are about to write or modify a DSH plugin, loading this skill first to walk through the boundaries can save you from shipping code that relies on undocumented behavior. Note that the conclusions were verified against DSH 0.1.0-rc.6, so re-checking critical rules after a DSH upgrade is strongly recommended.