chore: adopt GitHub Issue Types in issue templates

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,75 @@
+---
+name: Bug report
+about: Report behavior that works incorrectly.
+labels: ["triage"]
+assignees: ''
+type: Bug
+---
+
+<!--
+Maintainers fix reproducible reports faster. Fill every section not marked optional.
+Bugs stand alone or nest under an Epic, Feature, Story, or Task.
+Link this bug as a sub-issue of the work it blocks.
+Never paste secrets, credentials, or tokens.
+-->
+
+### Existing issue check
+
+<!-- Search open and closed issues before filing. -->
+
+- [ ] I searched the existing issues for this bug
+
+### Bug summary
+
+<!-- State what works incorrectly and where. -->
+
+### Steps to reproduce
+
+<!--
+1. Start the gateway with this configuration: ...
+2. Call this endpoint or run this command: ...
+3. Observe: ...
+-->
+
+### Expected behavior
+
+<!-- Describe the behavior you expect. -->
+
+### Actual behavior
+
+<!-- Describe what happened. Include the full error text. -->
+
+### Affected area
+
+<!-- Check every area involved. -->
+
+- [ ] Gateway core (API, services, middleware)
+- [ ] Admin UI
+- [ ] Federation or transports (SSE, WebSocket, stdio, gRPC)
+- [ ] Auth, RBAC, or security
+- [ ] Rust runtime (crates/mcp_runtime)
+- [ ] CLI, Makefile, or scripts
+- [ ] Containers or CI
+- [ ] Documentation
+- [ ] Other
+
+### Log output (optional)
+
+<!-- Paste stack traces or log lines. Never paste secrets. -->
+
+```shell
+
+```
+
+### Environment
+
+<!-- The `/version` endpoint reports most values. -->
+
+- Version or commit:
+- Runtime:
+- Platform / OS:
+- Container:
+
+### Additional context (optional)
+
+<!-- List configuration details, workarounds tried, or related issues. -->

.github/ISSUE_TEMPLATE/chore.md

@@ -0,0 +1,57 @@
+---
+name: Chore
+about: A maintenance task such as CI, dependencies, tooling, or formatting.
+labels: ["triage", "chore"]
+assignees: ''
+type: Task
+---
+
+<!--
+Chores are Tasks. This template applies the `chore` label.
+Chores stand alone or complete a Story. Chores typically cover CI
+pipelines, hooks and linters, dependency updates, build tooling,
+containers, and security scans.
+-->
+
+### Existing issue check
+
+<!-- Search open and closed issues before filing. -->
+
+- [ ] I searched the existing issues for this chore
+
+### Parent Story (optional)
+
+<!-- Give the issue number of the Story this Chore completes. Leave empty for standalone work. -->
+
+**Parent Story:**
+
+### Area affected
+
+<!-- Check every area involved. -->
+
+- [ ] GitHub Actions or CI pipelines
+- [ ] Pre-commit hooks or linters
+- [ ] Formatting (black, isort, ruff)
+- [ ] Type checking (mypy, ty, pyrefly)
+- [ ] Dependency updates or cleanup
+- [ ] Build system or Makefile
+- [ ] Containers (Docker, Podman, Compose)
+- [ ] SBOM, CVE scans, or license checks
+- [ ] Docs tooling or spellcheck
+- [ ] Other
+
+### Context
+
+<!-- State why this chore exists and what it unblocks or improves. -->
+
+### Work required
+
+<!-- Describe the change to make. Name known targets, configs, or files. -->
+
+### Definition of done
+
+<!-- Describe the checkable state that closes this Chore. -->
+
+### References (optional)
+
+<!-- List related Make targets, issues, pull requests, or commands. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/IBM/mcp-context-forge/discussions
+    about: Use Discussions for questions and proposals before you open an issue.
+  - name: Security vulnerability
+    url: https://github.com/IBM/mcp-context-forge/security/advisories/new
+    about: Report vulnerabilities privately. Do not open a public issue for them.

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,49 @@
+---
+name: Documentation update
+about: Fix, clarify, or extend documentation.
+labels: ["triage", "documentation"]
+assignees: ''
+type: Task
+---
+
+<!--
+Documentation updates are Tasks. This template applies the `documentation` label.
+Preview suggested changes locally with `cd docs && make serve`.
+-->
+
+### Existing issue check
+
+<!-- Search open and closed issues before filing. -->
+
+- [ ] I searched the existing issues for this documentation problem
+
+### Documentation issue
+
+<!-- State what is wrong, missing, or unclear. -->
+
+### Location
+
+<!-- List the affected files, sections, or pages. Use one line per location.
+
+docs/docs/using/agents/crewai.md
+https://ibm.github.io/mcp-context-forge/overview/features/
+-->
+
+### Kind of issue
+
+<!-- Check every kind that applies. -->
+
+- [ ] Typo or formatting
+- [ ] Outdated or incorrect information
+- [ ] Missing explanation or example
+- [ ] Unclear instructions
+- [ ] New page or section
+- [ ] Other
+
+### Suggested fix (optional)
+
+<!-- Describe the correction or new text. Use markdown. -->
+
+### Additional context (optional)
+
+<!-- Add screenshots, platform notes, or related issues. -->