dsh-doctor

dsh patch layers follow a whole-entry replacement model: change one field and every sibling field you did not restate silently vanishes from the boot tree, yet the exit code is still 0. A single typo in an entry id produces one stderr line you never see in the Web UI. These failures sit invisibly for weeks before behaviour drifts, and by then it is hard to trace which patch layer dropped the field.

dsh-doctor composes the actual boot tree via dsh --dump-config and the baseline via --dump-default-config, then diffs the two and attributes every finding back to your user patches. Seven check rules cover dropped fields (config-clobber), mismatched entry ids (dead-patch), tool-name collisions, unmounted plugins, stale plugins, removed entries, and added or toggled entries, each with a severity level and a did-you-mean suggestion. --explain lists every entry actually running in the profile and flags conditional expressions; --fix restates only the dropped fields inside the flagged config block, writes a .bak first, and leaves every other byte untouched. Installed as a plugin it also registers a config_doctor tool so the agent can answer "why is my setting not taking effect" from the composed tree rather than guessing.

Built for developers managing dsh profile patch layers, CI pipelines that need a pre-upgrade config check, and anyone tired of silent failures who wants a definitive answer in under ten seconds. Zero dependencies, read-only by default, no signup, no configuration required.