[Bug] @deepseek-ai/dsh-workspace-changes causes massive disk consumption and orphan residue leaks

[taxueseek]

Environment

• Package: @deepseek-ai/dsh-workspace-changes (v0.2.2-alpha.2)
• Monorepo Path: packages/deliverables/workspace-changes
• OS: macOS / Linux

Problem Description

@deepseek-ai/dsh-workspace-changes exhibits two critical resource issues during normal use:

1. Severe Disk Bloat: A single turn can generate multiple gigabytes of temporary objects in $TMPDIR/dsh-workspace-changes-*.
2. Permanent Orphan Leaks: When the DSH Host crashes, is SIGTERMed/killed, or the machine restarts, the temporary directories are never cleaned up, permanently consuming tens of gigabytes of disk space.

---

Root Cause Analysis (Code Level)

1. Unbounded git add --all in snapshotTree
   The snapshot captures the entire work tree using:

   await git.run(["add", "--all", "--ignore-errors", ...pathspec], ...);
   await git.run(["write-tree"], ...);

   • Although config.maxFileBytes exists, it is only enforced when generating diffs or capturing file-tool copies. In snapshotTree, git add --all unconditionally writes Git blob objects for all untracked, unignored files into GIT_OBJECT_DIRECTORY.
   • If a repository lacks a .gitignore or contains build outputs, node_modules, .venv, or SQLite databases, Git packages tens of thousands of files into blobs within the temporary directory on the very first turn.

2. Fragile Disposal Lifecycle

   • Directory cleanup is strictly bound to session/disposed and Cordis ctx.effect().
   • In real-world environments, developers frequently terminate the host via SIGINT (Ctrl+C), SIGTERM (hot restart scripts/supervisor), or experience host crashes. Under these conditions, the async cleanup rm(scratch) never completes, and the OS does not auto-reclaim custom temporary directory prefixes.
   • Production Evidence: On a single machine, we observed 35 orphaned dsh-workspace-changes-* directories accumulating 45.9 GB of leaked storage, with individual directories measuring up to 3.04 GB.

3. No Turn Eviction / LRU
   Temporary snapshot objects remain on disk for the entire lifetime of a Session across dozens of turns, with no sliding window (e.g. keeping only the last 3 turns).

---

Suggested Fixes

1. Built-in Ignore Defense in snapshotTree:
   Add built-in exclude pathspecs to git add for common non-source directories (e.g., :(exclude)node_modules, :(exclude).venv, :(exclude)dist, :(exclude)build, binary archives), or respect a configurable excludePatterns option.
2. Crash-Safe Host Recovery / Orphan Reaper:
   • Write a lightweight PID / session metadata marker inside $TMPDIR/dsh-workspace-changes-*.
   • On plugin startup, scan $TMPDIR and prune any dsh-workspace-changes-* directories whose owning PID is no longer alive.
3. Rolling Turn Snapshots (Sliding Window):
   Retain tree snapshots and file copies only for the most recent N turns (e.g., 3 turns), pruning older snapshot objects periodically instead of waiting for session/disposed.