[AI Translation][zh-CN → en-US] Bulk-Upgrade a Heterogeneous Codebase: Migration, Testing, and Repair with the QCA Batch Agent

[anchenqlw]

Cookbook contribution

Summary

• Content type: Workshop
• Locale: en-US
• Demo source included: no (an existing Demo is shared by link only; no files under demos/ change in this pull request)
• Target audience: Engineers and tech leads who must upgrade an SDK dependency across several heterogeneous services and want unattended Agent batches to produce test-verified patches.
• User problem and expected outcome: English-speaking readers cannot follow the zh-CN batch migration workshop. This adds the en-US language version of that workshop so readers can prepare an isolated Forward Environment, submit four migration tasks as a Batch, track each task by custom_id, resubmit only failed lines, and accept results with tests, patches, and reports.

Sources and assets

• Public sources used: the existing repository source article content/zh-CN/workshops/batch-sdk-migration-with-qca/index.md (slug batch-sdk-migration-with-qca, source commit 950c5d43d75cd8e328e3f0a0ab5ee06a67754a3f), plus the public Qoder Cloud Agents API documentation links already cited in that article.
• Asset owner and license: no new assets. No images or Demo files are added; prose follows the repository CC BY 4.0 scope.
• If fully original, state: All submitted text and assets are original. — Not applicable. This target article is an AI translation of the existing zh-CN article listed above; the prose is a derived translation, not fully original content. Metadata (type, category, tags, author), code, commands, endpoints, environment variables, URLs, and the Demo link are preserved from the source.

Specialist review

• Product, code, architecture, security, or regulated-domain reviewer, when applicable: none nominated by this automation. A maintainer with QCA Batch and English-language expertise should confirm terminology and that no technical claim shifted during translation.

Author checklist

• I used exactly one author and no more than five approved tags.
• The article has at least three ## sections and no hand-written table of contents.
• I did not use GitHub Alerts, video, raw HTML, JavaScript, MDX, iframe, remote images, SVG, or interactive content.
• Images are local PNG, JPEG, or WebP files with meaningful alternative text and documented rights.
• The contribution contains no credentials, customer data, personal information, internal links, or unreleased capabilities.
• If a Demo is included, demos/<slug>/ matches the owner article, and the article contains the exact GitHub Demo link.
• If a Demo is included, its README documents prerequisites, setup, run, verification, cleanup, and cost/safety considerations.
• Demo configuration uses placeholders; no dependency cache, build output, binary, archive, nested Git metadata, or symbolic link is included.
• I disclosed the origin and license of Demo source, dependencies, fixtures, and third-party assets.
• I reviewed the generated preview locally or from the required GitHub Actions checks.
• Every commit contains a Signed-off-by trailer.
• I understand that maintainer Merge to main is the publication event.

Notes on the checklist: this pull request adds no images and no Demo files. The image, Demo binding, and Demo README items are satisfied as not applicable — the translated article only links the existing demos/batch-sdk-migration-with-qca Demo owned by the zh-CN article, as required by the Demo Contract rule that translations share one Demo instead of copying it. The preview item was verified through a local npm run check run, which includes catalog and preview generation.

Maintainer Demo review

• Not applicable, or a Maintainer reviewed the Demo README and source manually. — Left unchecked: only a maintainer can confirm this, and this automation cannot perform maintainer review.
• Not applicable, or the claimed result, cleanup, billable operations, permissions, and destructive side effects were reviewed. — Left unchecked for the same reason. No Demo file changes, so review scope is limited to the translated prose that describes the existing Demo.

AI Translation

• Source path: content/zh-CN/workshops/batch-sdk-migration-with-qca/index.md
• Source commit SHA: 950c5d43d75cd8e328e3f0a0ab5ee06a67754a3f
• Direction: zh-CN → en-US
• Target path: content/en-US/workshops/batch-sdk-migration-with-qca-en/index.md
• Source slug: batch-sdk-migration-with-qca
• Target slug: batch-sdk-migration-with-qca-en
• Branch: automation/translate/batch-sdk-migration-with-qca-en
• translation_of: batch-sdk-migration-with-qca
• Validation results: git diff --check clean; npm ci --ignore-scripts succeeded; npm run check passed (8 content items with 0 errors and 0 warnings, 3 Demos with 0 errors, all relative links resolve, catalog and preview built). Only the target translation directory changed.
• Machine translation disclosure: the body carries the required notice > This language version was automatically translated by AI. immediately after Frontmatter.