[anycodes]

Description

The environment guide sends default Express users to an invalid create flag, treats terminal-only env overrides as instance-lifetime injection and omits explicit application credentials in HTTP examples. The two translations now use actual asynchronous ProviderSandbox ownership/cleanup, ordinary process-environment inheritance and authenticated application_client system.env/set_env calls. Interpreter/network APIs and exec initialize remain real interfaces with their actual scope. Historical comparison tables are unchanged.

Fixes #135

Type of Change

• Documentation

Changes

• Remove the independent-process-tree diagram, universal PATH inheritance promise and misleading CLI lifetime-env example.
• Keep Express create --env explicitly terminal-only; document per-process env and current provider interpreter prerequisites.
• Use authenticated application binding, policy prerequisites and existing typed environment methods; document startup-cached settings accurately.
• Add bilingual changelog and owner note/evidence, preserving the first pre-ready local HTTP failure separately from a later real local HTTP pass.

Testing

• Public client/server0.4.0a6 actual imports and API signatures: PASS.
• Both guides: ten Python fragments each compile; relative targets and whitespace checks pass.
• Real local server HTTP: typed env get/set/readback, secret-name filtering, wrong-token rejection, unchanged parent environment and owned-process independent absence: PASS. Only health probes retried two pre-ready protocol resets within the original10s budget; no post-ready API retry.
• Repository health:106PASS/1existingWARN/0FAIL; hygiene and staged secret scan pass.
• Full local make-ci not run because dev tools are absent and this scoped task installs no new dependencies. Full normal SDK PR matrix remains required.

Definition of Done

• ADR/note and evidence recorded; docs updated in English and Chinese; CHANGELOG updated.
• No runtime, docstring, dependency, package-version or historical command-map change.
• No sensitive information included; no new cloud resource created.
• Latest full SDK CI and normal final review/merge.

The published SDK remains0.4.0a6. Local HTTP/component proof is not represented as a cloud lifecycle or all-provider environment guarantee. Existing platform observations stay in the template owner's evidence; this prose fix creates no new runtime mode or package publication.