i18n(ja): restore lost code fences (batch 1, 135 files)

[yahonda]

What is changed, added or deleted? (Required)

First batch of a corpus-wide sweep fixing a structural MT regression: many config/log/command/output examples in Japanese translations lost their triple-backtick code fences entirely, degrading to plain (sometimes still-indented) text with no syntax highlighting or copy-button UI. The example content itself was untouched — only the fence markers were missing.

This PR (135 files) restores the fences to match the English source exactly:

• Fence markers (plain or taggedyaml/sql/shell/```json) added back at the correct position and indentation.
• Body content re-indented where it had accumulated stray leading whitespace from the old workaround (Markdown's "4-space indented code block" convention, used as a substitute once the real fence was lost) — every file's fence count and per-line indentation now matches the English source exactly.
• No translated prose, headings, or any other content was touched.

Verified mechanically for every file in this PR: (1) the count of occurrences matches the English source exactly, and (2) for every matched code block, per-line leading-whitespace matches the English source exactly, including code fences nested inside blockquotes (`> ... > ``` ), which need their own check since a naive leading-whitespace comparison does not catch indentation drift after a > ` marker.

An earlier round of independent review found and fixed two defect classes the initial automated verification missed: (1) one file where a pre-existing fence-indentation quirk broke the verification script's block-parser and caused the whole file to be silently skipped, leaving ~26 blocks with stale indentation; (2) two files with the blockquote-nested-fence blind spot described above. Both are now fixed and covered by the verification method for all files in this PR.

This is the first of several planned batches — a larger candidate list (~216 more files) remains and will follow in subsequent PRs (see #23506 for batch 2). See the tracking note for full scope and method.

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)

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

• This PR is translated from:
• Other reference link(s): i18n(ja): restore lost code fences (batch 2, 37 files) #23506 (batch 2 of the same sweep)

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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 460a6776-18f1-40e8-9da4-1fc7c2513813

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[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 lilin90 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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-12 08:58:57.696711539 +0000 UTC m=+3209723.732806616: ☑️ agreed by qiancai.