Fix .gitea ISSUE_TEMPLATE casing conflict

.gitea/ISSUE_TEMPLATE/bug.yaml

@@ -1,56 +1,85 @@
-name: "Bug"
+name: Bug Report
-about: "Something is broken or incorrect"
+about: Report a bug or unexpected behavior
 title: "[Bug]: "
 labels:
-  - "type/bug"
+  - type/bug
-  - "status/backlog"
+  - status/backlog
 body:
-  - type: textarea
+  - type: markdown
-    id: summary
     attributes:
-      label: "Bug summary"
+      value: |
-      description: "What’s wrong?"
+        ## Bug Report
+        Use this template to report bugs. Provide as much detail as possible to help reproduce the issue.
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: Platform
+      description: Where did you encounter this bug?
+      options:
+        - Mobile (iOS)
+        - Mobile (Android)
+        - Desktop (Chrome)
+        - Desktop (Firefox)
+        - Desktop (Safari)
+        - Desktop (Edge)
+        - Multiple platforms
     validations:
       required: true
 
   - type: textarea
-    id: repro
+    id: description
     attributes:
-      label: "Steps to reproduce"
+      label: Bug Description
+      description: What went wrong? Be specific.
+      placeholder: "When I click X, I expected Y to happen, but instead Z happened."
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: How can we reproduce this bug?
       placeholder: |
-        1.
+        1. Navigate to '...'
-        2.
+        2. Click on '...'
-        3.
+        3. Scroll down to '...'
+        4. See error
     validations:
       required: true
 
   - type: textarea
     id: expected
     attributes:
-      label: "Expected behavior"
+      label: Expected Behavior
+      description: What should have happened?
     validations:
       required: true
 
   - type: textarea
     id: actual
     attributes:
-      label: "Actual behavior"
+      label: Actual Behavior
+      description: What actually happened?
     validations:
       required: true
 
   - type: textarea
-    id: impact
+    id: context
     attributes:
-      label: "Impact / severity"
+      label: Additional Context
-      placeholder: "Who is affected? How badly? Workaround?"
+      description: Screenshots, error messages, console logs, etc.
     validations:
       required: false
 
   - type: textarea
-    id: logs
+    id: fix-hints
     attributes:
-      label: "Logs / screenshots"
+      label: Fix Hints (if known)
-      description: "Paste logs or link images. Redact secrets."
+      description: Any ideas on what might be causing this or how to fix it?
-      render: shell
+      placeholder: |
+        - Might be related to: [file or component]
+        - Similar issue in: [other feature]
     validations:
       required: false

.gitea/ISSUE_TEMPLATE/chore.yaml

@@ -1,41 +1,70 @@
-name: "Chore"
+name: Chore / Maintenance
-about: "Refactor, maintenance, dependency updates, cleanup"
+about: Technical debt, refactoring, dependency updates, infrastructure
 title: "[Chore]: "
 labels:
-  - "type/chore"
+  - type/chore
-  - "status/backlog"
+  - status/backlog
 body:
-  - type: textarea
+  - type: markdown
-    id: goal
     attributes:
-      label: "Goal"
+      value: |
-      description: "What needs to be done and why?"
+        ## Chore / Maintenance Task
+        Use this template for technical debt, refactoring, dependency updates, or infrastructure work.
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Category
+      description: What type of chore is this?
+      options:
+        - Refactoring
+        - Dependency update
+        - Performance optimization
+        - Technical debt cleanup
+        - Infrastructure / DevOps
+        - Testing improvements
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What needs to be done and why?
+      placeholder: "We need to refactor X because Y..."
     validations:
       required: true
 
   - type: textarea
     id: scope
     attributes:
-      label: "Scope"
+      label: Scope / Files Affected
+      description: What parts of the codebase will be touched?
       placeholder: |
-        - Includes:
+        - frontend/src/features/[name]/
-        - Excludes:
+        - backend/src/features/[name]/
+        - docker-compose.yml
     validations:
       required: false
 
   - type: textarea
     id: acceptance
     attributes:
-      label: "Acceptance criteria"
+      label: Definition of Done
+      description: How do we know this is complete?
       placeholder: |
-        - [ ] ...
+        - [ ] All tests pass
-        - [ ] ...
+        - [ ] No new linting errors
+        - [ ] Performance benchmark improved by X%
     validations:
       required: true
 
   - type: textarea
-    id: test_plan
+    id: risks
     attributes:
-      label: "Test plan"
+      label: Risks / Breaking Changes
+      description: Any potential issues or breaking changes to be aware of?
     validations:
-      required: true
+      required: false

.gitea/issue_template/bug.yaml

@@ -1,85 +0,0 @@
-name: Bug Report
-about: Report a bug or unexpected behavior
-title: "[Bug]: "
-labels:
-  - type/bug
-  - status/backlog
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Bug Report
-        Use this template to report bugs. Provide as much detail as possible to help reproduce the issue.
-
-  - type: dropdown
-    id: platform
-    attributes:
-      label: Platform
-      description: Where did you encounter this bug?
-      options:
-        - Mobile (iOS)
-        - Mobile (Android)
-        - Desktop (Chrome)
-        - Desktop (Firefox)
-        - Desktop (Safari)
-        - Desktop (Edge)
-        - Multiple platforms
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Bug Description
-      description: What went wrong? Be specific.
-      placeholder: "When I click X, I expected Y to happen, but instead Z happened."
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to Reproduce
-      description: How can we reproduce this bug?
-      placeholder: |
-        1. Navigate to '...'
-        2. Click on '...'
-        3. Scroll down to '...'
-        4. See error
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected Behavior
-      description: What should have happened?
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual Behavior
-      description: What actually happened?
-    validations:
-      required: true
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional Context
-      description: Screenshots, error messages, console logs, etc.
-    validations:
-      required: false
-
-  - type: textarea
-    id: fix-hints
-    attributes:
-      label: Fix Hints (if known)
-      description: Any ideas on what might be causing this or how to fix it?
-      placeholder: |
-        - Might be related to: [file or component]
-        - Similar issue in: [other feature]
-    validations:
-      required: false

.gitea/issue_template/chore.yaml

@@ -1,70 +0,0 @@
-name: Chore / Maintenance
-about: Technical debt, refactoring, dependency updates, infrastructure
-title: "[Chore]: "
-labels:
-  - type/chore
-  - status/backlog
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Chore / Maintenance Task
-        Use this template for technical debt, refactoring, dependency updates, or infrastructure work.
-
-  - type: dropdown
-    id: category
-    attributes:
-      label: Category
-      description: What type of chore is this?
-      options:
-        - Refactoring
-        - Dependency update
-        - Performance optimization
-        - Technical debt cleanup
-        - Infrastructure / DevOps
-        - Testing improvements
-        - Documentation
-        - Other
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: What needs to be done and why?
-      placeholder: "We need to refactor X because Y..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: scope
-    attributes:
-      label: Scope / Files Affected
-      description: What parts of the codebase will be touched?
-      placeholder: |
-        - frontend/src/features/[name]/
-        - backend/src/features/[name]/
-        - docker-compose.yml
-    validations:
-      required: false
-
-  - type: textarea
-    id: acceptance
-    attributes:
-      label: Definition of Done
-      description: How do we know this is complete?
-      placeholder: |
-        - [ ] All tests pass
-        - [ ] No new linting errors
-        - [ ] Performance benchmark improved by X%
-    validations:
-      required: true
-
-  - type: textarea
-    id: risks
-    attributes:
-      label: Risks / Breaking Changes
-      description: Any potential issues or breaking changes to be aware of?
-    validations:
-      required: false