v0.3.3 — DSH 0.2.2 compatibility

Why

DSH desktop upgraded to 0.2.2-rc.1, which the old engines.dsh: >=0.2.1-rc.1 <0.2.2-0 range rejected. The loader marked the bundle incompatible-version, inserted no rows, and the whole second Go connection disappeared from the app after the upgrade.

What changed

• engines.dsh and the DSH peer ranges now read >=0.2.1-rc.1 <0.2.3-0, so 0.2.1-rc.x and 0.2.2-rc.x both load.
• @deepseek-ai/schemastery peer widened to >=3.18.5 <3.20.0; DSH 0.2.2 ships 3.19.0.
• Tests now run against @deepseek-ai/dsh-llm-pi-ai@0.2.2-rc.1; every public symbol this plugin imports still exists and behaves the same.
• The fake host context used by the interleave test implements the cordis 4.1 waterfall hook that the native pi-ai adapter now calls while preparing request headers.

Plugin behavior, routes, stored credentials, saved model selections and manual-only model refresh are unchanged.

Validation

24 local tests pass against the 0.2.2-rc.1 packages (including the real PiAiAdapter header path and 38-model protocol matrix); npm ci accepts the refreshed lockfile; package-lock.json and the release tag agree on 0.3.3.