# DSH compatibility evidence

This record documents the disposable-Profile checks used for the `dsh-vision-mix` 0.2.3 manifest. It is install and startup evidence for one Windows environment, not a claim of complete cross-platform runtime coverage.

## Environment

| Item | Value |
|---|---|
| Checked | 2026-09-08 |
| OS | Windows x64 |
| Node.js | 24.18.0 |
| Package under test | Local `dsh-vision-mix-0.2.3.tgz` built from the candidate source |
| Profile isolation | A separate `DSH_HOME` for each DSH release |
| User Profile | Not read or modified |

## Result matrix

| DSH release | Manifest status | Install | Config load | Web start | Uninstall | Evidence summary |
|---|---|---:|---:|---:|---:|---|
| `0.1.2-rc.1` | `compatible` | Pass | Pass | Pass | Pass | The authenticated Web URL returned HTTP 200 on port 3091; the plugin entry disappeared after uninstall. |
| `0.1.3-alpha.1` | `unknown` | Not run | Not run | Not run | Not run | npm returned E404 because this exact release has no public `@deepseek-ai/dsh` artifact. |
| `0.1.3-alpha.2` | `unknown` | Pass | Pass | Blocked | Pass | The official CLI failed before loading this plugin because `fs-ext` had no built Windows native module; a local rebuild also failed because the required Windows SDK 10.0.26100.0 was unavailable. |

The `0.1.3-alpha.2` result is not marked `incompatible`: its disposable Profile accepted the plugin and generated a config containing only the additive `dsh-vision-mix` entry, but the host could not reach plugin initialization. It is not marked `compatible` because a successful Web startup was not observed.

## `0.1.2-rc.1` procedure

The test used `E:\git\dsh-vision-mix\.compat-work-rc1\dsh-home` as `DSH_HOME` and ran:

```powershell
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh --version
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh plugin --profile web add E:\git\dsh-vision-mix\.compat-artifacts\dsh-vision-mix-0.2.3.tgz
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh --profile web --dump-config
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh web --port 3091
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh plugin --profile web remove dsh-vision-mix
pnpm --package=@deepseek-ai/dsh@0.1.2-rc.1 dlx dsh --profile web --dump-config
```

The generated config contained one plugin-owned Bundle entry:

```yaml
- id: dsh-vision-mix
  name: dsh-vision-mix
```

No protected `@deepseek-ai/*` package name or official entry ID was replaced. After the Web response was checked, the test process was stopped, the package was removed, the final config contained no `dsh-vision-mix` entry, and port 3091 had no listener.

## `0.1.3-alpha.2` procedure

The same install, `--dump-config`, and uninstall sequence used `E:\git\dsh-vision-mix\.compat-work-alpha2\dsh-home` and DSH `0.1.3-alpha.2`. The Web check used port 3092. The startup failure named the official `session-persistence-jsonl` entry and occurred while requiring `fs-ext`, before `dsh-vision-mix` was imported. The final config again contained no plugin entry after uninstall, and port 3092 had no listener.