docs: add mock device plugin contribution templates

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,35 @@
+---
+name: Bug Report
+about: Report a problem encountered while using mock device plugin
+labels: bug
+---
+
+<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
+-->
+
+**What happened**:
+
+**What you expected to happen**:
+
+**How to reproduce it (as minimally and precisely as possible)**:
+
+**Anything else we need to know?**:
+
+- The selected mock vendor and relevant `hami-scheduler-device` ConfigMap section
+- Sanitized `hami.io/node-*-register` annotations
+- Relevant node capacity and allocatable extended resources
+- Relevant, time-bounded mock-device-plugin, kubelet, and scheduler log excerpts
+- The minimal deployment manifest and commands used to reproduce
+
+Before posting, include only relevant, time-bounded excerpts and remove or mask credentials, tokens, private keys, certificates, device identifiers, node or host names, workload identifiers, and internal image names.
+
+**Environment**:
+- mock-device-plugin version or commit:
+- HAMi version:
+- Kubernetes distribution and version:
+- Container runtime and version:
+- Mock vendor and resource names:
+- Deployment image and tag:
+- Host or emulated environment, such as Kind on macOS:
+- Kernel version, if applicable:
+- Others:

.github/ISSUE_TEMPLATE/enhancement.md

@@ -0,0 +1,13 @@
+---
+name: Enhancement Request
+about: Suggest an improvement to mock device plugin
+labels: enhancement
+---
+
+<!-- Please use this template for enhancement and feature requests. -->
+
+**What would you like to be added**:
+
+**Why is this needed**:
+
+**Additional context**:

.github/ISSUE_TEMPLATE/good-first.md

@@ -0,0 +1,19 @@
+---
+name: Good First Issue
+about: Publish a task suitable for a first-time contributor
+labels: "good first issue"
+---
+
+<!-- Please use this template when publishing a good first issue. -->
+
+**Task description**:
+
+**Suggested solution**:
+
+**Files or components involved**:
+
+**Acceptance criteria**:
+
+**Additional context**:
+
+Contributors: reply below before starting so a maintainer can assign the issue and confirm the intended approach.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,30 @@
+---
+name: Question
+about: Ask a question about mock device plugin
+labels: question
+---
+
+**Please provide a detailed description of your question**:
+
+**What have you already tried or investigated?**:
+
+**Relevant diagnostics, when applicable**:
+
+- Relevant `hami-scheduler-device` ConfigMap section:
+- Sanitized `hami.io/node-*-register` annotations:
+- Relevant node capacity and allocatable extended resources:
+- Time-bounded mock-device-plugin, kubelet, and scheduler log excerpts:
+- Minimal deployment manifest and reproduction commands:
+
+Before posting, include only relevant, time-bounded excerpts and remove or mask credentials, tokens, private keys, certificates, device identifiers, node or host names, workload identifiers, and internal image names.
+
+**Environment**:
+- mock-device-plugin version or commit:
+- HAMi version:
+- Kubernetes distribution and version:
+- Container runtime and version:
+- Mock vendor and resource names:
+- Deployment image and tag:
+- Host or emulated environment, such as Kind on macOS:
+- Kernel version, if applicable:
+- Others:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+**What type of PR is this?**
+
+<!--
+Add one of the following kinds:
+/kind bug
+/kind cleanup
+/kind deprecation
+/kind design
+/kind documentation
+/kind failing-test
+/kind feature
+/kind flake
+-->
+
+**What this PR does / why we need it**:
+
+**Which issue(s) this PR fixes**:
+Fixes #
+
+**Special notes for your reviewer**:
+
+**Does this PR introduce a user-facing change?**:
+
+**AI Disclosure**:
+
+<!-- Briefly disclose any AI assistance used. Do not add AI co-author or assistance trailers to commits. -->