feat(ui): native-text BibleReader body and footnotes (POC)

[Dustin-Kelley]

Summary

A proof of concept that the BibleReader scripture body and footnote sheets can render with React Native <Text> instead of Expo DOM WebViews, at visual parity with the Swift and Kotlin SDKs. No native modules.

https://www.loom.com/share/5ad15c233898465ca30c2968902905da

Native reader (POC, opt-in)

• BibleReaderNative takes the same props as the DOM reader body and swaps in through the impl registry. unstable_setReaderRenderer('dom' | 'native') picks one; DOM stays the default.
• Parsing reuses platform-core's transformBibleHtml under linkedom, flattened into blocks of verse-tagged runs (packages/ui/src/native/scripture/).
• Styling follows the Swift and Kotlin readers: block rules, line spacing on Swift's model (natural line 1.24em + the step's fraction), verse labels, small caps, and words-of-Jesus colour.
• Layout uses the style spec's 32pt horizontal gutter and Swift's 16pt top padding.
• Small caps are synthesized at 0.85× with 0.055em tracking. On TOJB Luke 23 they measure the same width as Swift's lowercaseSmallCaps() and are within 1px of its height.
• Text direction comes from a majority vote of the passage's letters, with headings left out. A rule based on the first letter flipped ASV Psalm 119 to right-to-left, because its acrostic lines open with Hebrew.
• Load errors: 403 and 404 read as "unavailable in this version". Any other failed response, or a body that won't parse, shows the generic request error with Retry. A rejected fetch shows offline.
• The selection underline is a 1pt strip clipped from a hidden copy of the paragraph, placed off onTextLayout line metrics. RN has no underline offset, and iOS breaks text underlines at descenders.
• Highlights are drawn the same way, clipped per line to the text width and to Swift's band height, so line spacing shows as a gap between lines.
• No chapter header above the text; as in Swift, the reference shows only in the toolbar.
• The example Bible tab has a DOM / Native toggle.

Native footnote content (YPE-5832, changeset included)

• FootnoteContent renders with native text in both reader modes. It keeps italic notes, bold locators and verse superscripts, sized to match the web sheet.

Tooling

• pnpm dev:ios falls back to DeviceHub when Xcode has no Simulator.app (Xcode 27).

Cleanup

• Removed the example app's first native-text prototype tab and the dependencies only it used.

Not yet covered

• The highlight band uses em constants measured off the serif, so sans, fallback and non-Latin fonts may sit slightly off.
• A BSB continuation line attaches to the previous verse, and verse focus centres the paragraph rather than the verse.
• Prose sometimes wraps one word earlier than Swift. This is deliberate: the spec's 32pt gutter is 2pt wider each side than Swift's 30pt.
• Indented poetry lines (q2) wrap later than Swift, which breaks them before the line is full. This predates this branch's fixes and is untraced.
• Toolbar pills truncate earlier than Swift ("Song of…", "TOJB2…").
• The generic error copy is English-only until platform-localization ships the other locales.
• NIV is unlicensed for the example key, so 25 USFM classes were checked against Swift's styles in code rather than on screen.
• Not yet compared side by side for the pickers, or for highlights painted after sign-in.

Test plan

• pnpm lint, the UI package tsc, and UI Jest (952 passed)
• iOS simulator: John 1 checked against the Swift reader for underline, highlights and header
• Android device or emulator pass
• Scripture-class audit: 15 passages across BSB, ASV, WEB, FBV and TOJB, compared side by side with the Swift sample, before and after the fixes
• Right-to-left detection and long chapters (ASV and BSB Psalm 119)

🤖 Generated with Claude Code