[AI Translation][zh-CN → en-US] Wire Qoder Cloud in as an "Employee" Inside Your Own System

[anchenqlw]

Cookbook contribution

Summary

• Content type: Best Practice
• Locale: en-US
• Demo source included: no (the existing Demo demos/integrate-qoder-cloud-runtime/ is shared by link only; no Demo files change in this pull request)
• Target audience: English-reading platform and backend engineers who want to embed a Qoder Cloud Agent into their own task-dispatch system and expose their business capabilities as custom tools.
• User problem and expected outcome: English readers had no version of this integration best practice. After this change they can understand the managed-sandbox boundary, the requires_action whole-batch tool protocol, SSE resume with Last-Event-ID, idempotency, token separation, and the honest limits of in-process exactly-once.

Sources and assets

• Public sources used: The repository source article content/zh-CN/best-practices/integrate-qoder-cloud-runtime/index.md at commit 9764c7aee25f00fc1dad2ddfb916911eefc4d75d. This target is an AI translation of that article; the prose is not fully original. No external sources were consulted and no assets were added.
• Asset owner and license: No new assets and no new Demo source. The translated prose derives from the existing in-repository article by 时之 (@yefengzi7) and stays under the repository CC BY 4.0 prose license. The linked Demo remains under Apache-2.0 and is unchanged.
• If fully original, state: All submitted text and assets are original. — Not applicable: this is an AI translation of an existing repository article.

Specialist review

• Product, code, architecture, security, or regulated-domain reviewer, when applicable: None assigned. Because the article covers allowlist enforcement, idempotency, and token separation, a maintainer with security and Qoder Cloud runtime expertise should confirm the translated wording does not weaken any of those claims.

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, so that item is satisfied as "not applicable". No Demo source is added or modified; the translation only reuses the existing Demo URL https://github.com/QoderAI/cloud-agents-cookbook/tree/main/demos/integrate-qoder-cloud-runtime, which belongs to the zh-CN owner article, as the Demo Contract requires for translations. The preview was reviewed from the local npm run preview output.

Maintainer Demo review

• Not applicable, or a Maintainer reviewed the Demo README and source manually.
• Not applicable, or the claimed result, cleanup, billable operations, permissions, and destructive side effects were reviewed.

Both items are Not applicable for this pull request: no files under demos/ change, so there is no new Demo source to review. The existing Demo was already reviewed with its owner article.

AI Translation

• Source path: content/zh-CN/best-practices/integrate-qoder-cloud-runtime/index.md
• Source commit SHA: 9764c7aee25f00fc1dad2ddfb916911eefc4d75d
• Direction: zh-CN → en-US
• Target path: content/en-US/best-practices/integrate-qoder-cloud-runtime-en/index.md
• Source slug: integrate-qoder-cloud-runtime
• Target slug: integrate-qoder-cloud-runtime-en
• Branch: automation/translate/integrate-qoder-cloud-runtime-en
• translation_of: integrate-qoder-cloud-runtime
• Validation results: scope check passed (only content/en-US/best-practices/integrate-qoder-cloud-runtime-en/ changed); git diff --check passed; npm run check passed (tests, validate 4 items 0 errors 0 warnings, validate:demos 2 Demos 0 errors, links, build, preview).

Only the title, summary, and reader-facing prose were translated. Type, category, tags, author, heading levels, code fences, Mermaid syntax, commands, URLs, Markdown link targets, and the Demo link were preserved. This language version was automatically translated by AI.