fix(core): stop routing every createElement call through the host's factory

[Fiona2016]

Fixes a regression introduced in 0.1.4. On an app using a css-interop based styling library (nativewind), 0.1.4 with trackInteractions: true crashes at startup — Hermes GCBase::oom, heap growing without bound.

⚠️ Do not merge on the strength of the reasoning below. The mechanism was misdiagnosed twice before landing on this, and the only thing that can confirm it is a release build on a device. See Verification still owed.

The defect

These two lines were not talking about the same property:

const originalCreateElement = React.createElement;      // member expression
replaceProperty(reactModule, 'createElement', wrapper); // computed access

react-native-css-interop ships a Babel plugin that rewrites React.createElement to ReactNativeCSSInterop.createInteropElement in every file except react's and its own — the SDK's files included. Compiling the SDK's published lib/ with such an app's Babel config shows exactly that:

var originalCreateElement = _ReactNativeCSSInterop.createInteropElement;   // read: rewritten
replaceProperty(reactModule, 'createElement', function(){...})             // write: untouched

So the SDK saved the host's wrapper and replaced React's own factory with something that calls it. From then on every createElement call in the process — React's internals included — went through the host's wrapper, which is input it was never written to receive.

The same mismatch applied to the value stopTracking restores from, so uninstalling made it worse rather than better.

Why 0.1.3 did not crash

In 0.1.3 both sides were member expressions, so both were rewritten together: the assignment hit a getter-only property and threw, and the factory was never actually replaced. 0.1.4 changed the write to a computed access to remove that exception — and in doing so replaced the factory for the first time, with a mismatched original. The exception it removed was load-bearing.

The fix

Both sides now read through the module object with a computed access, which no plugin of that kind can rewrite. Verified by recompiling the built SDK with such an app's Babel config: createInteropElement no longer appears anywhere in the output.

This branch also keeps a second, independent change: an accessor is left alone rather than redefined, because a host that puts a getter in that slot is managing it. That one was written for the same crash and does not explain it — on this path React.createElement is a plain writable property — but it is correct on its own terms and is covered by tests.

Verification still owed

Repo-side gates pass: 883 tests, lerna run prepare across all 9 projects, lint clean, and the compiled-output check above. None of that exercises the crash. Before this ships, a release build with trackInteractions: true on an app using nativewind needs to start cleanly and record actions, with the pre-fix build as the negative control.