Skip to content

Set-up funnel rework - #3392

Merged
innolope-dev merged 90 commits into
devfrom
innolope/setup-coordinated-transitions
Oct 6, 2026
Merged

innolope-dev merged 90 commits into
devfrom
innolope/setup-coordinated-transitions

Conversation

@innolope-dev

@innolope-dev innolope-dev commented Sep 23, 2026 •

Copy link
Copy Markdown
Collaborator

Make signup open and guided, with residence-based feature introductions, email and notification choices, passkey confirmation, and a completion celebration. Preserve referral and marketing attribution without requiring an invite.

  • Update onboarding animations: add the first-launch mascot intro and full-screen celebration; use Phone to phone for the available-features checklist, Top up for funding, phone-receiving-an-update for notifications, Card flip for the pink card, and LATAM-to-Europe globe and Plane delivery from UI #3579 for bank accounts and “Pay people, not account numbers.” Increase movement of the residence passport, ID and checkmark while preserving the Peanut crest. Play the username @ background at 4× speed (a five-second loop), with smooth curves and matching inner/outer outlines; add three softly glowing background stars to the banking globe’s opening frame while retaining its 1× playback. Pause Card flip for one second after each loop and shorten the completion celebration from five to 4.5 seconds. Keep the centered celebration layout and render the fireworks and full-height side curtain as one coordinated canvas effect, with a denser top burst. All regions stop emitting together and fully settle before the 4.5-second redirect; no static stars remain after the fireworks. Preserve haptics, reduced-motion feedback, native particle budgets, Strict Mode safety and cleanup on hide/unmount. Use a 40% viewport-height artwork area on every mobile setup screen, reduce artwork by 20% on screens 6, 7, 8, 9 and 11 and their feature alternatives, and retain the larger notifications artwork. Preserve desktop layouts, reduced-motion still frames and cleanup when hidden or unmounted. Resolve the bank globe conflict with the updated Add money-plane and LATAM globe Lottie illustrations #3579 export and its loop fix. Verify playback, reduced motion, sizing and gallery navigation across all five feature combinations; browser card pauses measured approximately 1001ms.
  • Suggest residence from edge/IP country and choose the initial language from device/browser preferences; users still confirm residence.
  • Use matching 48px DataRows with black typography, icons, dashed dividers and interactive checkboxes on both checklists. Always show the available-features checklist for every residence, including restricted and partially supported countries; Ukraine shows Digital dollars account and Peanut-to-Peanut payments only. While the eligibility lookup is pending, show those two universal options and update the list when it settles. Remove the available-features introduction and row descriptions. Longer setup content scrolls so actions remain reachable.
  • Match funding choices to the available-features checklist: when only Digital dollars account and Peanut-to-Peanut payments are shown, offer Crypto and From someone on Peanut only. Keep all four funding choices when bank or card adds an available feature. Share the availability calculation between both screens and clear hidden Bank/Cash selections after residence changes while retaining visible choices.
  • Place funding between the two conditional feature introductions without changing eligibility: bank + card → Bank / Funding / Card; Argentina or Brazil → Bank / Funding / Local; bank only → Bank / Funding / Exchange; card only → Exchange / Funding / Card; neither → Exchange / Funding / People.
  • Save signup email before continuing, retain it on Next/Back, and use it as the editable default in Profile and web/native KYC. Require acknowledged notification opt-outs; permission denial and SDK failures still allow signup.
  • Show “The user with this email was already registered.” for the API’s duplicate-email response, with a grey “How to recover your account” link below Continue that opens the localized recovery guide in the setup drawer. Retain the email draft and clear the notice when edited; other save failures keep the retry message.
  • Preserve attribution across signup, store handoffs and app restarts, retaining unacknowledged writes for retry.
  • Restore the card eligibility, reveal and funding journey, including the card illustration and left-aligned copy. Require $10 in live spendable balance before a first application (UI enforcement).
  • Hide the Home welcome card after 24 hours from the first Home render, on the fifth Home visit, or when another checklist item completes, whichever happens first. Keep the checklist visible and remember dismissal per user on the device.
  • Replace generic navigation labels with the approved screen-specific copy: “Looks good,” “Now we’re talking,” “Love the pink,” “That’s a good deal,” “Let’s go local,” “That makes sense,” “Let’s keep going,” and “Sounds good.” The email button remains “Continue.”
  • Consolidate the own-name withdrawal notice and exchange-rate explanation into shared translation keys across claim, withdrawal and QR payment views. Use “updating” in the bank-verification message and the approved exchange-rate and Mercado Pago comparison copy.
  • Replace fractional screenshot-catalogue steps with distinct integers, preserving the setup journey and all conditional feature-screen sequences. Add regression coverage that validates the real catalogue in all four locales.
  • Use shared design-system components and translate all changes into English, Spanish, Argentine Spanish and Brazilian Portuguese, including regional fallback.

Backend dependencies: API #1789 for notification preferences and API #1579 for open signup and durable attribution. #1579 requires four database migrations: Render applies them automatically during staging builds on dev; production must apply them before API rollout. Detailed instructions remain in that PR.

Validation: 145 focused setup, DataRow and locale tests passed for the layout changes, followed by 45 locale/Manteca claim tests for shared copy and 61 focused player, email/notification, setup-document, transition and locale tests for the latest update. The 17 email/notification tests passed again after adjusting the recovery icon to the design-system 16px size. Full TypeScript, changed-file ESLint, Prettier and the complete design-system lint ratchet passed. Browser checks covered translated layouts at 320px and 390px, equal checklist rows, consistent button labels, localized recovery links and reachable actions without horizontal overflow. These component previews use mocked network/state; native-device behavior is not established by these checks.

The advisory screen-wordiness check measures Manteca withdrawal at 347/347, down from 353 after sharing the duplicate notice. After the provider-disclosure merge and readable Pix comparison copy, QR payment scores 225 against the current dev baseline of 203; this remains the only wordiness failure. The baseline is unchanged.

The screenshot-capture Invalid screen order failure is fixed by integer setup steps. The new regression test reproduced the failure before the change and now passes for all four locale manifests; all 23 catalogue, capture-core and route-inventory tests pass, with changed-file ESLint and Prettier also passing. The dev merge includes #3580’s fix for version-control files in prebuilt preview functions. Full before/after capture and deployment behavior still require current-head CI verification.

Public onboarding gallery

Latest motion/footer validation: 23 focused animation-player, email/notification and celebration tests passed. Browser checks measured the one-second card pause and verified the recovery link below Continue at 320px and 390px in all four locales. The original globe/route layers remain unchanged; the new glow layers have matching loop endpoints, and @ outlines have equal stroke widths with the fill painted behind the inner stroke. Full TypeScript, changed-file ESLint, Prettier and the design-system lint ratchet passed.

Latest checklist/order validation: 98 residence and setup-flow tests passed, including forward/back navigation for all five feature combinations and exactly two interactive options for Ukraine. All 23 capture/catalogue/inventory tests passed with distinct integer orders. Browser checks covered 24 conditional-checklist layouts across four locales at 320px and 390px. Full TypeScript, changed-file ESLint, Prettier and the design-system lint ratchet passed. Current-head CI remains separate from this local validation.

Latest funding validation: all 91 funding, residence and residence-availability tests passed, covering two-option countries, three/four-feature countries, residence changes and pending eligibility. Browser checks covered the two-row funding layout in all four locales at 320px and 390px, with 48px rows and reachable actions. Full TypeScript, changed-file ESLint, Prettier and the design-system lint ratchet passed.

Latest celebration validation: all 30 success, final-confirmation, shared-confetti, coordinated-curtain and lifecycle tests passed. Browser checks covered eight translated layouts, particle coverage on both sides from top to bottom, and a completely clear canvas before redirect. Full TypeScript, changed-file ESLint, Prettier and the design-system lint ratchet passed.

  • Unify setup typography and field sizing: use 16px Body/M descriptions with 26px line height and the approved #5F646D colour throughout setup, including residence and celebration. Keep notes and legal text at their secondary sizes; use the DS 48px email input to match username.

  • Typography/input verification: 33 focused setup tests, TypeScript, changed-file ESLint, Prettier and DS ratchet passed; rendered component previews checked across all four supported locales at 320px and 390px widths. Full Next.js preview verification was unavailable because the existing development server timed out while compiling.

Latest dev conflict resolution: preserve the approved Mercado Pago savings explanation from commit 2bbf8f46c and the shared exchange-rate/own-account notices while importing dev’s Manteca provider row, disclosure sheet, and other upstream updates. Apply the same readable style to the Pix savings tooltip in all four locales: lead with how the payment works, explain IOF as Brazilian tax, and replace issuer FX jargon with currency conversion fees. Keep the catalogue membership test independent of journey order, and regenerate the marketing catalogs.

Conflict-resolution validation: all 523 tests across the 32 upstream-changed suites, all 149 focused locale/provider/catalogue tests, and all 166 screen-library script tests passed. Full TypeScript passed after generating Next types; translation formatting and the Git whitespace/conflict-marker checks passed. The full local Jest run stalled and was stopped, so full-suite validation remains with current-head CI. The deliberate readable-copy growth leaves the advisory QR wordiness score at 225/203; the baseline is unchanged by this resolution.

@innolope-dev innolope-dev self-assigned this Sep 23, 2026
@vercel

vercel Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
peanut-wallet Ready Ready Preview Oct 6, 2026 1:57pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: peanutprotocol/peanut-ui/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 601559cc-a4b0-4f9a-b164-c8fc64fb859d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions

github-actions Bot commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Code-analysis diff

Painscore total: 9216.83 → 9391.45 (+174.62)
Findings: +103 net (+437 new, -334 resolved)

🆕 New findings (437)

  • critical complexity — src/utils/general.utils.ts — CC 303, MI 55.51, SLOC 1033
  • critical complexity — src/app/(mobile-ui)/withdraw/manteca/page.tsx — CC 234, MI 50.87, SLOC 849
  • critical complexity — src/components/Claim/Link/useInitialClaimFlow.ts — CC 178, MI 49.21, SLOC 741
  • critical complexity — src/components/Setup/components/SetupWrapper.tsx — CC 164, MI 59.83, SLOC 308
  • critical complexity — src/utils/signup-attribution.ts — CC 160, MI 55.11, SLOC 452
  • critical complexity — src/app/(setup)/setup/page.tsx — CC 132, MI 57.74, SLOC 442
  • critical complexity — src/dev/surfaces/registry.tsx — CC 113, MI 68.04, SLOC 557
  • critical complexity — src/utils/deferred-link.ts — CC 108, MI 53.88, SLOC 358
  • critical complexity — src/hooks/useNotifications.ts — CC 107, MI 56.23, SLOC 451
  • critical complexity — src/components/AddMoney/components/AddMoneyBankDetails.tsx — CC 98, MI 53.54, SLOC 246
  • critical complexity — src/features/card/useCardFlow.ts — CC 98, MI 51.45, SLOC 457
  • critical complexity — src/components/Invites/InvitesPage.tsx — CC 83, MI 55.7, SLOC 206
  • critical complexity — src/components/Setup/Views/Residence.tsx — CC 79, MI 62.14, SLOC 254
  • critical complexity — src/app/(mobile-ui)/MobileLayoutClient.tsx — CC 75, MI 56.93, SLOC 124
  • critical complexity — src/components/AddMoney/components/MantecaAddMoney.tsx — CC 74, MI 54.08, SLOC 250
  • critical method-complexity — src/app/(mobile-ui)/withdraw/manteca/page.tsx:125 — MantecaBankWithdrawFlow CC 65 SLOC 298
  • critical complexity — src/components/Claim/Link/SendLinkActionList.tsx — CC 65, MI 55.54, SLOC 212
  • critical complexity — src/components/Setup/Views/SignTestTransaction.tsx — CC 61, MI 54.62, SLOC 256
  • critical complexity — src/components/Profile/views/ProfileEdit.view.tsx — CC 60, MI 52.73, SLOC 197
  • critical complexity — src/components/Setup/Views/Signup.tsx — CC 58, MI 56.27, SLOC 225

…and 417 more.

✅ Resolved (334)

  • src/utils/general.utils.ts — CC 303, MI 55.5, SLOC 1033
  • src/app/(mobile-ui)/withdraw/manteca/page.tsx — CC 234, MI 50.86, SLOC 850
  • src/components/Claim/Link/useInitialClaimFlow.ts — CC 182, MI 48.7, SLOC 774
  • src/app/(setup)/setup/page.tsx — CC 131, MI 57.33, SLOC 450
  • src/components/Setup/Views/Residence.tsx — CC 103, MI 61.26, SLOC 301
  • src/dev/surfaces/registry.tsx — CC 97, MI 67.92, SLOC 497
  • src/hooks/useNotifications.ts — CC 96, MI 56.28, SLOC 416
  • src/components/AddMoney/components/AddMoneyBankDetails.tsx — CC 95, MI 53.15, SLOC 239
  • src/features/card/useCardFlow.ts — CC 90, MI 51.68, SLOC 438
  • src/components/Invites/InvitesPage.tsx — CC 85, MI 55.64, SLOC 206
  • src/app/(mobile-ui)/MobileLayoutClient.tsx — CC 79, MI 56.66, SLOC 126
  • src/components/Invites/JoinWaitlistPage.tsx — CC 78, MI 56.21, SLOC 291
  • src/components/AddMoney/components/MantecaAddMoney.tsx — CC 74, MI 54.13, SLOC 249
  • src/app/(mobile-ui)/withdraw/manteca/page.tsx:125 — MantecaBankWithdrawFlow CC 65 SLOC 299
  • src/components/Claim/Link/SendLinkActionList.tsx — CC 65, MI 55.47, SLOC 213
  • src/utils/deferred-link.ts — CC 61, MI 58.09, SLOC 211
  • src/components/Profile/views/ProfileEdit.view.tsx — CC 59, MI 53.02, SLOC 193
  • src/components/Kyc/SumsubNativeSdk.tsx — CC 56, MI 59.15, SLOC 203
  • src/components/Profile/components/PublicProfile.tsx — CC 52, MI 56.64, SLOC 148
  • src/components/Kyc/useSumsubWebSdk.ts — CC 50, MI 59.18, SLOC 251

…and 314 more.

📈 Painscore deltas (top movers)

File Before After Δ
src/utils/signup-attribution.ts 0.0 14.9 +14.9
src/components/Setup/Views/Email.tsx 0.0 8.3 +8.3
src/components/Setup/components/SetupWrapper.tsx 11.6 19.9 +8.2
src/services/pending-invite-attribution.ts 0.0 7.8 +7.8
src/components/Setup/components/OnboardingAnimation.tsx 0.0 7.6 +7.6
src/features/card/components/CardAcquisitionScreen.tsx 0.0 7.2 +7.2
src/hooks/useFirstLaunchIntro.ts 0.0 6.8 +6.8
src/features/setup/country-signals.ts 0.0 6.6 +6.6
src/components/Global/PeanutMascot/PeanutMascotScene.tsx 0.0 6.3 +6.3
src/components/Setup/Views/Notifications.tsx 0.0 6.1 +6.1
src/components/Setup/Views/Funding.tsx 0.0 6.0 +6.0
src/features/home/useHomeWelcome.ts 0.0 6.0 +6.0
src/services/signup-attribution.ts 0.0 5.6 +5.6
src/components/Setup/Views/Success.tsx 0.0 5.1 +5.1
src/components/Setup/components/setupDocuments.server.tsx 0.0 5.0 +5.0
src/utils/setup-celebration.ts 0.0 5.0 +5.0
src/components/Setup/components/CelebrationCurtain.tsx 0.0 4.9 +4.9
src/features/setup/filterSetupSteps.ts 0.0 4.9 +4.9
src/components/Setup/Views/Advantage.tsx 0.0 4.8 +4.8
src/components/Setup/components/SetupLanguageSwitcher.tsx 0.0 4.6 +4.6

@github-actions

github-actions Bot commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

🧪 UI test report — ✅ all green

Suites

  • ✅ unit: 11265 ran, 0 failed, 0 skipped, 4.3m

📊 Coverage (unit)

metric %
statements 83.9%
branches 74.3%
functions 78.7%
lines 85.2%
⏱ 10 slowest test cases
time test
🐢 9.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › Network failure keeps loading while retries remain, then shows the generic error
4.1s src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › never places two stickers in heavy overlap (broad seed sweep)
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_MERCHANT_RECENT_REFUND fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_USER_NOT_PROVISIONED fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › a refused idempotency key tells the user to scan again, not to contact support
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_MERCHANT_VOLUME_NEAR_CAP fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › routes the KYC rejection on its wire code, and does not retry it
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › User KYC not approved fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_SOURCE_OVER_MONTHLY_CAP fails fast with copy that names the real cause
3.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › Going offline blames the connection, and reconnecting clears it for the recovered scan
📍 Inline annotations are in the **Unit test report** check above. Coverage artifact: `coverage-unit`. Generated by `.github/workflows/tests.yml`.

@chip-peanut-bot chip-peanut-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chip review — no blocking findings — this is not an approval

The screen catalogue still prevents visual captures, and the QR copy still exceeds its CI baseline. The recovery-guide icon is fixed; none of the three earlier save-path findings survives.

Findings

  • MAJOR · src/dev/screens/catalogue.ts:126 · Keep setup screen orders valid for screenshot capture
    These new fractional setup steps (43.5 here, and 43.2/43.6/43.7 below) become screen order values, but validateCapture requires Number.isInteger(order). At the preceding head, all eight before/after capture jobs failed with Invalid screen order; this head changes only the email icon, leaving the failure path intact. Renumber the setup journey with distinct integer steps in the intended order.

  • MINOR · src/features/payments/flows/qr-pay/views/QrPayFormView.tsx:220 · Reconcile the QR payment copy budget
    The shared exchange-rate tooltip and revised comparison copy raise this screen to 214 words against its 200-word baseline. The screen-wordiness check failed at the preceding head, and this head only changes an email icon. Shorten the copy or update the baseline with the rationale for the approved longer wording.

Checked clean

  • Prior P1 is fixed: explicit notification opt-outs require an acknowledged preferences write before advancing.
  • Prior P2 is fixed: failed attribution attachment keeps a user-bound pending marker for retry.
  • Prior P3 is fixed: failed email writes retain the draft and do not advance setup.
  • The latest commit changes only the recovery-guide icon from 14px to the design-system 16px size, resolving the preceding off-scale finding.
  • Current-head capture and wordiness CI jobs were still in progress at review time; their affected code is unchanged from the preceding head whose failure logs were inspected.
  • Local reruns were unavailable because the supplied detached worktree has no installed dependencies.

Security review by moonshotai/kimi-k3: 0 finding(s), marked with the model name. It reads the diff only and answers only security, privacy and money, so treat its findings as advice.

Third opinion: did not run — it reads only the first review of a pull request; the first reviewer checks later rounds. This review is one reviewer short.

Exact head: 432eca63e464 · Context: repo, sibling, ci · Took 7m

Comment thread src/dev/screens/catalogue.ts Resolved

@chip-peanut-bot chip-peanut-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chip review — no blocking findings — this is not an approval

The screenshot-catalogue order is fixed. The QR payment screen still exceeds the advisory wordiness baseline; the other five listed findings are fixed at this head.

Answered by a human, not raised again

These are still present as far as this review can tell. You resolved the thread or deferred the fix, so Chip files them instead of repeating them.

  • MINOR · src/features/payments/flows/qr-pay/views/QrPayFormView.tsx:220 · Reconcile the QR payment copy budget — no task filed, please file one

Checked clean

  • P1 fixed: explicit notification opt-outs require acknowledged preference writes before setup advances.
  • P2 fixed: unacknowledged signup-attribution attachment keeps its user-bound retry marker.
  • P3 fixed: failed email writes retain the draft and prevent setup advancement.
  • P4 fixed: all 21 account-setup catalogue steps are distinct integers; the added test validates manifests in all four locales using the capture validator.
  • P6 fixed: the recovery-guide icon now uses the design-system 16px size; design-system lint succeeded at the preceding head.
  • Current-head screenshot and wordiness CI jobs were in progress at review time; the QR copy and baseline are unchanged from the preceding failed wordiness check.

Security review by moonshotai/kimi-k3: 0 finding(s), marked with the model name. It reads the diff only and answers only security, privacy and money, so treat its findings as advice.

Third opinion: did not run — it reads only the first review of a pull request; the first reviewer checks later rounds. This review is one reviewer short.

Exact head: 205b0933b1d2 · Context: repo, sibling, ci · Took 6m

@chip-peanut-bot chip-peanut-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chip review — no blocking findings — this is not an approval

The new shared residence checklist promises account and payment access to sanctioned residents. The changed common translations leave the marketing catalogs out of sync and the unit check failing. The QR copy budget finding remains; P1–P4 are fixed.

Findings

  • MAJOR · src/components/Setup/Views/Residence.tsx:199 · Do not promise Peanut access to sanctioned residents
    Selecting a fully restricted sanctioned residence such as Iran or Russia now enters this shared checklist and displays checked “Digital dollars account” and “Peanut-to-Peanut payments” under “Here’s what you get with Peanut.” Peanut’s country policy excludes the sanctioned countries from the product; open registration does not make these benefits available. Keep the checklist for eligible restriction tiers, but show an honest unavailable state for sanctioned residences instead of these checked promises.

  • MAJOR · src/i18n/app/messages/en.json:3 · Regenerate marketing catalogs after adding common copy
    Adding these common keys in all four app catalogs without regenerating their .marketing.json subsets makes marketing-messages.test.ts fail for every locale in the preceding head’s unit check; this head does not change either catalog set. common is a required marketing namespace, so run the marketing-message generator and commit the updated subsets.

Answered by a human, not raised again

These are still present as far as this review can tell. You resolved the thread or deferred the fix, so Chip files them instead of repeating them.

  • MINOR · src/features/payments/flows/qr-pay/views/QrPayFormView.tsx:220 · Reconcile the QR payment copy budget — no task filed, please file one

Checked clean

  • P1 fixed: explicit notification opt-outs still require acknowledged preference writes before advancing.
  • P2 fixed: failed signup-attribution attachment still retains its user-bound retry marker.
  • P3 fixed: a failed email write retains the draft and does not advance; the moved recovery link remains conditional on duplicate email.
  • P4 fixed: setup catalogue order values remain distinct integers; all eight capture jobs succeeded at the preceding head.
  • The new feature-step sequence places funding between the two selected introductions and has focused forward/back tests.
  • The Lexicon establishes open registration, while the current country policy excludes sanctioned residences from Peanut availability.
  • Current-head unit and wordiness CI jobs were still pending at review time; their affected catalog and QR-copy files are unchanged from the preceding failing head.

Security review by moonshotai/kimi-k3: 0 finding(s), marked with the model name. It reads the diff only and answers only security, privacy and money, so treat its findings as advice.

Third opinion: did not run — it reads only the first review of a pull request; the first reviewer checks later rounds. This review is one reviewer short.

Exact head: 074819998495 · Context: repo, product, lexicon, ci · Took 9m

Comment thread src/i18n/app/messages/en.json Resolved

This branch was successfully deployed

1 active deployment
Preview — 0f6b0e6f Deployed Oct 6, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant