Sync OpenAPI spec: add check-username and product entitlement endpoints

api-reference/openapi.json

@@ -1071,6 +1071,32 @@
         "security": [{ "bearerAuth": [] }],
         "responses": { "200": { "description": "OK" } }
       }
+    },
+    "/api/user/check-username": {
+      "get": {
+        "tags": ["User", "Auth and onboarding"],
+        "summary": "Check username availability",
+        "description": "Returns whether a given username (handle) is available. Case-insensitive check.",
+        "parameters": [
+          { "name": "username", "in": "query", "required": true, "schema": { "type": "string" }, "description": "The username to check." }
+        ],
+        "security": [],
+        "responses": {
+          "200": { "description": "{ success, data: { available } }" },
+          "400": { "description": "Username is required" }
+        }
+      }
+    },
+    "/api/v1/product_entitlement_mapping": {
+      "get": {
+        "tags": ["Products", "Commerce and purchases"],
+        "summary": "Product entitlement mapping",
+        "description": "Returns the mapping of RevenueCat product IDs to entitlements and D-Sports Cash tiers. Used by the mobile app and RevenueCat integration.",
+        "security": [],
+        "responses": {
+          "200": { "description": "{ success, data: { mappings } }" }
+        }
+      }
     }
   },
   "components": {

repositories/d-sports-api.mdx

@@ -1,6 +1,6 @@
 ---
 title: "d-sports-api"
 description: "PWA and backend for the D-Sports fan engagement platform. Next.js, Prisma, Clerk, RevenueCat, Thirdweb."
 icon: "server"
 ---
 
@@ -16,10 +16,10 @@
 | Category   | Technology                    |
 | ---------- | ----------------------------- |
 | Framework  | Next.js 16, React 19          |
-| Database   | PostgreSQL, Prisma 6.8        |
+| Database   | PostgreSQL (Supabase), Prisma 6.8 |
 | Auth       | Clerk 6.x                     |
 | Styling    | Tailwind CSS 4, Radix UI, shadcn/ui |
 | Web3       | Thirdweb, Viem, Wagmi        |
 | Payments   | RevenueCat (purchases-js)     |
 | State      | TanStack Query, TanStack Store |
 | Secrets    | HashiCorp Vault (optional)    |
@@ -28,10 +28,10 @@
 ## Features
 
 - **Locker room** — Social feed, posts, comments, likes, following
 - **Gamification** — Quests, points, achievements, leaderboards, Frontline Pass
 - **Digital collectibles** — NFT-style collectibles, rarity tiers, pack opening, inventory
 - **Shop** — Product catalog, cart, RevenueCat purchases
 - **Wallet** — Web3 wallet, token balances, Thirdweb integration
 - **Interactive games** — Trivia, wheel spin
 - **Team manager dashboard** — Collectible creation, bulk upload, packs, analytics, revenue
 - **Admin** — Impersonation, roles (SuperAdmin, Admin, TeamManager), user management
@@ -49,13 +49,13 @@
 
 This app is the primary API surface for the D-Sports platform. The [API reference](/api-reference/introduction) in these docs covers endpoints and usage; detailed OpenAPI or API specs live in the repo.
 
 ## Season 0.5 leaderboard infrastructure
 
 - Points events are now scoped in `PointsHistory` by both leaderboard and season.
 - Season reset/wipe behavior is unchanged.
 - Legacy Season 0 rows with null scoping are intentionally preserved for backward compatibility.
 
 ### Leaderboard scoring behavior
 
 - Team boards now compute totals from `PointsHistory` rows filtered by both active `seasonId` and the team `leaderboardId`.
 - The global board computes totals from `PointsHistory` rows filtered by active `seasonId` only (cross-board season aggregate).
@@ -67,25 +67,25 @@
 
 - `GET /api/leaderboard?leaderboardId=<id>` resolves and scores a specific board.
 - `GET /api/leaderboard?teamId=<teamId>` resolves (or creates) that team board, then scores it.
 - `GET /api/leaderboard` (no params) returns global leaderboard scoring for the active season.
 - This release does not introduce season reset/archiving behavior changes, and does not remove `LeaderboardEntry.points` yet (planned Season 2 cleanup).
 
 ## Gamification deep dives!
 
 Comprehensive non-admin gamification docs now live in dedicated sections with subsections:
 
 <CardGroup cols={2}>
   <Card title="Gamification docs hub" icon="trophy" href="/repositories/d-sports-api/gamification/index">
     Start here for architecture and behavior docs across quests, points, leaderboards, rewards, and achievements.
   </Card>
   <Card title="Backend coverage status" icon="clipboard-list" href="/repositories/d-sports-api/gamification/coverage-status">
     See exactly what is documented vs missing across all non-admin backend feature domains, not only gamification.
   </Card>
 </CardGroup>
 
 ## Backend domain deep dives
 
 Each non-admin backend domain now has dedicated folderized docs with architecture and behavior subsections.
 
 <CardGroup cols={2}>
   <Card title="Auth and onboarding" icon="shield-check" href="/repositories/d-sports-api/auth-onboarding/index">
@@ -107,7 +107,7 @@
     User-facing report intake and moderation model lifecycle.
   </Card>
   <Card title="Platform and infrastructure" icon="server" href="/repositories/d-sports-api/platform-infra/index">
     Streams, sync routes, backfills, and non-admin operational patterns.
   </Card>
   <Card title="Backend coverage status" icon="clipboard-list" href="/repositories/d-sports-api/gamification/coverage-status">
     Track what is documented, partial, or not yet documented across all non-admin backend domains.
@@ -115,5 +115,5 @@
 </CardGroup>
 
 <Card title="Ecosystem overview" icon="map" href="/repositories/ecosystem-overview">
   See how d-sports-api fits with the site, native app, and Mic'd Up.
 </Card>