Ndsanes/dsh-rules

dsh-rules is a native cordis plugin built specifically for DeepSeek Harness, distributed as the npm package @ndsanes/dsh-rules and registered through the dsh plugin --profile <name> add @ndsanes/dsh-rules command. It targets the Open Mod Protocol (OMP) rule format, discovering Markdown rule files from the workspace's .omp/rules directory, the user rules folder, the omp-plugins pluginRoots tree, the agents directories, plus foreign directories such as <cwd>/.cursor/rules, <cwd>/.windsurf/rules, the nearest .clinerules, and .github/instructions/*.instructions.md. Identity is the rule name alone, so the merge keeps the first rule to claim it in priority order, which is why <cwd>/.cursor/rules/style.md defeats a same-named ~/.cursor/rules/style.md. Operators must also remove any stale link: dependency or dsh.profile.bundles entry under an old package name before installing, because the loader resolves bundle rows by current name and a leftover entry causes a bare import failed boot error that the plugin cannot diagnose.

The plugin injects alwaysApply rules and the rulebook directly into the system prompt so the model can pull individual rule bodies on demand, then enforces **time-traveling stream rules** that interrupt violating model output mid-turn before it lands on the user. It ships a browser half that renders the same rule editor twice — once on the Plugins page under this plugin's own row, once as a tab inside Settings → Plugins — where fixed-vocabulary fields such as interruptMode use dropdowns so a typo cannot slip through; an unrecognised value silently falls back to the profile default of always. Workflow suits teams that want OMP conventions plus Cursor, Windsurf, Cline and GitHub instruction files to be governed by one consistent harness-wide layer, and the bundled src/builtin-rules/ directory holds 27 MIT-licensed defaults for TypeScript, Go and Rust that override OMP's own copy under identical names. The repo also provides helper scripts: scripts/audit-rules.ts to dump what the plugin parsed from a real project, scripts/render-prompt.ts to mount the plugin on a real DSH system-prompt service and print the assembled prompt without making a model call, and scripts/verify-interrupt.sh to run one prompt twice against a live DSH — once with an interrupting rule, once with a warning-only twin — so the transcript diff is the evidence.

First-run caveats are concrete: discovery is asynchronous, so the very first prompt assembly after a late mount renders without rule layers while the build runs, and the first tool call waits on the same waterfall, though a violating call is still blocked. The rule tool distinguishes "still being discovered" from "no rules exist" so a stale session does not look broken. Development follows a dev → main branch flow where the Release workflow publishes via npm Trusted Publishing using a short-lived OIDC credential scoped to one run, so no token is stored in the repository; configuration happens once on npmjs.com with user Ndsanes, repository dsh-rules, workflow filename release.yml. Build commands are pnpm install, pnpm test (vitest), pnpm typecheck, pnpm build, and after editing anything under src/builtin-rules/ the maintainer must run pnpm run embed:rules so the bundler, which cannot import Markdown as text, regenerates src/generated/builtin-rules.ts. Offline coverage is provided by tests/interrupt-loop.spec.ts, which mounts a real AgentLoop, SessionStore, LlmRuntime and tool registry through the DSH test kit and asserts abort, <system-interrupt> retry, the <system-reminder> path for interruptMode: never, and that repeatMode: once spends the rule, all under the MIT license.