web: PRO needs a proven address — email verification gates the studio

A signed-in account is served exactly like a guest until it opens the
verification link: watermarked 2048px export, no saving, no PRO frames,
GPS stamp or HDF. SMTP is declared in .env; with SMTP_HOST unset the link
goes to the container log. Allowlisted admins count as verified.

docker/frontend/src/i18n/en.ts

@@ -109,6 +109,19 @@ export const en: Dict = {
   'auth.continueDemo': 'Keep using the demo',
   'auth.busy': 'Working…',
   'auth.loggedInAs': 'Signed in as {email}',
+  'auth.verifyTitle': 'Verify your email',
+  'auth.verifyBody': 'We sent a verification link to {email}. Open it to unlock the PRO features.',
+  'auth.verifyProHint': 'Until then the account works exactly like a guest: exports stay 2048px with a watermark, and nothing can be saved.',
+  'auth.verifySent': 'Verification email sent again.',
+  'auth.verifiedDone': 'I have verified',
+  'auth.signupVerifyHint': 'After signing up we email you a verification link — open it to unlock the PRO features.',
+
+  // The PRO gate. Signed in but unproven is served as a guest, so the studio
+  // needs one place that says why and one way to ask for the letter again.
+  'pro.verifyChip': 'VERIFY EMAIL TO USE PRO',
+  'pro.unverifiedBar': 'Account {email} is not verified — it works like a guest.',
+  'pro.resend': 'RESEND VERIFICATION EMAIL',
+  'pro.resent': 'SENT',
 
   'save.title': 'Save recipe',
   'save.name': 'Recipe name',