DSH-PackForge/dsh-pack-plugin

DSH-PackForge/dsh-pack-plugin is a DSH-native pure Plan-B bundle plugin that ships as a self-contained npm package named @dsh-packforge/dsh-pack-plugin, built exclusively for the official DeepSeek Harness desktop client. It is loaded through the stock bundle mechanism by appending host entries to cordis.patch.yml and client entries to dsh.client, so the underlying apps/desktop and apps/desktop-host source trees remain untouched. The plugin only consumes DSH's own runtime services (ctx.connection, ctx.webServer, ctx.slots, ctx.locale, ctx.profileContext) plus fflate for ZIP packaging, and it vendors every remaining dependency under src/core/ and src/host-node.js instead of pulling any @dsh-packforge/* engine package.

Its core capability set covers exporting a profile (or, internally, a whole dshhome snapshot) into a single-file .dspack, installing packs from local files, HTTP(S) URLs or the bundled marketplace, verifying each pack with sha256 + size, browsing the index.json light-weight market index with lazy-loaded full manifests under packs/<owner>.<repo>/, switching between multiple profiles by repointing the profiles/desktop junction and the per-profile skills / .agent-presets slots, and persisting per-profile workspace settings as a single UTF-8 JSON file called .dshpkcfg. A non-blocking task center streams install / export / create progress (phase timeline plus process output) from an in-memory registry exposed via task/list and task/get. Typical users are operators who want to snapshot, share or swap whole DSH environments between machines; the plugin is UI plus backend only and deliberately performs no AI-driven pack-management decisions of its own.

First-run engineering flow is plain Node work: run pnpm install, then pnpm test (node --test unit suite covering profile junction repointing, the skills / .agent-presets isolation, and end-to-end migration) and finally pnpm bundle to emit lib/client.js for the renderer via esbuild. An RPC channel named /dsh-pack is mounted by the host through ctx.webServer (a frontend route guarded by ctx.connection), while the client side calls it through a silent rpc.call wrapper that emits no chat-bar tool invocations. The plugin is dual-licensed under MIT and targets Windows-class junction semantics with an explicit red line: always unlink junctions rather than rm -r, because recursive removal on Windows would delete the target directory contents. Current limits: only the profile form of .dspack export is wired into settings UI even though the dshhome pack/install/verify logic already lives in core, so end-to-end export and install still await a real profile plus pnpm environment for full validation.