Ecosystem Cleanup — Execution Hand-Off (2026-07-06)

Everything Claude could do from code is done and committed. This file is the short list of what only Eric can do, plus exactly what shipped and where.

✓ What shipped today

Rewardee repo (github.com/boommedia/rewardee, main — pushed)

• Phase 1 committed (was 21+ uncommitted files, 43 files / ~11.8k lines): dashboard (members, rewards catalog, staff rewards, AI assistant, billing), customer portal, /rate flow, full API (/api/award, /api/balance, /api/staff/*, billing webhooks), 002_boo_loyalty_tables.sql, 003_staff_reviews.sql.
• NEW supabase/004_boo_bridge.sql — bridges every BOO restaurant onto the Rewardee engine: nullable owner_id, table_label/legacy_id columns, a rewardee_businesses row per restaurant (slug = client_id), imports legacy JSON staff reviews, seeds loyalty_program_config with BOO's LIVE rates (1 pt/$1, 100 pts = $5, min 100, cap 50%, lucky orders OFF). Idempotent.

boo-v2 repo (branch ecosystem-cleanup — pushed, NOT merged)

• Commit 1 (copy): Replyee = "AI chatbot & live chat" everywhere (addons card, site strip, /saas page, app console rewritten from review-inbox to chatbot, suggest_reply → test_question AI action); Compliee = "scanning & monitoring" (FTC guardrail — was "ADA compliance"); Assistee = remote desktop support (was "AI ordering assistant"); Servvee removed from public lists; portal "Staff Reviews" → "Staff Recognition".
• Commit 2 (engine swap): new src/lib/rewardee.ts bridge; lib/staff-reviews.ts reads/writes rewardee_staff* tables (legacy value_json fallback until the SQL runs; POS/HR roster auto-syncs in); checkout earn/redeem goes through awardOrderPoints() — config-driven rates + loyalty_transactions ledger + opt-in Lucky Order bonuses. Best-effort everywhere: a loyalty failure never touches a paid order.

Safe deploy order: the branch is written to be safe in ANY order (fallbacks), but the intended order is SQL first, then merge.

🔲 Eric's 4 steps (in order)

1. Run the Rewardee SQL at https://studio.boommedia.us (SQL editor), in order, from the Rewardee repo supabase/ folder:
   001_rewardee_schema.sql → 002_boo_loyalty_tables.sql → 003_staff_reviews.sql → 004_boo_bridge.sql.
   (001–003 may already be partially run — all are IF NOT EXISTS-safe.)
2. Merge & deploy boo-v2: merge branch ecosystem-cleanup into main (GitHub PR or git merge), let Coolify deploy.
3. Smoke test (5 min): place one test order with a signed-in customer → confirm points earned + a row appears in loyalty_transactions; open /{slug}/rate → submit a staff rating → confirm it lands in rewardee_staff_reviews and shows on the portal Staff Recognition page.
4. Rewardee Stripe products (for standalone selling, not needed for BOO): Starter $29 / Growth $59 / Agency $99 at dashboard.stripe.com → price IDs into Vercel env (STRIPE_PRICE_*) + RESEND_API_KEY + NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY + STRIPE_WEBHOOK_SECRET.

Notes / follow-ups (not urgent)

• Replyee: still verify 002_live_chat.sql ran + one E2E handoff test.
• Displayee/KDS split (R10 ruling): BOO keeps KDS data+logic; point Displayee's Fire TV app at BOO's /kds/[slug] — separate session.
• 1–2★ staff ratings now award 0 pts (Rewardee config default) instead of legacy 1 pt. Change in rewardee_staff_config per business if unwanted.
• Redeem-rate UI in cart still uses platform constants (matches seeded config); making redemption config-driven per restaurant is a later enhancement.
• Six light BOO hooks still open (Bloggy, Rankee, Posttee, Compliee, Signnee, Assistee) — see the decision board Section 2.