deepseek-harness/packages/typert/registry/README.md

@deepseek-ai/dsh-typert-registry

English | 中文

Runtime registry for generated Typert artifacts. A contribution carries one package face's business reflection and optional live Zod schemas; ctx.typert registers both atomically and withdraws them with the calling Cordis fiber. TypeScript analysis and code generation live in dsh-typert-generator.

Package reflection is keyed by <package>#<face>. Schemas are keyed by <package>#<name> and retain the producer's Zod instance. JSON Schema is computed on demand at the consumer edge.

Public API

• TypertRegistry is the default plugin and provides ctx.typert.
• register(contribution) rejects malformed identities and duplicate package-face or schema keys before committing anything, then returns the exact Cordis effect disposer.
• get(key), resolve(key), and list(filter?) query live schemas. resolve() distinguishes a malformed key, an absent package, and a package that contributes no schema under that name.
• getPackage(packageName, face?) and listPackages(filter?) query generated service, event, and object reflection; the default face is host.
• toJSONSchema(key, params?) projects a live schema with z.toJSONSchema() without caching the result.
• typertKey() and typertPackageKey() compose the two stable identity forms.

The @deepseek-ai/dsh-typert-registry/types subpath contains the pure contribution and record contracts. dsh-typert-loader discovers and registers generated host artifacts in Loader compositions; direct ctx.typert.register() supports other composition owners.

Model Experience

None, as the registry contributes no prompt, tool, or session event; consumers such as cordis_inspect own any model-visible projection.

KV Cache effect

No direct effect. A consumer that places reflection in a request owns the resulting prefix change.

Known Limitations and Deferred Work

• The registry stores generated reflection but does not merge host and client graphs or resolve TypeScript references. Those are analyzer and emitter concerns.
• Schema keys omit the face because host and client run in separate contexts. Registering same-named schemas from both faces into one context is rejected as a duplicate.