i18n(ja): restore particles dropped after code spans and links

[yahonda]

What is changed, added or deleted? (Required)

The old MT pipeline dropped the particle between a code span (or link) and the verb that governs it. The correct particle depends on grammatical voice, so every site was read against the English source rather than pattern-replaced:

EN: See [Manual collection](/x.md) for details.     -> [手動収集](/x.md)を参照してください
EN: `200 OK` is returned.                           -> `200 OK`が返されます      (passive: が, not を)
EN: You can safely use `KILL`.                      -> `KILL`を使用できます
EN: If no `project_id` is specified                 -> `project_id`が指定されていない

433 lines across 212 files. Particle distribution:

particle	count	when
を	319	active / transitive
が	139	passive され forms, and potentials whose subject is the code span
は	20	code span is the sentence topic
に	7	code span is a location or complement — e.g. "INFORMATION_SCHEMA.CLUSTER_HARDWARE might contain …" -> に…含まれている
の / で / も	6	genitive; agent of a passive ("the name that -n/--name specifies" -> で); correlative ("neither <version> nor --all" -> も)

28% of the sites are not を. A mechanical を insertion would have been wrong on those 112 lines — which is why #23272 deliberately excluded passive forms and left them for a pass like this one.

How it was checked

• Every changed line differs from the original by inserted characters only — zero deletions, so every code span, link URL, list marker, table pipe and indentation is byte-identical. (13 lines also carry a sibling PR's fix, see below.)
• Link targets: 0 added, removed or altered. Code-span multiset per line: unchanged.
• No doubled particle (をを/はは/がが/にに/でで/をが/がを) introduced.
• No line-ending (CRLF/LF) changes.

Not fixed

About a dozen flagged sites are damaged beyond a missing particle — the pipeline transposed or duplicated code spans, so no particle is correct. Examples: optimizer-hints.md (ヒントを already holds the accusative, so QB_NAME has no valid slot), br/br-checkpoint-restore.md (the br span is duplicated, giving two subjects), partition-pruning.md (the operator list is torn apart). These need rewording, not particle restoration, and are left for a follow-up.

Relationship to the sibling PRs

These fixes were developed on top of the other open ja PRs and then harmonized with them, so all thirteen merge cleanly in any order (verified: 78 pairwise merges, 0 conflicts). Where a line is shared or adjacent, every branch carries the same final text — which is why 13 lines here also contain a sibling PR's fix (a stray digit removed, a stranded }} dropped).

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

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 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)
• v5.3 (TiDB 5.3 versions)

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

• This PR is translated from: N/A (Japanese-only accuracy fix)
• Other reference link(s): sibling ja PRs i18n(ja): add missing object-marker particle (wo) before code-span transitive verbs #23272 i18n(ja): add missing particle after Markdown links (wo before verbs, wa for subject) #23273 i18n(ja): miscellaneous review fixes (bit-shift description) #23274 i18n(ja): remove stray digits inserted before code spans #23275 i18n(ja): standardize the "Data Service" product name (データサービス → Data Service) #23291 i18n(ja): restore admonition labels to English (Note/Warning/Tip) #23292 i18n(ja): fix trailing "page number" typo after page reference links #23294 i18n(ja): restore variable names and clean up heading anchors in system variable docs #23295 i18n(ja): unify "plan cache" katakana term (remove stray space) in sql-prepared-plan-cache.md #23297 i18n(ja): fix partial negations rendered as full negations #23311 i18n(ja): restore text dropped by the translation pipeline #23315 i18n(ja): restore text dropped by the translation pipeline (part 2) #23316

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

Draft detected.

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

Run ID: 6daea668-f2e6-454b-913a-250a0ccffcc9

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

✨ Finishing Touches

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

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