chore: add issue templates (bug, feature, refactor)

.codeberg/ISSUE_TEMPLATE/bug.yaml

@@ -0,0 +1,49 @@
+name: Bug Report
+about: Something is broken or behaving incorrectly
+labels:
+  - bug
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What's broken
+      description: What happens vs what should happen. Include error messages, logs, or screenshots.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: Minimal steps to trigger the bug.
+      placeholder: |
+        1. Run `dev-poll.sh disinto.toml`
+        2. See error: "..."
+    validations:
+      required: true
+  - type: textarea
+    id: affected-files
+    attributes:
+      label: Affected files
+      description: Which source files need to change? Include test files that cover this area.
+      placeholder: |
+        - dev/dev-agent.sh
+        - lib/agent-session.sh
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: How do we know it's fixed?
+      placeholder: |
+        - [ ] Bug no longer reproduces with steps above
+        - [ ] Regression test added
+        - [ ] CI green
+    validations:
+      required: true
+  - type: textarea
+    id: deps
+    attributes:
+      label: Dependencies
+      description: Issues that must be merged first. Leave empty if none.
+      placeholder: "- #NNN (reason)"

.codeberg/ISSUE_TEMPLATE/feature.yaml

@@ -0,0 +1,51 @@
+name: Feature
+about: New functionality or enhancement
+labels:
+  - backlog
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / motivation
+      description: Why is this needed? What's the current limitation?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: How should it work? Be specific about behavior, not just "add X."
+    validations:
+      required: true
+  - type: textarea
+    id: affected-files
+    attributes:
+      label: Affected files
+      description: Which files need to change? Include test files if applicable.
+      placeholder: |
+        - lib/agent-session.sh
+        - formulas/run-gardener.toml
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: Checkboxes. Max 5 — if you need more, split the issue.
+      placeholder: |
+        - [ ] Feature works as described
+        - [ ] Tests added / updated
+        - [ ] CI green
+    validations:
+      required: true
+  - type: textarea
+    id: deps
+    attributes:
+      label: Dependencies
+      description: Issues that must be merged first. Leave empty if none.
+      placeholder: "- #NNN (reason)"
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Links to docs, prior art, design decisions, related issues.

.codeberg/ISSUE_TEMPLATE/refactor.yaml

@@ -0,0 +1,50 @@
+name: Refactor / Tech Debt
+about: Code improvement without changing behavior
+labels:
+  - backlog
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What needs cleaning up
+      description: Current state and why it's a problem.
+    validations:
+      required: true
+  - type: textarea
+    id: approach
+    attributes:
+      label: Approach
+      description: How to fix it. Specifics matter — the dev-agent will follow this literally.
+    validations:
+      required: true
+  - type: textarea
+    id: affected-files
+    attributes:
+      label: Affected files
+      description: Every file that will change. Include test files.
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      placeholder: |
+        - [ ] Refactored code works identically (no behavior change)
+        - [ ] Existing tests still pass
+        - [ ] CI green
+    validations:
+      required: true
+  - type: textarea
+    id: deps
+    attributes:
+      label: Dependencies
+      description: Issues that must be merged first. Leave empty if none.
+      placeholder: "- #NNN (reason)"
+  - type: textarea
+    id: risks
+    attributes:
+      label: Risks
+      description: What could break? Which e2e tests cover this area?
+      placeholder: |
+        - Phase handler changes could break dev/action/review lifecycle
+        - ShellCheck may flag new patterns