docs: refresh translations for recent English changes
Re-runs scripts/docs/translations.py translate for all twelve languages to catch up with English changes since the translations were first published in #3280.
Motivation and Context
Eighteen pages per language had sections whose English source changed (error handling, prompts, structured output, media, deprecated helpers, transports, troubleshooting, and a handful of one-line edits elsewhere), so translated sites were showing the "translation behind the English page" notice on those. The tool retranslated only the changed sections; everything else in each page is carried over byte for byte, which is why the diff is section-scoped despite touching 216 files.
Nothing under docs/, i18n/*/instructions.md, i18n/*/glossary.json or the tool itself changed.
How Has This Been Tested?
translations.py statusreports 0 missing / 0 outdated / 51 current for every language.scripts/docs/build.shbuilds the English site strictly and all twelve language sites with 0 warnings (no dead links or anchors).- An offline pass over every generated page checked that it is a fixed point under the tool's own structure re-imposition and validation, that sections with unchanged English are identical to what's on
main, and that no section came back untranslated, in the wrong script, truncated, or with prompt text leaked into it. - Each language's diff was read against the English source for missing or garbled content.
Breaking Changes
None.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed
Additional context
Generated pages are never hand-edited; if a reviewer spots a wording problem, the fix goes into that language's instructions.md/glossary.json and the page is re-run.