Adopt React Native 0.82 DOM Node APIs

[yaminyassin]

Summary

Bumps react-native peer dependency to >=0.82.0 and rewrites useStrictDOMElement to wrap the underlying RN host node in a thin Proxy instead of cloning it via Object.create / Object.defineProperties. React Native 0.82 ships the stable DOM Node APIs (DOM traversal, ownerDocument, getRootNode, children / childNodes, pointer-capture, etc.) that strict-dom helped drive into RN — adopting them as the substrate turns the native ref polyfill into a lightweight overlay.

Tracks discussion #462.

What's still polyfilled

The Proxy traps only the keys strict-dom still needs to control:

• nodeName → uppercase DOM name (RN exposes tagName as 'RN:View')
• getBoundingClientRect + length getters → divided by the active viewportScale
• <img>.complete → fallback to false when the underlying RN Image node doesn't expose it
• <input> / <textarea> setSelectionRange / selectionStart / selectionEnd → polyfilled on top of setSelection. Self-disables the day RN exposes the W3C selection API.

What now passes through to the RN node

ownerDocument, getRootNode, parentNode, parentElement, children, childNodes, sibling navigation, contains, compareDocumentPosition, setPointerCapture / hasPointerCapture / releasePointerCapture, and legacy measure / measureInWindow / measureLayout / setNativeProps. The Proxy forwards function values bound to the underlying target so internal this-references inside RN's implementations resolve correctly. [[GetPrototypeOf]] and Symbol reads forward by default — instanceof keeps working.

Identity caching via a WeakMap<Node, Proxy> is preserved so the same RN node always yields the same wrapped ref.

Breaking

Peer dep react-native >=0.79.5 → >=0.82.0. Apps on older RN must stay on the previous react-strict-dom release.

Bundle size impact

dist/native/index.js drops −363 bytes minified / −69 bytes brotli. Web build is byte-identical. Other bundles unchanged.

Perf benchmarks (css.create, css.createTheme) move within ±2% — noise. Those benchmarks don't exercise the ref path, so they confirm the unrelated style system didn't regress.

Notes for reviewers

• Expo SDK pairing. No Expo SDK targets exactly RN 0.82 (SDK 53 = RN 0.79, SDK 54 ≈ RN 0.81, SDK 55 = RN 0.83). The example apps land on SDK 55 / RN 0.83.6, which satisfies the new peer dep and ships the same DOM Node APIs.
• React devDeps. RN 0.82+ requires React >=19.1.1. The workspace root and library packages' devDependencies pin react / react-dom / react-test-renderer to ~19.2.0 to keep a single React instance across the monorepo.
• Flow type changes in RN 0.83. Animated.createAnimatedComponent is now a single-type-arg generic — fixed properly by dropping the over-specified two-type-arg form. ImageProps / TextInputProps became exact; the wide-spread of strict-dom's ReactNativeProps onto those hosts is covered with two targeted $FlowFixMe annotations. Properly narrowing the spread is a real follow-up.
• 10 new ref tests in tests/html/html-refs-test.native.js pin every Proxy behavior: nodeName uppercase, getBoundingClientRect pass-through and scaled, DOM Node API pass-through (ownerDocument / getRootNode / childNodes / children), strict-ref identity stability, and <img>.complete fallback / pass-through.

[yaminyassin]

Related follow-up: #477: switches strict-dom from the deep import react-native/Libraries/Text/TextAncestor to the public unstable_TextAncestorContext API exposed in facebook/react-native#52368. Logically depends on this PR (the bumped peer dep is what makes the public API guaranteed available). Once both land, the corresponding RN-side cleanup can delete the compatibility shim.