Add R3L to readme and doc

[yanxi-chen]

Description

As the title says.

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @yanxi-chen, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the project's documentation to formally introduce R3L, a new reflect-then-retry Reinforcement Learning mechanism. The changes ensure that both English and Chinese-speaking users are informed about this development, providing clear links to its repository and associated research paper within the main README files and the Sphinx documentation. This enhances the discoverability and accessibility of the R3L project within the Trinity-RFT ecosystem.

Highlights

• R3L Integration in READMEs: Added a news entry for R3L (reflect-then-retry RL) to both the English and Chinese README.md files, providing links to its GitHub repository and research paper.
• R3L in Documentation: Integrated R3L into the 'Algorithm development' section across both English and Chinese README.md and Sphinx documentation files (docs/sphinx_doc/source/main.md, docs/sphinx_doc/source_zh/main.md), ensuring its visibility and accessibility.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds information about R3L to the README files (both English and Chinese versions) and the corresponding Sphinx documentation. The changes include adding a news item and an entry in the algorithm development table. The updates are clear and consistent across the files. I've suggested a minor punctuation fix for consistency in the Chinese README.

[gemini-code-assist]

For consistency with other list items in this section, please use the Chinese period (。) at the end of the sentence. The current full-width period (.) is inconsistent with the punctuation used elsewhere in this list.

Suggested change

	* [2026-01] 推出 [R3L](https://github.com/shiweijiezero/R3L)：基于反思-重试的强化学习机制，由自然语言反馈引导高效探索，并达成稳定的 off-policy 学习（[论文](https://arxiv.org/abs/2601.03715)）.
	* [2026-01] 推出 [R3L](https://github.com/shiweijiezero/R3L)：基于反思-重试的强化学习机制，由自然语言反馈引导高效探索，并达成稳定的 off-policy 学习（[论文](https://arxiv.org/abs/2601.03715)）。