[BACKEND] Add conversation mute/archive for a user

[codebestia]

Add is_muted and is_archived boolean columns to conversation_members. Expose PATCH /conversations/:id/settings accepting { muted?: boolean, archived?: boolean }. Archived conversations should be excluded from GET /conversations by default unless ?archived=true is passed.

Acceptance criteria:

• Muted/archived state is per-user, not per-conversation
• Archived conversations hidden by default in list

[cyberdocs120]

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

I’d like to work on this issue because it improves conversation management and user experience while involving backend patterns I’ve worked with extensively, including per-user conversation preferences, filtered query logic, and authenticated settings updates. I have experience building messaging and collaboration backend systems with Node.js, Express, TypeScript, and relational databases, including features like conversation membership metadata, soft visibility controls, and user-specific state management. I’ve implemented PATCH endpoints, schema migrations, filtered listing behavior, and authorization checks to ensure settings apply correctly at the membership level rather than globally. For this task, I’d add the is_muted and is_archived fields to conversation_members, implement the settings update endpoint with proper validation and auth checks, and update the conversations listing logic so archived conversations are excluded by default while still retrievable through the ?archived=true query parameter.

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

[Damola09]

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

I’d like to handle this feature. I’ll add per-user mute/archive settings at the conversation member level, wire the new PATCH endpoint, and update conversation listing behavior so archived chats stay hidden unless explicitly requested.

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

[drips-wave]

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

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