# Compatibility evidence Plugin 0.2.0 targets the DSH 0.1.5 release series. The official npm registry and GitHub release resolver from `AI-Scarlett/build-dsh-plugin` reported `0.1.5-alpha.1`, `0.1.5-alpha.2`, and `0.1.5-rc.1` on 2026-09-10. ## Migration DSH 0.1.5 no longer publishes the `dsh-client-runtime` browser module. The plugin now declares the renderer as its client load dependency, imports `Context` from Cordis, and imports `UseProjection` from `dsh-api-session-controller/client`. It retains the additive `conversation.composer.dock` contribution and the existing `tokenUsage` projection. Plugin 0.1.1 at commit `b7e2b54dae8d8400fd24f55c3b7fcededbdd31d5` remains the historical release for DSH 0.1.0-rc.6. This is a direct DSH Bundle and a read-only UI plugin (R0). It introduces only the `dsh-api-usage-bar` Host row and `api-usage-bar` slot entry. It does not override official entries, install a replacement official package, call a model, access credentials, or mutate session logs. Migrating to the current public client types keeps the implementation small; the cost is that 0.2.0 does not support the removed runtime used by the historical DSH release. ## Observed results | DSH | Install | Config | Authenticated Web startup | Uninstall | Rollback | | --- | --- | --- | --- | --- | --- | | 0.1.5-alpha.1 | passed | passed | passed | passed | unknown | | 0.1.5-alpha.2 | passed | passed | passed | passed | unknown | | 0.1.5-rc.1 | passed | passed | passed | passed | unknown | The machine-readable records are [alpha.1](compatibility-0.1.5-alpha.1.json), [alpha.2](compatibility-0.1.5-alpha.2.json), and [rc.1](compatibility-0.1.5-rc.1.json). Tests ran on Windows with Node.js 24.16.0, independently installed official npm CLIs, and newly created disposable DSH homes on the same drive as the npm cache. Each test installed the prebuilt plugin through the official CLI, checked its composed row, booted on an OS-assigned loopback port, exchanged the official startup token for a cookie, checked the authenticated index and plugin boot manifest, observed sustained process liveness, stopped the test process, removed the plugin through the CLI, and checked the row and dependency were absent. The rc.1 Web UI also loaded in the in-app browser: onboarding completed, the normal workspace/composer shell rendered, the plugin-owned stylesheet was present, and captured browser warnings/errors were empty. This is startup and registration evidence; the new matrix did not perform a paid model request or verify a populated token bar in all three browsers. The component's synthetic token rendering and disposal tests pass independently. The screenshot in the README is from the historical 0.1.0-rc.6 verification. Rollback to a previous plugin release, Linux/macOS runtime behavior, and the user's real Profile were not tested. Their status remains unknown. Catalog re-listing is controlled by DSH STORE's next fixed-commit scan; these results do not claim the marketplace has already re-listed the plugin. ## Reproduce Install the exact official CLI into an isolated tool directory and pass its `lib/bin.js` to the script. Build and pack this repository first: ```sh pnpm run check pnpm pack node scripts/verify-profile.mjs /absolute/path/to/dsh/lib/bin.js 0.1.5-rc.1 dsh-api-usage-bar-0.2.0.tgz ``` Repeat with each exact version and matching CLI. `DSH_USAGE_TEST_ROOT` optionally selects a temporary-directory parent; every run creates a fresh child and sets `DSH_HOME` before the first CLI command. On Windows, use a parent on the npm installation drive if cross-volume fallback junctions cannot be resolved. Test directories are retained for inspection; the runner stops its server and removes the installed plugin. Authentication values are excluded from committed evidence.