Bowen Liang
a4bd0d40f9
The supported V3 line follows the newest release: the baseline becomes v0.1.5-alpha.2 (tag, vendored session package) and the declared release map names 0.1.5-alpha.2. The release workflow fetches the new tag. The alpha.2 client seams are pinned in the matrix: the conversation surface moved under the keyed `main` panel (`main.conversation`) while the plugin's `conversation.view` seat keeps its name, and `SidebarRightGuideEntry` dropped its description line. tests/baselines.ts therefore gains a guideEntry probe (the fields present plus the dropped copy field asserted absent). Every support/capability label states the 0.1.5-alpha.2+ floor; `0.1.5-alpha.x+` remains only as the V3 LOG-generation label. The docs record the verified matrix, the two moved seams, and the install row that still waits on the CLI's npm publication (the `alpha` dist-tag lags the release).
6.2 KiB
Compatibility
dsh-context declares per-release compatibility with @deepseek-ai/dsh in its package manifest (dsh.compatibility.dshReleases). This page records what is actually verified for each declared release, and how.
Last verified: 2026-09-09 (plugin dsh-context@0.47.0 source tree).
Supported dsh releases
| dsh release | Session log | Declared | Automated seam matrix | Disposable-profile install / uninstall |
|---|---|---|---|---|
0.1.2-rc.1 |
V0 | compatible | ✅ baseline v0.1.2-rc.1 |
✅ install OK → 1 composed row → uninstall OK → 0 rows (verified 2026-09-05) |
0.1.3-alpha.2 |
V2 | compatible | ✅ baseline v0.1.3-alpha.2 |
✅ install OK → 1 composed row → uninstall OK → 0 rows |
0.1.5-alpha.2 |
V3 | compatible | ✅ baseline v0.1.5-alpha.2 |
⏳ pending — @deepseek-ai/dsh@0.1.5-alpha.2 is not on npm yet (the alpha dist-tag lags); the previous V3 release's result is carried forward |
The automated seam matrix runs for every row on every pnpm test. The disposable-profile column is a manual, per-release check: 0.1.2-rc.1 was verified on 2026-09-05 and carried forward; 0.1.3-alpha.2 and the previous V3 release were verified on 2026-09-09 against the official npm registry (a stale mirror can 404 the harness's own dependency closure before the plugin is even considered). 0.1.5-alpha.2 changed no install-path seam — the manifest, the patch layer, and the composed row are byte-identical to the previous V3 release apart from the version — so its install row waits only on the CLI's npm publication.
Releases older than 0.1.2-rc.1 — the 0.1.1 line and the 0.1.2-alpha.* previews — were supported and verified through dsh-context@0.41.x and are no longer in the support matrix.
Session-log generations
The supported range spans three durable-log generations, and the plugin folds all of them from one shape-driven code path (src/host/logShapes.ts):
| Seam | V0 (0.1.2-rc.x) |
V2 (0.1.3-alpha.x) |
V3 (0.1.5-alpha.x+) |
|---|---|---|---|
| System prompt | request/header.header.system |
same as V0 | system/message surface node |
| First token | assistant/chunk events |
embedded data.stream (also assistant/attempt) |
same as V2 |
| Replacement endpoints | { start, end } |
same as V0 | { startSeq, endSeq } |
| Nested PTC dispatch | tool/code-dispatch |
same as V0 | tool/ptc-dispatch |
The fold never branches on a detected harness version: a log carries exactly one generation, and the spellings are mutually exclusive. This matters because a deployment's version probe can be wrong — a healed profile mirror may name a different release than the running harness.
Web client seams
The browser half rides generation-specific seats, each reached through an optional seam so an older line simply goes without the capability. One V3 boundary moved them:
| Seam | Before 0.1.5-alpha.2 |
0.1.5-alpha.2+ |
|---|---|---|
| Conversation panel root | flat conversation slot |
keyed main panel's main.conversation (the plugin's conversation.view seat is unchanged and hangs under it) |
| Right Sidebar guide entry | glyph + title + description line | glyph + title (the description line was dropped) |
What each check means
- Automated seam matrix — part of this repository's
pnpm test(thecompatvitest project). For every baseline tag it stages the harness's REAL sources at that tag, boots the plugin's built host entry into that tag's actualSessionProjectionRegistryon the cordis release the line vendors, and probes the tag's client seams (slots, finalized-nodes seat, image loader, history face/envelope, markdown chrome, platform module table, that generation's durable-event vocabulary, the right Sidebar tab seam and its guide-entry contract where the line ships one, settings namespace). Definitions live intests/baselines.ts; the release workflow fetches the pinned baseline tags before testing. Optional seams are asserted BOTH ways: the right Sidebar tab registers only on the generation that serves it, and every older line is proven to have no such service, so the plugin's deferred registration stays inert instead of pending. - Statistics against the harness's own folds — the plugin's figures are differentially checked against the harness's OWN projection values (
sessionStats,contextBreakdown,contextPressure,tokenUsage) over real V0 and V3 session logs: system/tools/message tokens, per-request counts, turns/steps, TTFT, generation, tool time, and every billed cost bucket match exactly, and a migrated V0→V3 log reproduces the same figures as its V0 original. - Disposable-profile install / uninstall — for each release, that exact
dshCLI version was installed from npm into a temporaryDSH_HOME(the real~/.dshis never touched), then:dsh plugin --profile <disposable> add dsh-context— install OK;dsh --profile <disposable> --dump-config— the bundle's- id: dsh-contextrow composes into the effective configuration (exactly 1 row);dsh plugin --profile <disposable> remove dsh-context— uninstall OK, dump-config back to 0 rows.
Scope
These checks prove source-level seam compatibility, statistical parity with the harness's own folds, and disposable-profile install/start-composition/uninstall per release. They are not a claim of full web-app runtime acceptance on a real Profile — visible UI behavior depends on the harness generation and the browser half, which the seam matrix approximates from the tag's sources.
Upgrading from an older plugin build
The plugin keeps its projection stateVersion unchanged, so cached per-session projection rows stay usable: bumping it would invalidate every row and orphan the contextTimeline key for idle sessions, which have no refresh channel until they go live again.
One consequence: a session whose row was folded by an older build keeps serving that older figure set until its log receives a new event (the registry seeds the cached state and replays only the tail). New sessions are exact from their first event. To force a full refold of an existing session, delete its cached projection row — it is a derived cache and is rebuilt from the durable log:
rm ~/.dsh/storages/session_projcache/sessions/<session-id>.json