* 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 |
|---|---|
| The storage group map: durable non-session data through named backends and the typed domain data form, for users and maintainers navigating the group. | package-group |
packages/storage
English | 中文
Summary
The storage group keeps non-session application data across restarts, including workspace records and session sidecars. Choose storage-json for human-readable files or storage-sqlite for point updates in one database; storage-domain adds schema-validated typed records and change notifications, while storage selects the configured backend. These packages are optional and host-side: they do not expose tools, prompt content, or session events to the model. Use the group when application state must outlive a process, and omit it when the composition has no such data.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
storage |
Connects registered backends with mounted data-form facilities | ctx.storage |
storage-json |
Stores each unit as one human-readable JSON file | registers backend json |
storage-sqlite |
Stores units as JSON documents in one SQLite database | registers backend sqlite |
storage-domain |
Provides schema-validated, change-emitting KV domains over routed backends | ctx.storageDomain |
Related documentation
- Storage subsystem — the authoritative contract: the backend contract, domain declaration, change events, and generated API.
- domain KV storage Agent Note — the design behind the family, the workspace consumer, and the deferred session-backend migration.
- Workspace subsystem — the first consumer of the domain data form.
Dev Note
Working context for maintainers — click to expand
The design Agent Note is still marked proposed while the family ships; its out-of-scope table is the deferred-work list for the migration phase (the log facet, session-backend reuse, cross-process change push). Promote decisions into implemented notes as they land.