# Vietnamese bold rendering proof

Manual native-app comparison. Android is not supported by scenarios:prove.

Base: [87707319cf](https://github.com/pingdotgg/t3code/commit/87707319cff2c6886d8d5816793c7e1e70050605)
Head: [84e0849ba7](https://github.com/pingdotgg/t3code/commit/84e0849ba789cdc92db78fdfc463d0382c4564b2)

Use separate worktrees and fresh databases with T3CODE_DEV_SEED=0. Install dependencies with vp i. Run seed.py with the checkout root as its argument on each checkout before starting its dev server. This changes only the showcase replay recording, equally on both sides, and adds the reported phrases, regular controls, a bold Latin line, H2/H3 headings, and all affected precomposed glyphs.

Start dev:server with --host 0.0.0.0 and a synthetic environment label. Wait for the server to listen before running the CLI. Add the checkout as a project titled "Vietnamese typography" through `t3 project add`. Start a thread through `t3 thread start` with message "Show Vietnamese bold text and headings.", title "Chỉ đổi mỗi tên hiển thị", --provider devReplay --model showcase --wait --json. Use the checkout's own --base-dir and server port.

Prepare the native client for each platform with `vp run mobile:install <platform> --prepare`, then lease Pixel 9 / iPhone 17 Pro and install with --session. Run one Metro at a time from the tested checkout's apps/mobile directory, using dev:client, all interfaces, and a device-reachable host. Open its Expo development-client link, allow the iOS system confirmation if shown, and use test-t3-mobile's pair-client.sh to connect to that checkout's backend. Open the exact thread through `t3code-dev://threads/<environmentId>/<encodedThreadId>`.

Capture the completed assistant message in light T3 Code theme at default text size, with keyboard down and developer chrome disabled. The final replay response is visible below Worked for. It contains the reported strong spans, regular controls, bold Latin control, H2/H3 and affected glyph rows. No application rendering code is modified for the proof.

Then open these real app routes on each native client:
- t3code-dev://settings/appearance — selected System label uses font-t3-bold.
- t3code-dev://settings/open-source-licenses — select @babel/code-frame — large package title uses font-t3-bold.
- t3code-dev://dev/components — default Controls page — selected Light, Controls and Overview labels exercise font-t3-bold through the shared segmented control.

Run capture.py with output path, session name and checkout root. It takes two screenshots separated by a 500 ms pause and requires identical RGB evidence pixels (the full Android frame or the documented iOS crop). iOS captures use native 3x density with normalized status bar. Android captures are 1080x2424; iOS captures are 1206x2622. Open each capture to inspect it. The Android detail images are unscaled crops (40,1270,1040,2000) from the full chat screenshots, with identical coordinates on each side.

For iOS evidence, crop-ios.py checks identical RGB pixels from both captures after removing the top 150 pixels (the charging icon changes between captures). The Controls crop also stops at y=2240, before the catalog’s continuously animated Loading example. These are unscaled crops with matching coordinates on both commits.
