Update issue templates for GitHub issue types (#1146)

.github/ISSUE_TEMPLATE/bug.md

@@ -1,12 +1,14 @@
 ---
 name: Bug
 about: Used for bug reports
-title: "[Bug] "
-labels: bug, enhancement
+title: ""
+type: Bug
 assignees: ''
 
 ---
 
+Use a concise sentence-case title that describes the broken behavior. Do not add `Bug` or bracket prefixes to the title.
+
 ## Summary
 
 What failed, in one or two sentences (user-visible symptom or test failure).

.github/ISSUE_TEMPLATE/feature.md

@@ -1,12 +1,14 @@
 ---
 name: Feature
 about: Used for new features or suggestions
-title: "[Feature] "
-labels: enhancement
+title: ""
+type: Feature
 assignees: ''
 
 ---
 
+Use a concise sentence-case title that describes the requested outcome. Do not add `Feature` or bracket prefixes to the title.
+
 ## Summary
 
 What we’re building and the user-visible outcome.

.github/ISSUE_TEMPLATE/task.md

@@ -0,0 +1,35 @@
+---
+name: Task
+about: Used for work items that are not primarily bugs or net-new features
+title: ""
+type: Task
+assignees: ''
+
+---
+
+Use a concise sentence-case title that describes the work item. Do not add `Task` or bracket prefixes to the title.
+
+## Summary
+
+What needs to be done and the intended outcome.
+
+## Problem / Context
+
+Why this work matters, what it unblocks, and any constraints or dependencies. Include links to related issues, PRs, docs, or design context where helpful.
+
+## Scope (optional)
+
+What is in scope, what is not, and any implementation notes or tradeoffs worth capturing up front.
+
+## Acceptance criteria
+
+- [ ] **Task 1** — TODO
+- [ ] **Task 2** — TODO
+- [ ] **Task 3** — TODO
+- [ ] **Diff coverage ≥ 80%** — the implementing PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by [`.github/workflows/coverage.yml`](../../.github/workflows/coverage.yml)) when code changes are involved.
+
+- …
+
+## Related
+
+Links to issues, PRs, docs, or prior discussion.