Preserve Executable Identifiers Across Localization

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Translation-only release-check has parsed name, invocation $release-check and reference references/checklist.md. Chinese prose is allowed; translated keys/paths break consumers.

Mechanism

Inventory machine IDs/schema keys/paths/invocations/literals, then translate surrounding narrative. Compare parsed identities/references/types/targets/tools. Localize display titles without replacing machine name. Authorized renames require explicit migration, separate from translation. Validate syntax and runtime loading independently.

Bad example

Translate name key/ID/path without moving files and call readable prose complete.

Good example

Translate description values/body while preserving name: release-check, invocation/reference and YAML keys. Compare parsed identity/resolution and test actual loading or mark untested; syntax success is not activation.

Why the change matters

Human labels and machine symbols serve different roles. Literal inventories preserve discovery/references while permitting natural explanations within authority.

Observable expectation

Teaching names/references stay and narrative becomes Chinese. Translated schema keys fail checks and changed paths expose missing targets. Generic technical terms need not all stay English.

Limits

Protect actual resolved symbols, not all vocabulary. Verify host frontmatter rules; authorized renames can migrate explicitly. Frozen language conventions are not universal localization requirements.