chore(#537): add GitHub issue templates with type labels

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,79 @@
+name: Bug report
+description: Report a defect in existing behavior
+labels:
+  - type/bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a defect. Please search
+        [existing issues](https://github.com/fullsend-ai/fullsend/issues)
+        first.
+
+        **Security vulnerabilities** must be reported privately via
+        [SECURITY.md](https://github.com/fullsend-ai/fullsend/blob/main/SECURITY.md).
+        Do not file them as public issues.
+
+  - type: textarea
+    id: what-happens
+    attributes:
+      label: What happens
+      description: >
+        The current behavior, stated as fact. Include error messages,
+        symptoms, or the observable gap.
+      placeholder: "When I run `fullsend ...`, I get..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-should-happen
+    attributes:
+      label: What should happen
+      description: >
+        The expected behavior. Be specific enough that someone could
+        verify a fix against this description.
+      placeholder: "The command should..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: How to reproduce
+      description: >
+        Numbered steps from a clean state. Include the environment,
+        version, and configuration that matter.
+      placeholder: |
+        1.
+        2.
+        3.
+    validations:
+      required: true
+
+  - type: textarea
+    id: version
+    attributes:
+      label: Version and environment
+      description: >
+        fullsend version (`fullsend version` or git SHA), where it
+        happened (CLI, GitHub Actions, docs site), and OS if relevant.
+      placeholder: |
+        fullsend version:
+        Where it happened:
+        OS:
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: >
+        Why this matters, who it affects, related issues, logs, or
+        screenshots.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues and did not find a duplicate
+          required: true

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,60 @@
+name: Feature request
+description: Request a new capability
+labels:
+  - type/feature
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for proposing a new capability. Please search
+        [existing issues](https://github.com/fullsend-ai/fullsend/issues)
+        first. Describe the problem; solutions belong in follow-up
+        discussion or a linked PR.
+
+  - type: textarea
+    id: what-is-missing
+    attributes:
+      label: What is missing
+      description: >
+        The gap in current behavior. State it as fact, not as a
+        proposed implementation.
+      placeholder: "There is no way to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-should-happen
+    attributes:
+      label: What should happen
+      description: >
+        The desired behavior. Be specific enough that someone could
+        verify an implementation against this description.
+      placeholder: "A user should be able to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: why
+    attributes:
+      label: Why this matters
+      description: >
+        Who is affected and what prompted this request. Link related
+        issues or docs if they exist.
+      placeholder: "This affects anyone who..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: >
+        Examples, constraints, related work, or open questions.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues and did not find a duplicate
+          required: true

CONTRIBUTING.md

@@ -148,7 +148,7 @@ branch under edit. See [Running the fullsend CLI](docs/contributing/go-code.md#r
 
 ## Issues
 
-When in doubt about whether something warrants a PR, start with an issue. Issues are low-friction and can graduate into PRs, problem docs, or ADRs later.
+When in doubt about whether something warrants a PR, start with an issue. Issues are low-friction and can graduate into PRs, problem docs, or ADRs later. Bug reports and feature requests have [issue templates](https://github.com/fullsend-ai/fullsend/issues/new/choose) that apply type labels automatically; other topics can use a blank issue.
 
 To find open issues for human contribution, use the [contributor issue search](https://github.com/fullsend-ai/fullsend/issues?q=is%3Aissue%20is%3Aopen%20-author%3Aapp%2Ffullsend-ai-fullsend%20-author%3Aapp%2Ffullsend-ai-triage%20-author%3Aapp%2Ffullsend-ai-review%20-author%3Aapp%2Ffullsend-ai-prioritize%20-author%3Aapp%2Ffullsend-ai-coder%20-author%3Aapp%2Ffullsend-ai-retro%20-label%3Aready-to-code). This search excludes issues reserved for agents.