forgejo_admin
0 followers · 0 following
  • Joined on 2025-07-24
Repositories
1
 Projects Packages Public activity Starred repositories
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#49 2025-08-05 20:11:51 +02:00
49. When all jobs in a batch reach status "DONE", the client shall auto‑navigate to /batch/{batch_id}/review.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Auto-…

49. When all jobs in a batch reach status "DONE", the client shall auto‑navigate to /batch/{batch_id}/review.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#48 2025-08-05 20:11:51 +02:00
48. The Proposed Filename shall always include at least one token derived from the user's original Keyword Set.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Filen…

forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#52 2025-08-05 20:11:50 +02:00
52. Pressing "Regenerate this name" on a row shall re‑run the naming algorithm with a new random seed.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: "Rege…

52. Pressing "Regenerate this name" on a row shall re‑run the naming algorithm with a new random seed.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#51 2025-08-05 20:11:50 +02:00
51. Editing a Proposed Filename shall update the entry's state to "CUSTOM".

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Inlin…

51. Editing a Proposed Filename shall update the entry's state to "CUSTOM".
53. The "Download ZIP" button shall remain disabled until at least one row exists and no rows are in "PROCESSING".
55. The ZIP archive shall preserve original EXIF metadata.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#54 2025-08-05 20:11:15 +02:00
54. Clicking "Download ZIP" shall trigger a GET to /api/batch/{batch_id}/zip; the server shall stream a ZIP archive containing renamed files.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: ZIP…

54. Clicking "Download ZIP" shall trigger a GET to /api/batch/{batch_id}/zip; the server shall stream a ZIP archive containing renamed files.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#53 2025-08-05 20:11:15 +02:00
53. The "Download ZIP" button shall remain disabled until at least one row exists and no rows are in "PROCESSING".

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Downl…

forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#57 2025-08-05 20:11:14 +02:00
57. The server shall decrement the user's remaining quota atomically at the start of each job.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Atomi…

57. The server shall decrement the user's remaining quota atomically at the start of each job.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#56 2025-08-05 20:11:14 +02:00
56. A usage table shall store one row per successfully renamed image with columns user_id, timestamp, and byte_size.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Usage…

56. A usage table shall store one row per successfully renamed image with columns user_id, timestamp, and byte_size.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#55 2025-08-05 20:11:14 +02:00
55. The ZIP archive shall preserve original EXIF metadata.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: ZIP…

60. The API shall respond to the /healthz probe in < 150 ms 95th percentile.
forgejo_admin commented on issue Vibecode-Together/SEO_iamge_renamer_starting_point#59 2025-08-05 20:11:13 +02:00
59. All public pages shall score ≥ 90 on Google Lighthouse performance and accessibility audits.

✅ Resolved in v1.0.0 Release

This requirement has been fully implemented in the production-ready v1.0.0 release of the AI Bulk Image Renamer SaaS platform.

Implementation Details: Front…

59. All public pages shall score ≥ 90 on Google Lighthouse performance and accessibility audits.