Files
deepseek-harness/examples/AGENTS.md
Tianyi Cui 93a6dc6716 test(todo): add the todo-plan ACP snapshot scenario and a with-key e2e
Record the `todo-plan` snapshot scenario: a real prompt drives the model to call
todo_write, and the golden captures the resulting `plan` sessionUpdate (three
entries, priority synthesized as medium, status 1:1) plus the persisted
todo/write event. Registered in SCENARIOS; replays deterministically keyless.

Add a with-key coding-agent e2e that verifies the WORLD — a real model call to
todo_write lands a todo/write event whose snapshot is a valid, one-in-progress
list — not the agent's self-report. Wire tool-todo into the e2e harness.
2026-06-29 10:56:55 +08:00

3.7 KiB

AGENTS.md — Examples

Runnable demos that show how the harness is wired. Examples are NOT workspaces — each examples/*/package.json is a private, dependency-free stub with no build. They are booted as unbuilt tsx subprocesses via the cordis Loader reading a cordis.yml; the @deepseek-ai/dsh-* plugin names in those YAML files resolve through the root tsconfig.json paths map, not through node_modules.

Because examples are not under the packages/*/src coverage gate, an example that grows real, reusable logic should extract it into a packages/ package (where it gets the per-file 100% gate and a README). Keep only example-specific glue here: the cordis.yml wiring, demo-only mocks/teaching artifacts, and the e2e/snapshot scenarios. There is no start.ts — the boot glue (Loader tail, .env load, snapshot-mode selection, stdin-dispose lifecycle) lives in each app package's bin (@deepseek-ai/dsh-stdio-agent, @deepseek-ai/dsh-acp-agent), which the demo:* scripts invoke against the leaf cordis.yml.

Every example ships e2e smokes (keyless + with-key)

Each example must have both kinds of end-to-end smoke, because they catch different failures:

  • Keyless smoke — boot the example through its real cordis.yml via the Loader (no API key), drive it, and assert the rendered output and a clean exit. This is the guard a hand-mounted unit test structurally cannot be: it exercises the REAL load path (unwrapExports, inject, the whole plugin tree), so a broken plugin export shape — e.g. a stray export default that collapses a namespace plugin and drops inject — fails here even when unit tests stay green (see docs/postmortem/0001). It runs in the default e2e gate (CI has no secrets).
  • With-key smoke — send a real prompt against the live model and verify the WORLD (a file on disk, a non-empty assistant turn), not the agent's self-report. This proves the actual product works, which a mock/keyless run structurally cannot. Key-gated: it self-skips without DEEPSEEK_API_KEY (see the with-key policy — inference is cheap here, so write many).

Exception — keyless-by-nature examples. An example whose model is itself a mock/deterministic stand-in (no real provider) has no meaningful with-key smoke; the keyless smoke is the complete requirement. State the exception inline in the test.

A keyless smoke that spawns the example from a temp cwd must set TSX_TSCONFIG_PATH to the repo-root tsconfig — the unbuilt paths map is found by searching UP from cwd, so a temp cwd outside the repo would otherwise fall back to stale built lib/. Pass --expose-internals when the example's cordis.yml loads the HMR plugin (mirror the demo:* script).

Current state

Example Keyless smoke With-key smoke
echo-agent tests/echo.e2e.ts — boots the real cordis.yml, drives the echo tool round-trip and the direct canned reply N/A — keyless by nature (the mock-echo model has no real provider)
coding-agent tests/keyless-smoke.e2e.ts — boots the full real tree (dummy key, no prompt → no model call), asserts banner + clean exit tests/{full-loop,coding-task,resume,todo-write}.e2e.ts — real model + real bash + real todo_write, world-verified
acp-agent pnpm run test:snapshot — boots the real ACP subprocess and replays a recorded session keyless; tests/acp.e2e.ts also asserts stdout purity without a key tests/acp.e2e.ts — real ACP prompt, verifies a file the agent wrote

See the root AGENTS.md for repo-wide conventions and docs/architecture.md for the design.