v8.5.6: dm experimentally supports foreign key

[Oreoxmt]

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)

• Update four docs pages to document DM's experimental foreign key support shipping in v8.5.6
• Covers three engineering PRs: tiflow#12351 (safe mode FK), tiflow#12414 (multi-worker causality), tiflow#12329 (DDL whitelist)
• All behaviors validated against a live build (v8.5.5-12-gd6d53adbe) with 13 test scenarios, all passing

File	Change
dm/dm-safe-mode.md	Add "Foreign key handling (experimental)" section: non-key UPDATE optimization, session-level FK_CHECKS toggle, multi-worker causality. Add forward-reference from Working principle.
dm/dm-compatibility-catalog.md	Rename "Incompatibility with FK CASCADE" to "FK CASCADE operations". Add experimental support with validated constraints (PK/UK guardrail, DDL rejection, routing, BAL ancestor, ON UPDATE CASCADE mismatch).
dm/dm-precheck.md	Update FK warning: TiDB supports FKs (GA since v8.5.0), DM experimental since v8.5.6.
foreign-key.md	Replace "DM does not support foreign keys" with experimental v8.5.6 support, warning, and backward-compat note.

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: v8.5.6: dm experimentally supports foreign key docs#22616
• 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

[Oreoxmt]

/hold

[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 ask for approval from oreoxmt. 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

[Oreoxmt]

/cc @qiancai

[qiancai]

Rest LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-04-10 05:03:35.533473827 +0000 UTC m=+1105420.738833874: ☑️ agreed by qiancai.