docs: add community health files

Signed-off-by: FenjuFu <fufenjupku@gmail.com>

Author: FenjuFu

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,52 @@
+# iFLYTEK Open Source Community Code of Conduct
+
+As contributors, maintainers, and participants in the iFLYTEK Open Source
+Community, we pledge to make participation in this project a harassment-free
+experience for everyone.
+
+## Our standards
+
+Examples of behavior that contributes to a positive community include:
+
+- Demonstrating empathy and kindness toward other people
+- Respecting differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility, apologizing, and learning from mistakes
+- Focusing on what is best for the overall community
+- Using welcoming and inclusive language
+
+Examples of unacceptable behavior include:
+
+- Sexualized language or imagery and unwelcome sexual attention
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing another person's private information without explicit permission
+- Violence, threats of violence, stalking, or unwelcome physical contact
+- Knowingly providing false information during an investigation
+- Retaliating against someone who reports an incident or acts as a witness
+
+Project maintainers may remove, edit, or reject contributions that do not align
+with this Code of Conduct and will apply these standards fairly and consistently.
+
+## Scope
+
+This Code of Conduct applies in all project and community spaces. It also applies
+when an individual represents the project or directs words or actions at a
+community participant in the context of a project activity.
+
+## Reporting and enforcement
+
+Report incidents privately to the
+[iFLYTEK Open Source Code of Conduct Committee](https://github.com/iflytek/community/tree/master/code-of-conduct).
+If a private contact channel is unavailable, use the
+[iFLYTEK community issue tracker](https://github.com/iflytek/community/issues/new)
+and avoid including sensitive personal information in a public report.
+
+The response team will review reports and determine appropriate action. Retaliation
+against reporters or witnesses is prohibited.
+
+## Attribution
+
+This project follows the
+[iFLYTEK Open Source Community Code of Conduct](https://github.com/iflytek/community/blob/master/code-of-conduct.md),
+which is adapted from the Contributor Covenant, version 2.0.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,42 @@
+name: Bug report
+description: Report a reproducible problem in Domux
+title: "[Bug]: "
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: Thanks for helping us improve Domux. Please search existing issues first.
+  - type: textarea
+    id: description
+    attributes:
+      label: Problem
+      description: What happened, and what did you expect instead?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Include the smallest reproducible input, command, or code sample.
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Domux version or commit
+      placeholder: v0.1.0 or commit SHA
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Operating system, Python version, hardware, and relevant dependencies.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs and additional context
+      description: Remove credentials and sensitive information before posting.
+      render: shell

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/iflytek/community/blob/master/SECURITY.md
+    about: Follow the private reporting process instead of opening a public issue.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,32 @@
+name: Feature request
+description: Propose an improvement to Domux
+title: "[Feature]: "
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: Please describe the user problem before proposing a solution.
+  - type: textarea
+    id: problem
+    attributes:
+      label: User problem
+      description: What use case is difficult or impossible today?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: Describe the behavior and, if useful, a possible API or workflow.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: How are you handling this today?
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add examples, mockups, benchmarks, or related links.

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,32 @@
+name: Question
+description: Ask for help using or understanding Domux
+title: "[Question]: "
+labels: [question]
+body:
+  - type: markdown
+    attributes:
+      value: Please check the README, documentation, and existing issues first.
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: What are you trying to accomplish, and where are you blocked?
+    validations:
+      required: true
+  - type: textarea
+    id: attempted
+    attributes:
+      label: What have you tried?
+      description: Include relevant commands, configuration, or documentation.
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Domux version, operating system, Python version, and relevant dependencies.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Remove credentials and sensitive information before posting logs.