Huanqi Cao
be4a441ecd
The ::warning:: wrapper kept the lane job green on failure — honest about not gating merges, but a Windows regression was visible only as an annotation buried in the run summary. GitHub has no yellow job state, so the choice is green+annotation (too hidden) or a red X on a non-required job (visible, still non-blocking). Take the red X: job-level continue-on-error, plain 'Run gates' step, one less wrapper. The step stays on the runner's native pwsh — never shell: bash — per the MSYS-parent leak recorded in the windows-support RFC. Also remove the temporary Windows-only failing demo test that exercised the wrapper's annotation path (REVERT ME commit a496b9ae).
DeepSeek Harness
English | 中文
The DeepSeek Harness SDK is a plugin-based SDK for building agent harnesses.
Development
This monorepo is built on the Cordis framework (vendored as source under vendor/), microkernel-style: everything is a plugin.
pnpm install
pnpm run test # vitest
pnpm run demo:repl # REPL agent demo (needs DEEPSEEK_API_KEY)
pnpm run demo:acp # ACP server agent demo (needs DEEPSEEK_API_KEY)
For humans, start with the development guide for local setup, hooks, environment variables, and quality gates, then read the architecture design and documentation graph index before package work. Local context lives in packages/ and vendor/.
For agents, follow AGENTS.md.