Dsh Explain

Needs allowlistBundlegit + preparefreshinstall scripts

DSH 本地优先学习模式插件：跨会话全局学习线程、按来源讲解、ExplainContext、压缩与可诊断设置界面

Install Dsh Explain

Installs from git, but pnpm >=10 will refuse until you add an `allowBuilds` entry in your profile's pnpm-workspace.yaml. That grants this package permission to execute code on your machine at install time, outside the agent sandbox — pin a commit (github:owner/repo#sha) before allowing it.

The one-line version

dsh plugin --profile my-profile add github:yuezengwu/dsh-explain

This one needs an explicit build approval before it works

Installed from git, this package builds itself with a prepare script. pnpm 10 refuses to run that script until you list the package in pnpm-workspace.yaml. Adding it means you are allowing this package's code to run on your machine, outside the agent sandbox, at install time. The first install prints an allowBuilds hint and fails — that is expected, add the entry and retry.

1. allow the build in pnpm-workspace.yaml

onlyBuiltDependencies:
  - dsh-explain

2. install, pinning a commit so the code you approved is the code you get

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:yuezengwu/dsh-explain#<commit-sha>

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Before you run itinstall scripts

This package declares prepare — package-manager lifecycle scripts that execute on your machine at install time, outside the agent sandbox, before any tool-approval prompt exists.
A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
Installing from git resolves a moving branch. Pin a commit — github:yuezengwu/dsh-explain#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key: Not required.
Network access: Not required at runtime.
Build approval: Required — the package must be listed in pnpm-workspace.yaml before it will build.
Language: TypeScript — a git install pulls this source, not build output.

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checked	Result	Weight	What the spec says about it
lifecycleScripts	fail	warn	runs at install time, outside the agent sandbox: prepare
dsh.bundle	pass	fatal	package.json declares a `dsh.bundle` layer
dsh.bundle.patch file	pass	fatal	patch file present at `cordis.patch.yml`
npm registry	missing	warn	`dsh-explain` is not published to npm
prepare script	pass	fatal	ships a `prepare` script that builds on git install
pnpm allowBuilds	fail	warn	pnpm >=10 refuses to run a git dependency's prepare script until allowlisted

Verdict reason: git-only with a prepare script — requires an explicit build allowance
package.json read: package.json
Rules applied from: docs/user/develop/basic/publish.md
Checked at: 2026-08-15
Install-time scripts: prepare

From the README

Excerpt as published by the author, plain text, unedited

**English** | [简体中文](README.zh-CN.md) > ✅ **Status: M6 is implemented entirely in Explain and passes its DSH `0.1.0-rc.6` acceptance gates. No other plugin requires a patch or runtime dependency.** > See the [product requirements](docs/PRD.md) and [technical architecture](docs/ARCHITECTURE.md) for the full design. The detailed design documents are currently written in Chinese. `dsh-explain` turns useful material from multiple [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) work sessions into one private, local-first learning thread. It keeps at most one active explanation per source session and continuously adapts explanations to the user's knowledge, preferences, and learning progress. - A `$DSH_HOME` contains exactly one local learning thread. Work sessions, resumes,