huxin7735-collab/dsh-maintainer-doc-guard

dsh-maintainer-doc-guard is a native DeepSeek Harness (dsh) bundle plugin: the repository carries the dsh-plugin topic and ships a bundle-manifest, and the entire product name, packaging, and integration surface are written against the dsh harness. Its core capability is keeping long-term project memory outside the context window by externalising it into five maintainer documents — plan.md, conventions.md, stack.md, state.md, and lessons.md — stored per-session under .dsh-maintainer-doc-guard/<session-id>/ (overridable via the docsDir knob). The plugin registers a maintainer-doc-guard system-prompt section that re-evaluates on every prompt assembly, instructing the model to read the relevant document before each operation, so memory is re-hydrated from files instead of recalled from a lossy compacted summary.

The intended audience is project maintainers and dsh power users running small-parameter models on long, drift-prone sessions, where compacted summaries silently drop conventions, plans, stack decisions and working state. The typical workflow is automatic: on first open of the panel the plugin creates the per-session folder and one blank file for each document, with nothing to wire by hand. On top of that, two tools/pre-execute guards enforce discipline: a precedent gate denies any write/edit in a guarded infrastructure area until the session has read at least one same-basename working precedent, surfacing a model-visible block message that lists concrete candidate files (sibling packages found by walking up the directory chain); and a cheaper intent gate polices whether a turn was worth taking at all, blocking actions whose intent the model has not yet declared.

Dependencies are minimal — dsh itself plus pnpm with nodeLinker: hoisted — and the license is MIT. The install is a profile edit in $DSH_HOME/profiles/web/package.json: add "dsh-maintainer-doc-guard": "link:/abs/path/..." under dependencies AND add it to dsh.profile.bundles (both halves matter, since a resolvable package not listed there mounts nothing), then pnpm install and fully restart dsh, because bundles are not hot-loaded and a window close-reopen often reuses the old service PID and shows adopted orphan service in the shell log. Limitations worth knowing: the guarded areas, document names, and all ten tuning knobs live in cordis.patch.yml and must be rewritten for any harness that guards different directories; the precedent gate is bounded by gate.maxDeniesPerTarget so a stubborn model cannot deadlock its turn; every internal path is wrapped so failures degrade to "no decision" with a warning rather than break tool dispatch; and dsh web --dump-config plus 设置 → 插件 → 插件配置 are the recommended first-run verification steps, with GET /dsh-maintainer-doc-guard/settings as the live check that the reminder channel is genuinely wired in.