Developer preview boundaryDo not mutate a production profile first. Test the exact target with a new DSH home, limited credentials, and a disposable workspace.

Run one reversible loop.

  1. 01Record

    Path, version, integrity or commit, Node, package manager.

  2. 02Stop

    Dispose Web, workers, supervisors, and Session writers.

  3. 03Capture

    Manifest, lockfile, patches, resolved graph, required Sessions.

  4. 04Isolate

    Boot the exact target in a new home and workspace.

  5. 05Gate

    Add pinned plugins one by one and test the full boundary.

  6. 06Decide

    Promote exact evidence or restore and cold-boot known good.

Capture more than the version.

ExecutablePackage or source

Path, exact version, integrity, remote, commit, and dirty diff.

ProfileDependencies + graph

Manifest, lockfile, build allowances, patches, and dump-config.

DurabilitySessions + writers

Stopped-writer backup using the active persistence contract.

Test the target without touching known good.

upgrade_home=$(mktemp -d)
upgrade_workspace=$(mktemp -d)
cd "$upgrade_workspace"

DSH_HOME="$upgrade_home" \
  npx @deepseek-ai/dsh@<target-version> \
  --profile web --dump-config > target-clean.yml

Pass ten compatibility gates.

Executable

Exact expected bytes

Clean boot

No stale state

Composition

Understood row diff

Model route

Expected credential

Permissions

Denial still holds

Tools

One registration

Sessions

Fresh + resume

Plugins

Pinned compatibility

Shutdown

Writers dispose

Restart

Same cold result

Promote or restore exact state.

PassPromote what passed

Use the same exact version and integrity, plus the reviewed profile graph.

or
FailRestore known good

Stop writers, restore executable and captured state, compare the dump, and cold boot.

A version downgrade is not a rollback by itself.

If the target changed profile files or durable Session state, the old executable can still fail. Restore every boundary the target mutated, then prove the previous behavior.

Primary evidence.

Keep the complete upgrade record.

The canonical guide covers artifact identity, stopped-writer capture, isolated homes, plugin compatibility, failure routing, promotion, rollback, and a reusable evidence template.

Read the complete guide on GitHub