forgejo_admin
  • Joined on 2025-07-24
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
78. users : id, google_uid, email_hash, plan, quota_remaining, created_at.
a829770c7e Final front-end version for day 1 by Jeen.
forgejo_admin created branch front-end in Vibecode-Together/SEO_iamge_renamer_starting_point 2025-08-04 22:20:38 +02:00
4b82d495b2 Jeens made front end design with all mvp functions without vision ai
forgejo_admin created branch back-end in Vibecode-Together/SEO_iamge_renamer_starting_point 2025-08-04 21:14:44 +02:00
8faf2c9dde new-plan
e0d4d6d8d5 more info for MVP added
6b6df81b1e Added MVP information
92. A compliance suite shall map each requirement ID to a unit‑test prompt following the pattern: "Assert that requirement NN is satisfied by …".
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.
90. Zero‑downtime deploys shall be achieved with rolling updates and readiness probes.
89. Production shall run on Kubernetes with separate pods for API, worker, and front‑end static hosting.
88. CI shall run ESLint, Prettier, unit tests, and Cypress e2e tests on every pull request.