Skip to content

feat(dsh): support DeepSeek Harness 0.2.x - #37

Open
attolee wants to merge 2 commits into
EverMind-AI:mainfrom
attolee:feat/dsh-0.2
Open

attolee wants to merge 2 commits into
EverMind-AI:mainfrom
attolee:feat/dsh-0.2

Conversation

@attolee

@attolee attolee commented Oct 30, 2026 •

Copy link
Copy Markdown

Summary

Port the DeepSeek Harness (DSH) memory plugin from the DSH 0.1.x plugin surface to 0.2.x (0.2.1-rc.5 tested). 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.events was removed, so capture and recall throw and the plugin's fail-open path swallows it — DSH looks healthy while memory silently stops.

What changed

Area 0.1.x 0.2.x
Install / activation peers >=0.1.0-rc.6 <0.2.0-0, no engines.dsh peers >=0.2.1-rc.5 <0.3.0-0, engines.dsh set
Capture scans session.events each turn (O(n²) on long sessions) follows the committed session/event feed incrementally
Recall history reads session.events keeps a bounded ring of recent direct user messages
Recall provenance source.kind = 'plugin' declares its own everos-memory source (form: 'recall'); 0.2 removed the shared plugin kind
Tool results user-role message with nested ToolResultBlock.toolCallId tool-role message with top-level message.toolCallId and flat content blocks
Pre-step rewrite returns a new object spreads the host decision so startsRequestSeries survives (goal-round semantics)

Also: tests rewritten against 0.2 event shapes (21 tests), e2e script updated to the 0.2 SessionStore API and pinned 0.2.1-rc.5 dependencies, README documents requirements and the 0.1.x → 0.2.0 upgrade.

Verification

  • npm run ci against DSH 0.2.1-rc.5 packages: lint + typecheck + 21 unit tests + build — passing.
  • scripts/e2e-everos.mjs drives a real @deepseek-ai/dsh-session 0.2.1-rc.5 Session through real cordis events.
  • Against a real EverOS 1.5.1 configured with a DeepSeek LLM key: store phase produced /memory/add + /memory/flush and an episode/profile on disk; the fresh recall session received INJECTED=1 with the fact inside the <everos_memory> fence and source: { kind: "everos-memory", form: "recall" }.
  • A recording EverOS stub gives the same lifecycle counts without credentials.
  • scripts/e2e-everos.sh still requires a configured EverOS instance with LLM credentials; not run in this PR.

Upgrade notes

  • EverOS 1.5.1+ recommended (defer_extraction is released there).
  • 0.1.x users should stay on 0.1.0; this branch intentionally does not carry a dual code path.

- 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant