@lmzhen/dsh-evolution-all

Q: Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.0 <0.2.3-0 the CLI loads @lmzhen/dsh-evolution-all; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @lmzhen/dsh-evolution-all is the per-package override if you accept the risk.

A self-evolution bundle: host automation plus model-facing tools in one install.

Version 0.46.0 of @lmzhen/dsh-evolution-all, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add @lmzhen/dsh-evolution-all writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @lmzhen/dsh-evolution-all

Compatibility

engines.dsh in @lmzhen/dsh-evolution-all declares >=0.2.2-rc.0 <0.2.3-0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

A bundle that pulls the other evolution packages in. Installing it beside @lmzhen/dsh-evolution-skill-health installs the same panel twice, and the duplicate row wins one of the two configs.

Who made it

Author: lmzhen. Repository: https://github.com/lmzhen/dsh-evolution. Package page: https://www.npmjs.com/package/@lmzhen/dsh-evolution-all.

After install

It declares no dsh peer and renders scheduled run entries in the sidebar; after dsh plugin add @lmzhen/dsh-evolution-all, dsh --profile web --dump-config lists the @lmzhen/dsh-evolution-all row that mounts it.

Files it touches

No storage peer appears in the manifest of @lmzhen/dsh-evolution-all, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing @lmzhen/dsh-evolution-all is the mirror command, dsh plugin --profile web remove @lmzhen/dsh-evolution-all. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

What does it hook into, and how do I check that slot is free?

Its manifest names no community counterpart, so the check is manual: after dsh plugin add @lmzhen/dsh-evolution-all, run dsh --profile web --dump-config and look for two rows claiming the same slot.

Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.0 <0.2.3-0 the CLI loads @lmzhen/dsh-evolution-all; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @lmzhen/dsh-evolution-all is the per-package override if you accept the risk.