[Enhancement] Conference service has six unimplemented API endpoint stubs

[RUKAYAT-CODER]

Overview

src/services/conferenceService.ts contains six functions with TODO comments indicating they need real API integrations. These include creating meetings, listing participants, toggling recording, and ending sessions. The conference UI may appear functional but all operations fail silently or return mock data.

Specifications

Features:

• All six conference service methods are wired to real backend endpoints
• Meeting state is persisted

Tasks:

• Implement the six missing API routes in src/app/api/conference/
• Replace each TODO stub in conferenceService.ts with real fetch() calls to those routes
• Implement meeting state persistence in the database
• Add integration tests for each endpoint

Impacted Files:

• src/services/conferenceService.ts
• src/app/api/conference/ (new)

Acceptance Criteria

• All six conference methods return real data from the backend
• No TODO comments remain in conferenceService.ts
• Integration tests cover the happy path for each endpoint

[heymide]

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

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

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

[Abdulrasaq1515]

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

I want to implement the six missing conference API endpoints because the conference UI appears functional but all operations fail silently or return mock data. The six methods (create meeting, list participants, toggle recording, end session, get meeting status, update meeting) need real fetch calls to backend routes with meeting state persistence.

Relevant experience:

API implementation — implemented conference API endpoints for 2 platforms; meeting CRUD, participant management

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

[Bojest001]

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

Hi maintainer I will to work on this issue

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

[olaleyeolajide81-sketch]

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

I would love to work on this issue

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

[drips-wave]

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

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