[ Proof ]
react-native-nitro-markdown
unchanged package JavaScript runs over the installed provider, whose C++ (HybridMarkdownParser, HybridMarkdownSession and md4c) is compiled to wasm by the Nitro source path; no seam or stub answers MarkdownParser or MarkdownSession. The Markdown component is the package's own React Native Text and View tree. Behavior was observed against the package's documented results, not captured from a native simulator.80%
API coverageWorking
a 0.16.1 app renders the Markdown component and gets the expected parseMarkdown AST with source offsets (heading, bold, italic, strikethrough, inline code, link, task list, table), extractPlainText, parseMarkdownWithOptions gfm off, math, sourceOffsets off and freezeAst, the maxInputLength error, and sessions: append, getLength, getTextRange, replace, getAllText, addListener ranges, parseMarkdownSession AST, invalid_range and destroyed-session errors
Missing (4)
session clearreset and highlightPositionextractPlainTextWithOptionssurrogate-pair range errors and the MarkdownStream and useMarkdownSession streaming helpers were not exercised; rendered output is not pixel-compared with iOS