Patch Changes
- Model the engine's real
ContextProxyrouting: each thread now owns its owngetCoreContext()/getJSContext()proxy pair, and an event whose target equals the dispatching proxy's origin is delivered locally instead of crossing threads (matchingcontext_proxy.cc). Previously both contexts shared one event bus, so wrong-direction dispatches (e.g.lynx.getCoreContext().dispatchEvent(...)from the main thread) still reached the other thread in tests while silently failing on real devices. (#3351)