dsh-permission-rules

项目详情摘要

🛡️ dsh-permission-rules **1024 store channel**: `npm i -g dsh1024` once, then `dsh1024 plugin --profile web add dsh-permission-rules` (counts toward the deepseek1024.com install ranking). Claude Code-style declarative permission rules for DeepSeek Harness.** Rules decide what is known. A reviewer model decides what is not.* English · 简体中文 · Español · Português · हिन्दी Compatibility Surface | Status | Harness | DeepSeek Harness `dsh-v0.1.5-rc.2` (adapted 2026-09-09, full gate chain + profile install smoke): its `Session.append` still cannot stamp the `ignorable` marker — verified on the published `0.1.5-rc.2` package, where the third argument is silently dropped and the envelope field survives for stored-log reads only — so the whole `0.1.5-alpha` line is pre-checked as unmarked and session-log audit stays disabled by default. The `0.1.3-alpha` line keeps the same surface-only append signature. Both lines' log migrations refuse unclassified plugin events even when marked, so `strip` v1 audit rows before a `0.1.3-alpha` host opens the log and v2 audit rows before a `0.1.5-alpha` host migrates it (native v3 logs only need `repair`). | Node | `^22.19.0 || >=24.0.0` | Platforms | All (host + web settings client) | Model | Any (deny/ask reasons surface through tool results) | What you get `dsh-permission-rules` puts an ordered **`allow` / `deny` / `ask`** rule list in front of every tool call on the `tools/pre-execute` waterfall — deterministic, instant, auditable, and written by you in plain YAML: **`deny`** blocks the call; the rule's `reason` becomes the model-visible error. **`ask`** rides the official approval seam (mount `dsh-auto-review` for a second-model answerer, or a human answers; with neither, the harness fails closed). **`allow`** (and no-match) strictly delega