Choose a compatible DSH plugin

Start with your environment

Match the operating system and DSH profile first. A plugin documented for Web may not expose the same behavior in Headless or a terminal profile.

• DSH version or commit.
• Profile and bundle stack.
• Operating system and architecture.
• Node and package-manager versions.
• Required local services, credentials, and browsers.

Prefer reproducible evidence

A dated successful install against a named DSH version is more useful than a broad compatible badge. Look for the command, environment, expected output, and the smallest runtime smoke test.

Inspect the composed configuration

DSH profiles are ordered bundle layers plus user patches. Dump the resolved tree to confirm that the plugin inserted the expected rows and did not unexpectedly replace another service.

dsh --profile plugin-test --dump-config

Separate unknown from failed

An untested platform is not a pass and not necessarily a failure. Keep unknown, limited, maintainer-reported, repository-tested, and independently-tested evidence visibly distinct.

Keep a rollback path

Use a separate profile, pin the installed revision, preserve your current patch files, and verify the remove command before trusting a plugin with important work.