Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/master' into worktree/minimal-profiles-bare-runtime

Browse Source 
# Conflicts:
#	examples/jsonrpc-agent/README.i18n.yaml
#	examples/jsonrpc-agent/README.md
This commit is contained in:
Yichen Jiang
2026-08-11 15:51:03 +08:00
parent 663253099d 5d591e55c1
commit 2b5c17ab6b
650 changed files with 1831 additions and 1446 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
examples/jsonrpc-agent/README.i18n.yaml
View File

@@ -2,5 +2,5 @@
# side as of the last confirmed-consistent state. Both languages carry equal authority;
# after editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write examples/jsonrpc-agent/README.md
README.md: 93ac1d4bc966568d2baab70f763394d1293d348f
README.md: 9eb37fd29442dc40c7a17cd266c225e6750a6886
README.zh.md: f358d3c8b22017a10dff62ce2dedced2bfd6de6c

2
examples/jsonrpc-agent/README.md
View File

@@ -2,7 +2,7 @@
English | [中文](README.zh.md)
The unattended coding-agent composition for the Python SDK's bundled JSON-RPC runtime. It intentionally loads no terminal UI, console logger, approval surface, or user-interaction tool because stdout belongs to the SDK protocol and turns are driven by the SDK.
The unattended coding-agent composition for the Python SDK's bundled JSON-RPC runtime. It intentionally loads no terminal UI, console logger, approval UI, or user-interaction tool because stdout belongs to the SDK protocol and turns are driven by the SDK.
The model-facing tools are:

4
examples/jsonrpc-agent/tests/sdk.snapshot.ts
View File

@@ -2,8 +2,8 @@
* Keyless snapshot coverage for the TypeScript SDK path: each scenario spawns
* the REAL `dsh-jsonrpc-agent` runtime (per `DSH_EXAMPLE_MODE`) through the
* REAL `@deepseek-ai/dsh-sdk-client`, drives one turn over stdio JSON-RPC,
* and pins three surfaces — the SDK `RunResult`, the complete notification
* stream, and the persisted session logs. Replay serves recorded model
* and pins the SDK `RunResult`, the complete notification stream, and the
* persisted session logs. Replay serves recorded model
* responses via `llm-replay` (`cordis.snapshot.yml`); `DSH_SNAPSHOT=record`
* re-records against the live API; `DSH_SNAPSHOT=refresh` replays committed
* fixtures and rewrites expected outputs.