fix(app-lock): friendlier lock-screen copy

[innolope-dev]

What

Reword the native app-lock screen. The shipped copy — "Peanut is locked" / "Could not confirm it is you. Try again to continue." — reads as scary and technical, especially for users hitting the gate for the first time after today's build.

New copy:

• Title: Welcome back!
• Prompt: Please log in to access the app.
• After a failed/cancelled attempt: Please log in again to access the app.
• Primary button: Log in (was "Unlock"); "Log out" unchanged.

Copy-only — no behavior change.

Notes

#2489 rewrites this component with localized strings (appLock.* in src/i18n/app/messages); a matching commit on that branch updates all three locales, so whichever merges first, the friendly copy wins.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
peanut-wallet	Ready	Preview, Comment	Jul 23, 2026 1:33pm

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 40995ab2-d49e-4928-9b68-8cd2e01d07fc

📥 Commits

Reviewing files that changed from the base of the PR and between 5fd5969 and 2ee9362.

📒 Files selected for processing (1)

• src/components/Global/AppLock/index.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/app-lock-friendly-copy

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Code-analysis diff

Painscore total: 6242.76 → 6242.89 (+0.13)
Findings: 0 net (+0 new, -0 resolved)

[github-actions]

🧪 UI test report — ✅ all green

Suites

• ✅ unit: 2062 ran, 0 failed, 0 skipped, 35.0s

📊 Coverage (unit)

metric	%
statements	60.1%
branches	43.9%
functions	49.0%
lines	60.5%

⏱ 10 slowest test cases

time	test
3.8s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › never places two stickers in heavy overlap (broad seed sweep)
1.2s	src/utils/__tests__/demo-api.test.ts › isDemoMode() is false when not running under Capacitor
0.5s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › every sticker stays within canvas at any count
0.4s	src/app/actions/__tests__/api-headers.test.ts › should include Content-Type in validateInviteCode
0.3s	src/app/actions/__tests__/api-headers-extended.test.ts › should not include apiKey in validateInviteCode body
0.3s	src/app/(mobile-ui)/withdraw/__tests__/withdraw-states.test.tsx › Bank withdrawal keeps the $1 minimum for sub-$1 amounts
0.2s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › keeps stickers off the username pill (final pass respects the keep-out)
0.1s	src/utils/__tests__/demo-balance.test.ts › starts at the full balance on a fresh install and stamps a timestamp
0.1s	src/utils/__tests__/url.utils.test.ts › uses the public BASE_URL in Capacitor, not the localhost WebView origin
0.1s	src/services/__tests__/resolveClaimLink.test.ts › restores the pristine password after a redirect mangles the fragment

_{📍 Inline annotations are in the **Unit test report** check above. Coverage artifact: `coverage-unit`. Generated by `.github/workflows/tests.yml`.}

[kushagrasarathe]

Reviewed — SAFE. Approving.

Copy-only change to the app-lock screen, no behavior change; follows the primary-CTA design-system convention (variant="purple" shadowSize="4"). #2489 rewrites this component with localized appLock.* strings, so whichever merges first the friendly copy wins.

Nit (non-blocking): the primary button now reads "Log in" but it triggers a biometric unlock (the user is already authenticated), so "Log in" is a slight misnomer vs. "Unlock". Superseded by #2489's localized copy anyway — fine to ship.