mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-11-09 20:07:43 +08:00
Tianyi Cui
371c804336
The expected-output CI lane sets DSH_EXAMPLE_MODE=lib. Selecting tsx/esm alone did not exercise the source bin there, and the compatibility test only checked --help, so removing source profile link resolution could silently restore duplicate source/lib Tools instances in a green CI run. Run the existing real headless-profile tool round trip explicitly in both src and lib modes. The explicit mode overrides the CI environment default; the source case uses the supported tsx/esm entry. Both cases retain the real profile, shell tool, persisted Session assertions, stdout, and stderr expectations, with isolated temporary directories. No recorded generation or output normalization changes are needed. After a full build, both cases pass with DSH_EXAMPLE_MODE=lib. Negative control: removing only the source bin link-resolution selection makes the source case fail at scheduler.prepare while the built case still passes. Restoring the implementation makes both cases pass again. Scoped lint passes. This puts the regression in the existing post-build expected-output CI lane without adding artifact requirements to compatibility-only jobs.