dsh-session-move v0.1.1

Distribution and Installation

What this repository distributes

dsh-session-move ships as two coordinated artifacts:

Artifact	Contents	Used for
dsh-session-move-<version>.tgz	Built lib/, cordis.patch.yml, the 8 first-party core patches, patch/verification scripts, and all docs	dsh plugin --profile <profile> add <tarball> after the patched DSH build
dsh-session-move-patches-<version>.tar.gz	Only the patch series, the revision-fenced apply script, and the docs	Building the patched DSH from the exact public base, without installing anything
SHA256SUMS	SHA-256 for both tarballs	Verifying download integrity
release-manifest.json	Source commit, patch base, patch-check output, verification outputs, artifact hashes	Release provenance

The npm package and the patch bundle both contain the same patch series. The npm
package is the runtime plugin; the patch bundle exists because a user who wants
the full move capability must first build a patched DSH, and that step should
not require installing the plugin.

Support matrix

inspect is always read-only. Drag-to-move exists only when the patch series is
applied to the exact public base.

Runtime	Activation	ctx.sessionMove.inspect()	Sidebar drag move
Official installed DSH 0.1.0-rc.6 (no patches)	Yes, provided the profile also contains a host bundle such as @deepseek-ai/dsh-headless or @deepseek-ai/dsh-web-app	Yes — full read-only dry-run with stable blockers	No — the move is refused with the unsupported blocker because the runtime has no mover capability
Public base 47f943859bef60e4160492346772ded9b24f765a + the 8 bundled patches, built from source	Yes	Yes	Yes — official workspace.moveSession RPC and sidebar cross-group drag
Any other base revision, fork, or partially patched tree	Unknown	Unknown	No — the apply script refuses any revision except the exact base

Installing only the npm plugin on the official unpatched rc.6 runtime does not
enable dragging. Any release text that implies otherwise would be wrong.

Upstream contribution policy (checked 2026-08-16 UTC)

The route "wait for upstream to merge the patches, then ship a pure plugin" is
not available:

• CONTRIBUTING.md on the default master branch states verbatim:

  DeepSeek Harness is still at an early stage and under active development.
  We are sorry that we cannot accept external pull requests at the moment.
  However, contributing code to this repository is far from the only way to
  help. There are many other ways to get involved:

  • Identify and report issues or bugs in GitHub Discussions: …

  Source: https://github.com/deepseek-ai/deepseek-harness/blob/master/CONTRIBUTING.md.

• The repository home page
  (https://github.com/deepseek-ai/deepseek-harness) exposes the navigation
  tabs Code, Discussions, Security and quality, and Insights. There is no
  Pull requests tab and no Issues tab. The GitHub API reports has_issues: false and has_discussions: true; requesting /pulls returns a zero-state
  page ("There aren't any open pull requests.").

• The default branch is master (not main), so the policy document is read
  from master/CONTRIBUTING.md.

Conclusion: the distribution model in this document (npm plugin + patch set
against the exact public base) remains the correct route. No code is submitted
upstream.

Full install, rollback, and provenance documentation:
https://github.com/kirkchinese/DSH-Session-Move/blob/main/docs/distribution.md

npm install: dsh plugin --profile <profile> add dsh-session-move