mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
ec601ca13d
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`, `verify-translation-pairing --write` for the touched bilingual pairs, `gen-doc-graphs`, and one typert snapshot whose ids embed character offsets. `pnpm run rescope-vendor --check` verifies the result. Renames nine vendored packages (cordis, cosmokit, schemastery and the six @cordisjs plugins) and every reference that resolves them: manifest names and dependency keys, module specifiers including declare-module merges, cordis.yml plugin names, tsconfig paths, every Markdown fence, and `docs/` prose. Directory names, upstream versions, and dependency ranges are unchanged, so vendor/README.md still reads as an upstream snapshot; its manifest table gains an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed at each fork's origin. The tutorial tier follows the rename end to end: its yaml fences named plugins the Loader can no longer resolve, its `ts ignore-check` fences disagreed with the compiled fences beside them, and its prose quoted both. The contracts that told readers to keep upstream names — the root convention and the vendoring cookbook's tree comment and manifest invariant — now say to rescope instead. Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle purity gate now names the vendored libraries a browser bundle inlines, and the files where a bare `cordis` is an agent-preset id keep that product data.
@deepseek-ai/dsh-storage
English | 中文
Storage hub (ctx.storage) for non-session data: a named backend registry plus mounted data-form facilities. The hub performs no IO itself — backends own media, and data forms own semantics. The storage family overview maps those packages; the domain KV storage Agent Note records the design rationale.
Shape
ctx.storage.backend— name → backend table. Multiple backends stay mounted side by side (json,sqlite); which backend serves a consumer is that consumer's configuration (the domain layer's route table), never a hub-global choice.register()returns the disposer; duplicate names and unknown lookups fail loud.ctx.storage.mount(form, facility)/ctx.storage.form(form)— data-form mounting.StorageFormsis merge-extensible; the domain layer mergesdomainand is reached asctx.storage.domain.- A backend owns one medium and exposes the data-shape facets it supports.
kvis the current facet;src/backend.tsowns its exact contract.
Model Experience
Backend and form registrations
What the model sees
Nothing. ctx.storage is a host-side registration table; the hub registers no tools, injects no prompts, and writes no session events.
Token effect
Zero direct tokens on every request.
KV Cache effect
Independent of live requests: the hub never touches a request prefix, so it cannot invalidate provider cache reuse.
Known Limitations and Deferred Work
kvis the only data shape — backends currently have one facet to implement.- Forms resolve lazily — reading
ctx.storage.domainbefore the domain plugin mounts throwsform-not-mounted; assemblies order plugins accordingly (misconfiguration fails loud rather than silently deferring).