forgejo_admin
closed issue Vibecode-Together/SEO_iamge_renamer_starting_point#79
2025-08-05 14:54:38 +02:00
79. batches : id, user_id, status, created_at.
forgejo_admin
commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#78
2025-08-05 14:54:34 +02:00
78. users : id, google_uid, email_hash, plan, quota_remaining, created_at.
✅ Issue Completed and Verified
This requirement has been successfully implemented in the codebase:
Verification Results:
- Location:
prisma/schema.prisma:18-31
- *Implementation…
forgejo_admin
closed issue Vibecode-Together/SEO_iamge_renamer_starting_point#78
2025-08-05 14:54:03 +02:00
78. users : id, google_uid, email_hash, plan, quota_remaining, created_at.
forgejo_admin
pushed to front-end at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-05 00:15:42 +02:00
forgejo_admin
created branch front-end in Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 22:20:38 +02:00
forgejo_admin
pushed to front-end at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 22:20:38 +02:00
forgejo_admin
created branch back-end in Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 21:14:44 +02:00
forgejo_admin
pushed to back-end at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 21:14:44 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 21:09:38 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 21:04:57 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 21:01:18 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 20:51:20 +02:00

forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 20:49:55 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 20:48:38 +02:00
forgejo_admin
pushed to main at Vibecode-Together/SEO_iamge_renamer_starting_point
2025-08-04 20:39:37 +02:00
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#92
2025-08-04 19:24:02 +02:00
92. A compliance suite shall map each requirement ID to a unit‑test prompt following the pattern: "Assert that requirement NN is satisfied by …".
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#91
2025-08-04 19:23:21 +02:00
91. Every sentence numbered 10‑90 defines a single, atomic requirement that an LLM can verify by querying the deployed system's observable behaviour, data, or codebase.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#90
2025-08-04 19:22:30 +02:00
90. Zero‑downtime deploys shall be achieved with rolling updates and readiness probes.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#89
2025-08-04 19:21:43 +02:00
89. Production shall run on Kubernetes with separate pods for API, worker, and front‑end static hosting.
forgejo_admin
opened issue Vibecode-Together/SEO_iamge_renamer_starting_point#88
2025-08-04 19:21:09 +02:00
88. CI shall run ESLint, Prettier, unit tests, and Cypress e2e tests on every pull request.