Repository navigation
Conversation
- follow session/event instead of removed Session.events - declare own everos-memory message source and 0.2 tool-result shape - preserve startsRequestSeries when rewriting agent/pre-step - bump engines.dsh and peer ranges to 0.2.1-rc.3+ - rewrite tests for 0.2 event shapes and update e2e/README BREAKING CHANGE: drops DeepSeek Harness 0.1.x support.
Update engines.dsh, peer ranges and dev dependencies to the current 0.2.1 release candidate; regenerate the lockfile and e2e pins.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Port the DeepSeek Harness (DSH) memory plugin from the DSH
0.1.xplugin surface to0.2.x(0.2.1-rc.5tested). Version bumps to 0.2.0 and drops 0.1.x support.The 0.1.x package cannot work on 0.2.x even when force-installed:
Session.eventswas removed, so capture and recall throw and the plugin's fail-open path swallows it — DSH looks healthy while memory silently stops.What changed
>=0.1.0-rc.6 <0.2.0-0, noengines.dsh>=0.2.1-rc.5 <0.3.0-0,engines.dshsetsession.eventseach turn (O(n²) on long sessions)session/eventfeed incrementallysession.eventssource.kind = 'plugin'everos-memorysource (form: 'recall'); 0.2 removed the sharedpluginkindToolResultBlock.toolCallIdmessage.toolCallIdand flat content blocksstartsRequestSeriessurvives (goal-round semantics)Also: tests rewritten against 0.2 event shapes (21 tests), e2e script updated to the 0.2
SessionStoreAPI and pinned 0.2.1-rc.5 dependencies, README documents requirements and the 0.1.x → 0.2.0 upgrade.Verification
npm run ciagainst DSH0.2.1-rc.5packages: lint + typecheck + 21 unit tests + build — passing.scripts/e2e-everos.mjsdrives a real@deepseek-ai/dsh-session0.2.1-rc.5 Session through real cordis events./memory/add+/memory/flushand an episode/profile on disk; the fresh recall session receivedINJECTED=1with the fact inside the<everos_memory>fence andsource: { kind: "everos-memory", form: "recall" }.scripts/e2e-everos.shstill requires a configured EverOS instance with LLM credentials; not run in this PR.Upgrade notes
defer_extractionis released there).