add issue templates for bug reports and feature requests

.forgejo/issue_template/bug.yaml

@@ -0,0 +1,53 @@
+name: Bug Report
+about: Something is broken or behaving unexpectedly
+labels:
+  - bug
+body:
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Which part of the system is affected?
+      options:
+        - Frontend / UI
+        - Backend / API
+        - Download pipeline (yt-dlp, queue, progress)
+        - Scheduler / monitoring
+        - Database / data integrity
+        - Docker / deployment
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Describe the bug. Include the steps to reproduce if possible.
+      placeholder: |
+        1. Go to ...
+        2. Click ...
+        3. See error ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What should have happened?
+      description: Brief description of the correct behavior.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / error output
+      description: Paste any relevant logs, error messages, or stack traces. Check browser console (F12) for frontend issues, or docker logs for backend issues.
+      render: shell
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Anything else — what you already tried, when it started, screenshots, related issues.

.forgejo/issue_template/config.yaml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.forgejo/issue_template/feature.yaml

@@ -0,0 +1,48 @@
+name: Feature Request
+about: Suggest a new capability or improvement
+labels:
+  - enhancement
+body:
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Which part of the system does this touch?
+      options:
+        - Frontend / UI
+        - Backend / API
+        - Download pipeline (yt-dlp, queue, progress)
+        - Scheduler / monitoring
+        - New platform / source support
+        - Docker / deployment
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: Describe the use case or pain point. "I want to ..." or "Currently there's no way to ..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: How should it work? Be as specific as you can — endpoint behavior, UI flow, config options, etc. If you have multiple ideas, list them.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives or workarounds
+      description: Any workaround you're using today, or alternative approaches you considered.
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Links, mockups, examples from other tools, related issues.