Overview
dsh-trace
Community · Topic auto-analysis — Automatically discovered through the dsh-plugin GitHub Topic. Static checks verified a pinned public root bundle contract and committed files without executing third-party code. This is not a human review, security audit, runtime smoke test, publisher identity check, or official endorsement.
Install this bundle from GitHub
The CLI validates the bundle, invokes native DSH, then reports completion.
npx dshpub add vibeinging/dsh-trace --ref caadf1b831ae2643bd25a365cc1356c2100e7a05Capabilities
What it contributes
README / EN
Package documentation
English | 中文
LIMITATIONS
Known limitations
- **Private Git distribution** — the package is not published to a registry. Installation requires authorized GitHub access, pnpm `11.7.0`, a reviewed commit, and a compatible DSH profile. - **The database is a native dependency** — `@yitrace/db` currently supplies prebuilt packages for macOS arm64/x64, glibc Linux arm64/x64, and Windows x64. Other operating systems, CPU targets, and musl Linux are not covered by this package's current lockfile. - **One local storage mode** — the plugin deliberately has no HTTP backend or cross-machine transport. Give concurrently running DSH processes separate writable data directories unless the yiTrace database documents a shared-writer setup for that deployment. - **State is segmented across telemetry reloads** — disposal closes open spans as failed and resets the adapter's message accumulator. A later positioned event (`turn`/`step`) opens a span marked `dsh.recovered_segment`; its input includes only redacted message events observed after that backend instance loaded. A lone `user/message` has no position in its payload and cannot reconstruct a missing step by itself. - **Hashed session identity** — yiTrace's TypeScript SDK accepts a numeric `session_id`, while DSH owns opaque string ids. FNV-1a makes the mapping stable but leaves a theoretical 64-bit collision risk; a future SDK string-id surface would remove this compromise.