feat: support for DeepSeek harness (dsh) runner

[chatterzhao]

Hi there,

First of all, thank you for building such an amazing self-evolution engine! Evolver's GEP-based approach is really impressive.

I'm writing to ask about the possibility of supporting DeepSeek harness (dsh) as a runner in the path. Currently only claude|codex|gemini are supported, and I noticed issue #627 discussing third-party runner plugin mechanisms.

Are there any plans or progress on adding DeepSeek harness support? If there's an existing roadmap or discussion thread I might have missed, I'd appreciate being pointed in the right direction.

Thanks for your time, and keep up the great work! 🙏

[imxyanua]

Thanks for the suggestion! Support for DeepSeek Harness (dsh) is a useful request and closely relates to the extensible runner support discussed in #627.

DeepSeek Harness provides headless and SDK entry points that look promising for an Evolver adapter. The integration would need to cover the full execution lifecycle: workspace isolation, credential handling, timeouts, cancellation, cleanup, and structured results.

A proposed path would be:

1. Verify the current cycle capability gaps described in cycle execute/verify is fail-closed for every runtime; no plugin mechanism for third-party runners (e.g. Pi) #627 and define a reusable external-runner contract.
2. Implement a dsh adapter against that contract.
3. Test the complete cycle flow with real tasks, including independent validation and failure recovery.

Since DeepSeek Harness is currently in developer preview, the integration should also specify and test supported versions.

I suggest using #627 to track the shared runner contract and this issue to track the DSH integration. This is a proposed direction; implementation scope and timing still need to be confirmed.