[Refactor] Approval workflow uses in-memory store — all submissions lost on restart

[RUKAYAT-CODER]

Overview

src/app/api/approvals/route.ts uses a module-level Map as its data store. Content submitted for approval disappears on every server restart or cold start. In a production environment with autoscaling or periodic restarts, this makes the approval workflow completely unreliable.

Specifications

Features:

• Approval submissions are persisted to the database
• The approval queue survives restarts and works across multiple server instances

Tasks:

• Create a content_approvals table with all ApprovalItem fields
• Replace in-memory CRUD operations with SQL queries
• Update GET/POST/PATCH handlers to be async with proper error handling
• Migrate the generateId helper to use uuid for database-compatible IDs

Impacted Files:

• src/app/api/approvals/route.ts
• src/lib/db/ (new migration)

Acceptance Criteria

• Approval items persist across server restarts
• Two concurrent server instances see the same approval queue
• GET /api/approvals returns items from the database, not module memory

[Windowlight]

@Windowlight has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'm interested in this issue and have experience with contracts, backend systems, and frontend implementation.
I've reviewed the issue requirements and my plan is to:
• Understand the existing implementation.
Implement the requested changes.
•Add tests where applicable.
•Submit a clean, well-documented PR.
I can start immediately and will provide regular progress updates as I work through the task.
Thanks for considering my application.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Windowlight to this issue.

[fredericklamar342-prog]

@fredericklamar342-prog has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Kindly assign to I can implement

ℹ️ Repo Maintainers: To accept this application, review their application or assign @fredericklamar342-prog to this issue.

[MerlinTheWhiz]

@MerlinTheWhiz has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi there, let me handle this. I can implement this nicely.
Please assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MerlinTheWhiz to this issue.

[drips-wave]

Congratulations, @MerlinTheWhiz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @MerlinTheWhiz: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊