chore: add bug report and feature request issue templates

.forgejo/issue_template/bug.yaml

@@ -0,0 +1,67 @@
+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:
+        - Pipeline — LLM extraction, Celery tasks, transcript processing
+        - Content quality — incorrect extractions, bad classifications, missing data
+        - Search — Qdrant vector search, keyword fallback, autocomplete
+        - Frontend / UI — technique pages, creator pages, navigation, styling
+        - Backend / API — endpoints, auth, admin panel
+        - Ingestion — watcher service, transcript upload, file processing
+        - Infrastructure — Docker, PostgreSQL, Redis, Qdrant, Ollama, LightRAG
+        - Other
+    validations:
+      required: true
+
+  - type: input
+    id: location
+    attributes:
+      label: Where specifically?
+      description: Page URL, API endpoint, pipeline stage, service name, or container.
+      placeholder: "/techniques/compression-sidechain, stage 5 synthesis, chrysopedia-worker, etc."
+
+  - type: dropdown
+    id: reproducibility
+    attributes:
+      label: Reproducibility
+      options:
+        - Always
+        - Sometimes
+        - Saw it once
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Describe the bug and how to reproduce it. For pipeline issues, include the video/transcript that triggered it. For content issues, link to the affected technique page.
+      placeholder: |
+        Steps:
+        1. Ingested transcript for "..."
+        2. Pipeline stage X failed / produced bad output
+        3. See error ...
+
+        Expected: ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / error output
+      description: "Paste relevant logs. Check: docker logs chrysopedia-api, docker logs chrysopedia-worker, browser console (F12), or the admin pipeline panel."
+      render: shell
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Source video URL, creator name, transcript filename, screenshots, what you already tried.

.forgejo/issue_template/config.yaml

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

.forgejo/issue_template/feature.yaml

@@ -0,0 +1,57 @@
+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:
+        - Pipeline — extraction stages, LLM prompts, processing logic
+        - Content — new technique types, categories, metadata fields
+        - Search & discovery — ranking, filters, recommendations, LightRAG
+        - Frontend / UI — pages, components, navigation, themes
+        - Creator experience — consent, dashboard, attribution
+        - Admin — pipeline management, monitoring, bulk operations
+        - Ingestion — new input formats, sources, automation
+        - API / integrations — new endpoints, external services
+        - Infrastructure — performance, scaling, deployment
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope
+      description: Rough size of what you're asking for.
+      options:
+        - Tweak — adjust existing behavior
+        - Feature — new capability or screen
+        - Large — multi-part, needs planning
+    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 — UI flow, pipeline behavior, prompt changes, new fields, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Examples from other tools, mockups, links to related techniques/creators, related issues.