# Distribution status

## Published v0.4.0 destinations

Read back on 2026-09-20:

- [npm 0.4.0](https://www.npmjs.com/package/dsh-session-insights/v/0.4.0) is public and `latest` resolves to `0.4.0`.
- [GitHub Release v0.4.0](https://github.com/GreenLv/dsh-session-insights/releases/tag/v0.4.0) and its annotated tag point to `395bb4c308f053c494074e252950c63599fa4fce`. The bilingual notes and all three downloaded assets match the frozen release files.
- The npm and GitHub tarballs match byte for byte: SHA-256 `a95c79096ffafdd3acdf9ad161c98a69f1ac39485e96b3c1641ac2635672b34a`.
- A [Chinese update](https://github.com/AI-Scarlett/DSH-Store/issues/965#issuecomment-5750277537) describes the runtime changes in STORE issue #965. STORE recheck and real DSH host acceptance remain pending.

The [release receipt](acceptance/v0.4.0-release-receipt.json) records the public identities. This entry was added after publication; it does not change the released package. Earlier sections describe their named release dates.

## Published v0.3.0 destinations

1. [GitHub Release `v0.3.0`](https://github.com/GreenLv/dsh-session-insights/releases/tag/v0.3.0) is published as a non-draft, non-prerelease release (read back 2026-08-25); the tag points at commit `d6065402`.
2. [`dsh-session-insights@0.3.0` on npm](https://www.npmjs.com/package/dsh-session-insights) is published, and `latest` resolves to `0.3.0`. Registry `dist.shasum` = `7d89604458ff9a15bc3f50d0ab4ef40c3a299d3f`, matching the local release-commit `npm pack --dry-run` shasum.
3. Community indexes and dsh.pub resolve the npm/`latest` entry or the `main`-branch screenshot URLs, so screenshots refresh automatically; no community-index PR is expected for this release.
4. The sibling cross-machine skill-sync consumer index pins this release at its own `dsh-session-insights.json` (`v0.3.0` / `d6065402`).

Validation: local pytest (37) and node --test (11) pass; CI matrix (ubuntu/macos/windows × 3.11–3.13) runs on the `v0.3.0` commit. Native-acceptance evidence **is recorded**: cross-platform acceptance completed 2026-08-25 — macOS offline regression plus the isolated deterministic readback (six gates pass; three real-model gates `not_run`), and the Windows-native record closing the real-model semantic round trips, rendered-English-DOM evidence, and a full `verify.json` `status=pass` — see the [v0.3.0 acceptance record](acceptance/v0.3.0-candidate.md), the [Windows record](acceptance/windows-v0.3.0.md), and the [cross-platform summary](acceptance/v0.3.0-summary.md). A fresh macOS re-verification of the deterministic subset (managed 0.3.0 runtime, isolated home, three-report cache pattern miss/hit/invalidate, verifier skill-discovery) was run 2026-08-29. The remaining explicit boundary is the interactive `/session-insights` slash dispatch inside a live, plugin-loaded DSH Web profile (unverified on both platforms); re-tests of the v0.2.0 edges were not repeated for this release.

## Published v0.2.0 destinations

The following `v0.2.0` destinations have been published and independently read back:

1. [`dsh-session-insights@0.2.0` on npm](https://www.npmjs.com/package/dsh-session-insights) is published, and `latest` resolves to `0.2.0`. The registry tarball matches the accepted release artifact.
2. [GitHub Release `v0.2.0`](https://github.com/GreenLv/dsh-session-insights/releases/tag/v0.2.0) is published as a non-draft, non-prerelease release. Its annotated tag and downloadable assets match the accepted release identity.
3. [dsh.pub](https://dsh.pub/en/plugins/dsh-session-insights/) has a public plugin entry. Its [submission PR #29](https://github.com/dsh-pub/dsh-pub/pull/29) was merged and the directory deployment completed successfully.

The repository `package.json` declares `dsh.engines.dsh` (`>=0.1.0-rc.8`); the published `0.2.0` tarball predates that declaration, which takes effect on the next npm release.

Exact package, checksum, tag, Release, CI, and native-platform evidence remains recorded in the [v0.2.0 acceptance record](acceptance/v0.2.0-candidate.md).

## Community indexes and marketplaces

| Channel | Entry | Status | Evidence |
|---|---|---|---|
| [Awesome DeepSeek Harness](https://github.com/Dominic789654/awesome-deepseek-harness#session--memory-management) | `GreenLv/dsh-session-insights` | Listed | Entry visible in the generated list under "Session & Memory Management" (read back 2026-08-25) |
| [awesome-dsh-plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) | `GreenLv/dsh-session-insights` (category `session`) | Listed | Listing merged via [PR #2680](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2680), read back from the generated README and the published catalog at `https://awesome-dsh-plugin.com/plugins.json` (2026-08-23). Screenshots registered via [PR #2937](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2937) (merged `4886a9a4`, 2026-08-24): the public catalog exposes a `screenshots` array with both dashboard images, both image URLs return PNG content, and the storefront page exposes the npm install command (read back 2026-08-26). Visual rendering of the catalog screenshots remains a separate dsh-market readback. |
| [dsh-market.com](https://dsh-market.com/) workshop | `dsh-session-insights` (category `tools`) | Listed | Community-index registration [PR #1055](https://github.com/zhu1090093659/dsh-web-ui/pull/1055) merged into `dev` (merge commit `05c57c8a`) then deployed to `main`; read back from the live manifest at `https://dsh-market.com/manifest/plugins.json` (generated 2026-08-24, 37 entries, rank 37) |
| [dshworks/awesome-dsh-plugins](https://github.com/dshworks/awesome-dsh-plugins) | `GreenLv/dsh-session-insights` (category `bundle`) | Listed | Added via [PR #54](https://github.com/dshworks/awesome-dsh-plugins/pull/54) (merged 2026-08-24); entry read back from `data/plugins.json` (`status: verified`, npm linked). Registry site: `https://dsh.works/awesome-dsh-plugins/` |
| [dshplugin.app](https://dshplugin.app/plugins/dsh-session-insights) | `dsh-session-insights` | Listed | Anonymous directory page read back 2026-08-30. Directory visibility is independent of package installation, runtime behavior, and screenshot rendering. |