# Contribution Guidelines

Thank you for your interest in this project! We welcome any suggestions and contributions regarding code, documentation, testing, or design. The following instructions are intended to make the participation process clear, simple, and traceable.

## Overview

This project is a collaborative effort. All changes are reviewed and merged into the `main` branch through GitHub **Pull Requests (PRs)**. Before submitting, please ensure your modifications have been tested locally and are clearly described.

## How to Contribute (Quick Flow)

1. **Fork** this project on GitHub.
2. **Implement** your changes directly in your fork and include necessary tests or documentation updates.
3. **Run** the project locally to verify all tests pass.
4. **Open a Pull Request**, clearly explaining the changes, your motivation, and how you tested the code in the PR description.

*Tip: Keeping a single PR focused on one specific task makes it easier to review and merge.*

## Issues (Bug Reports & Suggestions)

To report a bug or start a discussion, please create an **Issue** on GitHub. We recommend providing the following:

- **Title**: A concise summary of the problem.
- **Background**: Context or use cases where the issue occurs.
- **Reproduction Steps**: Minimal steps or code snippets to reproduce the issue.
- **Expected vs. Actual Behavior**: A description of the discrepancy.
- **Environment Info**: Version, OS, input data, and any relevant error messages.

Detailed yet concise reports help accelerate the resolution process.

## Code Style and Testing

Please adhere to the project's existing coding styles and naming conventions. If you introduce third-party packages or perform significant refactoring, please explain the reasoning and any alternatives considered in your PR.

## License

By contributing, you agree that your contributions will be licensed under the project's **Apache License 2.0**. For more details, please refer to the `LICENSE` file in the root directory. If you have questions regarding licensing, please contact the maintainers beforehand.