community: define contributor entry points and collect external install reports

[Altairpaca]

Goal

Make DSHelm legible as a community project rather than a repository whose roadmap is visible only through maintainer commits.

Work

• expose a small set of bounded contribution areas: provider/model evidence, platform verification, documentation, routing examples, and reproducible bugs;
• document what evidence is required before changing model capability metadata or compatibility claims;
• add/refresh contribution guidance for install reports and route traces with privacy redaction rules;
• point public DSH interface questions back to the relevant upstream Discussion rather than maintaining a parallel undocumented contract;
• collect the first external install reports and link them from this issue.

Success criteria

The community-roadmap target is at least three non-maintainer issues and two reusable user cases over time. This issue should remain focused on building the entry path and evidence quality; raw star count is not an acceptance criterion.

[Altairpaca]

Maintenance update (2026-09): PR #12 establishes the first contributor-funnel layer:

• adds a project Code of Conduct and Support/channel guide;
• routes usage/design questions to DSHelm Discussions and upstream DSH contract questions to DSH Discussions;
• makes non-trivial Core/schema/runtime/provider/compatibility/UI work issue-first;
• changes the PR template to require problem, linked issue, reproducible evidence, and compatibility/policy impact;
• links the community-health guides from both READMEs.

This addresses the entry-path/governance part of this issue. Remaining work should focus on discoverable bounded starter tasks and collecting actual non-maintainer install/routing reports; the issue should stay open until external evidence exists.

[Altairpaca]

Main-branch progress update:

• PR docs: tighten community contribution and support flow #12 is merged: contributor/support funnel, issue-first scope rules, evidence-driven PR template, Code of Conduct, and channel routing are now live.
• PR feat: add credential-free first-run routing example #13 is merged: the root README now exposes a credential-free first-run routing fixture; this provides one reusable observable user case while example: ship a credential-light planner → workers → reviewer first-run path #9 remains open for live bounded execution.
• good first issue: verify source-preview install on macOS Apple Silicon #15 and good first issue: verify source-preview install on Windows 11 + WSL2 #16 are open as bounded good first issue + help wanted platform-verification tasks for macOS Apple Silicon and Windows 11 + WSL2.
• PR chore: prepare publishable package surfaces and release contract #14 is merged: package/release hygiene and CI stale-run cancellation are now on main.

The repository-side entry path is therefore largely in place. Keep #10 open for the community-side success criteria: non-maintainer issues/PRs and linked external install/routing evidence.