@harzva/dsh-restart-autoresume
安全的 DSH 重启协调与持久化顶层会话自动恢复
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Harzva/dsh-restart-autoresume#d52ffdbce247cef0549759a87555d9209d94eb81Restart Autoresume 以 @harzva/dsh-restart-autoresume 发布，当前版本为 0.1.0-alpha.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
@harzva/dsh-restart-autoresume adds a controlled Restart & resume running tasks flow to DeepSeek Harness (DSH). It records ordinary top-level sessions, flushes their durable state, delegates the actual restart to the existing dsh-restart Host service, and safely submits one auditable continuation turn per eligible intent after the new Host starts.
This public alpha targets DSH 0.1.1-rc.2, Cordis 4.0.1, and Node.js 22+. It is distributed through GitHub Releases and is not installed in a production profile by the release process.
Restart actions backed by the existing DSH restart service
One running ordinary top-level task captured before restart
The continuation turn completes in the original durable session
The operator intent is durably completed after one attempt
The screenshots come from a disposable local Web profile. They contain no credentials or machine-private paths and are repository documentation assets, not runtime dependencies.
dsh-restart Host-service capability checks that fail closed;0600 files;User-stopped, completed, blocked, max-token, errored, and subagent sessions are excluded. A resumed turn is a new visible continuation request; it is not process-level checkpoint restoration.
This package deliberately does not implement another DSH restart mechanism. The target profile must already mount dsh-restart@0.3.1 or another compatible provider of this small Host contract:
{
provider: 'dsh-restart',
requestRestart: () => Promise<void>
}
dsh-restart remains the sole owner of closing and reopening DSH. This package owns only the durable recovery orchestration around that action. If dshRestartRuntime is absent or malformed, restart requests return RESTART_RUNTIME_UNAVAILABLE before candidates are captured or Ledger state is written. No launchd/systemd/macOS helper configuration is accepted by this package.
Install only into a disposable or explicitly approved profile:
dsh plugin --profile web add https://github.com/Harzva/dsh-restart-autoresume/releases/download/v0.1.0-alpha.1/harzva-dsh-restart-autoresume-0.1.0-alpha.1.tgz --ignore-scripts
The compatible dsh-restart@0.3.1 provider is a prerequisite and must be installed and mounted first. Do not substitute the unrelated public npm package currently using the unscoped dsh-restart name unless it explicitly implements the dshRestartRuntime contract above.
The bundle contributes exactly one row, dsh-restart-autoresume. Configure that row in the profile patch layer; an id-targeted patch replaces the whole config, so restate every non-default field you need:
- id: dsh-restart-autoresume
config:
autoResumeCrash: true
maxAttempts: 3
claimTtlMs: 30000
intentTtlMs: 86400000
recoveryConcurrency: 1
startupSettleMs: 1000
restartDelayMs: 250
The dsh-restart bundle must be mounted in the same Host realm. Service lookup is live, so stopping or unloading the provider immediately disables the restart actions without affecting DSH startup or Ledger inspection.
The single loader row is the immediate recovery boundary. Keep the package installed but disable all Host and Client behavior with:
- id: dsh-restart-autoresume
disabled: true
Restart the profile and confirm stock DSH starts without the sidebar action. To remove the package dependency as well:
dsh plugin --profile web remove @harzva/dsh-restart-autoresume
The Resume Ledger contains only safe routing/status metadata. Disabling or removing the loader does not modify DSH Session history.
dshRestartRuntime through a Cordis-owned timer.interrupted.dsh-restart-autoresume:<intentId> as stable RPC provenance. Durable inbox and user-message evidence is checked before any redispatch.pnpm install --ignore-scripts
pnpm check
pnpm run pack:dsh
pnpm run verify:dsh-offline
The final isolated validation includes real Web loading, Client Remote activation, a closed-loop restart through the existing dsh-restart Host service, durable continuation of one running ordinary top-level task, prior no-task/single-task/multi-task and SIGKILL recovery drills, tool-result-unknown boundaries, user-stop protection, retry ceiling/manual retry, disconnect/reconnect, responsive light/dark UI, and disable-only stock cold start. See docs/05-验收报告.md for the evidence matrix and known limits.
0.1.1-rc.2; other DSH release candidates require a fresh contract and runtime validation.fsync durability against sudden power loss.