feat: add Team billing tier

Widens the tier enum from free/pro to free/pro/team and every
"free" | "pro" cast that assumed exactly two tiers (~30 call sites:
every AI route's withAiQuota/checkAndIncrementTierLimit call, admin
user/invite management, upload quota checks, OpenAPI schemas). Team
sits above Pro with genuinely unlimited recipes/public-recipes (the
-1 sentinel, which Pro doesn't actually use — Pro uses large finite
numbers instead) and a higher AI-call/storage cap. Seeded via
db:seed, editable afterward from Admin > Tiers.

role (user/moderator/admin — permissions) and tier (free/pro/team —
billing limits) stay separate concepts, as they already were; this
does not touch role-based permissions.

Requires migration 0043 to run against a live DB — not applied in
this sandbox (no Docker here); run `pnpm db:migrate` then `pnpm db:seed`.

v0.44.0
This commit is contained in:
Arnaud
2026-07-17 17:34:13 +02:00
parent c5a8f94b26
commit c31ab8771a
46 changed files with 5271 additions and 51 deletions
+3 -2
View File
@@ -15,12 +15,12 @@ import { Label } from "@/components/ui/label";
interface UserEditorProps {
userId: string;
currentRole: "user" | "moderator" | "admin";
currentTier: "free" | "pro";
currentTier: "free" | "pro" | "team";
}
export function UserEditor({ userId, currentRole, currentTier }: UserEditorProps) {
const [role, setRole] = useState<"user" | "moderator" | "admin">(currentRole);
const [tier, setTier] = useState<"free" | "pro">(currentTier);
const [tier, setTier] = useState<"free" | "pro" | "team">(currentTier);
const [saving, setSaving] = useState(false);
async function handleSave() {
@@ -68,6 +68,7 @@ export function UserEditor({ userId, currentRole, currentTier }: UserEditorProps
<SelectContent>
<SelectItem value="free">Free</SelectItem>
<SelectItem value="pro">Pro</SelectItem>
<SelectItem value="team">Team</SelectItem>
</SelectContent>
</Select>
</div>