Overview
dsh-context-provenance
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 030611/dsh-context-provenance --ref 3788ecbbdf9391d8ab0c29a18ed65bd59ca1c30fCapabilities
What it contributes
README / EN
Package documentation
An observe-only, CPU-only, local-only DeepSeek Harness plugin that reports what public runtime interfaces can actually prove about the requesting Agent's context. It retains only the two most recent ordinary agent-loop request observations in memory and exposes them through the existing Cordis inspect query mechanism. It performs no file, network, subprocess, GPU, persistence, session, permission, tool, model-routing, or request mutation.
LIMITATIONS
Known limitations
- Loader entries do not identify the bundle, profile, override, or dependency that introduced them. - Plugin inventory reveals ordered enablement and lifecycle categories, but never raw entry ids, package names, file URLs, absolute paths, or patch specifiers. - A tool name or schema does not identify its owning plugin. - Skill names remain visible because they are the public callable identity; source/provider are reduced to fixed categories. A skill name itself may still be sensitive if a deployment chooses a sensitive name. - AGENTS location categories are durable injected-source metadata, not a filesystem inventory or proof of hidden instructions. - Adjacent observations cover actual ordinary `llm/stream` calls seen while this plugin is mounted. Earlier requests, auxiliary calls, and observations lost on unload or restart are unavailable.