Literal definition: a plugin declares its supported host version range in engines.dsh inside package.json; when the host falls outside it, the plugin stays listed but is not loaded.
Measured: reading every package.json for the 223 packages under ~/.dsh/profiles/node_modules, zero declare engines.dsh. Not one official package declares it.
So on this version there is no observable evidence of the gate as a mechanism: nothing declares it, so nothing can be blocked by it. The 'rejected by the version gate' entry in /fix/ comes from a community plugin's CHANGELOG and is a compiled claim, not our measurement.
Then how does incompatibility show up
On this version, observable compatibility problems come from two places:
- Host engines.node: the node requirement in package.json,
>=24.9.0from 0.2.2. This one genuinely applies. - Dependencies failing to install: the plugin's own dependencies break during pnpm install, so it fails at install time rather than loading and being skipped.
How to use this
When you meet a claim like 'the version gate rejected it', ask three questions: which file declares it, where the host checks it, and what refusal looks like. If none can be answered, treat it as a community claim, not a troubleshooting step.