dsh-janitor
DeepSeek Harness 的确定性工件生命周期：扫描代理会话遗留的计划文档和临时脚本，返回可供审核的清理计划——清理程序绝不是代理
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:zhengqiuyang/dsh-janitor#3e99897b33184650abc40fa2ae44fcedbf5aecffJanitor 以 dsh-janitor 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Deterministic artifact lifecycle for DeepSeek Harness (dsh).
Agent sessions leave debris: plan docs from finished tasks, scratch scripts,
one-off fixtures. People fear agent-driven cleanup precisely because cleanup
driven by an agent is unaccountable. This plugin registers a janitor_scan
tool that runs the agent-janitor
engine over the workspace and returns a reviewable cleanup plan — every
candidate file with a deterministic verdict (protected / keep / recent /
needs-review / safe-to-remove) and the evidence behind it.
The janitor is never an agent. The scan and verdicts are pure deterministic rules (reference analysis, git metadata, age thresholds); v0.1 never deletes anything — applying a reviewed plan stays with the upstream CLI or with you, on purpose.
Family: read-guard (what agents read) · pr-gate (what they write) · attest (what they did) · mcp-test (what they can call) · janitor (what they leave behind).
Nothing in the dsh ecosystem does deterministic workspace hygiene. The
@goodandready/dsh-time-machine plugin does checkpoints and rollback
(snapshot safety), which is complementary: it answers "can I undo?", this
answers "what is safe to remove?". Deterministic scan → reviewable plan →
apply as a three-step, non-agent pipeline is unowned.
| verdict | meaning |
|---|---|
protected | exact file or directory prefix in the protected list |
keep | referenced by any code file |
recent | younger than minAgeDays (git commit time preferred) |
needs-review | referenced by docs/other, or otherwise ambiguous |
safe-to-remove | plan doc with task merged & zero refs, or zero refs + old enough |
dsh plugin --profile default add github:zhengqiuyang/dsh-janitor
git installs build from source; authorize once in the profile's
pnpm-workspace.yaml:
allowBuilds:
dsh-janitor: true
- id: dsh-janitor
name: dsh-janitor
config:
minAgeDays: 14
protectedPaths: ["plans", "docs/decisions"] # exact file or directory prefix
npm install
npm test # syncs the vendored agent-janitor engine, builds, runs fixture tests
The scan/verdict engine is vendored from the sibling agent-janitor
checkout (npm run sync; CI runs sync --check).
janitor_apply with an explicit per-path confirmation protocol (still
deterministic — no agent judgment in the loop).dsh-* ledgers, scratch plugins dirs)applyIf dsh ships first-party workspace hygiene, or time-machine-style plugins add deterministic removal planning, this freezes at its last working version with a postmortem here. The engine stays owned by agent-janitor either way.