From 1425b48239580d61dce89ad813b37c0f910629de Mon Sep 17 00:00:00 2001 From: Samir Boulahtit Date: Sat, 16 May 2026 23:50:23 +0200 Subject: [PATCH] docs(loyalty): record session pause + next-session resume sequence Add a short "Next session" subsection to the 2026-05-16 update spelling out the three steps to pick up Test 1 round 2 (SMTP re-apply post-reset, program sanity check, live log tail + fresh enrollment). Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/proposals/loyalty-go-live-readiness.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/proposals/loyalty-go-live-readiness.md b/docs/proposals/loyalty-go-live-readiness.md index e63fb608..7228c702 100644 --- a/docs/proposals/loyalty-go-live-readiness.md +++ b/docs/proposals/loyalty-go-live-readiness.md @@ -62,6 +62,14 @@ After reset, admin credentials are back to the defaults from `init_production.py - Step 3 (migrations) — now at `tenancy_005`, still ✅ - Step 6 (web user-journey E2E tests) — Test 1 round 2 pending on clean DB; the bugs found in round 1 are no longer blockers +### Next session + +Session paused 2026-05-16 evening. To resume Test 1 round 2: + +1. Re-apply SMTP overrides under `/admin/settings` (port 587, STARTTLS, `support@wizard.lu`) — the reset wiped them. +2. Confirm `/admin/loyalty/programs` shows the Fashion Group program (should be seeded by `seed_demo.py`). +3. Tail `api` and `celery-worker` logs live, then enroll at `https://fashionhub.rewardflow.lu/loyalty/join` with a fresh email. The point of the live tail is to catch where B1-F actually dies — at dispatch, at SMTP, or somewhere else. + ## Status board | # | Pre-launch step | State | Notes |