Use the relevant repository's issue tracker for reproducible bugs and scoped feature proposals. Use discussions when a repository enables them for open-ended questions and design exploration.
If a problem spans multiple capabilities, describe the complete research workflow, the last verified step, the observed failure, affected inputs and outputs, and any provenance or permission constraints. Report it to the repository that owns the failing interface. If ownership is unclear or no relevant repository is public, contact the organization rather than duplicating the same issue across projects.
For organization-level research collaboration, institutional partnerships, or questions that do not belong to a specific repository, contact liuzaoqu@163.com.
Do not use public support channels for vulnerabilities, credentials, personal data, patient data, unpublished restricted research, or other sensitive material. Follow SECURITY.md for security reports.