* 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
description, kind
| description | kind |
|---|---|
| Official DeepSeek request-extension registry for provider plugins contributing lifecycle-owned top-level API fields. | package-reference |
@deepseek-ai/dsh-deepseek-llm-api-extensions
English | 中文
Summary
Provider-specific registry for additive top-level fields on official DeepSeek LLM API requests. DeepSeekLlmApiExtensionRegistry registers ctx.deepseekLlmApiExtensions; contributor plugins claim one declaration-merged field, and dsh-llm-deepseek prepares the current contributions after serializing its base request. Use it when a plugin must add a validated provider-specific field without changing the base adapter.
Table of Contents
Service
register(field, provider)reserves one field for the calling fiber. Duplicate or malformed names fail synchronously; disposing the registration releases it for a later provider.prepare(request)snapshots the registered providers, prepares them concurrently, clones and freezes returned JSON values, and returns{ fields, accept }. A provider whose preparation throws is omitted while the other fields are returned, and only its first failure is logged; request cancellation rejects and stops awaiting providers even when one ignores its signal.accept()runs every captured post-2xx callback once. Concurrent calls join the same settlement, every callback settles before failures are reported, and several failures become oneAggregateError.
Each provider sees the exact serialized Messages body, the request AbortSignal, plus optional sessionId and auxiliary-call purpose. It must stop its own work promptly after cancellation and returns undefined when its field does not apply to that request. A prepared operation retains the providers it captured even if HMR removes their registrations before HTTP acceptance.
Request purpose is the producer-defined string forwarded by the adapter, or absent for ordinary conversation requests. The registry forwards unfamiliar purposes without choosing field-specific policy.
The registry owns addition and lifecycle, not field semantics. @deepseek-ai/dsh-session-log-deepseek owns dsh_session_log; @deepseek-ai/dsh-plugin-package-inventory-deepseek owns dsh_plugin_packages. The provider-neutral LLM seam and llm-pi-ai do not consume this registry.
Model Experience
Indirectly, through @deepseek-ai/dsh-llm-deepseek, which sends registered fields outside the model's messages, system prompt, and tool schemas.
KV Cache effect
None; registry fields are model-hidden provider metadata and do not alter the serialized model-input prefix.
Known Limitations and Deferred Work
- Official DeepSeek requests only — the registry intentionally has no provider-neutral routing or pi-ai adapter integration.
- No field ordering contract — JSON object member order follows registration preparation but receivers address fields by name.
Dev Note
Working context for maintainers — click to expand
None.