Use the narrowest channel that matches the problem. This keeps reproducible bugs, design discussion, upstream DSH questions, and security reports from being mixed together.
| Need | Where to go |
|---|---|
| Reproducible DSHelm bug | Bug report |
| Installation / platform evidence | Install report |
| Real routing scenario or model-selection evidence | Routing scenario |
| Feature proposal | Feature request |
| Usage question, design discussion, or idea that is not yet a scoped bug/feature | DSHelm Discussions |
| Question about DSH public interfaces or runtime behavior | DeepSeek Harness Discussions |
| Security vulnerability | SECURITY.md |
Search existing Issues and Discussions first. Include the DSHelm commit/version, DSH version, platform, minimal reproduction, and a redacted Resolution Trace or log when relevant. Do not post tokens, cookies, account identifiers, private repository names, or sensitive local paths.
DSHelm is an alpha project maintained on a best-effort basis. There is no guaranteed response or fix SLA. Maintainers prioritize reproducible defects, release blockers, compatibility evidence, and changes that preserve the Core / DSH boundary documented in docs/ARCHITECTURE.md.