Files
deepseek-harness/packages/examples
Tianyi Cui d8dbb8235c refactor(acp): launch automation through the dsh acp profile
Replace the standalone @deepseek-ai/dsh-acp-demo application with dsh --profile acp plus ordered example patches. The shipped acp-app bundle owns only the protocol bridge; every example overlay now targets shared dsh-base rows instead of copying a complete application tree.

Move launcher responsibilities into the ACP snapshot harness: it materializes profile patches, links required packages, reserves stdout for JSON-RPC, observes spawn and drain failures, and escalates process teardown deterministically. The relocated control-surface fixture and the ACP/subagent integration tests now exercise the real CLI/profile path.

This commit contains authored runtime, configuration, and test changes only. Generated transcript and projection churn is deliberately left for the next commit so reviewers can inspect the migration logic without hundreds of expected-output edits.
2026-08-23 10:59:00 +08:00
..
2026-08-21 19:48:58 +08:00
2026-08-21 19:48:58 +08:00

examples/ — ready-to-run demo bundles

English | 中文

Pre-composed plugin bundles a thin leaf cordis.yml loads instead of assembling the spine and an entry point by hand. These are demo / reference packages — the -demo npm suffix marks each one as non-product surface, readable straight off the package name. The runnable leaves under the repo-root examples/ and the Python SDK runtime are the consumers; each is just its swappable backends plus one bundle entry.

Package npm name Role
agent-spine-demo/ @deepseek-ai/dsh-agent-spine-demo Reusable agent-spine bundle
acp-demo/ @deepseek-ai/dsh-acp-demo ACP automation application bundle
jsonrpc-demo/ @deepseek-ai/dsh-sdk-jsonrpc-demo External-config JSON-RPC runtime

agent-spine-demo is the shared bundle; acp-demo adds its automation entry point, while jsonrpc-demo boots a deployment-owned plugin tree. Product one-shot execution belongs to dsh --profile headless; no package in this directory provides it.

These packages are not product API. Product seams and entry points remain in their owning groups; demo bundles select concrete compositions.

Do not confuse this group with the repo-root examples/: that directory holds the runnable cordis.yml leaves; this group holds the bundles those leaves load.