bowenliang123/dsh-context v0.38.4 on GitHub

Install / Update

Install the dsh-context plugin on DeepSeek Harness with released NPM package:

dsh plugin --profile web add dsh-context@latest

Update the dsh-context plugin:

dsh plugin --profile web update dsh-context@latest

Compatible with dsh 0.1.2-alpha.2 — 0.1.2-alpha.2 removed the settingsNamespace() helper this plugin's host half imported at load time, which aborted the whole plugin on that host; the namespace is now registered the same way dsh's own packages do, as the raw string. The client half also serves the markdown chrome (fence copy buttons, footnote heading) that the 0.1.2-alpha MarkdownText requires — on the 0.1.2-alpha line, fenced code and footnotes in the Context browser's detail cards used to render broken.
- Works across dsh 0.1.0-rc.7+, 0.1.1-rc.2+, and 0.1.2-alpha.2; pre-0.1.2 faces ignore the new chrome prop and render exactly as before
Stable dependency resolution in DSH profiles (#35) — zod moves from peerDependencies to dependencies. Profiles install out-of-tree plugins with nodeLinker: hoisted + autoInstallPeers: false, so a peer-only zod was never installed and the host half silently resolved to whichever zod the profile's other packages happened to hoist; a hoisted zod predating the Standard Schema protocol (zod < 3.24) left Config["~standard"] undefined and cordis failed the whole plugin tree with a bare TypeError. Every install now materializes a standard-schema-capable zod ^4.4.3, deduped with the host's own when compatible.
- The published bundle is unchanged — the host build keeps production dependencies external

fix(host): register the settings namespace without the removed brand helper (0a9dc86)
fix(client): pass the markdown chrome the 0.1.2-alpha primitives require (648b601)
test(host): inline the lossless-JSON probe dropped from dsh-session (09aabe0)
fix(host): carry zod as a real dependency, not an auto-installed peer (1c98027)