Plugin X is incompatible with dsh Y
The plugin declares an engines.dsh range and your CLI is outside it, so it is skipped at boot rather than loaded into a combination that may crash.
The message names both versions, which is enough to decide without guessing.
The error, verbatim
It reads like "Plugin dsh-client-ui-aqua@1.3.1 is incompatible with dsh 0.2.1-rc.2".
What to check, most likely first
The plugin was published for a newer dsh line than yours. engines.dsh in its package.json is the authority, not the README.
You are on a release candidate and the plugin pinned a narrow window, for example >=0.2.2-rc.1 <0.2.3-0.
Two plugins in the same profile disagree about the range, so one of them can never load while the other is installed.
The two real options
Upgrade dsh to a version inside the range, or install the plugin version that matched your dsh. If you accept the risk for one package, allow that single version:
dsh plugin allow-version <package>If that does not settle it
Read the range from the tarball rather than the npm page: npm view <package> engines.dsh.
If the range excludes your dsh entirely, no allow-version will make it work; the plugin needs an update.
Common questions
Does allow-version patch the plugin?
No. It records an exemption for that package so the boot check passes; the code is unchanged.
Where is the exemption stored?
In the profile directory, alongside the profile manifest — which is why it does not follow you to another profile.