bowenliang123
33068ee1c9
The install/runtime compatibility floor moves from 0.1.1-rc2+ and 0.1.2-alpha2+ to 0.1.2-rc.1+. The 0.1.1 line and the 0.1.2-alpha previews leave the support matrix, so every pre-0.1.2 fallback they existed for is removed outright: - client history: drop the legacy `connection.api.sessions.history` face, the `result`-nested envelope, and the `events` rows field — the gateway `remote.session.page` face and its ClientResult envelope are the only served shapes. - client image loader: drop the pre-0.1.2 `conversation.resolveImage` face; `uiConversation.imageUrl` only. - client node join: drop the pre-0.1.2 `useSession.nodes` seat; `useChat`'s ChatSnapshot `legacy.nodes` only (UseSessionLike removed). - tests/baselines.ts: single baseline `v0.1.2-rc.1`; HostSeam dropped (the registry generation hard-codes header-passing init and seq-0 eager seeding, now mirrored with the exact `init(header, inheritedEventCount)` arity); ClientSeam slimmed to the consumed probes. - deps: devDeps re-pinned to the 0.1.2-rc.1 generation (types compile against the real rc.1 surfaces); cordis ^4.0.2 and schemastery ^3.18.2 per the rc.1 peer requirements; dsh-scope/dsh-invariants declared as dev deps; peer floors >=0.1.2-rc.1; dshReleases table trimmed. - release workflow fetches only the dsh-v0.1.2-rc.1 tag; docs updated (AGENTS.md, README, docs/compatibility.md). - verified against the rc.1 sources: the tool-attribution map (names and packages, incl. the documented `subagent_fork` alias), MCP naming, the page/imageUrl/legacy.nodes faces, and the registry contract.
2.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-04 (plugin dsh-context@0.41.3 source tree).
Supported dsh releases
| dsh release | npm channel | Declared | Automated seam matrix | Disposable-profile install / uninstall |
|---|---|---|---|---|
0.1.2-rc.1 |
next |
compatible | ✅ baseline v0.1.2-rc.1 |
✅ install OK → 1 composed row → uninstall OK → 0 rows |
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.
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, durable-event vocabulary, settings namespace). Definitions live intests/baselines.ts; the release workflow fetches the pinned baseline tags before testing. - 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 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.