MultiverbeBOS

Sessione C — Handoff (2026-05-10 sera, post sessione B)

Sessione: vibrant-bose-36816a (worktree codice Multiverbe) Modello: Claude Opus 4.7 (1M context) Durata: ~2.5h Task principale: Stripe checkout flow code building + git hygiene merge sessione B → master + canon commit

✅ Cosa è stato fatto

1. Git hygiene Multiverbe (codice)

Master Multiverbe ora include:

  • 3 commit "leftover sessione A" recuperati dal main worktree (CLAUDE.md skills 8→10, .env.example pulizia, Stripe deps in package.json, asset Closed-Sphere + sales brief, Stripe scaffold api/+lib+types)
  • 3 commit sessione B mergiati con --no-ff (CLAUDE.md conflict risolto in favor di c3c393a "complete rewrite canon 6 pianeti")
  • 1 commit sessione C: feat(billing): Stripe checkout flow (10 file, +1259 righe)
  • 1 merge commit

HEAD attuale: f659740 (locale, NON pushato — rule sistema "direct push to default branch" blocca, founder push manuale).

2. Git hygiene Multiverbe-Business

main pushato a origin/main:

  • f70add3 — docs(canon + ops): Business Plan v2.32 + decisioni founder 2026-05-10 (6 file)

5 file untracked rimasti (working notes operativi): canon/10-admin-ch-italia-transition.md, execution/days-3-6-roadmap.md, execution/next-session-prompt-2026-05-10.md, ops/business-eye-audit-2026-05-10.md, ops/session-A-handoff-2026-05-10.md. Da commit a fine workflow se ha senso.

3. Stripe checkout flow code (code-only, NO Stripe products yet)

Files creati:

  • database/migrations/2026-05-11a_stripe_idempotency_setup_fee.sql — ALTER webhook_events.stripe_event_id UNIQUE + subscriptions.setup_fee_paid (NON applicata, founder gate)
  • frontend/.../api/stripe/create-checkout-session.ts — Vercel function POST endpoint, auth Supabase JWT, RLS workspace ownership check, line_items recurring + setup_fee opzionale
  • frontend/.../scripts/seed-stripe-prices.ts — Node script idempotent che crea 6 product + 9 price CHF (uso STRIPE_SECRET_KEY=sk_test_... npx tsx scripts/seed-stripe-prices.ts)
  • frontend/.../src/hooks/useCheckout.ts — React Query mutation + redirect Stripe Checkout
  • frontend/.../src/components/billing/PricingTable.tsx — 3 tier Nebula Glass (Hero=Pro recommended, Support=Starter/Business), toggle monthly/annual, -25% badge
  • frontend/.../src/components/billing/BillingPage.tsx — modal full-screen con subscription corrente (query DB) + PricingTable

Files modificati:

  • src/store/index.ts — showBilling toggle
  • src/App.tsx — lazy import BillingPage + render condizionale
  • src/components/settings/SettingsPage.tsx — button "Vedi piani Multiverbe" nel tab Billing apre il modal

TypeCheck: ✅ clean (./node_modules/.bin/tsc --noEmit) Build: NON eseguito in sessione (founder fa quando ha env vars)

4. Founder actions completate in sessione

  • ✅ ANTHROPIC_API_KEY settato in Vercel multiverbe-app env (Production+Preview)
  • ✅ VITE_ONBOARDING_V2=true settato in Vercel
  • ✅ Push master Multiverbe (founder ha eseguito git push origin master post sessione)
  • ✅ Stripe OAuth autorizzato (MCP attivo, tools caricati)
  • ⏳ Stripe TEST mode non completato in sessione: founder deve completare profilo Stripe (Connect setup → "Buyers will purchase from you" — Multiverbe NON usa Connect) + switchare Test mode toggle + copiare test API keys

5. Discovery / decisioni

  • Landing page multiverbe.com: NON c'è source locale. È un Vercel project landing separato (deploy via UI/template o repo GitHub non clonato locale). Il folder D:\Desktop\Metaverbe\metaverbe.com\ è la landing Metaverbe (agenzia, dominio metaverbe.com) — diverso brand. Lockdown landing multiverbe.com → solo Vercel Dashboard → Settings → Deployment Protection.
  • Stripe MCP modalità default = LIVE: per evitare di creare prezzi in produzione, abbiamo evitato MCP create_price/create_product. Procediamo via script Node con STRIPE_SECRET_KEY=sk_test_... (idempotent, ripetibile per Live al lancio).
  • Stripe Connect NON usato: Multiverbe vende subscription SaaS direttamente al PMI, è merchant unico. No marketplace, no payout terzi. Connect post Series-A se launch agency partner program.
  • Business Eye v2.32 timeline: aggiungere TODO "Multi-currency Stripe (EUR/USD) trigger lancio Europa/mondo" (founder 2026-05-10: solo CHF first market).

🚦 Pendenze per sessione D

Founder browser actions (15 min)

  1. Completa profilo Stripe Connect step → "Buyers will purchase from you" → Continue → arriva al toggle Test mode
  2. Switch Test mode ON (top-left toggle Dashboard, sfondo arancione)
  3. Copia 2 test keys da https://dashboard.stripe.com/test/apikeys:
    • pk_test_... (publishable, public OK)
    • sk_test_... (secret, NON in chat — solo Vercel env)
  4. Vercel env vars project multiverbe-app (Production + Preview):
    • VITE_STRIPE_PUBLISHABLE_KEY=pk_test_...
    • STRIPE_SECRET_KEY=sk_test_...
    • APP_BASE_URL=https://app.multiverbe.com (success/cancel redirect)
  5. Vercel Password Protection entrambi i project (lockdown pre-launch):
    • Project landing (multiverbe.com): Settings → Deployment Protection → Vercel Authentication o Password
    • Project multiverbe-app (app.multiverbe.com): stesso pattern

Claude actions sessione D

  1. Apply DB migration 2026-05-11a_stripe_idempotency_setup_fee.sql via Supabase MCP (gate: AskUserQuestion — schema prod)
  2. Seed Stripe prices in test mode: founder esegue cd D:\Desktop\Multiverbe\frontend\maind-dashboard\maind-dashboard && STRIPE_SECRET_KEY=sk_test_... npx tsx scripts/seed-stripe-prices.ts → output 9 price_xxx IDs
  3. Vercel env 9 price IDs: founder copia output script in Vercel env vars (VITE_STRIPE_PRICE_* + STRIPE_PRICE_* server-side mirrors)
  4. Webhook endpoint Stripe Dashboard:
    • URL: https://app.multiverbe.com/api/stripe/webhook
    • 8 eventi (lista in api/stripe/webhook.ts:11-20)
    • Riceve whsec_... → Vercel env STRIPE_WEBHOOK_SECRET
  5. Smoke test E2E: dev server → SettingsPage → Billing tab → "Vedi piani Multiverbe" → modal → click Pro Annual → redirect Stripe Checkout → carta 4242 4242 4242 4242 → return → DB row subscriptions insert
  6. TypeCheck + vite build finale
  7. Push master finale (founder)

Bloccanti upstream (non blocca sessione D)

  • Brevo verify domain DNS — debug 2026-05-11 (TXT brevo-code apex Register.it sospetto wrong position). Dopo: B3 SMTP signup confirmation Supabase Auth.
  • Stripe profile completion: residenza CH per evitare problemi legali. Test mode FUNZIONA senza profile completo, ma per Live mode al lancio serve Einzelfirma CH (vedi canon/10-admin-ch-italia-transition.md).

📦 Stat sessione C

  • File creati: 6 (PricingTable, BillingPage, useCheckout, create-checkout-session, seed-stripe-prices, migration SQL)
  • File modificati: 4 (App.tsx, SettingsPage.tsx, store/index.ts, package-lock.json)
  • Commits Multiverbe: 5 (3 leftover sessione A + merge sessione B + 1 feat billing)
  • Commits Multiverbe-Business: 1 pushato (canon v2.32)
  • TypeCheck: clean
  • Linee codice aggiunte: ~1700 (1259 billing + 412 stripe scaffold)

Confidenza: alta. Tutto wiring pronto. Mancano solo env vars + script seed + apply migration + webhook config — tutte azioni 5-15 min ognuna.

Sessione C chiusa: 2026-05-10 sera (contesto Claude full → handoff sessione D)