[Enhancement] Certificate service has a hardcoded completion check — real progress tracking not connected

[RUKAYAT-CODER]

Overview

src/services/certificate-service.ts contains a TODO comment at line 41 noting that course completion validation needs to be connected to the actual progress tracking system. Currently, certificate generation may succeed regardless of whether the user has actually completed the course, undermining the certificate's credibility.

Specifications

Features:

• Certificate issuance is gated on verified course completion from the progress tracking system
• Users who have not completed the course receive HTTP 403 with a clear message

Tasks:

• Query the user_progress table for the requesting user and the target course
• Assert that progress >= 100 (or all required lessons are marked complete) before generating the certificate
• Return HTTP 403 with { error: 'Course not completed' } if the check fails
• Add tests covering the incomplete-course rejection case

Impacted Files:

• src/services/certificate-service.ts
• src/app/api/certificates/generate/route.ts

Acceptance Criteria

• Certificate generation fails with HTTP 403 if course completion is below 100%
• Certificate generates successfully when progress is complete
• No hardcoded completion bypass remains

[GOE001]

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

I would like to work on this

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

[Benedict315]

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

Hello please assign this issue to me

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

[Wildflower-mariposa]

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

Hello,

I am excited to contribute to this issue. I have experience collaborating on open-source projects and understand the importance of clear communication and reliable delivery. If assigned, I will provide consistent progress updates and a well-tested implementation.

I would appreciate the opportunity to work on this issue.

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

[drips-wave]

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

🧑‍💻 @Benedict315: 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 🌊