docs: add issue templates, PR template, and labeler config

- Bug report: version, component, repro steps, logs, environment
- Feature request: component, description, alternatives
- Question: with links to docs/Discord
- PR template: summary, type, testing checklist, screenshots
- Labeler: auto-label PRs (python, config, c-backend, styling, ci, docs, assets, install)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+## Summary
+
+<!-- What does this PR do? Keep it brief. -->
+
+## Related Issue
+
+<!-- Link: "Closes #123" or "Fixes #123" -->
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Refactor
+- [ ] Documentation
+- [ ] CI / Build
+- [ ] Config / Assets
+
+## What Changed
+
+<!-- Bullet list of key changes -->
+
+## Component(s) Affected
+
+<!-- Panel, Dock, Spotlight, App Switcher, Lock Screen, Notifications, Widgets, Global Menu, Settings, etc. -->
+
+## Testing
+
+<!-- How did you test this? Include commands or steps. -->
+
+- [ ] `uv run pre-commit run --all-files` passes
+- [ ] Tested locally on Hyprland
+- [ ] Existing functionality not broken
+
+## Screenshots / Videos
+
+<!-- If UI changed, before → after. Delete if not applicable. -->
+
+## Checklist
+
+- [ ] Code follows project style (`ruff` lint + format)
+- [ ] No new warnings or errors
+- [ ] Docs updated (if applicable)
+- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)