CONTROLLED KOREAN FIXTURE · REAL BROWSER CAPTURE

Korean launch QA sample

3 checks × 2 viewports · captured 2026-08-09T07:45:21.132Z

HOLD

Truth boundary

This report came from an actual Playwright run with locale ko-KR against a controlled fixture. The mobile Korean CTA overflow was deliberately seeded. It is not a customer audit, native-human linguistic signoff, market-demand proof, security certification, or PayPal test.

Launch blocker

P1 · Korean call-to-action escapes its mobile container. The desktop assertion passed, while the 390px unit measured the CTA beyond its card. Hangul input round-trip and Korean locale checkout readback passed on both viewports.

Evidence family: FP-DEMO-KO-MOBILE-OVERFLOW. Recommended fix: remove the fixed mobile width, allow wrapping, and retain the no-overflow browser assertion as a regression test.

Required-unit matrix

FlowViewportStatusFailed evidence
Hangul input to saved valuedesktopPASS
Hangul input to saved valuemobilePASS
Korean mobile text containmentdesktopPASS
Korean mobile text containmentmobileFAILmobile_layout-mobile-S02
Korean locale checkout to backend orderdesktopPASS
Korean locale checkout to backend ordermobilePASS

Hangul input to saved value · desktop

PASS

Controlled browser evidence for Hangul input to saved value on desktop

Hangul input to saved value · mobile

PASS

Controlled browser evidence for Hangul input to saved value on mobile

Korean mobile text containment · desktop

PASS

Controlled browser evidence for Korean mobile text containment on desktop

Korean mobile text containment · mobile

FAIL

Controlled browser evidence for Korean mobile text containment on mobile

Korean locale checkout to backend order · desktop

PASS

Controlled browser evidence for Korean locale checkout to backend order on desktop

Korean locale checkout to backend order · mobile

PASS

Controlled browser evidence for Korean locale checkout to backend order on mobile

What the future service would add

Owner authorization, staging-only scope, Korean copy/context review, native evidence manifest, sanitized console/network records, one immutable recheck, private delivery, expiry, and payment-provider lifecycle controls. Those capabilities are not yet live.

Check non-QA pilot eligibility · View the USD 59 price hypothesis · Back to FlowProof