Docs: clarify repository roles and roadmap (#3203)

[qiulang]

Summary

• Clarify the canonical responsibilities, user entry points, and issue routing for FunASR, Fun-ASR, SenseVoice, and FunClip.
• Add matching English and Chinese repository-role documents with a directional Now / Next / Later roadmap.
• Link the new guidance from the top-level READMEs and contributing guide.

Closes #3203

Type of change

• Bug fix
• Documentation
• Example or demo
• Runtime or deployment
• Benchmark or evaluation
• Model/training change

Validation

• python -m compileall funasr examples tests
• Markdown tables and newly added links checked during review
• Runtime/deployment command tested

Runtime validation is not applicable because this PR changes documentation only.

User impact

Users can identify which repository owns toolkit and deployment questions versus model, checkpoint, or media-editing workflows. Contributors also get a single issue-routing reference and a roadmap whose live implementation status remains linked to the relevant issues and pull requests.

Notes for reviewers

The author has not directly used FunAudioLLM/SenseVoice or modelscope/FunClip. Their role descriptions were derived from the #3203 discussion and the existing community_growth_20k.md guidance, so maintainers of those repositories should verify the final wording before merge.

[gemini-code-assist]

Code Review

This pull request introduces documentation regarding repository roles, responsibility boundaries, user entry points, and issue routing across the four FunASR ecosystem repositories, including both English and Chinese versions, and updates the README files to link to these new documents. The review feedback suggests correcting the casing of "vLLM" and removing extra spaces in both the English and Chinese repository roles documents, as well as filling an empty table cell in the Chinese README for consistency.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[LauraGPT]

Thanks for taking this on. I checked the full diff against the #3203 scope, validated the Markdown tables, and verified all newly added relative and external links; the repository boundaries and canonical realtime-service direction are aligned with the issue discussion.

Please make this small final pass before merge:

1. Apply the three existing Gemini suggestions: normalize vLLM casing/spacing in both role documents and fill the empty second cell in the Chinese README row.
2. In both roadmap documents, avoid hard-coding 100 success, 2 skipped, 0 failure for Transformers #46180. That count and the approval state can change without this repository changing; use wording such as “in review; see the linked PR for current CI/review status.”
3. Localize the two remaining English-only labels in the Chinese document (Versioned release roadmap: pending maintainer confirmation and directional roadmap) so the Chinese entry point reads naturally.
4. Add Closes #3203 to the PR description and finish the incomplete User impact sentence.

No runtime test is needed for this docs-only change. Once those edits are pushed, I will re-check the exact head and complete the maintainer review.

[LauraGPT]

Re-checked head 821a0461. The three inline suggestions and the maintainer follow-ups are addressed: vLLM casing and spacing, the Chinese README table link and localized roadmap labels, and non-stale wording for the Transformers integration status. The PR body closes #3203 and the User impact section is complete. git diff --check, targeted content checks, table structure, and the new external link all pass.