Repository navigation
v0.1.4 — DeepSeek Harness 0.1.7-rc.1 (session format v4)
中文
适配 DeepSeek Harness 0.1.7-rc.1 的 session format v4。
改了什么
- 消息来源形状(写):handoff、checkpoint continuation 和 pressure notice 现在写生产者自己的 kind(
kind: '<宿主 plugin id>'),不再写 v4 已废弃的{ kind: 'plugin', plugin: … }包装——后者会被 v4 的门直接拒绝。 - 消息来源形状(读):读侧同时认新 kind 和 v4 在读取时对已发布 v3 历史的改名结果
plugin:<producer>,两种身份精确匹配;历史日志不需要改写。 - tool/result 字段:
toolCallId与isError现在读 message 自身(rc.1 把它们从 content 包装移到了 message)。这个类型检查看不见,漏了会让工具结果投影静默错位。 - pressure notice 的一次性闩锁:同一条消息来源规则的第四处落点,同样对类型检查不可见;漏了会每一步都重新注入提醒。
破坏性变更:peer 范围
>=0.1.7-rc.1 <0.1.8,不再接受 0.1.5-rc.x / 0.1.6-alpha.x。开发依赖固定 0.1.7-rc.1,@deepseek-ai/cordis 开发依赖 4.0.4。
同时发布的还有
上一版之后未发布的改动:readContextTimeline 接受可选的 hardLimit(仅用于回显),不可返回的时间线锚点会带上自己的标识符并标注不可选。
验证
typecheck、208/208 测试、build 全绿;CI linux 与 windows 均通过。
npm i @wowyuarm/dsh-context-continuity@0.1.4
English
Adapts to the session format v4 of DeepSeek Harness 0.1.7-rc.1.
What changed
- Message source shape (write): handoffs, checkpoint continuations, and pressure notices now carry the producer's own kind (
kind: '<host plugin id>') instead of the{ kind: 'plugin', plugin: … }wrapper v4 retires — which the v4 gate refuses outright. - Message source shape (read): the read side recognizes both the new kind and the
plugin:<producer>identity that v4 assigns to released v3 history at read time, by exact match. Logs on disk are never rewritten. - tool/result fields:
toolCallIdandisErrorare now read from the message itself (rc.1 moved them off the content wrapper). Typecheck cannot see this one; missing it misplaces tool-result projection silently. - The pressure notice's once-per-generation latch: the fourth landing point of the same source rule, equally invisible to typecheck; missing it re-injects the notice on every step.
Breaking change: peer range
>=0.1.7-rc.1 <0.1.8; 0.1.5-rc.x and 0.1.6-alpha.x are no longer accepted. Dev dependencies are pinned at 0.1.7-rc.1, with @deepseek-ai/cordis at 4.0.4.
Also released here
Changes that went unpublished after the previous version: readContextTimeline accepts an optional hardLimit (echoed back for display only), and non-restorable timeline anchors quote their own identifier marked not selectable.
Verification
typecheck, 208/208 tests, and build all green; CI passed on both linux and windows.
npm i @wowyuarm/dsh-context-continuity@0.1.4