[baba-dev]

ClubKeep B3 — Unified Club Experience, Guided Setup & Public Discovery

Implements the owner-approved B3 architecture in one coherent PR, based on merged B1/B2 and existing authentication. All five club verticals are supported: Gym/Fitness, Yoga, Dance, Sports and General.

Delivered

• Additive Prisma 7/PostgreSQL 17 migration: typed club verticals; separate setup and lifecycle statuses; persistent wizard progress; publication draft/approved-revision records; atomic one-pending-review constraint. Existing clubs migrate to LEGACY_ACTIVE to preserve live operations.
• Five-step mandatory new-club setup: type, country/currency/timezone and business details, optional branding, required first plan using the B1 plan service, launch review. Server-side readiness enforcement covers operational B1/B2 services, while the first-plan endpoint remains owner-only and transaction-scoped. Concurrent step writes validate version.
• Responsive Luxe business navigation, owner/staff/member club home, club switcher via /home; all existing routes and seven-day member invitation mechanism remain intact.
• Club settings allow a legacy or new club owner to edit club vertical, city and country without rewriting historical records.
• Owner profile editor, explicit opt-in publication requests, approved public profile snapshots, public search by name/category/city at /discover/clubs, canonical /c/[slug] pages.
• Dedicated PLATFORM_ADMIN moderation for approve/reject/suspend/reinstate; compare-and-swap state changes protect an owner unlisting their profile. No implicit club-membership rights for platform admins.
• Currency-aware first-plan pricing using existing ISO currency minor-unit parser.
• PG17 B3 tenant/uniqueness tests and CI registration, B3 implementation contract.

Verification — final commit 7bfa552f563465b67ca82550f1074ed0b754b77c

GitHub Actions CI run #43013271534: SUCCESS.

• ✅ x64 lint, Prettier check, typecheck, unit tests, native service smoke, Next build and standalone runtime.
• ✅ PostgreSQL 17 fresh/legacy migrations, repeated no-op, schema drift, identity/B1/B2/B3 schema and invitation checks.
• ✅ ARM64 validation, typecheck, standalone build and startup smoke.
• ✅ Temporary feature-branch formatter workflow removed from the PR before final CI.

Preserved limitations / independent release gates

• Not deployed or merged by this PR. Production activation and any automatic deployment of main must remain under the existing release and security gates.
• Real Google/passkey/magic-link enrollment, age/guardian and regional policies must be authorized before opening public signup. No SMS or clinical functionality.
• Staging end-to-end, camera/scanner hardware, 360/390px responsive and keyboard/screen-reader tests, and verified off-host restore remain human acceptance requirements, not implied by green CI.
• Private first-release core works for each vertical; full class packs, batches, schedules, sports scoring and payments are later engines. This PR does not claim them shipped.
• External logo URL is configuration only; secure image uploads and full light-mode parity remain follow-up visual-hardening work and should not be claimed complete.
• Business Free quotas and Growth/Pro sponsored seat counts remain unresolved; no values invented.

Merge/release recommendation

Code review the schema/route authorization, preview all five setup journeys and public moderation in staging, verify migration/restore and hardware QA, then merge deliberately. A merge may trigger the configured production workflow depending on CLUBKEEP_AUTO_DEPLOY.