Skip to content

v0.1.0-rc.7

Latest
Latest

Choose a tag to compare

View all tags
@1473382 1473382 released this 16 Aug 13:41
· 3 commits to master since this release
v0.1.0-rc.7
ad2dba0

Popper v0.1.0-rc.7 — session-event compatibility (old hosts no longer crash)

Popper is a DeepSeek Harness plugin (not an MCP server, not a standalone CLI): it mounts into a harness profile as a cordis layer, runs inside the harness's own agent loop, and gates real sessions for better development quality.

Released artifacts

  • tarball: deepseek-ai-dsh-popper-0.1.0-rc.7.tgz (43.1 kB)
  • sha256: 67bcd9f8e38a5a8df08f12311c4dde05b501a4688d52fe1b0076a454b30ef658

What changed since rc.6

  • Event compatibility root fix: the falsification ledger event (falsification/ledger) is now written with the session-event envelope's ignorable: true marker. A host whose event vocabulary does not include the type skips the ledger rows and loads the session normally instead of refusing the whole log (SessionFormatUnsupportedError).
  • Session.append() gained an official ignorable writer option (host change in deepseek-harness packages/core/session); before this, downstream plugins could not mark events skippable at all.
  • Event vocabulary (KNOWN_SESSION_EVENT_TYPES, docs/persistence-catalog.md) now registers falsification/ledger; regenerated via pnpm run verify-persistence-catalog.
  • Product positioning stated up front: a DeepSeek Harness plugin, not MCP.

What this means for users

  • If your harness knows the event type: ledger is interpreted in full (same as rc.6).
  • If your harness is older: history loading no longer crashes — the ledger rows are simply skipped.
Assets 3
Loading