`GET /conversations/:id/messages`: per-device ciphertext shape + `unavailable` marker

[codebestia]

The message-list handler correctly joins message_envelopes filtered to the caller's own deviceId but returns raw row objects instead of running them through the shared serializeMessage helper that GET /:id already uses. Callers can't distinguish "this device has no envelope for this message" from "this message legitimately has no content". There's no dedicated test file for this route.

Acceptance criteria:

• The handler maps each row through serializeMessage, matching the shape GET /:id already produces
• Messages with no matching envelope for the caller's device are explicitly marked unavailable: true
• A dedicated test file covers: normal pagination, an unavailable-envelope case, and cursor correctness

[DavidAkere204]

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

I would like to work on this issue

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

[doctorlight0]

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

Hello Maintainer, I'm interested in working on this issue. After reviewing the requirements, I'm confident I can provide a reliable implementation that aligns with the project's coding standards. I'd appreciate being assigned to it.

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

[femiolutayo]

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

Hello maintainer. I can resolve this issue quickly. Please assign to me. Thank you

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

[ndyugwu]

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

i would like to work on this issue kindly assign me

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

[johdanike]

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

I can pick this up! I will update the message-list handler to map all returned rows through the shared serializeMessage helper, matching the output shape of GET /:id. I will properly surface the unavailable: true flag for missing per-device envelopes, and I'll add the dedicated test file to comprehensively cover pagination, cursor correctness, and the unavailable edge cases. Happy to be assigned!

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

[drips-wave]

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

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