* 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. * feat(agent-preset): ship plugin artwork skill with creator mode * docs(skills): clarify artwork icon lookup and official review steps * refactor(agent-preset): fold plugin artwork into cordis plugin development * feat(agent-preset): require detail documents for creator bundles * test(release): expect source and maps in master's new payload cases * refactor(agent-preset): consolidate creator skills into dsh-doc * 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. * docs(agent-preset): add dsh-doc install, upgrade, and fallback guidance * docs(agent-preset): align dsh-doc archive reads and upgrade start versions * docs(agent-preset): bound dsh-doc upgrade index reads and test documented commands * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * docs(upgrade-guide): correct dsh-doc session verification step * test(agent-preset): use a block body for dsh-doc fixture cleanup * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * docs(agent-preset): read the running DSH version from the installation * build(release): publish source and maps from the message-quotes package * docs(agent-preset): document the verified PowerShell runtime invocation * docs(agent-preset): keep PowerShell runtime output streams and exit code * docs(tool-cordis): describe the shipped dsh-doc skill * docs(skills): load configuration guidance separately * fix(skills): declare shared template details in every locale * fix(skills): verify dsh-doc guidance through recorded sessions * test(skills): retain current runtime reminder in dsh-doc replay * test(snapshot): refresh terminal panel runtime context
6.2 KiB
description
| description |
|---|
| 浏览全部已捕获 DSH alpha/RC tag 之间的 Session 持久化类型变化,并离线校验历史快照。 |
DSH 预发行版本的持久化变化
English | 中文
概述
本归档提供 26 个 DSH alpha/RC tag 及其 25 次相邻转换的近似历史视图。每个版本包含简要说明、源码 tag、before/after 摘要以及变化类型的完整快照,供阅读和格式校验使用。它不确认历史运行时兼容性,也不替代当前源码的确认记录。
目录
已归档版本
清单记录了 2026-09-12 捕获的全部 DSH alpha/RC tag:16 个有发行记录,最早的 10 个只有 tag。版本按语义版本顺序排列;不存在的 tag 不补造。首条记录是历史起点,变化数包含其所有根。
| Tag | 源码日期(UTC) | Session 版本 | 根 / 类型 | 变化根 |
|---|---|---|---|---|
| dsh-v0.0.1-rc.1 | 2026-08-10 | 0 | 42 / 341 | 42 |
| dsh-v0.0.1-rc.2 | 2026-08-11 | 0 | 47 / 374 | 45 |
| dsh-v0.0.1-rc.3 | 2026-08-12 | 0 | 47 / 374 | 12 |
| dsh-v0.0.1-rc.4 | 2026-08-12 | 0 | 47 / 374 | 0 |
| dsh-v0.0.1-rc.5 | 2026-08-12 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.1 | 2026-08-13 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.2 | 2026-08-13 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.3 | 2026-08-13 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.5 | 2026-08-13 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.6 | 2026-08-13 | 0 | 47 / 374 | 0 |
| dsh-v0.1.0-rc.7 | 2026-08-17 | 0 | 47 / 376 | 1 |
| dsh-v0.1.0-rc.8 | 2026-08-19 | 0 | 51 / 403 | 8 |
| dsh-v0.1.1-rc.1 | 2026-08-21 | 0 | 51 / 407 | 1 |
| dsh-v0.1.1-rc.2 | 2026-08-21 | 0 | 51 / 404 | 10 |
| dsh-v0.1.2-alpha.1 | 2026-08-27 | 0 | 54 / 417 | 52 |
| dsh-v0.1.2-alpha.2 | 2026-08-30 | 0 | 54 / 417 | 52 |
| dsh-v0.1.2-alpha.3 | 2026-08-31 | 0 | 54 / 417 | 0 |
| dsh-v0.1.2-alpha.4 | 2026-09-01 | 0 | 54 / 415 | 4 |
| dsh-v0.1.2-alpha.5 | 2026-09-02 | 0 | 54 / 415 | 0 |
| dsh-v0.1.2-rc.1 | 2026-09-03 | 0 | 54 / 415 | 0 |
| dsh-v0.1.3-alpha.1 | 2026-09-04 | 2 | 54 / 425 | 17 |
| dsh-v0.1.3-alpha.2 | 2026-09-07 | 2 | 56 / 435 | 2 |
| dsh-v0.1.5-alpha.1 | 2026-09-08 | 3 | 57 / 443 | 12 |
| dsh-v0.1.5-alpha.2 | 2026-09-09 | 3 | 59 / 462 | 4 |
| dsh-v0.1.5-rc.1 | 2026-09-10 | 3 | 59 / 462 | 0 |
| dsh-v0.1.5-rc.2 | 2026-09-10 | 3 | 59 / 462 | 0 |
文件与范围
每个 tag 对应 kind: persistence-release 的中英记录、配对 sidecar 和 .schema.json。机器声明包含 tag、直接前驱、实际写入版本以及每个变化根的 before/after 摘要。首条快照包含全部根;后续快照只保存仍然存在的变化根及其所有可达类型。删除使用空 after,未变的版本保留空变化和空快照。
快照覆盖逻辑 Session header、物理 JSONL header、事件信封以及该 tag 的所有第一方事件及传递引用。类型数仅统计规范化后仍可达的定义。历史源码引用仅保留文件路径,不包含行号。
这些回溯记录与上层目录的当前确认链分开校验。当前规则对旧变化的分类只是阅读提示:历史上的 version 0 确实出现过不升版本的结构变化。不得把回填记录作为当前 PR 省略确认或版本提升的依据。
提取与限制
重建使用各 tag 中的源码、TypeScript 6.0.3 和已合入的 schema 提取器。唯一提取适配是省略早期具体事件记录交叉类型中冗余的 object 成员。原有 any / unknown 保持不透明;没有为缺失引用额外替换不透明类型。发行快照 JSON 保留历史标识符;术语检查仍适用于人工记录和当前 schema。
前 22 个 tag 的 surface 事件合法地带有可选 surfaceOp。历史解析保留此可选性;当前源码解析仍要求该字段必需。旧版 SessionHeader.version: number 也按原声明保留,实际写入版本常量另行记录。不能从宽泛的 number 声明推导它。
本批 tag 的写入版本为 0、2 和 3,没有写入版本 1 的 tag。
摘要对应规范化后的重建类型,不是原始源码文本或当时工具链的逐字重现。说明仅提供结构变化的粗略理解;未重放旧应用、验证完整编解码行为或证明迁移安全。摘要未变也不能证明行为未变。
校验
全部 26 个快照已通过规范图、根摘要和可达类型摘要校验。发行归档检查只读取本树中的清单、记录和快照,不访问 Git、网络或旧版本 checkout;它校验清单覆盖、前驱、before/after、快照类型完整性和双语机器声明。
pnpm run verify-persistence-releases
pnpm run doc-sync
标记区间内的索引、清单单元格和结构变化事实由快照生成。默认校验会拒绝陈旧事实。运行 pnpm run verify-persistence-releases --write 可在全部机器数据校验通过后刷新这些区间和配对记录;人工概述、源码证据、机器声明和 schema 文件保持不变。
tag 的完整性以清单的捕获范围为准;离线检查不会自动发现后续新 tag。配对记录及 Markdown 链接由常规文档检查校验。格式模板规定单条记录的字段。
开发备注
维护者工作上下文 — 点击展开
无。