contributions: a bug report form and a pull request template (#5)

The issue form asks for what happened, with only that field required, then what 1.12.1 does,
how to see it, and the build line. Blank issues stay open, and questions point to the Discord.
The pull request template asks what changes, the 1.12.1 fact behind it, and how it was checked.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,25 @@
+name: Bug report
+description: Something benilla gets wrong, or does differently from 1.12.1.
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened
+      description: Screenshots or a clip help a lot; drag them in here.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What 1.12.1 does instead
+  - type: textarea
+    id: steps
+    attributes:
+      label: How to see it
+      placeholder: Where you were and what you did.
+  - type: input
+    id: build
+    attributes:
+      label: Build and setup
+      description: The `benilla build` line from the start of the terminal output, your OS, and the server you play on.
+      placeholder: "benilla build 64cca13 · 2026-09-24 · release, macOS 15, vmangos"

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Discord
+    url: https://discord.gg/wJSJx467G4
+    about: Questions, ideas and chat.

.github/pull_request_template.md

@@ -0,0 +1,7 @@
+<!-- One change per pull request. docs/CONTRIBUTING.md says what gets in. -->
+
+**What this changes**
+
+**What 1.12.1 does, and how you know** (the client's behaviour, a DBC field, a FrameXML line, a capture)
+
+**How you checked it** (`scripts/check.sh` or `scripts/gates.sh`, and before and after)