This repository was archived by the owner on Sep 27, 2026. It is now read-only.
Repository navigation
中文
适配 DeepSeek Harness 0.1.7-rc.1;peer 范围与 0.1.4 相同。
改了什么
- 宿主可以说自己的话:
createContinuityTools的文案缝加宽了四个口子——carriedContext(一次 rollover 会自动带走什么,用来点出你自己的耐久信道)、timelineGuidance(你的边界表怎么读,拼进context_timeline的描述)、topicNoun/topicNounPlural(边界上的可归因主体怎么称呼,例如Thread而不是topic,描述与逐行渲染同时改口)。 - handoff 按 delta 讲述(默认文案变了):默认的 rollover 指引现在要求「写成一个新 generation 自己重建不出来的活状态」,并给出唯一普适的携带事实——主体在切换前后是同一个身份,不必重述;清单也随之重写(在飞的原动作、别处没记过的事实与证据、未解冲突、外部副作用及其验证状态、一个明确的下一步)。
- 压力提醒同一口径:
contextPressureNoticeText现在同样只说「写新 generation 重建不出来的部分」。 - 结构性契约仍归引擎:防伪造那句、"a context change never rolls back any external effect"、"Structural only: no transcript content" 与 restorable 判定都不接受宿主覆盖。
兼容性
没有破坏性变更:peer 范围与 0.1.4 相同(>=0.1.7-rc.1 <0.1.8,不再接受 0.1.5-rc.x / 0.1.6-alpha.x),开发依赖仍固定在 0.1.7-rc.1。
验证
本地:typecheck、boundaries、214/214 测试(7 个文件)全绿;CI 在 linux 与 windows 两条 lane 均通过(提交 4246ed8)。
npm i @wowyuarm/dsh-context-continuity@0.1.5
English
Adapts to DeepSeek Harness 0.1.7-rc.1; the peer range is unchanged from 0.1.4.
What changed
- Hosts can now speak their own vocabulary: the tool-text seam on
createContinuityToolsgained four openings —carriedContext(what a rollover carries forward automatically, where you name your own durable channels),timelineGuidance(how your boundary rows read, spliced into thecontext_timelinedescription), andtopicNoun/topicNounPlural(what an attributable subject of a boundary is called —Threadrather thantopic— in both the description and the rendered rows). - The handoff is framed as a delta (the default wording changed): the default rollover guidance now asks for "the live working state a fresh generation could not reconstruct on its own" and states the one universal carried fact — the subject keeps its identity across the switch, so restating it is waste. The checklist was retuned to match: the atomic action in flight, facts and evidence not already recorded elsewhere, unresolved conflicts, external side effects and their verification state, and one explicit next step.
- The pressure notice says the same thing:
contextPressureNoticeTextnow asks for only what a fresh generation could not reconstruct. - The structural contract stays engine-owned: the anti-forgery sentence, "a context change never rolls back any external effect", "Structural only: no transcript content", and the restorable rule are not host knobs.
Compatibility
No breaking change: the peer range is identical to 0.1.4 (>=0.1.7-rc.1 <0.1.8; 0.1.5-rc.x and 0.1.6-alpha.x remain excluded), and dev dependencies stay pinned at 0.1.7-rc.1.
Verification
Local: typecheck, boundaries check, and 214/214 tests (7 files) all green; CI passed on both linux and windows (commit 4246ed8).
npm i @wowyuarm/dsh-context-continuity@0.1.5