Summary

Add structured GitHub issue templates to guide contributors when filing bugs and requesting features:

• Bug report template (.github/ISSUE_TEMPLATE/bug_report.md) — description, repro steps, actual/expected behaviour, environment info (CLI version, OS, Go version)
• Feature request template (.github/ISSUE_TEMPLATE/feature_request.md) — summary, current state, proposed changes, usage examples, API reference links

These were scoped during #373 but deferred to allow discussion on format. The "coming soon" notes in CONTRIBUTING.md should be updated once templates land.

Worth exploring

• Pull request template (.github/PULL_REQUEST_TEMPLATE.md) — a minimal summary + test plan checklist to match existing team practice

References

• Discussion in PR docs(DCP-2585): add CONTRIBUTING.md and update cross-references #373
• Patterns from existing issues: Fix Project Create #243, Make prolific study list project and status filters non exclusive #245, Create a Batch #229, Bring study create up to date with API spec #283, Request participant to return a submission #303, Global Output Flag (structured JSON by default, GH CLI standard) #357, Automated Release Process #358
• Patterns from existing PRs: fix(DCP-2422): use inclusive approach for changelog area mapping #331, feat(DCP-2500): add study update command #348, ci: fix dependabot commit messages to match conventional format #349, feat(DCP-2517): add submission request-return command #352, feat(DCP-2527): add min/max validation for free_text and free_text_with_unit instructions #354