ci: add issue forms, labels-as-code and repo workflow

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,129 @@
+name: Bug Report
+description: Something works incorrectly (wrong results, missing behavior, errors).
+labels: ["kind:bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! Please search existing issues first to avoid duplicates.
+
+        If clice **crashed** (server exited, connection lost), please use the **Crash Report** template instead.
+
+  - type: input
+    id: version
+    attributes:
+      label: clice version
+      description: Output of `clice --version`, or the nightly build date / extension version you installed.
+      placeholder: e.g. clice 0.1.0-nightly-20260801
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating system
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: dropdown
+    id: editor
+    attributes:
+      label: Editor
+      options:
+        - VS Code
+        - Zed
+        - Neovim
+        - Vim
+        - Emacs
+        - Helix
+        - Sublime Text
+        - JetBrains
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: build_system
+    attributes:
+      label: Build system
+      description: How your `compile_commands.json` is generated.
+      options:
+        - CMake
+        - XMake
+        - Bazel
+        - Meson
+        - Make
+        - MSBuild
+        - GN
+        - SCons
+        - Other / not sure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Related area
+      description: Which part of clice does this relate to? Pick all that apply.
+      multiple: true
+      # Keep in sync with the feature: labels in .github/labels.yml.
+      options:
+        - Code completion
+        - Hover
+        - Semantic highlighting
+        - Inlay hints
+        - Diagnostics
+        - Document symbols
+        - Document links
+        - Folding ranges
+        - Formatting
+        - Inactive regions
+        - Signature help
+        - Go to definition / references
+        - Indexing
+        - C++20 modules
+        - Configuration
+        - Server / process management
+        - Toolchain detection
+        - Compilation database
+        - Editor extension
+        - Performance
+        - Other / not sure
+
+  - type: textarea
+    id: what_happened
+    attributes:
+      label: What happened
+      description: What you did, what you expected, and what actually happened.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: Steps and a minimal code snippet if possible. Small self-contained examples help us fix things much faster.
+      placeholder: |
+        1. Open a project with ...
+        2. Trigger completion at ...
+        3. Observe ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Relevant server log output, if available. Will be automatically formatted as code.
+      render: text
+
+  - type: textarea
+    id: config
+    attributes:
+      label: clice configuration
+      description: Your `clice.toml` and relevant editor settings, if customized.
+      render: toml

.github/ISSUE_TEMPLATE/config.yml

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

.github/ISSUE_TEMPLATE/crash_report.yml

@@ -0,0 +1,104 @@
+name: Crash Report
+description: The clice server crashed, exited unexpectedly, or the editor lost connection.
+labels: ["kind:crash"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Sorry about the crash! The **clice version** and **stack trace** fields below are parsed automatically to symbolize the crash, so please fill them in exactly as requested.
+
+  - type: input
+    id: version
+    attributes:
+      label: clice version
+      description: Output of `clice --version`, or the nightly build date / extension version you installed. Required to locate matching debug symbols.
+      placeholder: e.g. clice 0.1.0-nightly-20260801
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating system
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: dropdown
+    id: editor
+    attributes:
+      label: Editor
+      options:
+        - VS Code
+        - Zed
+        - Neovim
+        - Vim
+        - Emacs
+        - Helix
+        - Sublime Text
+        - JetBrains
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Related area
+      description: Which part of clice was involved, if you know? Pick all that apply.
+      multiple: true
+      # Keep in sync with the feature: labels in .github/labels.yml.
+      options:
+        - Code completion
+        - Hover
+        - Semantic highlighting
+        - Inlay hints
+        - Diagnostics
+        - Document symbols
+        - Document links
+        - Folding ranges
+        - Formatting
+        - Inactive regions
+        - Signature help
+        - Go to definition / references
+        - Indexing
+        - C++20 modules
+        - Configuration
+        - Server / process management
+        - Toolchain detection
+        - Compilation database
+        - Editor extension
+        - Other / not sure
+
+  - type: textarea
+    id: what_were_you_doing
+    attributes:
+      label: What were you doing when it crashed
+      description: The action that triggered the crash, e.g. opening a project, hovering a symbol, triggering completion.
+    validations:
+      required: true
+
+  - type: textarea
+    id: stack_trace
+    attributes:
+      label: Stack trace
+      description: Paste the stack trace from the crash output or log. Paste it as-is — do not edit or truncate it.
+      render: text
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Server log output around the crash, if available.
+      render: text
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: If you can reproduce the crash, describe how — ideally with a minimal code snippet.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,49 @@
+name: Feature Request
+description: Suggest a new feature or an improvement to existing behavior.
+labels: ["kind:feature-request"]
+body:
+  - type: dropdown
+    id: area
+    attributes:
+      label: Related area
+      description: Which part of clice does this relate to? Pick all that apply.
+      multiple: true
+      # Keep in sync with the feature: labels in .github/labels.yml.
+      options:
+        - Code completion
+        - Hover
+        - Semantic highlighting
+        - Inlay hints
+        - Diagnostics
+        - Document symbols
+        - Document links
+        - Folding ranges
+        - Formatting
+        - Inactive regions
+        - Signature help
+        - Go to definition / references
+        - Indexing
+        - C++20 modules
+        - Configuration
+        - Server / process management
+        - Toolchain detection
+        - Compilation database
+        - Editor extension
+        - Performance
+        - Other / new area
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What would you like clice to do? Performance and configuration suggestions are welcome here too.
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this useful? What is your use case, and how do you work around it today?