Electron Releases

Description of Change

webContents.send() went through the mainFrame accessor (a full binding call that looks up/creates the WebFrameMain wrapper) and then a second binding call to _send. Resolve the primary main frame in C++ so a send crosses the boundary once. Channel validation and error handling move to the webContents wrapper unchanged: a destroyed contents / missing frame still throws a TypeError, a serialization failure is still logged.

Roughly 250 ns off each send on a testing build; the rest of a send is serialization and mojo.

Checklist

• I have built and tested this change
• I have filled out the PR description
• I have reviewed and verified the changes
• npm test passes

Release Notes

Notes: none