docs(loyalty): go-live readiness snapshot — 2026-05-10

Captures where the loyalty pre-launch checklist actually stands after
tonight's prod readiness pass:

  - Step 1 (email templates seeded) ✅
  - Step 2 (Google Wallet config) ✅ validated via wallet-debug
  - Step 3 (migrations) ✅ all module heads incl. loyalty_011 on prod
  - Step 7 (Wallet real-device test) ✅
  - Steps 4, 5 (FR/DE/LB analytics keys, store-owner template
    permission) deferred — cosmetic / non-blocking
  - Step 6 (8 user-journey E2E tests) is the remaining human gate
  - Step 9 (Google Wallet production access) post-launch

Also records the SMTP path-change diagnosis (own mail server on port
465 blocked outbound from Hetzner; switched to 587 STARTTLS via
/admin/settings DB overrides) and the cosmetic fix shipped in
f2d1bdcd so the test email reports the *effective* config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

app/modules/loyalty/docs/production-launch-plan.md

@@ -325,10 +325,13 @@ Tracked separately, not blocking launch.
 
 Everything below must be completed before going live. Items are ordered by dependency.
 
-### Step 1: Seed email templates on prod DB
-- [ ] SSH into prod server
-- [ ] Run: `python scripts/seed/seed_email_templates_loyalty.py`
-- [ ] Verify: 20 rows created (5 templates × 4 locales)
+> **Latest status snapshot:** see [Go-Live Readiness (2026-05-10)](../../proposals/loyalty-go-live-readiness.md)
+> — only Steps 6 and 8 still pending; Step 9 is post-launch.
+
+### Step 1: Seed email templates on prod DB ✅
+- [x] SSH into prod server
+- [x] Run: `python scripts/seed/seed_email_templates_loyalty.py`
+- [x] Verify: 20 rows created (5 templates × 4 locales)
 - [ ] Review EN email copy — adjust subject lines/body if needed via admin UI at `/admin/email-templates`
 
 ### Step 2: Google Wallet — already deployed, verify config
@@ -339,12 +342,13 @@ The Google Wallet integration is already deployed on the Hetzner server (see Ste
 - Service account linked to Issuer with Admin role ✅
 
 Verify after deploy:
-- [ ] Restart app — confirm no startup error (config validator checks file exists)
-- [ ] `GET /api/v1/admin/loyalty/wallet-status` returns `google_configured: true`
+- [x] Restart app — confirm no startup error (config validator checks file exists)
+- [x] `GET /api/v1/admin/loyalty/wallet-status` returns `google_configured: true`
+- [x] Wallet diagnostics screen at `/admin/loyalty/wallet-debug` → Config Validation → all green (validated 2026-05-10)
 
-### Step 3: Apply database migrations
-- [ ] Run: `alembic upgrade heads`
-- [ ] Verify migrations applied: `loyalty_003` through `loyalty_006`, `customers_003`
+### Step 3: Apply database migrations ✅
+- [x] Run: `alembic upgrade heads`
+- [x] Verify migrations applied: all four module heads current incl. `loyalty_011`
 
 ### Step 4: FR/DE/LB translations for new analytics i18n keys
 - [ ] Add translations for 7 keys in `app/modules/loyalty/locales/{fr,de,lb}.json`:
@@ -375,12 +379,12 @@ Follow the **Pre-Launch E2E Test Checklist** at the bottom of `user-journeys.md`
 - [ ] **Test 7:** Admin oversight (programs, merchants, analytics)
 - [ ] **Test 8:** Cross-location disabled behavior (separate cards per store)
 
-### Step 7: Google Wallet real-device test (demo mode)
+### Step 7: Google Wallet real-device test (demo mode) ✅
 Google Wallet currently works in **demo/test mode** — only your Google account and explicitly added test accounts can see passes. This is sufficient for launch testing.
-- [ ] Enroll a test customer on prod
-- [ ] Tap "Add to Google Wallet" on success page
-- [ ] Open Google Wallet on Android device — verify pass renders with merchant branding
-- [ ] Trigger a stamp/points transaction — verify pass auto-updates within 60s
+- [x] Enroll a test customer on prod
+- [x] Tap "Add to Google Wallet" on success page
+- [x] Open Google Wallet on Android device — verify pass renders with merchant branding
+- [x] Trigger a stamp/points transaction — verify pass auto-updates within 60s
 
 ### Step 8: Go live
 - [ ] Remove any test data from prod DB (test customers, test cards)