i18n(ja): unify semantic search notation in Japanese docs

[yahonda]

What is changed, added or deleted? (Required)

The EN source consistently uses plain lowercase "semantic search" (no
special casing or alternate phrasing) at all 14 sites across these 10
files, so this is a pure notation split with no EN-driven justification
for variance. Unifies to セマンティック検索, matching the corpus-wide
majority (29 sites vs 16 before this fix).

Heading anchors (English-derived) left unchanged.

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

• i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

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

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Standardized Japanese terminology for “semantic search” across AI, vector search, and release documentation.
  • Updated related image alt text and captions for consistency.
  • Reformatted a release-notes comparison table without changing its content.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign csuzhangxc for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: f32f4227-a2b4-4e99-bf22-557b6e40f668

📥 Commits

Reviewing files that changed from the base of the PR and between 3fc0051 and f83c486.

📒 Files selected for processing (5)

• ai/integrations/embedding-openai-compatible.md
• ai/integrations/vector-search-integrate-with-langchain.md
• ai/vector-search-get-started-using-python.md
• releases/release-8.4.0.md
• releases/release-8.5.0.md

Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.

---

📝 Walkthrough

Walkthrough

The Japanese AI documentation and release notes replace 「意味検索」 with 「セマンティック検索」. One release-notes table was reformatted without content changes.

Changes

Japanese terminology consistency

Layer / File(s)	Summary
AI documentation terminology ai/examples/vector-search-with-pytidb.md, ai/integrations/*.md, ai/quickstart-via-python.md, ai/vector-search-get-started-using-python.md	Updated vector search descriptions, captions, examples, and headings to use 「セマンティック検索」.
Release notes terminology and formatting releases/release-8.4.0.md, releases/release-8.5.0.md	Updated two 8.4.0 terminology references. Reformatted the 8.5.0 highlights table without changing its content.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: qiancai

Merge Risk: ⚪ Minimal · up to f83c4

This documentation-only terminology update does not introduce an actionable product or operational risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: unifying Japanese terminology for semantic search.
Description check	✅ Passed	The description explains the terminology changes, affected scope, version, AI involvement, and applicable change categories. It is sufficiently complete, although the version checkbox uses the reposit…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}