i18n(ja): keep the literal information_schema identifier in table-page summaries

[yahonda]

What is changed, added or deleted? (Required)

Found while checking for information_schema mistranslations: 5 information-schema/*.md summary lines translate the literal, lowercase schema identifier information_schema (matching the USE information_schema; statement shown in each page's own example code block) as "情報スキーマ" instead of keeping it literal. The other 57 pages in the same directory already keep it correctly (e.g. COLUMNS` INFORMATION_SCHEMA テーブルについて学習します。), so these 5 were outliers.

Fixed:

• information-schema/information-schema-analyze-status.md
• information-schema/information-schema-resource-groups.md
• information-schema/information-schema-placement-policies.md
• information-schema/information-schema-tidb-hot-regions-history.md
• information-schema/information-schema-tikv-region-status.md

Note: the general translation "情報スキーマ" for the Information Schema feature/concept name (e.g. information-schema/information-schema.md's own H1) is correct and separate from this — only the literal lowercase information_schema identifier in these 5 summaries was wrong. A separate, much larger pre-existing issue (a missing opening backtick before the table name in ~58 of the 62 summary lines in this directory) was found in the same pass and is intentionally left out of this PR per the user's request to handle it separately.

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): found while reviewing i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-08-27 #23616

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

Summary by CodeRabbit

• Documentation
  • Updated Japanese page summaries to consistently use the information_schema table name for several Information Schema references.
  • Improved terminology consistency across documentation for ANALYZE_STATUS, PLACEMENT_POLICIES, RESOURCE_GROUPS, TIDB_HOT_REGIONS_HISTORY, and TIKV_REGION_STATUS.

[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 hfxsd 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ca68d151-a0d6-4992-8c13-93f68b441374

📥 Commits

Reviewing files that changed from the base of the PR and between d41688a and dab5ae5.

📒 Files selected for processing (5)

• information-schema/information-schema-analyze-status.md
• information-schema/information-schema-placement-policies.md
• information-schema/information-schema-resource-groups.md
• information-schema/information-schema-tidb-hot-regions-history.md
• information-schema/information-schema-tikv-region-status.md

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

---

📝 Walkthrough

Walkthrough

Five information schema documentation summaries replace the Japanese term 「情報スキーマテーブル」 with 「information_schemaテーブル」. No public declarations or functional behavior changed.

Changes

Information Schema Documentation

Layer / File(s)	Summary
Update information schema summary terminology information-schema/information-schema-*.md	Five frontmatter summaries now use information_schemaテーブル to describe the documented tables.

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

Merge Risk: ⚪ Minimal · up to dab5a

This documentation-only change corrects five Japanese summaries to preserve the literal information_schema identifier. It is localized and introduces no actionable merge-blocking risk beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly identifies the Japanese localization change and the preservation of the literal information_schema identifier in table-page summaries.
Description check	✅ Passed	The description explains the five affected files, the reason for the corrections, the applicable documentation version, related review context, AI involvement, and intentionally excluded scope. Requir…

Full details: Docstring Coverage

Explanation

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 files. (5 skipped: 5 unsupported.)

Full details: Description check

Explanation

The description explains the five affected files, the reason for the corrections, the applicable documentation version, related review context, AI involvement, and intentionally excluded scope. Required sections are present and sufficiently complete.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-information-schema-literal-identifier

---

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.}