# DSH 0.1.1 compatibility evidence

This record documents the narrow runtime boundary claimed by
`dsh-context-provenance` 0.1.1. It is compatibility evidence, not a security
audit or a claim about untested systems and releases.

## Exact release matrix

| DSH release | Status | Basis |
| --- | --- | --- |
| `0.1.0-rc.8` | `incompatible` | Outside the exact rc.2 peer contract; no runtime acceptance was attempted. |
| `0.1.1-rc.1` | `incompatible` | Outside the exact rc.2 peer contract; no runtime acceptance was attempted. |
| `0.1.1-rc.2` | `compatible` | Compile/unit/package gates and disposable Web Profile acceptance passed. |

The Node.js range is `^22.19.0 || >=24.0.0`. The disposable acceptance used
Node.js 24.19.0 and pnpm 11.19.0 on Windows. macOS and Linux remain untested;
the manifest does not infer system support from the Windows result.

## Disposable Web Profile acceptance

Date: 2026-08-24. The profile used a new, isolated `DSH_HOME` and a locally
packed `dsh-context-provenance-0.1.1.tgz`. It did not read or modify a real user
Profile.

1. `dsh plugin --profile web add <local-0.1.1-tarball>` exited 0. The profile
   manifest contained the plugin dependency and appended the plugin-owned
   `dsh-context-provenance` bundle.
2. `dsh --profile web --dump-config` exited 0 and contained the additive
   `context-provenance` entry from `cordis.patch.yml`.
3. `dsh --profile web --host 127.0.0.1 --port 31921` remained live and served
   the Web root with HTTP 200. The process was then stopped by the operator.
4. `dsh plugin --profile web remove dsh-context-provenance` exited 0. The
   dependency, bundle, and composed-config entry were all absent afterward.

No model, provider, remote API, GPU, persisted session, rollback, or real-user
Profile was exercised. Install, start, and uninstall passed; rollback remains
unknown.