dsh-version-inventory

Debugging dsh, the plugin list in the settings panel shows module names and fiber states but the version column is empty. You cannot tell which Harness build is actually running, or whether a preset-only plugin differs in version from its global counterpart. A subtler trap: two copies of the same package will silently break Cordis runtime-identity matching, and the built-in panel gives no way to spot the duplicate before the behavior goes wrong.

This plugin reads both the global Loader tree and every agent preset composition, resolves each module specifier to its nearest package.json, and merges mounts by resolved directory rather than by package name so duplicate copies stay visible, sorted adjacent and tagged. The panel also surfaces the install path, Node version, DSH_HOME, a harness-package version-drift alert, and automatically redacts any config field whose key contains key, token, secret, password, credential, or auth. Each row copies as name@version; the header copies a share-safe environment report that carries no filesystem path, no DSH_HOME, and no config value. The same reading is registered as the dsh_version_inventory tool, so an agent mid-session can answer a version question directly instead of asking its user to open a settings tab and paste a report back.

Best for anyone running dsh from a source checkout or an npm install, especially deployments that compose presets (Creator mode and beyond); developers chasing silent version drift or duplicate-package mismatches; and teams that want a one-line "what exactly is running here" snapshot they can drop into a ticket or a chat thread.