What problem does it solve? Standalone DSH plugins need proof that their Loader exports, configuration, lifecycle disposal, composition, visible output, and built artifacts actually work, but running every repository test wastes effort while missing the narrowest test that would catch a regression. ## Core Features & Use Cases - Evidence Mapping: Builds a behavior-to-test mapping covering Loader unwrap paths, config defaults and rejections, registration disposal, invariant companions, composition, snapshots, and artifact imports. - Composition Testing: Requires a real Cordis composition booted through the actual Loader and application path, mocking only external services, credentials, time, and randomness. - Artifact Verification: Runs verify:self-contained, typecheck, test, build, and prepare, then imports each public runtime entry from lib/ under plain Node. - Use Case: After adding a new slash command to a DSH Web plugin, use this Skill to select the exact test files proving Loader export, disposal, and browser-visible behavior before claiming the package is tested. ## Quick Start Use the dsh-plugin-test skill to select and run the smallest complete evidence for this standalone DSH plugin.