Files
deepseek-harness/packages/sdk
imccyu a66b98d270 fix(telemetry): report unless telemetry entry is explicitly disabled
Per ccyu's decision (option A), remove the consent asymmetry in ConsentResolver:
telemetry is OFF only when cordis.yml has a telemetry entry with disabled: true.
A cordis.yml with no telemetry entry now reports (allowWhenEntryAbsent defaults
to true) rather than denying. No cordis.yml, an enabled entry, and DO_NOT_TRACK/CI
are unchanged. Both no-config and absent-entry defaults stay configurable.

Updates the module/README docs and the unit tests (file-present-but-no-entry and
non-object/non-sequence roots now report). Per-file 100% coverage holds.
2026-07-18 16:11:25 +08:00
..

SDK packages

Developer tooling for creating, editing, building, and running DeepSeek Harness projects.

The feature RFC owns the developer workflow; the architecture RFC owns the package and project-editing boundaries.

Package Role
helper Project aggregate, edit session, builtin features, project documents, templates, package managers, and prompt abstraction
scripts The dsh-sdk launcher: start, dev, build, and interactive config
create-sdk The npm create @deepseek-ai/sdk initializer
plugin-fetch Fetch an external plugin (github/npm) into a temp dir — pinned and un-executed — for dsh-sdk create

@deepseek-ai/create-sdk is the one package-name exception to the repository's @deepseek-ai/dsh-* rule: npm's scoped initializer convention requires that name for npm create @deepseek-ai/sdk.

Generated projects keep cordis.yml as the only runtime plugin tree. dsh-sdk dev adds TypeScript and local-workspace resolution around that same file; it does not create a development-only config.