Ray1270/dsh-task-stack

@ray1270/dsh-task-stack is a Cordis plugin bundle packaged as the npm scope @ray1270/dsh-task-stack and built exclusively for the DeepSeek Harness (DSH) Agent, targeting DSH 0.2.0-rc.2 in development and CI. It installs as a profile bundle via dsh plugin --profile desktop add @ray1270/dsh-task-stack, which drops the package into the profile's node_modules and records it inside dsh.profile.bundles of the profile's package.json; the included cordis.patch.yml then resolves the loader line name: @ray1270/dsh-task-stack from that location, and a DSH Desktop restart is required before new sessions can invoke the tools. For ad-hoc debugging the repo ships a dev.patch.yml that uses name: ./lib/index.js and is mounted with dsh --profile web --patch ./dev.patch.yml --no-open, which does not require installation or any node_modules resolution.

The plugin exposes three defineTool registrations — focus_task, focus_complete, and read_focus — plus a /focus slash command for the human operator. The intended workflow is: push the outermost user-facing goal onto the stack with focus_task, push subgoals above it as they emerge, and pop completed tasks with focus_complete only after the deliverable has actually landed and before writing the final reply. State is written as plain JSON under <session-cwd>/<stateDir>/<sessionId>.json, so it survives context compaction and is recoverable whenever the same sessionId plus cwd is reattached. It targets multi-step agents that need durable focus across compression, not single-turn Q&A.

Runtime dependencies are declared as peerDependencies and supplied by the host: @deepseek-ai/cordis ^4.0.2, @deepseek-ai/dsh-tools, @deepseek-ai/dsh-commands, and @deepseek-ai/schemastery ^3.18.2. Configurable fields include stateDir (default .dsh/task-stack, must be relative and non-empty), maxStackDepth (integer ≥ 1, default 20), historyLimit (integer ≥ 1, default 100), and statePruneDays (integer ≥ 0, default 0). Schema violations are rejected by Cordis before plugin activation, with the specific offending field named in the startup log rather than silently clamped. Release is gated by prepack running a ten-step scripts/release-check.mjs (typecheck, build, check-build, probe, five test suites, demo) without invoking any package manager, so a misbehaving pnpm on PATH cannot poison it; first publish needs npm publish --access public. First-run caveat — do not write "dependencies": { "@ray1270/dsh-task-stack": "link:..." } when the profile lives on a different drive, because path.resolve stops at the drive root and a broken link: makes future pnpm install fail.