T3 Code referral verification

Cross-platform verification for PR #8330. The referral balance is account-backed, the shared link is canonical, and the interface was tested from the actual web and mobile components against the real referral routes in isolated environments.

Passed locally on web, desktop, iOS, and Android
201points visible on the same referrer account after three successful referrals
67 × 3web, iOS, and Android each completed one real claim-and-link award
61 / 61focused referral, relay, discovery, resolver, and client-state tests passed

What was proven

1 · Web referralThe hosted link was opened, its ref value was retained, the URL was cleaned, sign-in was prompted once, and the claim completed after authentication. Balance: 67.
2 · iOS referralThe code was applied in the actual React Native screen, the success alert appeared, and the first environment link qualified it. Balance: 134.
3 · Android referralThe release bundle applied the code, showed the native success alert, linked the environment, and awarded once. Balance: 201 everywhere.

Exact link and share copy

https://app.t3.codes/?ref=0101010101014101
Try T3 Code with my referral. If you claim it before linking your first environment, I get 67 points.
https://app.t3.codes/?ref=0101010101014101

The message says who receives the points. It does not imply that the recipient gets 67 points. Invalid codes are rejected before a link can be generated, and codes with separators are normalized into the canonical 16-character URL.

Test matrix

SurfaceResultEvidence
Web · desktop widthPassedActual referrals component, real route client, 201-point account state, copy/share controls.
Web · narrow widthPassed390 × 844 responsive layout with the same live account state.
Hosted referral URLPassedCapture, history cleanup, one sign-in prompt, pending-code retention, automatic post-sign-in claim.
DesktopPassedProduction web renderer bundled into Electron; full desktop build and post-build Electron smoke passed.
iOS simulatorPassedNative claim, success alert, share sheet, first-environment qualification, live simulator stream.
Android emulatorPassedEmbedded release bundle, native claim and alert, Android share chooser, exact shared URL/message.
Multi-device account statePassedThe same referrer showed 201 points and 3 successful referrals on web, iOS, and Android.

Automated and build checks

Focused tests76 passed10 files: relay rules, first-link ordering, blocked storage, native share dismissal, claim recovery, client state, discovery, resolver, and shared helpers.
Typechecks4 passedShared, web, mobile, and desktop.
Production buildsPassedWeb, server sidecar, and Electron bundle.
Lint and formatPassedAll touched TypeScript/TSX plus mobile native static checks.
PR automation18 passed · 8 skipped · 1 neutral · 0 failedLatest pushed commit 22ee34f09.

Web

T3 Code web referrals page using muted T3 theme surfaces
Corrected desktop-width Clerk profile surface. Muted shadcn cards, secondary utility actions, and T3 theme tokens replace the high-contrast rule grid.

iOS

T3 Code iOS referrals screen showing 201 points
Final iOS state: 201 points, 3 successful referrals, T3 Settings grouped-section design.
iOS native referral applied confirmation
Native confirmation after applying a referral code.
iOS native share sheet containing the T3 Code referral
Native iOS share sheet from the actual screen.

Android

T3 Code Android referrals screen showing 201 points
Final Android release-bundle state: the same account total and grouped T3 Settings design.
Android native share chooser containing the exact T3 Code referral message and URL
The Android chooser exposes the exact canonical URL and honest 67-point copy.

Environment boundary

No production account or live database was mutated. Tests used isolated relay state. Referral routing, ledger behavior, UI state, native share surfaces, and environment qualification were real. The web harness replaced only the external Clerk identity boundary so signed-out and signed-in states could be driven deterministically.