Tianyi Cui 1bb201365d docs(agents): add doc-current-state convention + sharpen the summary worked example (review)
Two review findings on the AGENTS.md additions:

- Add a convention to § Type Safety and Documentation: document the CURRENT
  state (what + why), never the PROCESS/HISTORY of how the code got there. No
  "previously/now/used-to/replaces/the old X" in comments or JSDoc — that rots
  on the next change and belongs in the commit message / PR / RFC. A standing
  contrast against a live alternative is fine; a contrast against the codebase's
  past is not.

- The "tests document behavior" worked example overstated the audit as "nothing
  in production read or wrote" the summary. The backends DID write it (JSONL
  sidecar, SQLite updated_at); what made it dead was no CONSUMER and no
  update() caller. Corrected so a future reader does not infer the write path
  never existed.
2026-06-20 12:42:53 +08:00
2026-06-16 14:55:37 +08:00
2026-06-16 14:55:37 +08:00
2026-06-16 14:55:37 +08:00
2026-06-16 14:55:37 +08:00

DeepSeek Harness

Monorepo for the DeepSeek Harness group.

Projects

  • DeepSeek Code — DeepSeek's coding agent product.

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:echo     # runnable echo-agent example (no API key needed)
pnpm run demo:coding   # the real DeepSeek coding agent (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 before package work. Local context lives in packages/ and vendor/.

For agents, follow AGENTS.md.

Description
No description provided
Readme MIT 120 MiB
Languages
TypeScript 97%
CSS 1.6%
Python 0.7%
JavaScript 0.6%