Upstream merged five of our Enriched Markdown PRs since the archive the app ships today: onLinksChange (software-mansion/enriched-markdown#1088), Android inline image alignment (software-mansion/enriched-markdown#1089), the iOS and Android build fixes (software-mansion/enriched-markdown#1086, software-mansion/enriched-markdown#1087), and the iOS streaming memory bounds from #24263 (software-mansion/enriched-markdown#1138). The fork still carried its own copies, three of which upstream edited before merging.
This moves the mobile app to archive 1.2.0-t3.18 from fork/t3-mobile 4287c5d3, on upstream 1d00a92a. The fork reverted its copies so upstream's versions apply, then merged upstream main. Upstream also brings code block renderers (used by #32190), onTextPress, spoken LaTeX, several Android layout fixes, and on iOS a newly mounted message now draws in its first frame instead of showing an empty box for a few frames (software-mansion/enriched-markdown#1139). Since software-mansion/enriched-markdown#1121 the app generates the library's codegen itself, so both native clients need a rebuild.
The fork carries these changes, each with an upstream PR:
Clipboard link metadata: software-mansion/enriched-markdown#962. The maintainer asked for a smaller API, and we agreed.
Development-host autolinks: software-mansion/enriched-markdown#961, waiting on software-mansion-labs/md4c#7.
md4cFlags.preserveWindowsPaths: software-mansion/enriched-markdown#1105, after mity/md4c#477.
New: ~ strikes through by GitHub's rules, so ~$0.48 vs ~$0.65 and ~/foo and ~/bar stay plain. From pingdotgg/enriched-markdown#11 by ahalekelly; upstream is software-mansion-labs/md4c#6.
New: links whose fragment is a hash route now link, such as https://host:9501/#/chat and our own /pair#token=… links. From pingdotgg/enriched-markdown#9 by Dananz, plus a fix that keeps a trailing ; out of the link. md4c master already does this (mity/md4c#454), and it arrives with software-mansion-labs/md4c#7.
New: with Render math on, \(…\) and \[…\] render as math. This is upstream's software-mansion/enriched-markdown#1043 (with software-mansion-labs/md4c#4) by Yash-Singh1, copied line for line. Fixes pingdotgg/t3code#29599.
New: on iOS, Copy as Markdown on part of - **What**: … no longer copies **W****hat**. From pingdotgg/enriched-markdown#12 by dansanduleac; upstream is software-mansion/enriched-markdown#1143.
New: a line break in a copied table cell stays <br>, so Copy as Markdown keeps the row whole. #29355 shipped this as a pnpm patch on the old archive. The fork now carries the same change, by shivamhwp; upstream is software-mansion/enriched-markdown#1144. The patch is gone.
.pnpmfile.cjs now fails any install whose patchedDependencies names a package that apps/mobile installs from apps/mobile/deps, Enriched Markdown or our react-native-screens fork. A patch on a fork tarball is a second source of truth that the next tarball drops without a trace, as the t3.16 patch would have been here.
Icon links that wrap (#32238) are left for a later build.
; case, and upstream's LaTeX cases), the WASM bundle check after a rebuild, all 1816 Jest tests, and the library build pass.vp run check:changed passes.~$0.48, ~/foo and ~/bar stay plain and ~~this~~ is struck;; outside;\(e^{i\pi}+1=0\) renders inline and the \[…\] sum as display math. With it off, the text is unchanged from before;- **What**: … copies - **What**. In a 30 fps recording of opening the thread, all message content appears in the same frame.| iOS | Android | iOS Copy as Markdown |
|---|---|---|
| iOS: strikethrough, hash-route links and bracket math in the fixture thread | Android: the same fixture thread | iOS: What selected with the Copy as Markdown menu |
Done with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code
Verdict: Approved at 7750c24
Macroscope's review found this PR approvable — Updates mobile Markdown rendering and copying behavior, consolidates the fork patch, and adds an install-time guard against patch drift. Reported iOS and Android verification supports the limited presentation risk; native clients need rebuilding.
You can add or adjust custom eligibility rules. Learn more.
✅ Thread transfer remains within every enforced ceiling.
| Provider | Metric | Main baseline | This PR | Impact | PR ceiling | |
|---|---|---|---|---|---|---|
| Codex | Total thread wire | 5.0 KiB | 5.0 KiB | 0 B (0.0%) | 6.8 KiB | ✅ |
| Codex | Thread snapshot wire | 3.8 KiB | 3.8 KiB | 0 B (0.0%) | 4.9 KiB | ✅ |
| Codex | Live turn WebSocket wire | 1.2 KiB | 1.2 KiB | 0 B (0.0%) | 2.0 KiB | ✅ |
| Codex | Live turn WebSocket decoded | 21.5 KiB | 21.5 KiB | 0 B (0.0%) | 24.4 KiB | ✅ |
| Codex | Live turn messages | 1 | 1 | 0 (0.0%) | 8 | ✅ |
| Claude | Total thread wire | 5.0 KiB | 5.0 KiB | 0 B (0.0%) | 6.8 KiB | ✅ |
| Claude | Thread snapshot wire | 3.8 KiB | 3.8 KiB | 0 B (0.0%) | 4.9 KiB | ✅ |
| Claude | Live turn WebSocket wire | 1.2 KiB | 1.2 KiB | 0 B (0.0%) | 2.0 KiB | ✅ |
| Claude | Live turn WebSocket decoded | 21.9 KiB | 21.9 KiB | 0 B (0.0%) | 24.4 KiB | ✅ |
| Claude | Live turn messages | 1 | 1 | 0 (0.0%) | 8 | ✅ |
Baseline: 0770446 · PR result: 7750c24 · Source CI: success
10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.
No actionable comments were generated in the recent review.
The mobile package now uses the react-native-enriched-markdown t3.17 archive, and the workspace allows its build scripts. The dependency README updates upstream notes and the archive example.
Changes: Enriched Markdown dependency
| Layer / File(s) | Summary |
|---|---|
Update archive reference and documentation apps/mobile/package.json, pnpm-workspace.yaml, apps/mobile/deps/README.md | The mobile dependency and workspace build permission now reference the t3.17 archive. The README identifies onLinksChange as upstream, removes two fork-specific entries, updates the Windows-path reference, and changes the archive example version and commit prefix. |
Estimated code review effort: 2 (Simple) | ~6 minutes
Change: Other
Possibly related PRs
Suggested labels: 📱 Native Change
Suggested reviewers: yash-singh1
edcb1The update is ready to merge after normal checks and native client rebuilds.
Failed Failed checks: 1 warning
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | Warning | The description follows the repository template in substance. It has a Problem-equivalent section explaining the archive move from t3.16 to t3.18 and the upstream changes it brings in. It has a Change… | 1. Add a 'Scope and approval' section. For each new fork behavior, link the triaged bug issue or the maintainer discussion with explicit approval, including the approval comment. Examples are the hash-route autolinks, bracket math delimiter… |
| Check name | Status | Explanation |
|---|---|---|
| Linked Issues check | Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | Passed | Check skipped because no linked issues were found for this pull request. |
| Title check | Passed | The title "chore(mobile): sync Enriched Markdown with upstream 1d00a92a" names the main change: syncing the mobile app's Enriched Markdown dependency with upstream commit 1d00a92a. The objectives and … |
Explanation
The title "chore(mobile): sync Enriched Markdown with upstream 1d00a92a" names the main change: syncing the mobile app's Enriched Markdown dependency with upstream commit 1d00a92a. The objectives and raw summary describe the dependency bump to archive t3.17 (commit 0706a56a, based on upstream 0b59df11), and the description describes archive t3.18 on upstream 1d00a92a. The title therefore matches the broad intent (a sync with upstream), but the referenced archive and upstream commits differ between the title/description and the code-level summary and objectives. The title is specific and conventional, so this is a discrepancy to note, not a failure.
Explanation
The description follows the repository template in substance. It has a Problem-equivalent section explaining the archive move from t3.16 to t3.18 and the upstream changes it brings in. It has a Change section describing the fork reverting its copies, merging upstream main, and the fork-carried changes, each with an upstream PR link. It has a Verification section with specific focused checks, observed results, and before/after screenshots and a recording reference. Gaps: the template's Scope and approval section is not present. The description does not link a triaged bug issue or maintainer-approved discussion for the new fork-carried behavior changes, such as the hash-route autolinks, the Render math bracket delimiters, and the iOS Copy as Markdown fix. It also does not explain why those 'New' items qualify for an exemption. The description also says the Windows-path and autolink entries await upstream, but it does not state what is not verified. The template asks for the model and harness used, and the description includes 'Done with Claude Opus 5.5 in Claude Code', which meets that requirement. The objectives text also reports a different archive commit (0706a56a, t3.17) and a different test count (1812 vs 1816) than the description (t3.18, 4287c5d3, 1816), which is a discrepancy the author should reconcile.
Resolution
b03c020f-d68f-4555-a87f-2060e66a339dReviewing files that changed from the base of the PR and between bdb8d5dfc067134f460ea7757e62355fe5f9b2a7 and edcb13d0ce3e2e140d64d19cd9e72239776f4ceb.
pnpm-lock.yaml is excluded by !**/pnpm-lock.yamlapps/mobile/deps/README.mdapps/mobile/deps/react-native-enriched-markdown-1.2.0-t3.16-29ddd424.tgzapps/mobile/deps/react-native-enriched-markdown-1.2.0-t3.17-0706a56a.tgzapps/mobile/package.jsonpnpm-workspace.yamlIncluded review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.
Added 5 commits