Do not double-proxy methods being return over the contextBridge

Editor assessment

The intent, avoiding double-proxying of methods returned across the contextBridge for performance, is recoverable, but the subject's broken grammar (being return over) makes the reader work for it. The perf type is well chosen and matches the optimization nature of the change. No scope identifies the context-bridge area, no body explains the overhead being removed or how it was measured, and no footers appear. Hygiene is the main flaw: the mangled participle reads as unedited. Understandable in the end, but the sloppy wording and absent rationale keep this at acceptable rather than publishable.