Parent: #790. Related: #786, #791.
The environment-declaration integration run exposed a real identity bug: currentGlobalObject resolves the writable globalThis binding instead of the canonical global object. The existing low-level test vm: sloppy recursive calls retain their function realm global fails when exact variable Reference plans replace forced global definitions.
Simply preferring Interpreter.global_object is insufficient: an ambient native call can still belong to the caller while a foreign generator executes in its own closure environment. The existing dynamic generator functions validate params and prototype realms test caught this with ReferenceError on the foreign calls binding.
Implement stable per-realm ownership on the root environment, initialized before publication and traced/relocated as an owned managed edge. Resolve function and global binding realm identity through that environment, including dynamic constructors, indirect eval, evalScript and ShadowRealm entry. Neither writable nor lexically shadowed globalThis can select a realm. Do not modify Promise/job lifecycle or use ambient-global special cases for individual tests.
Acceptance: reassigned and shadowed globalThis, foreign dynamic generator/async-generator construction, child realm evalScript, precise edge relocation, no-GIL/TSan and full integration. The initial ambient-only candidate is not landable.
Completed integration
CI run 33113309062 completed successfully on main commit 8a1398ffc04e9e30987f968693667c7271ca3ce1, a descendant containing this implementation. All 53 executed jobs succeeded (unit and TSan-unit shards, Linux no-GIL TSan, functional/no-GIL corpus gates, fuzz profiles, ABI, Wasm, Test262 parallel, and docs); the scheduled-only nightly job was skipped. Together with the measured local evidence in the comments, this completes this issue's acceptance.