Files
deepseek-harness/packages/typert/loader
Turtle 38c7a9fbf4 feat(release): publish package source, declaration maps, and documentation (#5884)
* feat(release): publish package source, declaration maps, and documentation

Every release member publishes its TypeScript source and the declaration
maps that resolve into it, and @deepseek-ai/dsh publishes the repository
Markdown documentation staged from docs/ at prepack time.

The ./src/* export most members already declared now resolves for an
installed consumer, and a consumer editor follows a declaration to the
implementation. Bundled JavaScript maps stay unpublished; the vendored
family and the Desktop runtime file policy are unchanged.

Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md

* feat(release): publish JavaScript maps and compress bundles

Every emitted JavaScript map ships beside the bundle it describes, and the
workspace build and the client preset compress bundles without mangling
identifiers.

The documentation payload now mirrors the website publication manifest and
is removed again by `postpack`; Desktop and the Python executable exclude
the published source, documentation, and maps; `clean` removes a staged
copy. Typert's publication contract gains the Remote declaration map.

* fix(release): keep node bundles readable for the worker image

The browser worker image lowers `yield*` only as a whole statement and
rewrites `for await` loops by their source layout, so compressed node-side
entries either fail that lowering or lower to unparseable code. Only the
browser bundles keep compression, which removes about a third of their text.

The bundle-purity assertion now matches the module-loader call regardless of
the quote style compression picks, and the release-pack fixture exercises
the installed package's new documentation requirement.

* feat(release): publish the whole documentation tree

`@deepseek-ai/dsh` copies `docs/` in full instead of the website's page
set: the maintainer documents, the generated migration records, the
translation guidelines, and the `*.i18n.yaml` consistency records ship
with the installed package, so the documentation's own links resolve
without a checkout.

* feat(release): publish the upgrade guides with the documentation

The staged documentation keeps the website's page set and adds every
`docs/upgrade-guide/` document, which is what an installed reader consults
when a released change breaks something. The rest of the maintainer tree
stays out.

* test(release): expect source and maps in master's new payload cases

* feat(release): keep installed docs and source readable in Desktop

Desktop keeps the published src/ and docs/ trees inside app.asar, and
every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE
so an agent can read them through Electron's Node mode. Staging also
generates docs/upgrade-guide/README.md, an index of the upgrade guides
grouped by the release they upgrade from.

Minified client bundles print string literals with backticks: the
worker image packer now recognizes those chunk requests, client license
banners are prepended after minification so their text survives, and
the affected artifact tests accept either quote.

* test(desktop): read archived docs through the Windows PowerShell form

Regenerate the config catalog for the shifted shell-env source line.

* test(desktop): wait for the GUI-subsystem Electron process from PowerShell

* build(release): publish source and maps from the message-quotes package

* build(release): publish source and maps from packages new on master

* build(release): publish source and maps from the tool-office package
2026-11-05 00:22:36 +08:00
..

description, kind
description kind
Loader integration for generated Typert artifacts: how mounted packages automatically contribute their host-face reflection and schemas to the runtime registry. package-reference

@deepseek-ai/dsh-typert-loader

English | 中文

Summary

With dsh-typert-loader mounted, every package that mounts in a Loader composition automatically contributes its generated Typert reflection and schema factories to the runtime registry — and withdraws them when the package or the plugin unmounts. Packages without the generated export are skipped, so adding the plugin to any composition is safe. An explicit packages list covers plugins nested behind another Loader entry, whose fibers carry no resolvable package specifier. It is a Node-only plugin and needs the config-tree resolution anchor to resolve packages.

Table of Contents


Use this package

Mount this plugin in a Host Loader composition that loads packages publishing generated Typert artifacts. The registry itself comes from dsh-typert-registry; this plugin only discovers and registers.

Minimal configuration

Load the registry and the loader; the loader defaults to discovering every Loader entry:

- name: '@deepseek-ai/dsh-typert-registry'
- name: '@deepseek-ai/dsh-typert-loader'
Field Default Meaning
packages [] Additional package artifacts to register for plugins nested behind another Loader entry; each must resolve from the config tree and export ./typert

The generated configuration catalog is the exhaustive source for every accepted field.

What gets registered

Each qualifying Loader entry contributes its generated host-face reflection, schema factories, and TYPERT.invocations to the runtime registry. The ordinary artifact's getter exposes descriptors from a private Remote info instance; generated direct descriptors also provide named input and invocation helpers. Registration follows the entry lifecycle: it is withdrawn when the entry or the plugin unmounts, and an import that settles after either owner is gone is discarded.

Source compositions requiring strict Remote validation prebuild and load the ordinary ./typert artifact. The loader registers its invocations in ctx.typert.local; it does not recover erased constraints, documentation, or schemas from live Services. Limited descriptor-free source fallback remains a Gateway concern, and local.hasSeen() prevents downgrading to it after a registered definition is withdrawn.

Observable behavior and failures

Packages without the export are skipped silently. Resolution verdicts and imported manifests are cached for the process lifetime, so adding a ./typert export requires a restart. A malformed artifact among already-mounted entries fails activation loudly; a later failure is logged per package without preventing unrelated packages from registering. An explicit packages entry that cannot be resolved from the config tree, or that lacks the export, fails loudly and names the package.


Understand the implementation

Implementation internals — click to expand

This section explains how the loader scans, validates, and registers; the observable behavior is covered in Use this package.

Design concept

The plugin is an incremental scanner mirroring the client-modules node half: every Cordis internal/plugin emission marks the fiber's entry name dirty, and a microtask flush reconciles each dirty name against the live Loader entries; the activation pass seeds the same dirty set with all current entries.

Manifest validation

validateTypertManifest() checks artifacts before they enter the typed registry. A manifest must name its exporting package, carry face host, hold schema factories, and contain well-formed reflection records; invocation descriptors require strict codecs with factories. Validation checks parameter codec and any supplied strictCodec specs and requires generated direct-method input and invoke to be callable; result remains the sole output codec. Documentation and JSON Schema are optional. Registration never calls the input selector, parser factories, or projection getters; validation inspects only supplied static projection data. Every failure names the package and the defect.

Caching and ownership

Verdicts (resolvable specifier, export presence) and imported manifests are cached per package name and never expire. Registrations are keyed by entry name and withdrawn through the exact ctx.typert.register() disposer; in-flight tasks are tracked per entry so a late import cannot register a contribution after its owner is gone.

Source map

File Role
src/index.ts Plugin entry: Config, scanner, manifest validation, registration wiring

Further Exploration

Read these pages when the package-level contract is not enough; they move from the loader to what it registers and what produces it.


Model Experience

None, as loader integration only registers generated artifacts; consumers own any model-visible projection.

KV Cache effect

No direct effect; registration changes reach a request only through a consumer that reads the registry.

Known Limitations and Deferred Work

These limits define what the loader does not discover or register; they are current package constraints, not a task backlog.

  • Host face only — discovery imports only the host ./typert artifact; client runtimes need a separate composition owner before equivalent discovery is added.
  • Explicit entries for nested plugins — Loader entries are discovered automatically, but plugins nested behind another entry, or not loaded by the Loader at all, need an explicit packages entry or direct ctx.typert.register() ownership.
  • Cached verdicts never expire — a package that gains a ./typert export mid-process needs a restart before the loader registers it.
  • Host readiness remains composition-owned — consumers requiring strict metadata must wait for registration before serving calls. The lazy info factory does not make asynchronous Loader registration ready; local.hasSeen() only protects definitions already observed.

Dev Note

Working context for maintainers — click to expand

None.