[ Proof ]
react-native-nitro-network-info
unchanged package JavaScript runs over the installed provider, whose Swift (HybridNitroNetworkInfo on NWPathMonitor) is compiled to wasm by the Nitro source path and answers every call; no seam or stub stands in for it. Behavior was observed against the Swift source rules, not captured from a native simulator.50%
API coverageWorking
isConnected and connectionType reads (false/unknown before the monitor starts, then the host path state), addListener with an asynchronous initial callback followed by the path update, payload shape, unsubscribe, resubscribe with retained state, and a replacing listener
Missing (2)
the headless host publishes no interface type so connectionType stays unknown and wificellular and ethernet are never produced; offline and online transitions were not driven; no native simulator capture