What problem does it solve? Testing a standalone DSH plugin requires proving many distinct behaviors—Loader export unwrapping, configuration validation, registration disposal, composition, snapshots, and built artifacts—and it is easy to either miss critical evidence or waste effort on redundant tests. This Skill maps each promised behavior to the narrowest test that would fail for the regression. ## Core Features & Use Cases - Evidence Mapping: Builds a behavior-to-test mapping covering Loader exports, config defaults and rejections, lifecycle disposal, invariants, composition, visible output, and distribution paths. - Real Composition Testing: Requires a non-unit test that boots a real Cordis composition through the actual Loader, catching wrong package names, missing peers, and boot-order defects. - Artifact Verification: Runs verify, typecheck, test, build, and prepare commands, then imports built entries from lib/ under plain Node to confirm ESM exports. - Use Case: After adding a new configuration option to a DSH plugin, use this Skill to identify exactly which test files and assertions prove the default, explicit values, and rejection paths without running the entire suite blindly. ## Quick Start Use the dsh-plugin-test skill to select and run the smallest complete set of tests proving this plugin's Loader exports, disposal, and composition behavior.
