new nav: move AI related docs to an independent doc set

[qiancai]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Moved all vector search documentation files from develop/vector-search/ to ai/. All internal and TOC references have been updated accordingly. This change centralizes AI and vector search documentation, simplifies navigation, and ensures consistency across documentation links.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[gemini-code-assist]

Summary of Changes

Hello @qiancai, 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 a significant refactoring of the documentation structure for TiDB's vector search features. The primary goal is to centralize all AI and vector search-related content under a new ai/ directory, enhancing discoverability and maintaining consistency across documentation links. This reorganization simplifies the navigation experience for users seeking information on vector search, auto embedding, integrations, and performance improvements.

Highlights

• Documentation Reorganization: All vector search documentation files have been moved from the develop/vector-search/ directory to a new, centralized ai/ directory.
• Internal Link Updates: All internal references and Table of Contents (TOC) entries across the documentation have been updated to reflect the new ai/ path, ensuring consistency and correct navigation.
• Centralized AI Documentation: This change centralizes AI and vector search documentation, simplifying navigation and improving the overall user experience for finding relevant information.
• New Entry Point for Vector Search: A new develop/dev-guide-vector-search.md file has been added to serve as a consolidated entry point for vector search documentation within the develop section, linking to the newly organized ai/ content.

🧠 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 refactors the vector search documentation by moving all related files from the develop/vector-search/ directory to a new ai/ directory. This change centralizes the AI and vector search documentation, which should improve navigation and consistency. The changes are extensive and mostly involve file moves and link updates across many files.

I've reviewed the changes and they appear to be correct and consistent with the goal of the PR. I've added a couple of minor suggestions on the new develop/dev-guide-vector-search.md and TOC-ai.md files to align them better with the repository's documentation style guide. Overall, this is a good refactoring that improves the documentation structure.

[qiancai]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [qiancai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment