[ Proof ]
react-native-nitro-fs
unchanged package JavaScript runs over its own HybridNitroFS Swift (FileManager), compiled to wasm by the Nitro source path; no seam or stub answers NitroFS. An unmodified install does not currently compile: the package depends on react-native-safe-area-context, and the Turbo build fails on its missing safeareacontext codegen headers. The observed behavior used a setup with that installed dependency removed. Behavior was observed against the Swift source rules, not captured from a native simulator.60%
API coverageWorking
DOCUMENT_DIR, CACHE_DIR and BUNDLE_DIR; exists, mkdir, writeFile and readFile in utf8, ascii and base64, overwrite, stat, file:// paths, copyFile, copy of a directory tree, rename, unlink of a file and a tree, dirname, basename, extname, and the package error messages for missing, wrong-kind and invalid inputs
Missing
readdir on an existing directory traps in the Swift SDK (URLResourceValues.contentType is not implemented) and ends the Swift process; readdir of a regular file returns an empty list where Apple Foundation is expected to throw; uploadFile and downloadFile were not run; no native simulator capture