docs: add issue/PR templates and commit conventions

- Add bug report and feature request issue templates (structured YAML forms)
- Add config.yml to disable blank issues and redirect to Discussions
- Add pull_request_template.md with testing and contributor checklists
- Document Conventional Commits conventions in CONTRIBUTING.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: tschm

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,57 @@
+name: Bug Report
+description: Report a bug or unexpected behaviour
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug. Please fill out the sections below.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of what the bug is.
+      placeholder: What happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: Minimal steps to reproduce the behaviour.
+      placeholder: |
+        1. Run `make ...`
+        2. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behaviour
+      description: What did you expect to happen?
+    validations:
+      required: true
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: |
+        Relevant versions and system info. Run `make info` if available.
+      placeholder: |
+        - OS: macOS 14 / Ubuntu 24.04 / Windows 11
+        - Python: 3.13.x
+        - rhiza version:
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Logs, screenshots, or anything else that may be helpful.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question / Discussion
+    url: https://github.com/jqr-labs/rhiza/discussions
+    about: Ask questions or discuss ideas in GitHub Discussions rather than opening an issue.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,41 @@
+name: Feature Request
+description: Suggest a new feature or enhancement
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for proposing a feature. Please align with the team before investing significant effort.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / motivation
+      description: What problem does this solve? Why is it valuable?
+      placeholder: As a contributor I find it hard to ... because ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: Describe the solution you have in mind.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Other approaches you have considered and why you ruled them out.
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Links, mockups, prior art, or anything else that may be helpful.
+    validations:
+      required: false

.github/pull_request_template.md

@@ -0,0 +1,23 @@
+## Summary
+
+<!-- One or two sentences describing what this PR does and why. -->
+
+Closes #<!-- issue number -->
+
+## Changes
+
+<!-- Bullet list of what changed. -->
+
+-
+
+## Testing
+
+- [ ] `make test` passes locally
+- [ ] `make fmt` has been run
+- [ ] New tests added (or explain why not needed)
+
+## Checklist
+
+- [ ] Commit messages follow the [Conventional Commits](https://www.conventionalcommits.org/) format
+- [ ] Documentation updated if behaviour changed
+- [ ] `make deptry` passes (no unused or missing dependencies)

CONTRIBUTING.md

@@ -55,6 +55,52 @@ following:
 - Browse the open issues,
   and look for the issues tagged "help wanted".
 
+## Commit conventions
+
+We use [Conventional Commits](https://www.conventionalcommits.org/). Every commit message must have a
+structured prefix so tooling can generate changelogs automatically.
+
+### Format
+
+```
+<type>(<scope>): <short summary>
+```
+
+`scope` is optional but encouraged when the change is limited to a specific area.
+
+### Types
+
+| Type       | When to use                                      |
+|------------|--------------------------------------------------|
+| `feat`     | New feature or capability                        |
+| `fix`      | Bug fix                                          |
+| `docs`     | Documentation only                               |
+| `refactor` | Code change that is neither a fix nor a feature  |
+| `test`     | Adding or updating tests                         |
+| `ci`       | CI / build system changes                        |
+| `chore`    | Maintenance tasks (deps, tooling, config)        |
+| `perf`     | Performance improvement                          |
+| `security` | Security fix or hardening                        |
+
+### Examples
+
+```
+feat(templates): add devcontainer template for Python 3.13
+fix: resolve path issue in bootstrap script
+docs: update CONTRIBUTING with commit conventions
+ci: cache uv dependencies in GitHub Actions
+```
+
+### Breaking changes
+
+Append `!` after the type/scope and add a `BREAKING CHANGE:` footer:
+
+```
+feat!: rename make target from `book` to `docs`
+
+BREAKING CHANGE: `make book` no longer exists; use `make docs`.
+```
+
 ## Code style
 
 We use ruff to enforce our Python coding style.