0559e0207e
- Per-file 100% coverage across the five new packages (invariant companion suites, failure-injection negatives, lifecycle and malformed-medium branches). - Canonical README Model Experience / Known Limitations sections; new storage/ and workspace/ group READMEs; packages/README.md rows (budget ceiling raised 760 → 790 for the two new groups). - Cordis catalog/type-link registrations, service-role classification, and regenerated catalogs/graphs for the new services and events. - Agent Note: English body + i18n pairing record; design-sketch fences opted out of doc-typecheck as ignore-check. - Two exactOptionalPropertyTypes/discriminant fixes in new tests. doc-sync (24 gates), typecheck, hygiene, and the five-package suite (92 tests) all pass.
@deepseek-ai/dsh-domain
Domain data form for the DeepSeek Harness storage hub: mounts ctx.storage.domain, opening schema-validated KV domains over configured storage backends. A domain is declared once with defineDomain (zod record schemas, z.infer-derived types), opened through DomainFacility.open, and served from authoritative in-memory state — reads are synchronous, writes serialize on one per-domain chain, reach durability on the routed backend first, then update memory and emit domain/changed.
Design rationale, open semantics, and the storage/domain layer split live in the Agent Note.
Configuration
| key | meaning |
|---|---|
backend |
Default backend name for every domain (required; no universally correct medium exists). |
routes |
Per-domain overrides: domain name → backend name. |
Model Experience
Durable domain state
What the model sees
Nothing. The package registers no tools, injects no prompts, and appends no session events; it stores non-session data (workspace records, future session sidecars) behind ctx.storage.domain and emits only the in-process domain/changed event, which reaches a model only if a consumer package renders it through its own documented surface.
Token effect
Zero. No text from this package enters any model request.
KV Cache effect
Independent: domain reads and writes never touch request prefixes, so nothing here can invalidate provider cache reuse.
Known Limitations and Deferred Work
- Single-process change visibility —
domain/changedis an in-process event; a second host process or a reconnecting GUI observes no changes until the cross-process revision pattern deferred in the Agent Note lands. - No cross-table transactions, secondary indexes, or multi-segment keys — each write touches one record; triggers and rework points for these extensions are tabled in the Agent Note's deferred-work list.