forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#27
2025-08-04 18:46:47 +02:00
27. The client shall block any drag event containing > N files, where N = user's remaining monthly quota.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#26
2025-08-04 18:46:20 +02:00
26. The Dashboard shall feature a drag‑and‑drop zone that accepts only .jpg, .jpeg, .png, .gif, and .webp MIME types.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#25
2025-08-04 18:45:33 +02:00
25. Cancellation in Stripe shall downgrade the user to Basic at the period's end and persist renamed files already created.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#24
2025-08-04 18:44:56 +02:00
24. Successful Stripe webhooks shall update the User's plan field and reset their quota counter immediately.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#23
2025-08-04 18:44:43 +02:00
23. The Upgrade flow shall open a Stripe Checkout session in a modal.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#22
2025-08-04 18:44:18 +02:00
22. The Billing page shall display current plan, remaining quota, next renewal date, and an "Upgrade" button.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#21
2025-08-04 18:43:59 +02:00
21. Password‑based logins are explicitly out of scope for V1.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#20
2025-08-04 18:43:32 +02:00
20. The system shall store only the Google user ID, display name, and email hash, never the raw OAuth access token.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#19
2025-08-04 18:43:14 +02:00
19. The system shall create a new User record on first successful OAuth callback.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#18
2025-08-04 18:42:52 +02:00
18. The sign‑in button shall initiate Google OAuth 2.0 with email scope only.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#17
2025-08-04 18:42:15 +02:00
17. Administrators can view global usage stats, force‑reset quotas, refund payments, and ban accounts.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#16
2025-08-04 18:41:44 +02:00
16. Max users inherit Basic rights and raise the quota to 1 000 images per month.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#15
2025-08-04 18:41:24 +02:00
15. Pro users inherit Basic rights and raise the quota to 500 images per month.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#14
2025-08-04 18:41:08 +02:00
14. Basic users can upload ≤ 50 images per month and access all core renaming features.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#13
2025-08-04 18:40:38 +02:00
13. Anonymous visitors can view the marketing landing page but cannot upload images.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#12
2025-08-04 18:40:20 +02:00
12. The product shall monetise via tiered monthly quotas and Stripe‑handled subscriptions.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#11
2025-08-04 18:40:03 +02:00
11. The product shall output renamed images that are search‑engine‑friendly, syntactically safe for all major file systems, and semantically descriptive of image content.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#10
2025-08-04 18:39:37 +02:00
10. The product shall let any authenticated user rename many images in one batch using a combination of user‑supplied keywords and automatic computer‑vision tags.
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 17:25:45 +02:00
forgejo_admin
created branch main in Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 16:04:50 +02:00