fix: recipe/storage tier limits are lifetime totals, not monthly (v0.58.0)
Recipe count and storage usage shared the monthly user_usage bucket with AI calls, so both incorrectly reset every month even though nothing was deleted. Only AI calls should be monthly. Recipe count and storage are now derived live from real data (recipes, recipe/review photos, avatar) instead of a counter — deleting a photo or recipe is itself the "decrement", no extra wiring needed. Storage size is tracked per-row (recipePhotos.sizeMb, ratings.photoSizeMb, users.avatarSizeMb) and threaded through presign -> upload -> save. Also fixes avatar removal silently no-oping (client sent a field the PATCH schema didn't recognize). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -419,8 +419,8 @@
|
||||
"apiKeys": "API Keys",
|
||||
"webhooks": "Webhooks",
|
||||
"usage": {
|
||||
"title": "Usage this month",
|
||||
"description": "Resets at the start of each month ({month}).",
|
||||
"title": "Usage & limits",
|
||||
"description": "AI calls reset monthly ({month}). Recipes and storage are lifetime totals.",
|
||||
"aiCalls": "AI calls",
|
||||
"recipes": "Recipes created",
|
||||
"storage": "Storage",
|
||||
|
||||
Reference in New Issue
Block a user