#32004731 A4A > Referrals: add referral logo picker and shared logo validation

Part of https://linear.app/a8c/issue/A4A-2092/frontend-logo-picker-and-co-branded-checkout-ui
Resolves https://linear.app/a8c/issue/A4A-2121/initial-implementation-of-logo-upload-for-referrals

Proposed Changes

• Add a new feature-flagged referral logo section in checkout (a4a-referral-cobranded-checkout) and enable it in A4A development + horizon.
• Extract logo UI/behavior into a dedicated ReferralLogo checkout component and a reusable LogoFileUpload component.
• Add shared logo validation helpers (logo-file-validation.ts) and use them across referral checkout and partner-directory (consistent format + dimension checks; partner-directory keeps no size limit as requested).
• Update referral flow behavior so:
  • profile logo option is shown only when agency.profile.company_details.logo_url exists,
  • profile preview renders under “Use profile logo” only when selected,
  • uploader renders under “Use a different logo…” only when selected.

Why are these changes being made?

These changes implement the frontend for the co-branded referrals checkout experience:

• let agencies choose branding for each referral (Use profile logo vs Use a different logo for this referral),
  show the profile logo preview when selected,
• allow logo upload for referral branding,

Testing Instructions

Note: This is not a full implementation.

• Open the A4A live link > Go to Partner Directory > Edit Profile > Please don’t save the changes if you haven’t uploaded any logo till now. Try uploading a logo that is not 800px*320px > Verify that the error is shown as before. We refactored the logic a bit here. The intention is to see if it still works fine.
• Go to Marketplace > Toggle the referral mode > Select some products > Go to checkout > Verify the Logo section is displayed as shown below:

When there is no profile logo

When there is a profile logo

• If you don’t have a profile logo uploaded,> Go to Partner Directory and upload the profile logo > Come back to Referral checkout and verify you can see it here.
• Verify you can choose both the option > Select “Use a different logo for this referral” > Play around with different scenarios mentioned below and verify it works as expected.

When no logo is uploaded:

When a logo is uploaded:

Error scenarios:

• Append the URL with ?flags=-a4a-referral-cobranded-checkout and verify you are able to send a referral.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?